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 Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

VMpro Config Blank but Callflows working

Status
Not open for further replies.

Ballzington

IS-IT--Management
Oct 1, 2013
3
AU
Have Voicemail Pro running on a 2008 server with one custom Auto Atendant menu then a bunch of group mailboxs and so on.
The system is working but the Config is blank showing no call flows as if its just a plain VM setup with user and group mailboxs no custom works show.
I have checked the cfg file int he VMpro folder and it is also blank. I have no other backups.
I am told if the was to restart the service I'm very likely to lose everything as it will load the blank cfg file in its directory.
Is there any way to get the active config with the call flows so I can migrate upgrade.
VMPro 6.0 or 7.0 I can't tell if the client is newer than the install.
I have all the recordings for the menus that play but want to avoid rebuilding them by guessing
 
this sounds like the VMdata.mdb file has been lost
this is efectivle a "Source code" file that the VM Pro client uses to generate the GUI for editing

the VM service Actually uses a file called root.vmp which is generated when you press save & make live so resetting the VM service sold be fine but t will not resolve your issue of being unable to edit the call flow.

unfortunately you will have no option other than to reprogram from scrath unless you can locate a backup.

one piece of good news is the root.vmp file is a plane txt file & human readable



Do things on the cheap & it will cost you dear
 
I have had this issue in the past when using the upgrade option with VM Pro. I was able to just save a backup of the config and reimport it and that worked fine.
 
Had this happen on a customers 8.1 VMPro, the mother ship accessed the system and said there was nothing they could do. but you could hear the greetings and still press digits to get to the options but the modules were invisible. I ended up rebuilding the modules

No matter how hard you try, you can't fix stupid...
 
Indeed, never happened to me but apparently used to be a common problem on older versions if remote access such as Windows remote desktop or terminal services ws used to configure the system.

Stuck in a never ending cycle of file copying.
 
Seen lots, but not for a while!

It happens if you open vm pro client in 2 windows sessions on a server. I always check task manager before opening the client to avoid this.

Not sure if just opening is enough or if you have to do something else to corrupt the mdb.

Root.vmp is fun to read through. It is in the order the modules were made.

Jamie Green

[bold]A[/bold]vaya [bold]R[/bold]egistered [bold]S[/bold]pecialist [bold]E[/bold]ngineer
 
Did you check under short codes in the Call me when you get a chance. Pro?
Or are you looking at the modules only?
 
There are 2 ways to build Auto Attendants onvm pro.
Modules or under short codes?

Did you check both locations?
 
Are you using a version of the VM Pro Client that is of the same release as the VM Pro software?

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top