MSI 1603 Error when installing latest package
MSI 1603 Error when installing latest package
#1
Posted 24 Sep 2015
#2
Posted 25 Sep 2015
Kate Dulko
Customer Relations
The Welkin Suite
twitter: @KateDulko
skype id: d_katerina
e-mail: kate.dulko@welkinsuite.com
#3
Posted 26 Sep 2015
Hi Irvin,
Can I please ask you to check the file with the given path %temp%\TWS_Installation.txt and attach it to the message in the forum? In case if file does not exist - please retry installation and file should appear.
This will help us to understand what exactly went wrong.
Thanks,
Vladimir
Vladimir Gubanovich
Head of Product
The Welkin Suite
skype id: vladimir.gubanovich
e-mail: vladimir.gubanovich@welkinsuite.com
#4
Posted 01 Oct 2015
[attachment=34:TWS_Installation.txt]Note that I have attempted to Run as Adminstrator as well.
Filename: TheWelkinSuiteSetup-0.22.14.4.exe
File is not blocked.
#5
Posted 02 Oct 2015
Hi Irvin,
Thank you for your answer and the attached log file.
Let’s look at the details.
The error about the lack of privileges to start The Welkin Suite Auto-Updater service is present in the log. The installation cannot be finished due to this.
Can I please ask you to run the ‘TheWelkinSuiteAutoUpdater’ service manually? You should go to the Control Panel -> Administrative Tools -> Services or launch Task Manager / Services, find ‘TheWelkinSuiteAutoUpdater’ service, and right click on it, ‘Start service’.
Probably the service will be started and you will be able to use The Welkin Suite.
If the result is negative, please send us the log file as you did previously of the Auto-Updater service (C:\Program Files (x86)\The Welkin Suite\The Welkin Suite\UpdaterService\log.txt).
I will wait for your answer and hope it is positive.
Thank you,
Kate
Kate Dulko
Customer Relations
The Welkin Suite
twitter: @KateDulko
skype id: d_katerina
e-mail: kate.dulko@welkinsuite.com
#6
Posted 23 Dec 2015
Hi, I don't think that I ever followed up with you. My apologies. To be clear, I was only getting that error on one machine. The installation worked fine on other machines. It has been a while, but I believe that the issue was related to the PATH environment variable exceeding the MAX PATH length for Windows 7. I cleaned up the env variable and later upgraded to Windows 10. Issue was resolved. Hope this helps others. Cheers.
#7
Posted 24 Dec 2015
Hi Irvin.
Thank you for your reply.
We will consider your comment related to the cause of the issue.
This case will be solved by our team.
Regards,
Kate
Kate Dulko
Customer Relations
The Welkin Suite
twitter: @KateDulko
skype id: d_katerina
e-mail: kate.dulko@welkinsuite.com