Failed To Advertise Product Error Code 1624
Contents |
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) Home2012Previous VersionsLibraryForumsGallery Ask a question Quick access Forums home Browse
Unmatched Exit Code (1603) Is Considered An Execution Failure
forums users FAQ Search related threads Remove From error applying transforms. verify that the specified transform paths are valid. My Forums Answered by: Failed to advertise product, error code 2 System exit code 2 Center Configuration Manager > Configuration Manager 2007 General Question 0 Sign in to vote When I try to deploy
Windows Installer Cleanup Utility
a Quickbooks package I get the following in my log file. I have the package set to run as administrator and have the computer included in my boundary. Thanks for any help! Successfully prepared Command Line "C:\WINDOWS\System32\msiexec.exe" /i "\\server\APPS\DISTRIBUTION\SCCM\SMSPKG\NTC0001B\QuickBooks.msi" TRANSFORMS=Quickbooks.mst
Orca
/qn execmgr 5/14/2009 6:48:37 PM 3768 (0x0EB8) Advertising MSI package \\server\APPS\DISTRIBUTION\SCCM\SMSPKG\NTC0001B\QuickBooks.msi to user execmgr 5/14/2009 6:48:37 PM 3768 (0x0EB8) Failed to advertise product, error code 2 execmgr 5/14/2009 6:48:38 PM 3768 (0x0EB8) Lowright users might fail to install this application if it requires higher privileges execmgr 5/14/2009 6:48:38 PM 3768 (0x0EB8) Command line = "C:\WINDOWS\System32\msiexec.exe" /i "\\server\APPS\DISTRIBUTION\SCCM\SMSPKG\NTC0001B\QuickBooks.msi" TRANSFORMS=Quickbooks.mst /qn, Working Directory = \\server\APPS\DISTRIBUTION\SCCM\SMSPKG\NTC0001B\ execmgr 5/14/2009 6:48:38 PM 3768 (0x0EB8) Created Process for the passed command line execmgr 5/14/2009 6:48:38 PM 3768 (0x0EB8) Raising event: [SMS_CodePage(437), SMS_LocaleID(1033)] instance of SoftDistNonElevatedInstall { AdvertisementId = "NTC20026"; ClientID = "GUID:DB665CFA-A85D-4D83-855B-EF9A3D0DE45E"; DateTime = "20090514234838.757000+000"; MachineName = "A165-46189"; PackageName = "NTC0001B"; ProcessID = 1784; Pr
helpful is this to you? Average Rating 5 98417 views 07/26/2006 Windows Installer (MSI) Windows Installer (MSI) Error Messages Troubleshooting appdeploy-faqs Microsoft Windows Installer The errors returned by the Windows Installer service are unique to MSI setups, each one providing some level of help to specify a problem, check each below for details. Answer Summary: This open question is a holding place for the answer below which provides links to a page detailing each of the internal errors https://social.technet.microsoft.com/Forums/systemcenter/en-US/abec3707-a8e8-4c80-a156-62d20379ac16/failed-to-advertise-product-error-code-2?forum=configmgrgeneral you may encounter when working with Windows Installer. TextThis open question is a holding place for the answer below which provides links to a page detailing each of the internal errors you may encounter when working with Windows Installer.Save summary Cancel 0 Comments [ + ] Show Comments Comments This content is currently hidden from public http://www.itninja.com/question/what-does-this-msi-error-mean view. Reason: Member has been banned from the site For more information, visit our FAQ's. This content is currently hidden from public view. Reason: Member has been banned from the site For more information, visit our FAQ's. This content is currently hidden from public view. Reason: Member has been banned from the site For more information, visit our FAQ's. 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 7 -2147287038: %1 could not be found. 13: The data is invalid. 120: This function is not available for this platform. It is only availabl... 258: The wait operation timed out. 1101: Could not open file stream: [2]. System error: [3] 1155: File [1] not found 1259: This error code only occurs when using Windows Installer version 2.0... 1301: Cannot create the file '[2]'. A directory with this name already exis... 1302: Please insert the disk: [2] 1303: The Installer has insufficient privileges to access thi
with Error Code 1603 in Execmgr.log May 20, 2010 by rbalsley 3 Comments Error code 1603 by definition is just a generic windows installer (MSIexec) fatal error code. Yesterday I was seeing this for a software package deployment. The interesting part of this was this was an application http://richardbalsley.com/sccm-software-distribution-fails-with-error-code-1603-in-execmgr-log that was packaged for us by a third party vendor (a vendor that will remain nameless, but has created some poor packages for us in the past that allows me to write up blog posts like this explaining the solution to https://support.symantec.com/en_US/article.HOWTO3085.html their packaging issues), and the application was actually installing on some machines but not all. In total, about 50% had successfully installed the application and the other 50% had failed. So it was a very peculiar push that piqued my interest. exit code After looking at the advertisement report, I noticed that most of the successful installs were from Windows 7 machines. The failures were coming from Windows XP. So that pointed me to setup a test XP machine and test the push on that platform. Next I looked at the package and how it was created in SCCM (I personally didn't set this up or work with the vendor on packaging it, so this was all new to me). I noticed that the install program failed to advertise was using a transform that the vendor had created as well as a requiring ISScript8 be run first before installing. After doing some research, I came across a forum post that made reference to DCOM InstallShield InstallDriver Identity properties being set incorrectly. In my case, we were running this application with administrative rights and silently via SCCM. When a local administrator was logged on during runtime, the application would install fine. It would also install fine if no one was logged on. However if a user was logged on without admin rights, we'd get the 1603 error. So I took a look at the InstallShield InstallDriver Properties from DCOMCNFG. To do this, follow the following steps: From a command line (or start - run) type in dcomcnfg Select Component Services Expand Computers Expand My Computer Expand DCOM Config Right click on InstallShield InstallDriver (in my case I had two of these) Select Properties Select the Identity tab What SHOULD be selected here is The launching User. What I had selected was The interactive user. So by changing both InstallShield InstallDriver identities to The Launching User I was able to run the application successfully as the user which was a low rights account. How to change the Installshield Installdriver Identity via VBScript So I had the problem solved, but I needed a way to do this programatically. I basically needed to run ISScript first, then run a VBScript to change the Identity value, then run the
PKI Service Identity Access Manager Shop Online Cyber Security Services Managed Security Services DeepSight Intelligence Incident Response Security Simulation Website Security SSL Certificates Complete Website Security Code Signing Certificates Norton Shopping Guarantee Buy SSL Products A-Z Services Services Home Business Critical Services Consulting Services Customer Success Services Cyber Security Services Education Services Solutions Solutions Home Topics Encryption Everywhere Internet of Things Next Generation Endpoint Office 365 Industries Automotive Cyber Insurance Education Financial Services Global Service Providers Industrial Control Systems Healthcare Retail Government Federal Government State & Local Support Center Technical Support Symantec Connect Buying Programs Upgrades Maintenance & Renewals Training Security Center Security Center Home Blogs ISTR Threats Virus Definitions and Security Updates Removal Tools Partner Find a Partner Become a Partner Login Required Login into Partner Portal Partner Licensing Partner Renewals Partner Training Margin Builder Opportunity Registration Financial Benefits English 中文(简体) 中文(繁體) Česká English Français Deutsch Magyar Italiano 日本語 한국어 Polski Português Pусский Español Site: Symantec Enterprise Small Business Norton United States Search Support Home Support Home MySymantec Licensing Products A-Z SYM16-015 Security Advisory Login Profile Subscriptions Logout Login Forgot Password? Don't have a SymAccount? Create a SymAccount now!' What do the various MSI Error codes mean? HOWTO3085 April 4th, 2006 http://www.symantec.com/docs/HOWTO3085 Support / What do the various MSI Error codes mean? Did this article resolve your issue? Thank you for your feedback! Provide feedback on this article Request Assistance Print Article Subscribe to this Article Manage your Subscriptions Search Again Description Question If we execute an MSI and receive errors, is there any way to know what these mean? AnswerThis was pulled from a Mi