Forum Discussion
Procedure for diagnosing failure to print?
Hi Jimmy_Wu , how does badge release work? I would imagine that would require a high-end MFC printer with that specific capability? Unless universal print offers something I'm yet unaware of that runs on some other device that can be placed near a generic printer...
The reason for not using dirsync is that it makes many things a pain. With dirsync enabled, I'm unable to change things such as aliases from o365. As we do not use onsite exchange server, there really is no good way to edit those locked attributes with dirsync on. At least that was how things operated since I last used it, which was within the past year I think.
So I guess the solution here is to use an onsite VM running the connector, which isn't joined to AAD nor ADDS?
MicrosoftNetFire, sounds like your printer doesn't need the user account/ID, so yes, just setup a workstation PC that's not domain joined or AADJ to host the Connector. It can be a VM or a real hardware.
- Rani_Abdellatif
We mitigated an issue relating to printer sharing. Please try again and let us know is this still doesn't work for you.
Rani_Abdellatif I tried with two unique share names, and it did not work. I downloaded the latest connector, but I'm not sure if I need to uninstall the old one first? I launched the new .msi and was prompted to repair or uninstall. I chose repair, but the version did not seem to get updated.
- Rani_Abdellatif
NetFire
To get most likely causes out of the way, does the share name you chose already exist (i.e. is there another printer share with the same name)?As for the connector update, did you download the latest MSI from http://aka.ms/ConnectorMSI and it doesn't upgrade?
I'm having another issue when attempting to share a printer that has been successfully registered. This is an identical model printer to the others that are working fine, with identical firmware, on the same network, with the same driver. When I attempt to share the printer, universal print throws a very non-descript "Printer Sharing Failed" error. The event logs for the connector show the following (although I'm not sure if these correlate to this issue):
System.Printing.PrintQueueException: An exception occurred while populating the properties for the PrintQueue object. Win32 error: The printer name is invalid. at System.Printing.PrintQueue.Initialize(PrintServer printServer, String printQueueName, String[] propertiesFilter, PrinterDefaults printerDefaults) at System.Printing.PrintQueue..ctor(PrintServer printServer, String printQueueName) at ProxyLibrary.JobStatusUpdater.<CheckStatus>d__16.MoveNext()Any ideas for me? I noted that I am on connector v0.20.7380.21779, however I see that v0.20.7380.21783 is available for download. I tried to update the existing one by launching the msi and doing a "repair", however it did not update the connector. How would I go about updating the connector while keeping all existing preferences and connections intact.
