Error message Bookings Automate
Hi all, For my current position I use MS Bookings to have customers book appointments for training dates. I then use Automate to register this information to a SP list. I used to use a workaround, but since the Bookings connector was released it seems to not contain all the necessary information it used to before. Using the new connector i get the following error message I've seen others post as well, but haven't seen a resolution yet. Staff not part of the booking mailbox. I am however the sole owner of the bookings calendar as well as the admin on the Automate flow. Can anyone help shed a light on this?MS Teams - Unable to delete connector in inactive/term employee account
re: https://answers.microsoft.com/en-us/education_ms/forum/all/ms-teams-unable-to-delete-connector/e4df9a9c-f262-43d7-bacb-92feb34acad7?page=2 I have this exact same situation. 1. An active account employee (ie, Bob) created connector in a team channel. 2. Bob leaves the company. 3. Bobs Connectors still exist within the team channel. However, Team channel admins are unable to delete... I am able to replicate this error on the thick client, and the web app.Universal Print Connector unable to registert
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: 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. 🙂
