I would first check to see if SEC Solutions (Cypher1) is compatible with v30.1.143.0, this would be a valid reason for the above error.

I'll leave this post open in case anyone has direct experience of using SEC Solutions with Sage 50 Accounts v30.1, but I would suggest checking with the third party to see if they can advise that their software is compatible and offer appropriate support.

Ian

I would first check to see if SEC Solutions (Cypher1) is compatible with v30.1.143.0, this would be a valid reason for the above error.

I'll leave this post open in case anyone has direct experience of using SEC Solutions with Sage 50 Accounts v30.1, but I would suggest checking with the third party to see if they can advise that their software is compatible and offer appropriate support.

Ian

Response from SEC

"Yes, Cypher1 is compatible with v30.1.143.0, and has been since March when we released the update.

 No other Sage v30 users are having any issues, and the only time we had this error was with v27, and the users uninstalled/ reinstalled Sage which resolved it, we made no changes on our end to resolve the issue."

We have uninstalled and reinstalled sage but issue still exists.

Is the Accounts application on the same machine as Cypher1 able to connect to, and open the data? It is very possible that the Cypher1 application is being blocked access to the port on the server running the data service (TCP 32230 see this link for more info https://gb-kb.sage.com/portal/app/portlets/results/viewsolution.jsp?solutionid=200427112311452&hypermediatext=null#). If it is blocked for Cypher1 you would need to speak to your IT support to get this unblocked.

Hope that helps

The server that the software is installed on does not post to accounts however doesnt generate any errors and that the port is allowed on both the device and server inbound on the advised TCP port.

The issue still remains.