Fix for File Replication System (NTFRS) replication problems (Event ID 13549)

This fix worked for me in resolving an issue where a additional domain controller was in a death cycle of starting/stopping/restarting the FRS service every few minutes.

Symptoms

If, after you run DCPROMO to add a domain controller to the existing domain, after reboot, you run into a problem where the NETLOGON and SYSVOL shares are not being created and you check the File Replication Service logs in the Event log to find the following error messages:

(Event ID 13549)
The File Replication Service is unable to replicate from a partner computer because the event time associated with the file to be replicated is too far into the future. It is 30 minutes greater than the current time. This can happen if the system time on the partner computer was set incorrectly when the file was created or updated. To preserve the integrity of the replica set this file update will not be performed or propagated further.

The file name is: “[YOUR_PROBLEM_FILE_HERE]”
The connection to the partner computer is:
“DOMAIN SYSTEM VOLUME (SYSVOL SHARE)\NEWDC_NAME\\\PDC_EMULATOR_NAME.domain.com <- \\ PDC_EMULATOR_NAME.domain.com RemoteCxt”

Resolution

Make sure and keep copies of all the folders and files.

Take these actions to resolve your problem:

On all Active Directory registered domain controllers:

1. Stop NETLOGON Service
2. Stop File Replication Service (NTFRS)

On the PDC Emulator:

1. Rename all files in the %systemroot%\ntfrs folder and subfolders (change their extension to .old).
2. Give an unlisted account full control of the directory %systemroot%\SYSVOL folder and reset permissions on all child objects.
3. Change the registry key:
HKLM\System\CurrentControlSet\Services\ntfrs\paramaters\Backup/Restore\Process at Startup\BurFlags (REG_DWORD) = D4
(The default on this is 0)
4. Start the NETLOGON Service
5. Start the NTFRS Service

On all non-PDC emulators:

1. Change the registry key:
HKLM\System\CurrentControlSet\Services\ntfrs\paramaters\Backup/Restore\Process at Startup\BurFlags (REG_DWORD) = D2
2. Start the NETLOGON Service
3. Start the File Replication Service (NTFRS)

At this point, the system in question should have recreated the SYSVOL share and the NETLOGON share. Check this by running ‘net share’ from a command prompt. You should also see the Group Policy Objects listed in the SYSVOL directory as:

%systemroot%\SYSVOL\domain_name\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}

%systemroot%\SYSVOL\domain_name\Policies\{6AC1786C-016F-11D2-945F-00C04FB984F9}

There may be more directories listed here, but these are the Default Domain Policy and the Default Domain Controllers Policy that are installed by default when the Active Directory is created. If these are being replicated, then file replication is functioning.

.NET Framework Cleanup Tool

This .NET Framework cleanup tool is designed to automatically perform a set of steps to remove selected versions of the .NET Framework from a computer.  It will remove files, directories, registry keys and values and Windows Installer product registration information for the .NET Framework.  The tool is intended primarily to return your system to a known  state in case you are encountering .NET Framework installation, uninstallation, repair or patching errors so that you can try to install again.

Download location

http://blogs.msdn.com/astebner/attachment/8904493.ashx

Outlook 2003 Error when creating profile

This solution is for error message when you try to create a new profile in Outlook 2003:

There was an error locating one of the items needed to complete this operation. It might have been deleted.

This error encountered and can be reproduced with the following:

• Downgrade Microsoft Office / Outlook 2007 to Office / Outlook 2003.
• Connecting to exchange server.
• Operating system: Windows XP Professional.

Figure 1. When creating a new profile, an error message pop up as soon as OK button is pressed.

profile is created even with the error message, and when trying to add a new account for exchange the same error pops up.

Solution:

1. Delete or rename file: Mapisvc.inf in \Windows\System32 folder
2. Delete or rename file: Mapisvc.inf in \Program Files\Common Files\System\MSMAPI\1033 folder 
3. Create a new profile again and setup will re-install that file. New profile can be created and Outlook can connect to exchange.