Universal Print Connector unable to registert

Steel Contributor

Hi,

today i wanted to make some first steps with the Universal Print Feature.

Therefore i've read through the prerequisites and tried to install the Universal Print Connector onto a machine. (I've tried different ones).

The installation was working fine, afterwards i've started the software, logged in with administrative credentials, typed in a Connector name and hit "register". 

Now the following error popped up:

PatrickF11_1-1617782686578.png

 

The last Eventlog item stated the following error:

EventID 8

Register connector start: LMPrint
Sending connector registration request... Done 

Checking Registration status...
StatusCode: 500, ReasonPhrase: 'Internal Server Error', Version: 1.1, Content: System.Net.Http.StreamContent, Headers:
{
  Transfer-Encoding: chunked
  X-Content-Type-Options: nosniff
  X-MSEdge-Ref: Ref A: 9E743355D74C45BE9F8B05C81A343E73 Ref B: VIEEDGE1913 Ref C: 2021-04-07T07:53:52Z
  Cache-Control: no-store, must-revalidate, no-cache, max-age=0
  Date: Wed, 07 Apr 2021 07:53:52 GMT
  Content-Type: application/json; charset=utf-8
}

Before this there were some other error entrys. (EventID 8, 1 & 2)

The first EventID8

Failed to get valid connector registration status StatusCode: 500, ReasonPhrase: 'Internal Server Error', Version: 1.1, Content: System.Net.Http.StreamContent, Headers:
{
  Transfer-Encoding: chunked
  X-Content-Type-Options: nosniff
  X-MSEdge-Ref: Ref A: 46482393AAE84754943C880672969CAF Ref B: VIEEDGE1913 Ref C: 2021-04-07T07:52:36Z
  Cache-Control: no-store, must-revalidate, no-cache, max-age=0
  Date: Wed, 07 Apr 2021 07:52:35 GMT
  Content-Type: application/json; charset=utf-8
} {"error":"service_error","error_description":"Failed to register the device with the ADRS. Status: BadRequest, Error: {\"ErrorType\":\"UnknownError\",\"Message\":\"Either objectSid or objectGuid should be set.\",\"TraceId\":\"3840065e-b3e6-4454-9ad9-3726ed10551d\",\"Time\":\"04-07-2021 7:52:32Z\"}","registration_id":"47f13c65-d2b0-46b5-904e-3b57d8af0886","http_status_code":500}

One of the EventdIDs 1

Retry 4 Exception: StatusCode: 500, ReasonPhrase: 'Internal Server Error', Version: 1.1, Content: System.Net.Http.StreamContent, Headers:
{
  Transfer-Encoding: chunked
  X-Content-Type-Options: nosniff
  X-MSEdge-Ref: Ref A: 05C88060B428496A8BFDCF20FAD5FEB9 Ref B: VIEEDGE1913 Ref C: 2021-04-07T07:53:27Z
  Cache-Control: no-store, must-revalidate, no-cache, max-age=0
  Date: Wed, 07 Apr 2021 07:53:26 GMT
  Content-Type: application/json; charset=utf-8
}

And the #2

Retry Failure: StatusCode: 500, ReasonPhrase: 'Internal Server Error', Version: 1.1, Content: System.Net.Http.StreamContent, Headers:
{
  Transfer-Encoding: chunked
  X-Content-Type-Options: nosniff
  X-MSEdge-Ref: Ref A: 9E743355D74C45BE9F8B05C81A343E73 Ref B: VIEEDGE1913 Ref C: 2021-04-07T07:53:52Z
  Cache-Control: no-store, must-revalidate, no-cache, max-age=0
  Date: Wed, 07 Apr 2021 07:53:52 GMT
  Content-Type: application/json; charset=utf-8
}

 

At this moment i absolutely don't know why this happen.

  • DotNet is up to date. (on some devices 4.7.2, on another device 4.8)
  • Server 2019, Windows 10 20H2
  • Server was onprem joined, Win10 Client was AAD Only
  • The User is licensed with Office E5 and Win10 E5 (In the service plan details is no "Universal Print" visible, is this correct?)
  • The Azure Universal Print Portal shows, that we have a number of printjobs available, so this should work.

Any help is highly appreciated. :)

5 Replies
Hi Patrick - I request you to reach out to Microsoft Support team and log a new case. You can open a case through Azure Support portal, or by going to Universal Print portal (https://aka.ms/UPportal) and then clicking on help / Get Support option.

Thanks
Saurabh

@PatrickF11 Were you able to solve the issue? I have the same error and no clue about the cause. 

@TobiasAT unfortunatelly not. :\
To be honest i've totally forget about this topic.

@PatrickF11@TobiasAT - If you are having this issue, I recommend two things:

  1. Download the latest connector from https://aka.ms/UPConnector.
  2. If problem persists, contact Microsoft Support via Azure Support portal.

Thanks,

Saurabh

 

@PatrickF11 I had the same problem and I totally understand that MS is not the fan of ccleaner because of changing the registry but I used the free version and ran the Registry cleaner few times untill nothing showed up as a problem and it resolved this issue on my Application Event log, it does not show as an error anymore, again it's your call if you want to use it or not.