I have a website application that uses Microsoft Data Transactions and is based on the .NET Framework 4.0 and SQL Server 2008 R2 Express Edition for a database deployed to Windows 2008 Server R2, which is a virtual server. The database and IIS are on the same server.
The problem is that the error occurs in the server’s event logs as: - MSDTC detected an error (HR = 0x80000171) when trying to establish a secure connection to the ZEPHYR system. Zephyr is the name of my server.
I have already done almost all the questions included in two forums:
http://social.technet.microsoft.com/Forums/en-US/winservergen/thread/eb8835d9-5f5b-4df2-8c68-4a61d5e44d6b/
http: // social. msdn.microsoft.com/Forums/en-US/sqlgetstarted/thread/13586ca7-f645-4ed7-96e8-ba03f66ef38b
Everything works fine, but when executing the following command using the SUBINACL tool: -
C:\Program Files (x86)\Windows Resource Kits\Tools>subinacl /service msdtc /grant="Network Service"=QSETIL
msdtc - OpenService Error : 5 Access is denied.
Elapsed Time: 00 00:00:00
Done: 1, Modified 0, Failed 1, Syntax errors 0
Last Done : msdtc
Last Failed: msdtc - OpenService Error : 5 Access is denied.
subinacl /service msdtc /grant="Network Service"=QSETIL
But then I used the following ICACLS command to access it using the ICACLS command: -
icacls c:\windows\system32\msdtc\msdtc.log /grant admin:(d,wdac)
NOTE. "Admin is my user for the Server. But again, this does not solve the problem. Access rights for the msdtc.log file by command: -
{"icacls c:\windows\system32\msdtc\msdtc.log"} are as follows:-
C:\>icacls c:\windows\system32\msdtc\msdtc.log
c:\windows\system32\msdtc\msdtc.log NT AUTHORITY\NETWORK SERVICE:(F)
ZEPHYR\Administrator:(D,WDAC)
ZEPHYR\admin:(D,WDAC)
BUILTIN\Administrators:(F)
ZEPHYR\admin:(I)(F)
NT AUTHORITY\SYSTEM:(I)(F)
BUILTIN\Administrators:(I)(F)
NT SERVICE\KtmRm:(I)(F)
NT SERVICE\MSDTC:(I)(F)
Successfully processed 1 files; Failed processing 0 files
As far as I saw, there are very few forums that post a question about such an error.
I would like to ask how to solve this problem, because this error caused a bottleneck, and transactions do not work on those .aspx pages, wherever they are implemented. Are there any problems for this problem?
source
share