Page 1 of 1

Primalscript Crash on Launch - MSVCR110.dll Error

Posted: Thu Sep 17, 2015 4:13 pm
by lee025
Hi - I am having difficulty getting Primalscript to run after install. It crashes on launch with a general error message (attached).

A quick look at the Event Viewer log indicates a problem with the MSVCR110.dll (screen shot also attached).

Assistance with getting it up and running would be much appreciated.

Details of product:
Product version and build: Primalscript 2015 (32 bit) - 7.1.68.0
Operating System: Windows 7 Professional (32 bit)

Primalscript Crash on Launch - MSVCR110.dll Error

Posted: Thu Sep 17, 2015 4:13 pm
by SAPIEN Support Forums
This is an automated post. A real person will respond soon.

Thank you for posting, lee025.

Did you remember to include the following?
  • 1. Product, version and build (e.g. Product: PrimalScript 2014, Version & Build: 7.0.46. Version and build information can be found in the product's About box accessed by clicking the blue icon with the 'i' in the upper right hand corner of the ribbon.)
    2. Specify if you are running a 32 or 64 bit version
    3. Specify your operating system and if it is 32 or 64 bit.
    4. Attach a screenshot if your issue can be seen on the screen
    5. Attach a zip file if you have multiple files (crash reports, log entries, etc.) related to your issue.
If not, please take a moment to edit your original post or reply to this one.

*** Make sure you do not post any licensing information ***

Re: Primalscript Crash on Launch - MSVCR110.dll Error

Posted: Thu Sep 17, 2015 4:34 pm
by davidc
Can you verify that you have the Microsoft Visual C++ 2012 Redistributable version 11.0.61030 installed?

And did you have a previous build of PrimalScript installed?

David

Re: Primalscript Crash on Launch - MSVCR110.dll Error

Posted: Thu Sep 17, 2015 4:51 pm
by lee025
I can confirm I have Microsoft Visual C++ 2012 Redistributable (x86) version 11.0.61030 installed (screenshot attached).

A previous version of Primalscript 2014 had been installed but would not launch. It was uninstalled prior to trying to install Primalscript 2015.

Re: Primalscript Crash on Launch - MSVCR110.dll Error

Posted: Thu Sep 17, 2015 5:29 pm
by davidc
We are investigating the cause of the crash.

David

Re: Primalscript Crash on Launch - MSVCR110.dll Error

Posted: Thu Sep 17, 2015 9:53 pm
by Alexander Riedel
You said a previous version "would not launch". Can you elaborate on that? Any errors or log entries?

In order to establish if this is a PrimalScript problem or a problem isolated to the runtime or your system, please to the following:

- Download and install PrimalPad. It uses the same runtime but statically
links. Please let us know if it runs.

- Download and install PowerShell Profile Editor. It also uses
these runtimes but in the same fashion as PrimalScript.

Both can be downloaded from this page:
https://www.sapien.com/software/productivity_pack

If you have access to a similar machine in your environment, please also try on this other machine to establish if this is only a problem on this one machine or not.

Thanks!

Re: Primalscript Crash on Launch - MSVCR110.dll Error

Posted: Mon Sep 21, 2015 9:08 pm
by lee025
From memory the previous version of PrimalScript would not launch either. It possibly failed during installation.

Both PrimalPad and PowerShell Profile Editor appear to install and launch just fine. However, I cannot test these applications any further as I am met with an expired trial period screen (I am not aware of either of these previously being installed on this computer, but this is probably the case).

I have not been able to test PrimalScript on a similar computer but understand it had worked in the past.

Re: Primalscript Crash on Launch - MSVCR110.dll Error

Posted: Tue Sep 22, 2015 10:59 am
by DevinL
Please try updating to the latest build (7.1.69) and verify it resolves the issue for you.

Re: Primalscript Crash on Launch - MSVCR110.dll Error

Posted: Tue Sep 22, 2015 6:34 pm
by lee025
Hi - thanks, I can confirm that installing the new build has now resolved this issue for me and all appears to be up and running.

Thank you for all your assistance - very much appreciated.