You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: support/entra/entra-id/user-prov-sync/fail-connect-azure-information-protection-powershell.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,7 +24,7 @@ When you try to connect to Microsoft Azure Information Protection using Windows
24
24
>
25
25
> `Connect-AipService : The attempt to connect to the Azure Information Protection service failed. Verify that the user name and password you are using are correct and try again. If you have continued problems, see http://go.microsoft.com/fwlink/?LinkId=251909.`
26
26
>
27
-
> `The correlation ID is 1df4c755-f859-4284-907b-be5d2a551260. Please note and provide this value if asked by support for it.`
27
+
> `The correlation ID is aaaa0000-bb11-2222-33cc-444444dddddd. Please note and provide this value if asked by support for it.`
Configuration Manager clients that report to a particular server or subset of servers may repeatedly become inactive. You may also notice that the clients do not send inventory information for 30 days or more and that the data in the Inventoryagent.log file is static. Additionally, the ClientIDManagerStartup.log displays repeated occurrences of this error:
18
18
19
-
> [RegTask] - Client is not registered. Sending registration request for GUID:4874BD6C-CB98-4EEB-9F4F-721CC65B25C3 ...
19
+
> [RegTask] - Client is not registered. Sending registration request for GUID:00001111-aaaa-2222-bbbb-3333cccc4444 ...
20
20
>
21
-
> [RegTask] - Client is registered. Server assigned ClientID is GUID:4874BD6C-CB98-4EEB-9F4F-721CC65B25C3. Approval status 1
21
+
> [RegTask] - Client is registered. Server assigned ClientID is GUID:00001111-aaaa-2222-bbbb-3333cccc4444. Approval status 1
During content download, there are intermediate state messages sent to the MP which include the download percentage. To see all available State IDs, see [Advanced troubleshooting tips for Content Distribution](advanced-troubleshooting-tips.md).
945
945
@@ -959,8 +959,8 @@ After sending the **Success** state message, pull DP clears the job states for t
@@ -972,7 +972,7 @@ Note that verbose and debug logging should be enabled on the MP to see above log
972
972
After the state message SMX file arrives in the `StateSys.box\incoming` directory, State System component on the site server processes the message. All state messages are processed by calling `spProcessReport` stored procedure. For pull DP state messages, `spProcessReport` calls `spProcessPullDPMessage` which updates the `PullDPResponse` table with the state message details.
> SMS_STATE_SYSTEM 23544 (0x5bf8) CMessageProcessor - the cmdline to DB exec dbo.spProcessStateReport N'?\<Report>\<ReportHeader>\<Identification>\<Machine>\<ClientInstalled>0\</ClientInstalled>\<ClientType>1\</ClientType>\<Unknown>0\</Unknown>\<ClientID IDType="0" IDFlag="1">925b0ab0-247b-466b-be0f-93d7cb032c87\</ClientID>\<ClientVersion>5.00.0000.0000\</ClientVersion>\<NetBIOSName>P01PDP1.CONTOSO.COM\</NetBIOSName>\<CodePage>437\</CodePage>\<SystemDefaultLCID>1033\</SystemDefaultLCID>\</Machine>\</Identification>\<ReportDetails>\<ReportContent>StateMessage\</ReportContent>\<ReportType>Full\</ReportType>\<Date>20190107200618.000000+000\</Date>\<Version>1.0\</Version>\<Format>1.1\</Format>\</ReportDetails>\</ReportHeader>~~ \<ReportBody>\<StateMessage MessageTime="20190107200618.000000+000" SerialNumber="3">\<Topic ID="P010000F" Type="902" IDType="0"/>\<State ID="1" Criticality="0"/>\<UserParameters Flags="0" Count="4">\<Param>P010000F\</Param>\<Param>["Display=\\\P01PDP1.CONTOSO.COM\\"]MSWNET:["SMS_SITE=P01"]\\\P01PDP1.CONTOSO.COM\\\</Param>\<Param>{04AD1BB3-5E54-457A-9873-DFB2E8035090}\</Param>\<Param>\</Param>\</UserParameters>\</StateMessage>\</ReportBody>\~~\</Report>~~'
975
+
> SMS_STATE_SYSTEM 23544 (0x5bf8) CMessageProcessor - the cmdline to DB exec dbo.spProcessStateReport N'?\<Report>\<ReportHeader>\<Identification>\<Machine>\<ClientInstalled>0\</ClientInstalled>\<ClientType>1\</ClientType>\<Unknown>0\</Unknown>\<ClientID IDType="0" IDFlag="1">00001111-aaaa-2222-bbbb-3333cccc4444\</ClientID>\<ClientVersion>5.00.0000.0000\</ClientVersion>\<NetBIOSName>P01PDP1.CONTOSO.COM\</NetBIOSName>\<CodePage>437\</CodePage>\<SystemDefaultLCID>1033\</SystemDefaultLCID>\</Machine>\</Identification>\<ReportDetails>\<ReportContent>StateMessage\</ReportContent>\<ReportType>Full\</ReportType>\<Date>20190107200618.000000+000\</Date>\<Version>1.0\</Version>\<Format>1.1\</Format>\</ReportDetails>\</ReportHeader>~~ \<ReportBody>\<StateMessage MessageTime="20190107200618.000000+000" SerialNumber="3">\<Topic ID="P010000F" Type="902" IDType="0"/>\<State ID="1" Criticality="0"/>\<UserParameters Flags="0" Count="4">\<Param>P010000F\</Param>\<Param>["Display=\\\P01PDP1.CONTOSO.COM\\"]MSWNET:["SMS_SITE=P01"]\\\P01PDP1.CONTOSO.COM\\\</Param>\<Param>{11112222-bbbb-3333-cccc-4444dddd5555}\</Param>\<Param>\</Param>\</UserParameters>\</StateMessage>\</ReportBody>\~~\</Report>~~'
976
976
977
977
Note that **StateSys.log** does not log the message body unless verbose logging for **StateSys.log** is enabled. To enable verbose logging for **StateSys.log**, see [Enable verbose logging](advanced-troubleshooting-tips.md#enable-verbose-logging).
0 commit comments