Unknown Sage error "1.4172.37" (5 replies)
After more testing, it appears that we are getting the same error when we attempt to connect to other companies in Sage.
Attempting to connect to any of the companies via the Sage interface works fine with no errors/popups.
Randy, is this site or existing?
We've had the website up for a few months, if that's what you're asking.
Randy, the error is a Session initiation error.
Unfortunately, in these instances there is almost no other messaging, so the error you're receiving is all that IMan is receiving.
As a first pass I would restart the server, then attempt the following:
a. Ensure the Sage300 workstation is installed correctly. Yes, you can open Sage, but is it actually still installed correctly (the UI masks a multitude of errors). Check path statements, check the exe is loading from the same location as the registry (not a local path and a UNC path).
b. Redo permissions.
c. Reinstall the Sage300 Workstation.
Thanks
After connecting with the customer we found the following issues:
a. Running the integration from the command line resulting in an error to do with the CRM integration installation.
b. Attempting to alter a customer record (changing the name and saving) from within the Sage300 UI resulted the screen freezing and no error.
It would appear there's an install/module issue with the CRM integration installation.
Background:
We are getting a weird error back from Sage. We've dealt with something similar in the past where there was a "Restart Maintenance" screen in Sage which needed to be closed for IMan to connect properly. This time, when we open Sage, there are no popups to close.
When attempting to use a Sage 300 connector to connect to a certain company, I am getting the error "1.4172.37". When I change the System Connector dropdown to a different company, the error appears to go away, which seems to indicate that there is something wrong that that 1 company.
When I log into Sage, there are no errors that pop up.
I've turned on debug logging in appconfig.xml, but that didn't write anything to the log.