I've been having this issue with several customers where the VMPro service on a Windows PC just stops, so I have to login and start it to get VM back up. They're all running windows 10 but some are running different versions of vmpro. 10.1 GA and R11 SP2. I thought the issue was the R10.1 GA so I ran a few upgrades to R11 SP2 and the issue still persists. Has anyone else run into this?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
VMPro Service randomly stops 3
- Thread starter Jonjr88
- Start date
Do you get any log messages or messages in windows event log?
IP Office remote service Fixed price SIP trunk configuration: CLI based cale blocking: SCN fallback over PSTN:
IP Office remote service Fixed price SIP trunk configuration: CLI based cale blocking: SCN fallback over PSTN:
- Thread starter
- #3
I have the same issue lately a lot.
sometimes it resolves it when you run the voicemail pro service as local service instead of logging on to a user name
Joe W.
FHandw, ACSS (SME)
"This is the end of the world, make sure to buy your T-shirt before it is too late"
Original expression of my daughter
sometimes it resolves it when you run the voicemail pro service as local service instead of logging on to a user name
Joe W.
FHandw, ACSS (SME)
"This is the end of the world, make sure to buy your T-shirt before it is too late"
Original expression of my daughter
To be honest I don't know. Just check event log. Go into application logs and then Voicemail Pro. Look for warnings and error messages.
You can also set the log level of VMPro higher.
IP Office remote service Fixed price SIP trunk configuration: CLI based cale blocking: SCN fallback over PSTN:
You can also set the log level of VMPro higher.
IP Office remote service Fixed price SIP trunk configuration: CLI based cale blocking: SCN fallback over PSTN:
- Thread starter
- #6
Make sure the power settings under control panel is not turning the hard drive off after so many minutes or putting the computer to sleep. This will cause this behavior with Voicemail Pro servers on Windows PCs.
The truth is just an excuse for lack of imagination.
The truth is just an excuse for lack of imagination.
Telecomboy
Programmer
My guess would be power settings as well. Check those and make sure they are not set to allow the computer to go to sleep.
- Thread starter
- #9
Nortel4Ever
Vendor
I've seen this a few times too, on both Linux and Windows VM Pro servers. With the Linux servers it seemed to be network congestion, if the communication between the IPO and Linux box was slow or dropped it would not reestablish without rebooting the Linux box. To prove this we connected the Linux box directly to the IPO's WAN port, taking the network out of the picture and that cleaned up all of the issues, the voicemail ran flawlessly. Obviously this was not a permanent solution but we used it to prove the customer's network was at fault. We provided a 4 port switch and connected it to the IPO, Linux box, and customer's network. The IPO and Linux box could now communicate without network congestion.
On Windows servers I have gone to Services - Voicemail Pro Service - right clicked, selected one of the tabs (can't remember which one) and set the re-start options. The first two to restart the service, the third one to restart the PC. Since doing that we have never had a problem.
On Windows servers I have gone to Services - Voicemail Pro Service - right clicked, selected one of the tabs (can't remember which one) and set the re-start options. The first two to restart the service, the third one to restart the PC. Since doing that we have never had a problem.
- Thread starter
- #12
So it just happened again and looking back at the logs from 430am this morning shows a windows update and a reboot. Looked at the voicemail pro service and it was just stopped, had to start it manually. I spoke to my distributor support team and they said to repair the voicemail pro install after every windows update which is crazy I think. Any other ideas?
Nortel4Ever
Vendor
Have you tried my suggestion of setting the restart options in the VM Pro Service?
-
1
- #14
Windows updates is one big reason of many it is suggested to go with an application server so you don't have to deal with that type of issue. A Windows PC is simply not the ideal solution for a Voicemail Pro server.
The truth is just an excuse for lack of imagination.
The truth is just an excuse for lack of imagination.
- Thread starter
- #15
Nortel4ever, i set the restart options on all windows vmpro machines.
critchey i would love for everyone to move to an app server but many customers dont have the resources to do so or they're not about to spend extra cash. And i would never use the UCM....
critchey i would love for everyone to move to an app server but many customers dont have the resources to do so or they're not about to spend extra cash. And i would never use the UCM....
-
1
- Thread starter
- #18
-
1
- #19
I have a step by step written down that you can try..
1. Search for Task Scheduler
2. Create Basic Task
3. Name it Voicemail Pro Service Restart (or whatever)
4. Start the task to start 'When a specific event is logged'
5. Set Trigger
Log: Application
Source: VoicemailProServer (Note: You will need to type this in)
Event ID: 0
6. Select 'start a program' for the action you want to perform
7. Set these Variables
Program/Script: NET
Add Arguments: START "VoicemailProServer"
Now find the basic task you created by clicking on Task Scheduler (Local) on the top of the list.
Then hit 'Refresh at the bottom right. Your task should be there. Double Click on the task and select 'Properties' on the right handside.
Go to the Conditions tab and untick everything, then go to settings and make sure 'Allow task to be run on demand' is the only one ticked.
1. Search for Task Scheduler
2. Create Basic Task
3. Name it Voicemail Pro Service Restart (or whatever)
4. Start the task to start 'When a specific event is logged'
5. Set Trigger
Log: Application
Source: VoicemailProServer (Note: You will need to type this in)
Event ID: 0
6. Select 'start a program' for the action you want to perform
7. Set these Variables
Program/Script: NET
Add Arguments: START "VoicemailProServer"
Now find the basic task you created by clicking on Task Scheduler (Local) on the top of the list.
Then hit 'Refresh at the bottom right. Your task should be there. Double Click on the task and select 'Properties' on the right handside.
Go to the Conditions tab and untick everything, then go to settings and make sure 'Allow task to be run on demand' is the only one ticked.
Because several other services don't stop their work after a windows update, it just be an Avaya issue and not windows.
Nevertheless App Server is the better way. If the customer doesn't have the resources, it would perhaps be an option to run Hyper V on the windows server and run App Server virtualized.
IP Office remote service Fixed price SIP trunk configuration: CLI based cale blocking: SCN fallback over PSTN:
Nevertheless App Server is the better way. If the customer doesn't have the resources, it would perhaps be an option to run Hyper V on the windows server and run App Server virtualized.
IP Office remote service Fixed price SIP trunk configuration: CLI based cale blocking: SCN fallback over PSTN:
- Status