Skip to main content

I have a script that is being run from an Access database with the VBA line

Script = Shell("C:\\Program Files\\Micro Focus\\RUMBA\\System\\ScriptEngine\\vsp.exe" & " " & Path & "MO.csf", vbNormalFocus) 

This was working fine until last week when my users started mentioning that the script would start and then crash. 

Below is the event in event view when this happens. The same script runs fine if it is launched manually by double clicking on it. But users randomly get the failure below when using the database in the automated process. Has anyone else ran into this issue? Thanks.

<?xml version="1.0" encoding="UTF-8" standalone="true"?>

-<Events>


-<Event xmlns="schemas.microsoft.com/.../event">


-<System>

<Provider Name="Application Error"/>

<EventID Qualifiers="0">1000</EventID>

<Level>2</Level>

<Task>100</Task>

<Keywords>0x80000000000000</Keywords>

<TimeCreated SystemTime="2016-04-18T09:15:35.000000000Z"/>

<EventRecordID>35100</EventRecordID>

<Channel>Application</Channel>

<Computer>name</Computer>

<Security/>

</System>


-<EventData>

<Data>vsp.exe</Data>

<Data>8.0.404.0</Data>

<Data>4b0ad2ae</Data>

<Data>OLEAUT32.dll</Data>

<Data>6.1.7601.19144</Data>

<Data>56b24bc6</Data>

<Data>c0000005</Data>

<Data>00020b9e</Data>

<Data>3e88</Data>

<Data>01d19952c862b20b</Data>

<Data>C:\\Program Files\\Micro Focus\\RUMBA\\System\\ScriptEngine\\vsp.exe</Data>

<Data>C:\\Windows\\system32\\OLEAUT32.dll</Data>

<Data>1b426a19-0546-11e6-b0a5-40a8f0441f3a</Data>

</EventData>


-<RenderingInfo Culture="en-US">

<Message>Faulting application name: vsp.exe, version: 8.0.404.0, time stamp: 0x4b0ad2ae Faulting module name: OLEAUT32.dll, version: 6.1.7601.19144, time stamp: 0x56b24bc6 Exception code: 0xc0000005 Fault offset: 0x00020b9e Faulting process id: 0x3e88 Faulting application start time: 0x01d19952c862b20b Faulting application path: C:\\Program Files\\Micro Focus\\RUMBA\\System\\ScriptEngine\\vsp.exe Faulting module path: C:\\Windows\\system32\\OLEAUT32.dll Report Id: 1b426a19-0546-11e6-b0a5-40a8f0441f3a</Message>

<Level>Error</Level>

<Task>Application Crashing Events</Task>

<Opcode>Info</Opcode>

<Channel/>

<Provider/>


-<Keywords>

<Keyword>Classic</Keyword>

</Keywords>

</RenderingInfo>

</Event>

</Events>


#Rumba

I have a script that is being run from an Access database with the VBA line

Script = Shell("C:\\Program Files\\Micro Focus\\RUMBA\\System\\ScriptEngine\\vsp.exe" & " " & Path & "MO.csf", vbNormalFocus) 

This was working fine until last week when my users started mentioning that the script would start and then crash. 

Below is the event in event view when this happens. The same script runs fine if it is launched manually by double clicking on it. But users randomly get the failure below when using the database in the automated process. Has anyone else ran into this issue? Thanks.

<?xml version="1.0" encoding="UTF-8" standalone="true"?>

-<Events>


-<Event xmlns="schemas.microsoft.com/.../event">


-<System>

<Provider Name="Application Error"/>

<EventID Qualifiers="0">1000</EventID>

<Level>2</Level>

<Task>100</Task>

<Keywords>0x80000000000000</Keywords>

<TimeCreated SystemTime="2016-04-18T09:15:35.000000000Z"/>

<EventRecordID>35100</EventRecordID>

<Channel>Application</Channel>

<Computer>name</Computer>

<Security/>

</System>


-<EventData>

<Data>vsp.exe</Data>

<Data>8.0.404.0</Data>

<Data>4b0ad2ae</Data>

<Data>OLEAUT32.dll</Data>

<Data>6.1.7601.19144</Data>

<Data>56b24bc6</Data>

<Data>c0000005</Data>

<Data>00020b9e</Data>

<Data>3e88</Data>

<Data>01d19952c862b20b</Data>

<Data>C:\\Program Files\\Micro Focus\\RUMBA\\System\\ScriptEngine\\vsp.exe</Data>

<Data>C:\\Windows\\system32\\OLEAUT32.dll</Data>

<Data>1b426a19-0546-11e6-b0a5-40a8f0441f3a</Data>

</EventData>


-<RenderingInfo Culture="en-US">

<Message>Faulting application name: vsp.exe, version: 8.0.404.0, time stamp: 0x4b0ad2ae Faulting module name: OLEAUT32.dll, version: 6.1.7601.19144, time stamp: 0x56b24bc6 Exception code: 0xc0000005 Fault offset: 0x00020b9e Faulting process id: 0x3e88 Faulting application start time: 0x01d19952c862b20b Faulting application path: C:\\Program Files\\Micro Focus\\RUMBA\\System\\ScriptEngine\\vsp.exe Faulting module path: C:\\Windows\\system32\\OLEAUT32.dll Report Id: 1b426a19-0546-11e6-b0a5-40a8f0441f3a</Message>

<Level>Error</Level>

<Task>Application Crashing Events</Task>

<Opcode>Info</Opcode>

<Channel/>

<Provider/>


-<Keywords>

<Keyword>Classic</Keyword>

</Keywords>

</RenderingInfo>

</Event>

</Events>


#Rumba

Hi elcron, 

Unfortunately, we do not have any similar reported incidents, and I am unable to reproduce this error. I'm testing with MS Access 2013 (15.0.4771.1000) and Rumba 9.4.

Can you try running vse.exe in place of esp.exe in your VBA subroutine and then manually run the script from the editor? Does it work as expected?

Can you try a simple script to see it is executes OK using VSE.exe, here is what I tested with.

Sub Main
Dim MyString as String, MyMsg as String, i as Integer
MyMsg = ""
For i = 1 to 10
EMReadScreen MyString, 80, i, 1
MyMsg = MyMsg & MyString & Chr(10)
Next i
Msgbox MyMsg
End Sub

Also, have you tried an alternative method of launching the script? I often use CreateProcess for Kernel32.dll, here is some sample code.

Option Compare Database

Private Type PROCESS_INFORMATION
hProcess As Long
hThread As Long
dwProcessId As Long
dwThreadId As Long
End Type

Private Type STARTUPINFO
cb As Long
lpReserved As String
lpDesktop As String
lpTitle As String
dwX As Long
dwY As Long
dwXSize As Long
dwYSize As Long
dwXCountChars As Long
dwYCountChars As Long
dwFillAttribute As Long
dwFlags As Long
wShowWindow As Integer
cbReserved2 As Integer
lpReserved2 As Long
hStdInput As Long
hStdOutput As Long
hStdError As Long
End Type

Private Declare Function OpenProcess Lib "kernel32" (ByVal dwDesiredAccess As Long, ByVal bInheritHandle As Long, ByVal dwProcessId As Long) As Long
Private Declare Function GetExitCodeProcess Lib "kernel32" (ByVal hProcess As Long, lpExitCode As Long) As Long
Private Declare Function CreateProcess Lib "kernel32" Alias "CreateProcessA" (ByVal lpApplicationName As String, ByVal lpCommandLine As String, lpProcessAttributes As Any, lpThreadAttributes As Any, ByVal bInheritHandles As Long, ByVal dwCreationFlags As Long, lpEnvironment As Any, ByVal lpCurrentDriectory As String, lpStartupInfo As STARTUPINFO, lpProcessInformation As PROCESS_INFORMATION) As Long

Const SYNCHRONIZE = 1048576
Const NORMAL_PRIORITY_CLASS = &H20&

Dim pInfo As PROCESS_INFORMATION
Dim sInfo As STARTUPINFO

Sub RunAndReturn(RunThisOne As String)

Dim sNull As String
Dim lSuccess As Long
Dim lRetValue As Long
Dim Path As String

Path = "c:\\temp\\"
sInfo.cb = Len(sInfo)

lSuccess = CreateProcess(sNull, "C:\\Program Files (x86)\\Micro Focus\\RUMBA\\System\\ScriptEngine\\vsp.exe " Path RunThisOne, ByVal 0&, ByVal 0&, 1&, NORMAL_PRIORITY_CLASS, ByVal 0&, Path, sInfo, pInfo)

Do While lSuccess > 0
nn = GetExitCodeProcess(pInfo.hProcess, nExitCode)
If nExitCode = 0 Then lSuccess = 0
Loop
End Sub

Sub test()
Dim Path As String
Path = "c:\\temp\\"
RunAndReturn ("Msgbox10Rows.csf")
' Script = Shell("C:\\Program Files (x86)\\Micro Focus\\RUMBA\\System\\ScriptEngine\\vsp.exe" & " " & Path & "Msgbox10Rows.csf", vbNormalFocus)
End Sub

Given that you state the issue only started to occurs last week and it appears as if multiple users were affected simultaneously, something must have changed.

Can you check for any recent Windows updates?
Can you check the host screens to ensure they have not changed (it's unlikely as you say you can run the script manually)?
Have you had any patches recently applied to your Rumba install base?

If you are unable to address the issue, I would advise you to open a ticket with Micro Focus Technical Support.