Windows Update causing BarTender errors Follow
Overview
There is an issue printing from all BarTender versions if Microsoft Windows Updates from August 9, 2016 are installed.
Latest Update
2 September 2016, 12:16pm PST: Microsoft has released updates that resolve this issue for all affected operating systems and all updates have been tested by Seagull Scientific. Please see the “Recommended Solution” section on this page for more details.
If you would like to be notified when this page is updated please "Follow" the Community post Notifications for "Windows Update causing BarTender errors."
Windows Updates that cause printing problems
Microsoft has acknowledged this problem in the Known Issues section of the articles below:
"After you apply this security update and you print multiple documents in succession, the first two documents may print successfully. However, the third and subsequent documents may not print."
Security Update for Microsoft Windows (KB3177725)
Security Update for Microsoft Windows (KB3176493)
Symptoms
Applies to: All BarTender versions
BarTender will print 2-3 jobs successfully and then throw one or more of the following BarTender or Windows errors. The error message you receive may vary based on your unique environment.
BarTender Errors
Error 3700
BarTender cannot use printer '<printer name>' to design, print or export a document due to a printer setup problem.
Error 3721
BarTender cannot use printer '<printer name>' to design, print, or export a template due to a printer setup problem.
A Windows error code was returned: <data>
Error message: <data>
Windows Errors
Error 995
Error_Operation_Aborted
The I/O operation has been aborted because of either a thread exit or an application request.
Error 1804
Error_Invalid_Datatype
The specified datatype is invalid.
Error 122
Error_Insufficient_Buffer
The data area passed to a system call is too small.
Recommended Solution
Microsoft has released updates that resolve this issue on all affected operating systems. Please download and install the update specific to your operating system. All of these solutions have been tested by Seagull Scientific.
Windows 10 version 1607
Installing KB3176938 resolves this issue. Install the update using Windows Update or download it from the Microsoft Update Catalog (site requires Internet Explorer 6.0 or later; other browsers are not supported).
Windows 10 version 1511
Installing KB3186988 resolves this issue. Microsoft has informed us that this update will not be available through Windows Update until mid-September. You can download and install it from the Microsoft Update Catalog (site requires Internet Explorer 6.0 or later; other browsers are not supported).
Windows 7, Windows 8.1, Windows Vista, Server 2008, Server 2012, Server 2012 R2
Installing KB3185911 resolves this issue. Microsoft has informed us that this update will not be available through Windows Update until mid-September. You can download and install it from the Microsoft Update Catalog (site requires Internet Explorer 6.0 or later; other browsers are not supported).
Note: Please check the pre-requisites section here before installing this update.
Alternative Solutions
Modify BarTender setting for each printer
Applies to: BarTender 2016, v10.1
When "Use new device context for each print job" is enabled, BarTender can print without issue with the Windows Updates installed. This setting may impact performance in high volume printing. Visit Use new device context for each print job for instructions.
Remove the update from the affected system
Applies to: Windows 10, Windows 8.1, Windows 7, Windows Server 2012 R2, Windows Server 2012, and Windows Server 2008 R2
The issue appears to be directly related to specific Windows Updates from August 9, 2016. Uninstalling the appropriate update should allow BarTender to return to normal functionality. Visit How to find and remove a Windows Update for instructions.
Please assess your security needs carefully before deciding whether to uninstall or delay installing these Windows security updates.
Windows Version | Windows Update to remove |
Windows 10 | Security Update for Microsoft Windows (KB3176493) |
Windows 8.1, 7, Server 2012 R2, Server 2012, Server 2008 R2 | Security Update for Microsoft Windows (KB3177725) |
Continuously restart BarTender
Applies to: All versions of BarTender
Restarting BarTender will allow 2-3 print jobs to work before it needs to be restarted again.
38 comments
Paul Hennell
We were having this issue with Bartender not printing and "Windows Error code 122" - but following this post and removing the mentioned updates seemed to fix it.
For anyone else with several machines the following code run as a batch file works pretty well to quickly getting things moving again:
wusa /uninstall /kb:3178034 /quiet /norestart
wusa /uninstall /kb:3177725 /quiet /norestart
wusa /uninstall /kb:3175443 /quiet /norestart
wusa /uninstall /kb:3167679 /quiet /forcerestart
Hope things are resolved with the updates soon!
Edit: This script was written when it was recommended to remove all 4 Aug 9 updates. With the narrowing down of the issue to only the specific updates listed above, it's now likely easier just to remove the appropriate updates manually (Or edit the above script accordingly), and keep/re-install any other updates that arn't causing the problem.
Chris Wineinger
Can I be notified when there's an update/resolution to this problem?
Kai Kohler
Hi Chris,
I opened a ticket for you regarding this issue. You will be notified when we have an update.
Thank you for your patience.
matt mentele
Can I be notified when there's an update/resolution to this problem as well?
Kai Kohler
Hi Matt,
I opened a ticket for you regarding this issue, as well. You will be notified when we have an update.
Thank you for your patience.
David Rodgers
Can I also be notified when there is an update/resolution to this problem?
Jamie Wojcik
I'm wondering if you might want to create a link so people can get on a notification list for when a resolution has been reached. I too would like to be notified. Thank you.
Paul Walker
Please can I be notified about updates to this as well?
Rachel Daugherty
Agreed - please notify me as well. Thank you!
Jared Baszler
Please open a ticket for me as well. While I'm frustrated this happened and I spent a good half day on the issue I'm so grateful an email came out informing us of the issue. Or I would have spent another entire day on the problem. Thanks for the info and the workarounds.
Scott Owart
As per the others, please notify me as well, thanks.
Russell Johnson
The article specifically calls out KB3177725 (note this KB also applies to Windows 8.1), but Paul includes some of the other August updates in his uninstall list. Which is it?
Russell Johnson
We run Bartender Commander as a service on Server 2012 R2. KB3177725 also applies to that OS. Is Commander suffering the same issues?
Ruben Franco
Any news as to when will be fixed? Can I receive some sort of notification with any news related to this update? Thanks.
Kai Kohler
Thank you for your patience. If you would like to be notified when this page is updated please "Follow" the Community post Notifications for "Windows Update causing BarTender errors."
Link to Community post:
https://support.seagullscientific.com/hc/en-us/community/posts/216590067
Kai Kohler
Russell,
1) Paul's instructions remove all the updates from August 9, but further testing showed that only specific updates needed to be removed.
2) Yes, any integration that uses BarTender to print jobs will suffer from this issue (Commander, Integration Builder, Custom SDK application, Print Portal, etc.)
Kevin Smiley
Please notify me when on any updates or when this issue is fixed. Thanks
Russell Johnson
Thanks for the clarification! Precision can't be overvalued...
Faiz
Hi Team
Which version will be impacted?
Bartender 10.1 or above?
Please notify me after problem solves
Kai Kohler
Hi Faiz,
All versions of BarTender are impacted by this issue.
Amos Phoenix
Can I be notified as well when there is a fix available?
Thank you
Carol Shepherd
I would like to be notified as well...
Bryan Luisana
Please notify me when a fix for this issue is found.
Rutger Van Huyssteen
Please notify me as well
F. van 't Hoff
Please notify me as well.
Dan g
Please notify me as well.
Zach Taylor
The following script will run through a list of PC names and remove the update. I have this scheduled to run after our updates are pushed. Don't forget to create your kbremovallog and kbremovallist on C:\.
$Logfile = "C:\kbremovallog.log"
Function LogWrite
{
Param ([string]$logstring)
Add-content $Logfile -value $logstring
}
function Uninstall-Hotfix {
[cmdletbinding()]
param(
$computername = $env:computername,
[string] $HotfixID
)
$hotfixes = Get-WmiObject -ComputerName $computername -Class Win32_QuickFixEngineering | select hotfixid
if($hotfixes -match $hotfixID) {
$hotfixID = $HotfixID.Replace("KB","")
LogWrite ((Get-Date).ToString("MM-dd-yy hh:mm:ss") + " $computername found the hotfix KB$HotfixID.")
LogWrite ((Get-Date).ToString("MM-dd-yy hh:mm:ss") + " $computername uninstalling the hotfix.")
$UninstallString = "cmd.exe /c wusa.exe /uninstall /KB:$hotfixID /quiet /norestart"
([WMICLASS]"\\$computername\ROOT\CIMV2:win32_process").Create($UninstallString) | out-null
while (@(Get-Process wusa -computername $computername -ErrorAction SilentlyContinue).Count -ne 0) {
Start-Sleep -s 5
LogWrite ((Get-Date).ToString("MM-dd-yy hh:mm:ss") + " $computername waiting for update removal to finish ...")
}
LogWrite ((Get-Date).ToString("MM-dd-yy hh:mm:ss") + " $computername Completed the uninstallation of $hotfixID")
Restart-Computer -Force $computername
}
else {
LogWrite ((Get-Date).ToString("MM-dd-yy hh:mm:ss") + " $computername given hotfix($hotfixID) not found")
return
}
}
$pcL = Get-Content c:\kbremovallist.txt
Foreach($pc in $pcL) {
Uninstall-Hotfix -ComputerName $pc -HotfixID KB3177725
}
Zach Taylor
I should add that this does force a reboot, so schedule accordingly.
Faiz
Hi after i remove patch my bartender become crash
Anyone have the same issue
Kai Kohler
Faiz,
We have not had reports of BarTender crashing after removing the appropriate Windows Update. I went ahead and opened a ticket for you with our Technical Support team so they can troubleshoot it.