Overview
If you are receiving a dsiEMVClientX "Socket Error Trying to Connect Error 3006" or "Error trying to Connect Error 2006 4003". Although similar they may indicate different remediation paths.
Error trying to Connect Error 3006 4003
This error looks like the Datacap deployment id has not been activated correctly when there is no Datawire ID. The customer will need to contact their Merchant Service provider and ask them to allow the Datawire ID to be re-provisioned.
- A Datawire account exists for the MID/TID entered, but is either not provisioned for self-registration or the Datawire ID has already self-registered. Contact the First Data rep to update the account to support the DID self-registration service (SRS) reset.
- Once the Datawire ID has been reset, Escalate to development to have the Datacap deployment ID reset.
- Restart the NETePay Service
- Check to ensure the NETePay Service is configured to auto-start
- Open the "Setup Wizard"
- Navigate to "Payment Processing"
- Choose your processor
- Review the departments and configuration information.
- Ensure the EMV Server IP is set to the correct IP address where Netepay Datacap is running.
- If you are using System Five departments feature in the case of multiple locations. EMV Server IP and Merchant ID information will need to be completed for each department to process payments.
Socket Error Trying to Connect Error 3006
The "Socket Error Trying to Connect Error 3006" can be reported for multiple reasons. The solutions are listed in the most common causes.
Solution 1) Check if Datacap Netepay is not running
This error may indicate the Datacap Netepay service is not running. Check the workstation that is supposed to have the Datacap NETePay service is running and if not restart the service.
Solution 2) Review for Incomplete Payment Processing Setup
This may indicate the Payment Processing setup is configured incorrectly or not configured at all. Check the Payment Processing server setting and deployment ID for the department. They could be pointing at an incorrect Datacap Netepay server or deployment ID.
Solution 3) Review Incoming Firewall Settings
This solution will typically require a consult with a customer's IT professional who maintains or configures their network firewall settings. Unblocking port 9000 (unless a different port has been configured) will need to be allowed into the network running Datacap NetePay. Additional information on troubleshooting and testing is available in this solution article.