User Profile
keeron
Former Employee
Joined 6 years ago
User Widgets
Recent Discussions
Re: Universal print connector "ErrorCode": "-2146233033",
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: How To - Change printer driver | Microsoft Learn 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.2KViews0likes1CommentRe: Printing job stuck pending but a restart of Print connecter service gets them printed
Brandon_Emlinger Thanks for that info, that (1.83.8291) version is the latest one so far. For folks hitting this, and where restart of the Print Connector service is helping re-establish the connection with UP or get print jobs working again, I can suggest couple of items. 1. We recently added a sample PowerShell script that helps reset just the individual printer. You can download this on the Connector host machine, (edit it to uncomment the invoke method at the very end), and run it from an elevated PS window. It just takes in the printer name (matching the printer name locally on that Connector machine). There's no service restart involved here, and the impacted is limited to just one printer. This isn't fixing the root cause (we don't know the issue yet), but is a better alternative than performing a restart on the Print Connector service and potentially impacting other printers/users. 2. For finding the root cause, I would suggest reaching out to our Azure Support and filing a support case - https://aka.ms/upsupport-azureportal Our support team can guide you in collecting the required information. Hopefully once the issue is identified, you won't have to reset the printer (or the service).9.9KViews0likes1CommentRe: Printing job stuck pending but a restart of Print connecter service gets them printed
Brandon_Emlinger what version of the connector are you using? At the moment, 1.83 is the latest. If you're using an older version, please update your connetor: https://aka.ms/UPConnector. If you're seeing the same behavior on the latest version, please let us know.9.1KViews0likes3CommentsRe: Error occurred while registering the connector
Adam Weldon-Ming we have a canary/pre-release version of Connector with a few fixes, including this crash. Can you try upgrading to it via https://aka.ms/ConnectorMSI-Canary and trying to run the Connector again? Please let us know if you see any issues or if it ends up resolving the issue you were seeing earlier. Thanks2.7KViews2likes1CommentRe: 2 print queues using the same printer are failing to register
Holger Luebsen When this 2nd printer fails to register, does the Connector event log say something to the effect of "device_already_exists"? Also, how are these 2 print queues installed on the Connector machine?2.3KViews0likes0CommentsRe: Unregister printer fails after printer rename
Holger Luebsen Was the printer queue renamed from the Connector machine, or from the Azure Portal? Suggestion is to restart the PrintConnectorSvc (Print Connector service). There's a known issue where the Connector may not pick up the renamed print queue. Let us know if this resolves the issue1.2KViews0likes0CommentsRe: Printer registration error
bandelj The error appears to be related to TLS 1.2. The Connector uses that as our Universal Print service requires it. It might be that the TLS 1.2 needs to be configured on this Windows Server. A few things to check, and then instructions on how to enable/verify this: 1. Is the operating system updated (as far as security patches go)? 2. Have you explicitly disabled TLS 1.2 on the server? If no, below might help To enable TLS 1.2: Set the following registry keys: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2] [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Client] "DisabledByDefault"=dword:00000000 "Enabled"=dword:00000001 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Server] "DisabledByDefault"=dword:00000000 "Enabled"=dword:00000001 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319] "SchUseStrongCrypto"=dword:00000001 Restart the server.3KViews0likes2CommentsRe: Removing Universal Print
dnakanishi as mentioned above, the ability to remove the Connector isn't yet available. So for now, you'll have the old connector reference show up in the Azure Portal. We are also working on adding the Connector health in future. For now, my suggestion is to look at the individual printer's status, as well as whether the jobs in each printer's queue are being processed (for example if you see jobs stay "Pending" for a while, or "Aborted", it is likely that something is not correct on the Connector) If you have a specific suggestion on what type of health status or alerts would help regarding the Connector, I'd suggest posting them in our feedback section here.6.7KViews1like1CommentRe: No available printers - how do I register printers?
arildg Thanks for the details, I believe the Smart Print queues are not local connections on the machine where Connector is installed. Connector only support local print queues (i.e. installed via WSD, TCP, or USB port). What is the 'type', 'shared', and 'published' values if you run this in Powershell: Get-Printer -name YOUR_PRINTER_NAME If this is a local print queue and the Connector is still unable to show it, my suggestion is to get in touch with our support folks. Do you have a Microsoft support plan? You can report this issue (and the details mentioned here) through Help + support in the Azure Portal, Support for business, or Services Hub.7.2KViews0likes5CommentsRe: No available printers - how do I register printers?
arildg Thanks for trying out Universal Print. The printer installed on the Windows Server machine (where the Connector is installed) may not be supported by Universal Print. Try the following steps: * Refresh the list of printers in the print connector app * Open up the event log (shortcut is Start -> Run -> eventvwr /c:microsoft-windows-printconnector ) * It should have enumerated over the printers locally installed and told you the reason why something was skipped. Depending on the answer, we can point you to support or perhaps clarify here why the printer was skipped.7.2KViews0likes7CommentsRe: Adding Tenant-Guests to the Printers?
Mirko Colemberg We don't currently support guest printing. Sorry for the unnecessary troubleshooting 🙂 The best way to help us land this feature as soon as possible is to submit the idea on our Feature Requests page so that we can prioritize it! We check this section often, and actively use it to prioritize what we're working on.873Views0likes1CommentRe: Printer registration fails
_dibi_ Thanks for the details, that may explain the crash The Universal Print connector must be installed on a virtual or physical machine running Windows 10 Pro or Enterprise version 1809 (OS Build 17763) or later. For Server SKUs, it must be Windows Server 2016 or later. For more reference: https://docs.microsoft.com/en-us/universal-print/fundamentals/universal-print-connector-installation#prerequisites1.3KViews1like0CommentsRe: CanonUDprint
jeroenjacobs Connector skips certain types of printers that are not compatible with Universal Print (for various reasons). If you open up the event viewer (Connector logs specifically), you should be able to find your printer name in there with a message stating why it was skipped. Let us know if you see that what the reason was. Start -> Run -> eventvwr /c:microsoft-windows-printconnector/operational1KViews1like1CommentRe: Removing Universal Print
Jakub Piesik thank you for the feedback. We are tracking this internally as well. You are correct in that you can uninstall the Universal Print Connector software, although it will still show the Connector as registered in the Universal Print Portal. We are looking into allowing customers to unregister the connector if/when needed. Let us know if you are blocked on this and we can work with you offline to provide a workaround.7.8KViews0likes4Comments
Recent Blog Articles
No content to show