Ending A Windows Installer Transaction Event Id 1042

2020. 3. 3. 06:42카테고리 없음

Hi @brunoqc!Thanks for reporting, and apologies for the slow response, I'm travelling with poor internet access.The error you're getting is a generic 'something went wrong'. Here are a few things to check:1. Is there a pending restart? For instance a Windows update that hasn't finalized yet, or some other software installation?2. How are you starting the installer? Commandline or gui?3. Windows 2003 was pre-UAC dialog, so I'm not sure how it would handle elevation.

Does the user you are starting as have enough permissions to install in the Program Files directory?It could also be related to some inconpatibility between the Windows Installer framework features we're using and what Windows 2003 provides. I'll need to do some research on that though, which will have to wait a few days until I'm home. @brunoqc Thanks! I found this in the logs:ExecFirewallExceptions: FirewallExtension: Cannot add firewall rule 'WMI Exporter (HTTP 9182)', which defines both an application and a port or protocol. Such a rule requires Microsoft Windows Vista or later.So, we're using too modern features, basically.

Are you having the firewall activated? If I recall correctly it was not on by default in those older versions. Maybe we should just skip installing the firewall rule for old versions? Alternatively we could have some installer flag for toggling it off.I've build a custom msi without the firewall rule, could you give it a shot and see if it works better?

So long story short according to coworkers years ago (server 2003 era) we could push apps with GPO then they updated to SRV 2008 and things broke. We now moved the PDC/ FSMO master to a 2016 server, the other 2 2008 box are still active.

To test the process of makign the MSI, etc I made a SRV 2016 VM and a win 10 PC VM toed into their own internal V switch on my PC. I was able to push notepad to the client.I then copied the working notpad MSI for that to a production share on a file server that has read share and read/execute NTFS rights for authenticated users and domain computers. I made a test OU put my PC in it, I am assigning the software to the computer through the GPO. I can't get notepadto show on my PC. I run gpupdate /force /target:computer I get thisgpupdate /force /target:computerUpdating policy.Computer Policy update has completed successfully.The following warnings were encountered during computer policy processing:The Group Policy Client Side Extension Software Installation was unable to apply one or more settings because the changes must be processed before system startup or user logon. The system will wait for Group Policy processing to finish completely before the next startup or logon for this user, and this may result in slow startup and boot performance.For more detailed information, review the event log or run GPRESULT /H GPReport.html from the command line to access information about Group Policy results.Certain Computer policies are enabled that can only run during startup.I check event log and I see these in this order from earliest to latest.Source: MSI installer, Event ID: 1040, Beginning a Windows Installer transaction: srv1deployNotepad.msi. Client Process Id: 9492.Source: restart manager, Event ID: 10,000 Starting session 0 - ‎2019‎-‎10‎-‎16T15:32300Z.Source: MSI installer, Event ID: 1042, Ending a Windows Installer transaction: srv1deployNotepad.msi.

1042

Client Process Id: 9492.Source: Restart manager, event id: 10,001, Ending session 0 started ‎2019‎-‎10‎-‎16T15:32300Z.To me this looks like should be working, AV does not seem to be blocking it, win firewall turned off on client PC still does not work. These don't look like errors to me so seems this should be working, but when I try to find notpad on the client it does not seem to be present like it never installed. Not sure what to make of this.Any idea??Thanks, -C. I had similar problems deploying via GPO. It ended up being an issue with using shortservernamesharefile.msiWhen I switched to using the Fully Qualified Domain Name (FQDN), GPO deployments now work 100%.See if it's that simple for you. Change deployment source to srv1.yourdomain.comdeployNotepad.msiThough, having said that, I would have expected to see a message in your logs saying something along the lines of it not being able to locate the MSI files, so this might be a wild goose chase. Helps to rule out anyway and using FQDN has other benefits in being more resilient especially if you ever need this to run over a VPN tunnel where servername may not actually resolve properly due to Split DNS.

I think we'll need more details. Can you generate resultant set of policy to see how that application deployment GPO has been setup? And a download location for the MSI you're using?

I'll be away until after the weekend but if nobody else has been able to help and resolve this, I won't mind trying to replicate your GPO setup on my end and see how it behaves. It could very well be the MSI file itself that isn't running unattended and may require a transform (MST) file created to go with it to specify options to make it run fully unattended in the background. I did this once in school for a class I pushed apps in a lab with a few VMs. I ended up using advanced installer to make the MSI as we needed like a handful of apps for that and none came in MSI. I just wanted something simple so I was trying notepad.

Ending A Windows Installer Transaction Event Id 1042 Key

Adobe, etc seemed like a real mess to push. I am kind of second guessing myself on the VM thing now too as it seems like if it works it is very sporadic, I tried making MSI again and called it NP that seems to push to the client as it shows in installed programs, but I can not find it anywhere else like you would normally go to launch it. I downloaded another program too called KASE I loaded that on my VM server to try and capture the install and make MSI that way that did not help either. The advanced installer I just find the EXE throw some switches at it /S for silent install and chose to use silent install and then make the MSI.