SQL Server Q&A

Symptoms
This article describes the following about this hotfix release:The issues that are fixed by the hotfix packageThe prerequisites for installing the hotfix packageWhether you must restart the computer after you install the hotfix packageWhether the hotfix package is replaced by any other hotfix packageWhether you must make any registry changesThe files that are contained in the hotfix package
Resolution
When you try to use Database Mail to send an e-mail message in Microsoft SQL Server 2005, you receive the following error message:

TITLE: Microsoft SQL Server Management Studio
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
ADDITIONAL INFORMATION:
profile name is not valid (Microsoft SQL Server, Error: 14607)
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.2047&EvtSrc=MSSQLServer&EvtID=14607&LinkId=20476
BUTTONS:OK
——————————This problemoccurs if the following conditions are true:You log in to the instance of SQL Server by using a Microsoft Windows account.You send the e-mail message by using a private Database Mail profile.

Symptoms
When you try to perform a one-phase commit on an XA-, or two phase-, enabled JDBC connection in Microsoft SQL Server 2005, the following exception occurs:

Exception in thread “main” com.microsoft.sqlserver.jdbc.SQLServerException: The COMMIT TRANSACTION request has no corresponding BEGIN TRANSACTION.
at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(Unknown Source)
at com.microsoft.sqlserver.jdbc.IOBuffer.processPackets(Unknown Source)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectionCommand(Unknown Source)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.sendCommit(Unknown Source)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.commit(Unknown Source)
Resolution
This problem occurs because SQL Server 2005 does not allow a one-phase commit on a two-phase-enabled data source.

Symptoms
Consider the following scenario. In Microsoft SQL Server 2005, you restore a database from a backup. Then, you try to open a full-text catalog by using SQL Server Management Studio. In this scenario, you may receive the following error message:

Property IsAccentSensitive is not available for FullTextCatalog ‘[CatalogName]‘. This property may not exist for this object, or may not be retrievable due to insufficient access rights. (Microsoft.SqlServer.Smo) Additionally, when you try to query the information about the AccentSensitivity property of the full-text catalog by using the FULLTEXTCATALOGPROPERTY Transact-SQL function, you receive a null value. For example, you use a Transact-SQL statement that resembels the following statement to query the information about the AccentSensitivity property.

select FULLTEXTCATALOGPROPERTY(‘<CatalogName>’,'AccentSensitivity’)When you use this statement, you receive a null value. However, when you query the information about the AccentSensitivity property directly from the full-text catalog view, SQL Server returns the correct information. For example, you can use the following Transact-SQL statement to query the information.

select * from sys.fulltext_catalogsThis problem may occur when the following conditions are true: You back up a database and then delete the database.The database has a full-text catalog.Before you restore the database, you create one or more databases. Therefore, the previous database ID is used by the newly created databases.
Resolution
This problem occurs because SQL Server stores a wrong full-text catalog name for the existing full-text catalog when you restore the database.

Symptoms
Consider the following scenario. In Microsoft SQL Server 2005 Integration Services (SSIS), you create an SSIS package. The SSIS package contains some Script tasks or Script components. When the file size of the SSIS package increases to more than 7 megabytes (MB), you receive the following error message when you try to save the SSIS package in SQL Server Business Intelligence Development Studio:

TITLE: Microsoft Visual Studio
Failure saving package.
ADDITIONAL INFORMATION:
Exception of type ‘System.OutOfMemoryException’ was thrown. (Microsoft.SqlServer.ManagedDTS)
BUTTONS:
OK
Resolution
This problem occurs because heap memory is fragmented in the SQL Server Business Intelligence Development Studio process.

Symptoms
When you start SQL Server Management Studio in Microsoft SQL Server 2005, you receive the following error message in a Microsoft .NET Framework dialog box:

Unhandled exception has occurred in a component in your application. If you click Continue, the application will ignore this error and attempt to continue.
Unable to cast object of type‘Microsoft.SqlServer.Management.UI.ConnectionDlg.Personalization’ to type’Microsoft.SqlServer.Management.UI.ConnectionDlg.Personalization’.
Resolution
This problem occurs when you have Microsoft SQL Server 2005 Express Edition or SQL Server 2005 Express Edition with Advanced Services installed side-by-side with one of the following SQL Server 2005 editions:MicrosoftSQL Server 2005 Standard Edition Microsoft SQL Server 2005 Developer Edition Microsoft SQL Server 2005 Enterprise EditionIn this case, the Mru.dat file that is installed by SQL Server 2005 Express Edition or SQL Server 2005 Express Edition with Advanced Services causes this error message.

Symptoms
When you create a new maintenance plan that runs on a schedule in Microsoft SQL Server 2005, you may receive the following error message:

Create maintenance plan failed.
Additional information:
Create failed for JobStep ‘Subplan’. (Microsoft.SqlServer.MaintenancePlanTasks)
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
The specified ‘@subsystem‘ is invalid (valid values are returned by sp_enum_sqlagent_subsystems). (Microsoft SQL Server, Error 14234)This behavior may occur when you create the maintenance plan manually or by using the Maintenance Plan Wizard.
Resolution
This behavior occurs when you install SQL Server 2005 without installing the SQL Server 2005 Integration Services (SSIS) service. When you create the maintenance plan, the following code is run.

EXEC msdb.dbo.sp_update_jobstep @job_name=N’System DB Maintenance Plan’, @step_id=1 , @subsystem=N’SSIS’, @command=N’/SQL “\Maintenance Plans\System DB Maintenance Plan” /SERVER ASHBSQL701 /MAXCONCURRENT ” -1 ” /CHECKPOINTING OFF’This code tries to access the Integration Services service.