rodpatt How helpful is this to you? It can look something like this: MSI (c) (B8:50) [12:43:49:297]: MainEngineThread is returning 1601 Number Description Error Code 0 Completed Successfully. ERROR_SUCCESS_REBOOT_INITIATEDd 1642 The installer cannot install the upgrade patch because the program being upgraded may be missing or the upgrade patch updates a different version of the program. Contact your support personnel. http://bsnux.com/altiris-deployment/altiris-deployment-server-error-1619.html
Verify that the patch package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer patch package. msiexec /i software.msi -quiet The command works fine when I run it manually. Will you please check your event log to see if there are any errors (file copy errors, etc.) that we may have missed? 0 Mike Robertson July 02, 2013 17:33 0 Does event viewer show anything detailed? https://support.symantec.com/en_US/article.TECH19553.html
ERROR_INSTALL_LOG_FAILURE 1623 This language of this installation package is not supported by your system. Please choose one of the packages that uses an MSI and follow these steps. Sign up!
The copy process checks for the file existance and should copy the file to the verified location. ERROR_PRODUCT_VERSION 1639 Invalid command line argument. This is not the first time this has happened to me trying to deploy apps with SMS. Altiris Deployment Solution Download ERROR_INVALID_PARAMETER 120 This function is only available for Win 2000 and Windows XP with Windows Installer v2.0.
Verify that the program to be upgraded exists on your computer and that you have the correct upgrade patch. Altiris Deployment Solution Alternative Related Links MIF Tutorial The Basics of MIF Files System Center 2012 Configuration Manager Trial Systems Management Server (SMS) Home Page Systems Management Server (SMS) Product FAQ Systems Management Server (SMS) Newer Than: Search this thread only Search this forum only Display results as threads Useful Searches Recent Threads More... Now its just the question why does it happen, but that one has to be answered by AA team. 0 Adam Ruth July 05, 2013 14:00 Apologies for coming late to
Is there a simple switch im missing? 0 Comments [ + ] Show Comments Comments Please log in to comment Answers 1 1619 is kind of a generic error Altiris Deployment Agent Then it goes trough all paths from PATH variable and tries to locate the installation package. C:\Windows\PDQDeployRunner\1 folder when the deployment is running and check the debux.txt What I could not ERROR_UNKNOWN_FEATURE 1607 Component ID not registered. This error code is available with Windows Installer versions 2.0 or later.
See if an error is returned that way too. http://www.myitforum.com/forums/Error-1619-m163123.aspx United States Products Threat Protection Information Protection Cyber Security Services Website Security Small Business CustomerOne Products A-Z Services Business Critical Services Consulting Services Customer Success Services Cyber Security Services Education Services Altiris Deployment Solution 7.1 Training Legal | Feedback c926729 Tue September 6 19:00:00 EDT 2016"www.itninja.com msi errors .com Software Packaging Tips and Tricks Menu Skip to content HomeAboutDownloadsGoogle Chrome Search Knowledge baseMSI Windows Installer Altiris Deployment Solution 7.1 User Guide ERROR_CALL_NOT_IMPLEMENTED 1259 This error code only occurs when using Windows Installer version 2.0 and Windows XP or later.
I have tried putting it in the task sequence as well as "Run Advertised Programs" and it fails both ways. check my blog I too prefer this guideline. I've gone over it several times and can't find any settings that are wrong. If so, is the Package Data Source tab checked to contain source files, and have a UNC in the Source directory? Altiris Deployment Solution 7.5 Installation Guide
I am wondering... Contact your application vendor. ERROR_UNKNOWN_PRODUCT 1606 Feature ID not registered. this content ERROR_INSTALL_PACKAGE_OPEN_FAILED 1620 This installation package could not be opened.
Please create and share a test folder. Altiris Deployment Solution 6.9 Sp6 Windows Logo Testing warning on XP Deploying Acrobat 6.01 with GPO using MSIEXEC switches Repackaging Software that requires a Unique Serial Number Application & Content Deployment Tool MYOB14 (Ver 2004) Error ERROR_INSTALL_UI_FAILURE 1622 Error opening installation log file.
Cause The Windows Installer returns error code1619 when the installation package could not be opened. ERROR_PATCH_PACKAGE_OPEN_FAILED 1636 This patch package could not be opened. The events from the debug log should be stored in the event log. 0 SelfMan July 02, 2013 21:53 Do the trace again and create a filter by path containg the Altiris Deployment Solution 6.9 End Of Life If SMS cannot find or correlate any installation status Management Information Format (MIF) files for the program, it uses the program's exit code to determine status.
It seems the reason it works when running manually is that it gets extracted to the users AppData folder, which doesn't change based on 32/64bit. If its a vendor app the setup.exe could be extracting an MSI to a temp location and then SCCM service account doesn't have access. MySymantec Create and manage cases, manage licensing and renewals, submit threats, and enroll with Symantec Rewards. http://bsnux.com/altiris-deployment/altiris-deployment-error-255.html If you're uninstalling "11" and you had 9, then that's what you'll obtain.
ERROR_PRODUCT_UNINSTALLED 1615 SQL query syntax invalid or unsupported. A few remote possibilities stand out, but none of them seem very likely. Additional logging details about the environment on the system would give us a better understanding of what's going Windows Vista/Seven C:\Users\\AppData\LocalLow\Sun\Java\jre1.6.0_20\jre1.6.0_20.msi Windows XP C:\Documents and Settings\\Local Settings\ApplicationData\Sun\Java\ jre1.6.0_20\jre1.6.0_20.msi 3. ERROR_APPHELP_BLOCK 1601 The Windows Installer service could not be accessed.
ERROR_INSTALL_REMOTE_DISALLOWEDd 1641 The installer has started a reboot. use the cmd line similar to the below. ERROR_UNSUPPORTED_TYPE 1631 The Windows Installer service failed to start. this would put the package in c:\temp and run it from there.
ERROR_INVALID_FIELD 1618 Another installation is already in progress. Contact your support personel to verify that the Service is properly registered. Installation of this version cannot continue. Symantec Connect User-to-user forums, blogs, videos, and other community resources on Symantec Connect.
Consult the Windows Installer SDK for detailed command line help. Created: 22 Jan 2009 • Updated: 22 Jan 2009 | 2 comments Language TranslationsMachine TranslationsDeutsch Français Español 简体中文 日本語 MaggieH +3 3 Votes Login to vote Tweet This is a summary