joeOctel
Technical User
- Feb 11, 2005
- 101
When I upgraded from VM Pro 4.2 to 5.0(21) I noticed that some of my VB Script actions aren't working as expected. I can't concatenate strings that are stored in CP registers or system variables like I could in 4.2.
Also one of my VB Script actions uses WinHTTP. I'm using the CreateObject method to create a new instance and the Set WinHttp = Nothing to close the instance. Everything works fine for about a day then stops working. I'll get an error in the dbg view about "failed to import one of more functions from the WinHTTP library". I can still manually run the VBS script on the VM Pro server. I have to restart the VM Pro service in order for the VM Pro VB Script action to start functioning correctly.
Nothing on the VM Pro server has changed except going from 4.2 to 5.0(21).
I'm guessing I'll have to start a ticket with Avaya, but I was curious if anyone else had similar experiences with the VB Script action.
Joe
Also one of my VB Script actions uses WinHTTP. I'm using the CreateObject method to create a new instance and the Set WinHttp = Nothing to close the instance. Everything works fine for about a day then stops working. I'll get an error in the dbg view about "failed to import one of more functions from the WinHTTP library". I can still manually run the VBS script on the VM Pro server. I have to restart the VM Pro service in order for the VM Pro VB Script action to start functioning correctly.
Nothing on the VM Pro server has changed except going from 4.2 to 5.0(21).
I'm guessing I'll have to start a ticket with Avaya, but I was curious if anyone else had similar experiences with the VB Script action.
Joe