gfsupport
asked on
FRS failing to add server to replica set
Hi there,
I'm getting an issue with FRS for a migration I'm attempting from SBS 2003 to 2008 R2.
So far I've added the 2008 R2 server as a DC in another AD site (same domain) but noticed that the Sysvol & Netlogon shares were not present.
I then noticed on the SBS server that we are seeing events 13552 & 13555 for FRS, restarting the FRS service has no effect.
I performed a D4 restore on the server which briefly added the servers (both) to the replica set but then falls back to event 13552 & 13555 and stops sharing the Sysvol & Netlogon shares on the server (SBS) about 2 second afterwards. In order to reinstate the Syvol & Netlogon shares on the SBS server I have to set the following reg key to '1'
HKEY_LOCAL_MACHINE\SYSTEM\
In the event 13552 I can see:
'FRS error status code is FrsErrorJournalInitFailed'
And in the FRS debug log I can also see the following two entries one after another:
Error from JrnlOpen WStatus: ERROR_JOURNAL_DELETE_IN_PR
CMD_JOURNAL_INIT_ONE_RS failed WStatus: ERROR_GEN_FAILURE
DCdiag, repadmin & netdiag return no issues (other than mentioning that there are error messages in for FRS).
As this is the only DC they have currently and no System State backup exists I'm at a loss of how to proceed?
If anyone has come across this issue before and could offer a possible method to get this working?
Many thanks
David
I'm getting an issue with FRS for a migration I'm attempting from SBS 2003 to 2008 R2.
So far I've added the 2008 R2 server as a DC in another AD site (same domain) but noticed that the Sysvol & Netlogon shares were not present.
I then noticed on the SBS server that we are seeing events 13552 & 13555 for FRS, restarting the FRS service has no effect.
I performed a D4 restore on the server which briefly added the servers (both) to the replica set but then falls back to event 13552 & 13555 and stops sharing the Sysvol & Netlogon shares on the server (SBS) about 2 second afterwards. In order to reinstate the Syvol & Netlogon shares on the SBS server I have to set the following reg key to '1'
HKEY_LOCAL_MACHINE\SYSTEM\
In the event 13552 I can see:
'FRS error status code is FrsErrorJournalInitFailed'
And in the FRS debug log I can also see the following two entries one after another:
Error from JrnlOpen WStatus: ERROR_JOURNAL_DELETE_IN_PR
CMD_JOURNAL_INIT_ONE_RS failed WStatus: ERROR_GEN_FAILURE
DCdiag, repadmin & netdiag return no issues (other than mentioning that there are error messages in for FRS).
As this is the only DC they have currently and no System State backup exists I'm at a loss of how to proceed?
If anyone has come across this issue before and could offer a possible method to get this working?
Many thanks
David
Don S.
Need to do both the D4 on the sbs2003 server then a d2 on the 2008 server (or remove DS, reboot and add DS back). Just had this two weeks ago - annoying as heck.
ASKER
Hi Dons6718,
Thank you for your advice, I have previously performed a D4 / D2 on both servers but the issue isn't with the 2008 R2 box, its with the SBS 2003 server itself:
In the event 13552 I can see:
'FRS error status code is FrsErrorJournalInitFailed'
And in the FRS debug log I can also see the following two entries one after another:
Error from JrnlOpen WStatus: ERROR_JOURNAL_DELETE_IN_PR
CMD_JOURNAL_INIT_ONE_RS failed WStatus: ERROR_GEN_FAILURE
Many thanks
David
Thank you for your advice, I have previously performed a D4 / D2 on both servers but the issue isn't with the 2008 R2 box, its with the SBS 2003 server itself:
In the event 13552 I can see:
'FRS error status code is FrsErrorJournalInitFailed'
And in the FRS debug log I can also see the following two entries one after another:
Error from JrnlOpen WStatus: ERROR_JOURNAL_DELETE_IN_PR
CMD_JOURNAL_INIT_ONE_RS failed WStatus: ERROR_GEN_FAILURE
Many thanks
David
That would seem to indicate either a permissions problem or a file corruption problem on the SBS server. Does NTFRS stop and start cleanly on the SBS box? If not, what messages does it throw?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Troubleshooting with Microsoft.
Microsoft's platform team moved the Sysvol folder off the hardware Raid 5 array that the OS sat on to a USB pen Drive, once this was done replication started functioning once more
Microsoft's platform team moved the Sysvol folder off the hardware Raid 5 array that the OS sat on to a USB pen Drive, once this was done replication started functioning once more