Feature Key server showing red x 1

[wirednet]

I upgraded an IP office 3.2 (57) to 3.2 (69) and the voicemail to the 3.2(39). Now the Feature Key server shows a red x. The key service shows started. The IP address is in the manager for the voice mail server which has the serial dongel. Tried reboots too...repairs... any ideas on how to get the key server working?

 

[Bas1234]

Try to power down the Avaya completly. Also check the firewall on the server.

___________________________________________
It works! Now if only I could remember what I did...

Dain Bramaged
___________________________________________

 

[Bas1234]

Also try this driver;

http://www.safenet-inc.com/support_and_downloads/download_drivers/sentinel_drivers.aspx

___________________________________________
It works! Now if only I could remember what I did...

Dain Bramaged
___________________________________________

 

[Duffman88]

I personally never ran the feature key server. I would always simply plug the serial dongle into the back of the 406 to keep complications like this down to a minimum. What IPO do you have?

Chris
ACA- Implement IP Office

 

[Telecomboy]

I would check the driver was installed properly. I had that happen with 3.2 release when upgrading to a 4.2 a while back.

 

[jamie77]

serial dongles should be in the back of the kit, not in a PC. What model IPO do you have.

Are you sure it is serial (Silver) and not parrallel (Red)??

If the key server is a white box with a red cross, it can't see the dongle plugged in. run the drivers above, reseat it and so on until you get a red box.

Jamie Green

Football is not a matter of life and death-It is far more important!!!!

 

[DrDrayAvaya]

yep, parallel port drivers... check your device manager for the parallel port it's physically plugged into on that PC. is it even still there??!
have had same happen many moons ago, and I think we
relocated and reinstalled admin suite onto another PC with another parallel port in the end.. line of least resistance at end of the day. just adjust IP address in config, or use broadcast 255.255.255.255
No good reason for it to have stopped.
The red cross is just the dongle being accepted and seen by the service on that machine, nothing to do with whether they're valid or invalid in manager.
of course they will be invalid as long as you have a red cross thru a white box!!

 

[wirednet]

I was able to re-launch the sentinal driver. It fixed the errors. Thanks for the replys.