Forum Discussion
Universal print connector "ErrorCode": "-2146233033",
Hello
we er deploynig the universal print connector to rigster our On prem printres that not support direct connect to azure .
som of the priters rigsterd and deployed and the users has acess but when they try to print , they get the print faild . and in azure status i aborted . at the event logg show this error message
the printer is coneccted wifi
, added to our print server working fine with local on prem Pcs
server windows 2016 fully updated
any idea ?
error message
Merging/validating the job print ticket failed with error "Validating print ticket(s)for ................. Reading input files C:\ProgramData\Microsoft\UniversalPrintConnector\PrinterCapabilities\...........-............._PT.xml, C:\WINDOWS\TEMP\tmpE0F1.tmp timing: Open provider time (ms): 32 timing: MergAndValidate time (ms): 78 Validation failed with hresult 80004005, description: (null) timing: Close provider (ms): 0 Service failed to merge and validate print ticket w/err 0x80004005 " and exception: { "Level": 1, "Type": "System.FormatException", "ErrorCode": "-2146233033", "Message": "PrintTicket XML er ikke korrekt utformet. Rotelementet mangler.", "StackTrace": " ved ProxyLibrary.PrintTicketTransformer.GetMergedPrintTicket(PrintTicket defaultPrintTicket, PrintTicket printerCompatiblePrintTicket, IPrinter printer, String& validationErrorMessage)\r\n ved ProxyLibrary.PrintTicketTransformer.GetPrinterCompatibleJobPrintTicket(IPrinter printer, String jobIdString, IppAttributeGroup jobAttributeGroup, PrintTicket jobPrintTicket, String& errorMessage)", "InnerException": { "Level": 2, "Type": "System.Xml.XmlException", "ErrorCode": "-2146232000", "Message": "Rotelementet mangler.", "StackTrace": " ved System.Xml.XmlTextReaderImpl.Throw(Exception e)\r\n ved System.Xml.XmlTextReaderImpl.ParseDocumentContent()\r\n ved System.Xml.XmlLoader.Load(XmlDocument doc, XmlReader reader, Boolean preserveWhitespace)\r\n ved System.Xml.XmlDocument.Load(XmlReader reader)\r\n ved System.Xml.XmlDocument.Load(Stream inStream)\r\n ved MS.Internal.Printing.Configuration.InternalPrintTicket..ctor(Stream xmlStream)" } } |
Best Regards
- hello Thanks for you answer , thi topic fixed the error
https://learn.microsoft.com/en-us/universal-print/fundamentals/universal-print-known-issues#event-9-merge-ticket-errors-in-print-connector-event-log
5 Replies
- keeronBrass Contributor
Thaer_Badawi Can you let us know which driver you are using on the Connector machine (that was showing this error during printing)?
As the earlier suggestion indicated, please try upgrading the driver to the latest version or if the manufacturer has a 'universal' driver (and not printer/model specific) one, try to use that. Remember to follow steps mentioned here when changing driver on existing UP Connector printer: https://learn.microsoft.com/en-us/universal-print/fundamentals/universal-print-updating-printer-driver-howto
If this approach doesn't work, you may have to reach out to our customer support (https://aka.ms/upsupport-azureportal). Customer support engineers can help guide you to setup the Connector configuration such as the driver can be used, if possible.
- Thaer_BadawiCopper Contributor
hello Thanks for you answer this topic was the answer
https://learn.microsoft.com/en-us/universal-print/fundamentals/universal-print-known-issues#event-9-merge-ticket-errors-in-print-connector-event-log
- AndreasAsanderIron ContributorTry to unregister the queue that doesn't work in the universal print portal.
Then change the driver to another supported driver, i.e. if you are using PostScript change to PCL.
If you are using v4 try changing to v3 or vice versa.
Re-register the printer to the portal.
Try to print again.- Thaer_BadawiCopper Contributorhello Thanks for you answer , thi topic fixed the error
https://learn.microsoft.com/en-us/universal-print/fundamentals/universal-print-known-issues#event-9-merge-ticket-errors-in-print-connector-event-log- keeronBrass Contributor
Thanks Thaer_Badawi , that was going to be my next link if you were using the Brother printer driver. Glad this worked out!