Hello,
I'm trying to package an Information Mapping FormattingSolutionsPro 4.0 EXE. The EXE has 3 embedded MSI files. When I am logged into the PC, I can install the MSI files without a problem. However, when use the dos AT command to schedule the MSIs to install using the Local System Account while I am logged off the PC, the MSIs don't install properly.

They seem to start the install, but then just don't seem to finish. I would expect them to either run completely, or not run at all. But it seems to do something kind of in between.

I'll post a snippit of the log files that shows the results of being installed while logged in and being installed while logged out. I'm looking for any theories as to why this is acting like this.

Snippit of log file when logged into the PC:

Property(S): SourcedirProduct = {09959E11-AD5D-408E-96AF-E3346954D6B8}
Property(S): ProductToBeRegistered = 1
MSI (s) (2C:F4) [23:58:41:607]: Note: 1: 1707
MSI (s) (2C:F4) [23:58:41:607]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (2C:F4) [23:58:41:607]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (2C:F4) [23:58:41:607]: Product: Shared Add-in Extensibility Update for Microsoft .NET Framework 2.0 (KB908002) -- Installation completed successfully.

MSI (s) (2C:F4) [23:58:41:607]: Cleaning up uninstalled install packages, if any exist
MSI (s) (2C:F4) [23:58:41:607]: MainEngineThread is returning 0
----------------------------------------------------------------------
Snippit of log file when not logged into PC:

Property(S): SourcedirProduct = {09959E11-AD5D-408E-96AF-E3346954D6B8}
Property(S): ProductToBeRegistered = 1
MSI (s) (F4:48) [23:38:09:662]: Cleaning up uninstalled install packages, if any exist
MSI (s) (F4:48) [23:38:09:662]: MainEngineThread is returning 0

You'll see that 4 lines of logging are simply missing when I run it while logged off the PC. Any theories as to why?
Thanks.
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Additional note: This MSI is created as Per-User install. So on my command line I set the Public Property ALLUSERS=1
Thanks.
Answered 02/18/2010 by: troy_in_wi
Orange Belt

Please log in to comment
0
A verbose log (/l*v %temp%\somenameorother.log) will show you much more information. Compare the two logs first and the failure should stand out.
Answered 02/18/2010 by: VBScab
Red Belt

Please log in to comment
0
This might be what happens when an MSI is "Advertised But Not Installed" instead of "Installed" depending on the ProductState. When the MSI was installed with nobody logged in, the verbose log showed ProductState=1 and when it was installed with someone logged in, the verbose log showed ProductState=2.

By looking at the log, it also appears that it recognized my command line ALLUSERS=1 and then it simply disregarded it and deleted that propterty.
Answered 02/18/2010 by: troy_in_wi
Orange Belt

Please log in to comment
0
Now, sometimes the ProductState of that MSI is 5 which is to install for Current User. This gets installd when the PC is logged off so the Current User is "LocalService". Why does my ProductState for installing this MSI change from 1 to 2 to 5?
Maybe a Transform would help, unless it just disregards my setting like it did for my ALLUSERS=1 setting.
Answered 02/19/2010 by: troy_in_wi
Orange Belt

Please log in to comment
Answer this question or Comment on this question for clarity