Databases
StackOverflow2013
Postsdbo
POPsExec Throws Error Messages, but works without any problems
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POPsExec Throws Error Messages, but works without any problems
    primarykey
    data
    text
    <p>So we are using PsExec a lot in our automations to install virtual machines, as we can't use ps remote sessions with our windows 2003 machines. Everything works great and there are no Problems, but PsExec keeps throwing errors, even every command is being carried out without correctly. For example:</p> <pre><code>D:\tools\pstools\psexec.exe $guestIP -u $global:default_user -p $global:default_pwd -d -i C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -command "Enable-PSRemoting -Force" </code></pre> <p>Enables the PsRemoting on the guest, but also throws this error message:</p> <pre><code>psexec.exe : Bei D:\Scripts\VMware\VMware_Module5.ps1:489 Zeichen:29 + D:\tools\pstools\psexec.exe &lt;&lt;&lt;&lt; $guestIP -u $global:default_user -p $global:default_pwd -d -i C:\Windows\System32\WindowsPowerShell\ v1.0\powershell.exe -command "Enable-PSRemoting -Force" + CategoryInfo : NotSpecified: (:String) [], RemoteException + FullyQualifiedErrorId : NativeCommandError PsExec v1.98 - Execute processes remotely Copyright (C) 2001-2010 Mark Russinovich Sysinternals - www.sysinternals.com Connecting to 172.17.23.95...Starting PsExec service on 172.17.23.95...Connecting with PsExec service on 172.17.23.95...Starting C:\Windows\ System32\WindowsPowerShell\v1.0\powershell.exe on 172.17.23.95... C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe started on 172.17.23.95 with process ID 2600. </code></pre> <p>These kinds of error messages apear ALWAYS no matter how i use psexec, like with quotes, with vriables/fixed values, other flags, etc. Does anybody has an idea how i could fix this? It is not a real problem, but it makes finding errors a pain in the ass, because the "errors" are everywhere. Disabling the error messages of psexec at all would also help...</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USSimons0n
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. POPsExec Throws Error Messages, but works without any problems
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POPsExec Throws Error Messages, but works without any problems
      1. USplunkets
      1. VTFavorite
    3. VO
      singulars
      1. POPsExec Throws Error Messages, but works without any problems
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI have the same problem, and i use `$ErrorActionPreference = "SilentlyContinue"` before the psexec command. But it is not a real solution.
      singulars
      1. POPsExec Throws Error Messages, but works without any problems
      1. USplunkets
    2. COWell, not the best idea, but way better than my "solution". I guess, i will write a psexec-silent function, tuning the ErrorActionPreference on and off before the psexec command. At least i can switch off the error message, which clearly isn't one.
      singulars
      1. POPsExec Throws Error Messages, but works without any problems
      1. USSimons0n
    3. COCheck this; http://stackoverflow.com/a/2095623/469777
      singulars
      1. POPsExec Throws Error Messages, but works without any problems
      1. USStafford Williams
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload