4.2 VM pro keeps locking up?

[akb1111]

IP office 406v2 4.2
VM pro 4.2
XP pro on the VM pro server

when working in voicemail pro client, if i try to make any changes, the voicemail pro software and service locks up. they only way to get things working is to reboot the computer?

has anyone had or seen this problem? if so, how did you fix it?

thanks!

 

[Westi]

are you working directly on the PC or remote in, in any way shape or form?

Joe W.

FHandw., ACS

If you can't be good, be good at it!

 

[Birdy213]

I have had this problem before, you may not have installed the voicemail pro client properly or have antivirus, firewalls running on the pc.Check the services for andy firewalls or antivirus' and if not try uninstalling and reinstalling

 

[akb1111]

hey guys,

thanks for the replys.

we are connected directly to the ip office on site. this is a new install that we are doing at the moment.

as far as i know there is no firewall on the pc. i will try to unistall and then reinstall.

thanks again!

 

[akb1111]

well, we reloaded the software, and we are getting the same problem. the problem is...

in system status there is an alarm that states....

cant connect to the feature key server.

on the vm pro server, this is where we have the key server, we can see the dongle icon in the bottom right corner by the time. if we remove the dongle, we get the white box with the red X on it. i think the dongle is good, but for some reason, the key server wont sync/validate with the ip office???????

any suggestions?

 

[amriddle01]

The Key server often doesn't upgrade properly going to 4.2, try re installing it and check how it runs in services.msc i.e auto and with the right account, it can be a pain in the ar5e to get it working properly, I think they really messed it up on 4.2 as you're not the only one.

ACS - IP Office Implement

 

[Telecomboy]

I have had this issue, the sentinel got messed-up. I don't have the steps in front of me how I fixed it, but basically you need to re-install the sentinel driver. I'll see if I can find the steps.

 

[Telecomboy]

Ok, here's what I did: Stop the Keyserver under services. Then go to the Keyserver folder under Program files, Avaya, IP Office, Keyserver, Drivers, and click on Setupx86. Then, click on Functions, Choose install Driver, It will then ask you to specify the path, erase the \I386 and click OK. Then go and restart your keyserver and it should go red. If that doesn't work, you may have to de-install the keyserver, re-install it, and then follow the steps above. Hopefully that takes care of it for you.

 

[akb1111]

i cant find the driver folder under keyserver?

 

[Telecomboy]

Go to the disk or wherever you are loading the Admin features from and you should see a folder called "Sentinel System Driver". Open it and install the sentinel driver from there.

 

[akb1111]

here is what comes up in monitor if this helps????

i have unistalled and reinstalled the software with no luck?

i downloaded the driver 7.4.2 from safe net, but that did not help?



517848mS PRN: Monitor Started IP=192.168.42.3 IP 406 DS 4.2(4) Star LLC
(IP Office: Supports Unicode, System Locale is enu)
517849mS PRN: LAW=U PRI=1, BRI=0, ALOG=0, ADSL=0 VCOMP=20, MDM=0, WAN=0, MODU=0 LANM=0 CkSRC=0 VMAIL=0(VER=0 TYP=1) CALLS=0(TOT=0)
518837mS PRN: RTC not initialised, Initialise ...
518837mS PRN: RTC not initialised, Initialise ...
518837mS PRN: RTC not initialised, Initialise ...
521477mS PRN: RTC not initialised, Initialise ...
523846mS PRN: RTC not initialised, Initialise ...
523846mS PRN: RTC not initialised, Initialise ...
523847mS PRN: RTC not initialised, Initialise ...
528853mS PRN: RTC not initialised, Initialise ...
528853mS PRN: RTC not initialised, Initialise ...
528854mS PRN: RTC not initialised, Initialise ...
529837mS PRN: RTC not initialised, Initialise ...
529848mS LIC: Rainbow token file not received/invalid from 192.168.42.3.
531477mS PRN: RTC not initialised, Initialise ...
533864mS PRN: RTC not initialised, Initialise ...
533864mS PRN: RTC not initialised, Initialise ...
533865mS PRN: RTC not initialised, Initialise ...
538337mS PRN: RTC not initialised, Initialise ...
538872mS PRN: RTC not initialised, Initialise ...
538872mS PRN: RTC not initialised, Initialise ...
538872mS PRN: RTC not initialised, Initialise ...
541477mS PRN: RTC not initialised, Initialise ...
543873mS PRN: RTC not initialised, Initialise ...
543874mS PRN: RTC not initialised, Initialise ...
543874mS PRN: RTC not initialised, Initialise ...
544857mS PRN: RTC not initialised, Initialise ...
544859mS PRN: RTC not initialised, Initialise ...
544859mS RES: Mon 25/8/1997 00:00:00 FreeMem=45102384(1) CMMsg=2 (2) Buff=100 522 500 1068 5 Links=1387
544860mS RES2: RTEngine=0, CMRTEngine=0, Timer=44, Poll=0, Ready=0, CMReady=0, CMQueue=0, VPNNQueue=0
544870mS LIC: Rainbow token file not received/invalid from 192.168.42.3.
548877mS PRN: RTC not initialised, Initialise ...
548877mS PRN: RTC not initialised, Initialise ...
548877mS PRN: RTC not initialised, Initialise ...
551477mS PRN: RTC not initialised, Initialise ...
553887mS PRN: RTC not initialised, Initialise ...
553887mS PRN: RTC not initialised, Initialise ...
553887mS PRN: RTC not initialised, Initialise ...
578926mS PRN: RTC not initialised, Initialise ...
578926mS PRN: RTC not initialised, Initialise ...
578926mS PRN: RTC not initialised, Initialise ...

********** Warning: Logging to Screen Stopped **********

 

[Westi]

you have to uninstall the drivers for the USB key (Rainbow drivers) then uninstall and reload the admin software and then put the usb key back it will then have the drivers loaded and should work.
Sometimes it is a bit painful to get them to work, as a workaround you could always put it on a different PC on the network. It doesn't have to be the VM server it can be any PC on the network.

Cheers

Joe W.

FHandw., ACS

If you can't be good, be good at it!

 

[akb1111]

we have the parallel dongle. would this be the same setup?

 

[tlpeter]

Yes the same setup

Do the uninstall, remove all rainbow and sentinell in the registry

plug in the dongle and install the drivers


ACA - Implement IP Office
ACS - Implement IP Office
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!

 

[akb1111]

FOUND THE PROBLEM!!!!!!!!!!

the control unit (406v2) had a problem. there was a "chip" the "F.I.T. BATTERY PACK"????? it has a yellow cover on it.?? that was unplugged. we plugged it back in and the error message went away from the monitor program. ALL THE LISENCES VALIDATED!!!! there was nothing wrong with the 4.2 software or computer/key server.

thanks again for all your help!