BatchPatch Forums Home › Forums › BatchPatch Support Forum › Error 2 or Error 0
- This topic has 7 replies, 2 voices, and was last updated 9 years, 8 months ago by doug.
-
AuthorPosts
-
April 20, 2015 at 2:23 pm #9082coffeysmParticipant
Hi,
I’ve been using BatchPatch pretty successfully for awhile. However, lately over 50% of my Server 2012 R2 have been reporting back either Error 2 or Error 0. If I also attempt to get the pending Reboot status, I get the object reference not set to an instance of an object.
I can view the log files from the GUI.
April 20, 2015 at 2:43 pm #10856dougModeratorWhat version of BatchPatch is this? (See Help > About)
What action produces the error 0 and error 2? What is the full *exact* text of the error?
-Doug
April 20, 2015 at 5:50 pm #10818coffeysmParticipantVersion is 2014.3.7.11.38.
I get those errors involving anything with Windows Updates. I also tried different versions of psexec and get the same results.
For servers that end with Error 0 it flashes quickly saying no applicable updates and then displays Error 0 with timestamp. The progress bar reads 100%. The all messages column shows Windows Update Error: 0
For servers that end with Error 2 and timestamp. The progress bar is blank. The all messages column shows Windows Update Error: 2
April 20, 2015 at 6:03 pm #10819dougModeratorThe Error 0 server 2012 issue was fixed in August 2014 (started occurring after a particular patch that Microsoft released at the time), so please update to the latest version. Also note there were more than a dozen other releases between your version and the current version, so I would highly recommend that you stay up to date as new versions are released. The default config of the software automatically notifies when updates are released (Tools > Settings > Check for updates on startup).
I’m not sure about the other Error 2 issue that you’re experiencing, but let’s see if it’s also addressed by the update.
-Doug
April 20, 2015 at 7:19 pm #10820coffeysmParticipantJust ran the latest version and the Error 0 problem has been resolved like you state.
The Error 2 problem still exists, however, it gives more information this time.
It can’t read the BatchPatchTempResult.log file. I’m also getting that problem where PSEXECV is not deleting itself from the Windows services. I don’t have any anti-virus software on these machines, but the agent is being deleted.
April 20, 2015 at 7:47 pm #10826dougModeratorWhat is the *exact* error text? Please copy/paste the entire thing, verbatim.
Approximately how many of your 2012 R2 servers are working properly and how many are throwing this error?
If you compare the list of installed Windows Updates on a computer that is working properly with the list of installed updates on a computer that is throwing the error, are there any discrepancies between the two lists?
Please also review the below threads carefully, and let me know if you have any luck with the suggestions. Essentially, this issue (if the one you’re experiencing is *identical* to the ones noted below) has been reported by only a very small number of users, and it’s always only happening on just one or two of their servers. We have not so far been able to reproduce the problem.
error-2-hresult-2147024894-could-not-find-file
error-2-very-often-server-2012-r2-on-domain-controllers
-Doug
April 22, 2015 at 2:33 pm #10809coffeysmParticipantMy issue was resolved by upgrading BatchPatch to the latest version AND downgrading PSEXEC from V2.11 to V1.98. I don’t have the time or desire to figure out why PSEXEC version 2.11 doesn’t work on all servers. 99% of them are configured the same, however, I had issues on servers that offer file shares.
Thanks for your help.
April 22, 2015 at 4:28 pm #10810dougModeratorThanks for reporting back. I’m glad you got it fixed. I would suggest that at some point you try v2.11 again. I wouldn’t be surprised if it started working, as we saw this happen with one other customer who was having the same problem.
-Doug
-
AuthorPosts
- You must be logged in to reply to this topic.