Support Forums

PrimalScript 2015 package crash

Support for all customers who have purchased a PrimalScript product license. This forum does not offer a response time guarantee.
Forum rules
DO NOT POST SUBSCRIPTION NUMBERS, LICENSE 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.
User avatar
clum09
Posts: 114
Joined: Thu Apr 24, 2008 9:11 am

PrimalScript 2015 package crash

Postby clum09 » Mon Jan 25, 2016 1:32 pm

Product, version and build: 7.1.74.122315
32 or 64 bit version of product: 64-Bit
Operating system: Windows 7 Professional
32 or 64 bit OS: 64-Bit

Hello,

I have a PowerShell script that I attempt to package with PrimalScript 2015. The moment I click on the "Build" button I get the error message dialog as shown in attachment. The option I have is to click on the "Close Program" button, and the only file I see in the folder is the script.exe.intermediate file - no .exe file is found in the folder.


How can I package the PowerShell if it keeps crashing like this?
Attachments
PS2015PackagerCrash.jpg
PS2015PackagerCrash.jpg (27.99 KiB) Viewed 3719 times
User avatar
clum09
Posts: 114
Joined: Thu Apr 24, 2008 9:11 am

Re: PrimalScript 2015 package crash

Postby clum09 » Mon Jan 25, 2016 1:43 pm

In the Application Event Viewer general tab, there are lines of error with the description below:

Faulting application name: psbuild.exe, version: 4.1.36.0, time stamp: 0x567af93d
Faulting module name: ntdll.dll, version: 6.1.7601.19045, time stamp: 0x56259295
Exception code: 0xc0000374
Fault offset: 0x00000000000bffc2
Faulting process id: 0x12c0
Faulting application start time: 0x01d157aefb96ff04
Faulting application path: C:\Program Files\SAPIEN Technologies, Inc\PrimalScript 2015\psbuild.exe
Faulting module path: C:\windows\SYSTEM32\ntdll.dll
Report Id: 398a6864-c3a2-11e5-99cc-005056c00008

In the Detail tab if the Application Event Viewer, the errors below were posted:

+ System

- Provider

[ Name] Application Error

- EventID 1000

[ Qualifiers] 0

Level 2

Task 100

Keywords 0x80000000000000

- TimeCreated

[ SystemTime] 2016-01-25T20:28:43.000000000Z

EventRecordID 13635

Channel Application

MyComputername.mydomain.com

Security


- EventData

psbuild.exe
4.1.36.0
567af93d
ntdll.dll
6.1.7601.19045
56259295
c0000374
00000000000bffc2
12c0
01d157aefb96ff04
C:\Program Files\SAPIEN Technologies, Inc\PrimalScript 2015\psbuild.exe
C:\windows\SYSTEM32\ntdll.dll
398a6864-c3a2-11e5-99cc-005056c00008
User avatar
clum09
Posts: 114
Joined: Thu Apr 24, 2008 9:11 am

Re: PrimalScript 2015 package crash

Postby clum09 » Mon Jan 25, 2016 2:19 pm

I attempted to build a brand new Windows 10 Professional with update 1511. I installed PrimalScript 2015 with the latest version on this new computer. I attempted to package the script, and the result is the same. The error dialog is shown in the attachment.
Attachments
PS2015PackagerCrash_Win10.PNG
PS2015PackagerCrash_Win10.PNG (7.97 KiB) Viewed 3710 times
User avatar
Alexander Riedel
Posts: 5862
Joined: Tue May 29, 2007 4:43 pm

Re: PrimalScript 2015 package crash

Postby Alexander Riedel » Mon Jan 25, 2016 2:40 pm

Is it only "the" script or any script?
Alexander Riedel
SAPIEN Technologies, Inc.
User avatar
clum09
Posts: 114
Joined: Thu Apr 24, 2008 9:11 am

Re: PrimalScript 2015 package crash

Postby clum09 » Tue Jan 26, 2016 8:56 am

It appears that the editor generated some strange characters appended to the end of the script during packaging the script. Once this happens, the packager just crashes. Below is what I found in one of my scripts with a successful packaging right before it crashed.

ERROR: ??ÿ : The term '??ÿ' is not recognized as the name of a cmdlet, function, scrip
ERROR: t file, or operable program. Check the spelling of the name, or if a path was i
ERROR: ncluded, verify that the path is correct and try again.
ERROR:
ERROR: At line:118 char:4
ERROR: + ??ÿ <<<<
ERROR: + CategoryInfo : ObjectNotFound: (??ÿ:String) [], CommandNotFound
ERROR: Exception
ERROR: + FullyQualifiedErrorId : CommandNotFoundException
ERROR:

The script never had the strange characters to begin with. I tried to view the strange characters using notepad, and I could not find any strange characters in the script that the packaged script complained about. Also, this is on a brand new Windows 10 machine.
User avatar
Alexander Riedel
Posts: 5862
Joined: Tue May 29, 2007 4:43 pm

Re: PrimalScript 2015 package crash

Postby Alexander Riedel » Tue Jan 26, 2016 9:10 am

This looks like a remnant of an unsuccessful encoding conversion. What encoding are you using for that script?
And please indicate, as asked before, if this is only this ONE particular script or any script.
Alexander Riedel
SAPIEN Technologies, Inc.
User avatar
clum09
Posts: 114
Joined: Thu Apr 24, 2008 9:11 am

Re: PrimalScript 2015 package crash

Postby clum09 » Tue Jan 26, 2016 11:33 am

This is not on one single script. This happens randomly and nearly 90 percent of the times on all the scripts. Therefore, I seldom use PrimalScript 2015 to package my scripts. I always use PrmalScript 2012 to package my scripts since it has never crashed on any script that I package. Maybe because PrimalScript 2015 has the MSI packager which may interferes with the standard script packager.

By the way, the Windows 10 professional computer that runs PrimalScript 2015 does not have any Antivirus software installed either. However, this computer has Visual Studio 2015 Enterprise installed before I installed PrimalScript 2015. I don't know if this will make any difference just because the computer has Visual Studio 2015 Enterprise installed.
User avatar
Alexander Riedel
Posts: 5862
Joined: Tue May 29, 2007 4:43 pm

Re: PrimalScript 2015 package crash

Postby Alexander Riedel » Tue Jan 26, 2016 2:27 pm

Well, no one else seems to have that problem so far (or they don't tell us) so lets find out what is different for you.
Can you try to package a script and as soon as PSBuild blows up zip the script in question and email it to us?

Please also don't try to guess the cause, it would really help if you would answer our questions. We do ask them for a reason.
Some of the things you say do not match up. Originally you say you use Windows 7, then you say Windows 10. I was under the impression this is a new problem, but your last post indicates this has been like that for a while. So I am not sure at the moment where to start to look.

So let me ask you again: What encoding are you using for your scripts?

Also, please copy and paste what you seen in the output window of PrimalScript when that happens. That gives us maybe an indication of WHEN this happens.
Alexander Riedel
SAPIEN Technologies, Inc.
User avatar
DevinL
Site Admin
Posts: 733
Joined: Mon Aug 17, 2015 2:25 pm

Re: PrimalScript 2015 package crash

Postby DevinL » Tue Jan 26, 2016 4:02 pm

So far I have tested packaging a couple PowerShell scripts in as many ways I can think of. One script displayed network adapter information and the other lists all of the software installed on a machine. Here's the tests I performed:

  • I packaged each script as is into an exe and msi, then changed the encoding and rebuilt it using each available option. (ASCII, UTF-8, Unicode BE, Unicode LE).
  • After changing the encoding to ensure that wasn't an issue I tried signing the scripts in each possible encoding then packaging them again.
  • Sign the .exe as well as the script and then rebuild it.
  • Sign the .msi as well as the .exe and script and then rebuild it.
  • Sign ONLY the .exe and then rebuild.
  • Sign ONLY the .msi and then rebuild.

Each of these tests were done on Windows 7 and Windows 10. At this point I don't know where else to look for an issue so any further information would be greatly appreciated. Specifically, as Alex mentioned, if you could provide us with a zip of the project that crashes then I can look into this further.
DevinL
SAPIEN Technologies, Inc.
User avatar
clum09
Posts: 114
Joined: Thu Apr 24, 2008 9:11 am

Re: PrimalScript 2015 package crash

Postby clum09 » Wed Jan 27, 2016 7:44 am

DevinL ,

Have you tried to have a Windows 10 machine that had Visual Studio 2015 Enterprise installed first and then install PrimalScript 2015 and see if this can cause the problem I am experiencing?

But my Windows 7 machine did not have Visual Studio installed, but it still crashed with the dialog screen shot that I attached with this post originally.

Return to “PrimalScript”

Who is online

Users browsing this forum: No registered users and 5 guests