The Basware integration encounters a communication error during document processing, which prevents successful data exchange. The error is generally generated by the BaswareLISTENER component while executing the BaswareGET task. The error below was encountered on the QAD side.
<?xml version="1.0"?> <ErrorMessage xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <ErrorMessageRow> <Component>BaswareLISTENER</Component> <Taskname>BaswareGET</Taskname> <Date>05/06/2025 03:16:17.056</Date> <DocumentType>NTFT</DocumentType> <Info_1>XXWRKFL</Info_1> <Info_2>Basware</Info_2> <Error>HTTP BASW COM ERROR/Client socket not connected(max retry:5)</Error> <Info_3>einvoice-sending@yfai.interiors.mx</Info_3> <Info_4>OUT</Info_4> <Info_5>929a8605-fee9-4526-8989-c2bca558ebe600065393001</Info_5> <Info_6/> <LastOperation>BaswareGET</LastOperation> </ErrorMessageRow> </ErrorMessage>
This issue is not related to the Basware application. It is caused by an incorrect or unavailable DNS IP configuration on the MM Server on the customer side. Due to the DNS server issue, the system is unable to establish the required network connection, which can result in repeated connection failures and prevent the client socket from being established.
The DNS server configuration on the MM Server must be reviewed and corrected by the QAD IT Team. This is an infrastructure and network configuration issue within the customer’s environment, and no changes or fixes are required on the Basware side.
Once the DNS issue is resolved, the customer will be able to establish a successful connection, and Basware communication will resume normally.
Reference cases:
BWCS2734267
BWCS2307881