Can't see VM Config

[jamie77]

I have upgraded our in house system to 4.1.

SIP now doesn't work. One way transission on both my providers!! Will look at this later.

More importantly, our vm if working properly but the VM Client will not show the database!! All my custom call flows do what they should but the CLient shows a default blank databse. my .mdb backup has disapeared also so can't even put it back in not sure if it didn't save properly when I exported the config.

Any ideas how to get this back. It must be there as it works but can't see it!!!

Jamie Green

ACA:Implement - IP Office
ACS:Implement - IP Office

http://www.alliedcom.co.uk

Fooball is not a matter of life and death-It is far more important!!!!

 

[ProviderReborn]

What about your Backup folder in your VMPro Directories?

ACA - IP Office Implement
ACA - IP Telephony
ACS - IP Office Implement
CCNA - Working towards.

 

[SuperJenks]

You should have exported your old call flows for backup purposes before ugrading.

 

[jamie77]

I did export but can't have done it properly as the file is nowhere to be seen!! DOH!!! I love new year!!!

The backup directory files are all blank.

Which files VMDATA etc actually contain the config??

Jamie Green

ACA:Implement - IP Office
ACS:Implement - IP Office

http://www.alliedcom.co.uk

Fooball is not a matter of life and death-It is far more important!!!!

 

[gknight1]

if you say it is working fine, try doing an export and see what it exports? you might get lucky and it will export the one you had before.

 

[colpot]

Does the client definately connect to the online db?
I had a similar issue but, as gknight1 says, I ran an export and then a reimport and it worked, but I had to be logged onto the db and not offline.

Colpot
(Remember - If it aint broke - fix it till it is.)

 

[jamie77]

tried an export and no dice.

def online colpot. This is our own VM!!!!


I don't understand how the db can be there and work but not showing in the client!!

Jamie Green

ACA:Implement - IP Office
ACS:Implement - IP Office

http://www.alliedcom.co.uk

Fooball is not a matter of life and death-It is far more important!!!!

 

[gknight1]

i would say reboot the machine. you didnt change the name of the pc or anything did you? When you exported what did it export?

 

[ProviderReborn]

Jamie has it started both of your VM services correctly.

ACA - IP Office Implement
ACA - IP Telephony
ACS - IP Office Implement
CCNA - Working towards.

 

[jamie77]

I exported c:\alliedvm.mdb but the file wasn't there after upgrading 4.0(18)>4.1(27) and rebooting the server.

Both services are running. Even installed the vm onto my laptop and copied various files and/or the whole voicemail directory from the server to get it running and re-export the config but still no joy.

I have just found out that our backup tapes on the server don't include the VM folder. That was my only option!!!

The DB has to be there somewhere in on or more of the files, the bloody thing actually works!!! On the Alchemy it used to be the Root.VMP but I know that isn't the case anymore. I wich it was.

Jamie Green

ACA:Implement - IP Office
ACS:Implement - IP Office

http://www.alliedcom.co.uk

Fooball is not a matter of life and death-It is far more important!!!!

 

[IPGuru]

If you cannot find a copy of the MDB file backup the root.vmp file now!
this is the file that the VM service actualy uses (it is created from he MDB when you click save & make live)

root.vmp is a plain text file & can be read in any text editor
this will enable you to reprogramm your MDB file.

 

[jamie77]

Our distributor has this already outstanding with Avaya as it is a known issue that Avaya are denying!!!!

I have tried copying the root.vmp to another VM server but it still doesn't show. Have tried copying this into a 4.0 and 4.1 VM.

Jamie Green

ACA:Implement - IP Office
ACS:Implement - IP Office

http://www.alliedcom.co.uk

Fooball is not a matter of life and death-It is far more important!!!!

 

[IPGuru]

root.vmp will not show in VMPro client
but it can be read in plain text (Notepad or wordpad) & then printed out
this will make it much easier to recreate the customers call flow

 

[SuperJenks]

Can the root.vmp file be converted in any way to the .mdb? Im wondering if .vmp can be viewed in microsoft access and then saved as a mdb so it can then be imported.

 

[jamie77]

The root.vmp says it is created by the VM Pro client for use by the VM Pro server. If this file is the callflow info then surely the problem I have is the VM Pro Client not reading this file properly!!!

All the info is in there are the timestamp it has inside the file is consistent with the last config change I made.

SuperJenks: I have tried that and it doesn't work. the root.vmp file is a text file.

When the VM Pro client is started does it read the root.vmp on the server to get the callflows. If that is correct then the problem is with the Client as the VM Service is reading this file correctly.

How many people have installed/upgraded to 4.1 out there????? Any issues to speak of???

Jamie Green

ACA:Implement - IP Office
ACS:Implement - IP Office

http://www.alliedcom.co.uk

Fooball is not a matter of life and death-It is far more important!!!!

 

[ronromano]

I upgraded our in house to $.1 on win2kserver. No issues. Have a 4.1 upgrade next Wed. We'll see.

 

[ronromano]

I sould tell you that I have this same issue with a customer on 3.2. I don't think it is a 4.1 issue. I saw a post here that said VNC corrupted his VMPro and it just so happens this is the only customer I have that ever used VNC so I don't know if there is a correlation. I have not been able to resolve that on either.

 

[jamie77]

I have a 3.2 site that I always log into with VNC. VM Pro Server has no screen. been like that for 18 months with no problems. I don't buy into this RDP/VNC corrupting thing, but I also never rule anything out.

I do have VNC on our server but it used once a blue moon (and haven't seen one of those in the sky for a while!!!). Use RDP quite a lot, but all was fine until upgrading.

I just can't get my head round the fact that the VM Pro Service can read the db but not the client.

If it all went up the spout then it would make more sense. I would be worse for me right now having said that.

Jamie Green

ACA:Implement - IP Office
ACS:Implement - IP Office

http://www.alliedcom.co.uk

Fooball is not a matter of life and death-It is far more important!!!!

 

[jamie77]

Upgrade was done locally on the machine btw, no remote connection involved.

Jamie Green

ACA:Implement - IP Office
ACS:Implement - IP Office

http://www.alliedcom.co.uk

Fooball is not a matter of life and death-It is far more important!!!!

 

[mattKnight]

>I don't buy into this RDP/VNC corrupting thing

I am aware of the issue with RDP... Are you saying that VNC does the same?

I have experienced this issue - including corrupted splash screen with RDP - but never with VNC!


As I understand it, when you hit save and make live the VMpro client saves the MDB, then converts it into the VMP file. So it is possible to remove the MDB file without upseting the running system.



Take Care

Matt
If at first you don't succeed, skydiving is not for you.