Password for VoiceMail Pro Client 4

[BENANDSERA]

Can anyone help me out with how to reset the password for IP Office VoiceMail Pro Client Version 5.0(25). Somehow I have logged myself out and cannot log back in, in order for the conference bridge portion of this to work you need to be actively logged in. I do have the password for IP Office but that may not help. Any suggestions?

 

[Westi]

If you run the voicemail pro client from the server/PC the voicemail is installed in them you don't need a password.
If you have any other constellation then you need to give us more information.

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

 

[BENANDSERA]

Thanks for the quick response Joe,

I think you may have answered part of my question, this isn't the original PC that VoiceMail Pro was installed on. The IP office was installed though a backup program onto a new PC because the original PC failed. Do you know of anyway around this, thanks.

 

[IPGuru]

The IP office was installed though a backup program onto a new PC because the original PC failed.

have the VM Pro properly installed on the new machine

Oh btw you should not need to have the VM Pro client to use conferencing or any other VM Facilitys


Do things on the cheap & it will cost you dear

 

[BENANDSERA]

I appreciate everyone's input on this so far.

I went ahead and properly installed IP Office/VoiceMail Pro on the new machine. I'm able to access the system and reload the database but now I am receiving a "Access Violation at address 004b94db in module VoiceMail Pro.exe."

Evidently this has something to do with user permissions. Has anyone had any experience with this?

 

[IPGuru]

it is to do with the "Data Execution prevention " setting in windows you probably have it set for all programs
change it to windows system programs only


Do things on the cheap & it will cost you dear

 

[budbyrd]

VM Pro does a lot of permission stuff to windows. Usually I go through and add 'Everyone' to the permission list for the entire Avaya folder. This week we found one that windows decided all of the VM Pro files were read only.

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

 

[PabsUK]

or add voicemail pro.exe to the programs list by right clicking on Computer, goto properties, then advanced system settings, click settings next to performance in the advanced tab, then goto data execution prevention tab, click add and browse to the voicemail pro.exe then ok out and try again.

 

[IPGuru]

Better yet Ditch windows completely & install as application server


Do things on the cheap & it will cost you dear

 

[BENANDSERA]

Okay, I tried what everyone suggested, except for the applications server idea but I'm still thinking about that. Unfortunately it didn't work but it may have helped get me closer to a working machine. Did another complete install of the software and I was getting that login problem again. Decided to put the ip address of my new machine in the destination or source bar, can't remember the name of it but its the third space down right below password and it took it. The name and password grayed out, so I'm in. Everything looks good but its still not working, when I call the VDN I still get a busy signal. We use to get a busy signal when the computer when down our lost comm with the server. Any ideas, appreciate everyone's help.

 

[IPGuru]

assuming the VM password is correct (usualy just blank but it needs to match the IPO security settings) then the usual suspects are Firewall & Antivirus software, both of which could be blocking communications



Do things on the cheap & it will cost you dear

 

[PabsUK]

I'm assuming you've checked the obvious? VM pc can ping ip office, VM Pro ip address in manager isn't still set to old VM Ip address, services all running on new VM pc etc

 

[BENANDSERA]

Found the firewall turned on, so I turned it off and everything is working. I really appreciate everyone's input on this. I swear I would buy you guys all beers if I could. Happy New Year!

 

[joe2938]

show them some pink then

 

[BENANDSERA]

Almost forgot joe, thanks

 

[BENANDSERA]

Looks like I spoke too soon, figures. lol For some reason its not staying connected, after about an hour or so it stops working. The program shows that its connected, tried stopping and restarting the program but that doesn't work. The only way I can get it to start working again is to reboot the computer. Any ideas what that could be?

 

[Westi]

make sure you install it as Administrator then go to the voicemailpro.exe and make sure you run it as administrator for all users and I also run the service as local service (from old days when it was bad to log on as a user)

You can run the firewall batch file from the knowledgebase but if you have it turned off that should not be the issue.

What OS are you running this on because it is R5.0 it may not run easily on Server 2008 or Win10 or even Win7 without compatibility for an older OS



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

 

[derfloh]

It is not running together with DNS Service?

 

[Westi]

or the Domain controller.
Had a colleague move a server a month or so ago and after powering it back on it would not work any more due to some Windows updates that were done when shutting it down.

Thanks derfloh for picking that up.




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

 

[BENANDSERA]

So it looks like it was the computer itself that was the issue, it was operating kind of flaky to begin with but after the long weekend it finally died.

So I installed everything on a windows 7 machine this morning, the computer is connected directly to the IP Office server but it looks as though the operating system is preventing Voicemail Pro from connecting. The user name and password or masked out and I have the correct IP address. I can ping it to but when I go to connect I get a failed to connect prompt.

I've disabled the firewall which worked on the other machine.
I've deleted any kind of virus/malware program.
Changed the compatibility feature to Windows XP on the icon properties. The other previous machines were XP.
Changed the Avaya file to add everyone permission.
Turned off the Data Execution Prevention for VoiceMail Pro.

Is there something else I could be missing because it windows 7?

Thanks for everyone's input so far.