Trouble login into CallPilot and staying connected

[Watchoutforsnakes]

Greetings all,

We have been experiencing an issue with accessing our Callpilot Manager (4.0) from a client machine. Ever since a cp-pm card went bad in our CS1000, Not sure if that has something to do with it or just a coincidence.

Sometimes we are able to login to Callpilot Manager for a short bit. Long enough to reset a VM password, but soon after it will start displaying error "Time zone AOS COM object is unable to retrieve server time zone ID -2147024891#(Null)". If we try logging out and back in again we'll receive an error "failed to connect to CallPilot server. Check server information and try again. If this problem persists the server may be improperly configured." sometimes the number "[-2147467259]" will follow the error other times it'll be "[-2146827781]". After sometime has passed we'll try logging in again, and sometimes it'll allow us to, but other times it'll display one of those last two errors I listed.

We have tried looking though the events in Callpilot manager and though the Windows server event viewer, but nothing appears that unusual.

We have made sure the time on the CallPilot Server is adjusted to whats on our CS1000.

Tried continually pinging the CP server from the client machine to see if it starts to loose it's connection, but that doesn't appear to be a problem.

We're not sure what else to look for, and similar problems online seem to be resolved by reimaging the CP server, but that's not something we have experience doing.

If anyone has any suggestions on where to look or anything to try, it would be greatly appreciated!

 

[Wanebo]

First thing to try is make sure the time on your server agrees with the CS1K time (it should be synching from the CS1K no matter what you are setting in Windows) and Windows should not be set to use an NTP server or automatically update in any way.

The second thing (if you can stand the reboot required after) is to run through the config wizard, reload the language CD's at the end of that and the do the reboot.

Doing that does a very deep reset on a lot of the CP services and processes and can fix a lot of weird issues like what you are describing.

 

[Watchoutforsnakes]

Thank you for the suggestion, but no dice. We were painfully able to run the Config Wizard, Callpilot would have a hard time staying connected during the wizard, so The only way we managed to get through it without being disconnected was to restart the "Callpilot AOS" service, for some reason this allowed us to refresh the page and continue with the wizard. After the server came back up it tried starting CallPilot and after 4 hours of waiting for it, we decided to restart it again. Thankfully CallPilot came back up after the 2nd restart, but still having the connection issues with CallPilot Manager.