Print Portal error when opening a Librarian document Follow

Avatar
Laura Vela

Symptom

Error displayed in Print Portal:

"BarTender document XXX does not exist. Please verify the document exists and that a correct path has been provided" 

The log file shows:
2016-03-17 17:00:03.2239 ERROR: PrintController Print: Failed to load document properties for lib://XXX.btw. Status=Failure

2016-03-17 17:00:03.2239 ERROR: PrintController Print: BarTender document lib://XXX.btw does not exist. Please verify the document exists and that a correct path has been provided.

2016-03-17 17:00:03.2239 ERROR: PrintData LoadInitialDocumentProperties: Failed to query document properties for lib://ADF_120V.btw. Error: BarTender document lib://XXX.btw does not exist. Please verify the document exists and that a correct path has been provided.

2016-03-17 17:00:03.2239 ERROR: <Not Available> lambda_method: Printing data is not valid. RootFolderName=Librarian, Relative Path=XXX.btw

2016-03-17 17:00:03.5000 ERROR: ErrorController Default: An error occurred: An error occurred while loading the document lib://XXX.btw. Please try again. Details: BarTender document lib://XXX.btw does not exist. Please verify the document exists and that a correct path has been provided.

Environment

  • Print Portal
  • Librarian
  • Windows credentials for accessing the BarTender System Database
  • IIS account setup with a user account with enough access to the BSDB
  • BarTender System Service setup with a user account with enough access to the BSDB

Fix/Answer

It seems to be due to the impersonation option not working as expected for the Print Scheduler service.

Alternatives:

  • Connect to the BarTender System Database using SQL credentials instead
  • Set up the BarTender Print Scheduler service to run with the same account that is running the Application Pool (or a different user which has enough rights over the BarTender System Database)

More Information (optional)

https://seagull/jira/browse/BUG-1544

* I had a customer affected with this issue that was using BarTender (R3), Windows credentials and the Print Scheduler service running with the same account as the Application Pool that had to re-assign all the accounts to all BarTender Services as the error had appeared again unexpectedly after working fine for a while.

Was this article helpful?

Please sign in to leave a comment.