The paexec page lists Windows 2000 supported as of version 1.3 however when I try to run a remote command on a Windows 2000 SP4 computer I get the following error: Connecting to ###.###.###.###... Starting PAExec service on ###.###.###.###... Failed to start service on ###.###.###.### The service did not respond to the star t or control request in a timely fashion. [Err=0x41D, 1053] Failed to stop PAExec service. The service has not been started. [Err=0x426, 106 2] PAExec returning exit code -6 I have tried multiple Windows 2000 computers with the same results. Errors show up in the event log such as "The PAExec service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." and "The PAExec service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 0 milliseconds: No action." and "Timeout (30000 milliseconds) waiting for the PAExec service to connect." I have tried paexec version 1.9 and 1.6 as those were the only versions I could find and neither works. Version 1.6 actually pops up a Program Error on the destination computer that says "paexec.exe has generated errors and will be closed by Windows. You will need to restart the program. An error log is being created." Did support for Windows 2000 get dropped at some point? Could it be added back in or is there a place I can download an older version that would work? I would love to use this utility but I manage a lot of Windows 2000 computers. asked 07 Sep '12, 16:33 bjschip |
When an app won't start on Windows 2000, you can usually find out why using DependencyWalker from http://www.dependencywalker.com/ Start Dependency Walker and load PAExec and it will show why the app can't start (ie which system DLL is missing, or which function in a DLL is missing). Let us know what you see on that system. answered 11 Sep '12, 09:04 Doug ♦♦ When running Dependency Walker I get an error about APPHELP.DLL missing and a warning about MPR.DLL not containing the function WNetRestoreConnectionA. Both are mentioned as safe to ignore for Windows 2000 in the Dependency Walker help assuming the application is prepared to work around them.
(12 Sep '12, 10:04)
bjschip
|