| Item | Description |
|---|---|
| Error message from M3 | Failed to access the WSDL at: http://<M3Server>:<Poort>/webservice/UploadInvoiceDataService?wsdl. It failed with: Connection refused: connect |
| M3 programs | None - this occurs on the MEC server |
| Type of message | Connection error |
| Has the invoice already been (partly) posted in M3? | No - no connection could be established, so no new data was processed in M3. |
What does this message mean?
No connection can be established between AP Automation and M3.
What to check
- Ask your own IT department whether any issues with the MEC server are known.
- If everything is in order there and the message keeps occurring, raise a case with ISPnext.
How to process the invoice further
Because no connection could be established, no new data should have been processed in M3. Invoices with this message can therefore in principle be submitted again.
⚠️
Attention: This applies to this message only. If the connection was established and then dropped, it is unclear whether the invoice was processed. In that case, check in M3 first.
More information
For a dropped connection, see M3 error message: Error indicates a webservice connection error (WebServiceException). There you may not submit the invoice again without checking.
The article M3 error messages - introduction shows how the M3 error messages are organised and describes the approach that applies to all of them. If you are looking for a specific message, search for the text of the error.