We have an ongoing issues with Quickbooks Point of Sale (POS) where periodically POS client workstations lose connectivity with the server. Once this happens we have found no way to get the client computers to reconnect on their own, including by rebooting and renaming the WSActivity.xml as suggested in one article. The only workarounds we have found are to either going to single user mode and back to multi-user, or to switch to a another DB then back again. However, these are increasingly inconvenient workarounds, as it requires staff at working registers to all quit POS, while implementing the above workaround, as while this used to happen maybe only monthly it has become more frequent including happening the last three days in a row, and today more than once. We really need to find out the root cause of this issue as we cannot continue on like this for much longer. If this helps, 1) the network itself is solid, and the clients never actually lose network connectivity to the POS server as the POS server is also the file and printer server for these workstations and those functions continue uninterrupted, and 2) once one POS station disconnects, if you go to another workstation that is still working and click on File, then Company Operations, even the working workstations are unable to locate the server (yet they continue working). This makes be believe that perhaps some service on the server that advertises the existence of the server to the workstations just quits working. Hopefully some Intuit developer familiar with the Sybase back-end sees this and can tell me how to resolve, or at least further troubleshoot my issues. I am working on getting network traces now. Please, and thanks . . .
... View more
The Log for Intuit QB Point of Sale (POS) starts cleanly, but then when I log into the server it logs the following 2 error messages: * Login procedure 'sp_login_environment' caused SQLSTATE '52W09' * Procedure 'sp_login_environment' not found A quick search found this reported on Sybase's site, and they referred the user to Intuit, but I found no sign of this error when searching Intuit's site, with or without a resolution/solution. How serious are these errors, and what does this error mean? More importantly, how do I fix it? Thanks . . .
... View more