External Script Driver Crash

This forum can be browsed by the general public. Posting is limited to current SAPIEN license holders with active maintenance and does not offer a response time guarantee.
Forum rules
DO NOT POST LICENSE NUMBERS, ACTIVATION KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM.
Only the original author and our tech personnel can reply to a topic that is created in this forum. If you find a topic that relates to an issue you are having, please create a new topic and reference the other in your post.

Any code longer than three lines should be added as code using the 'Select Code' dropdown menu or attached as a file.
User avatar
smokingjoe
Posts: 16
Joined: Wed Jul 22, 2015 4:20 am

External Script Driver Crash

Post by smokingjoe »

Product PowerStudio 2016 Version 5.2.127
32 or 64 bit version of product: 64bit
Operating system: Windows 8.1
32 or 64 bit OS: 64bit
PowerShell Version:
Major Minor Build Revision
----- ----- ----- --------
4 0 -1 -1


Repeatable crash in the External Script Driver. one thing I notice is that Powershell Studio.exe is a 64bit process ut the ScriptDriver32.exe seems to be a 32bit driver. Here are some details from the event log.

Application: scriptdriver32.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
Stack:
at System.Buffer.__Memcpy(Byte*, Byte*, Int32)
at System.Buffer._Memcpy(Byte*, Byte*, Int32)
at System.Buffer.Memcpy(Byte*, Byte*, Int32)
at System.StubHelpers.BSTRMarshaler.ConvertToNative(System.String, IntPtr)

Faulting application name: scriptdriver32.exe, version: 1.4.40.0, time stamp: 0x57722e7a
Faulting module name: MSVCR120_CLR0400.dll, version: 12.0.52361.36361, time stamp: 0x5743c02b
Exception code: 0xc0000005
Fault offset: 0x0000137a
Faulting process id: 0x3754
Faulting application start time: 0x01d1f193b7ca35cc
Faulting application path: C:\Program Files (x86)\Common Files\SAPIEN Debugger 2016\scriptdriver32.exe
Faulting module path: C:\WINDOWS\SYSTEM32\MSVCR120_CLR0400.dll
Report Id: 0083d612-5d87-11e6-82eb-7c5cf822cdb4
Faulting package full name:
Faulting package-relative application ID:

User avatar
Alexander Riedel
Posts: 7458
Joined: Tue May 29, 2007 4:43 pm

Re: External Script Driver Crash

Post by Alexander Riedel »

Possibly missing the correct run-time for the 32 bit version. Is there any specific reason you need to run your scripts in 32 bit mode? Have you tried 64 bit mode?
Alexander Riedel
SAPIEN Technologies, Inc.

User avatar
smokingjoe
Posts: 16
Joined: Wed Jul 22, 2015 4:20 am

Re: External Script Driver Crash

Post by smokingjoe »

No just did not pay attention to that box. I guess I assumed it should be running the same engine version my bad. Seems to work if I set to 64bit.