The Directory Service received a failure while trying to perform an authenticated RPC call to another Domain Controller. The failure is that the desired Service Principal Name (SPN) is not registered on the target server. The server being contacted is %1. The SPN being used is %2. Please verify that the names of the target server and domain are correct. Please also verify that the SPN is registered on the computer account object for the target server on the KDC servicing the request. If the target server has been recently promoted- it will be necessary for knowledge of this computer’s identity to replicate to the KDC before this computer can be authenticated.

Details
Product: Windows Operating System
Event ID: 1645
Source: Active Directory
Version: 5.0
Symbolic Name: DIRLOG_DRA_SPN_WRONG_TARGET_NAME
Message: The Directory Service received a failure while trying to perform an authenticated RPC call to another Domain Controller. The failure is that the desired Service Principal Name (SPN) is not registered on the target server. The server being contacted is %1. The SPN being used is %2. Please verify that the names of the target server and domain are correct. Please also verify that the SPN is registered on the computer account object for the target server on the KDC servicing the request. If the target server has been recently promoted- it will be necessary for knowledge of this computer’s identity to replicate to the KDC before this computer can be authenticated.
   
Explanation

Active Directory did not perform an authenticated remote procedure call (RPC) to another domain controller because the desired service principal name (SPN) for the destination domain controller is not registered on the Key Distribution Center (KDC) domain controller that resolves the SPN.

   
User Action

Verify that the names of the destination domain controller and domain are correct. Also, verify that the SPN is registered on the KDC domain controller. If the destination domain controller has been recently promoted, it will be necessary for the local domain controller’s computer account data to replicate to the KDC before this computer can be authenticated.

Related:

The GovernsID attribute is missing from class schema object %1. Stop and restart this Windows Domain Controller and try again.

Details
Product: Windows Operating System
Event ID: 1032
Source: Active Directory
Version: 5.0
Symbolic Name: DIRLOG_GOVERNSID_MISSING
Message: The GovernsID attribute is missing from class schema object %1. Stop and restart this Windows Domain Controller and try again.
   
Explanation

Internal event: Active Directory could not find the GovernsID attribute for the schema class.

   
User Action

Restart this local domain controller, and then try again.

Related:

Active Directory failed a query for a UNIX user’s corresponding Windows user account. The user will not be able to access NFS shares on this server.

Details
Product: Windows Operating System
Event ID: 4012
Source: Server for NFS
Version: 5.2.3790.1830
Message: Active Directory failed a query for a UNIX user’s corresponding Windows user account. The user will not be able to access NFS shares on this server.
   
Explanation

For UNIX users to access files on a Windows computer through Server for NFS, the UNIX users must associated with Windows user accounts. Storing UNIX UID and GID data in Active Directory enables Server for NFS to find corresponding Windows accounts for UNIX users.

If Server for NFS cannot access an Active Directory server, discovers multiple Windows user accounts associated with a UNIX UID, or discovers multiple Windows groups associated with a UNIX GID, Server for NFS will not provide file access to the UNIX user.

Cause

Manually query Active Directory to verify that no Windows user accounts have the same UID.

   
User Action

Verify the Active Directory server is online and available.

Make sure that Windows and UNIX users are mapped one-to-one.

Make sure that Windows and UNIX groups are mapped one-to-one.

Related:

Service detected and dropped inconsistent volume configuration

Details
Product: Windows Operating System
Event ID: 6602
Source: DFSR
Version: 5.2.3790.1830
Message: Service detected and dropped inconsistent volume configuration
   
Explanation

The DFS Replication service detected and discarded an inconsistent volume configuration.

Cause

This error can appear when multiple configurations reference the same volume.

   
User Action

Determine the last configuration change made to the volume configuration and verify whether any replicated folders on that volume have already been configured.

If previous configurations conflict with the current configuration, resolve the conflicts. If the conflict cannot be resolved, delete the membership of the member and re-create the membership.

Related:

Working folder overlaps with Windows system folder

Details
Product: Windows Operating System
Event ID: 6410
Source: DFSR
Version: 5.2.3790.1830
Message: Working folder overlaps with Windows system folder
   
Explanation

A replicated folder overlaps with the DFS Replication service debug log.

Cause

The folder is not being replicated because replication of a DFS Replication service debug folder is an unsupported configuration.

   
User Action

Reconfigure the replicated folder so that none of its working folders overlaps with the debug folder.

Related:

Service detected invalid object data while polling for configuration information

Details
Product: Windows Operating System
Event ID: 6002
Source: DFSR
Version: 5.2.3790.1830
Message: Service detected invalid object data while polling for configuration information
   
Explanation

The DFS Replication service detected an invalid object while polling the domain controller for configuration information.

Cause

The object’s attributes do not match the expected attributes.

   
User Action

The service will try polling again in a few minutes, at which time the problem can resolve itself. If the problem is resolved, Event 6014 will be displayed.

Note: If the service is restarted before the problem is corrected, the success event will not be displayed.

If the problem does not resolve itself, check the object attribute being reported as invalid against what it should be in the MSDN documentation.  It might be necessary to delete the object and reconfigure it in Active Directory® using the management tools.

Related:

The XsltFileName argument is missing.

Details
Product: SQL Server Notification Services
Event ID: 7001
Source: NotificationServices
Version: 2.0.9999.9
Message: The XsltFileName argument is missing.
   
Explanation
This error occurs when your ADF specifies the use of an XSLT content formatter, but does not include the XsltFileName argument, which is required by the XSLT content formatter.
   
User Action
In your ADF, search for “XsltFormatter”. In the <contentformatter> element, find the segment that looks similar to this:

<contentformatter><classname>XsltFormatter</classname><arguments>

Inside the <arguments> element, make sure that you have the XsltFileName argument defined. It should look like this:

<argument><name>XsltFileName</name><value>MyTransform.xsl</value></argument>

Make sure that the XsltFileName argument is spelled correctly and defined exactly once.</arguments></arguments></contentformatter></contentformatter>

Related:

Could not open new database ‘%.*ls’. CREATE DATABASE is aborted.

Details
Product: SQL Server
Event ID: 1813
Source: MSSQLServer
Version: 8.0
Component: SQL Engine
Message: Could not open new database ‘%.*ls’. CREATE DATABASE is aborted.
   
Explanation
sp_attach_single_file_db or sp_attach_db failed to attach the specified data and/or log files. A common scenario is that you used sp_attach_single_file_db to attach a database that had multiple log files. For more information about this scenario, see the Microsoft Knowledge Base article271223.

If other errors occurred, this could be a side effect of another failure.

   
User Action
If other errors occurred, address them first.

Always detach a database with sp_detach_db before you attach the files. Always attach all the files that were detached; do not try to leave off the log files in an attempt to shrink the database. To properly shrink a database, follow the instructions in the Microsoft Knowledge Base article 272318.

Related:

CREATE DATABASE failed. COLLATE clause cannot be used with the FOR ATTACH option.

Details
Product: SQL Server
Event ID: 1812
Source: MSSQLServer
Version: 8.0
Component: SQL Engine
Message: CREATE DATABASE failed. COLLATE clause cannot be used with the FOR ATTACH option.
   
Explanation
Your CREATE DATABASE statement included both the COLLATE clause and the FOR ATTACH option. These options cannot be used together in a CREATE DATABASE statement. When you use the FOR ATTACH option, you are attaching existing database files, and the COLLATION of those files will be applied to the new database.
   
User Action
Do not specify both the COLLATE clause and the FOR ATTACH option in the CREATE DATABASE statement. If you need to change the collation of the database you attached, follow the instructions in Microsoft Knowledge Base article 325335.

Related: