SQL Server Q&A

Symptoms
This article describes the following about this hotfix release:The issues that are fixed by this hotfix packageThe prerequisites for installing the hotfix packageInformation about whether you must restart the computer after you install the hotfix packageInformation about whether the hotfix package is replaced by any other hotfix packageInformation about whether you must make any registry changesThe files that are contained in the hotfix package
Resolution
When you try to use the sp_send_dbmail stored procedure to send an e-mail in SQL Server 2005, an error message that resembles the following is written to the database mail log:

Invalid XML message format received on the ExternalMailQueue. conversation_handle: 61D18223-D17B-DB11-B0E7-0014221181C7.message_type_name: {//www.microsoft.com/databasemail/messages}SendMailStatus.message body:
<?xml version=”1.0″ encoding=”utf-8″?>
<responses:SendMail xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance” xsi:schemaLocation=”http://schemas.microsoft.com/databasemail/responses ResponseTypes.xsd” xmlns:responses=”http://schemas.microsoft.com/databasemail/responses”>
<Information>
<Failure Message=”The mail could not be sent to the recipients because of the mail server failure. (Sending Mail using Account 1 (2006-11-24T16:33:54). Exception Message: Could not connect to mail server. (Une tentative de connexion a échoué car le parti connecté n’a pas répondu convenablement au-delà d’une certaine durée ou une connexion établie a échoué car l’h?te de connexion n’a pas répondu).&#xD;&#xA;)” />
</Information>
<MailItemId Id=”2″ />
<SentStatus Status=”3″ />
<SentAccountId Id=”0″ />
<SentDate Date=”2006-11-24T16:33:54″ />
<CallingProcess Id=”864″ />
</responses:SendMail>Note The following text is the English translation of the error message:
A connection attempt failed because the party connected did not properly respond within a certain period of time, or a connection established failed because the host connection did not respond.
Additionally, when you query the msdb.dbo.sysmail_allitems table for the operation record, you notice that the value of the sent_status column is UNSENT instead of FAILED.
This problem occurs if the following conditions are true: You are running SQL Server 2005 on a localized version of the Microsoft Windows operating system. For example, you are running SQL Server 2005 on the French version of Microsoft Windows Server 2003.The e-mail actually was not sent for some reason. For example, the e-mail was not sent because of an unknown recipient or an incorrect server name.

Symptoms
This article describes the following about this hotfix release:The issues that are fixed by this hotfix packageThe prerequisites for installing the hotfix packageInformation about whether you must restart the computer after you install the hotfix packageInformation about whether the hotfix package is replaced by any other hotfix packageInformation about whether you must make any registry changesThe files that are contained in the hotfix package
Resolution
In SQL Server 2005, an error message that resembles the following is logged in the SQL Server error log after you roll back transactions on a table:

Error: 3315, Severity: 21, State: 1
During rollback, the following process did not hold an expected lock: process 51 with mode 8 at level 2 for row Rid pageid is (1:73) and row num is 0×0 in database ‘DatabaseName’ under transaction (0:546). Restore a backup of the database, or repair the database.This problem occurs when page locks are disabled on the table before the transactions are rolled back.
NotesIn the error message, DatabaseName represents the database that contains the table.You may have run the sp_indexoption stored procedure todisable the page locks on the table.For more information about how to view the SQL Server error log, visit the following Microsoft Developer Network (MSDN) Web site:
http://msdn2.microsoft.com/en-us/library/ms187885.aspx(http://msdn2.microsoft.com/en-us/library/ms187885.aspx)