PureConnect

 View Only

Discussion Thread View
  • 1.  Weird Error IpShellExec() : CreateProcess failed with error code

    Posted 04-28-2016 22:05
    IpShellExec() : CreateProcess failed with error code: 193 : %1 is not a valid Win32 application. [Context Attribute 'Thread Name']: IP-Handler [Context Attribute 'IP Context Id']: 172 This is from an Execute Shell Command handler which is calling a .vbs script that opens up Office Windows 2007. Server is 2016 R2... Any idea what this could mean?


  • 2.  RE: Weird Error IpShellExec() : CreateProcess failed with error code

    GENESYS
    Posted 04-29-2016 12:16
    I would guess that the error basically amounts to that windows server not knowing what to do with a .vbs file. Does the script execute if you double click on the .vbs file in explorer or run it from a command line by hand? My guess is that if you try to run the file it will pop a "How do you want to open this type of file" dialog. Once you setup that association everything will work as desired.


  • 3.  RE: Weird Error IpShellExec() : CreateProcess failed with error code

    Posted 04-29-2016 14:31
    Originally posted by I3 ACD Guy;33391
    I would guess that the error basically amounts to that windows server not knowing what to do with a .vbs file. Does the script execute if you double click on the .vbs file in explorer or run it from a command line by hand? My guess is that if you try to run the file it will pop a "How do you want to open this type of file" dialog. Once you setup that association everything will work as desired.
    This .VBS file requires parameters passed in it to run. If I run it manually via command prompt it runs fine though, only when the handler executes it does this happen. d:\work\word.vbs 517050773016 /Tokens:"the_provider_fax_num|the_sfhp_id|the_first_name|the_last_name|the_gender|the_dob|THE_REQUESTED_DATE|the_status|the_program|the_medical_group |the_pcp_name|the_pcp_clinic|the_pcp_phone|the_OfficevisitCopay|the_ERvisitCopay|the_genericdrug|the_branddrug|THE_CONFIRMATION_NUMBER|the_fax_to_name|the_fax_to_num" /Values:"000-000-0000||||||12/4/2010|||||||||||517050773016|SFHP Provider|000-000-0000" The IP log has correct usage of the command as well, if I copy from the IP log and run it also runs fine. Execute Shell Command for sure allows .vbs to run in 2016 R2 correct? It worked perfectly in 3.0 :(


  • 4.  RE: Weird Error IpShellExec() : CreateProcess failed with error code

    GENESYS
    Posted 04-29-2016 15:11
    Are you logged in with the same account that IC run as? If you are running as the same account, then it is possible that you would need to prefix your ipShellExec command with the utility that runs the vbs file, Wscript.exe.


  • 5.  RE: Weird Error IpShellExec() : CreateProcess failed with error code

    Posted 04-29-2016 15:22
    Originally posted by I3 ACD Guy;33393
    Are you logged in with the same account that IC run as? If you are running as the same account, then it is possible that you would need to prefix your ipShellExec command with the utility that runs the vbs file, Wscript.exe.
    Yes it is the same account. Here is the Execute Command Shell, where would you suggest putting wscript.exe? [ATTACH]729[/ATTACH]


  • 6.  RE: Weird Error IpShellExec() : CreateProcess failed with error code

    Posted 04-29-2016 15:25
    Workspace value is : D:\\work\\ File Name value is : word.vbs (located in D:\work\) Command Line Parameters are: "" & sUniqueId & " " & "/Tokens:" & sTokens & " " & "/Values:" & sValues Error from IP N CIP2HandlerStep_External::Run : STEP_ENTERED(stepID=43 | type=External | func=IpShellExec | dll=IpMiscellaneousToolsU) 08:25:20.4179065_0274 HandlerExecution 0x4cc N CIPManager::IntegerCall : Calling IntegerCall (dll=IpMiscellaneousToolsU | func=IpShellExec | parmCount=7 | handler=ivr_sfhp_SendFax | step=43) 08:25:20.4179065_0275 Handler 0x4cc N IpShellExec() : (D:\work\\word.vbs 546692858081 /Tokens:"0|the_fax_to_name|the_fax_to_num" /Values:"0||||||12/4/2010|||||||||||546692858081|0" (hide=1, synchronous=1, wait=30) 08:25:20.4179065_0276 Tools 0x4cc W InterceptorSink::Output : Handler Context: [ Step ID =43, Handler Name = ivr_sfhp_SendFax] < [ Step ID =10, Handler Name = init_sfhp_SendFax] 08:25:20.4179065_0277 HandlerContextInfo 0x4cc E IpShellExec() : CreateProcess failed with error code: 193 : %1 is not a valid Win32 application. 08:25:20.4179065_0278 Tools 0x4cc


  • 7.  RE: Weird Error IpShellExec() : CreateProcess failed with error code

    GENESYS
    Posted 04-29-2016 16:31
    Shouldn't "" & sUniqueId & " " & "/Tokens:" & sTokens & " " & "/Values:" & sValues actually be: " " & sUniqueId & " " & "/Tokens:" & sTokens & " " & "/Values:" & sValues I think you may be missing a space.


  • 8.  RE: Weird Error IpShellExec() : CreateProcess failed with error code

    Posted 04-29-2016 17:09
    Originally posted by GGanahl;33398
    Shouldn't "" & sUniqueId & " " & "/Tokens:" & sTokens & " " & "/Values:" & sValues actually be: " " & sUniqueId & " " & "/Tokens:" & sTokens & " " & "/Values:" & sValues I think you may be missing a space.
    The way it is currently set produces this within IP log. IpShellExec() : (D:\work\\word.vbs 546692858081 /Tokens:"0|the_fax_to_name|the_fax_to_num" /Values:"0||||||12/4/2010|||||||||||546692858081|0" (hide=1, synchronous=1, wait=30) I could remove that blank quotes, but I'm not sure it would do anything. I will try though, thanks


  • 9.  RE: Weird Error IpShellExec() : CreateProcess failed with error code

    GENESYS
    Posted 05-09-2016 12:53
    I found two solutions to this issue. The first solution is to uncheck the "Run Synchronously" checkbox. In my testing this works without having to specify the application that is used to run the .vbs file. However, your task would now run asynchronously and you would not get any return code back from the job. The second solution is to specify the utility that runs the vbs file. My properties look like this: Directory path: "c:\\windows\\system32" File Name: "cscript.exe" Command Line Parameters: "c:\\work\\word.vbs" I verified that setting up my "Execute Shell Command" like that did work correctly with and without the "Run Synchronously" checkbox checked.


Need Help finding something?

Check out the Genesys Knowledge Network - your all-in-one access point for Genesys resources