We have a single user with 1 workstation that periodically has problems printing.
The user is printing to WIN:/IP_###.###.###.###
Generally speaking the print job works perfectly.
Occasionally the print job simply doesn’t print.
The user noticed that this “Pop-Up Window” that says printing to windows does not happen in these cases.
We also found that the WBSPL###.## does not get delete, and it contains the print job.
My thought is that when we issue CLOSE#255: some windows error is causing the print job to fail, but we don’t have any way to know there was a problem.
Strange problems with printing are sometimes resolved by going into the Antivirus program and exclude the BR folder, and other associated folders that BR uses,
and
the C:\windows\system32\spool directory.
Norton, LightSpeed, TrendMicro especially have this abnomally.