VM Pro "There was a problem opening the call flow database"

[nickofherts]

Can anyone help me with this one ?
VM Pro has been working fine for 5 weeks but I needed to change a couple of items. When starting up the client I got "There was a problem opening the call flow database" although the auto-attendant was still working fine. So I removed the VMPro application, rebooted, re-installed it, rebooted and still get the same error but the AA has stopped ! The error stops the client loading any further and the VMPro is running on the same machine as the client.

I have removed the PABXSoft call logger, disabled as much Norton as I can find and there are no other applications loaded.

PC is running XP SP2 and VMPro is 4.1.27

 

[kwing112000]

Check the VM DB service. make sure its running. i have seen that cause it before.

 

[nickofherts]

Yes, both DB Service and Server are running.

 

[mattKnight]

Have you ever accessed this machine using Microsoft Remote Desktop?

Whwn you start the VM pro client application is the splach screen garbled?

Take Care

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

 

[TomMills]

is that was causes the splash screen to look like a subtitled bernard manning gig

 

[mattKnight]

Tom,
Apparently so, under some circumstances...
see tech tip 183

We always (nearly) use VNC and have had no problems..

Take Care

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

 

[TomMills]

i used to always use rdp to connect to our vm server, because i was too lazy to put a screen on it, i always assumed it was a dodgy install or something, i never had any issues with it so i left it at that.

cheers for pointing me in the right direction, ill try and avoid it in future

 

[puregold]

There is something good coming in 4.2 that will make managing VM pro remotely much easier.

ACE - Avaya Certified Expert
ACI - Avaya Certified Instructor

 

[jamie77]

I've seen that message twice before. Once on a new install. The PC didn't like the VM Pro. Got a new machine and all was good.

2nd time was 2 months ago. Not so good. Got the message once, restarted the server and after that the VM Client DB was goosed (VMData.mdb) so no changes could be made to VM. Could not be recovered and had to rewrite our VM.

Hope you have more luck

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!!!!

 

[as1981]

Every time we've used remote desktop we've had problems, try to avoid it.

Thanks

Andrew

 

[jamie77]

Will it work PG????

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!!!!

 

[aarenot]

Did you ever back up the database, and the WAV files during the 5 weeks that it was working properly?

 

[puregold]

I would hope so!

ACE - Avaya Certified Expert
ACI - Avaya Certified Instructor

 

[aarenot]

If so, you should be able to re-install the VMPRO. You may need to clean up the mnachine first to fix whatever issue it was having that caused the issue. I do not have any information leading me to believe that the VMPRO software is the issue at this point. Probably the reason that the call flow stopped working was that uninstalling the VMPRO application requires reloading the backed up DB before it is expected to work again.

 

[IPONEWBIE1]

I have had this problem, I had a customer that had their IT guy partition the drive to install just avaya apps so I could not have access to their medical billing data (which I was glad he did so I could never be implicated in anything). Everything was running on the partitioned drive. I would term service in and get the same error. It must have something to do with access to services or the registry. When I was added as a admin over the whole box with explicit deny rights on the medical stuff it worked fine. My short answer would be try it with full admin rights and see if that works.