VM Pro Modules Disappear

[hbsurfn]

I've have had this issue on SE 9.1 and now on an r9 IP500/Windows VM Pro. When I open the VM Pro client some of the modules I have create are not visible. The call flows work fine but I cannot see them in the VM Pro client to be able to edit them. Anyone else had this issue? If so, any fix?

ACIS
ACSS
APSS
CompTIA Convergence+
CCNA
CCVP
I'm also ShoreTel certified

 

[Nortel4Ever]

Is your version of the VM Pro client at the same software level as the VM Pro?

 

[amriddle01]

Been using Remote Desktop?...don't

 

[mojoputter]

Look here

http://www.tek-tips.com/viewthread.cfm?qid=1771750

No matter how hard you try, you can't fix stupid...

 

[RodneyMcSnow]

Where are these built?
As a module or under Short codes?

No known firmware issueswith Avaya, just checked.

 

[IPGuru]

No known firmware issueswith Avaya, just checked.

Lovely line form Avaya that one, I doesn't actually mean there are no issues it just means they don't know about it (yet)
& they are unlikely to if this statement makes whoever is reporting it "go away & stop bothering them".

Clearly there are some circumstances that cause call flows to be lost & they need to start trying to reproduce them even if only so they can use one of their 2 other favorite responses "User Error" or "Design Intent"


Do things on the cheap & it will cost you dear

 

[hbsurfn]

They are Modules not short codes. I tried exporting and opening with another VM Pro Client on a different machine and same issue. I was able to find a usable backup MDB file and import it but am still curious what causes it. This instance is on a MS Hyper-V virtual machine on Server 2008 host. I also had it happen on a fresh 9.1 SE install where none of the modules would display after they were created, but if you add a new one with the same name it would appear in the right side window pane

ACIS
ACSS
APSS
CompTIA Convergence+
CCNA
CCVP
I'm also ShoreTel certified

 

[mojoputter]

Had the same issue at a customer site about a year ago, Avaya accessed the system and said there gone and cannot be fixed. Luckily it was not a very busy auto attd so just rebuilt it.

No matter how hard you try, you can't fix stupid...

 

[vladcbv]

Hy,

1. Like it was mentoined before, be carefull when using Remote desktop..
2. I too had the problem with modules.. try creating a new one with the same identycal name and it should reapear again.. then try changing the name to something else but don't forget to change it in Manager aswell and restart voicemail service .

Good luck!