PrimalScript Ent 2007 crashes running PoSH script

Post by **rbarbour** » Fri May 16, 2008 6:40 am

[Original post to http://www.sapien.com/forums/viewtopic. ... t=20#p9176]
Releases 565 & 566 crash Primalscript if I try to run "hello world" within the editor. I have reverted to 564 since it at least doesn't crash when I try to run a PoSH script. I have reproduced it on multiple W2K3 servers. Works fine on Windows XP, though.

[Reply from Alex Riedel]
Can you provide a little more detail? Our test servers run PowerShell scripts fine, so we need some more information on your environment.

What exactly constitutes a "Hello World" script in your case? When exactly does the crash occur? Before output, after output? Are these W2K3 servers 64 or 32 bit?
When you say it runs fine on XP, did you compare what exact PowerShell versions and build numbers you run?

Did you by any chance install a PowerShell 2 CTP on any of these servers?
Please post this information in a new thread, so that we can keep issues separated.

Thanks,

Alex

[Information new in this post]
I can reproduce this on x86 and x64 OS builds. I have not installed any PoSH V2 CTP versions.

The entire script content is:

"Hello World"

When using the Run Script [F7 or menu] option from within the IDE (build 4.5.566), the output window appears and there is a long pause where the IDE becomes unresponsive. After a few moments, the GUI disappears. Primalscript.exe sometimes exists, sometimes remains in the process list and has to be terminated manually.

The environment has not changed (except for the build of PrimalScript) from the one posted at http://www.sapien.com/forums/viewtopic. ... t=20#p9176]

PrimalScript 2007 Enterprise v4.5.566

OS Name Microsoft(R) Windows(R) Server 2003 Enterprise x64 Edition; Version = "5.2.3790.1830 (srv03_sp1_rtm.050324-1447)

PowerShell version is 6.0.5429.0"

Execution policy is set to RemoteSigned in both the x32 and x64 versions of PowerShell

NetFX versions are v1.1.4322 & v2.0.50727

NetFX x64 version is v2.0.50727

PoSH environment on Server 2003 Enterprise x64

Name : Microsoft.PowerShell.Core
IsDefault : True
ApplicationBase : C:WINDOWSsyswow64WindowsPowerShellv1.0
AssemblyName : System.Management.Automation, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad
364e35, ProcessorArchitecture=MSIL
ModuleName : C:WINDOWSsyswow64WindowsPowerShellv1.0System.Management.Automation.dll
PSVersion : 1.0
Version : 1.0.0.0
Types : {types.ps1xml}
Formats : {Certificate.format.ps1xml, DotNetTypes.format.ps1xml, FileSystem.format.ps1xml, Help.for
mat.ps1xml...}
Description : This Windows PowerShell snap-in contains Windows PowerShell management cmdlets used to ma
nage components of Windows PowerShell.
Vendor : Microsoft Corporation
LogPipelineExecutionDetails : False

Name : Microsoft.PowerShell.Host
IsDefault : True
ApplicationBase : C:WINDOWSsyswow64WindowsPowerShellv1.0
AssemblyName : Microsoft.PowerShell.ConsoleHost, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf38
56ad364e35, ProcessorArchitecture=MSIL
ModuleName : C:WINDOWSsyswow64WindowsPowerShellv1.0Microsoft.PowerShell.ConsoleHost.dll
PSVersion : 1.0
Version : 1.0.0.0
Types : {}
Formats : {}
Description : This Windows PowerShell snap-in contains cmdlets used by the Windows PowerShell host.
Vendor : Microsoft Corporation
LogPipelineExecutionDetails : False

Name : Microsoft.PowerShell.Management
IsDefault : True
ApplicationBase : C:WINDOWSsyswow64WindowsPowerShellv1.0
AssemblyName : Microsoft.PowerShell.Commands.Management, Version=1.0.0.0, Culture=neutral, PublicKeyToke
n=31bf3856ad364e35, ProcessorArchitecture=MSIL
ModuleName : C:WINDOWSsyswow64WindowsPowerShellv1.0Microsoft.PowerShell.Commands.Management.dll
PSVersion : 1.0
Version : 1.0.0.0
Types : {}
Formats : {}
Description : This Windows PowerShell snap-in contains management cmdlets used to manage Windows compon
ents.
Vendor : Microsoft Corporation
LogPipelineExecutionDetails : False

Name : Microsoft.PowerShell.Security
IsDefault : True
ApplicationBase : C:WINDOWSsyswow64WindowsPowerShellv1.0
AssemblyName : Microsoft.PowerShell.Security, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856a
d364e35, ProcessorArchitecture=MSIL
ModuleName : C:WINDOWSsyswow64WindowsPowerShellv1.0Microsoft.PowerShell.Security.dll
PSVersion : 1.0
Version : 1.0.0.0
Types : {}
Formats : {}
Description : This Windows PowerShell snap-in contains cmdlets to manage Windows PowerShell security.
Vendor : Microsoft Corporation
LogPipelineExecutionDetails : False

Name : Microsoft.PowerShell.Utility
IsDefault : True
ApplicationBase : C:WINDOWSsyswow64WindowsPowerShellv1.0
AssemblyName : Microsoft.PowerShell.Commands.Utility, Version=1.0.0.0, Culture=neutral, PublicKeyToken=3
1bf3856ad364e35, ProcessorArchitecture=MSIL
ModuleName : C:WINDOWSsyswow64WindowsPowerShellv1.0Microsoft.PowerShell.Commands.Utility.dll
PSVersion : 1.0
Version : 1.0.0.0
Types : {}
Formats : {}
Description : This Windows PowerShell snap-in contains utility Cmdlets used to manipulate data.
Vendor : Microsoft Corporation
LogPipelineExecutionDetails : False

Name : Pscx
IsDefault : False
ApplicationBase : C:Program Files (x86)PowerShell Community Extensions
AssemblyName : Pscx, Version=1.1.1.0, Culture=neutral, PublicKeyToken=null
ModuleName : C:Program Files (x86)PowerShell Community ExtensionsPscx.dll
PSVersion : 1.0
Version : 1.1.1.0
Types : {TypeDataDateTime.ps1xml, TypeDataDirectoryServices.ps1xml, TypeDataFeedStore.ps1xml,
TypeDataFileSystem.ps1xml...}
Formats : {FormatDataDirectoryServices.ps1xml, FormatDataPingHost.ps1xml, FormatDataPscx.ps1xml,
FormatDataTerminalServices.ps1xml}
Description : PowerShell Community Extensions (PSCX) base snapin which implements a general purpose set
of cmdlets.
Vendor : PowerShell Community Developers
LogPipelineExecutionDetails : False

Windows XP version is "5.1.2600.2765 (xpsp.050928-1517)".
PoSH environment on XP:

Name : Microsoft.PowerShell.Core
IsDefault : True
ApplicationBase : C:WINDOWSsystem32WindowsPowerShellv1.0
AssemblyName : System.Management.Automation, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=
MSIL
ModuleName : C:WINDOWSsystem32WindowsPowerShellv1.0System.Management.Automation.dll
PSVersion : 1.0
Version : 1.0.0.0
Types : {types.ps1xml}
Formats : {Certificate.format.ps1xml, DotNetTypes.format.ps1xml, FileSystem.format.ps1xml, Help.format.ps1xml...}
Description : This Windows PowerShell snap-in contains Windows PowerShell management cmdlets used to manage components of Windows Pow
erShell.
Vendor : Microsoft Corporation
LogPipelineExecutionDetails : False

Name : Microsoft.PowerShell.Host
IsDefault : True
ApplicationBase : C:WINDOWSsystem32WindowsPowerShellv1.0
AssemblyName : Microsoft.PowerShell.ConsoleHost, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, ProcessorArchitect
ure=MSIL
ModuleName : C:WINDOWSsystem32WindowsPowerShellv1.0Microsoft.PowerShell.ConsoleHost.dll
PSVersion : 1.0
Version : 1.0.0.0
Types : {}
Formats : {}
Description : This Windows PowerShell snap-in contains cmdlets used by the Windows PowerShell host.
Vendor : Microsoft Corporation
LogPipelineExecutionDetails : False

Name : Microsoft.PowerShell.Management
IsDefault : True
ApplicationBase : C:WINDOWSsystem32WindowsPowerShellv1.0
AssemblyName : Microsoft.PowerShell.Commands.Management, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, ProcessorA
rchitecture=MSIL
ModuleName : C:WINDOWSsystem32WindowsPowerShellv1.0Microsoft.PowerShell.Commands.Management.dll
PSVersion : 1.0
Version : 1.0.0.0
Types : {}
Formats : {}
Description : This Windows PowerShell snap-in contains management cmdlets used to manage Windows components.
Vendor : Microsoft Corporation
LogPipelineExecutionDetails : False

Name : Microsoft.PowerShell.Security
IsDefault : True
ApplicationBase : C:WINDOWSsystem32WindowsPowerShellv1.0
AssemblyName : Microsoft.PowerShell.Security, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture
=MSIL
ModuleName : C:WINDOWSsystem32WindowsPowerShellv1.0Microsoft.PowerShell.Security.dll
PSVersion : 1.0
Version : 1.0.0.0
Types : {}
Formats : {}
Description : This Windows PowerShell snap-in contains cmdlets to manage Windows PowerShell security.
Vendor : Microsoft Corporation
LogPipelineExecutionDetails : False

Name : Microsoft.PowerShell.Utility
IsDefault : True
ApplicationBase : C:WINDOWSsystem32WindowsPowerShellv1.0
AssemblyName : Microsoft.PowerShell.Commands.Utility, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, ProcessorArch
itecture=MSIL
ModuleName : C:WINDOWSsystem32WindowsPowerShellv1.0Microsoft.PowerShell.Commands.Utility.dll
PSVersion : 1.0
Version : 1.0.0.0
Types : {}
Formats : {}
Description : This Windows PowerShell snap-in contains utility Cmdlets used to manipulate data.
Vendor : Microsoft Corporation
LogPipelineExecutionDetails : False

Name : NetCmdlets
IsDefault : False
ApplicationBase : C:Program FilesnsoftwareNetCmdlets
AssemblyName : nsoftware.NetCmdlets.Commands, Version=1.0.3022.0, Culture=neutral, PublicKeyToken=cdc168f89cffe9cf
ModuleName : C:Program FilesnsoftwareNetCmdletsnsoftware.NetCmdlets.Commands.dll
PSVersion : 1.0
Version : 1.0.3022.0
Types : {}
Formats : {}
Description : /n software NetCmdlets
Vendor : /n software inc.
LogPipelineExecutionDetails : False

Name : Pscx
IsDefault : False
ApplicationBase : C:Program FilesPowerShell Community Extensions
AssemblyName : Pscx, Version=1.1.1.0, Culture=neutral, PublicKeyToken=null
ModuleName : C:Program FilesPowerShell Community ExtensionsPscx.dll
PSVersion : 1.0
Version : 1.1.1.0
Types : {TypeDataDateTime.ps1xml, TypeDataDirectoryServices.ps1xml, TypeDataFeedStore.ps1xml, TypeDataFileSystem.ps1xml...}
Formats : {FormatDataDirectoryServices.ps1xml, FormatDataPingHost.ps1xml, FormatDataPscx.ps1xml, FormatDataTerminalServices.p
s1xml}
Description : PowerShell Community Extensions (PSCX) base snapin which implements a general purpose set of cmdlets.
Vendor : PowerShell Community Developers
LogPipelineExecutionDetails : False

Name : PshX-SAPIEN
IsDefault : False
ApplicationBase : C:ScriptsPowerShelldownloadsPSCX
AssemblyName : PshX-SAPIEN, Version=1.2.0.0, Culture=neutral, PublicKeyToken=null
ModuleName : C:ScriptsPowerShelldownloadsPSCXpshx-sapien.dll
PSVersion : 1.0
Version : 1.2.0.0
Types : {}
Formats : {}
Description : SAPIEN Extensions for PowerShell adds several cmdlets for working with databases and for use in logon scripts.
Vendor : SAPIEN Technologies, Inc.
LogPipelineExecutionDetails : False

Windows XP version is "5.1.2600.2765 (xpsp.050928-1517)".
PoSH environment on XP:

Post by **Alexander Riedel** » Fri May 16, 2008 7:20 am

Remove the PowerShell Community Extensions from your profile and try again. Most likely your crash is in PSCX.DLL and caused by the Community Extensions.

Alex

Post by **rbarbour** » Fri May 16, 2008 9:19 am

That is very strange. This PrimalScript feature currently works on Windows Server x64 and has always worked on my XP x86 client with PSCX loaded.

Does not work for my Windows Server x86, even with PSCX not installed. This Server x86 build is much older, so something may be 'busted' on this OS somehow. If others say it works on Server 2003 x86 then I'll accept it is a problem on my end.

Since my last test on this x64 server host (that failed, BTW), I have installed some more SW; that may have changed the environment. I intend to change from the x86 to x64 OS for my development work, so as long as it's working on this new build I guess I'm OK with it.

I know that PrimalScript uses some internal instance/engine/emulation of the PoSH environment, but my expectation is that I should be able to run scripts within PrimalScript that I can run within the real PowerShell shell. I'm not trying to be rude, just clearly stating my expectation the scripts should run equally in both environments.

Post by **Alexander Riedel** » Fri May 16, 2008 10:22 am

No offense taken, your expectation is correct, but please note that there are always multiple vendors involved. We host the same engine PowerShell.exe hosts, we run the same profiles and we actually use the same thing, not an emulation. We use Microsoft's official hosting API.

There are various plugins that don't always work, the community extensions is one of those that come up frequently, hence my suggestion to try that.

In order to figure this out, we really need to look more coordinated at your enviroment. From your first post I was sure this happens equally on 64 and 32 bit Windows 2003 installations you have. From your second post it sounds like this only does NOT work on 2003 32 bit. I am therefore
not quite sure what I should be looking for.

When you get a crash, the resulting dialog usually also shows a module at the very least. Please include that information. Please try ALWAYS to run the same thing with profiles disabled to see if there is anything loaded there that causes this. If a plugin causes this, see if there is a new version.

We'll be happy to look at whatever information you can provide.

Alex

Post by **rbarbour** » Fri May 16, 2008 11:03 am

I agree that it's strange that it now works on the x64 system, but not on the x86. Is there some diagnostic I can enable to capture what's happening. All I see is the PrimalScript UI hang for a few moments, then it disappears. There is no "resulting dialog", no Dr Watson, if you will.

I did find this in the Application event log:
Source: .NET Runtime 2.0 Error
Category: None
Type Error
Event ID: 1000

Faulting application primalscript.exe, version 4.5.566.0, stamp 48054b97, faulting module primalscript.exe, version 4.5.566.0, stamp 48054b97, debug? 0, fault address 0x000b5961.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Following that link and submitting the information results in

Details

ID:
1000

Source:
.NET Runtime 2.0 Error Reporting

We're sorry

There is no additional information about this issue in the Error and Event Log Messages or Knowledge Base databases at this time. You can use the links in the Support area to determine whether any additional information might be available elsewhere.

Thank you for searching on this message; your search helps us identify those areas for which we need to provide more information.

Post by **Alexander Riedel** » Fri May 16, 2008 2:51 pm

Hmm, thanks. I'll see what I can do with that.

Alex

Post by **rbarbour** » Mon Jun 16, 2008 1:42 am

What's the status? Is there anything I can send you to help you reproduce this problem? It's getting to the point where PrimalScript is not providing the value I paid for it.

Post by **Alexander Riedel** » Mon Jun 16, 2008 7:39 pm

Unfortunately we have not been able to produce this problem.
We did discover a potential thread synchronization issue that, if a machine is under heavy load, could cause this, theoretically.

I have added some traps to the next service build to get better diagnostics if something like that might happen.
Let's take it from there and see if this persists.

Thank you for your patience!

Alex

Post by **jclore@quixtar.com** » Thu Jul 31, 2008 12:26 am

I get a very silimiar experience on my Windows Server 2003. Same "hello, world" code same PrimalScript build. Running Windows Server 2003 x86 SP2. Also, I do get a popup error message:Title: PSIntellisense: primalscript.exe - Application ErrorDescription: The instruction at "0x004b3933" referenced memory at "0x00000000". The memory could not be "read".Click on OK to terminate the programClick on CANCEL to debug the programAlso, I get Event ID: 1000 Source: Application ErrorFaulting application primalscript.exe, version 4.5.566.0, faulting module primalscript.exe, version 4.5.566.0, fault address 0x000b3933.For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Post by **Alexander Riedel** » Mon Aug 04, 2008 7:49 pm

I have tried for a few days to produce this now, unfortunately to no end.
It is not quite clear where and how that happens. From the error message title (PSIntellisense: primalscript.exe ) I would deduct that this MUST happen when some form of PrimalSense is about to engage.

Please update to the latest service build and see if this persists.
If you can, please provide an exact chain of events to make this happen, even if it's only moving the mouse somewhere that may produce a tooltip.

Thanks!

Alex