This problem has now surfaced at two clients running version 5.
A response would be helpful
Hi Arline, are there any anti-virus products on these servers? We have found that Kaspersky antivirus can produce some very strange errors, which went away when we switched it off. Next problem is how to keep the AV but stop it affecting IMan.
Realisable Software Ltd provides code-free, cost-effective applications integration solutions for SMEs. Our core IMan product is designed to integrate almost any application with a number of Sage solutions and online payment processors.
Looking to purchase IMan, please see our resellers here.
Realisable Software
Ph: +44 (0) 208 123 1017
Copyright © Realisable. All rights reserved.
Realisable is a registered trademark
Realisable Software Ltd provides code-free, cost-effective applications integration solutions for SMEs. Our core IMan product is designed to integrate almost any application with a number of Sage solutions and online payment processors.
Looking to purchase IMan, please see our resellers here.
Realisable Software
Ph: +44 (0) 208 123 1017
Copyright © Realisable. All rights reserved.
Realisable is a registered trademark
Realisable Software Ltd provides code-free, cost-effective applications integration solutions for SMEs. Our core IMan product is designed to integrate almost any application with a number of Sage solutions and online payment processors.
Looking to purchase IMan, please see our resellers here.
Realisable Software
Ph: +44 (0) 208 123 1017
Copyright © Realisable. All rights reserved.
Realisable is a registered trademark
Unclear about the root cause here but we are suddenly having difficulty where the Sage 300 connector that points to the one of the Sage 300 databases has started throwing an error:
"The server threw an exception. (Exception from HRESULT: 0x80010105 (RPC_E_SERVERFAULT))"
There is another Sage 300 connector pointing to a different Sage 300 company that is working fine. I have created a new Setup record for the problematic Sage 300 company database and it is also failing.
I tried deleting & re-adding Sage 300 connectors and they fail with the same problem.
Previously, the connector was creating Sage 300 orders without a problem.
I tested another job that points to this same Sage 300 database and it's having the same issue.
It's unclear how to troubleshoot this as it suggests something is fundamentally wrong with the Sage 300 connector, but only the one pointing to this database. I checked the credentials, changed them to the ADMIN credentials, and both give the same results.
Thank you for any advice.