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

VBScript action not always firing 1

Status
Not open for further replies.

paul1979

IS-IT--Management
Aug 19, 2008
27
GB
I've got a trial Advanced Edition licence on my VMPro at the moment as I'm trying out some VBScript stuff that we want to use shortly, but got an odd problem with it. Thought I'd ask here first before going to our reseller as it may be something in the code I can do as opposed to something else.

Basically, the VBScript actions don't always fire. If I let the call flow complete and disconnect me by itself, I can run it again fine, so I know my code's not necessarily incorrect. However, it appears that if the call is hung up during the VBScript being run, another VBScript action won't work until I restart the voicemail service. All other call flows not using VBScript continue to function fine without a service restart... unless I put a VBScript action in, and then it runs ok up to the VBScript and then halts, unless I restart the service.

I can re-write the call flow I want to do using the Database actions, but I'd rather use VBScript as it's easier from my point of view (says the VB6 Programmer!)

I'm using VMPro 7.0(28) on a Windows 2008 R2 x64 box, and I'll post the code if necessary later.
 
Yeah I would post the code.
Just FYI thought, the DB actions within vmpro are SUPER easy.

-Austin
ACE: Implement IP Office
qrcode.png
 
Aha! Think I may have a solution (and it's not my dodgy coding - for once!)

Did a bit more Googling, and found I might need to look in DbgOut.txt (I didn't know that was the VMPro log until then!) - Had a look in there, and sure enough found some errors starting the VBS temporary file it created when running.

The error was 0x80004005 and after a bit more time on google, it seems related to the fact that its a x64 server and (I'm presuming) VMPro is 32-bit. I've registered the copy of vbscript.dll in c:\windows\system\syswow64 as per a bunch of instructions I came across, and appears to work thus far.....! :)
 
I've rewritten it using the DB actions, and actually now works perfectly!!!

AACon - you were right, it was super-easy!! Serves me right for trying to reinvent the wheel :)
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top