Search found 6155 matches

by Alexander Riedel
Fri Jul 14, 2017 8:43 pm
Forum: PrimalScript
Topic: The older version of primalscript 2017 cannot be removed. Contact your technical support group.
Replies: 8
Views: 536

Re: The older version of primalscript 2017 cannot be removed. Contact your technical support group.

Run the installer like this:
PSR17Setup_7.3.104_070117_x64.exe /qn /L*V "Installer.log"

Look at the log file and see if you can discover something that holds it up. If not, please post it here.
by Alexander Riedel
Fri Jul 14, 2017 8:19 pm
Forum: PrimalScript
Topic: The older version of primalscript 2017 cannot be removed. Contact your technical support group.
Replies: 8
Views: 536

Re: The older version of primalscript 2017 cannot be removed. Contact your technical support group.

To be honest, I wouldn't really know. This is Windows Installer stuff. Only Microsoft would really know and the documentation is rudimentary. There are a few installer registry entries that normally tell Windows what is installed. The installfix tool removes those. Does the control panel show instal...
by Alexander Riedel
Fri Jul 14, 2017 4:48 pm
Forum: PrimalScript
Topic: The older version of primalscript 2017 cannot be removed. Contact your technical support group.
Replies: 8
Views: 536

Re: The older version of primalscript 2017 cannot be removed. Contact your technical support group.

It could be as simple as a lingering file lock. Try rebooting and uninstalling afterwards.
It also seems you have our installfix tool in your folder. Try removing it with that.
by Alexander Riedel
Tue Jul 11, 2017 2:08 pm
Forum: PowerShell Studio
Topic: Win32.exe flagged as virus
Replies: 3
Views: 83

Re: Win32.exe flagged as virus

Because these are new files, they have not been included in previous builds. So whatever your provider is, they have not seen those before.
by Alexander Riedel
Tue Jul 11, 2017 1:48 pm
Forum: PowerShell Studio
Topic: Cabinet file is corrupt and will not install
Replies: 3
Views: 75

Re: Cabinet file is corrupt and will not install

When the error about the cab file pops up, find t he location of the file, right click and select properties. Then select digital signatures. Click on the signature and press "Details" On each certificate or countersignature, click "View certificate" and select "Certification Path". Examine all sign...
by Alexander Riedel
Tue Jul 11, 2017 1:38 pm
Forum: PowerShell Studio
Topic: Win32.exe flagged as virus
Replies: 3
Views: 83

Re: Win32.exe flagged as virus

We cannot confirm that files on your system are ok. While we continuously scan our products and our installers, we cannot control what happens on your computer. While we have seen false positives with the packager engine templates before, your should always submit the files in question to your antiv...
by Alexander Riedel
Tue Jul 11, 2017 9:11 am
Forum: PowerShell Studio
Topic: Cabinet file is corrupt and will not install
Replies: 3
Views: 75

Re: Cabinet file is corrupt and will not install

The cabinet file is very likely not corrupt. The exact error message is probably the one that indicates an invalid signature. This is likely due to a missing root certificate on your system, Please make sure your system is fully updated. Unfortunately you just say "Windows" rather than the actual ve...
by Alexander Riedel
Tue Jul 11, 2017 8:33 am
Forum: PowerShell Studio
Topic: Executable will not run
Replies: 1
Views: 127

Re: Executable will not run

Depending on what you do in your script, the .config file is required for a .NET executable. If your packaged exe does not work without one, your will need it.
by Alexander Riedel
Tue Jul 11, 2017 8:28 am
Forum: PowerShell Studio
Topic: Decompile EXE
Replies: 3
Views: 115

Re: Decompile EXE

Please upload your file here: https://www.sapien.com/support/upload
We will look and and let you know what we can retrieve.
by Alexander Riedel
Tue Jul 11, 2017 8:24 am
Forum: Installation Issues
Topic: RESET POWERSHELLSTUDIO KEYS
Replies: 1
Views: 117

Re: RESET POWERSHELLSTUDIO KEYS

Sorry for the late reply here. It seems this was taken care of, yes?