Error Code 1723: Rpc Server Is Too Busy To Complete This Operation S’abonner

0
Avatar
Legacy Poster

We constantly have Commander stop working after a little while.

Stopping and restarting the Detection seem to solve the problem but this is annoying!

 

The error that I see from the History Explorer shows Windows error code is 1723 and the error message is "The RPC server is too busy to complete this operation." No events are logged to Windows Event Viewer.

 

The commander is running as a system service on a Windows 7 vm and the Bartender version is 10.0 SR2.

 

Printers are locally installed (using IP address as ports) and also using shared network printers (//Serername/Printername)

 

 

Any clues?

9 commentaires

0
Avatar
Ian Cummings
Modérateur
Actions pour les commentaires Permalien

0
Avatar
Legacy Poster
Actions pour les commentaires Permalien

Thanks for your reply.

 

Does SR4 address this specific issue? as I don't see any details about it...

0
Avatar
Ian Cummings
Modérateur
Actions pour les commentaires Permalien

Yes!

0
Avatar
Legacy Poster
Actions pour les commentaires Permalien

Bartender suite has been updated to SR4 and now Commander is running as an Application...

and still receive this error... RPC server is too busy to complete this operation.

 

What can I do? How to Fix?

0
Avatar
Domingo Rodriguez
Modérateur
Actions pour les commentaires Permalien

Could you open Intermet Explorer "Internet Options" on this PC while being logged on Windows with the same account under which you use Commander, then select the "Advanced" tab and uncheck the "Check for publisher's certificate revocation" checkbox. Restart Commander and let me know if you still get the same issues.

0
Avatar
Legacy Poster
Actions pour les commentaires Permalien

so far so good... havent got this error anymore. :)

0
Avatar
Domingo Rodriguez
Modérateur
Actions pour les commentaires Permalien

Did the error seem to have disappeared after unchecking the "Check for publisher's certificate revocation" checkbox?

0
Avatar
Legacy Poster
Actions pour les commentaires Permalien

yes, so far we haven't got that error yet... but another issue came up after we updated the license info to include more printers...

The History Explorer doesn't log the print jobs anymore.

0
Avatar
Domingo Rodriguez
Modérateur
Actions pour les commentaires Permalien

Please report this into a different topic, and include as many details as possible, such as is the BarTender System database running and enabled, under which account is the "BarTender System" Windows service running...

http://www.bartenderbarcodesoftware.com/label-software/training-video-(setting-up-a-system-database).aspx

 

If you prefer to write us an email or contact support by telephone:

http://www.bartenderbarcodesoftware.com/label-software/technical-support.aspx#contact

Vous devez vous connecter pour laisser un commentaire.