FRS Error
5200: Error executing query: Simappwds06/HUM_FIN/HUM_FIN/admin/Error(1200467) Error executing formula for [Act YTD]: status code [1042006] in function [@_VAL];hasPovDims=0;povXML=<?xml version="1.0"?><datasources></datasources>
i got the following error while opening the frs report
can anyone help me with this
I wouldn't count out the issue with too many connections being opened for windows to handle,
I have seen this a number of times with financial reports and have had to update the registry to resolve the issue.
Basically you need to do the following on the windows servers
1. From the Start menu, click Run.
2. Type regedit and then click OK.
3. In the Registry Editor window, click the following directory:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters
4. From the Edit menu, click New, DWORD Value.
The new value appears in the lis t of parameters.
5. Type MaxUserPort and then press Enter.
Double-click MaxUserPort.
6. In the Edit DWORD Value window, do the following:
* Click Decimal.
* Enter 65534.
* Click OK.
7. From the Edit menu, click New, DWORD Value.
The new value appears in the list of parameters.
8. Type TcpTimedWaitDelay and then press Enter.
9. Double-click TcpTimedWaitDelay.
10. In the Edit DWORD Value window, do the following:
* Click Decimal.
* Type 300
* Click OK.
11. Close the Registry Editor window.
12. Reboot server
If you think it is a database connection issue, log into workspace, Explore > Tools, then Database Connection Manager.
You can then edit the connection.
Cheers
John
http://john-goodwin.blogspot.com/
Similar Messages
-
FRS errors 13552 & 13555. SYSVOL not replicating.
Hi All, looking for a little help here...
Here is the scenario. My (new) client has ONLY 1 domain controller (Windows Server 2003 which I will call SERVER1). I recently installed a new 2008 R2 server and made it a replica domain controller. Everything went well until I realised that
there was no SYSVOL share on the new server. I checked FRS event logs on SERVER1 and noticed that event ID errors 13552 & 13555 have been occuring since December 2010.
I've been reading about changing burflags to do a nonauthorative restore from a replica DC however in this case there is only 1 DC. Can someone advise how I go about fixing this?
Event Type: Error
Event Source: NtFrs
Event Category: None
Event ID: 13552
Date: 21/06/2011
Time: 2:15:57 PM
User: N/A
Computer: SERVER1
Description:
The File Replication Service is unable to add this computer to the following replica set:
"DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"
This could be caused by a number of problems such as:
-- an invalid root path,
-- a missing directory,
-- a missing disk volume,
-- a file system on the volume that does not support NTFS 5.0
The information below may help to resolve the problem:
Computer DNS name is "server1.mydomain.local"
Replica set member name is "SERVER1"
Replica set root path is "c:\windows\sysvol\domain"
Replica staging directory path is "c:\windows\sysvol\staging\domain"
Replica working directory path is "c:\windows\ntfrs\jet"
Windows error status code is
FRS error status code is FrsErrorMismatchedJournalId
Event Type: Error
Event Source: NtFrs
Event Category: None
Event ID: 13555
Date: 21/06/2011
Time: 2:15:57 PM
User: N/A
Computer: SERVER1
Description:
The File Replication Service is in an error state. Files will not replicate to or from one or all of the replica sets on this computer until the following recovery steps are performed:Hi CURNS, thanks for the replies. Yes, it works in below scenario (Replication from 2003 to 2008).
There was only 1 copy of sysvol, and it was on the old DC. The new DC has not yet shared or replicated sysvol thus making the burflag D2 option a no go. I first had to fix whatever the issue was with the old DC before the new one would replicate.
I fixed replication issue with 4 easy steps:
1. stopped the FRS service on both DCs (old and new)
2. set burflag on old DC to D4 (to tell it its the boss)
To configure the SYSVOL replica set to be authoritative, follow these steps:
Click Start, click Run, type regedit, and then click OK.
Locate and then click the BurFlags entry under the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NtFrs\Parameters\Cumulative
Replica Sets\GUID
GUID is the GUID of the domain system volume replica set that is shown in the following
registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NtFrs\Parameters\Replica
Sets\GUID
Right-click BurFlags, and then click Modify.
Type D4 in the Value Data field (HexaDecimal), and then click OK.
3. restarted FRS service on old DC.
4. restarted FRS service on new DC.
After this I could see event logs saying FRS was now working and I confirmed sysvol and netlogon shares now existed on the new DC using net share command.
Thanks. -
SBS 2011 no longer issues DHCP leases: DHCP, DNS, and AD Errors
Hi all. On early 8/13/2012 and into the morning, our UPS failed several times. The battery seems to be fine but the unit was shutting off power to the unit which means the (Windows SBS 2011 Standard) server shut off unexpectedly several times.I replaced
the UPS.
Now I'm trying to figure out what in the world this did to the server. It seems DHCP, DNS, and AD all have issues, as seen in the logs below. The client PC's are going offline one-by-one because the leases are expiring and it can't connect to the server
to renew. When trying to start the DHCP service, I get a 20013 error saying it cannot be started.
So I attempted to follow a kb article and repair the database but that didn't work because it seems the Jetpack utility is not in SBS 2011? And even at that, I'm thinking it may not even be a corrupted DHCP database due to the other errors in the event log.
This is a small office and I only know enough to be dangerous but usually I can just follow a kb to fix any issues. But there are so many errors, this one has me stumped.. Could any Server whizzes identify the big picture here?
Level Date and Time Source Event ID Task Category
Critical 8/13/2012 1:33:12 PM Microsoft-Windows-Kernel-Power 41 (63) The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Critical 8/13/2012 11:30:37 AM Microsoft-Windows-Kernel-Power 41 (63) The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Critical 8/13/2012 8:23:24 AM Microsoft-Windows-Kernel-Power 41 (63) The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Critical 8/13/2012 8:05:08 AM Microsoft-Windows-Kernel-Power 41 (63) The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Critical 8/13/2012 7:38:04 AM Microsoft-Windows-Kernel-Power 41 (63) The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Critical 8/13/2012 7:29:29 AM Microsoft-Windows-Kernel-Power 41 (63) The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Critical 8/13/2012 12:55:11 AM Microsoft-Windows-Kernel-Power 41 (63) The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Critical 8/13/2012 12:15:49 AM Microsoft-Windows-Kernel-Power 41 (63) The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Critical 8/13/2012 12:09:49 AM Microsoft-Windows-Kernel-Power 41 (63) The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Level Date and Time Source Event ID Task Category
Error 8/15/2012 12:48:02 PM ADWS 1202 ADWS Instance Events "This computer is now hosting the specified directory instance, but Active Directory Web Services could not service it. Active Directory Web Services will retry this operation periodically.
Directory instance: NTDS
Directory instance LDAP port: 389
Directory instance SSL port: 636
Error 8/14/2012 2:23:37 PM ADWS 1202 ADWS Instance Events "This computer is now hosting the specified directory instance, but Active Directory Web Services could not service it. Active Directory Web Services will retry this operation periodically.
Directory instance: NTDS
Directory instance LDAP port: 389
Directory instance SSL port: 636
Error 8/14/2012 1:14:33 PM ADWS 1202 ADWS Instance Events "This computer is now hosting the specified directory instance, but Active Directory Web Services could not service it. Active Directory Web Services will retry this operation periodically.
Directory instance: NTDS
Directory instance LDAP port: 389
Directory instance SSL port: 636
Error 8/13/2012 8:06:12 AM ADWS 1202 ADWS Instance Events "This computer is now hosting the specified directory instance, but Active Directory Web Services could not service it. Active Directory Web Services will retry this operation periodically.
Directory instance: NTDS
Directory instance LDAP port: 389
Directory instance SSL port: 636
Error 8/13/2012 7:38:59 AM ADWS 1202 ADWS Instance Events "This computer is now hosting the specified directory instance, but Active Directory Web Services could not service it. Active Directory Web Services will retry this operation periodically.
Directory instance: NTDS
Directory instance LDAP port: 389
Directory instance SSL port: 636
Error 8/13/2012 12:16:52 AM ADWS 1202 ADWS Instance Events "This computer is now hosting the specified directory instance, but Active Directory Web Services could not service it. Active Directory Web Services will retry this operation periodically.
Directory instance: NTDS
Directory instance LDAP port: 389
Directory instance SSL port: 636
Error 5/31/2012 12:00:19 PM ADWS 1202 ADWS Instance Events "This computer is now hosting the specified directory instance, but Active Directory Web Services could not service it. Active Directory Web Services will retry this operation periodically.
Directory instance: NTDS
Directory instance LDAP port: 389
Directory instance SSL port: 636
Error 5/31/2012 11:14:20 AM ADWS 1202 ADWS Instance Events "This computer is now hosting the specified directory instance, but Active Directory Web Services could not service it. Active Directory Web Services will retry this operation periodically.
Directory instance: NTDS
Directory instance LDAP port: 389
Directory instance SSL port: 636
Error 4/18/2012 4:32:07 PM ADWS 1202 ADWS Instance Events "This computer is now hosting the specified directory instance, but Active Directory Web Services could not service it. Active Directory Web Services will retry this operation periodically.
Directory instance: NTDS
Directory instance LDAP port: 389
Directory instance SSL port: 636
Error 9/2/2011 2:14:09 AM ADWS 1202 ADWS Instance Events "This computer is now hosting the specified directory instance, but Active Directory Web Services could not service it. Active Directory Web Services will retry this operation periodically.
Directory instance: NTDS
Directory instance LDAP port: 389
Directory instance SSL port: 636
Error 8/30/2011 11:37:18 PM ADWS 1202 ADWS Instance Events "This computer is now hosting the specified directory instance, but Active Directory Web Services could not service it. Active Directory Web Services will retry this operation periodically.
Directory instance: NTDS
Directory instance LDAP port: 389
Directory instance SSL port: 636
Error 8/23/2011 1:52:28 PM ADWS 1202 ADWS Instance Events "This computer is now hosting the specified directory instance, but Active Directory Web Services could not service it. Active Directory Web Services will retry this operation periodically.
Directory instance: NTDS
Directory instance LDAP port: 389
Directory instance SSL port: 636
Level Date and Time Source Event ID Task Category
Error 8/15/2012 8:23:17 PM Microsoft-Windows-DHCP-Server 1004 None "The DHCP service failed to initialize the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/15/2012 2:45:22 PM Microsoft-Windows-DHCP-Server 1004 None "The DHCP service failed to initialize the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/15/2012 12:52:46 PM Microsoft-Windows-DHCP-Server 1004 None "The DHCP service failed to initialize the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/15/2012 12:52:38 PM Microsoft-Windows-DHCP-Server 1004 None "The DHCP service failed to initialize the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/15/2012 12:52:17 PM Microsoft-Windows-DHCP-Server 1004 None "The DHCP service failed to initialize the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/15/2012 12:48:02 PM Microsoft-Windows-DHCP-Server 1004 None "The DHCP service failed to initialize the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/15/2012 12:27:04 PM Microsoft-Windows-DHCP-Server 1004 None "The DHCP service failed to initialize the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/15/2012 12:22:27 PM Microsoft-Windows-DHCP-Server 1004 None "The DHCP service failed to initialize the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/14/2012 8:03:57 PM Microsoft-Windows-DHCP-Server 1004 None "The DHCP service failed to initialize the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/14/2012 8:03:35 PM Microsoft-Windows-DHCP-Server 1004 None "The DHCP service failed to initialize the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/14/2012 7:52:07 PM Microsoft-Windows-DHCP-Server 1004 None "The DHCP service failed to initialize the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/14/2012 7:48:46 PM Microsoft-Windows-DHCP-Server 1004 None "The DHCP service failed to initialize the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/14/2012 7:28:39 PM Microsoft-Windows-DHCP-Server 1004 None "The DHCP service failed to initialize the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/14/2012 4:47:56 PM Microsoft-Windows-DHCP-Server 1004 None "The DHCP service failed to initialize the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/14/2012 3:41:50 PM Microsoft-Windows-DHCP-Server 1004 None "The DHCP service failed to initialize the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/14/2012 2:53:42 PM Microsoft-Windows-DHCP-Server 1004 None "The DHCP service failed to initialize the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/14/2012 2:42:26 PM Microsoft-Windows-DHCP-Server 1004 None "The DHCP service failed to initialize the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/14/2012 2:42:08 PM Microsoft-Windows-DHCP-Server 1004 None "The DHCP service failed to initialize the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/14/2012 2:23:24 PM Microsoft-Windows-DHCP-Server 1004 None "The DHCP service failed to initialize the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/14/2012 2:16:13 PM Microsoft-Windows-DHCP-Server 1004 None "The DHCP service failed to initialize the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/14/2012 1:14:33 PM Microsoft-Windows-DHCP-Server 1004 None "The DHCP service failed to initialize the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/13/2012 1:33:58 PM Microsoft-Windows-DHCP-Server 1004 None "The DHCP service failed to initialize the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/13/2012 11:48:37 AM Microsoft-Windows-DHCP-Server 1004 None "The DHCP service failed to initialize the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/13/2012 11:45:31 AM Microsoft-Windows-DHCP-Server 1004 None "The DHCP service failed to initialize the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/13/2012 11:41:43 AM Microsoft-Windows-DHCP-Server 1004 None "The DHCP service failed to initialize the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/13/2012 11:39:43 AM Microsoft-Windows-DHCP-Server 1004 None "The DHCP service failed to initialize the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/13/2012 11:31:22 AM Microsoft-Windows-DHCP-Server 1004 None "The DHCP service failed to initialize the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/13/2012 8:24:08 AM Microsoft-Windows-DHCP-Server 1004 None "The DHCP service failed to initialize the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/13/2012 8:06:12 AM Microsoft-Windows-DHCP-Server 1004 None "The DHCP service failed to initialize the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/13/2012 7:38:47 AM Microsoft-Windows-DHCP-Server 1004 None "The DHCP service failed to initialize the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/13/2012 7:30:14 AM Microsoft-Windows-DHCP-Server 1004 None "The DHCP service failed to initialize the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/13/2012 12:55:59 AM Microsoft-Windows-DHCP-Server 1004 None "The DHCP service failed to initialize the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/13/2012 12:16:52 AM Microsoft-Windows-DHCP-Server 1004 None "The DHCP service failed to initialize the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Level Date and Time Source Event ID Task Category
Error 8/15/2012 12:52:46 PM Microsoft-Windows-DHCP-Server 1008 None "The DHCP service is shutting down due to the following error:
The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""%2"" (Server IP Address %1)
Error 8/15/2012 12:52:38 PM Microsoft-Windows-DHCP-Server 1008 None "The DHCP service is shutting down due to the following error:
The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""%2"" (Server IP Address %1)
Error 8/15/2012 12:52:17 PM Microsoft-Windows-DHCP-Server 1008 None "The DHCP service is shutting down due to the following error:
The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""%2"" (Server IP Address %1)
Error 8/15/2012 12:48:02 PM Microsoft-Windows-DHCP-Server 1008 None "The DHCP service is shutting down due to the following error:
The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""%2"" (Server IP Address %1)
Error 8/15/2012 12:27:04 PM Microsoft-Windows-DHCP-Server 1008 None "The DHCP service is shutting down due to the following error:
The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""%2"" (Server IP Address %1)
Error 8/15/2012 12:22:27 PM Microsoft-Windows-DHCP-Server 1008 None "The DHCP service is shutting down due to the following error:
The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""%2"" (Server IP Address %1)
Error 8/14/2012 8:03:57 PM Microsoft-Windows-DHCP-Server 1008 None "The DHCP service is shutting down due to the following error:
The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""%2"" (Server IP Address %1)
Error 8/14/2012 8:03:35 PM Microsoft-Windows-DHCP-Server 1008 None "The DHCP service is shutting down due to the following error:
The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""%2"" (Server IP Address %1)
Error 8/14/2012 7:52:07 PM Microsoft-Windows-DHCP-Server 1008 None "The DHCP service is shutting down due to the following error:
The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""%2"" (Server IP Address %1)
Error 8/14/2012 7:48:47 PM Microsoft-Windows-DHCP-Server 1008 None "The DHCP service is shutting down due to the following error:
The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""%2"" (Server IP Address %1)
Error 8/14/2012 7:28:40 PM Microsoft-Windows-DHCP-Server 1008 None "The DHCP service is shutting down due to the following error:
The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""%2"" (Server IP Address %1)
Error 8/14/2012 4:47:56 PM Microsoft-Windows-DHCP-Server 1008 None "The DHCP service is shutting down due to the following error:
The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""%2"" (Server IP Address %1)
Error 8/14/2012 3:41:50 PM Microsoft-Windows-DHCP-Server 1008 None "The DHCP service is shutting down due to the following error:
The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""%2"" (Server IP Address %1)
Error 8/14/2012 2:53:42 PM Microsoft-Windows-DHCP-Server 1008 None "The DHCP service is shutting down due to the following error:
The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""%2"" (Server IP Address %1)
Error 8/14/2012 2:42:26 PM Microsoft-Windows-DHCP-Server 1008 None "The DHCP service is shutting down due to the following error:
The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""%2"" (Server IP Address %1)
Error 8/14/2012 2:42:08 PM Microsoft-Windows-DHCP-Server 1008 None "The DHCP service is shutting down due to the following error:
The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""%2"" (Server IP Address %1)
Error 8/14/2012 2:23:25 PM Microsoft-Windows-DHCP-Server 1008 None "The DHCP service is shutting down due to the following error:
The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""%2"" (Server IP Address %1)
Error 8/14/2012 2:16:13 PM Microsoft-Windows-DHCP-Server 1008 None "The DHCP service is shutting down due to the following error:
The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""%2"" (Server IP Address %1)
Error 8/14/2012 1:14:33 PM Microsoft-Windows-DHCP-Server 1008 None "The DHCP service is shutting down due to the following error:
The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""%2"" (Server IP Address %1)
Error 8/13/2012 1:33:59 PM Microsoft-Windows-DHCP-Server 1008 None "The DHCP service is shutting down due to the following error:
The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""%2"" (Server IP Address %1)
Error 8/13/2012 11:48:37 AM Microsoft-Windows-DHCP-Server 1008 None "The DHCP service is shutting down due to the following error:
The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""%2"" (Server IP Address %1)
Error 8/13/2012 11:45:33 AM Microsoft-Windows-DHCP-Server 1008 None "The DHCP service is shutting down due to the following error:
The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""%2"" (Server IP Address %1)
Error 8/13/2012 11:41:43 AM Microsoft-Windows-DHCP-Server 1008 None "The DHCP service is shutting down due to the following error:
The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""%2"" (Server IP Address %1)
Error 8/13/2012 11:39:43 AM Microsoft-Windows-DHCP-Server 1008 None "The DHCP service is shutting down due to the following error:
The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""%2"" (Server IP Address %1)
Error 8/13/2012 11:31:23 AM Microsoft-Windows-DHCP-Server 1008 None "The DHCP service is shutting down due to the following error:
The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""%2"" (Server IP Address %1)
Error 8/13/2012 8:24:09 AM Microsoft-Windows-DHCP-Server 1008 None "The DHCP service is shutting down due to the following error:
The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""%2"" (Server IP Address %1)
Error 8/13/2012 8:06:13 AM Microsoft-Windows-DHCP-Server 1008 None "The DHCP service is shutting down due to the following error:
The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""%2"" (Server IP Address %1)
Error 8/13/2012 7:38:48 AM Microsoft-Windows-DHCP-Server 1008 None "The DHCP service is shutting down due to the following error:
The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""%2"" (Server IP Address %1)
Error 8/13/2012 12:55:59 AM Microsoft-Windows-DHCP-Server 1008 None "The DHCP service is shutting down due to the following error:
The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""%2"" (Server IP Address %1)
Error 8/13/2012 12:16:52 AM Microsoft-Windows-DHCP-Server 1008 None "The DHCP service is shutting down due to the following error:
The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""2A040000"" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain ""%2"" (Server IP Address %1)
Level Date and Time Source Event ID Task Category
Error 8/15/2012 8:23:17 PM Microsoft-Windows-DHCP-Server 1018 None "The DHCP service failed to restore the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/15/2012 2:45:22 PM Microsoft-Windows-DHCP-Server 1018 None "The DHCP service failed to restore the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/15/2012 12:52:46 PM Microsoft-Windows-DHCP-Server 1018 None "The DHCP service failed to restore the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/15/2012 12:52:38 PM Microsoft-Windows-DHCP-Server 1018 None "The DHCP service failed to restore the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/15/2012 12:52:17 PM Microsoft-Windows-DHCP-Server 1018 None "The DHCP service failed to restore the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/15/2012 12:48:02 PM Microsoft-Windows-DHCP-Server 1018 None "The DHCP service failed to restore the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/15/2012 12:27:04 PM Microsoft-Windows-DHCP-Server 1018 None "The DHCP service failed to restore the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/15/2012 12:22:27 PM Microsoft-Windows-DHCP-Server 1018 None "The DHCP service failed to restore the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/14/2012 8:03:57 PM Microsoft-Windows-DHCP-Server 1018 None "The DHCP service failed to restore the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/14/2012 8:03:35 PM Microsoft-Windows-DHCP-Server 1018 None "The DHCP service failed to restore the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/14/2012 7:52:07 PM Microsoft-Windows-DHCP-Server 1018 None "The DHCP service failed to restore the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/14/2012 7:48:47 PM Microsoft-Windows-DHCP-Server 1018 None "The DHCP service failed to restore the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/14/2012 7:28:40 PM Microsoft-Windows-DHCP-Server 1018 None "The DHCP service failed to restore the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/14/2012 4:47:56 PM Microsoft-Windows-DHCP-Server 1018 None "The DHCP service failed to restore the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/14/2012 3:41:50 PM Microsoft-Windows-DHCP-Server 1018 None "The DHCP service failed to restore the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/14/2012 2:53:42 PM Microsoft-Windows-DHCP-Server 1018 None "The DHCP service failed to restore the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/14/2012 2:42:26 PM Microsoft-Windows-DHCP-Server 1018 None "The DHCP service failed to restore the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/14/2012 2:42:08 PM Microsoft-Windows-DHCP-Server 1018 None "The DHCP service failed to restore the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/14/2012 2:23:25 PM Microsoft-Windows-DHCP-Server 1018 None "The DHCP service failed to restore the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/14/2012 2:16:13 PM Microsoft-Windows-DHCP-Server 1018 None "The DHCP service failed to restore the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/14/2012 1:14:33 PM Microsoft-Windows-DHCP-Server 1018 None "The DHCP service failed to restore the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/13/2012 1:33:59 PM Microsoft-Windows-DHCP-Server 1018 None "The DHCP service failed to restore the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/13/2012 11:48:37 AM Microsoft-Windows-DHCP-Server 1018 None "The DHCP service failed to restore the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/13/2012 11:45:33 AM Microsoft-Windows-DHCP-Server 1018 None "The DHCP service failed to restore the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/13/2012 11:41:43 AM Microsoft-Windows-DHCP-Server 1018 None "The DHCP service failed to restore the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/13/2012 11:39:43 AM Microsoft-Windows-DHCP-Server 1018 None "The DHCP service failed to restore the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/13/2012 11:31:23 AM Microsoft-Windows-DHCP-Server 1018 None "The DHCP service failed to restore the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/13/2012 8:24:09 AM Microsoft-Windows-DHCP-Server 1018 None "The DHCP service failed to restore the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/13/2012 8:06:13 AM Microsoft-Windows-DHCP-Server 1018 None "The DHCP service failed to restore the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/13/2012 7:38:48 AM Microsoft-Windows-DHCP-Server 1018 None "The DHCP service failed to restore the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/13/2012 7:30:15 AM Microsoft-Windows-DHCP-Server 1018 None "The DHCP service failed to restore the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/13/2012 12:55:59 AM Microsoft-Windows-DHCP-Server 1018 None "The DHCP service failed to restore the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Error 8/13/2012 12:16:52 AM Microsoft-Windows-DHCP-Server 1018 None "The DHCP service failed to restore the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.
Level Date and Time Source Event ID Task Category
Error 8/15/2012 12:48:28 PM NtFrs 13552 None "The File Replication Service is unable to add this computer to the following replica set:
""DOMAIN SYSTEM VOLUME (SYSVOL SHARE)""
This could be caused by a number of problems such as:
-- an invalid root path,
-- a missing directory,
-- a missing disk volume,
-- a file system on the volume that does not support NTFS 5.0
The information below may help to resolve the problem:
Computer DNS name is ""SERVER2011.vhf.local""
Replica set member name is ""SERVER2011""
Replica set root path is ""c:\windows\sysvol\domain""
Replica staging directory path is ""c:\windows\sysvol\staging\domain""
Replica working directory path is ""c:\windows\ntfrs\jet""
Windows error status code is
FRS error status code is FrsErrorMismatchedJournalId
Other event log messages may also help determine the problem. Correct the problem and the service will attempt to restart replication automatically at a later time."
Error 8/15/2012 12:22:55 PM NtFrs 13552 None "The File Replication Service is unable to add this computer to the following replica set:
""DOMAIN SYSTEM VOLUME (SYSVOL SHARE)""
This could be caused by a number of problems such as:
-- an invalid root path,
-- a missing directory,
-- a missing disk volume,
-- a file system on the volume that does not support NTFS 5.0
The information below may help to resolve the problem:
Computer DNS name is ""SERVER2011.vhf.local""
Replica set member name is ""SERVER2011""
Replica set root path is ""c:\windows\sysvol\domain""
Replica staging directory path is ""c:\windows\sysvol\staging\domain""
Replica working directory path is ""c:\windows\ntfrs\jet""
Windows error status code is
FRS error status code is FrsErrorMismatchedJournalId
Other event log messages may also help determine the problem. Correct the problem and the service will attempt to restart replication automatically at a later time."
Error 8/14/2012 2:23:56 PM NtFrs 13552 None "The File Replication Service is unable to add this computer to the following replica set:
""DOMAIN SYSTEM VOLUME (SYSVOL SHARE)""
This could be caused by a number of problems such as:
-- an invalid root path,
-- a missing directory,
-- a missing disk volume,
-- a file system on the volume that does not support NTFS 5.0
The information below may help to resolve the problem:
Computer DNS name is ""SERVER2011.vhf.local""
Replica set member name is ""SERVER2011""
Replica set root path is ""c:\windows\sysvol\domain""
Replica staging directory path is ""c:\windows\sysvol\staging\domain""
Replica working directory path is ""c:\windows\ntfrs\jet""
Windows error status code is
FRS error status code is FrsErrorMismatchedJournalId
Other event log messages may also help determine the problem. Correct the problem and the service will attempt to restart replication automatically at a later time."
Error 8/14/2012 1:15:00 PM NtFrs 13552 None "The File Replication Service is unable to add this computer to the following replica set:
""DOMAIN SYSTEM VOLUME (SYSVOL SHARE)""
This could be caused by a number of problems such as:
-- an invalid root path,
-- a missing directory,
-- a missing disk volume,
-- a file system on the volume that does not support NTFS 5.0
The information below may help to resolve the problem:
Computer DNS name is ""SERVER2011.vhf.local""
Replica set member name is ""SERVER2011""
Replica set root path is ""c:\windows\sysvol\domain""
Replica staging directory path is ""c:\windows\sysvol\staging\domain""
Replica working directory path is ""c:\windows\ntfrs\jet""
Windows error status code is
FRS error status code is FrsErrorMismatchedJournalId
Other event log messages may also help determine the problem. Correct the problem and the service will attempt to restart replication automatically at a later time."
Error 8/13/2012 1:34:27 PM NtFrs 13552 None "The File Replication Service is unable to add this computer to the following replica set:
""DOMAIN SYSTEM VOLUME (SYSVOL SHARE)""
This could be caused by a number of problems such as:
-- an invalid root path,
-- a missing directory,
-- a missing disk volume,
-- a file system on the volume that does not support NTFS 5.0
The information below may help to resolve the problem:
Computer DNS name is ""SERVER2011.vhf.local""
Replica set member name is ""SERVER2011""
Replica set root path is ""c:\windows\sysvol\domain""
Replica staging directory path is ""c:\windows\sysvol\staging\domain""
Replica working directory path is ""c:\windows\ntfrs\jet""
Windows error status code is
FRS error status code is FrsErrorMismatchedJournalId
Other event log messages may also help determine the problem. Correct the problem and the service will attempt to restart replication automatically at a later time."
Error 8/13/2012 11:31:55 AM NtFrs 13552 None "The File Replication Service is unable to add this computer to the following replica set:
""DOMAIN SYSTEM VOLUME (SYSVOL SHARE)""
This could be caused by a number of problems such as:
-- an invalid root path,
-- a missing directory,
-- a missing disk volume,
-- a file system on the volume that does not support NTFS 5.0
The information below may help to resolve the problem:
Computer DNS name is ""SERVER2011.vhf.local""
Replica set member name is ""SERVER2011""
Replica set root path is ""c:\windows\sysvol\domain""
Replica staging directory path is ""c:\windows\sysvol\staging\domain""
Replica working directory path is ""c:\windows\ntfrs\jet""
Windows error status code is
FRS error status code is FrsErrorMismatchedJournalId
Other event log messages may also help determine the problem. Correct the problem and the service will attempt to restart replication automatically at a later time."
Error 8/13/2012 8:24:36 AM NtFrs 13552 None "The File Replication Service is unable to add this computer to the following replica set:
""DOMAIN SYSTEM VOLUME (SYSVOL SHARE)""
This could be caused by a number of problems such as:
-- an invalid root path,
-- a missing directory,
-- a missing disk volume,
-- a file system on the volume that does not support NTFS 5.0
The information below may help to resolve the problem:
Computer DNS name is ""SERVER2011.vhf.local""
Replica set member name is ""SERVER2011""
Replica set root path is ""c:\windows\sysvol\domain""
Replica staging directory path is ""c:\windows\sysvol\staging\domain""
Replica working directory path is ""c:\windows\ntfrs\jet""
Windows error status code is
FRS error status code is FrsErrorMismatchedJournalId
Other event log messages may also help determine the problem. Correct the problem and the service will attempt to restart replication automatically at a later time."Level Date and Time Source Event ID Task Category
Error 8/15/2012 12:48:28 PM NtFrs 13555 None "The File Replication Service is in an error state. Files will not replicate to or from one or all of the replica sets on this computer until the following recovery steps are performed:
Recovery Steps:
[1] The error state may clear itself if you stop and restart the FRS service. This can be done by performing the following in a command window:
net stop ntfrs
net start ntfrs
If this fails to clear up the problem then proceed as follows.
[2] For Active Directory Domain Services Domain Controllers that DO NOT host any DFS alternates or other replica sets with replication enabled:
If there is at least one other Domain Controller in this domain then restore the ""system state"" of this DC from backup (using ntbackup or other backup-restore utility) and make it non-authoritative.
If there are NO other Domain Controllers in this domain then restore the ""system state"" of this DC from backup (using ntbackup or other backup-restore utility) and choose the Advanced option which marks the sysvols as primary.
If there are other Domain Controllers in this domain but ALL of them have this event log message then restore one of them as primary (data files from primary will replicate everywhere) and the others as non-authoritative.
[3] For Active Directory Domain Services Domain Controllers that host DFS alternates or other replica sets with replication enabled:
(3-a) If the Dfs alternates on this DC do not have any other replication partners then copy the data under that Dfs share to a safe location.
(3-b) If this server is the only Active Directory Domain Services Domain Controller for this domain then, before going to (3-c), make sure this server does not have any inbound or outbound connections to other servers that were formerly Domain Controllers for this domain but are now off the net (and will never be coming back online) or have been fresh installed without being demoted. To delete connections use the Sites and Services snapin and look for
Sites->NAME_OF_SITE->Servers->NAME_OF_SERVER->NTDS Settings->CONNECTIONS.
(3-c) Restore the ""system state"" of this DC from backup (using ntbackup or other backup-restore utility) and make it non-authoritative.
(3-d) Copy the data from step (3-a) above to the original location after the sysvol share is published.
[4] For other Windows servers:
(4-a) If any of the DFS alternates or other replica sets hosted by this server do not have any other replication partners then copy the data under its share or replica tree root to a safe location.
(4-b) net stop ntfrs
(4-c) rd /s /q c:\windows\ntfrs\jet
(4-d) net start ntfrs
(4-e) Copy the data from step (4-a) above to the original location after the service has initialized (5 minutes is a safe waiting time).
Note: If this error message is in the eventlog of all the members of a particular replica set then perform steps (4-a) and (4-e) above on only one of the members."
Error 8/15/2012 12:22:55 PM NtFrs 13555 None "The File Replication Service is in an error state. Files will not replicate to or from one or all of the replica sets on this computer until the following recovery steps are performed:
Recovery Steps:
[1] The error state may clear itself if you stop and restart the FRS service. This can be done by performing the following in a command window:
net stop ntfrs
net start ntfrs
If this fails to clear up the problem then proceed as follows.
[2] For Active Directory Domain Services Domain Controllers that DO NOT host any DFS alternates or other replica sets with replication enabled:
If there is at least one other Domain Controller in this domain then restore the ""system state"" of this DC from backup (using ntbackup or other backup-restore utility) and make it non-authoritative.
If there are NO other Domain Controllers in this domain then restore the ""system state"" of this DC from backup (using ntbackup or other backup-restore utility) and choose the Advanced option which marks the sysvols as primary.
If there are other Domain Controllers in this domain but ALL of them have this event log message then restore one of them as primary (data files from primary will replicate everywhere) and the others as non-authoritative.
[3] For Active Directory Domain Services Domain Controllers that host DFS alternates or other replica sets with replication enabled:
(3-a) If the Dfs alternates on this DC do not have any other replication partners then copy the data under that Dfs share to a safe location.
(3-b) If this server is the only Active Directory Domain Services Domain Controller for this domain then, before going to (3-c), make sure this server does not have any inbound or outbound connections to other servers that were formerly Domain Controllers for this domain but are now off the net (and will never be coming back online) or have been fresh installed without being demoted. To delete connections use the Sites and Services snapin and look for
Sites->NAME_OF_SITE->Servers->NAME_OF_SERVER->NTDS Settings->CONNECTIONS.
(3-c) Restore the ""system state"" of this DC from backup (using ntbackup or other backup-restore utility) and make it non-authoritative.
(3-d) Copy the data from step (3-a) above to the original location after the sysvol share is published.
[4] For other Windows servers:
(4-a) If any of the DFS alternates or other replica sets hosted by this server do not have any other replication partners then copy the data under its share or replica tree root to a safe location.
(4-b) net stop ntfrs
(4-c) rd /s /q c:\windows\ntfrs\jet
(4-d) net start ntfrs
(4-e) Copy the data from step (4-a) above to the original location after the service has initialized (5 minutes is a safe waiting time).
Note: If this error message is in the eventlog of all the members of a particular replica set then perform steps (4-a) and (4-e) above on only one of the members."
Error 8/14/2012 2:23:56 PM NtFrs 13555 None "The File Replication Service is in an error state. Files will not replicate to or from one or all of the replica sets on this computer until the following recovery steps are performed:
Recovery Steps:
[1] The error state may clear itself if you stop and restart the FRS service. This can be done by performing the following in a command window:
net stop ntfrs
net start ntfrs
If this fails to clear up the problem then proceed as follows.
[2] For Active Directory Domain Services Domain Controllers that DO NOT host any DFS alternates or other replica sets with replication enabled:
If there is at least one other Domain Controller in this domain then restore the ""system state"" of this DC from backup (using ntbackup or other backup-restore utility) and make it non-authoritative.
If there are NO other Domain Controllers in this domain then restore the ""system state"" of this DC from backup (using ntbackup or other backup-restore utility) and choose the Advanced option which marks the sysvols as primary.
If there are other Domain Controllers in this domain but ALL of them have this event log message then restore one of them as primary (data files from primary will replicate everywhere) and the others as non-authoritative.
[3] For Active Directory Domain Services Domain Controllers that host DFS alternates or other replica sets with replication enabled:
(3-a) If the Dfs alternates on this DC do not have any other replication partners then copy the data under that Dfs share to a safe location.
(3-b) If this server is the only Active Directory Domain Services Domain Controller for this domain then, before going to (3-c), make sure this server does not have any inbound or outbound connections to other servers that were formerly Domain Controllers for this domain but are now off the net (and will never be coming back online) or have been fresh installed without being demoted. To delete connections use the Sites and Services snapin and look for
Sites->NAME_OF_SITE->Servers->NAME_OF_SERVER->NTDS Settings->CONNECTIONS.
(3-c) Restore the ""system state"" of this DC from backup (using ntbackup or other backup-restore utility) and make it non-authoritative.
(3-d) Copy the data from step (3-a) above to the original location after the sysvol share is published.
[4] For other Windows servers:
(4-a) If any of the DFS alternates or other replica sets hosted by this server do not have any other replication partners then copy the data under its share or replica tree root to a safe location.
(4-b) net stop ntfrs
(4-c) rd /s /q c:\windows\ntfrs\jet
(4-d) net start ntfrs
(4-e) Copy the data from step (4-a) above to the original location after the service has initialized (5 minutes is a safe waiting time).
Note: If this error message is in the eventlog of all the members of a particular replica set then perform steps (4-a) and (4-e) above on only one of the members."
Error 8/14/2012 1:15:00 PM NtFrs 13555 None "The File Replication Service is in an error state. Files will not replicate to or from one or all of the replica sets on this computer until the following recovery steps are performed:
Recovery Steps:
[1] The error state may clear itself if you stop and restart the FRS service. This can be done by performing the following in a command window:
net stop ntfrs
net start ntfrs
If this fails to clear up the problem then proceed as follows.
[2] For Active Directory Domain Services Domain Controllers that DO NOT host any DFS alternates or other replica sets with replication enabled:
If there is at least one other Domain Controller in this domain then restore the ""system state"" of this DC from backup (using ntbackup or other backup-restore utility) and make it non-authoritative.
If there are NO other Domain Controllers in this domain then restore the ""system state"" of this DC from backup (using ntbackup or other backup-restore utility) and choose the Advanced option which marks the sysvols as primary.
If there are other Domain Controllers in this domain but ALL of them have this event log message then restore one of them as primary (data files from primary will replicate everywhere) and the others as non-authoritative.
[3] For Active Directory Domain Services Domain Controllers that host DFS alternates or other replica sets with replication enabled:
(3-a) If the Dfs alternates on this DC do not have any other replication partners then copy the data under that Dfs share to a safe location.
(3-b) If this server is the only Active Directory Domain Services Domain Controller for this domain then, before going to (3-c), make sure this server does not have any inbound or outbound connections to other servers that were formerly Domain Controllers for this domain but are now off the net (and will never be coming back online) or have been fresh installed without being demoted. To delete connections use the Sites and Services snapin and look for
Sites->NAME_OF_SITE->Servers->NAME_OF_SERVER->NTDS Settings->CONNECTIONS.
(3-c) Restore the ""system state"" of this DC from backup (using ntbackup or other backup-restore utility) and make it non-authoritative.
(3-d) Copy the data from step (3-a) above to the original location after the sysvol share is published.
[4] For other Windows servers:
(4-a) If any of the DFS alternates or other replica sets hosted by this server do not have any other replication partners then copy the data under its share or replica tree root to a safe location.
(4-b) net stop ntfrs
(4-c) rd /s /q c:\windows\ntfrs\jet
(4-d) net start ntfrs
(4-e) Copy the data from step (4-a) above to the original location after the service has initialized (5 minutes is a safe waiting time).
Note: If this error message is in the eventlog of all the members of a particular replica set then perform steps (4-a) and (4-e) above on only one of the members."
Error 8/13/2012 1:34:27 PM NtFrs 13555 None "The File Replication Service is in an error state. Files will not replicate to or from one or all of the replica sets on this computer until the following recovery steps are performed:
Recovery Steps:
[1] The error state may clear itself if you stop and restart the FRS service. This can be done by performing the following in a command window:
net stop ntfrs
net start ntfrs
If this fails to clear up the problem then proceed as follows.
[2] For Active Directory Domain Services Domain Controllers that DO NOT host any DFS alternates or other replica sets with replication enabled:
If there is at least one other Domain Controller in this domain then restore the ""system state"" of this DC from backup (using ntbackup or other backup-restore utility) and make it non-authoritative.
If there are NO other Domain Controllers in this domain then restore the ""system state"" of this DC from backup (using ntbackup or other backup-restore utility) and choose the Advanced option which marks the sysvols as primary.
If there are other Domain Controllers in this domain but ALL of them have this event log message then restore one of them as primary (data files from primary will replicate everywhere) and the others as non-authoritative.
[3] For Active Directory Domain Services Domain Controllers that host DFS alternates or other replica sets with replication enabled:
(3-a) If the Dfs alternates on this DC do not have any other replication partners then copy the data under that Dfs share to a safe location.
(3-b) If this server is the only Active Directory Domain Services Domain Controller for this domain then, before going to (3-c), make sure this server does not have any inbound or outbound connections to other servers that were formerly Domain Controllers for this domain but are now off the net (and will never be coming back online) or have been fresh installed without being demoted. To delete connections use the Sites and Services snapin and look for
Sites->NAME_OF_SITE->Servers->NAME_OF_SERVER->NTDS Settings->CONNECTIONS.
(3-c) Restore the ""system state"" of this DC from backup (using ntbackup or other backup-restore utility) and make it non-authoritative.
(3-d) Copy the data from step (3-a) above to the original location after the sysvol share is published.
[4] For other Windows servers:
(4-a) If any of the DFS alternates or other replica sets hosted by this server do not have any other replication partners then copy the data under its share or replica tree root to a safe location.
(4-b) net stop ntfrs
(4-c) rd /s /q c:\windows\ntfrs\jet
(4-d) net start ntfrs
(4-e) Copy the data from step (4-a) above to the original location after the service has initialized (5 minutes is a safe waiting time).
Note: If this error message is in the eventlog of all the members of a particular replica set then perform steps (4-a) and (4-e) above on only one of the members."
Error 8/13/2012 11:31:55 AM NtFrs 13555 None "The File Replication Service is in an error state. Files will not replicate to or from one or all of the replica sets on this computer until the following recovery steps are performed:
Recovery Steps:
[1] The error state may clear itself if you stop and restart the FRS service. This can be done by performing the following in a command window:
net stop ntfrs
net start ntfrs
If this fails to clear up the problem then proceed as follows.
[2] For Active Directory Domain Services Domain Controllers that DO NOT host any DFS alternates or other replica sets with replication enabled:
If there is at least one other Domain Controller in this domain then restore the ""system state"" of this DC from backup (using ntbackup or other backup-restore utility) and make it non-authoritative.
If there are NO other Domain Controllers in this domain then restore the ""system state"" of this DC from backup (using ntbackup or other backup-restore utility) and choose the Advanced option which marks the sysvols as primary.
If there are other Domain Controllers in this domain but ALL of them have this event log message then restore one of them as primary (data files from primary will replicate everywhere) and the others as non-authoritative.
[3] For Active Directory Domain Services Domain Controllers that host DFS alternates or other replica sets with replication enabled:
(3-a) If the Dfs alternates on this DC do not have any other replication partners then copy the data under that Dfs share to a safe location.
(3-b) If this server is the only Active Directory Domain Services Domain Controller for this domain then, before going to (3-c), make sure this server does not have any inbound or outbound connections to other servers that were formerly Domain Controllers for this domain but are now off the net (and will never be coming back online) or have been fresh installed without being demoted. To delete connections use the Sites and Services snapin and look for
Sites->NAME_OF_SITE->Servers->NAME_OF_SERVER->NTDS Settings->CONNECTIONS.
(3-c) Restore the ""system state"" of this DC from backup (using ntbackup or other backup-restore utility) and make it non-authoritative.
(3-d) Copy the data from step (3-a) above to the original location after the sysvol share is published.
[4] For other Windows servers:
(4-a) If any of the DFS alternates or other replica sets hosted by this server do not have any other replication partners then copy the data under its share or replica tree root to a safe location.
(4-b) net stop ntfrs
(4-c) rd /s /q c:\windows\ntfrs\jet
(4-d) net start ntfrs
(4-e) Copy the data from step (4-a) above to the original location after the service has initialized (5 minutes is a safe waiting time).
Note: If this error message is in the eventlog of all the members of a particular replica set then perform steps (4-a) and (4-e) above on only one of the members."
Error 8/13/2012 8:24:36 AM NtFrs 13555 None "The File Replication Service is in an error state. Files will not replicate to or from one or all of the replica sets on this computer until the following recovery steps are performed:
Recovery Steps:
[1] The error state may clear itself if you stop and restart the FRS service. This can be done by performing the following in a command window:
net stop ntfrs
net start ntfrs
If this fails to clear up the problem then proceed as follows.
[2] For Active Directory Domain Services Domain Controllers that DO NOT host any DFS alternates or other replica sets with replication enabled:
If there is at least one other Domain Controller in this domain then restore the ""system state"" of this DC from backup (using ntbackup or other backup-restore utility) and make it non-authoritative.
If there are NO other Domain Controllers in this domain then restore the ""system state"" of this DC from backup (using ntbackup or other backup-restore utility) and choose the Advanced option which marks the sysvols as primary.
If there are other Domain Controllers in this domain but ALL of them have this event log message then restore one of them as primary (data files from primary will replicate everywhere) and the others as non-authoritative.
[3] For Active Directory Domain Services Domain Controllers that host DFS alternates or other replica sets with replication enabled:
(3-a) If the Dfs alternates on this DC do not have any other replication partners then copy the data under that Dfs share to a safe location.
(3-b) If this server is the only Active Directory Domain Services Domain Controller for this domain then, before going to (3-c), make sure this server does not have any inbound or outbound connections to other servers that were formerly Domain Controllers for this domain but are now off the net (and will never be coming back online) or have been fresh installed without being demoted. To delete connections use the Sites and Services snapin and look for
Sites->NAME_OF_SITE->Servers->NAME_OF_SERVER->NTDS Settings->CONNECTIONS.
(3-c) Restore the ""system state"" of this DC from backup (using ntbackup or other backup-restore utility) and make it non-authoritative.
(3-d) Copy the data from step (3-a) above to the original location after the sysvol share is published.
[4] For other Windows servers:
(4-a) If any of the DFS alternates or other replica sets hosted by this server do not have any other replication partners then copy the data under its share or replica tree root to a safe location.
(4-b) net stop ntfrs
(4-c) rd /s /q c:\windows\ntfrs\jet
(4-d) net start ntfrs
(4-e) Copy the data from step (4-a) above to the original location after the service has initialized (5 minutes is a safe waiting time).
Note: If this error message is in the eventlog of all the members of a particular replica set then perform steps (4-a) and (4-e) above on only one of the members."
Level Date and Time Source Event ID Task Category
Error 8/15/2012 8:23:17 PM Service Control Manager 7024 None The DHCP Server service terminated with service-specific error %%20013.
Error 8/15/2012 2:45:22 PM Service Control Manager 7024 None The DHCP Server service terminated with service-specific error %%20013.
Error 8/15/2012 12:52:46 PM Service Control Manager 7024 None The DHCP Server service terminated with service-specific error %%20013.
Error 8/15/2012 12:52:38 PM Service Control Manager 7024 None The DHCP Server service terminated with service-specific error %%20013.
Error 8/15/2012 12:52:17 PM Service Control Manager 7024 None The DHCP Server service terminated with service-specific error %%20013.
Error 8/15/2012 12:48:22 PM Service Control Manager 7024 None The SQL Server (SBSMONITORING) service terminated with service-specific error %%17058.
Error 8/15/2012 12:48:02 PM Service Control Manager 7024 None The DHCP Server service terminated with service-specific error %%20013.
Error 8/15/2012 12:27:04 PM Service Control Manager 7024 None The DHCP Server service terminated with service-specific error %%20013.
Error 8/15/2012 12:25:19 PM Service Control Manager 7024 None The Windows Search service terminated with service-specific error %%-1073473535.
Error 8/15/2012 12:22:48 PM Service Control Manager 7024 None The SQL Server (SBSMONITORING) service terminated with service-specific error %%17058.
Error 8/15/2012 12:22:27 PM Service Control Manager 7024 None The DHCP Server service terminated with service-specific error %%20013.
Error 8/14/2012 8:03:57 PM Service Control Manager 7024 None The DHCP Server service terminated with service-specific error %%20013.
Error 8/14/2012 8:03:35 PM Service Control Manager 7024 None The DHCP Server service terminated with service-specific error %%20013.
Error 8/14/2012 7:52:07 PM Service Control Manager 7024 None The DHCP Server service terminated with service-specific error %%20013.
Error 8/14/2012 7:48:47 PM Service Control Manager 7024 None The DHCP Server service terminated with service-specific error %%20013.
Error 8/14/2012 7:28:40 PM Service Control Manager 7024 None The DHCP Server service terminated with service-specific error %%20013.
Error 8/14/2012 4:47:56 PM Service Control Manager 7024 None The DHCP Server service terminated with service-specific error %%20013.
Error 8/14/2012 3:41:50 PM Service Control Manager 7024 None The DHCP Server service terminated with service-specific error %%20013.
Error 8/14/2012 2:53:42 PM Service Control Manager 7024 None The DHCP Server service terminated with service-specific error %%20013.
Error 8/14/2012 2:42:26 PM Service Control Manager 7024 None The DHCP Server service terminated with service-specific error %%20013.
Error 8/14/2012 2:42:08 PM Service Control Manager 7024 None The DHCP Server service terminated with service-specific error %%20013.
Error 8/14/2012 2:23:25 PM Service Control Manager 7024 None The DHCP Server service terminated with service-specific error %%20013.
Error 8/14/2012 2:16:13 PM Service Control Manager 7024 None The DHCP Server service terminated with service-specific error %%20013.
Error 8/14/2012 1:14:33 PM Service Control Manager 7024 None The DHCP Server service terminated with service-specific error %%20013.
Error 8/13/2012 1:33:59 PM Service Control Manager 7024 None The DHCP Server service terminated with service-specific error %%20013.
Error 8/13/2012 11:48:37 AM Service Control Manager 7024 None The DHCP Server service terminated with service-specific error %%20013.
Error 8/13/2012 11:45:33 AM Service Control Manager 7024 None The DHCP Server service terminated with service-specific error %%20013.
Error 8/13/2012 11:41:43 AM Service Control Manager 7024 None The DHCP Server service terminated with service-specific error %%20013.
Error 8/13/2012 11:39:43 AM Service Control Manager 7024 None The DHCP Server service terminated with service-specific error %%20013.
Error 8/13/2012 11:31:23 AM Service Control Manager 7024 None The DHCP Server service terminated with service-specific error %%20013.
Error 8/13/2012 8:24:09 AM Service Control Manager 7024 None The DHCP Server service terminated with service-specific error %%20013.
Error 8/13/2012 8:06:13 AM Service Control Manager 7024 None The DHCP Server service terminated with service-specific error %%20013.
Error 8/13/2012 7:38:48 AM Service Control Manager 7024 None The DHCP Server service terminated with service-specific error %%20013.
Error 8/13/2012 12:55:59 AM Service Control Manager 7024 None The DHCP Server service terminated with service-specific error %%20013.
Error 8/13/2012 12:16:52 AM Service Control Manager 7024 None The DHCP Server service terminated with service-specific error %%20013. -
Domain either does not exist or could not be contacted
Ok where to start!
Existing 2003 domain (2x DC)
New 2012 server - i have followed https://www.youtube.com/watch?v=OG5K6B7hgRU as i hadn't done a migration to 2012
Everything was generally ok, Active Directory appeared in sync as i had the users/computers etc before seizing the roles and these where confirmed by using 'netdom query fsmo'
Now there was FRS errors in the event log;
File Replication Service is scanning the data in the system volume. Computer SERVER-AD cannot become a domain controller until this process is complete. The system volume will then be shared as SYSVOL.
and
The File Replication Service has detected an enabled disk write cache on the drive containing the directory c:\windows\ntfrs\jet on the computer SERVER-AD. The File Replication Service might not recover when power to the drive is interrupted and critical
updates are lost.
The 2003 SBS log was suggesting it was in a RNL_WRAP_ERROR so i looked at one of the log and said to set the value one '1' for 'Enable Journal Wrap Automatic Restore' and this is where i think it went pear shaped!!!!!!
Entry was ' 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.' --- this is still set to value '1' do i need to change
to '0'????
So running through the FRS log entries i have ' 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.'
'The File Replication Service moved the preexisting files in c:\windows\sysvol\domain to c:\windows\sysvol\domain\NtFrs_PreExisting___See_EventLog.
The File Replication Service may delete the files in c:\windows\sysvol\domain\NtFrs_PreExisting___See_EventLog at any time. Files can be saved from deletion by copying them out of c:\windows\sysvol\domain\NtFrs_PreExisting___See_EventLog. Copying the files
into c:\windows\sysvol\domain may lead to name conflicts if the files already exist on some other replicating partner.
In some cases, the File Replication Service may copy a file from c:\windows\sysvol\domain\NtFrs_PreExisting___See_EventLog into c:\windows\sysvol\domain instead of replicating the file from some other replicating partner. '
'The File Replication Service successfully added this computer to the following replica set:
"DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"
Information related to this event is shown below:
Computer DNS name is "rookesbs.Rooke.local"
Replica set member name is "ROOKESBS"
Replica set root path is "c:\windows\sysvol\domain"
Replica staging directory path is "c:\windows\sysvol\staging\domain"
Replica working directory path is "c:\windows\ntfrs\jet"'
'The File Replication Service successfully added the connections shown below to the replica set:
"DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"
"rooketerm.Rooke.local"
"SERVER-AD.Rooke.local"
"rooketerm.Rooke.local"
"SERVER-AD.Rooke.local" '
SERVER-AD is the NEW server (master) and rooketerm is another 2003 member server
'The File Replication Service is having trouble enabling replication from ROOKETERM to ROOKESBS for c:\windows\sysvol\domain using the DNS name rooketerm.Rooke.local.' --- and getting the same for SERVER-AD
Now the SYSVOL folder SHARE had gone but looking there is a backup in that folder?
NOW i have 'NtFrs_PreExisting___See_EventLog' in the 2003 SBS SYSVOL folder -- can i use this?
I DONT HAVE A BACKUP OF SYSVOL -- i can maybe able to get an old backup of Backup exec SRS but NAS has been down :(
Now naturally how things are i can't access Active Directory on any server as it says not available/found etc
IS this going to stop users logging on in the morning??
REALLY need some urgent help!I also ran a NSLOOKUP to make sure DNS was ok - as i changed the order of DNS on SERVER-AD as the 2003 SBS server was first however those appear to be in sync anyhow - results of the lookup
> _ldap._tcp.dc._msdcs.rooke.local
Server: UnKnown
Address: ::1
_ldap._tcp.dc._msdcs.rooke.local SRV service location:
priority = 0
weight = 100
port = 389
svr hostname = server-ad.rooke.local
_ldap._tcp.dc._msdcs.rooke.local SRV service location:
priority = 0
weight = 100
port = 389
svr hostname = rooketerm.rooke.local
_ldap._tcp.dc._msdcs.rooke.local SRV service location:
priority = 0
weight = 100
port = 389
svr hostname = rookesbs.rooke.local
server-ad.rooke.local internet address = 192.168.1.21
server-ad.rooke.local AAAA IPv6 address = 2001:0:9d38:6ab8:20b5:74ee:2bfd:eff5
rooketerm.rooke.local internet address = 192.168.1.5
rookesbs.rooke.local internet address = 192.168.1.3
This all appears OK to me :)
Also SHOWREPL results
Repadmin: running command /showrepl against full DC localhost
Default-First-Site-Name\SERVER-AD
DSA Options: IS_GC
Site Options: (none)
DSA object GUID: 66f0b91a-f210-4a53-a1a9-4f585114c181
DSA invocationID: 15db3e56-e573-4c7e-a487-4a9259e7b6bd
==== INBOUND NEIGHBORS ======================================
DC=Rooke,DC=local
Default-First-Site-Name\ROOKETERM via RPC
DSA object GUID: bad19e19-a045-410f-8854-5d06d7cb5bb1
Last attempt @ 2014-03-12 18:26:07 was successful.
Default-First-Site-Name\ROOKESBS via RPC
DSA object GUID: 11aecea4-d53e-48b8-9c68-f996cca7e72e
Last attempt @ 2014-03-12 18:28:44 was successful.
CN=Configuration,DC=Rooke,DC=local
Default-First-Site-Name\ROOKESBS via RPC
DSA object GUID: 11aecea4-d53e-48b8-9c68-f996cca7e72e
Last attempt @ 2014-03-12 18:08:39 was successful.
Default-First-Site-Name\ROOKETERM via RPC
DSA object GUID: bad19e19-a045-410f-8854-5d06d7cb5bb1
Last attempt @ 2014-03-12 18:08:52 was successful.
CN=Schema,CN=Configuration,DC=Rooke,DC=local
Default-First-Site-Name\ROOKESBS via RPC
DSA object GUID: 11aecea4-d53e-48b8-9c68-f996cca7e72e
Last attempt @ 2014-03-12 18:08:28 was successful.
Default-First-Site-Name\ROOKETERM via RPC
DSA object GUID: bad19e19-a045-410f-8854-5d06d7cb5bb1
Last attempt @ 2014-03-12 18:08:32 was successful.
DC=ForestDnsZones,DC=Rooke,DC=local
Default-First-Site-Name\ROOKESBS via RPC
DSA object GUID: 11aecea4-d53e-48b8-9c68-f996cca7e72e
Last attempt @ 2014-03-12 18:08:28 was successful.
DC=DomainDnsZones,DC=Rooke,DC=local
Default-First-Site-Name\ROOKESBS via RPC
DSA object GUID: 11aecea4-d53e-48b8-9c68-f996cca7e72e
Last attempt @ 2014-03-12 18:08:28 was successful.
DCDIAG
Directory Server Diagnosis
Performing initial setup:
Trying to find home server...
* Verifying that the local machine SERVER-AD, is a Directory Server.
Home Server = SERVER-AD
* Connecting to directory service on server SERVER-AD.
* Identified AD Forest.
Collecting AD specific global data
* Collecting site info.
Calling ldap_search_init_page(hld,CN=Sites,CN=Configuration,DC=Rooke,DC=local,LDAP_SCOPE_SUBTREE,(objectCategory=ntDSSiteSettings),.......
The previous call succeeded
Iterating through the sites
Looking at base site object: CN=NTDS Site Settings,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=Rooke,DC=local
Getting ISTG and options for the site
* Identifying all servers.
Calling ldap_search_init_page(hld,CN=Sites,CN=Configuration,DC=Rooke,DC=local,LDAP_SCOPE_SUBTREE,(objectClass=ntDSDsa),.......
The previous call succeeded....
The previous call succeeded
Iterating through the list of servers
Getting information for the server CN=NTDS Settings,CN=ROOKESBS,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=Rooke,DC=local
objectGuid obtained
InvocationID obtained
dnsHostname obtained
site info obtained
All the info for the server collected
Getting information for the server CN=NTDS Settings,CN=ROOKETERM,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=Rooke,DC=local
objectGuid obtained
InvocationID obtained
dnsHostname obtained
site info obtained
All the info for the server collected
Getting information for the server CN=NTDS Settings,CN=SERVER-AD,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=Rooke,DC=local
objectGuid obtained
InvocationID obtained
dnsHostname obtained
site info obtained
All the info for the server collected
* Identifying all NC cross-refs.
* Found 3 DC(s). Testing 1 of them.
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-Name\SERVER-AD
Starting test: Connectivity
* Active Directory LDAP Services Check
Determining IP4 connectivity
* Active Directory RPC Services Check
......................... SERVER-AD passed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\SERVER-AD
Starting test: Advertising
Warning: DsGetDcName returned information for \\rookesbs.Rooke.local,
when we were trying to reach SERVER-AD.
SERVER IS NOT RESPONDING or IS NOT CONSIDERED SUITABLE.
......................... SERVER-AD failed test Advertising
Test omitted by user request: CheckSecurityError
Test omitted by user request: CutoffServers
Starting test: FrsEvent
* The File Replication Service Event log test
There are warning or error events within the last 24 hours after the
SYSVOL has been shared. Failing SYSVOL replication problems may cause
Group Policy problems.
A warning event occurred. EventID: 0x800034FD
Time Generated: 03/12/2014 16:42:38
Event String:
File Replication Service is initializing the system volume with data from another domain controller. Computer SERVER-AD 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 initialization 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, the availability of other domain controllers, and the replication
interval between domain controllers.
A warning event occurred. EventID: 0x800034C8
Time Generated: 03/12/2014 16:42:39
Event String:
The File Replication Service has detected an enabled disk write cache on the drive containing the directory c:\windows\ntfrs\jet on the computer SERVER-AD. The File Replication Service might
not recover when power to the drive is interrupted and critical updates are lost.
A warning event occurred. EventID: 0x800034C4
Time Generated: 03/12/2014 16:44:19
Event String:
The File Replication Service is having trouble enabling replication from rookesbs.Rooke.local to SERVER-AD for c:\windows\sysvol\domain using the DNS name rookesbs.Rooke.local. FRS will keep
retrying.
Following are some of the reasons you would see this warning.
[1] FRS can not correctly resolve the DNS name rookesbs.Rooke.local from this computer.
[2] FRS is not running on rookesbs.Rooke.local.
[3] The topology information in the Active Directory Domain Services for this replica has not yet replicated to all the Domain Controllers.
This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established.
A warning event occurred. EventID: 0x800034C4
Time Generated: 03/12/2014 16:52:19
Event String:
The File Replication Service is having trouble enabling replication from ROOKETERM to SERVER-AD for c:\windows\sysvol\domain using the DNS name rooketerm.Rooke.local. FRS will keep retrying.
Following are some of the reasons you would see this warning.
[1] FRS can not correctly resolve the DNS name rooketerm.Rooke.local from this computer.
[2] FRS is not running on rooketerm.Rooke.local.
[3] The topology information in the Active Directory Domain Services for this replica has not yet replicated to all the Domain Controllers.
This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established.
A warning event occurred. EventID: 0x800034C4
Time Generated: 03/12/2014 16:52:20
Event String:
The File Replication Service is having trouble enabling replication from ROOKESBS to SERVER-AD for c:\windows\sysvol\domain using the DNS name rookesbs.Rooke.local. FRS will keep retrying.
Following are some of the reasons you would see this warning.
[1] FRS can not correctly resolve the DNS name rookesbs.Rooke.local from this computer.
[2] FRS is not running on rookesbs.Rooke.local.
[3] The topology information in the Active Directory Domain Services for this replica has not yet replicated to all the Domain Controllers.
This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established.
A warning event occurred. EventID: 0x800034FE
Time Generated: 03/12/2014 17:42:51
Event String:
File Replication Service is scanning the data in the system volume. Computer SERVER-AD 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.
A warning event occurred. EventID: 0x800034C8
Time Generated: 03/12/2014 17:42:51
Event String:
The File Replication Service has detected an enabled disk write cache on the drive containing the directory c:\windows\ntfrs\jet on the computer SERVER-AD. The File Replication Service might
not recover when power to the drive is interrupted and critical updates are lost.
A warning event occurred. EventID: 0x800034C4
Time Generated: 03/12/2014 17:44:32
Event String:
The File Replication Service is having trouble enabling replication from rookesbs.Rooke.local to SERVER-AD for c:\windows\sysvol\domain using the DNS name rookesbs.Rooke.local. FRS will keep
retrying.
Following are some of the reasons you would see this warning.
[1] FRS can not correctly resolve the DNS name rookesbs.Rooke.local from this computer.
[2] FRS is not running on rookesbs.Rooke.local.
[3] The topology information in the Active Directory Domain Services for this replica has not yet replicated to all the Domain Controllers.
This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established.
......................... SERVER-AD passed test FrsEvent
Starting test: DFSREvent
The DFS Replication Event Log.
Skip the test because the server is running FRS.
......................... SERVER-AD passed test DFSREvent
Starting test: SysVolCheck
* The File Replication Service SYSVOL ready test
The registry lookup failed to determine the state of the SYSVOL. The
error returned was 0x0 "The operation completed successfully.".
Check the FRS event log to see if the SYSVOL has successfully been
shared.
......................... SERVER-AD passed test SysVolCheck
Starting test: KccEvent
* The KCC Event log test
Found no KCC errors in "Directory Service" Event log in the last 15 minutes.
......................... SERVER-AD passed test KccEvent
Starting test: KnowsOfRoleHolders
Role Schema Owner = CN=NTDS Settings,CN=SERVER-AD,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=Rooke,DC=local
Role Domain Owner = CN=NTDS Settings,CN=SERVER-AD,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=Rooke,DC=local
Role PDC Owner = CN=NTDS Settings,CN=SERVER-AD,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=Rooke,DC=local
Role Rid Owner = CN=NTDS Settings,CN=SERVER-AD,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=Rooke,DC=local
Role Infrastructure Update Owner = CN=NTDS Settings,CN=SERVER-AD,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=Rooke,DC=local
......................... SERVER-AD passed test KnowsOfRoleHolders
Starting test: MachineAccount
Checking machine account for DC SERVER-AD on DC SERVER-AD.
* SPN found :LDAP/SERVER-AD.Rooke.local/Rooke.local
* SPN found :LDAP/SERVER-AD.Rooke.local
* SPN found :LDAP/SERVER-AD
* SPN found :LDAP/SERVER-AD.Rooke.local/ROOKE
* SPN found :LDAP/66f0b91a-f210-4a53-a1a9-4f585114c181._msdcs.Rooke.local
* SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/66f0b91a-f210-4a53-a1a9-4f585114c181/Rooke.local
* SPN found :HOST/SERVER-AD.Rooke.local/Rooke.local
* SPN found :HOST/SERVER-AD.Rooke.local
* SPN found :HOST/SERVER-AD
* SPN found :HOST/SERVER-AD.Rooke.local/ROOKE
* SPN found :GC/SERVER-AD.Rooke.local/Rooke.local
......................... SERVER-AD passed test MachineAccount
Starting test: NCSecDesc
* Security Permissions check for all NC's on DC SERVER-AD.
The forest is not ready for RODC. Will skip checking ERODC ACEs.
* Security Permissions Check for
DC=DomainDnsZones,DC=Rooke,DC=local
(NDNC,Version 3)
* Security Permissions Check for
DC=ForestDnsZones,DC=Rooke,DC=local
(NDNC,Version 3)
* Security Permissions Check for
CN=Schema,CN=Configuration,DC=Rooke,DC=local
(Schema,Version 3)
* Security Permissions Check for
CN=Configuration,DC=Rooke,DC=local
(Configuration,Version 3)
* Security Permissions Check for
DC=Rooke,DC=local
(Domain,Version 3)
......................... SERVER-AD passed test NCSecDesc
Starting test: NetLogons
* Network Logons Privileges Check
Unable to connect to the NETLOGON share! (\\SERVER-AD\netlogon)
[SERVER-AD] An net use or LsaPolicy operation failed with error 67,
The network name cannot be found..
......................... SERVER-AD failed test NetLogons
Starting test: ObjectsReplicated
SERVER-AD is in domain DC=Rooke,DC=local
Checking for CN=SERVER-AD,OU=Domain Controllers,DC=Rooke,DC=local in domain DC=Rooke,DC=local on 1 servers
Object is up-to-date on all servers.
Checking for CN=NTDS Settings,CN=SERVER-AD,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=Rooke,DC=local in domain CN=Configuration,DC=Rooke,DC=local on 1 servers
Object is up-to-date on all servers.
......................... SERVER-AD passed test ObjectsReplicated
Test omitted by user request: OutboundSecureChannels
Starting test: Replications
* Replications Check
* Replication Latency Check
DC=DomainDnsZones,DC=Rooke,DC=local
Latency information for 2 entries in the vector were ignored.
2 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc. 0 had no latency
information (Win2K DC).
DC=ForestDnsZones,DC=Rooke,DC=local
Latency information for 2 entries in the vector were ignored.
2 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc. 0 had no latency
information (Win2K DC).
CN=Schema,CN=Configuration,DC=Rooke,DC=local
Latency information for 5 entries in the vector were ignored.
5 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc. 0 had no latency
information (Win2K DC).
CN=Configuration,DC=Rooke,DC=local
Latency information for 5 entries in the vector were ignored.
5 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc. 0 had no latency
information (Win2K DC).
DC=Rooke,DC=local
Latency information for 5 entries in the vector were ignored.
5 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc. 0 had no latency
information (Win2K DC).
......................... SERVER-AD passed test Replications
Starting test: RidManager
* Available RID Pool for the Domain is 5607 to 1073741823
* SERVER-AD.Rooke.local is the RID Master
* DsBind with RID Master was successful
* rIDAllocationPool is 5107 to 5606
* rIDPreviousAllocationPool is 5107 to 5606
* rIDNextRID: 5107
......................... SERVER-AD passed test RidManager
Starting test: Services
* Checking Service: EventSystem
* Checking Service: RpcSs
* Checking Service: NTDS
* Checking Service: DnsCache
* Checking Service: NtFrs
* Checking Service: IsmServ
* Checking Service: kdc
* Checking Service: SamSs
* Checking Service: LanmanServer
* Checking Service: LanmanWorkstation
* Checking Service: w32time
* Checking Service: NETLOGON
......................... SERVER-AD passed test Services
Starting test: SystemLog
* The System Event log test
Found no errors in "System" Event log in the last 60 minutes.
......................... SERVER-AD passed test SystemLog
Test omitted by user request: Topology
Test omitted by user request: VerifyEnterpriseReferences
Starting test: VerifyReferences
The system object reference (serverReference)
CN=SERVER-AD,OU=Domain Controllers,DC=Rooke,DC=local and backlink on
CN=SERVER-AD,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=Rooke,DC=local
are correct.
The system object reference (serverReferenceBL)
CN=SERVER-AD,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=Rooke,DC=local
and backlink on
CN=NTDS Settings,CN=SERVER-AD,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=Rooke,DC=local
are correct.
The system object reference (frsComputerReferenceBL)
CN=SERVER-AD,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=Rooke,DC=local
and backlink on CN=SERVER-AD,OU=Domain Controllers,DC=Rooke,DC=local
are correct.
......................... SERVER-AD passed test VerifyReferences
Test omitted by user request: VerifyReplicas
Test omitted by user request: DNS
Test omitted by user request: DNS
Running partition tests on : DomainDnsZones
Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... DomainDnsZones passed test
CrossRefValidation
Running partition tests on : ForestDnsZones
Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... ForestDnsZones passed test
CrossRefValidation
Running partition tests on : Schema
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Running partition tests on : Configuration
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... Configuration passed test CrossRefValidation
Running partition tests on : Rooke
Starting test: CheckSDRefDom
......................... Rooke passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... Rooke passed test CrossRefValidation
Running enterprise tests on : Rooke.local
Test omitted by user request: DNS
Test omitted by user request: DNS
Starting test: LocatorCheck
Warning: DcGetDcName(GC_SERVER_REQUIRED) call failed, error 1355
A Global Catalog Server could not be located - All GC's are down.
PDC Name: \\SERVER-AD.Rooke.local
Locator Flags: 0xe00071fd
Time Server Name: \\rookesbs.Rooke.local
Locator Flags: 0xe00001f8
Preferred Time Server Name: \\rookesbs.Rooke.local
Locator Flags: 0xe00001f8
KDC Name: \\rookesbs.Rooke.local
Locator Flags: 0xe00001f8
......................... Rooke.local failed test LocatorCheck
Starting test: Intersite
Skipping site Default-First-Site-Name, this site is outside the scope
provided by the command line arguments provided.
......................... Rooke.local passed test Intersite -
SYSVOL Replication Failing - 13508
We have two 2008 R2 DCs and our second DC has been getting the 13508 for months. I have checked the logs and have found no instance of 13509.
I have recently set up a third DC (server 2012 R2) and am now getting the message on that machine as well. Except, now it's showing the message for DC1 and DC2.
The File Replication Service is having trouble enabling replication from DC2 to DC3 for c:\windows\sysvol\domain using the DNS name DC2. FRS will keep retrying.
Following are some of the reasons you would see this warning.
[1] FRS can not correctly resolve the DNS name DC2 from this computer.
[2] FRS is not running on DC2.
[3] The topology information in the Active Directory Domain Services for this replica has not yet replicated to all the Domain Controllers.
This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established.
I'm not exactly sure what that means, but I continued to do some diagnostics. I was able to ping the FQDN with no problem. I disabled the firewalls on all boxes and tested with no luck. There is now internal firewall blocking anything and
the proper ports are open and listening.
In addition, I have noticed on the DC that is NOT receiving the 13508 error has had a couple 13562 errors-
Following is the summary of warnings and errors encountered by File Replication Service while polling the Domain Controller DC1 for FRS replica set configuration information.
Could not bind to a Domain Controller. Will try again at next polling cycle.
Other than that, there are no FRS errors on DC1. Here are the results of DCDiag on DC1:
Directory Server Diagnosis
Performing initial setup:
Trying to find home server...
Home Server = DC1
* Identified AD Forest.
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-Name\DC1
Starting test: Connectivity
......................... DC1 passed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\DC1
Starting test: Advertising
......................... DC1 passed test Advertising
Starting test: FrsEvent
......................... DC1 passed test FrsEvent
Starting test: DFSREvent
......................... DC1 passed test DFSREvent
Starting test: SysVolCheck
......................... DC1 passed test SysVolCheck
Starting test: KccEvent
......................... DC1 passed test KccEvent
Starting test: KnowsOfRoleHolders
......................... DC1 passed test KnowsOfRoleHolders
Starting test: MachineAccount
......................... DC1 passed test MachineAccount
Starting test: NCSecDesc
Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have
Replicating Directory Changes In Filtered Set
access rights for the naming context:
DC=ForestDnsZones,DC=domain,DC=local
Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have
Replicating Directory Changes In Filtered Set
access rights for the naming context:
DC=DomainDnsZones,DC=domain,DC=local
......................... DC1 failed test NCSecDesc
Starting test: NetLogons
......................... DC1 passed test NetLogons
Starting test: ObjectsReplicated
......................... DC1 passed test ObjectsReplicated
Starting test: Replications
......................... DC1 passed test Replications
Starting test: RidManager
......................... DC1 passed test RidManager
Starting test: Services
......................... DC1 passed test Services
Starting test: SystemLog
......................... DC1 passed test SystemLog
Starting test: VerifyReferences
......................... DC1 passed test VerifyReferences
Running partition tests on : ForestDnsZones
Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... ForestDnsZones passed test
CrossRefValidation
Running partition tests on : DomainDnsZones
Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... DomainDnsZones passed test
CrossRefValidation
Running partition tests on : Schema
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Running partition tests on : Configuration
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... Configuration passed test CrossRefValidation
Running partition tests on : domain
Starting test: CheckSDRefDom
......................... domain passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... domain passed test CrossRefValidation
Running enterprise tests on : domain.local
Starting test: LocatorCheck
......................... domain.local passed test LocatorCheck
Starting test: Intersite
......................... domain.local passed test Intersite
Here is the result from DC2:
Directory Server Diagnosis
Performing initial setup:
Trying to find home server...
Home Server = DC2
* Identified AD Forest.
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-Name\DC2
Starting test: Connectivity
......................... DC2 passed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\DC2
Starting test: Advertising
......................... DC2 passed test Advertising
Starting test: FrsEvent
There are warning or error events within the last 24 hours after the
SYSVOL has been shared.
Failing SYSVOL replication problems may cause
Group Policy problems.
......................... DC2 passed test FrsEvent
Starting test: DFSREvent
......................... DC2 passed test DFSREvent
Starting test: SysVolCheck
......................... DC2 passed test SysVolCheck
Starting test: KccEvent
......................... DC2 passed test KccEvent
Starting test: KnowsOfRoleHolders
......................... DC2 passed test KnowsOfRoleHolders
Starting test: MachineAccount
......................... DC2 passed test MachineAccount
Starting test: NCSecDesc
Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have
Replicating Directory Changes In Filtered Set
access rights for the naming context:
DC=ForestDnsZones,DC=domain,DC=local
Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have
Replicating Directory Changes In Filtered Set
access rights for the naming context:
DC=DomainDnsZones,DC=domain,DC=local
......................... DC2 failed test NCSecDesc
Starting test: NetLogons
......................... DC2 passed test NetLogons
Starting test: ObjectsReplicated
......................... DC2 passed test ObjectsReplicated
Starting test: Replications
......................... DC2 passed test Replications
Starting test: RidManager
......................... DC2 passed test RidManager
Starting test: Services
......................... DC2 passed test Services
Starting test: SystemLog
A warning event occurred.
EventID: 0x8000001D
Time Generated: 03/25/2015 10:53:38
Event String:
The Key Distribution Center (KDC) cannot find a suitable certificate to use for smart card logons, or the KDC certificate could not be verified. Smart card logon may not function correctly if this problem is not resolved. To correct this problem, either
verify the existing KDC certificate using certutil.exe or enroll for a new KDC certificate.
......................... DC2 passed test SystemLog
Starting test: VerifyReferences
......................... DC2 passed test VerifyReferences
Running partition tests on : ForestDnsZones
Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... ForestDnsZones passed test
CrossRefValidation
Running partition tests on : DomainDnsZones
Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... DomainDnsZones passed test
CrossRefValidation
Running partition tests on : Schema
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Running partition tests on : Configuration
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... Configuration passed test CrossRefValidation
Running partition tests on : domain
Starting test: CheckSDRefDom
......................... domain passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... domain passed test CrossRefValidation
Running enterprise tests on : domain.local
Starting test: LocatorCheck
......................... domain.local passed test LocatorCheck
Starting test: Intersite
......................... domain.local passed test Intersite
And finally, here is the result from DC3:
* Identified AD Forest.
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-Name\DC3
Starting test: Connectivity
......................... DC3 passed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\DC3
Starting test: Advertising
Warning: DsGetDcName returned information for \\DC1.domain.local,
when we were trying to reach DC3.
SERVER IS NOT RESPONDING or IS NOT CONSIDERED SUITABLE.
......................... DC3 failed test Advertising
Starting test: FrsEvent
There are warning or error events within the last 24 hours after the
SYSVOL has been shared.
Failing SYSVOL replication problems may cause
Group Policy problems.
......................... DC3 passed test FrsEvent
Starting test: DFSREvent
......................... DC3 passed test DFSREvent
Starting test: SysVolCheck
......................... DC3 passed test SysVolCheck
Starting test: KccEvent
......................... DC3 passed test KccEvent
Starting test: KnowsOfRoleHolders
......................... DC3 passed test KnowsOfRoleHolders
Starting test: MachineAccount
......................... DC3 passed test MachineAccount
Starting test: NCSecDesc
......................... DC3 passed test NCSecDesc
Starting test: NetLogons
Unable to connect to the NETLOGON share! (\\DC3\netlogon)
[DC3] An net use or LsaPolicy operation failed with error 67,
The network name cannot be found..
......................... DC3 failed test NetLogons
Starting test: ObjectsReplicated
......................... DC3 passed test ObjectsReplicated
Starting test: Replications
......................... DC3 passed test Replications
Starting test: RidManager
......................... DC3 passed test RidManager
Starting test: Services
......................... DC3 passed test Services
Starting test: SystemLog
......................... DC3 passed test SystemLog
Starting test: VerifyReferences
......................... DC3 passed test VerifyReferences
Running partition tests on : DomainDnsZones
Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... DomainDnsZones passed test
CrossRefValidation
Running partition tests on : ForestDnsZones
Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... ForestDnsZones passed test
CrossRefValidation
Running partition tests on : Schema
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Running partition tests on : Configuration
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... Configuration passed test CrossRefValidation
Running partition tests on : domain
Starting test: CheckSDRefDom
......................... domain passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... domain passed test CrossRefValidation
Running enterprise tests on : domain.local
Starting test: LocatorCheck
......................... domain.local passed test LocatorCheck
Starting test: Intersite
......................... domain.local passed test Intersite
Any idea what would be causing this and what my next steps would be? Let me know if I can get you any more info.
Thanks for the help in advance!Hello,
Is this is the FRSDiag_Log file? If so, I don't see that type of message anywhere. On the FRSDiag when I select all the DCs and select go, I get the following:
DC1:
FRSDiag v1.7 on 4/8/2015 8:10:49 AM
.\DC1 on 2015-04-08 at 8.10.49 AM
Checking for errors/warnings in FRS Event Log .... passed
Checking for errors in Directory Service Event Log .... passed
Checking for minimum FRS version requirement ... passed
Checking for errors/warnings in ntfrsutl ds ... passed
Checking for Replica Set configuration triggers... passed
Checking for suspicious file Backlog size... passed
Checking Overall Disk Space and SYSVOL structure (note: integrity is not checked)... passed
Checking for suspicious inlog entries ... passed
Checking for suspicious outlog entries ... passed
Checking for appropriate staging area size ... passed
Checking for errors in debug logs ... passed
Checking NtFrs Service (and dependent services) state...passed
Checking NtFrs related Registry Keys for possible problems...passed
Checking Repadmin Showreps for errors...passed
Final Result = passed
DC2:
FRSDiag v1.7 on 4/8/2015 8:10:49 AM
.\DC2 on 2015-04-08 at 8.10.49 AM
Checking for errors/warnings in FRS Event Log ....
NtFrs
4/8/2015 2:56:42 AM
Warning 13508
The File Replication Service is having trouble enabling replication
from DC1 to DC2 for c:\windows\sysvol\domain using the DNS name DC1.domain.local. FRS will keep retrying.
Following are some of the reasons you would see this warning.
[1] FRS can not correctly resolve the DNS name DC1.domain.local from this computer.
[2] FRS is not running on DC1.domain.local.
[3] The topology information in the Active Directory Domain Services for
this replica has not yet replicated to all the Domain Controllers.
This event log message will appear once per connection, After the problem
is fixed you will see another event log message indicating that the connection
has been established.
NtFrs
4/8/2015 2:33:02 AM
Warning 13508
The File Replication Service is having trouble enabling replication
from DC3 to DC2 for c:\windows\sysvol\domain using the DNS name DC3.domain.local. FRS will keep retrying.
Following are some of the reasons you would see this warning.
[1] FRS can not correctly resolve the DNS name DC3.domain.local from this computer.
[2] FRS is not running on DC3.domain.local.
[3] The topology information in the Active Directory Domain Services for
this replica has not yet replicated to all the Domain Controllers.
This event log message will appear once per connection, After the problem
is fixed you will see another event log message indicating that the connection
has been established.
NtFrs
4/7/2015 1:27:11 AM
Warning 13508
The File Replication Service is having trouble enabling replication
from DC3 to DC2 for c:\windows\sysvol\domain using the DNS name DC3.domain.local. FRS will keep retrying.
Following are some of the reasons you would see this warning.
[1] FRS can not correctly resolve the DNS name DC3.domain.local from this computer.
[2] FRS is not running on DC3.domain.local.
[3] The topology information in the Active Directory Domain Services for
this replica has not yet replicated to all the Domain Controllers.
This event log message will appear once per connection, After the problem
is fixed you will see another event log message indicating that the connection
has been established.
NtFrs
4/7/2015 1:25:07 AM
Warning 13565
File Replication Service is initializing the system volume with data from another
domain controller. Computer DC2 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 initialization 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,
the availability of other domain controllers, and the replication
interval between domain controllers.
NtFrs
4/6/2015 3:25:32 PM
Warning 13520
The File Replication Service moved the preexisting files in c:\windows\sysvol\domain to c:\windows\sysvol\domain\NtFrs_PreExisting___See_EventLog.
The File Replication Service may delete the files in c:\windows\sysvol\domain\NtFrs_PreExisting___See_EventLog at any time.
Files can be saved from deletion by copying them out of c:\windows\sysvol\domain\NtFrs_PreExisting___See_EventLog. Copying
the files into c:\windows\sysvol\domain may lead to name conflicts if the files already exist
on some other replicating partner.
In some cases, the File Replication Service may copy a file
from c:\windows\sysvol\domain\NtFrs_PreExisting___See_EventLog into c:\windows\sysvol\domain instead of replicating the file from some other
replicating partner.
Space can be recovered at any time by deleting the files in c:\windows\sysvol\domain\NtFrs_PreExisting___See_EventLog.
NtFrs
4/6/2015 3:25:32 PM
Warning 13565
File Replication Service is initializing the system volume with data from another
domain controller. Computer DC2 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 initialization 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,
the availability of other domain controllers, and the replication
interval between domain controllers.
NtFrs
4/3/2015 10:17:06 AM
Warning 13567
File Replication Service has detected and suppressed an average of 15 or more file updates
every hour for the last 3 hours because the updates did not change the contents of
the file. The tracking records in FRS debug logs will have the filename and event time
for the suppressed updates. The tracking records have the date and time followed by :T:
as their prefix. Updates that do not change the content of the file are suppressed to prevent
unnecessary replication traffic. Following are common examples of updates that do not
change the contents of the file.
[1] Overwriting a file with a copy of the same file.
[2] Setting the same ACLs on a file multiple times.
[3] Restoring an identical copy of the file over an existing one.
Suppression of updates can be disabled by running regedit.
Click on Start, Run and type regedit.
Expand HKEY_LOCAL_MACHINE, SYSTEM, CurrentControlSet, Services, NtFrs, Parameters,
and create or update the value "Suppress Identical Updates To Files" to 0 (Default is 1) to force
identical updates to replicate.
NtFrs
4/2/2015 6:28:57 PM
Warning 13567
File Replication Service has detected and suppressed an average of 15 or more file updates
every hour for the last 3 hours because the updates did not change the contents of
the file. The tracking records in FRS debug logs will have the filename and event time
for the suppressed updates. The tracking records have the date and time followed by :T:
as their prefix. Updates that do not change the content of the file are suppressed to prevent
unnecessary replication traffic. Following are common examples of updates that do not
change the contents of the file.
[1] Overwriting a file with a copy of the same file.
[2] Setting the same ACLs on a file multiple times.
[3] Restoring an identical copy of the file over an existing one.
Suppression of updates can be disabled by running regedit.
Click on Start, Run and type regedit.
Expand HKEY_LOCAL_MACHINE, SYSTEM, CurrentControlSet, Services, NtFrs, Parameters,
and create or update the value "Suppress Identical Updates To Files" to 0 (Default is 1) to force
identical updates to replicate.
NtFrs
4/2/2015 4:10:11 PM
Warning 13565
File Replication Service is initializing the system volume with data from another
domain controller. Computer DC2 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 initialization 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,
the availability of other domain controllers, and the replication
interval between domain controllers.
NtFrs
4/2/2015 3:56:38 PM
Warning 13520
The File Replication Service moved the preexisting files in c:\windows\sysvol\domain to c:\windows\sysvol\domain\NtFrs_PreExisting___See_EventLog.
The File Replication Service may delete the files in c:\windows\sysvol\domain\NtFrs_PreExisting___See_EventLog at any time.
Files can be saved from deletion by copying them out of c:\windows\sysvol\domain\NtFrs_PreExisting___See_EventLog. Copying
the files into c:\windows\sysvol\domain may lead to name conflicts if the files already exist
on some other replicating partner.
In some cases, the File Replication Service may copy a file
from c:\windows\sysvol\domain\NtFrs_PreExisting___See_EventLog into c:\windows\sysvol\domain instead of replicating the file from some other
replicating partner.
Space can be recovered at any time by deleting the files in c:\windows\sysvol\domain\NtFrs_PreExisting___See_EventLog.
NtFrs
4/2/2015 3:56:37 PM
Warning 13565
File Replication Service is initializing the system volume with data from another
domain controller. Computer DC2 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 initialization 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,
the availability of other domain controllers, and the replication
interval between domain controllers.
WARNING: Found Event ID 13508 errors without trailing 13509 ... see above for (up to) the 3 latest entries!
......... failed 9
Checking for errors in Directory Service Event Log .... passed
Checking for minimum FRS version requirement ... passed
Checking for errors/warnings in ntfrsutl ds ... passed
Checking for Replica Set configuration triggers... passed
Checking for suspicious file Backlog size... passed
Checking Overall Disk Space and SYSVOL structure (note: integrity is not checked)... passed
Checking for suspicious inlog entries ... passed
Checking for suspicious outlog entries ... passed
Checking for appropriate staging area size ... passed
Checking for errors in debug logs ...
ERROR on NtFrs_0005.log : "ERROR_ACCESS_DENIED" : <SndCsMain:
4416: 904: S0: 08:00:40> :SR: Cmd 003f5d40, CxtG 6af17002, WS ERROR_ACCESS_DENIED, To
DC1.domain.local Len: (368) [SndFail - Send Penalty]
ERROR on NtFrs_0005.log : "ERROR_ACCESS_DENIED" : <SndCsMain:
4416: 877: S0: 08:07:51> :SR: Cmd 003f5d40, CxtG 6af17002, WS ERROR_ACCESS_DENIED, To
DC1.domain.local Len: (368) [SndFail - rpc call]
ERROR on NtFrs_0005.log : "ERROR_ACCESS_DENIED" : <SndCsMain:
4416: 904: S0: 08:07:51> :SR: Cmd 003f5d40, CxtG 6af17002, WS ERROR_ACCESS_DENIED, To
DC1.domain.local Len: (368) [SndFail - Send Penalty]
ERROR on NtFrs_0004.log : "EPT_S_NOT_REGISTERED(This may indicate that DNS returns the IP address of the wrong computer. Check DNS records being returned, Check if FRS is currently running on the target server. Check if Ntfrs is registered with
the End-Point-Mapper on target server!)" : <SndCsMain:
300: 883: S0: 15:25:44> ++ ERROR - EXCEPTION (000006d9) :
WStatus: EPT_S_NOT_REGISTERED
ERROR on NtFrs_0004.log : "EPT_S_NOT_REGISTERED(This may indicate that DNS returns the IP address of the wrong computer. Check DNS records being returned, Check if FRS is currently running on the target server. Check if Ntfrs is registered with
the End-Point-Mapper on target server!)" : <SndCsMain:
300: 884: S0: 15:25:44> :SR: Cmd 002a3060, CxtG e2bb412a, WS EPT_S_NOT_REGISTERED, To
DC3.domain.local Len: (366) [SndFail - rpc exception]
ERROR on NtFrs_0004.log : "EPT_S_NOT_REGISTERED(This may indicate that DNS returns the IP address of the wrong computer. Check DNS records being returned, Check if FRS is currently running on the target server. Check if Ntfrs is registered with
the End-Point-Mapper on target server!)" : <SndCsMain:
300: 904: S0: 15:25:44> :SR: Cmd 002a3060, CxtG e2bb412a, WS EPT_S_NOT_REGISTERED, To
DC3.domain.local Len: (366) [SndFail - Send Penalty]
ERROR on NtFrs_0003.log : "RPC_S_CALL_FAILED_DNE(Indicates RPC Session was established to target, but there was a failure to send RPC call package. Check for Networking problems!)" : <SndCsMain:
1312: 883: S0: 10:19:22> ++ ERROR - EXCEPTION (000006bf) :
WStatus: RPC_S_CALL_FAILED_DNE
ERROR on NtFrs_0003.log : "RPC_S_CALL_FAILED_DNE(Indicates RPC Session was established to target, but there was a failure to send RPC call package. Check for Networking problems!)" : <SndCsMain:
1312: 884: S0: 10:19:22> :SR: Cmd 06bf9240, CxtG e2bb412a, WS RPC_S_CALL_FAILED_DNE, To
DC3.domain.local Len: (366) [SndFail - rpc exception]
ERROR on NtFrs_0003.log : "RPC_S_CALL_FAILED_DNE(Indicates RPC Session was established to target, but there was a failure to send RPC call package. Check for Networking problems!)" : <SndCsMain:
1312: 904: S0: 10:19:22> :SR: Cmd 06bf9240, CxtG e2bb412a, WS RPC_S_CALL_FAILED_DNE, To
DC3.domain.local Len: (366) [SndFail - Send Penalty]
Found 2230 ERROR_ACCESS_DENIED error(s)! Latest ones (up to 3) listed above
Found 6 EPT_S_NOT_REGISTERED error(s)! Latest ones (up to 3) listed above
Found 3 RPC_S_CALL_FAILED_DNE error(s)! Latest ones (up to 3) listed above
......... failed with 2239 error entries
Checking NtFrs Service (and dependent services) state...
ERROR : Cannot access SYSVOL share on DC2
ERROR : Cannot access NETLOGON share on DC2
......... failed 2
Checking NtFrs related Registry Keys for possible problems...
SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\SysvolReady = 0 :: ERROR: SysvolReady is not set to 1 :: SYSVOL is likely not Sharing! This key should NOT be changed manually but this should be addressed! See article KB.327781 (How to Troubleshoot
Missing SYSVOL and NETLOGON Shares on Windows Server) for further information!
failed with 1 error(s) and 0 warning(s)
Checking Repadmin Showreps for errors...passed
Final Result = failed with 2251 error(s)
DC3:
FRSDiag v1.7 on 4/8/2015 8:10:49 AM
.\DC3 on 2015-04-08 at 8.10.49 AM
Checking for errors/warnings in FRS Event Log ....
NtFrs
4/7/2015 4:52:26 PM
Warning 13508
The File Replication Service is having trouble enabling replication
from DC1 to DC3 for c:\windows\sysvol\domain using the DNS name DC1.domain.local. FRS will keep retrying.
Following are some of the reasons you would see this warning.
[1] FRS can not correctly resolve the DNS name DC1.domain.local from this computer.
[2] FRS is not running on DC1.domain.local.
[3] The topology information in the Active Directory Domain Services for
this replica has not yet replicated to all the Domain Controllers.
This event log message will appear once per connection, After the problem
is fixed you will see another event log message indicating that the connection
has been established.
NtFrs
4/7/2015 4:33:35 PM
Warning 13508
The File Replication Service is having trouble enabling replication
from DC2 to DC3 for c:\windows\sysvol\domain using the DNS name DC2.domain.local. FRS will keep retrying.
Following are some of the reasons you would see this warning.
[1] FRS can not correctly resolve the DNS name DC2.domain.local from this computer.
[2] FRS is not running on DC2.domain.local.
[3] The topology information in the Active Directory Domain Services for
this replica has not yet replicated to all the Domain Controllers.
This event log message will appear once per connection, After the problem
is fixed you will see another event log message indicating that the connection
has been established.
NtFrs
4/6/2015 3:27:45 PM
Warning 13508
The File Replication Service is having trouble enabling replication
from DC1 to DC3 for c:\windows\sysvol\domain using the DNS name DC1.domain.local. FRS will keep retrying.
Following are some of the reasons you would see this warning.
[1] FRS can not correctly resolve the DNS name DC1.domain.local from this computer.
[2] FRS is not running on DC1.domain.local.
[3] The topology information in the Active Directory Domain Services for
this replica has not yet replicated to all the Domain Controllers.
This event log message will appear once per connection, After the problem
is fixed you will see another event log message indicating that the connection
has been established.
NtFrs
4/6/2015 3:26:03 PM
Warning 13520
The File Replication Service moved the preexisting files in c:\windows\sysvol\domain to c:\windows\sysvol\domain\NtFrs_PreExisting___See_EventLog.
The File Replication Service may delete the files in c:\windows\sysvol\domain\NtFrs_PreExisting___See_EventLog at any time.
Files can be saved from deletion by copying them out of c:\windows\sysvol\domain\NtFrs_PreExisting___See_EventLog. Copying
the files into c:\windows\sysvol\domain may lead to name conflicts if the files already exist
on some other replicating partner.
In some cases, the File Replication Service may copy a file
from c:\windows\sysvol\domain\NtFrs_PreExisting___See_EventLog into c:\windows\sysvol\domain instead of replicating the file from some other
replicating partner.
Space can be recovered at any time by deleting the files in c:\windows\sysvol\domain\NtFrs_PreExisting___See_EventLog.
NtFrs
4/6/2015 3:26:03 PM
Warning 13565
File Replication Service is initializing the system volume with data from another
domain controller. Computer DC3 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 initialization 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,
the availability of other domain controllers, and the replication
interval between domain controllers.
NtFrs
4/6/2015 1:42:46 PM
Warning 13518
The File Replication Service did not grant the user "itadmin" access to the
API "Get Internal Information".
Permissions for "Get Internal Information" can be changed by running regedit.
Click on Start, Run, and type regedit.
Expand HKEY_LOCAL_MACHINE, SYSTEM, CurrentControlSet, Services, NtFrs, Parameters,
Access Checks, and highlight "Get Internal Information".
Click on the toolbar option Security and then Permissions...
Access checks can be disabled for "Get Internal Information". Double click on "Access checks are [Enabled or Disabled]" and
change the string to Disabled.
NtFrs
4/3/2015 10:24:13 AM
Warning 13565
File Replication Service is initializing the system volume with data from another
domain controller. Computer DC3 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 initialization 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,
the availability of other domain controllers, and the replication
interval between domain controllers.
NtFrs
4/3/2015 10:20:13 AM
Warning 13520
The File Replication Service moved the preexisting files in c:\windows\sysvol\domain to c:\windows\sysvol\domain\NtFrs_PreExisting___See_EventLog.
The File Replication Service may delete the files in c:\windows\sysvol\domain\NtFrs_PreExisting___See_EventLog at any time.
Files can be saved from deletion by copying them out of c:\windows\sysvol\domain\NtFrs_PreExisting___See_EventLog. Copying
the files into c:\windows\sysvol\domain may lead to name conflicts if the files already exist
on some other replicating partner.
In some cases, the File Replication Service may copy a file
from c:\windows\sysvol\domain\NtFrs_PreExisting___See_EventLog into c:\windows\sysvol\domain instead of replicating the file from some other
replicating partner.
Space can be recovered at any time by deleting the files in c:\windows\sysvol\domain\NtFrs_PreExisting___See_EventLog.
NtFrs
4/3/2015 10:20:13 AM
Warning 13565
File Replication Service is initializing the system volume with data from another
domain controller. Computer DC3 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 initialization 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,
the availability of other domain controllers, and the replication
interval between domain controllers.
NtFrs
4/2/2015 5:30:36 PM
Warning 13567
File Replication Service has detected and suppressed an average of 15 or more file updates
every hour for the last 3 hours because the updates did not change the contents of
the file. The tracking records in FRS debug logs will have the filename and event time
for the suppressed updates. The tracking records have the date and time followed by :T:
as their prefix. Updates that do not change the content of the file are suppressed to prevent
unnecessary replication traffic. Following are common examples of updates that do not
change the contents of the file.
[1] Overwriting a file with a copy of the same file.
[2] Setting the same ACLs on a file multiple times.
[3] Restoring an identical copy of the file over an existing one.
Suppression of updates can be disabled by running regedit.
Click on Start, Run and type regedit.
Expand HKEY_LOCAL_MACHINE, SYSTEM, CurrentControlSet, Services, NtFrs, Parameters,
and create or update the value "Suppress Identical Updates To Files" to 0 (Default is 1) to force
identical updates to replicate.
WARNING: Found Event ID 13508 errors without trailing 13509 ... see above for (up to) the 3 latest entries!
......... failed 8
Checking for errors in Directory Service Event Log .... passed
Checking for minimum FRS version requirement ... passed
Checking for errors/warnings in ntfrsutl ds ... passed
Checking for Replica Set configuration triggers... passed
Checking for suspicious file Backlog size... passed
Checking Overall Disk Space and SYSVOL structure (note: integrity is not checked)... passed
Checking for suspicious inlog entries ... passed
Checking for suspicious outlog entries ... passed
Checking for appropriate staging area size ... passed
Checking for errors in debug logs ...
ERROR on NtFrs_0005.log : "ERROR_ACCESS_DENIED" : <SndCsMain:
7060: 904: S0: 07:54:33> :SR: Cmd 63f84670, CxtG aac0c4ed, WS ERROR_ACCESS_DENIED, To
DC1.domain.local Len: (366) [SndFail - Send Penalty]
ERROR on NtFrs_0005.log : "ERROR_ACCESS_DENIED" : <SndCsMain:
288: 877: S0: 08:00:12> :SR: Cmd 63f947f0, CxtG aac0c4ed, WS ERROR_ACCESS_DENIED, To
DC1.domain.local Len: (366) [SndFail - rpc call]
ERROR on NtFrs_0005.log : "ERROR_ACCESS_DENIED" : <SndCsMain:
288: 904: S0: 08:00:13> :SR: Cmd 63f947f0, CxtG aac0c4ed, WS ERROR_ACCESS_DENIED, To
DC1.domain.local Len: (366) [SndFail - Send Penalty]
Found 1786 ERROR_ACCESS_DENIED error(s)! Latest ones (up to 3) listed above
......... failed with 1786 error entries
Checking NtFrs Service (and dependent services) state...
ERROR : Cannot access SYSVOL share on DC3
ERROR : Cannot access NETLOGON share on DC3
......... failed 2
Checking NtFrs related Registry Keys for possible problems...
SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\SysvolReady = 0 :: ERROR: SysvolReady is not set to 1 :: SYSVOL is likely not Sharing! This key should NOT be changed manually but this should be addressed! See article KB.327781 (How to Troubleshoot
Missing SYSVOL and NETLOGON Shares on Windows Server) for further information!
failed with 1 error(s) and 0 warning(s)
Checking Repadmin Showreps for errors...passed
Final Result = failed with 1797 error(s)
Keep in mind that this is after I tried an authoritative restore. -
Microsoft excel error while exporting a FRS report from Planning to excel
I have multiple screen shots of the issue.
are getting issues when within citrix trying to run an FRS report from workspace into excel.
first they get a windows login window looking for credentials of a User name and a Password.
the first error:
"Could not open 'http:SERVERNAME:19000/hr/hrget/modules/com/hyperion/reporting/web/office/HROfficeReport.jsp/FOLDERNAMEandFILENAME.xls?format=excel.20028viewAs=excel&instanceId=11165278&previewDone=true'.
second error:
Microsoft Excel cannot access the file 'http:SERVERNAME:19000/hr/hrget/modules/com/hyperion/reporting/web/office/HROfficeReport.jsp/FOLDERNAMEandFILENAME.xls?format=excel.20028viewAs=excel&instanceId=11165278&previewDone=true'. There are several possible reasons:
The file name or path does not exist.
The file is being used by another person
The workbook you are trying to save has the same name as a currently open workbook.
Third error:
The file you are trying to open, 'FILENAME.xls', is in a different format than specified by the file extension. Verify that the file is not corrupted and is from a trusted source before opening the file do you want to open the file now?
yes , no, or help
I am trying to figure out if its a CITRIX issue? An EPM issue? or what
We have Office 2010 32 bit with smart view and excel add-in.
Does anybody know why this may occur? I have screen shots I just don't know how to post them.When you export a FR report to excel, yes, you will get a prompt for credentials, but as said in 11.1.2 HFR guide, you have to ignore that by clicking "Cancel" and then you will get a second warning pop-up saying "The file you are trying to open, 'FILENAME.xls', is in a different format ........"... Click on "Yes"... you should be able to see the report in excel....
Both these are known issues in HFR export to excel and you can find them in oracle features guide. And they are not related to Citrix.
As in Oracle HFR user guide "When exporting a Financial Reporting document to a Microsoft Office format (Excel, Word or PowerPoint), when using Microsoft Office 2007, you may receive the following warning: "The file your are trying to open <filename>, is in a different format than specified by the file extension. Verify that the file is not corrupted and is from a trusted source before opening the file. Do you want to open the file now?". This warning notifies users that, although the file has an Office extension ( ".xls", ".doc" or ".ppt"), the content of the file is different from the expected (native) Office format. Although Financial Reporting reports are generated in an MHTML format during export, this is not a security concern. Microsoft Office is just warning a user of a file format that is different than expected. Upon selecting “Yes” in the warning, the file will successfully open in Microsoft Office."
Thanks,
Siva -
Error in Configuring the File Repository Server (FRS)
Hi All.
We are using sap bo 3.1 sp7
Huge space is occupied by File store folder .
So we are planning to move to share drive entire folder
as per few documents in Scn.sap .I followed the steps and made changes in cmc---core services--input and output file repository for successfully..
Note : I Restart each of the modified servers and Enable the servers and i restarted SIA
but still iam facing
Consider it as a high priory issue
Thanks,
RaghunathHi Raghu Go through below link it maybe helpful. http://wiki.scn.sap.com/wiki/display/BOBJ/File+Repository+Server http://wiki.scn.sap.com/wiki/pages/viewpage.action?pageId=322437724 http://blogs.hexaware.com/business-objects-boogle/business-objects-file-repository-servers/
-
Exchange 2003 Permissions Error when attempting to forward emails
Server 2003 R2 (fully patched as of 11/2013) running Exchange 2003 SP2 (Built 7638.x2) on ESXi 4.1; WinXP clients and Server 2003 Terminal Servers running Outlook 2003; Domain and Forest are running at 2008 Functional Levels.
Occasionally, some users are receiving this error message: "You do not have sufficient permission to perform this operation on this object. See the folder contact or your system administrator" intermittently when attempting
to 1) forward email both to and from senders/recipients inside and outside the domain, 2) When attempting to modify the subject of a previously received email (I didn't know you could do that), 3) When attempting to open received attachments.
There is no discernible pattern to the users or the original senders of the emails.
Most of the results I've found when searching relate to NTFS permissions or a ReadOnly propery on items in the users's profile folder, or sending on behalf of another user - these either do not apply or have been verified as not the cause.
During the initial rash of problems when there was a problem with an attachment and we absolutely needed it, I was able to connect to OWA using a special administrative account with access to the mailbox, open the attachment and log out. Once I had
done so with this account, the end user was able to open the attachment on their own without a warning.
Changes made to the environment prior to this issue that may be related (nobody remembers when exactly this started, so I can't state that it definitively happened after this change):
All servers were virtualized on ESXi 4.1 in late 2011; subsequently converted and migrated to Hyper-V Server 2012 in early 2013 (with the exception of the Exchange and SQL servers).
All 2003/R2 domain controllers demoted and removed; DFL/FFL raised to 2008; SYSVOL replication was migrated from FRS to DFS-R.
Troubleshooting steps:
Exchange server and affected client computers have been restarted several times; the various exchange services have been restarted; permissions on the mailboxes and AD objects have been verified; event logs are generally clean with the exception of ActiveSync
errors for a single user not currently affected by forwarding emails, there are no other errors reported.
Per recommendations on another forum, I had enabled several diagnostic logs in the diagnostic logging tab of the server. Unfortunately not much was found in the Application log even after filtering out the basics. There were occasional errors
referencing User A failed to modify an item in User B's mailbox because access was denied; however, I was unable to correlate these errors to any reported incidence of the above message.
I created a new mailbox database on the same server and migrated all the mailboxes to the new database, there was no change; users immediately began seeing these errors.
Over a holiday weekend, I then spun up a new Win 2003 R2 server, with a fresh installation of Server 2003 R2 (also fully patched through 11/2013) running the same version of Exchange 2003 SP2 this time running as a virtual guest on Hyper-V Server 2012.
I migrated all mailboxes from the original mail server to the new mail server and it appeared that the problem was remedied; however, it has slowly started up again and is starting to become more frequent.
I'm really at my wits end with this problem and would like to get it resolved before we purchase and install our new Exchange Server later this year.Updates
Users have reported that they can forward the email from OWA; even after doing so, they are unable to forward from Outlook. So either my previous notes on the issue were wrong, or this is just more of the "intermittent" nature of the problem.
I will have to investigate what logging options are available to me at the Outlook client level - any thoughts on that subject are also welcome.
Users have now reported that a previous (rarely used) workaround (the administrative account opening the email in OWA) no longer enables them to view attachments or forward emails in Outlook.
I'm still adjusting the various diagnostic logging settings to see if I can spot an event which corresponds to a reported occurrence. The most unusual warning reported is the following:
Source:MSExchangeIS Mailbox Store
Category: Access Control
Event ID: 1029
[email protected] failed an operation because the user did not have the following access rights:
'Delete' 'Read Property' 'Write Property' 'Create Message' 'View Item' 'Create Subfolder' 'Write Security Descriptor' 'Write Owner' 'Read Security Descriptor' 'Contact'
The distinguished name of the owning mailbox is /O=DOMAIN/OU=FIRST ADMINISTRATIVE GROUP/CN=RECIPIENTS/CN=USER_B. The folder ID is in the data section of this event.
However odd these occasional warnings are, they do not appears to correlate to the reported permissions issue. Everytime I've seen one of these events, I've inquired with "user_A" to see if they've recently seen the popup and in each case they have
not. -
Error trying to extract data via HFM objects
I've written a program to extract selected data from HFM (version 11.1.1.3.500) using the API objects. The program (shown at the bottom of this post) is failing on the 2nd of the following 2 lines:
oOption = oOptions.Item(HSV_DATAEXTRACT_OPT_SCENARIO_SUBSET)
oOption.CurrentValue = lBudgetScenario
where oOption is a data load/extract object previously initialized and lBudgetScenario is the long internal ID for our budget scenario.
The error is usually "COM Exception was unhandled" with a result code of "0x800456c7", but, mysteriously, even with no code changes, it sometimes throws the error "FileNotFoundException was not handled", where it says that it could not load "interop.HSXServerlib or one of its dependencies". The second error occurs even though HSXServer was previously initialized in the program and used in conjunction with the login.
I've carefully traced through the VB.NET 2010 code and find that all relevant objects are instantiated and variables correctly assigned. It also occurred to me that the data load DLLs might have been updated when the 11.1.1.3.50 and 500 patches were applied. For that reason, I removed the references to those DLLs, deleted the interop files in the debug and release folders and copied the server versions of those DLLs to my PC. I then restored the DLL references in Visual Studio which recreated the interops. However, the error still occurs.
The ID I'm using (changed to generic names in the code below) has appropriate security and, for example, can be used to manually extract data for the same POV via the HFM client.
I've removed irrelevant lines from the code and substituted a phony ID, password, server name and application name. The line with the error is preceded by the comment "THE LINE BELOW IS THE ONE THAT FAILS".
Imports HSVCDATALOADLib.HSV_DATAEXTRACT_OPTION
Module Module1
Public lActualScenario, lBudgetScenario As Long
Public oClient As HSXCLIENTLib.HsxClient
Public oDataLoad As HSVCDATALOADLib.HsvcDataLoad
Public oOptions As HSVCDATALOADLib.IHsvLoadExtractOptions
Public oOption As HSVCDATALOADLib.IHsvLoadExtractOption
Public oSession As HSVSESSIONLib.HsvSession
Public oServer As HSXSERVERLib.HsxServer
Sub Main()
'Create a client object instance, giving access to
'the methods to logon and create an HFM session
oClient = New HSXCLIENTLib.HsxClient
'Create a server object instance, giving access to
'all server-based methods and properties
oServer = oClient.GetServerOnCluster("SERVERNAME")
'Establish login credentials
oClient.SetLogonInfoSSO("", "MYID", "", "MYPASSWORD")
'Open the application, which will initialize the server
'and session instances as well.
oClient.OpenApplication("SERVERNAME", "Financial Management", "APPLICATION", oServer, oSession)
'Instantiate a data load object instance, which will be used to extract data from
'FRS.
oDataLoad = New HSVCDATALOADLib.HsvcDataLoad
oDataLoad.SetSession(oSession)
'Initialize the data load options interface.
oOptions = oDataLoad.ExtractOptions
'Find the internal ID numbers for various scenarios and years.
'These are required for HFM API function calls.
lActualScenario = GetMemberID(DIMENSIONSCENARIO, "Actual")
lBudgetScenario = GetMemberID(DIMENSIONSCENARIO, "Budget")
'Construct file names for open data.
strFileName = "c:\Temp\FEWND_BudgetData.dat"
strLogFileName = "c:\Temp\FEWND_BudgetData.log"
'Extract data for the current open cycle.
ExtractData("Budget", BudgetYear, "Dec", strFileName, strLogFileName)
End Sub
Sub ExtractData(ByVal strScenario As String, ByVal strYear As String, ByVal strPeriod As String, _
ByVal strFileName As String, ByVal strLogFileName As String)
'Populate the Scenario element.
oOption = oOptions.Item(HSV_DATAEXTRACT_OPT_SCENARIO_SUBSET)
If strScenario = "Actual" Then
oOption.CurrentValue = lActualScenario
Else
'THE LINE BELOW IS THE ONE THAT FAILS
oOption.CurrentValue = lBudgetScenario
End If
End Sub
Function GetMemberID(ByVal lDimID As Long, ByVal strMemLabel As String) As Long
Dim oMetaData As HSVMETADATALib.HsvMetadata
oMetaData = oSession.Metadata
oEntityTreeInfo = oMetaData.Dimension(lDimID)
GetMemberID = oEntityTreeInfo.GetItemID(strMemLabel)
End Function
End ModuleI stumbled upon the solution to my problem. The documentation for extracting data via objects defines member ID variables as Longs. In fact, I've always defined such variables as longs in previous object programs and had no problems. It appears that the datal load/extract "option" property of "Currentvalue" is defined as integer. When I changed all of my member ID items (such as the "lBudgetScenario" variable that was the right-side of the failing assignment statement) to be integers, the program worked.
-
BI Launch Pad - Error opening Web Intelligence Report (Error: INF)
Hi:
We're working with 4.1 Support Pack 3 Patch 1
Version: 14.1.3.1300
We migrated a Webi report from development environment to testing and it was working fine.
After making some minor changes on the Web Intelligence report, we migrated again, but now when we open the Web Intelligence report we get the following error:
Faltal Exception occured. The cause was: com.businessobjects.corba.generic.container.proxy.internal.DependencyFailoverCallbackImpl$FailoverFatalException:
Prepare failover failed (Error: INF)
Any ideas?
Thanks in advance!
Kind regards,
FlorenciaHi Florencia,
It seems like report is corrupted some how.
To check report is existing in filestore or not , go to report in Launchpad->Properties->check File name , there should be frs path assigned to it.If not it is corrupted.
Ex : File Name:frs://Input/a_067/064/004/278595/auytslwhrgrdneqcvzbefs0-guid[atli.nsurgzit4q8pfgonmi].wid
If it corrupted , check in myfavourites : ~webintelligence folder , there you can find last auto saved instance.If not we may need to create new report. -
Namespace Errors System Error 1355 - Specified domain does not exist or could not be contacted
Ok, lets start with my environment:
dc1 - windows server 2003 r2
dc2 - windows server 2012 r2
fs1- windows server 2003 r2
fs2 - windows server 2012 r2
Namespace - \\<fqdn>\data (the fqdn would be like contoso.microsoft.com)
I am in the process of migrating everything from server1 to server2 (dc and fs listed above). I am done with mostly everything except DFS. I have migrated the data, setup permissions, shares, etc. and replicated the data between fs1 and fs2.
I have verified that all data is currently replicated and up to date, so no backlogs. I am trying to add dc2 and fs2 as namespace servers. This is so that I can point all of the referrals to FS2 that way when I remove FS1 no one gets an error
about not being able to find the files. The problem is that from all 4 servers, I receive an error message when loading the namespace via DFS Management tool. I then thought because of the drastic differences between the versions, the next best
thing would be to export the namespace and then import it into the new server, but even attempting the export command (dfsutil) gives me the same error. My suspect is that the original namespace server was removed sometime ago without the previous IT
person properly migrating everything (but I am at a loss cuz here I am). I then thought if I go through ADSIedit, I can change the namespace server to the new one for all of my shares, and then possibly be able to load the namespace within the MMC tool
(again just a guess); however, I cannot find anything listed for namespace or remoteservers under the properties of the share.
Note: the namespace does work when I navigate to it from a PC. \\contoso.microsoft.com\data does bring up folders and files. (changed the name for obvious reasons)
At this point, I just want to have my new namespace server, so that I can change the referrals, and decommission my other servers. (And yes there are many other steps I need to perform for the decommissioning, but that's not the point of this). I
have read numerous articles on this and haven't found a way to accomplish what I want. Even though I walked through the steps listed for those issues and unfortunately they either did not apply or did not work. I prefer to not use ADSIedit if at
all possible, simply because it's not the "clean" way of doing things, but if I have no other option then I have no other option.
Edit 1: In event viewer on dc1, under File Replication Service on the left hand side, I see the following error appear numerous times (not every day, but still a lot). I have not performed any of the steps listed simply because
I do not know if this pertains to my problem and I don't want to start troubleshooting a server I plan on decommissioning unless I need to (say for the above issue):
Event ID: 13568
Source: NtFrs
Description:
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.
Expand HKEY_LOCAL_MACHINE.
Click down the key path:
"System\CurrentControlSet\Services\NtFrs\Parameters"
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.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Edit 2: I have verified that firewalls are off and I can communicate to all 4 servers from each other.
Edit 3: Attempted to try and fix error reported in 'Edit 1'; however the registry key mentioned does not exist (looked at all 4 servers to verify).I think in your situation it would be worth trying the things listed under the event. It does have to do with FRS and it's easy to do. I've used it to fix journal errors after a server unexpectedly restarts and sysvol stops replicating. I
could see where it could fix your issue, and if it doesn't, you're out 5 minutes. :)
The listed registry key does not exist
Expand HKEY_LOCAL_MACHINE.
Click down the key path:
"System\CurrentControlSet\Services\NtFrs\Parameters"
Double click on the value name
"Enable Journal Wrap Automatic Restore"
-
Error when adding an Object to the server via CMS
I am trying to upload a new report to the server via CMS.
I click on Objects > Browse for the report > Click Submit
After a few seconds, I get the following error:
There was an error while writing data back to the server: File Repository Server error : File system operation for frs://Input.reportingdb/a_068/047/000/12100/172659d5862b3e2.rpt on File Repository Server failed. If the problem persists, please contact your system administrator for event log information.
I can see that the Input.reportingdb server is running
I have tried restarting the physical server that CRE XI R2 is running on.
I have restarted the Tomcat as well as all of the report servers via ccm.sh and enabled all of the report servers via ccm.shYes, the installation directory is:
/opt/crystal/bobje
The directory where the repository is located:
data
Here are the permissions:
drwxr-xr-x 14 oracle oinstall 4096 Mar 24 16:10 data
Here are the permissions of the subdirectory:
drwxrwxrwx 2 oracle oinstall 4096 Jul 22 2008 Auditing
drwxrwxrwx 2 oracle oinstall 4096 Jul 22 2008 cacheserver
drwxrwxrwx 11 oracle oinstall 4096 Mar 26 09:50 frsinput
drwxrwxrwx 60 oracle oinstall 4096 Mar 24 16:11 frsinput_bak
drwxrwxrwx 259 oracle oinstall 12288 Mar 24 09:54 frsoutput
drwxrwxrwx 2 oracle oinstall 4096 Jul 22 2008 pageserver
drwxrwxrwx 6 oracle oinstall 4096 Mar 24 09:54 procSched
drwxrwxrwx 2 oracle oinstall 4096 Mar 24 12:07 reportingdb.cacheserver
drwxrwxrwx 3 oracle oinstall 4096 Mar 24 12:07 reportingdb.pageserver
drwxrwxrwx 2 oracle oinstall 4096 Jul 22 2008 reportserver
drwxrwxrwx 2 oracle oinstall 4096 Jul 22 2008 wcs
I have tried multiple times to re-start and re-enable the File Repository and get the error.
Is there a way to reinstall ONLY the File Repository server? -
Error Message: Information is needed before this report can be processed.
Hi Experts,
I am scheduling a Crystal Report from Infoview. Data Source for Report is BEx Query.
While scheduling i am providing all details like Parameters, Formats, Destination etc.
But Schedule is failing. The reason is parameter field is empty when i checked
in failed status , as below.
Parameters: [No Value]; [No Value]
Error Message: Information is needed before this report can be processed.
But when i am viewing the report with the same parameters, it is executing.
Please help
Regards,
Ajay Singh
Edited by: Ajay Singh on Sep 15, 2009 1:05 PMHi,
Try the below mentioned steps in addition to scheduling of your report.
Method 1: Following information might be helpful in resolving the issue.
To check if the .rep file exists in the Output FRS
1.Log on to the Central Management Console (CMC). Click Objects.
2.Click the report object to view its properties.
3.Click the History tab to view the list of instances.
4.Click Success to view the latest instance. Scroll to Instance Location.
5.Note the path name to the report.
6.Check the file store under the Output directory for the report.
If the report does not exist, delete the instance from the History tab in the CMC. Reschedule the report.
Method 2: To verify the configuration of multiple FRS
1.Log on to the CMC.
2.Click Servers.
3.Click the first Input file server. Note the home directory.
4.Click Home > Servers.
5.Click the second Input file server.
6.Check the home directory path for the second Input FRS. It must point to the same directory as the first Input FRS.
7.Repeat steps 2 through 6 to check the Output FRS.
====================
NOTE:
The Input and Output FRS physical machines must be able to connect to the file share for the file store. Also the Input and Output FRS are installed using the local administrator account. That account may not have rights to the network share for the file store. The security on the file store must be changed so the local administrator for each server can access it.
====================
Above mentioned steps are for deski/webi reports.
Cheers,
Suresh ALuri. -
Error while running the Financial Reporting in Workspace.
Dear Folks
I am facing an issue with FR Report in Workspace
Hyperion Version : 11.1.1.3 on Windows 2003 64 bit.
Problem Description: We are trying to run the FRS reports in workspace and getting an error in a window "
Error Details :
Error "<?xml version="1.0" encoding="UTF-8"?>
<BpmResponse action="" type="error">
<code>0</code>
<desc>; nested exception is:
java.rmi.UnmarshalException: error unmarshalling return; nested exception is:
java.io.InvalidClassException: com.hyperion.reporting.properties.PovProperties; local class incompatible: stream classdesc serialVersionUID = -1387329505542936014, local class serialVersionUID = 2904510004932374854</desc>
</BpmResponse>"
Please reply me with solution
Thanks in advance.
Thanks , Harsha.MHi Harsha,
Have you ever been able to run this report successfully? If yes, I would restart Reporting and Analysis services and see if it'll solve the issue?
Also, is there any special characters such as !, &, % in the report? If yes, I would try to remove these and re-run the report.
Hope it helps.
Mehmet -
I am using FRS, how do you select all the level 0 member of say Service Depts ?
I tried doing the Descendants Inclusive of Service Depts, Sames Level as Service depts using Operator " and" and I got the error message when I try to view the report an error: 5200 Error executing query
It's odd that FRS does not have a selection that just does Level 0 as one of the selection on it's add relationship options...
Please help.
ThanksHi,
Use the BottomOfHierarchy function to return all the level0 members.
Have a read of http://download.oracle.com/docs/cd/E12825_01/epm.111/fr_user/27.html for information on the various functions.
Ok?
Cheers
John
http://john-goodwin.blogspot.com/
Maybe you are looking for
-
Flash works on IE 9 (64-bit) but not on IE 9 (32-bit)
I have Windows 7 64-bit. I followed the steps in installing Flash on 64-bit for Internet Explorer. However, in some cases I need Flash to work on my 32-bit Internet Explorer and it simply isn't working. I downloaded the manual (silent) flash installe
-
Hi How do I create a cfg file of my own. ie I need to use MyApp.cfg inplace of the default formsweb.cfg. I am using Forms 9i. I need to retain the formsweb.cfg. I saw how to achive this in 6i. But is it possible in 9i? Please help Regards Sajan
-
Firefox still read old library file (.js) even if it updated
Hi support team, Sometime when i used Firefox to test my site as local host browser. Firefox did not update my library file even if I saved the document. For the example, when I changed jquery file.js and then I saved it. And after that, I executed t
-
Hello all! Yesterday, I upgraded me 12" PB to Leopard. I downloaded and installed the combo update to get up to 10.5.4. My machine gives me the "You must restart" screen constantly. Here is my last error log: Wed Jul 30 22:13:50 2008 Unresolved kerne
-
Running universal installer from Dos batch file
Trying to a script an unattended install for a couple of Oracle client products (namely 9i client and Oracle Workflow Builder). My script runs the relavent setup.exe with a responsefile and silent option. This is working fine but the control is retur