CMS Supervisor V.11 dropping

[Esmerelda]

Hoping someone can help.... We have CMS supervisors dropping intermittently from several PCs at one customer site, with this message: "The connection to the server lnicms.dis.wa.gov was lost". Security log: Hanging application avsRep.exe, version 11.0.0.0, hang module hungapp, version 0.0.0.0, hang address 0x00000000. CMS = V11. This started approx. mid June. Previously ran clean for approx. two years. There have been no network changes.

Ethereal shows (among other things):
TCP SRC port 1101, DST port 23 seq 6, ack 35, len 6
Checksum 0x0e7f (incorrect, should be 0x88a7)
Header checksum - all 0x0000 (incorrect, should be 0xde90)

This is site specific, in that this is the only one of several remote sites which have CMS supervisors that are getting kicked out of the system.

One would think that this is a network problem, but, the customer has had no problems with other applications, and, we don't really know where, in the network, to look, and, what the empty header checksum and incorrect checksums are telling us.

Thanks in advance for any direction. Avaya would be happy to help as long as we bring buckets and buckets of money.

Esmerelda

 

[p08757]

Are you running CMS Supervisor in Windows XP? If so try to delete contents of c:\Program Files\Avaya\CMS Supervisor V11\Cache

We have a similar problem. I think it is a bug with windows XP.

let me know if this works.

 

[Esmerelda]

Thanks. We will certainly try that. I wouldn't be surprised to see the cache be the culprit. Just curious what SP you are running. If you are running SP 1, maybe we should all consider upgrading to SP 2.

I'll let you know.

Thanks,

Esmerelda

 

[Esmerelda]

Updating this issue....
The customer did clear their cache. Apparently, most of their computers are already SP 2. One person did get bounced today, but, during a rather large download, so, they are watching it.
Avaya's take on this theory, however..........
"More than likely the cache folder became corrupted when they lost connection to the CMS server, so the cache folder would not have prevented them from losing connection to begin with. So, they probably just cleared up the corruption after it lost connection." He then went on to quote charges in the event that the trouble is not determined to be in CMS Supervisor or the CMS server.
Does this make sense to anyone? My guess is that there is an incompatibility between CMS Supervisor and XP, as mentioned in a previous message, and, that the best way to resolve it is to just clear the cache every once in a while.

 

[phonesrus]

Just a suggestion, but some of the M/S security updates of recent vintage have been causing havoc with various programs.
I had a call accounting package stop recognizing the security dongle key after a recent update. With the help of the c/a tech support we were able to remove and reinstall the c/a program registry entries, which resolved the issue. We know it was one of 8 K/B updates, just not sure which was the culprit yet, havn't heard back.
I do not know it this applies to you, but i'll pass it on.