KeyServe failure 1

[NickRyan]

I've noticed a problem with the keyserve "feature" server on our dedicated voicemail server - and no matter what we've tried so far, the service starts up and just shows a white box with a red cross through it in the system tray. No useful information whatsoever is shown on the "about" screen for the keyserve application other than "Feature Key Server 1.0".

The avaya log in the root of the system volume fills up instantenously to 4096kb. From what of this file I can read, I can find lines such as the following:

25/07 14:02:54.031 KeyServ (01,3) 1884,1940: Protection Check Failed. status: 0xc fullstatus 0x20c
25/07 14:02:54.031 KeyServ (01,5) 1884,1940: lR: 0 status: 0
25/07 14:02:59.171 KeyServ (01,3) 1884,1940: Protection Check Failed. status: 0xc fullstatus 0x20c
25/07 14:02:59.171 KeyServ (01,5) 1884,1940: lR: 0 status: 0
25/07 14:02:59.906 KeyServ (01,5) 1884,1936: lR: 0 status: 1
25/07 14:03:14.924 KeyServ (01,5) 1884,1936: lR: 0 status: 1
25/07 14:03:19.072 DbgOut (01,5) 532, 344: DllMain(hinstDLL=0x10000000, fdwReason=DLL_THREAD_DETACH)
25/07 14:03:19.072 DbgOut (01,5) 532, 776: DllMain(hinstDLL=0x10000000, fdwReason=DLL_THREAD_DETACH)
25/07 14:03:29.967 KeyServ (01,5) 1884,1936: lR: 0 status: 1
25/07 14:03:45.010 KeyServ (01,5) 1884,1936: lR: 0 status: 1
25/07 14:03:49.017 DbgOut (01,5) 532,1856: DllMain(hinstDLL=0x10000000, fdwReason=DLL_THREAD_ATTACH)
25/07 14:03:50.582 KeyServ (01,3) 1884,1940: Protection Check Failed. status: 0xc fullstatus 0x20c
25/07 14:03:50.582 KeyServ (01,5) 1884,1940: lR: 0 status: 0
25/07 14:03:55.732 KeyServ (01,3) 1884,1940: Protection Check Failed. status: 0xc fullstatus 0x20c
25/07 14:03:55.732 KeyServ (01,5) 1884,1940: lR: 0 status: 0
25/07 14:04:00.037 KeyServ (01,5) 1884,1936: lR: 0 status: 1
25/07 14:04:00.867 KeyServ (01,3) 1884,1940: Protection Check Failed. status: 0xc fullstatus 0x20c
25/07 14:04:00.867 KeyServ (01,5) 1884,1940: lR: 0 status: 0
25/07 14:04:15.064 KeyServ (01,5) 1884,1936: lR: 0 status: 1
25/07 14:04:30.091 KeyServ (01,5) 1884,1936: lR: 0 status: 1
25/07 14:04:45.118 KeyServ (01,5) 1884,1936: lR: 0 status: 1
25/07 14:04:52.288 KeyServ (01,3) 1884,1940: Protection Check Failed. status: 0xc fullstatus 0x20c
25/07 14:04:52.288 KeyServ (01,5) 1884,1940: lR: 0 status: 0
25/07 14:04:57.438 KeyServ (01,3) 1884,1940: Protection Check Failed. status: 0xc fullstatus 0x20c
25/07 14:04:57.438 KeyServ (01,5) 1884,1940: lR: 0 status: 0
25/07 14:05:00.146 KeyServ (01,5) 1884,1936: lR: 0 status: 1
25/07 14:05:02.587 KeyServ (01,3) 1884,1940: Protection Check Failed. status: 0xc fullstatus 0x20c
25/07 14:05:02.587 KeyServ (01,5) 1884,1940: lR: 0 status: 0
25/07 14:05:15.173 KeyServ (01,5) 1884,1936: lR: 0 status: 1
25/07 14:05:19.180 DbgOut (01,5) 532, 732: DllMain(hinstDLL=0x10000000, fdwReason=DLL_THREAD_DETACH)
25/07 14:05:30.200 KeyServ (01,5) 1884,1936: lR: 0 status: 1
25/07 14:05:45.227 KeyServ (01,5) 1884,1936: lR: 0 status: 1
25/07 14:05:54.009 KeyServ (01,3) 1884,1940: Protection Check Failed. status: 0xc fullstatus 0x20c
25/07 14:05:54.009 KeyServ (01,5) 1884,1940: lR: 0 status: 0
25/07 14:05:59.159 KeyServ (01,3) 1884,1940: Protection Check Failed. status: 0xc fullstatus 0x20c

Naturally this means nothing to me and the very limited Keyserve documentation.

Config of system: WinXP Pro (SP2), all fixes applied, PCI LPT card that specifically supports rainbow dongles (*), RAID mirror drives.

*) - PP500 3.3 Volt 3.3V/5V Universal PCI-X 32/64 bit/PCI Printer/Parallel Adapter Port

Anybody have any advice on where to start looking? The log isn't very useful and the fact that it instantly maxes out to 4096kb on boot up is a concern.

 

[NickRyan]

Hehehe - just moved the log file onto another system and viewed it using a decent text file viewer (textpad) and the file is a circular log file... so no concerns about the instant 4096kb file size after all!

 

[PlatinumGuy]

If this is a parralel or usb dongle?

If so go to

http://www.safenet-inc.com

and download the latest drivers, that should do it.

If it is a serial dongle it shouldnt be on the back of a pc, it wont work there. It needs to be on the back of the control unit.

ACA - IP Office Implement
ACS - IP Office Implement
ACE - IP Office Implement
ACI - IP Office Implement

 

[NickRyan]

Thanks PlatinumGuy - that worked just fine (it was a parallel dongle).