Home > Windows Installer > 1639 Invalid Command Line Argument

1639 Invalid Command Line Argument

Contents

This tool goes much deeper than a normal uninstall does and usually cures the problem.You can download it here.http://support.microsoft.com/kb/290301/en-usI hope this resolves your issue.Thank you for visiting Just Answer Ask Your I've attached the log file in case anyone would be so kind as to have a look. Close Sign In Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions Problem Installation of Backup Exec (BE) fails when the ID used to install has a Quote Reply With Quote 12-07-2010,01:50 PM #3 Mescalero View Profile View Forum Posts Super User (100+ Posts) Join Date Aug 2006 Posts 108 Thanks for that response. http://caterace.com/windows-installer/1639-invalid-command-line-argument-windows-xp.html

Still have questions? i tried that but it said to me that i dont need the update cause i already have the service pack with a newer one,if it could be able to install Close Login Didn't find the article you were looking for? Consult the Windows Installer SDK for detailed command line help.We've tried de-installing Peachtree and then re-installing it but it won't let us finish an installation, this error appears. https://support.threattracksecurity.com/support/solutions/articles/1000070819-msi-error-1639-invalid-command-line-argument-during-installation

Invalid Command Line Argument Windows Installer Sdk

Check out the community or submit a support ticket. installation menu will reappear. Please try the request again. Colin Vincent is online now Please help me out!

When I click OK, I get: error: command failed: 'msiexec' (Status: exit code: 1639) Using SysInternals procexp to find the cmd line args: msiexec /a "D:\Program Files\.multirust\tmp\u1q7cfw7ur9ke261_file.msi" /qn "TARGETDIR=D:\Program Files\.multirust\tmp\xr8xy3cg51_lssog_dir" (Btw, See the document How to back up the Windows registry before proceeding. Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? Error 1639 Dism CALL US: 1 (866) 837-4827 Solutions Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Government Products Backup and Recovery Business Continuity Storage Management Information Governance Products A-Z Services Education Services Business Critical

Skipping post install actions for BE. The return value for Symantec Backup Exec returned error code: 1639 Cause The ID used to install BE has a password with a Quote in it. Page 1 of 2 12 Last Jump to page: Results 1 to 5 of 6 Thread: Error: -1639 Invalid command line argument Thread Tools Show Printable Version Subscribe to this Thread… Consult the Windows Installer SDK for detailed command line help. 7/BS" The return code from the MSI is: 1639 Install was NOT successful. https://groups.google.com/d/topic/microsoft.public.platformsdk.sdk_install/sdT2VlBmlDs SHOW ME NOW © CBS Interactive Inc.  /  All Rights Reserved.

Generated Thu, 17 Nov 2016 14:35:39 GMT by s_wx1196 (squid/3.5.20) To use Google Groups Discussions, please enable JavaScript in your browser settings, and then refresh this page. . Command Prompt Error 1639 If the value is set to 1, then the NTFS file system will no longer make a second directory entry of the 8.3 standard for each file that has a long Terms of use for this information are found in Legal Notices.

Related Articles Article Languages x Translated Content Please note that this document is a translation from English, and may Please use the previous link instead.

Windows Installer Returned 1639

Here's where you can get it The tiny $60 Nintendo entertainment system is currently sold out in most places, but you still may able to snag one...eventually. https://community.flexerasoftware.com/showthread.php?195901-Error-1639-Invalid-command-line-argument Last edited by Mescalero; 12-14-2010 at 04:00 PM. Invalid Command Line Argument Windows Installer Sdk Reload to refresh your session. Error 1639 Peachtree 2010 Please refer to our CNET Forums policies for details.

Credentials confirmed by a Fortune 500 verification firm. this contact form Login|Contact Us Computer For Online Computer Support, Ask a Computer Technician Not a Computer Question? It is possible that updates have been made to the original version after this document was translated and published. Facebook Twitter Google+ YouTube LinkedIn Tumblr Pinterest Newsletters RSS Error 1639 Windows Installer Sdk Peachtree

Modify only the keys specified. Terms and Conditions Privacy Policy Powered by vBulletin Version 4.2.2 Copyright © 2016 vBulletin Solutions, Inc. All rights reserved. have a peek here Get a Professional Answer Via email, text message, or notification as you wait on our site.Ask follow up questions if you need to. 100% Satisfaction Guarantee Rate the answer you receive.

If you believe this post is offensive or violates the CNET Forums' Usage policies, you can report it below (this will not automatically remove the post). Error Code 1639 Sql Server 2012 Also please exercise your best judgment when posting in the forums--revealing personal information such as your e-mail address, telephone number, and address is not recommended. Thank you for helping us maintain CNET's great community.

Invalid command line argument." when installing Symantec AntiVirus 8.0 TECH100021 January 5th, 2004 http://www.symantec.com/docs/TECH100021 Support / Error: "1639.

Don't have a SymAccount? Today, it errors just before the feature transfer begins with "Error: -1639 Invalid command line argument. If you cannot upgrade to the latest build, the problem can be solved by setting the NtfsDisable8Dot3NameCreation registry value to 0. An Error Occurred Installing The Package. Windows Installer Returned '1639' 2k14 Can anyone suggest something to check, perhaps something in the log file?

Once reported, our moderators will be notified and the post will be reviewed. Forums New Posts FAQ Calendar Forum Actions Mark Forums Read Quick Links Today's Posts View Site Leaders Advanced Search

Forum Products Legacy Installer Products InstallShield InstallShield 2011 Error: -1639 Invalid How JustAnswer Works: Ask an Expert Experts are full of valuable knowledge and are ready to help with any question. Check This Out Have you tried putting quotes around the command line argument?

No Yes Connect with us facebook twitter CNET Reviews Top Categories CNET 100 Appliances Audio Cameras Cars Desktops Drones Headphones Laptops Networking Phones Printers Smart Home Software Tablets TVs Virtual Reality Consult the Windows Installer SDK for detailed command line help." Answer ID 14190 | Updated 09/10/2016 11:59 AM When installing ACT! Thanks very much. Customer Question Please help me out!

Date Updated 09/10/2016 11:59 AM Answers others found helpful Error: “Error 1603: Fatal Error During Installation” when installing Act! Privacy Policy Ad Choice Terms of Use Mobile User Agreement cnet Reviews All Reviews Audio Cameras Laptops Phones Roadshow Smart Home Tablets TVs News All News Apple Crave Internet Microsoft Mobile creating temp directory: C:\Users\nodakai\AppData\Local\.multirust\tmp\l3wd5pgwhvpbmy18_dir deleted temp directory: C:\Users\nodakai\AppData\Local\.multirust\tmp\l3wd5pgwhvpbmy18_dir deleted temp file: C:\Users\nodakai\AppData\Local\.multirust\tmp\qqfcjqbtji89jt41_file.msi error: command failed: 'msiexec' (Status: exit code: 1603) C:\Users\nodakai> I'm not an Admin on this machine. Discussions cover Windows 2003 Server, Windows installation, adding and removing programs, driver problems, crashes, upgrading, and other OS-related questions.Real-Time ActivityMy Tracked DiscussionsFAQsPoliciesModerators General discussion [Help] i got this error :-1639 by

Error Message: "Error 1603: Fatal Error During Installation", When Installing ACT! Preview post Submit post Cancel post You are reporting the following post: [Help] i got this error :-1639 This post has been flagged and will be reviewed by our staff. Please try again now or at a later time.