Voicemail Pro stopped working after Windows 10 update

[fakename05]

I have a system that was working fine until yesterday's Windows update. The error log on VM Pro says:

START_LOCK - Calling thread does not own OS_CRITICAL_SECTION

Services have been stopped and restarted. I've tried resetting security settings to default using Manager and then entering new non-standard passwords into the system. I've used that same password in VM Pro in Administration, Preferences, General. I've rebooted the phone system. I've uninstalled and reinstalled the VM Pro program. I checked netstat to see if there were any other programs trying to use UDP port 50791 but found nothing there conflicting.

I even tried bringing a different PC to connect to see if VM Pro running on it would connect to no avail. I've installed over 100 of these and this is a new one to me.

Any suggestions would be appreciated.

Thanks!

 

[IPGuru]

The usual Suspects.

Windows firewall
Anti Virus software
Account permissions for the account the VM pro uses to log in

changing settings on the IPO was almost certainly going to be futile



Do things on the cheap & it will cost you dear

 

[derfloh]

Better run VMPro on Application Server.

Need some help with IP Office?

https://www.fwilke.com/home

IP Office SIP trunk configuration:

https://www.fwilke.com/en/ip-office-sip-trunk-en/

CLI based cale blocking:

https://blog.fwilke.com/ip-office-block-calls-from-specific-cli/

SCN fallback over PSTN:

https://blog.fwilke.com/ip-office-scn-fallback/

 

[Westi]

run the firewall batch file for the firewall
You get it here from the Avaya support site. (didn't want to attach it because I don't trust batch files that I get from a non-validated site)

https://support.avaya.com/public/index?page=content&id=FAQ107855&group=UG_PUBLI

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

 

[Telecomboy]

VMPro is also dependant on a couple of other services. Makes sure those are running too. Also try to stop the service for Windows firewall to see if it is the firewall because even if you turn off the firewall it is still running in services and might be causing the issue.

 

[fakename05]

I agree that changing anything on the phone system would be futile but I looked at those anyway. ha!

The Windows firewall is off (and has been) and I've even temporarily turned off Windows Defender's anti-virus. There is no other anti-virus running.

I stopped and started VM Pro services a few times and even rebooted the phone system because I've seen it where that has restarted communication with VM Pro at other sites.

Just to get something working temporarily because this is a multi-site office with around 225 total users, I took over a laptop that has VM Pro installed, moved their accounts, greetings, names, and call flows to the laptop, connected it directly to the WAN port, and got them service even if it isn't on their computer. I'll go back after hours and work on their computer again to see if I have any better luck tonight. It was a mess trying to do this in the middle of the day but I can use this working laptop to determine if there is anything blocking it on the network to eliminate that as a potential problem.

Thanks for the link to the batch file. I had it on my computer but I was having trouble finding it.

 

[Westi]

default the security settings yet?

it looks sometimes like the vm is running because you see the IP Office IP address but that is all that works.

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

 

[fakename05]

I connected my serial cable to the port and typed in the command but it gave me an error message.

I also tried defaulting the settings using Manager. It required me to input new passwords at that time which I did. I used that password for the VM Pro client running on the laptop that is directly connected so I know the password is correct.

I think it was something in the Windows update because I have another customer that is having the same issue after their Windows update. One is running VM on a virtual server and the other is running VM on a standalone PC. Same problem. Same error in the error log in VM that I listed up above.

START_LOCK - Calling thread does not own OS_CRITICAL_SECTION

It's time to figure out what patches were installed and see if I can roll them back.

 

[derfloh]

I would create a SR with Avaya because they say Win10 is supported.

Need some help with IP Office?

https://www.fwilke.com/home

IP Office SIP trunk configuration:

https://www.fwilke.com/en/ip-office-sip-trunk-en/

CLI based cale blocking:

https://blog.fwilke.com/ip-office-block-calls-from-specific-cli/

SCN fallback over PSTN:

https://blog.fwilke.com/ip-office-scn-fallback/

 

[budbyrd]

Is the service running as a local account? Also I have seen the VM folder with limited permissions cause problems. I change the folder owner to 'Everyone' with full rights.

Dermis and feline can be divorced by manifold methods.*
*(Disclaimer for all advise given)--'Version Dependent'

 

[joe2938]

If possible see if you can roll back that last update and also disable any future windows update. And as stated earlier, better to run on an App Server.

 

[AlfonsoSF]

Perhaps it's a permission problem.

See the permissions for the VMpro folder.

 

[fakename05]

Not sure but I moved it to a different computer (even though the updates were completely done on it) and it works perfectly as before. I think the Windows update didn’t complete properly. We have decided to reinstall windows from scratch on the original PC because there were other components missing. Even Windows store was no longer on the PC.