Did you ever determine what code 1.3775.37 means? (1 reply)
In short 'No'.
There is however a series of cryptic errors resulting from failures in Session.Init
We recently recieved a support issue where Session.Init was failing with the error '1.3700.37'. The customer reported 'that IMAN could not reach the Accpac server'. A restart fixed this.
Historically we've also seen other error codes such as '1.3706.37'.
I can see the common theme of .37 as the last sequence in the error code, but the second sequence , after the 1. starts with 37.
Perhaps there's a resource lookup that's failing (and has been for the age of eternity)?
Did you ever determine what 1.3775.37 means when you are calling .init on a Sage Session? I have a utility that will log on to Sage and run macros and then log off. It seems that if the macro runs particularly quickly, there’s a chance that A4wVBA doesn’t close down and leaves the macro running. The macro code has completed (I’ve confirmed from log files) but the macro stays open. After that, subsequent attempts to .init a session result in 1.3775.37.