Ważne narzędzia:
Znowu problem z kontrolerem domeny, znowu MSDTC (nie pamiętam czy pisałem o tym wcześniej, stąd ku pamięci):
MSDTC Event ID 4143 and 53258 on Windows Server 2003 SP1 Domain Controller
I got hit by a problem on a freshly installed virtual machine using a slipstreamed SP1 installation and promoted to a domain controller. Two events were appearing in the event log which were unexpected.
Source: MSDTC Event ID: 4143 Information
MS DTC has detected that a DC Promotion has happened since the last time the MS DTC service was started.followed by
Source: MSDTC Event ID: 53258 Warning
MS DTC could not correctly process a DC Promotion/Demotion event. MS DTC will continue to function and will use the existing security settings.To resolve this, go through the following steps:
- Start/Administrative Tools/Component Services
- Navigate the tree view on the left to:
– Console Root
– Component Services
– Computers
– My Computer
- Right click on „My Computer” and select properties
- Select the MSDTC Tab
- Under „Transaction Configuration” near the bottom, click „Security Configuration”
- On the Security Configuration screen, just click OK – don’t change anything.
- Back on the „My Computer Properties” screen, click OK again to dismiss
- Right click on „My Computer” in the tree view and select „Stop MS DTC”
- Right click on „My Computer” in the tree view and select „Start MS DTC”
- Close the Component Services snapin.All should now be well again. Hope this helps someone.
Źródło: link
Problem:
Login failed for user ‘NT AUTHORITY\NETWORK SERVICE’. [CLIENT: <named pipe>]
Type: Failure Audit
Source: MSSQL$MICROSOFT##SSEE
Category: (4)
Event: 18456
User: NETWORK SERVICE
Rozwiązanie:
For supgraffix?s issue, based on the post, the errors are thrown repeatedly and there is an authorization problem in the configuration database.
I diagnosed that the issue happens in the Central Administration application pool account and the SharePoint Timer Service is not working properly.
There are both WSS 2.0 and WSS 3.0 error logs in your post. I suppose WSS 2.0 is the cause of your issue based on the database name.
To resolve the problem, you can do the following steps:
1. Browse to the SharePoint Central Administration page.
2. Under Server Configuration, click Configure Virtual Server for Central Administration.
3. Select Use an Existing Application Pool.
4. Select the application pool that the central administration virtual server is running under.
5. Click OK.
6. Run an IISReset.
7. Restart the SharePoint Timer Service.
W tym przypadku (pkt. 4) wybrany został:
StsAdminAppPool (NT AUTHORITY\NETWORK SERVICE).
Po takiej operacji restart usług (iisreset) nie wyrzucił żadnych błędów.