error 1603
Hello community!
Ok, I have an issue in which I reviewed with my fellow packaging colleagues as well as looking on google for a resolution, but nothing seems to be applicable in this case.
So here's the story:
I'm installing a software (Vendor MSI), in which I pass it a 1033.mst, a generic mst and a MST for the application made with a few changes. When I install it from my Test folder on the server, it works perfectly. If I copy the files in my production folder, I get a very annoying 1603 exit code. Some of my clleagues suggested I have a look at NTFS permissions on the 2 folders on the server: both are the same. So that's not my issue.
I have also read through the log file, and there may be something interesting with a Return Value 3, here are a few lines before that:
In my package, there doesn't seem to be a an action named getInstallationCode. I get the same issue when I run only the MSI, so my MST's aren't at fault either.
Do you guys know or see anything I could be missing here?
Thanks!
Stephane
Ok, I have an issue in which I reviewed with my fellow packaging colleagues as well as looking on google for a resolution, but nothing seems to be applicable in this case.
So here's the story:
I'm installing a software (Vendor MSI), in which I pass it a 1033.mst, a generic mst and a MST for the application made with a few changes. When I install it from my Test folder on the server, it works perfectly. If I copy the files in my production folder, I get a very annoying 1603 exit code. Some of my clleagues suggested I have a look at NTFS permissions on the 2 folders on the server: both are the same. So that's not my issue.
I have also read through the log file, and there may be something interesting with a Return Value 3, here are a few lines before that:
MSI (s) (2C:94) [15:27:06:215]: Doing action: getInstallationCode
Action ended 15:27:06: PDFInfo. Return value 1.
MSI (s) (2C:94) [15:27:06:215]: Transforming table CustomAction.
MSI (s) (2C:94) [15:27:06:215]: Note: 1: 2262 2: CustomAction 3: -2147287038
MSI (s) (2C:94) [15:27:06:215]: Transforming table CustomAction.
MSI (s) (2C:94) [15:27:06:215]: Transforming table CustomAction.
MSI (s) (2C:94) [15:27:06:215]: Transforming table Binary.
MSI (s) (2C:94) [15:27:06:215]: Note: 1: 2262 2: Binary 3: -2147287038
MSI (s) (2C:94) [15:27:06:215]: Transforming table Binary.
MSI (s) (2C:94) [15:27:06:215]: Transforming table Binary.
MSI (s) (2C:94) [15:27:06:215]: Note: 1: 2262 2: Binary 3: -2147287038
MSI (s) (2C:B4) [15:27:06:231]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI2F.tmp, Entrypoint: IsValidKeyCode
Action start 15:27:06: getInstallationCode.
MSI (s) (2C:94) [15:27:06:387]: Transforming table InstallExecuteSequence.
MSI (s) (2C:94) [15:27:06:387]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (2C:94) [15:27:06:387]: Transforming table InstallExecuteSequence.
MSI (s) (2C:94) [15:27:06:387]: Transforming table InstallExecuteSequence.
Action ended 15:27:06: getInstallationCode. Return value 3.
Action ended 15:27:06: INSTALL. Return value 3.
In my package, there doesn't seem to be a an action named getInstallationCode. I get the same issue when I run only the MSI, so my MST's aren't at fault either.
Do you guys know or see anything I could be missing here?
Thanks!
Stephane
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
Jamie B
15 years ago
Are you running the install direct from the server or through some kind of deployment tool?
Is the path length significantly different between your test and production folders?
Whats the application in question?
I'd compare the differences between a verbose log of a working and non working install. Alternatively post (or host and link) them here.
Is the path length significantly different between your test and production folders?
Whats the application in question?
I'd compare the differences between a verbose log of a working and non working install. Alternatively post (or host and link) them here.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.