Print Jobs not stable

%3CLINGO-SUB%20id%3D%22lingo-sub-1640656%22%20slang%3D%22en-US%22%3EPrint%20Jobs%20not%20stable%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1640656%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20All%2C%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20am%20facing%20some%20trouble%20with%20getting%20Universal%20Print%20to%20work%20properly%20so%20I%20can%20enroll%20it%20to%20our%20organisation.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20main%20issues%20I%20am%20facing%20are%20having%20to%20do%20with%20the%20actual%20printing%20the%20connector%20now%20work%20without%20issues%20and%20I%20can%20register%20the%20printers%20without%20issue%20also.%20But%20as%20soon%20as%20I%20start%20printing%20I%20am%20facing%20random%20issues.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ELast%20week%20the%20prints%20went%20perfect%20for%20myself%20and%20the%20test%20printer.%20So%20I%20decided%20to%20add%20another%20printer%20which%20is%20in%20another%20physical%20network%20to%20see%20if%20I%20could%20also%20print%20there.%20This%20resulted%20in%20the%20print%20getting%20automatically%20aborted%20by%20the%20Windows%20Print%20Queue%20and%20also%20in%20Universal%20Print.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFrom%20that%20point%20on%20I%20tested%20the%20old%20printer%20again%20that%20was%20working%20fine%20and%20I%20had%20the%20same%20results%20all%20the%20jobs%20get%20aborted.%26nbsp%3B%3C%2FP%3E%3CP%3E%3CBR%20%2F%3ESeeing%20as%20that%20was%20Friday%20I%20figured%20lets%20try%20it%20again%20after%20the%20weekend%20maybe%20something%20has%20changed%20and%20indeed%20it%20has.%20All%20of%20a%20sudden%20my%20print%20jobs%20now%20stay%20pending.%20Windows%20says%20it%20has%20been%20send%20to%20the%20printer%20and%20universal%20print%20says%20it%20is%20pending.%26nbsp%3B%3C%2FP%3E%3CP%3E%3CEM%3EI%20am%20currently%20on%20the%20same%20network%20as%20the%20printer%20I%20am%20testing%20with.%20%3C%2FEM%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20happened%20before%20and%20at%20that%20point%20I%20registered%20the%20printers%20again%20with%20an%20update%20of%20the%20PrintConnectorApp.%20From%20that%20point%20it%20worked%20for%20a%20few%20days%20and%20then%20all%20of%20the%20above%20happened.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20can%20I%20do%20to%20figure%20out%20where%20the%20issue%20is%3F%20Cause%20the%20main%20think%20I%20am%20lacking%20is%20feedback%20of%20what%20goes%20wrong%20so%20I%20can%20try%20to%20fix%20it.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20in%20advance!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EKind%20Regards%2C%26nbsp%3B%3C%2FP%3E%3CP%3EJohny%20de%20Koning%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1643210%22%20slang%3D%22en-US%22%3ERe%3A%20Print%20Jobs%20not%20stable%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1643210%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F733652%22%20target%3D%22_blank%22%3E%40Johny_de_Koning%3C%2FA%3E%26nbsp%3Bsorry%20to%20hear%20about%20your%20experience.%20What%20version%20of%20connector%20are%20you%20on%3F%20Is%20it%20same%20as%20the%20latest%20version%20on%20%3CA%20href%3D%22https%3A%2F%2Faka.ms%2FUPConnectorMSI%3F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Faka.ms%2FUPConnectorMSI%3F%3C%2FA%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%0A%3CP%3EIf%20system%20continue%20to%20be%20unstable%2C%20I%20recommend%20you%20to%20reach%20out%20to%20Microsoft%20Support%20via%20Azure%20Support%20portal.%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fms.portal.azure.com%2F%23blade%2FMicrosoft_Azure_Support%2FHelpAndSupportBlade%2Fnewsupportrequest%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fms.portal.azure.com%2F%23blade%2FMicrosoft_Azure_Support%2FHelpAndSupportBlade%2Fnewsupportrequest%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThanks%2C%3C%2FP%3E%0A%3CP%3ESaurabh%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1643267%22%20slang%3D%22en-US%22%3ERe%3A%20Print%20Jobs%20not%20stable%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1643267%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F572522%22%20target%3D%22_blank%22%3E%40Saurabh_Bansal%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you%20for%20the%20mail%20the%20version%20of%20the%20connector%20was%201.4%20and%20I%20just%20updated%20it%20to%201.10%20but%20the%20result%20is%20still%20the%20same.%20There%20is%20nothing%20currently%20printing%20they%20all%20stay%20at%20pending.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20there%20anywhere%20I%20can%20find%20some%20information%20of%20what%20is%20wrong%3F%20Cause%20I%20haven't%20really%20seen%20any%20logs%20or%20feedback%20or%20so%2C%20but%20I%20just%20might%20be%20missing%20it.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you%20again.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EKind%20Regards%2C%26nbsp%3B%3C%2FP%3E%3CP%3EJohny%20de%20Koning%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1651883%22%20slang%3D%22en-US%22%3ERe%3A%20Print%20Jobs%20not%20stable%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1651883%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F572522%22%20target%3D%22_blank%22%3E%40Saurabh_Bansal%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20raised%20a%20ticket%20thank%20you%20so%20far.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1655207%22%20slang%3D%22en-US%22%3ERe%3A%20Print%20Jobs%20not%20stable%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1655207%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F733652%22%20target%3D%22_blank%22%3E%40Johny_de_Koning%3C%2FA%3E%26nbsp%3BI%20would%20like%20assistance%20too%20this%20is%20really%20impacting%20my%20company%20now%20we%20have%20deployed%20a%20very%20large%20group%20of%20printers%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1656008%22%20slang%3D%22en-US%22%3ERe%3A%20Print%20Jobs%20not%20stable%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1656008%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F642062%22%20target%3D%22_blank%22%3E%40CSanchez1285%3C%2FA%3E%26nbsp%3Bwhen%20I%20get%20a%20reply%20from%20the%20ticket%20that%20solves%20the%20issue%20I%20will%20let%20it%20be%20known%20here%20so%20others%20might%20use%20the%20information.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

Hi All, 

 

I am facing some trouble with getting Universal Print to work properly so I can enroll it to our organisation. 

 

The main issues I am facing are having to do with the actual printing the connector now work without issues and I can register the printers without issue also. But as soon as I start printing I am facing random issues. 

 

Last week the prints went perfect for myself and the test printer. So I decided to add another printer which is in another physical network to see if I could also print there. This resulted in the print getting automatically aborted by the Windows Print Queue and also in Universal Print.

 

From that point on I tested the old printer again that was working fine and I had the same results all the jobs get aborted. 


Seeing as that was Friday I figured lets try it again after the weekend maybe something has changed and indeed it has. All of a sudden my print jobs now stay pending. Windows says it has been send to the printer and universal print says it is pending. 

I am currently on the same network as the printer I am testing with.

 

This happened before and at that point I registered the printers again with an update of the PrintConnectorApp. From that point it worked for a few days and then all of the above happened.

 

What can I do to figure out where the issue is? Cause the main think I am lacking is feedback of what goes wrong so I can try to fix it. 

 

Thanks in advance!

 

Kind Regards, 

Johny de Koning

8 Replies

@Johny_de_Koning sorry to hear about your experience. What version of connector are you on? Is it same as the latest version on https://aka.ms/UPConnectorMSI?

If system continue to be unstable, I recommend you to reach out to Microsoft Support via Azure Support portal.

https://ms.portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/newsupportrequest

 

Thanks,

Saurabh

 

@Saurabh_Bansal 

 

Thank you for the mail the version of the connector was 1.4 and I just updated it to 1.10 but the result is still the same. There is nothing currently printing they all stay at pending. 

 

Is there anywhere I can find some information of what is wrong? Cause I haven't really seen any logs or feedback or so, but I just might be missing it.

 

Thank you again.

 

Kind Regards, 

Johny de Koning

@Johny_de_Koning - we will really love for you to file a Azure Support ticket as per the link provided earlier, and help troubleshoot the issue.

@Saurabh_Bansal 

 

I have raised a ticket thank you so far.

@Johny_de_Koning I would like assistance too this is really impacting my company now we have deployed a very large group of printers

@CSanchez1285 when I get a reply from the ticket that solves the issue I will let it be known here so others might use the information. 

@CSanchez1285 The issue for us was that I removed the local printers from the machine with the Connector. And by doing that there is no connection from Azure to the printer (this goes through the connector). 

 

As soon as I installed the printer again and waited a few hours for everything to sync it worked again. So now I am going to get a dedicated machine for the test where I just leave everything on. 

 

If this doesn't solve the issue I suggest you raise a request.

I@Johny_de_Koning I was able to talk to a rep and it turns out the Print drivers needed to be updated as this was causing major issues. If anyone sees this update to the latest drivers (mine were all HP machines) and this resolved it! There a method to update the drivers in microsoft universal print driver documentation.