Home > Windows Installer > Invalid Command Line Argument Windows Installer Sdk

Invalid Command Line Argument Windows Installer Sdk


To start viewing messages, select the forum that you want to visit from the selection below. Discussion is locked Flag Permalink You are posting a reply to: [Help] i got this error :-1639 The posting of advertisements, profanity, or personal attacks is prohibited. Solution Use a different ID or change the password so it does not contain a Quote. Sign up! check over here

Legacy ID 2002102210433548 Terms of use for this information are found in Legal Notices. Please refer to our CNET Forums policies for details. Thanks again for the link. Alas, the error still occurs after correcting it to [$Documentation].

Invalid Command Line Argument Windows Installer Sdk

To change the Temp folder location: Go to System Properties; Windows XP Click the Start > Run > type sysdm.cpl Windows Vista, 7, and 8 Click Start and type sysdm.cpl into Generated Thu, 17 Nov 2016 22:36:40 GMT by s_fl369 (squid/3.5.20) To use Google Groups Discussions, please enable JavaScript in your browser settings, and then refresh this page. . Solution This problem is fixed in Symantec AntiVirus 8.01 build 429c and later.

Consult the Windows Installer SDK for detailed command line help. In the “Startup type”, select the “Automatic”, and then click “Apply” and “OK”. All rights reserved. Error 1639 Invalid Command Line Argument 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

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 Windows Installer Returned 1639 Consult the Windows Installer SDK for detailed command line help."I`m using windows XP sp2 right nowand does anyone know any patch or something like that that could help me get out No Yes Did this article save you the trouble of contacting technical support? https://groups.google.com/d/topic/microsoft.public.platformsdk.sdk_install/sdT2VlBmlDs 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.

My AccountSearchMapsYouTubePlayNewsGmailDriveCalendarGoogle+TranslatePhotosMoreShoppingWalletFinanceDocsBooksBloggerContactsHangoutsEven more from GoogleSign inHidden fieldsSearch for groups or messages Log in Sign up! Command Prompt Error 1639 Answers 1 /i [package] Installs the specified product/f p,o,e,d,c,a,u,m,s,v p - Reinstalls a product only when a file is missing o - Reinstalls a product when a file is missing or Track this discussion and email me when there are updates If you're asking for technical help, please be sure to include all your system info, including operating system, model number, and At the command prompt, type “msiexec /unregister”, and then press Enter.

Windows Installer Returned 1639

Terms and Conditions Privacy Policy Powered by vBulletin Version 4.2.2 Copyright © 2016 vBulletin Solutions, Inc. https://www.veritas.com/support/en_US/article.000010684 Facebook Twitter Google+ YouTube LinkedIn Tumblr Pinterest Newsletters RSS Community Forums Register Help Remember Me? Invalid Command Line Argument Windows Installer Sdk Toggle navigation Software Tips Questions Blogs Links Communities Questions & Answers Help with MSI 1639 Help with MSI 1639 AppDeploy.com How helpful is this to you? Error 1639 Peachtree 2010 Forgot Your Password?

Search ThreatTrack Security Support +877-757-4094 Home Solutions Forums Solution home General Windows Installer Errors MSI Error 1639: 'Invalid command line argument' during installation Modified on: Fri, 15 May, 2015 at 11:30 http://p2pgsm.com/windows-installer/windows-installer-error-1619.html Might there be spaces or special characters in the string? Reply With Quote Page 1 of 2 12 Last Jump to page: Quick Navigation InstallShield 2011 Top Site Areas Settings Private Messages Subscriptions Who's Online Search Forums Forums Home Forums Products installation menu will reappear. Error 1639 Windows Installer Sdk Peachtree

Disruptive posting: Flaming or offending other usersIllegal activities: Promote cracked software, or other illegal contentOffensive: Sexually explicit or offensive languageSpam: Advertisements or commercial links Submit report Cancel report Track this discussion Supported Products A-Z Get support for your product, with downloads, knowledge base articles, documentation, and more. Have you tried putting quotes around the command line argument? this content Flag Permalink This was helpful (0) Back to Windows Legacy OS forum 5 total posts Popular Forums icon Computer Help 51,912 discussions icon Computer Newbies 10,498 discussions icon Laptops 20,411 discussions

All rights reserved.

Skip to content Coopoint Menu How To Fix Windows Installer Error 1639 Posted on January 25, 2015 by Christine Smith While you are trying to install a An Error Occurred Installing The Package. Windows Installer Returned '1639' 2k14 No Yes How can we make this article more helpful? All rights reserved.

Posted in ArticlesTagged Installer Error 1639 Leave a Reply Cancel reply Your email address will not be published.

Consult the Windows Installer SDK for detailed command line help". Link for Peachtree or Error Messages Occur When Clicking the Peachtree Tab Share Delicious Digg Facebook Reddit StumbleUpon Twitter Print Email this page Recipient Email *Required Your e-mail *Required Your Name To use short file names by temporarily disabling the use of long file names Use Regedit.exe to Navigate to the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem In the right pane, right-click NtfsDisable8Dot3NameCreation and Error Code 1639 Sql Server 2012 It's a free tool but which item to remove varies with what fails to install.

This may enhance performance in some cases, but will cause the Symantec AntiVirus Corporate Edition installation to fail. I have no idea what I've done that's caused this; the only argument I am passing to the msi file is verbose logging. Consult the Windows Installer SDK for detailed command line help. http://p2pgsm.com/windows-installer/windows-installer-returned-1639.html Hosted by Freshdesk

ERROR The requested URL could not be retrieved The following error was encountered while trying to retrieve the URL: Connection to failed.

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 It is possible that updates have been made to the original version after this document was translated and published. LLC.