Applications that use the ActiveX Data Objects (ADO) interface in the following scenario may experience functionality issues:

• An application connects to Microsoft SQL Server 2005, to SQL Server 2005 Express Edition, to Microsoft SQL Server 2000, or to SQL Server Desktop Engine (also known as MSDE 2000).
• The application uses the SET NOCOUNT ON statement for the connection.
• The application inserts a row into a table that has an identity column by using a Microsoft ActiveX Data Objects (ADO) client-side cursor.

Note: This issue only occurs if the application uses a client-side cursor. If the application uses a server-side cursor, the application is not affected.
When the application queries the identity column value of the newly inserted row, the value “0″ is returned incorrectly. This may cause an application to malfunction or even data loss. Whether a malfunction or data loss occurs depends on how the application handles this scenario.

This problem exists in the Microsoft Data Access Components (MDAC) components of the following Windows operating systems:

• Windows Vista Service Pack 1
• Windows XP Service Pack 2 with hotfix 940569
• Windows XP Service Pack 3
• Windows Server 2008

To prevent this problem, install the hotfix that is described in this article.

On a Windows Vista-based computer, assume that you run an application that uses either the SQLDescribeCol function or the SQLColAttribute function to query the information for column length in a result set. In this situation, the query incorrectly returns the value of 2147483598 instead of the expected value of 255.

This article describes the following about this hotfix release:

• The issues that are fixed by the hotfix package
• The prerequisites for installing the hotfix package
• Whether you must restart the computer after you install the hotfix package
• Whether the hotfix package is replaced by any other hotfix package
• Whether you must make any registry changes
• The files that are contained in the hotfix package

On a Windows Vista-based computer, when you try to connect to Microsoft SQL Server Management Studio by using a virtual private network (VPN) connection, you receive an error message that resembles the following:

The user is not associated with a trusted SQL Server Connection

Note: This issue does not occur on a Windows XP Service Pack 2 (SP2)-based computer in the same environment.

On the computer that hosts the SQL Server role, the following events are logged:

Event Type: Error
Event Source: MSSQLSERVER
Event Category: (4)
Event ID: 17806
Date: Date
Time: Time
User: N/A
Computer: Computer
Description: SSPI handshake failed with error code 0x8009030c while establishing a connection with integrated security; the connection has been closed. [CLIENT: ClientIPAdress]
For more information, see Help and Support Center at go.microsoft.com/fwlink/events.asp.

Event Type: Failure Audit
Event Source: MSSQLSERVER
Event Category: (4)
Event ID: 18452
Date: Date
Time: Time
User: N/A
Computer: Computer
Description: Login failed for user. The user is not associated with a trusted SQL Server connection. [CLIENT:ClientIPAdress]
For more information, see Help and Support Center at go.microsoft.com/fwlink/events.asp.

If you enable debug logging for the Netlogon service on the authenticating server, the following entry is logged in the in the Netlogon.log file:

[LOGON] SamLogon: Network logon of Computer\User from Computer Entered
[CRITICAL] NlPrintRpcDebug: Could not get EEInfo for I_NetLogonSamLogonEx: 1761 (may be legitimate for 0xc0000064) (err 0xc0000064 = STATUS_NO_SUCH_USER)
[LOGON] SamLogon: Network logon of Computer\User from Computer Returns 0xC000006A (err 0xC000006A= STATUS_WRONG_PASSWORD)

Note: Computer is a placeholder for the name of the Windows Vista-based computer. Also, User is a placeholder for the user account that you use to log on to the computer.

This entry indicates that Windows Vista uses the Windows Vista-based computer credentials for authentication instead of using the domain credentials.

Note: In different network environments, the following servers can be authenticating servers:

• A Routing and Remote Access server
• An Internet Authentication Service (IAS) server

When you try to install the original release version of Microsoft SQL Server 2005 or Microsoft SQL Server 2005 Service Pack 1 (SP1) on a computer that is running Windows Vista, you receive the following error message:

SQL Server Setup failed to execute a command for server configuration. The error was [Microsoft][SQL Native Client][SQL Server]Windows NT user or group ‘ COMPUTERNAME \SQLServer2005MSSQLUser$ COMPUTERNAME $INSTANCENAME’ not found. Check the name again. Refer to the server error logs for detailed error information.

This problem occurs if the following conditions are true:

• The name of the computer that is running Windows Vista consists of lowercase characters or of a mixture of lowercase characters and uppercase characters. For example, the name of the computer resembles the following name:
  

  Workstation-1

• You specify a case-sensitive collation setting for the SQL Server service when you install SQL Server 2005.

Note: In some cases, this problem may occur if the name of the computer contains some special characters. For example, this problem may occur if the name of the computer contains some characters in Turkish.

When you try to install Microsoft SQL Server 2005 Express Edition Service Pack 1 (SP1) on a computer that is running Windows Vista, you receive the following error message:

SQL Server Setup failed to execute a command for server configuration. The error was [Microsoft][SQL Native Client][SQL Server]Windows NT user or group ‘COMPUTERNAME\SQLServer2005MSSQLUser$COMPUTERNAME$MSSQLSERVER’ not found. Check the name again.. Refer to the server error logs for detailed error information.

SQL Server 2005 Service Pack 2 supports Vista. Keep reading →