Psexec.exe Error Code 1603
Contents |
unattended client PsExec push install of unattended client - No combination of switches gets me where I need to be Options Email this topicWatch psexec msiexec error 1603 this topicPrint this topic » NormalThreaded Previous Topic Next Topic psexec the system cannot find the path specified piusg #1 Posted : Tuesday, May 20, 2014 6:32:16 PM(UTC) Rank: NewbieMedals: Joined: 5/29/2013(UTC)Posts: 6Location:
Psexec The System Cannot Find The File Specified Windows 7
Portland, OregonWas thanked: 1 time(s) in 1 post(s) I'm trying to create a cmd script to push an installation of the unattended client to a
Error Establishing Communication With Psexec Service On The System Cannot Find The File Specified
Windows 7 box using the Sysinternals tool PsExec.From a CMD window, I attempt to execute this: psexec \\remote-pc-name -u mydomain\admin1 msiexec /i \\software-repository\support\sc-remote-client.msiremote-pc-name is joined to the domain mydomain.mydomain\admin1 has Domain Administrator privileges and has access to the file \\software-repository\support\sc-remote-client.msi.I keep getting the following: msiexec exited on remote-pc-name with error code psexec error code 1619 1603.What am I doing wrong?Edited by userTuesday, May 20, 2014 6:36:06 PM(UTC) |Reason: Not specified User ProfileView All Posts by UserView Thanks Wanna join the discussion?! Login to your ScreenConnect Remote Support Software User Forum forum accountor Register a new forum account. piusg #2 Posted : Tuesday, May 20, 2014 7:20:15 PM(UTC) Rank: NewbieMedals: Joined: 5/29/2013(UTC)Posts: 6Location: Portland, OregonWas thanked: 1 time(s) in 1 post(s) Okay. I figured it out. I'm posting the solution in case this helps someone else.I forgot the -h switch, which uses the sessions elevated token on Windows Vista/7/8, if possible. That did the trick.So the command line should look like this:psexec \\remote-pc-name -h -u mydomain\admin1 msiexec /i \\software-repository\support\sc-remote-client.msiEdited by userTuesday, May 27, 2014 4:39:54 AM(UTC) |Reason: Not specified 1 user thanked piusg for this useful post. solutionssquad on 5/21/2014(UTC) User ProfileView All Posts by UserView Thanks Users browsing this topic Guest (15) ScreenConnect Remote Suppo
MSI package provided from a vendor that I am attempting to use to update their software on ~30 PCs. I am trying to do this using simple file transfer and psexec to
Psexec The System Cannot Find The File Specified Exe
run an interactive batch that just has the msiexec command in it. If I msiexec exited on with error code 1603 execute the batch for the msiexec command locally all is dandy, but if I try executing it using psexec, msiexec returns 1603. I psexec could not start cannot find the file specified sent the companies installer logs in, but they have yet to respond and I would like to do this sooner rather than later. I've tried running the command directly using psexec and calling it on the http://forum.screenconnect.com/yaf_postst3802_PsExec-push-install-of-unattended-client.aspx remote pc using at to schedule it. msiexec always executes and then errors out with 1603 after about 30 seconds. Any ideas would be appreciated. Reply Subscribe View Best Answer RELATED TOPICS: msiexec problem MSIexec not working properly? msiexec just returns a pop up   3 Replies Chipotle OP Helpful Post Simon1964 Aug 24, 2011 at 3:46 UTC Hello there, I do not have much experience with psexec, but I found https://community.spiceworks.com/topic/152993-weird-msiexec-1603-error this link:http://www.appdeploy.com/faq/detail.asp?id=73 It describes a way to activate verbose istaller logging. Maybe it can halp you analyse your problem? good luck 0 Serrano OP Best Answer RowanBarker Aug 24, 2011 at 10:25 UTC Try running PSEXEC with a /i switch and a /qb switch on the msi installer switch - this should give you a basic installation progress window and will show interactively on the end user's system - might give you more information about the error. I had this issue when trying to install Visio viewer on a bunch of systems - turned out they were missing a vital windows update but no mention of this in any of the logs! 0 Thai Pepper OP Mike Soule Aug 24, 2011 at 11:15 UTC @Simon thanks for the link, I already had verbose logging turned on, but that is an awesome reference. @Rowan I changed my /qn to /qb and the log is saying that it completed successfully, I will be checking this again tonight. To verify the installation took and did not interfere with the workstation while installing. Thanks for the help. After some testing I found that it would fail every time when I was RDPed into the machine using the local administrator account. Fix, set the command to execute at time x and
Studio 2015 products Visual Studio Team Services Visual Studio Code Visual Studio Dev Essentials Office Office Word/Excel/PowerPoint Microsoft Graph Outlook OneDrive/Sharepoint Skype Services Store Cortana https://msdn.microsoft.com/en-us/library/windows/desktop/aa376931(v=vs.85).aspx Bing Application Insights Languages & platforms Xamarin ASP.NET C++ TypeScript .NET https://social.technet.microsoft.com/Forums/forefront/en-US/ed91505d-9807-4447-b9b1-415de3a44e56/install-failing-msiexec-code-1603?forum=Forefrontclientsetup - VB, C#, F# Server Windows Server SQL Server BizTalk Server SharePoint Dynamics Programs & communities Students Startups Forums MSDN Subscriber downloads Sign in Search Microsoft Search Windows Dev Center Windows Dev Center Explore Why Windows What’s new for Windows 10 Intro to Universal Windows Platform Dev cannot find Center Benefits Develop for accessibility Build for enterprise Docs Windows apps Get started Design and UI Develop API reference Publish Monetize Promote Games Get started UI design Develop Publish Desktop Get started Design Develop API reference Test and deploy Compatibility Windows IoT Microsoft Edge Windows Holographic Downloads Samples Support Dashboard Explore Why Windows What’s new for Windows 10 cannot find the Intro to Universal Windows Platform Dev Center Benefits Develop for accessibility Build for enterprise Docs Windows apps Get started Design and UI Develop API reference Publish Monetize Promote Games Get started UI design Develop Publish Desktop Get started Design Develop API reference Test and deploy Compatibility Windows IoT Microsoft Edge Windows Holographic Downloads Samples Support Dashboard Windows Installer Windows Installer Reference Errors Reference Errors Reference MsiExec.exe and InstMsi.exe Error Messages MsiExec.exe and InstMsi.exe Error Messages MsiExec.exe and InstMsi.exe Error Messages Windows Installer Error Messages MsiExec.exe and InstMsi.exe Error Messages TOC Collapse the table of content Expand the table of content This documentation is archived and is not being maintained. This documentation is archived and is not being maintained. MsiExec.exe and InstMsi.exe Error Messages These error codes are returned by the Windows Installer functions MsiExec.exe and InstMsi.exe. Note that any error in Winerror.h (such as ERROR_INVALID_DATA, included here) can be returned as well. For more error codes returned by the Windows Installer, see Windows Installer Error Messages.Note The error codes ERROR_SUCCESS, ERROR_SUCCESS_REBOOT_INITIATED, and ERROR
(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeProductsLibraryLearnDownloadsSupportForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Asked by: Install failing... msiexec code 1603 Forefront > Read Only - Forefront Client Security Setup and Configuration Question 0 Sign in to vote I'm trying to set this up on a single server (inside a virutal machine - domain member to another virtual machine). It always fails installing the MOM Reporting service. The log shows: Task(Install MOM Reporting Service) "msiexec.exe failed with exit code 1603". Anyone else run into this or have a solution? Thanks in advance for your help! Mark Thursday, November 30, 2006 8:29 PM All replies 0 Sign in to vote Hi Mark Thanks for posting! The failure code 1603 is a generic failure that requires you to open the specific FCS log. If you could do the following: Open this folder: %Program Files%\Microsoft Forefront\Client Security\Server\Logs Open the MOMReporting.log file Do a search for "error" and let us know if you find anything Without having seen your log file, a potential item might be drive space available. By default, we attempt to allocate 15 GB for the MOM Operational DB (OnePoint) and 1 GB for the MOM Reporting DB (SystemCenterReporting). It may be that you've run out of drive space on your VM Let me know what you find and we will help you get it installed! Thanks Chris Forefront Client Security PM Proposed as answer by Jackyproof Tuesday, February 23, 2010 4:45 PM Friday, December 01, 2006 12:58 AM 0 Sign in to vote It was a space issue - the VM only had a 10 gig drive defined... Thanks for your help! Thursday, December 07, 2006 8:33 PM 0 Sign in to vote No problem!