Skip to content

Commit bea11f8

Browse files
committed
Update Microsoft-Platform.md
1 parent fe88510 commit bea11f8

File tree

1 file changed

+35
-37
lines changed

1 file changed

+35
-37
lines changed

connectors/Microsoft/Microsoft-Platform.md

+35-37
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ order to set the current values as normal.
1818

1919
### <span class="ms-rteStyle-Accent1">Ranges of the driver</span>
2020

21-
<table class="ms-rteTable-default" data-cellspacing="0" style="width: 50%;">
21+
<table class="ms-rteTable-default" data-cellspacing="0" style="width: 100%;">
2222
<colgroup>
2323
<col style="width: 25%" />
2424
<col style="width: 25%" />
@@ -103,8 +103,6 @@ Version 1.1.3.5 merged with 1.1.0.106</td>
103103
</tbody>
104104
</table>
105105

106-
###  
107-
108106
## Installation and configuration
109107

110108
The polling IP of the Microsoft server must be defined when the element
@@ -400,42 +398,42 @@ within DataMiner for this.
400398

401399
### <span class="ms-rteStyle-Accent1">Troubleshooting</span>
402400

403-
**Problem:**
401+
#### Problem
404402

405-
- Remote WMI queries for non-admin users:
403+
Remote WMI queries for non-admin users:
406404

407-
> Access is denied with error code 0x80070005 -> **Solution**: DCOM
408-
> configuration (see installation and configuration).
409-
>
410-
> Access is denied with error code 0x80041003 -> **Solution**: WMI
411-
> configuration (see installation and configuration).
412-
>
413-
> To check whether access is denied, the following two procedures are
414-
> possible:
415-
>
416-
> The first procedure:
417-
>
418-
> 1. Click **Start****Run** and enter *wmimgmt.msc*.
419-
> 2. Right-click **WMI Control (Local)** and select **Connect to
420-
> another computer**.
421-
> 3. Select **Actions** > **More Actions** > **Properties**.
422-
> At this point, you will receive the following error: Failed to
423-
> connect to [\\\\%RemoteIP%](file:///) because "Win32 Access is
424-
> denied”.
425-
>
426-
> The second procedure:
427-
>
428-
> - Run “wmimgmt.msc” directly on server.
429-
>  You will receive the following error: Microsoft Management
430-
> Console “An attempt was made to reference a token that does not
431-
> exist”.
432-
>
433-
> > **Solution**: If indeed you receive the indicated error using one of
434-
> > the test procedures above, you can fix this issue via Service
435-
> > Control Manager, by running a command to allow a user to have
436-
> > access:
437-
> > *sc sdset SCMANAGER
438-
> > D:(A;;CCLCRPRC;;;AU)(A;;CCLCRPWPRC;;;SY)(A;;KA;;;BA)S:(AU;FA;KA;;;WD)(AU;OIIOFA;GA;;;WD)*
405+
Access is denied with error code 0x80070005 -> **Solution**: DCOM
406+
configuration (see installation and configuration).
407+
408+
Access is denied with error code 0x80041003 -> **Solution**: WMI
409+
configuration (see installation and configuration).
410+
411+
To check whether access is denied, the following two procedures are
412+
possible:
413+
414+
The first procedure:
415+
416+
1. Click **Start****Run** and enter *wmimgmt.msc*.
417+
2. Right-click **WMI Control (Local)** and select **Connect to
418+
another computer**.
419+
3. Select **Actions** > **More Actions** > **Properties**.
420+
At this point, you will receive the following error: Failed to
421+
connect to [\\\\%RemoteIP%](file:///) because "Win32 Access is
422+
denied”.
423+
424+
The second procedure:
425+
426+
- Run “wmimgmt.msc” directly on server.
427+
 You will receive the following error: Microsoft Management
428+
Console “An attempt was made to reference a token that does not
429+
exist”.
430+
431+
> **Solution**: If indeed you receive the indicated error using one of
432+
> the test procedures above, you can fix this issue via Service
433+
> Control Manager, by running a command to allow a user to have
434+
> access:
435+
> *sc sdset SCMANAGER
436+
> D:(A;;CCLCRPRC;;;AU)(A;;CCLCRPWPRC;;;SY)(A;;KA;;;BA)S:(AU;FA;KA;;;WD)(AU;OIIOFA;GA;;;WD)*
439437
440438
**Problem:**
441439

0 commit comments

Comments
 (0)