Home > Error Code > Psexec Exe Error Code

Psexec Exe Error Code


The content you requested has been removed. You cannot edit your posts in this forum. Lastly, be sure that the user which you are using has permission to write directly to c:\, you might have to use a lower directory. 1 Thai Pepper Here's one possible source: FIX: 0x80131700 error code when starting or configuring the Enterprise Single Sign-On Service I don't know what utility.exe does, but if it attempts to perform Windows authentication, useful reference

I'm using PSExec (SysInternals PSTools) with NirCMD.exe to attempt to get screenshots. The command line I just gave you may work. Actually, I have not tested it (yet), but constructed it from what I learnt by using psexec. Default = local system To run against all computers in the current domain enter "\\*" @run_file Run command on every computer listed in the text file specified. http://stackoverflow.com/questions/26720734/psexec-error-code-2146232576

Psexec Error Code 2

Haha 0 Thai Pepper OP CrimsonKidA Apr 3, 2014 at 5:53 UTC Matt9169 wrote: as (root) said, it means success. This is an msiexec kludge I was butting my head against. Regards, Shirish drambo Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 18 December 2006 Location: United States Status: Offline Points: 3 Post Options Post Reply

  • The method of accessing those files might require more steps within PSExec (like mapping a drive, etc.).
  • No.
  • I have psexec.exe located on the root of C, along with the msi file.
  • Add Cancel × Insert code Language Apache AppleScript Awk BASH Batchfile C C++ C# CSS ERB HTML Java JavaScript Lua ObjectiveC PHP Perl Text Powershell Python R Ruby Sass Scala SQL

Do you have some knowledge that this issue with psexec is specific to Windows 2003? To run these commands from PsExec you must call CMD /C and then pass the commands as parameters - see the examples below. PsExec does not require you to be an administrator of the local filesystem, with the correct password psexec will allow UserA to run commands as UserB - a Runas replacement. Psexec Exited With Error Code -1073741502 To PsExec a .bat file from the command line you'd have to do the following: psexec \\targetServer -u domain\username -p password cmd.exe /C "\\networkshare\somebatfile.bat" To do the equivalent in BatchPatch, enter

If you omit this option the application must be in the system path on the remote system.-dDon't wait for process to terminate (non-interactive).-eDoes not load the specified account’s profile.-fCopy the specified Psexec Error Code 1073741502 What is summer in Spanish? "Estío" vs "verano" What to do with my pre-teen daughter who has been out of control since a severe accident? I hope this helps. -Doug Posted 3 years ago # veix Member Thank you for long explanation, and it did help (if you said you have not changed the code). more stack exchange communities company blog Stack Exchange Inbox Reputation and Badges sign up log in tour help Tour Start here for a quick overview of the site Help Center Detailed

Passed as clear text. Psexec Error Code 0 These users do NOT have local admin rights, so they can't write to C:\, plus I was thinking it was writing the file to my C:\ drive.  1 This discussion has Accept eula When launched for the first time, PsExec will create the license registry key: HKCU\Software\Sysinternals\PsExec\EulaAccepted=0x01 Psexec will swallow the first "-accepteula" on the commandline, no matter where it occurs, so However I have found that sometimes I have to put the command ie: "nircmd.exe savescreenshot "c:\shot.png"" into a .bat file, copy the file to the remote drive, and then run it

Psexec Error Code 1073741502

What stops messenger RNA from binding to itself? asked 2 years ago viewed 2467 times Blog Stack Overflow Podcast #92 - The Guerilla Guide to Interviewing Linked 56 How can I connect to a Windows server using a Command Psexec Error Code 2 Nested apply function at a list What's the difference between `su -` and `su --login`? Cmd Exited With Error Code -1073741502 So no path is needed.

If you doubleclick on an .msi file locally, you actually launch msiexec.exe which loads the .msi file. see here All that said, the BatchPatch code has not changed for the "remote script process" functionality, so I'm unsure how you would have had anything different work in an older version of If omitted, you will be prompted to enter a hidden password. -r The name of the remote service to create or interact with. -s Run remote process in the SYSTEM account If I'm on computer A, and I want to run a .bat on computer B, but the .bat file is located on computer C, then this can only be done if Psexec Error Code 1603

The remote computer is not running Windows Enterprise so I'm not sure if the suggested fix applies? –Benjulious Nov 3 '14 at 19:52 1 @Benjulious Among the errors listed in Text Quote Post |Replace Attachment Add link Text to display: Where should this link go? While this is a production server, rebooting during the day is an option since its primary workload is batch style processing at night. http://fapel.org/error-code/psexec-with-error-code-0.php If you omit the computer name, PsExec runs the application on the local system, and if you specify a wildcard (\\*), PsExec runs the command on all computers in the current

When you specify a username the remote process will execute in that account, and will have access to that account's network resources. Psexec Error Code 5 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 Does anyone know what part of the puzzle I am missing?

Note also, please: msiexec.exe by default is located in %windir%\system32.

Otherwise, the next time it happens, we'll probably reconfigure our current work to run as a service on the servers themselves. Help Desk » Inventory » Monitor » Community » Forum Home > Sysinternals Utilities > PsTools New Posts FAQ Search Events Register Login Cannot find the file specified Post This is the first problem we've had with psexec, so if we can find the cause, we'll probably stick with it. Psexec Error Code 1073741790 If no session is specified, the process runs in the console session. -l Limited - Run process as limited user.

For example, to run the application on CPU 2 and CPU 4, enter: "-a 2,4"-cCopy the specified program to the remote system for execution. For example, if you don't use a username/password, all attempts to access remote shares fails instantly. Posted 3 years ago # doug doug Interesting. Get More Info Login to your ScreenConnect Remote Support Software User Forum forum accountor Register a new forum account.

Hopefully, this will be useful information to someone else out there having the dreaded 1603 issue.Here's what my final line of psexec code looks like:psexec \\machinename -u username -p password msiexec i am having the exact same problem with the bloody flash .msi ..I am testing in dev with DA creds. Strips the Administrators group and allows only privileges assigned to the Users group. -n s Specify a timeout (s seconds) for connecting to the remote computer. -p psswd Specify a password more hot questions question feed about us tour help blog chat data legal privacy policy work here advertising info mobile contact us feedback Technology Life / Arts Culture / Recreation Science