Problems and Bug Reports

Re: V4.0 operator lockup problems

robsoninc — Tue, 13 Nov 2007 20:45:56 GMT

That wasn't our issue. Now we get an error and can't start SightMax. It asks us to report it to Microsoft. Tried to reinstall the app, same issue. I'll try to reinstall .net 2.0

Weird.

Re: V4.0 operator lockup problems

neburton — Mon, 12 Nov 2007 17:08:35 GMT

Any ETA on 5.0?

Re: V4.0 operator lockup problems

eweber — Mon, 12 Nov 2007 16:32:31 GMT

Sure, sorry for the delay.

If the system goes into hibernation or the server drops connection, the operator console doesn't exactly shut down gracefully. You probably need to kill the sightmax operator console from the task manager. In 5.0 we rewired the disconnect code so you can gracefully shutdown the operator console if you get abnormally disconnected.

Thanks.

Eric Weber

Re: V4.0 operator lockup problems

neburton — Thu, 08 Nov 2007 17:31:16 GMT

Anyone from Smartmax like to comment?

Re: V4.0 operator lockup problems

robsoninc — Mon, 05 Nov 2007 21:31:40 GMT

Yeah ours does that too. We use:

Version:        4.0
Build:        0.0 (6/21/2007 3:06:24 PM)
OS Version:    Microsoft Windows NT 5.1.2600 Service Pack 2
CLR Version:    2.0.50727.832

We also have issues with clients who get timeouts from the server and then logoff. It seemed to be related to the idle timeout, but after further investigation it wasn't. They are on Laptops with WIFI. From the same internet connection using WIFI on my Mac I am able to stay connected.

V4.0 operator lockup problems

neburton — Wed, 31 Oct 2007 09:51:48 GMT

Was wondering if anyone was experiencing problems with v4 console when left running for an extended period of time?

We go home at night and lock our workstations. When we unlock them in the morning, we find the Sightmax Operator Console won't respond and we have to kill the process and restart. We're finding this is happening on Vista and XP workstations. This has happened ever since we installed V4.

Don't if there is a newer build to solves this problem??