External Script Driver has stopped Working

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
andypotter
Posts: 10
Joined: Tue May 05, 2015 8:57 am

External Script Driver has stopped Working

Post by andypotter »

Product: PowerShell Studio 2020 (64 Bit)
Build: v5.7.181
OS: Windows 10 Enterprise (64 Bit)
Build: v10.0.18362.0

PSVersion table:
Name Value
---- -----
PSVersion 5.1.18362.628
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.18362.628
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1

We have a workstation with PSS 2020 installed on it, and any time we try to run a script from within PSS, we get an "External Script Driver has stopped working" error message.

Windows Application Log shows two errors, a NET runtime error and an Application Error. I've attached a .txt file with the text of the errors because putting it in the post keeps telling me that I have to have 5 posts before including an external url for some reason.

We've fully removed PSS from the workstation and re-installed it. We've tried repairing the NET framework via the NET Framework repair

Running commands from the console within PSS (either via typing commands in the console window or using the "Run in console" from the Run button) works fine, it's just trying to run a script file that fails.

Any ideas how to fix this?
Attachments
powershell studio errors.txt
(1004 Bytes) Downloaded 14 times

User avatar
brittneyr
Site Admin
Posts: 580
Joined: Thu Jun 01, 2017 7:20 am
Answers: 3
Been upvoted: 1 time

Re: External Script Driver has stopped Working

Post by brittneyr »

Please run the following tool then copy and paste the output:
https://sapien.s3.amazonaws.com/downloa ... nCheck.exe
Brittney Ryn
SAPIEN Technologies, Inc.

User avatar
andypotter
Posts: 10
Joined: Tue May 05, 2015 8:57 am

Re: External Script Driver has stopped Working

Post by andypotter »

Operating System: Windows 10 Enterprise 1903
OS build: 18362.628
32 or 64 bit OS: 64 bit
Screen Resolutions: DISPLAY1: 2496 x 1664 with scale factor 150%, DISPLAY2: 1920 x 1080 with scale factor 100%
PowerShell Core: No PowerShell Core version detected
PowerShell Core (x86): No PowerShell Core (x86) version detected
.NET Core Framework: 3.1.3
.NET Core Framework (x86): No .NET Core Framework (x86) version detected
.NET Core Desktop: 3.1.3
.NET Core Desktop (x86): No .NET Core Desktop (x86) version detected
PowerShell cache:
PowerShell 2: 32 Bit, 64 Bit
PowerShell 5: 32 Bit, 64 Bit
SAPIEN Software:
PowerShell Studio 2020: 5.7.181.0,
SAPIEN Updates: 1.1.37.0,
ScriptMerge 2020: 1.4.83.0
.NET Framework: 4.8 or later

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

Re: External Script Driver has stopped Working

Post by Alexander Riedel »

Please replace the file in your installation with the one in the attached zip file.
It should be located here: C:\Program Files\SAPIEN Technologies, Inc\PowerShell Studio 2020\Debugger64
(You should make a backup of the original file)

Then try again and see if you get any additional error message.
Attachments
PowerShellDebuggerV5.zip
(29.45 KiB) Downloaded 7 times
Alexander Riedel
SAPIEN Technologies, Inc.

User avatar
andypotter
Posts: 10
Joined: Tue May 05, 2015 8:57 am

Re: External Script Driver has stopped Working

Post by andypotter »

Same errors, I've attached a .txt again.
Attachments
new powershell studio errors.txt
(980 Bytes) Downloaded 9 times

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

Re: External Script Driver has stopped Working

Post by Alexander Riedel »

This line here : Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
leads me to believe it is either a .NET runtime problem (Repair does not fix everything) or a permission issue.
Do you have access to another similar machine or VM?
Alexander Riedel
SAPIEN Technologies, Inc.

User avatar
andypotter
Posts: 10
Joined: Tue May 05, 2015 8:57 am

Re: External Script Driver has stopped Working

Post by andypotter »

I don't have access to another of the same model machine, but I did install PSS on another PC running the same OS version and it seemed to work fine.

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

Re: External Script Driver has stopped Working

Post by Alexander Riedel »

This is only an experiment, since we kind of fly blind here. We have no machine that shows that problem.
Rename the file scriptdriver64.exe.config to scriptdriver64.exe.config.disabled
and see if that makes any difference.
Alexander Riedel
SAPIEN Technologies, Inc.

User avatar
andypotter
Posts: 10
Joined: Tue May 05, 2015 8:57 am

Re: External Script Driver has stopped Working

Post by andypotter »

Nope, no change.

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

Re: External Script Driver has stopped Working

Post by Alexander Riedel »

Can you provide some more background? Is that a recently commissioned machine?
Was it working on that one before and stopped? Anything you think could be helpful....
Alexander Riedel
SAPIEN Technologies, Inc.