Installation: Problem in Session 0 error 1603

Use this forum to ask questions about installation or issues encountered while installing our software.
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
bgsapien
Posts: 5
Last visit: Tue Mar 02, 2021 11:11 pm

Installation: Problem in Session 0 error 1603

Post by bgsapien »

Product, version and build: PowerShell Studio 2017 v5.4.136
(*** Please do not write "latest" as a version, specify a version number ***)
32 or 64 bit version of product: 32
Operating system: Windows7 Enterprise
32 or 64 bit OS: 32

Hello again,
Thank you for your support to a License file.
Now, we're trying to implement it for an automated software deployment, but we aren't successful.
==>> Installation runs in session 0 !!!
We're using (psexec.exe -d -s -i 0 "cmd") from Sysinternals for testing software installation in session 0.

Unattended install Option1: SPS17Setup_5.4.136_022717_x86.exe /exenoui /L*v SPSInstall_1603.log /qn
returns error 1603
SPSInstall_1603.log
Install return code 1603
(655.9 KiB) Downloaded 124 times
Attended install to see "what's going on"
option2: SPS17Setup_5.4.136_022717_x86.exe /L*v SPSInstallGUI.log
returns an Security Warning: unknown publisher
Unknown Publisher popup during Installation in session 0
Unknown Publisher popup during Installation in session 0
UnknownPublisher.jpg (43.44 KiB) Viewed 2382 times

Log file content is collected to this step
SPSInstallGUI.log
Unknow Publisher
(203.61 KiB) Downloaded 123 times

Do we have a certificate issue Or what do you think ?

Regards AM

User avatar
davidc
Posts: 5913
Last visit: Mon Jul 08, 2019 8:55 am

Re: Installation: Problem in Session 0 error 1603

Post by davidc »

Sorry for the late reply. Sounds like you need to update your trusted root certificates on that particular machine. Otherwise you will the error you mentioned above. We find this often happens with machines that are offline.
David
SAPIEN Technologies, Inc.