- This topic has 6 replies, 2 voices, and was last updated 11 years ago by .
-
Posts
-
Hello,
Anyone else seen Error 2250 when checking for windows updates? Thanks.
2250 appears to indicate a networking problem of some kind:
ERROR_NOT_CONNECTED
2250 (0x8CA)
This network connection does not exist.
-Doug
daemon8814 – is there an error.log file in the remote working directory on the target server where you experience this problem? The default location would be C:Program FilesBatchPatchBatchPatchError.log. Please post the contents of this error log. Also, it might be useful to see if there are any associated errors in the system or application log (check eventvwr) on the target system at the same time as this problem occurs.
Thanks,
Doug
Glad you got it figured out.
-Doug
We have isolated the issue that’s causing the 2250 error, and the fix for it was published in the build released on January 1, 2014.
If you need to work around this issue for some reason, follow the steps below:
The workaround that we are recommending for the time being is to stop using alternate credentials within BatchPatch. Instead, launch BatchPatch with the credentials of the other user, as described below.
1. Place BatchPatch.exe in a public directory, such as C:Program FilesBatchPatchBatchPatch.exe. For this workaround to be successful it is NOT sufficient to run BatchPatch from a user profile directory such as the desktop.
2. Launch BatchPatch from the public directory by shift-right-clicking on it and choosing “run as different user.” And then use the credentials of a user that has local administrative permissions on target computers.
3. Once BatchPatch is running as the different user, you can start patching target systems without using alternate credentials. Just use integrated security and everything will work.
4. Launch one separate instance of BatchPatch for each set of credentials that you desire to use for patching target systems.
- You must be logged in to reply to this topic.