Error 1812 Msiexec
Reading Mode exemgr log questions with package Author Message mbinetti Total Posts : 1087 Scores: 0 Reward points : 1750 Joined: 4/1/2005 Status: offline exemgr log questions with package Thursday, April 30, 2009 3:30 PM (permalink) 0 Execution Manager timer has been fired.execmgr4/30/2009 2:24:38 PM3520 (0x0DC0) Executing program msiexec.exe /q ALLUSERS=2 /m MSISN9AB /i "ViewMail.MSI" in Admin contextexecmgr4/30/2009 2:24:38 PM120 (0x0078) Execution Request for package SCH00008 program Per-system unattended state change from WaitingContent to NotifyExecutionexecmgr4/30/2009 2:24:38 PM120 (0x0078) Checking content location \\OPS-SMS01.xxx.dom\SMSPKGD$\SCH00008\ for useexecmgr4/30/2009 2:24:39 PM120 (0x0078) IsNetResourceAccessible failed with error code 0x00000005execmgr4/30/2009 2:24:39 PM120 (0x0078) Rolling over to network access account to check content locationexecmgr4/30/2009 2:24:39 PM120 (0x0078) Successfully selected content location \\OPS-SMS01.xxx.dom\SMSPKGD$\SCH00008execmgr4/30/2009 2:24:39 PM120 (0x0078) GetFileVersionInfoSize failed for file \\OPS-SMS01.xxx.dom\SMSPKGD$\SCH00008\msiexec.exe, error 1812execmgr4/30/2009 2:24:39 PM120 (0x0078) Executing program as a MSI scriptexecmgr4/30/2009 2:24:39 PM120 (0x0078) Valid MSI Package path = \\OPS-SMS01.xxx.dom\SMSPKGD$\SCH00008\ViewMail.MSIexecmgr4/30/2009 2:24:39 PM120 (0x0078) Found executable file msiexec.exe with complete path C:\WINDOWS\system32\msiexec.exeexecmgr4/30/2009 2:24:39 PM120 (0x0078) Successfully prepared command line "C:\WINDOWS\system32\msiexec.exe" /q ALLUSERS=2 /m MSISN9AB /i "ViewMail.MSI"execmgr4/30/2009 2:24:39 PM120 (0x0078) Current MSI script is an installation scriptexecmgr4/30/2009 2:24:39 PM120 (0x0078) can someone explain this to me Checking content location \\OPS-SMS01.xxx.dom\SMSPKGD$\SCH00008\ for useexecmgr4/30/2009 2:24:39 PM120 (0x0078) but then it says IsNetResourceAccessible failed with error code 0x00000005execmgr4/30/2009 2:24:39 PM120 (0x0078) then Rolling over to network access account to check content locationexecmgr4/30/2009 2:24:39 PM120 (0x0078) Successfully selected content location \\OPS-SMS01.xxx.dom\SMSPKGD$\SCH00008execmgr4/30/2009 2:24:39 PM120 (0x0078) it was successful but then i get GetFileVersionInfoSize failed for file \\OPS-SMS01.xxx.dom\SMSPKGD$\SCH00008\msiexec.exe, error 1812execmgr4/30/2009 2:24:39 PM120 (0x0078) error 1812 says The specified image file did not contain a resource section. Source: Windows if it did not then how did it find it here ---> Successfully selected content location \\OPS-SMS01.xxx.dom\SMSPKGD$
→ Deploy software, applications and drivers Javascript Disabled Detected You currently have javascript disabled. Several functions may not work. Please re-enable javascript to access full functionality. We use cookies to let you log in, for ads and for analytics. OK Advertisement fails Started by Tom5674 , Apr 27 2009 09:20 AM Please log in to reply 3 replies to this topic #1 Tom5674 Tom5674 Advanced Member Established Members 32 posts Location:Indianapolis, IN Posted 27 April 2009 - 09:20 AM Messages are Program http://www.myitforum.com/forums/exemgr-log-questions-with-package-m199690.aspx received and then Failed (bad environment). Example is installing Excel viewer from a network server, with out user intervention. The Exemgr.log shows that it can't find the xviewer.msi, the advert has the complete path to the folder on the network. Back to top #2 wmmayms wmmayms MCITP Established Members 325 posts Gender:Male Location:Sweden Interests:Soccer, Computers Posted 27 April https://www.windows-noob.com/forums/topic/845-advertisement-fails/ 2009 - 09:28 AM Canīt fully understand how you mean. but if ou get a (bad environment) failure when trying to distrubute a prgm i would suggest to look a the below tab on your program: if this dosent solve the problem please attach your execmgr.log and the cas.log from the computer who is having problems. MCITP: Deployment, MCTS: SCCM, Active Directory, Vista, Windows 7, Deployment, Office 2010LinkedInTwitter Back to top #3 Tom5674 Tom5674 Advanced Member Established Members 32 posts Location:Indianapolis, IN Posted 27 April 2009 - 09:40 AM Canīt fully understand how you mean. but if ou get a (bad environment) failure when trying to distrubute a prgm i would suggest to look a the below tab on your program: if this dosent solve the problem please attach your execmgr.log and the cas.log from the computer who is having problems.Computers are XP SP3. I have selected the correct platform and choose 20M. I have attached the log from one of the computers.I think I may have an issue with rights
I like to write so have a look at some of my work. Please feel free to leave a comment... Pages SCCM 2007 Thursday, 21 June 2012 Task Sequence Fails Error 0x80040104 http://docnorton.blogspot.com/2012_06_01_archive.html More fun and games with OSD Task Sequences - this time in the form of https://community.spiceworks.com/how_to/1812-deploy-msi-files-using-psexec error 0x80040104. The error as it was displayed on the clients screen was: This task sequence cannot be run because a package referenced by the task sequence could not be found. For more information, please contact your system administrator or helpdesk operator. This happened immediately after selecting the task sequence and processing the dependencies. Upon viewing the SMSTS.log we spotted the error 1812 error Failed to resolve selected task sequence dependencies. Code(0x80040104) The only change made to the TS since yesterday was a new driver package for the Lenovo X220T tablets. The reference to a missing package reminded me of a post I made once in reference to drivers and driver packages - that if you leave the distribution point on Source version 1 it will just bomb out. Refreshing the DP didn't help so went via "Manage" error 1812 msiexec and created a new source version. As if by magic..... It worked! SMSTS.log Posted by Doc Norton No comments: Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest Labels: 0x80040104, driver, error, Failed to resolve selected task sequence dependencies, OSD, package, SCCM, ts Wednesday, 20 June 2012 It's all quiet.. Not many people leaving comments here - be great to hear if any posts have helped you :) Posted by Doc Norton No comments: Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest verifying content availability for package optional program * I have a task sequence setup for quick deployment of corporate apps to machines that haven't yet got complete driver packages and get a vanilla install of Windows 7 x64 deployed. This TS was recently failing when run from "Run Advertised Programs" with the error: verifying content availability for package optional program * It turned out my Java Package didn't have program selected due to the it being disabled from the actual packages program its self. I've highlighted it below. If you do get the error it's worth checking your TS programs - unfortunately SCCM doesn't always give the most comprehensive of error messages - I hope this helps someone else. Posted by Doc Norton No comments: Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest Labels: error, fail, package, program, SCCM, task sequence, verifying content availa
PSExec http://technet.microsoft.com/en-us/sysinternals/bb897553 2 Setup a share for PSExec I always setup a share on my machine called C:\Installs or something of that sort and give it read-only permissions to Authenticated Users and give SYSTEM read-only. I place the PSExec.exe file in there. 3 Create list of computers to push the install to In the C:\Installs, I create a list of computers in a simple notepad text file. I name the file C:\Installs\SoftwareInstall.txt Ex: System01 System02 System03 4 Create a shared location on a server to house to .msi file \\Serverxx\installs\softwareinstall\ I give Authenticated Users & the SYSTEM account read-only under Security. 5 Place the .msi file(s) into the server's shared folder Make sure you have all of the required files and dependencies for the install in this folder or it could fail. 6 Create a batch to push the install out with Here's where everything becomes important, you may have been wondering why I suggested giving the SYSTEM account access and that is so you don't compromise any admin logins anywhere. The -s in the batch file is for the system account to login and do the install. To create the batch, open up notepad and have the locations of the files ready to copy and paste. "Location of the Psexec.exe file" @"Location of list file" -s msiexec.exe /i "\\Serverxx\installs\softwareinstall\firefox.msi" \q pause I save the batch file as C:\Installs\SoftwareInstallBatch.bat 7 Example of batch I use "C:\Installs\PsExec.exe" @C:\Installs\SoftwareInstall.txt -s msiexec.exe /i "\\Serverxx\installs\softwareinstall\firefox.msi" /q pause -s is used for the system account msiexec.exe /i is used to install msi files /q is the quiet switch with no user interaction Conclusion Common Q & A: Everything is shared for the SYSTEM account to access the files but this keeps security to a max by not compromising any admin logins and also doesn't rely on permissions so much to do the job. Windows Vista/7/Server 2008 users, you will have to "Run as Administrator" The /q switch is used so the end-user doesn't see anything on their screen when installs are being made. 38 Comments Datil GerardMainardi Jan 18, 2011 at 09:32am Nice use of PSExec! Mace Alex3031 Jan 18, 2011 at 10:28am Nice How-To, thanks Thai Pepper Emerson Leal Jan 18, 2011 at 12:23pm Very good job, congrats! Datil Gearhead89 Jan 18, 2011 at 01:21pm Thanks everyone, I hope you enjo