Voicemail Pro service will not start 1

[hurricaneguy]

We just installed Voicemail Pro and when we try to start the service it fails. It says "the service dis not respond to the start request in a timely fashion".

Has anyone seen this before?

 

[tlpeter]

Yes but i cannot recall why.
Did you use a user with admin rights for running the service ?


Homo sapiens non urinat in ventum

honey, i fried the IP Office !!!

Sarcasm, it's only one of the services I offer.

 

[hurricaneguy]

Yes the user has admin rights. I even unistalled VMPro and reinstalled using the default administrator.

 

[amriddle01]

What OS and what else is on that pc/server ?

ACSS (SME)
APSS (SME)

http://www.ipoffice.tel

"I'm just off to Hartlepool to buy some exploding trousers

 

[hurricaneguy]

Windows Server 2003 standard. This is on a VMware box. There is nothing else running on the server. The OS was just installed this morning.

 

[amriddle01]

what VM software level? As the service isn't even starting there isn't anything to be done on the VM side of things so it's an issue with the server somewhere, I have VM of diferent versions on VMware so it does work

ACSS (SME)
APSS (SME)

http://www.ipoffice.tel

"I'm just off to Hartlepool to buy some exploding trousers

 

[hurricaneguy]

VMPro 6.0.44. Most recent vesion downloaded directly from Avaya.

 

[amriddle01]

Only one thing left to suggest next, but that version does work fine in my experiance, try a repair/re-install as something must have gone wrong during installation the first time, if that gives no results it's the server itself

ACSS (SME)
APSS (SME)

http://www.ipoffice.tel

"I'm just off to Hartlepool to buy some exploding trousers

 

[kflounders]

DO you have One-X on the same server? If you do stop One-x service and then restart the VM service.

Kevin Flounders

http://www.comstar-usa.com

 

[hurricaneguy]

One-x is not installed.

I have tried to uninstall and reinstall several times. I even went to an older version and that did not work either.

I did just notice that for some reason .net is not installed on the computer. This is required for VMPro correct? I don't know why the VMPro setup did not spot it. I am installing .net on the server and will see if that helps.

 

[hurricaneguy]

installing .net did not fix the issue.

 

[amriddle01]

Install it on another PC, also making sure the firewall and AV is off. If it works you have narrowed it down a bit, it sounds like you don't trust the software

ACSS (SME)
APSS (SME)

http://www.ipoffice.tel

"I'm just off to Hartlepool to buy some exploding trousers

 

[hurricaneguy]

I trust the Avaya software. It's the Microsoft stuff that has me worried. Of course Microsoft is not being all that helpful.

 

[hurricaneguy]

It works on another machine. So something is wrong with this server. I just dont have a clue what that is.

 

[amriddle01]

Troubleshooting servers isn't my strong suit never mind VMware based servers (even though they should be the same). I have it working on VMware as have many others, so it just needs pinpointing, I now hand over to the other tippers for that

ACSS (SME)
APSS (SME)

http://www.ipoffice.tel

"I'm just off to Hartlepool to buy some exploding trousers

 

[hairlessupportmonkey]

so what do the event logs show about the service starting then stopping. Normally the reason is, something is using the same port(s) as VM Pro.

have a look for any suspicious apps installed that dont need to be on the box and remove them.

make sure the box is also fully up-to-date and has .NET installed. (3.5 sp1)

 

[hurricaneguy]

The Event log has these errors

Timeout (30000 milliseconds) waiting for the Voicemail Pro Service service to connect.

And

The Voicemail Pro Service service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.

The error comes up immediately. It does not wait 30 seconds.

The server has .net 4 which is the current downloadable from Microsoft.

 

[hairlessupportmonkey]

ok - so what other services are on this machine?

 

[hurricaneguy]

Well it is working now.

I uninstalled .net 4 and then ran a windows update and under optional components I had the option for .net 3.5 as well as 4. I installed 3.5 and everything started working.

So it seems like it did not like .net 4.

 

[amriddle01]

Damn that Bill Gates

ACSS (SME)
APSS (SME)

http://www.ipoffice.tel

"I'm just off to Hartlepool to buy some exploding trousers