I updated a 2003 R2 server over the weekend with SP2 and all critical & security updates. The machine is the only DC in the domain so obviously holds all FSMO roles etc.
I had to do a few restarts, but after each one, I had an error in the system log that said:
MS DTC could not correctly process a DC Promotion/Demotion event. MS DTC will continue to function and will use the existing security settings. Error Specifics: d:\nt\com\complus\dtc\dtc\adme\uiname.cpp:9351, Pid: 1288
No Callstack,
CmdLine: C:\WINDOWS\system32\msdtc.exe
The data (in words) is 80070005 - which equates to access denied. In an attempt to re-generate the error, I tried restarting MSDTC in component services (after reducing the COM+ duplicate log supression limit to 60 seconds) and got an informational log saying "MS DTC has detected that a DC Promotion has happened since the last time the MS DTC service was started", but I didn't get any warnings. I restarted MSDTC a few more times but didn't get this entry again. The machine has been operating as a DC for 2 years now without any issues.
Two suggestions on eventid.net may hold a solution, I haven't tried either of them as I don't have a definite way of reproducing the problem (other than a system restart). The solutions are the last 2 on this page:
What I'd like to know is if anybody has experienced this the past? Or if anybody has any ideas what might be causing this?
Additionally, some time last night, the server suddenly stopped synchronizing time, and when users arrived in this morning, they were unable to login. The NTP source is pool.ntp.org. Is it possible that this is related? Or maybe this is just related to network issues?
Irish Poetry - Karen O'Connor
Irish Poetry and Short Stories - Doghouse Books
Garten und Landschaftsbau
I had to do a few restarts, but after each one, I had an error in the system log that said:
MS DTC could not correctly process a DC Promotion/Demotion event. MS DTC will continue to function and will use the existing security settings. Error Specifics: d:\nt\com\complus\dtc\dtc\adme\uiname.cpp:9351, Pid: 1288
No Callstack,
CmdLine: C:\WINDOWS\system32\msdtc.exe
The data (in words) is 80070005 - which equates to access denied. In an attempt to re-generate the error, I tried restarting MSDTC in component services (after reducing the COM+ duplicate log supression limit to 60 seconds) and got an informational log saying "MS DTC has detected that a DC Promotion has happened since the last time the MS DTC service was started", but I didn't get any warnings. I restarted MSDTC a few more times but didn't get this entry again. The machine has been operating as a DC for 2 years now without any issues.
Two suggestions on eventid.net may hold a solution, I haven't tried either of them as I don't have a definite way of reproducing the problem (other than a system restart). The solutions are the last 2 on this page:
What I'd like to know is if anybody has experienced this the past? Or if anybody has any ideas what might be causing this?
Additionally, some time last night, the server suddenly stopped synchronizing time, and when users arrived in this morning, they were unable to login. The NTP source is pool.ntp.org. Is it possible that this is related? Or maybe this is just related to network issues?
Irish Poetry - Karen O'Connor
Irish Poetry and Short Stories - Doghouse Books
Garten und Landschaftsbau