Voicemail Pro Call Flow Import Fails

[mettech2]

I was upgrading our IPOffice 406 system to 3.1(65) from 3.0 (13) and the voicemail upgrade failed. I exported the call flows uninstalled 3.0 and installed 3.1 version. When I import the call flows to 3.1...it imports but I can not save. It gives me and error about saving to a text file and when I look at the modules some of the connectors are missing. So right now my IPO is at 3.1 but VMPro is at 3.0. Anyone had this kind of problem?

Thanks

 

[jml2665]

never seen it that issue before, but just guessing here, did you run the registry backup and restore?

 

[mettech2]

I did run the registry backup and restore. I get two erros when importing the call flow "stream read error" and if I try to save and make live I get "error saving call flow to a text file

 

[aarenot]

uninstall vmpro
reinstall it
import
then close the application.
a window will pop up asking if you want to save changes
click yes



You do not always get what you pay for, but you never get what you do not pay for.

 

[mettech2]

aarenot,
I did as you suggested and received no error, but the call flows did not save. When I open vmpro none of the flows are there.

 

[TheDoz]

Are you saving the call flow with a .mdb file extension?
Export and import using .mdb as file extension.


"A politician is a fellow who will lay down your life for his country.

 

[mettech2]

Yes. I am importing and exporting in .mdb file extension. I can import the same file into 3.0 without a problem. It is just importing into 3.1 or higher.

 

[jml2665]

what sort of server? OS?? anything other apps installed other then the VMPro stuff?

 

[aarenot]

improt the file into 3.0
then export the file again, and save it seperate from the original export.

then, try importing ther file again in 3.1

make sure to follow the procedure in the pdf to the letter, and do the reg file executions as well.

i assume you have uninstalled the old 3.0. also after uninstalling, delete all of the files from the old 3.0 vm manualy. save your mdb file on a seperate facility, like a usb drive, or compress it and em it out to yourself.

also, if possiblt try importing it on a different pc to see if it is a issue with the machine. this is a strange one.

you are using
file
import
and following the pop up menus to import the mdb file, correct

You do not always get what you pay for, but you never get what you do not pay for.

 

[mettech2]

Ok...looks like we finally figured it out. There were some broken connector links in the flows. It did not seem to matter in 3.0.13 but would break in any version higher than that. Thanks for all the help in troubleshooting this...