Re: UnauthorizedAccessException when using MSDTC

Hi Luke,
Thank you! We have checked the MSDTC service account, it is the same as
the other servers. I turned on the Security Audit and here is what I got in
the event viewer.

BLITZ is our domain controller
C8SERVER is our application server
dispatcher2 is the user logged on the client pc.

From what I understand there is a problem when we attempt to get to the
MSDTC service.....

In any case, I am sure you will have a better explanation than I for
this behavior.

Thank you

-Martin


Event Type: Failure Audit
Event Source: Security
Event Category: Object Access
Event ID: 560
Date: 15/08/2006
Time: 1:41:28 PM
User: BLITZ\dispatcher2
Computer: C8SERVER
Description:
Object Open:
Object Server: SC Manager
Object Type: SC_MANAGER OBJECT
Object Name: ServicesActive
Handle ID: -
Operation ID: {0,19314977}
Process ID: 452
Image File Name: C:\WINDOWS\system32\services.exe
Primary User Name: C8SERVER$
Primary Domain: BLITZ
Primary Logon ID: (0x0,0x3E7)
Client User Name: dispatcher2
Client Domain: BLITZ
Client Logon ID: (0x0,0x126A67F)
Accesses: READ_CONTROL
Connect to service controller
Enumerate services
Query service database lock state

Privileges: -
Restricted Sid Count: 0
Access Mask: 0x20015


For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

____________________________________________________________________________________________________________
Event Type: Failure Audit
Event Source: Security
Event Category: Object Access
Event ID: 560
Date: 15/08/2006
Time: 1:41:28 PM
User: BLITZ\dispatcher2
Computer: C8SERVER
Description:
Object Open:
Object Server: SC Manager
Object Type: SC_MANAGER OBJECT
Object Name: ServicesActive
Handle ID: -
Operation ID: {0,19314980}
Process ID: 452
Image File Name: C:\WINDOWS\system32\services.exe
Primary User Name: C8SERVER$
Primary Domain: BLITZ
Primary Logon ID: (0x0,0x3E7)
Client User Name: dispatcher2
Client Domain: BLITZ
Client Logon ID: (0x0,0x126A67F)
Accesses: READ_CONTROL
Connect to service controller
Enumerate services
Query service database lock state

Privileges: -
Restricted Sid Count: 0
Access Mask: 0x20015


For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

____________________________________________________________________________________________________________

Event Type: Failure Audit
Event Source: Security
Event Category: Object Access
Event ID: 560
Date: 15/08/2006
Time: 1:41:28 PM
User: BLITZ\dispatcher2
Computer: C8SERVER
Description:
Object Open:
Object Server: SC Manager
Object Type: SERVICE OBJECT
Object Name: MSDTC
Handle ID: -
Operation ID: {0,19315216}
Process ID: 452
Image File Name: C:\WINDOWS\system32\services.exe
Primary User Name: C8SERVER$
Primary Domain: BLITZ
Primary Logon ID: (0x0,0x3E7)
Client User Name: dispatcher2
Client Domain: BLITZ
Client Logon ID: (0x0,0x126A67F)
Accesses: Query status of service

Privileges: -
Restricted Sid Count: 0
Access Mask: 0x4


For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

____________________________________________________________________________________________________________

Event Type: Failure Audit
Event Source: Security
Event Category: Object Access
Event ID: 560
Date: 15/08/2006
Time: 1:41:28 PM
User: BLITZ\dispatcher2
Computer: C8SERVER
Description:
Object Open:
Object Server: SC Manager
Object Type: SERVICE OBJECT
Object Name: MSDTC
Handle ID: -
Operation ID: {0,19315253}
Process ID: 452
Image File Name: C:\WINDOWS\system32\services.exe
Primary User Name: C8SERVER$
Primary Domain: BLITZ
Primary Logon ID: (0x0,0x3E7)
Client User Name: dispatcher2
Client Domain: BLITZ
Client Logon ID: (0x0,0x126A67F)
Accesses: Query status of service

Privileges: -
Restricted Sid Count: 0
Access Mask: 0x4


For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

____________________________________________________________________________________________________________

Event Type: Failure Audit
Event Source: Security
Event Category: Object Access
Event ID: 560
Date: 15/08/2006
Time: 1:41:28 PM
User: BLITZ\dispatcher2
Computer: C8SERVER
Description:
Object Open:
Object Server: SC Manager
Object Type: SERVICE OBJECT
Object Name: MSDTC
Handle ID: -
Operation ID: {0,19315260}
Process ID: 452
Image File Name: C:\WINDOWS\system32\services.exe
Primary User Name: C8SERVER$
Primary Domain: BLITZ
Primary Logon ID: (0x0,0x3E7)
Client User Name: dispatcher2
Client Domain: BLITZ
Client Logon ID: (0x0,0x126A67F)
Accesses: Query status of service

Privileges: -
Restricted Sid Count: 0
Access Mask: 0x4


For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

____________________________________________________________________________________________________________

Event Type: Failure Audit
Event Source: Security
Event Category: Object Access
Event ID: 560
Date: 15/08/2006
Time: 1:41:28 PM
User: BLITZ\dispatcher2
Computer: C8SERVER
Description:
Object Open:
Object Server: SC Manager
Object Type: SC_MANAGER OBJECT
Object Name: ServicesActive
Handle ID: -
Operation ID: {0,19315269}
Process ID: 452
Image File Name: C:\WINDOWS\system32\services.exe
Primary User Name: C8SERVER$
Primary Domain: BLITZ
Primary Logon ID: (0x0,0x3E7)
Client User Name: dispatcher2
Client Domain: BLITZ
Client Logon ID: (0x0,0x126A67F)
Accesses: Connect to service controller
Query service database lock state

Privileges: -
Restricted Sid Count: 0
Access Mask: 0x11


For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

____________________________________________________________________________________________________________

Event Type: Failure Audit
Event Source: Security
Event Category: Object Access
Event ID: 560
Date: 15/08/2006
Time: 1:41:28 PM
User: BLITZ\dispatcher2
Computer: C8SERVER
Description:
Object Open:
Object Server: SC Manager
Object Type: SERVICE OBJECT
Object Name: MSDTC
Handle ID: -
Operation ID: {0,19315273}
Process ID: 452
Image File Name: C:\WINDOWS\system32\services.exe
Primary User Name: C8SERVER$
Primary Domain: BLITZ
Primary Logon ID: (0x0,0x3E7)
Client User Name: dispatcher2
Client Domain: BLITZ
Client Logon ID: (0x0,0x126A67F)
Accesses: Query service configuration information

Privileges: -
Restricted Sid Count: 0
Access Mask: 0x1


For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

____________________________________________________________________________________________________________



"Luke Zhang [MSFT]" <lukezhan@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:e5S5EIOwGHA.5576@xxxxxxxxxxxxxxxxxxxxxxxx
Hello Martin,

Regarding the issue, I suggest you may first check if this is a security
issue. For example, you may check if the Identity of the COM+ application
is a local administrator on the server. Also the MSDTC's account:

1. Click Start, click Run, type cmd, and then click OK.
2. At the command prompt, type control admintools, and then press ENTER.
3. Double-click Services.
4. In the Services pane, locate Distributed Transaction Coordinator.
5. In the Log On As column, note the account name.

You may also try a local administrator account here to see if it will
help.

And, for further trouble shooting on this issue, you may consider check
the
MSDTC log: %windir%\System32\Msdtc\Msdtc.log. It may provide some useful
information.

Also, you can compare the COM+ application and component settings on the
different server, to see if this cause the problem.
Sincerely,

Luke Zhang

Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================

This posting is provided "AS IS" with no warranties, and confers no
rights.





.

Relevant Pages

  • Re: Routing and Remote Access - Authentication Failure
    ... because the real client computer can tunel through it's local NAT router, ... travel the Intrenet, join the VPN and access the server, when this feature ... Their security system decided that the server was trying to steel ...
    (microsoft.public.windows.server.networking)
  • Re: WCF security advice (and clarification) needed
    ... You, the client, resolve the foo.mycompany.com hostname within your ... TCP/IP) with that ticket as the security token. ... There are two parties participating in a security scenario, the server ... HTTP supports other authentication ...
    (microsoft.public.dotnet.framework.webservices)
  • RE: Problems with security requirements in Windows WorkGroups.
    ... "A remote side security requirement was not fulfilled during authentication. ... small chat application between a client and a server ... When I try to use the TCP channel I get the error (with NO inner exception ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: VPN -- the next consumer "turnkey"?
    ... I'm not a security expert. ... "A Hamachi system is comprised of backend servers and end-node ... Server nodes track client's locations and provide ... services without providing Hamachi with a list of client IP's. ...
    (alt.internet.wireless)
  • lame server messages in named.log
    ... Mar 30 05:42:30.526 security: info: client 202.52.250.176#1052: ... query (cache) denied ...
    (RedHat)