BatchPatch Error: 0. HRESULT: -2147024894

[shoretelghst]

Hi

I am trying to Download and Install updates on Windows 2008 R2 Servers using BatchPatch. The Servers would be downloading updates from a local WSUS Server.

I am getting error “Windows Update: Error: 0. HRESULT: -2147024894. Could not find file ‘\XXXXC$WindowsSystem32BatchPatchTempResult.log’.” I can download and install updates if I run Windows Update directly on the same server.

Any ideas????

[doug]

Can you confirm what version of BatchPatch you are currently running? We were seeing this occur last year in July 2014, but we fixed it in August 2014. If you are not running the latest version of BatchPatch (2015.5.7.x.x), please make sure to update and then try again. Let me know what happens.

Thanks,

Doug

[shoretelghst]

Thanks for the reply doug.

I am running the latest version – BatchPatch 2015.5.7.13.44

[doug]

This is very peculiar. Approximately how many machines are you seeing this on? Approximately what percentage of your total number of machines does this include? Considering that this appears to be a new problem for you, I wonder if the issue was somehow introduced during your last Windows Update session. I think it’s plausible that one of the updates that you installed last maintenance window is the reason that this is occurring. Would you be able to list out the KBs that you installed in your most recent update session? If I can reproduce the issue by installing the update that caused it, then we should be able to fix it.

Thanks,

Doug

[shoretelghst]

I can’t say up till what time or update it was working because this is the first time I am trying to do this. The guy who used to do it before has left and I’ve taken over this role now.

I’ve added two Windows 2008 Standard x86 Servers and BatchPatch 2015.5.7.13.44 seems to work on these two. How come I am having problems on Server 2008 R2 x64 servers?

[doug]

Do you at least have any idea how many machines you are seeing this error on vs your total number of machines? It would be good to get some sense of what the overall percentage of machines are doing this.

The issue has nothing to do with ‘2008 Standard x86’ vs ‘2008 R2 x64.’ I say this because we have customers all over the world patching tens of thousands of 2008 R2 x64 machines who are not experiencing this problem. I believe the issue is likely to be occurring as a result of a particular patch or application being installed on the system, and somehow it’s affecting BatchPatch’s ability to perform its tasks.

Since I am not currently able to reproduce it, I think your best bet is to look at one of your 2008 R2 x64 machines that is NOT having the problem, and then compare it to one of your 2008 R2 x64 machines that IS having the problem. If you can find a certain set of Windows Updates that are installed on the problematic machine that are not installed on the working machine, then you can either remove them one by one, testing BP in between each one, until you determine which update is causing the issue. Or you can install the missing updates, one by one on the working machine, testing BP in between each one, until you determine which update is causing the issue. If you are able to narrow it down and provide me with a suspect KB number, I can then test that here to see if I can reproduce it. If I’m able to reproduce it, we should be able to fix it. Currently you are the only customer to have reported this issue. If the issue is affecting other people, we will hear about it soon enough. However, if it’s isolated to your own systems, then it could be tougher to track down a cause.

-Doug

[shoretelghst]

I have twenty-one (21) 2008 R2 x64 servers and all of them are having this problem.

If BatchPatch worked on at least one of these servers then I could have taken your advise and compared the update history. What do I do in this case?

[doug]

I’m going to send you an email to troubleshoot further.

-Doug

[booster]

Hi guys,

I guess the result of investigations will be shared, I faced this issue on some environment, most of time it was an AV problem or somehow a precedent unfinished BP job

Removing the remote folder and follow the process on the target server (file/folder creation) was enough to get rid of it for me. Maybe the WUA agent too but I never faced it at this level.

Waiting for update

Booster

[doug]

Booster – Are you *sure* that you were getting this *exact* same error? I suspect that the error you were experiencing included the same HRESULT but not the same error number — something like “Error: 2. HRESULT: -2147024894” but not specifically “Error: 0. HRESULT: -2147024894”

[doug]

Currently the only known cause of the following error:

Error: 0. HRESULT: -2147024894

is that PsExec cannot run successfully on a server that has Mandatory User Profiles: https://msdn.microsoft.com/en-us/library/windows/desktop/bb776895%28v=vs.85%29.aspx

When running a simple test of PsExec at the command line when Mandatory User Profiles are in use, such as:

psexec \targetcomputer IPCONFIG

The expected error that occurs is something similar to:

Error deriving session key:

The profile for the user is a temporary profile.

When BatchPatch tries to operate on a machine that has Mandatory User Profiles, it will return with this error:

Error: 0. HRESULT: -2147024894

[shoretelghst]

This issue is still not solved and remains outstanding.

[Author]

Posts