Using v7.05 SP4 March w/ SQL 2005 Std x86.
I had a user encounter a runtime error twice today while trying to register/print/post an 'IM Sale Return' Inventory Transaction. She had entered the transaction, clicked the green triangle, selected 3 copies to be printed in the print dialog box, and then clicked 'OK.' Then the following error appeared.
Run-time error -2147418105 (80010007): Automation error The callee (server [not server application]) is not available and disappeared; all connections are invalid. The call may have been executed.
I shadowed her TS session and we tried to register/print/post the transaction once again, and when I was watching it worked fine. 3rd time's a charm.
This exact error is addressed in Sage KBID 486913, but it's for a completely different scenario. It has to do with when a user is in SM -> User Preferences and attempting to change their password. It also says it's fixed in the March '08 update, which is what we're using. But again it's a completely different scenario so I don't think that particular KBID is relevant.
My question is this... Does anyone happen to think that this particular error might be eliminated by using the "SQL Native Client" ODBC driver instead of the standard SQL Server ODBC driver? Supposedly using the "SQL Native Client" corrects the error sometimes encountered in AP register posting "Error 4600 occurred at frmRegister in Procedure Form_QueryUnload. Connection is busy with results for another hstmte." I've not yet made the switch to the "SQL Native Client" though. I'm just curious if anyone feels that the error we saw today in IM Transactions might also be resolved by using the "SQL Native Client."
Thanks for any insight you may have about this.
), interestingly enough, with the five users here at our headquarters building using MAS on local clients (XP SP3) for the last six months, three of which are full-time users and two of which are only occasional users, they have probably seen about six errors in that time. We also still have a Windows 2000 TS in use by about six users, and we have never seen an application error on it. We only see the application errors on 2003 and XP. And I've certainly scoured the old Sage user-forum for answers on this, but have come up empty-handed everytime. We've been working on solving this random application error issue since April, and as far as I know Sage is still working on it.