[doug]

Tools > Export / Import

-Doug

[doug]

Thank you for the suggestions. We will consider this for a future build.

-Doug

[doug]

This is not currently possible because the filters are set globally, not per-row/host. We will consider per-host settings in a future build of the app.

Thanks,

Doug

[doug]

I would recommend that you utilize the ‘Update Date Filtering’ setting under ‘Tools > Settings > Windows Update.’ The setting allows you to “only install updates that were published / approved at least X days ago.” I think this will give you what you need. For example, if you set it to 30, then it will only install updates that were published or approved at least 30 days ago. Any updates released in the past 30 days will be skipped.

-Doug

[doug]

Hi DJ – We agree with you, and we’re working on it. However, at the moment we do not have a solution in place. We hope to have something workable ready for next release.

Thanks,

Doug

[doug]

Richard – I have never seen nor heard of this error before. In order to assist I need you to please answer the following questions.

1. What *exactly* are you doing to produce this error? Please describe the exact steps taken to produce this error.

2. What version of BatchPatch are you using?

3. Please paste the ‘All Messages’ column showing your BatchPatch actions that cause this error as well as the error itself if the error is displayed in the ‘All Messages’ column.

4. Please paste the ‘Remote Agent Log’ column that shows this error.

-Doug

[doug]

Thomas – I have never seen or heard of an issue where IP worked properly but computer name did not work, except when DNS or NetBIOS was at fault. However, your issue does sound particularly strange. It seems to me that as a workaround you should just make sure to use IP address for those 2 machines until you are able to resolve the root cause of the problem.

As for whether or not it could be a PsExec problem, it’s certainly possible but it’s hard to say for sure, especially considering that PsExec is working properly for you when you run it at the command line. However, if you still suspect an issue with PsExec, then certainly you can/should try a different old version of PsExec if you’re able to obtain such a version, or you could try to use the free PaExec (rename PaExec to PsExec and test). You can/should also try any other suggestions in that other forum posting. Another option is to try running BatchPatch from a different computer in case the problem is not the target computers but rather is with the computer you are currently using to run BP.

[doug]

Thanks for the suggestion, Andreas. We will take a look at this for a future build.

However, please also note that in the meantime you do not need to use a domain administrator account or separate local administrator accounts. You can use a single regular domain user account that has been added to the local administrators group of each target computer.

-Doug

[doug]

This error is a bit peculiar because normally we would expect to see ‘Access Denied’ if there were a permissions problem. Nevertheless, to enter a username and password a given row, select the row and then select ‘Actions > Specify alternate logon credentials.’ Alternatively, you may use run-as to run the entire BatchPatch.exe as a different user.

-Doug

[doug]

That’s very peculiar. If IP address works but name does not work, then it sounds like maybe it could be some type of issue with DNS or NetBIOS, but I’m not sure. It could probably also be something else, such as anti-virus, firewall, or host intrusion prevention software.

-Doug

[doug]

Magnus –

First, you will not see anything appear in the Windows Task Scheduler. BatchPatch tasks have nothing to do with Windows scheduled tasks.

Second, it’s unclear to me what the problem is that you are encountering. BatchPatch must be running in order for tasks to be executed, so perhaps that’s where you’re going wrong. I would suggest you review the tutorial for using the BP task scheduler here: Using the Task Scheduler in BatchPatch

Third, to test what you configure, I would recommend that you create some testing tasks that are scheduled to execute just a minute or two in the future, so that you can watch and make sure that they execute accordingly. If they are using monthly recurrence then you can also modify your system time temporarily to trigger a task to run if it’s scheduled for next month, just to make sure you understand how everything works and that everything executes as expected.

I hope this helps.

-Doug

[doug]

Please have a look through the following links which contain some possible solutions/fixes for the issue you are encountering. To me it sounds like PsExec is not working properly, but it’s hard to know why. Note that the error 2 you are receiving might be reported a bit differently than how it is reported in the links below because those are old postings where older versions of BP reported the error a bit differently. In your case you are seeing “Error 1611: 2. Failure” which indicates that PsExec is returning exit code 2. The 1611 just indicates the location in BP where the 2 was returned. It’s not relevant otherwise. The “2” is the relevant part of the error you are receiving because it’s the actual exit code being returned from the attempt to run the remote process.

error-2-very-often-server-2012-r2-on-domain-controllers

error-2-or-error-0

error-2-hresult-2147024894-could-not-find-file

Let me know how it goes.

-Doug

[doug]

The task scheduler in BatchPatch allows you to run a task on any day of any month or year.

Using the Task Scheduler in BatchPatch

-Doug

[doug]

As you pointed out, this is likely an issue with the proxy setup in your environment. Specifically, I believe this is related to proxy authentication. I know you said that the 3 computers are all configured the same, but if they were exactly the same then they would behave the same. They are not behaving the same, so therefore there must be something different about one of them.

Please review the instructions:

'Scenario 2: The Windows Update Agent on target computers is properly configured to use the corporate proxy, but the proxy requires authentication'

Using BatchPatch with an Enterprise Web Proxy

-Doug

[doug]

Kennis – Thank you for reporting your success with declining the single update ‘AMD driver update for Pci Bus.’ I’m very glad to know that this fixed the issue for you!

-Doug

[doug]

Sorry about that. The report currently lists the install date per update per computer.

-Doug

[doug]

Yes. Please use ‘Actions > Windows updates > Generate consolidated report of update history.’

[doug]

The 1611 is sort-of a generic error indicator. It means that the remote agent process exited with an unexpected code, with the unexpected codes being 59 and 5 on your two targets. The unexpected codes are Windows system error codes.

5 is normally:

ERROR_ACCESS_DENIED



5 (0x5)



Access is denied.

However, 5 could also mean that there was an access violation on the target, which would essentially mean that the remote agent crashed unexpectedly. If this were the case you would see something in the application event log of the target computer. Normally an ‘Access denied’ error would be reported differently in BatchPatch, which is why I suspect that in this case you might instead be dealing with an access violation unexpected crash of the agent.

59 is:

‘ERROR_UNEXP_NET_ERR

59 (0x3B)

An unexpected network error occurred.’

---

I would suggest that you start by rebooting the target computers. Then see if it happens again. You might find that these are transient issues, especially if you have not had any issues running BP with these computers in the past.

-Doug

[doug]

Hi Mats – Thanks for the suggestion. We will consider this, but I don’t think it’s likely something that we would do, as it would probably require a persistent agent to be installed on target machines, and there would still be a reliability issue for the connection between BP and the targets. The recommended approach/solution for the situation you describe is to simply run BP directly on the remote network instead.

-Doug

[doug]

When you are prompted in BatchPatch that there is an updated version available, you can click to download it. Then close your original version and open the new version that you just downloaded. That’s all there is to it. If you are seeing the same version as before then it sounds like you mixed up the old and new versions.

BatchPatch does not use PsKill. As for PsExec, you need to download that from Microsoft.

-Doug

[doug]

After a lot of testing with one customer’s database, we were able to determine the culprit update in his database to be ‘AMD driver update for Pci Bus’ I was able to decline this single update and then wait a few minutes, and the error disappeared.

-Doug

[doug]

I just emailed you.

Thanks!

Also, I would strongly encourage you to test out the scheduler in advance of patching by just setting up a bogus test job to a non-existent computer. You can schedule the job for a couple minutes in the future and then just watch it execute. Obviously it will fail because the target computer won’t exist, but you will then at least be able to confirm that the task is being executed in the first place, as opposed to just somehow not even getting executed.

-Doug

[doug]

Thanks for sharing. It’s unclear to me what might have happened here. We do not currently have any other reports of similar problems, and I’m not able to reproduce any similar issue. That said, it might be hard to determine exactly what conditions are required to produce the problem. Please let me know if it happens again.

Was this scheduled task loaded from a pre-existing .bps file that you loaded up on Tuesday? Or on Tuesday did you manually set the schedules up from scratch to run Wed at 01:00? If it came from a .bps file and if you have that .bps file still (without having saved over it), then if possible I would want to see that original .bps (sent to me as email attachment, pls). Let me know.

Thanks,

Doug

[doug]

After a lot of testing with one customer’s database, we were able to determine the culprit update in his database to be ‘AMD driver update for Pci Bus’ I was able to decline this single update and then wait a few minutes, and the error disappeared.

If you determine that this update is not the culprit on your server, the next best option would be to selectively declined all of the updates in the ‘Windows 10 and later drivers’ group. To do this…

1. create a new update view on the WSUS by right-clicking on ‘Updates’ in the left-pane, and selecting the option for ‘New Update View…’

2. Check the box ‘Updates are for a specific product.’

3. Modify the checkbox list of products to include ONLY the checkbox for ‘Windows 10 and later drivers.’

4. Specify a name for the view called ‘Windows 10 and later drivers’ or whatever you prefer and click OK.

5. Now make sure the new ‘Windows 10 and later drivers’ view that you just created is the selected view.

6. Change the the filter drop-downs to show

Approval: 'Any Except Declined' Status: 'Any'

7. Select all updates even if they are not approved, and go ahead and decline them. After the updates are declined you might still need to wait a few minutes (or longer) before the error will stop occurring.

-Doug

[doug]

That’s definitely odd. Can you paste the ‘All Messages’ column content for me to review? If BP modified the next run time, then it should have logged something indicating that the task ran or was missed etc. Also, you said in your original posting that you have the schedule set to run every Wed at 01:00. However, you are now saying that is says the next run time is for the 2nd Wed of April, which implies that you have it set to run monthly, not weekly. Not sure if that has something to do with the issue or not, but I’m highlighting it in case. How do you actually have it set? To run on the 2nd Wed of every month?

Thanks,

Doug

[doug]

Andreas – Thank you for this information! It’s very helpful to know that the issue is/was specifically related to a driver package for Win 10.

However, unfortunately at the moment this does not appear to be something that we can “fix” per se. The issue is not in BatchPatch. The issue is that a corrupt search result is being returned by the WSUS server, and we are not able to process/parse this corrupt search result. At this time we simply do not have a way to code around the problem. The only solution at present is to fix the issue on the WSUS side. If this changes at any time, I will post more info to this thread.

Thanks again,

Doug

[doug]

Troubleshooting common errors in BatchPatch

[doug]

It sounds to me like you did not enable the scheduler. After you schedule a date/time for a task to run you have to also enable the scheduler, which is not enabled by default. Please have a look at the following page, which explains in more detail how to use the task scheduler.

Using the task scheduler in BatchPatch

[doug]

Error 1611: 1072. Failure

---

ERROR_SERVICE_MARKED_FOR_DELETE

1072 (0x430)

The specified service has been marked for deletion.

---

I have never seen this reported by BatchPatch. I suspect that Windows is talking about the PsExec service (PSEXESVC) in this instance having been marked for deletion. You could probably confirm that by trying to execute psexec at the command line against that machine. So for example you could run something like:

psexec \targetComputer IPCONFIG

To resolve the problem my guess is that if you simply reboot the machine(s) in question, when it/they come back up after reboot it/they will behave normally. Let me know how it goes.

-Doug

[doug]

Thanks, Andreas. Yes, please let me know if you run into this problem again in the future. I don’t think it’s likely that it will occur again, but you never know. We have a lot of customers using the software with Windows 10 and with no problems at all. Additionally, in our lab, we have never experienced the issue. That said, it’s unclear why the issue has occurred for the few customers who have posted to this thread, including yourself.

-Doug

[Author]

Posts