File Replication Journal Wrap and Sysvol errors with Small Business Server migration

When doing a migration from Small Business Server (SBS) 2003 to SBS 2008, SBS 2011 or Windows server standard version, one of the first things you should do is run the SBS 2003 Best Practices Analyzer and of course check your event log for known problems.

One of the issues I see often is the sysvol, journal wrap Event ID 13568, Source NtFrs in the File Replication Eventlog.

The File Replication Service has detected that the replica set “DOMAIN SYSTEM VOLUME (SYSVOL SHARE)” is in JRNL_WRAP_ERROR.

Replica set name is    : “DOMAIN SYSTEM VOLUME (SYSVOL SHARE)”
Replica root path is   : “c:\windows\sysvol\domain”
Replica root volume is : “\\.\C:”
A Replica set hits JRNL_WRAP_ERROR when the record that it is trying to read from the NTFS USN journal is not found.  This can occur because of one of the following reasons.

[1] Volume “\\.\C:” has been formatted.
[2] The NTFS USN journal on volume “\\.\C:” has been deleted.
[3] The NTFS USN journal on volume “\\.\C:” has been truncated. Chkdsk can truncate the journal if it finds corrupt entries at the end of the journal.
[4] File Replication Service was not running on this computer for a long time.
[5] File Replication Service could not keep up with the rate of Disk IO activity on “\\.\C:”.
Setting the “Enable Journal Wrap Automatic Restore” registry parameter to 1 will cause the following recovery steps to be taken to automatically recover from this error state.
[1] At the first poll, which will occur in 5 minutes, this computer will be deleted from the replica set. If you do not want to wait 5 minutes, then run “net stop ntfrs” followed by “net start ntfrs” to restart the File Replication Service.
[2] At the poll following the deletion this computer will be re-added to the replica set. The re-addition will trigger a full tree sync for the replica set.

WARNING: During the recovery process data in the replica tree may be unavailable. You should reset the registry parameter described above to 0 to prevent automatic recovery from making the data unexpectedly unavailable if this error condition occurs again.

To change this registry parameter, run regedit.

Click on Start, Run and type regedit.

Click down the key path:
Double click on the value name
   “Enable Journal Wrap Automatic Restore”
and update the value.

If the value name is not present you may add it with the New->DWORD Value function under the Edit Menu item. Type the value name exactly as shown above.———————————————————————————————————————————–

Fixing this issue is in most cases relative simple just add the “Enable Journal Wrap Automatic Restore” registry key noted in the event log and change the value to “1” and restart the “File Replication Service” service.

Before changing the registry key I would recommend to make a backup from the C:\Windows\Sysvol folder.

But after doing that there appeared a new warning message in the File Replication Eventlog, Event ID 13566, Source Ntfrs.

File Replication Service is scanning the data in the system volume. computer <domain name> cannot become a domain controller until this process is complete. The system volume will then be shared as SYSVOL.

To check for the SYSVOL share, at the command prompt, type:
net share

When File Replication Service completes the scanning process, the SYSVOL share will appear.

The initialization of the system volume can take some time. The time is dependent on the amount of data in the system volume.———————————————————————————————————————————–

As stated you have to wait a while, but I could wait as long as I want but the sysvol share doesn’t appear.

Solution: At the end the solution seems to be that the ntfrs jet database was corrupted. To solve the problem:

Stop the “File Replication Service” service

Rename the “C:\windows\ntfrs\jet” folder

Start the “File Replication Service” service

One other thing that could happen is the folders under Windows\Sysvol are moved to a subfolder called “NtFrs_PreExisting_See_EventLog”. If you have more than one domain controller this is no problem and the folders will be replicated from another domain controller, but if you only have one domain controller which is mostly the case when using SBS. You can copy the right folders back from the backup you made before, or just move them out of the “NtFrs_PreExisting_See_EventLog” folder to one level up.

Solve these problems before you are starting your migration otherwise you will run into replication errors.

Posted in Blog, SBS 2008, SBS 2011 at April 7th, 2011. 29 Comments.

Migrating to Windows Small Business Server 2011 Standard

As microsoft already released documentation about migrating from SBS 2003 to SBS 2011, now they released some more migration scenarios. Here a overview of al released scenarios:

Migrate to Windows Small Business Server 2011 Standard from Windows Small Business Server 2003

Migrate to Windows Small Business Server 2011 Standard from Windows Small Business Server 2008

Migrate Windows Small Business Server 2011 Standard to New Hardware

Move all SharePoint Foundation 2010 databases for Windows SBS 2011 Standard to another server

Posted in Blog, SBS 2011 at February 4th, 2011. No Comments.

Migrate Small Business Server 2003 to Small Business Server 2011 guide

For all you early adopters of Windows small business server 2011 Microsoft released there migration guide from small business server 2003 to small business server 2011.

You can find the guide over here: technet.microsoft.com

If you are coming from small business server 2008 you have to wait a little longer because this guide isn’t released yet.

Posted in Blog, SBS 2011 at December 29th, 2010. No Comments.

Error transfering Schema Master role from Windows 2003 to 2008

After tranfering the first 4 operation master roles without a problem from windows 2003 to the new windows 2008 server, the Schema Master role gave an error using the Active Directory Schema mmc add-in:

The parameter is incorrect.
The transfer of the current Operation Master could not be preformed.

Solution: First check if the windows 2003 role owner is alive and you can reach that server. You can check which server holds the role “netdom query fsmo”. If that all is fine try moving the role with ntdsutil.
Open a command prompt on your windows 2008 server and type: ntdsutil
Type roles and then press ENTER
Type connections, ENTER
Type connect to server , ENTER
Type q, ENTER
Type Transfer schema master, ENTER
You will get a warning message choose Yes to continue.
Then type q and again q to exit ntdsutil.

You can use: Transfer domain naming master, Transfer infrastructure master, Transfer PDC and Transfer RID master if you also would transfer the other FSMO roles with ntdsutil.

Posted in Blog, Windows 2008 at October 31st, 2010. No Comments.

SQL Server (dbname) service won’t start after promoting the server to a domain controller

When you promote your windows member server to a domain controller the SQL Server (dbname) service won’t start anymore.

The system event log notes error even id: 7024 “The SQL Server (dbname) service terminated with service-specific error 17113 (0x42D9).”

Solution: This is because the SQL Server (dbname) service is started under the local system account, this doesn’t work on a domain controller. Start the service under a user account with enough rights.

Posted in Blog, SQL 2005, SQL 2008 at October 22nd, 2010. 2 Comments.

Exchange 2010 SP1 mailbox move errors

When moving mailbox from a exchange 2003 server to a exchange 2010 server I ran into some warnings and errors.

When you try to move a mailbox via the wizard and choose “Skip the corrupted messsages.” and select to skip more then 50 messages you get the following error:
“Large BadItemLimit (50+) is specified. Please confirm your intention to accept a large amount of data loss by specifying AcceptLargeDataLoss.”

Solution: Use the Exchange Management Shell and use “New-MoveRequest -Identity “Mailboxname” -BadItemLimit 50+ -AcceptLargeDataLoss”
You can use other options if you like, but the -AcceptLargeDataLoss resolves this issue. More option on the New-MoveRequest cmdlet are available here.

Another error I ran into was, “Active Directory operation failed on Servername. This error is not retriable. Additional information: Insufficient access rights to perform the operation.
Active directory response: 00002098: SecErr: DSID-03150A45, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0
+ CategoryInfo : NotSpecified: (0:Int32) [New-MoveRequest], ADOperationException
+ FullyQualifiedErrorId : D6EC1D97,Microsoft.Exchange.Management.RecipientTasks.NewMoveRequest”

Solution: Go to the Active Directory user account witch you are trying to move. Select properties, security tab and then Advanced. Make sure the “Allow inheritable permissions from the parent to propagate to this object and all child objects. Include these with the entries explicity defined here.” is checked. If not enable it and then apply the setting.

Posted in Blog, Exchange 2010 at September 24th, 2010. No Comments.

Exchange 2007 or 2010 migration fails with: Access control list (ACL) inheritance is blocked

The setup of Exchange 2007, Exchange 2010 or even SBS 2008 stops with the error “Access control list (ACL) inheritance is blocked”

Solution: Exchange setup requires that permission inheritance is enabled for the following objects:
Exchange Organization object, Exchange Administrative Group object, Exchange Servers container object, Exchange Address List object, Exchange Public Folder object and Exchange Public Folder tree object.

For Exchange 2003 start Exchange system manager and goto the objects and right click and choose properties, then on the security tab choose advanced and make sure “Allow inheritable permissions from the parent to propagate to this object and all child objects” is enabled. After that restart the Exchange server.

If security tab isn’t available you have to create the following registry value:
Value Name: ShowSecurityPage, Data Type: REG_DWORD, Radix: Binary, Value: 1 At the HKEY_CURRENT_USER\Software\Microsoft\Exchange\EXAdmin key.

For Exchange 2007 and 2010 use adsiedit, and browse to the object you want to change. Right click and choose properties, then on the security tab choose advanced and make sure “Allow inheritable permissions from the parent to propagate to this object and all child objects” is enabled. Wait till Active Directory replication has replicated the changes.

Posted in Blog, Exchange 2007, Exchange 2010, SBS 2008 at September 17th, 2010. No Comments.

OfflineAddressBook, PublicFolderDatabase still points to old server

After migrating your Exchange server (I’ve seen this in transition to exchange 2007 and 2010) the PublicFolderDatabase for your OfflineAddressBook is still pointing to the old servers public folder store.

When you run the get-OfflineAddressBook | fl command in a exchange management shell on your new server, you get a result like this:

At Server you see the new servername and the PublicFolderDatabase is still pointing to your old server. Public folder replica’s and offline address book generation server are already moved to the new server.

Solution: I found if you do the following steps you can change the PublicFolderDatabase.
First start adsiedit and browse to CN=Configuration, CN=Services, CN=Microsoft Exchange, CN=First Organization, CN=Address Lists Container, CN=Offline Address Lists and open the properties of CN=Default Offline Address List

Look for the siteFolderServer attribute, here you will see the old public folder store. Choose clear and close with ok, now you may close adsiedit.

Now go to the exchange management console, Organization Configuration, Mailbox, Offline Address Book open the properties of the Default Offline Address List and go to the tab distribution.

Uncheck “Outlook version 2 and 3” at client support and “Enable public folder distribution”. Make sure “Web-based distribution” is enabled. Choose apply and ok, then right click on Default Offline Address List and choose update. After that go back to properties and distribution and check “Outlook client support version 2 and 3” and “Enable public folder distibution”. Again choose apply and ok and right click and choose update.

When you go back to the exchange management shell and repeat get-OfflineAddressBook | fl you now will see the public folder store on your new server.

Posted in Blog, Exchange 2007, Exchange 2010 at September 8th, 2010. 46 Comments.

Exchange 2007 ‘public folder database’ cannot be deleted

When you try to remove a Exchange 2007 public folder database after a migration to Exchange 2010 you’ll get a “Object is read only because it was created by a future version of Exchange: 0.10 ( Current supported version is 0.1 (8.0.535.0).” error.

Solution: Run adsiedit.msc goto configuration container CN=Configuration , CN=Services , CN=Microsoft Exchange , CN=First Organisation , CN=Administrative Groups , CN=Exchange Administrative Group (FYDIBOHF23SPDLT) , CN=Servers , CN=EXCHANGE2007SERVER , CN=Information Store , CN=Second Storage Group delete the CN=Public Folder Database.

Posted in Blog, Exchange 2007, Exchange 2010 at August 27th, 2010. No Comments.

Logon Failure on database while accessing or moving mailboxes

We were migrating a SBS 2003 server to a new SBS 2008 server via the swing migration method. After turning on the SBS 2008 server and temporary dc / exchange 2003 server we were not able to access or move the exchange 2003 mailboxes.

The mailbox move gives a: “The move-mailbox task for mailbox ‘mailboxname’ failed. Error: Failed to open mailbox with error: The operation failed.” error on the SBS 2008 (Exchange 2007) server.

On the Exchange 2003 server we get a: Event id 1022: “Logon Failure on database “First Storage Group\Mailbox Store” – Windows account domain\accountname; mailbox /o=domain/ou=first administrative group/cn=Recipients/cn=accountname.Error: 1144″ error.

Solution: It looks like that after forklift and update a exchange 2003 database it could take some time to connect because AD has to replicate the information between the 2 domain controllers. When this is done everything works fine. This can also occur after moving the exchange mailboxes to a the new sbs 2008 / exchange 2007 server.

Posted in Blog, Exchange 2007, SBS 2008 at August 17th, 2010. No Comments.
Sharing Buttons by Linksku