August 8, 2008 at 12:44 am
WHEN I SEND MAIL THROUGH DATABASE MAIL THEN THREE ERRORS I GOT IN [msdb].[dbo].[sysmail_log] BUT MAIL IS RECEIVED BY THE USER.
ERROR-1
---------
Invalid XML message format received on the ExternalMailQueue.
conversation_handle: 1751E177-8C64-DD11-991D-001A644FD5EE.
message_type_name: {//www.microsoft.com/databasemail/messages}SendMailStatus.
message body: <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"> .
====================================================================================================================================================================
ERROR-2
---------
1) Exception Information ===================
Exception Type: System.Data.SqlClient.SqlException
Errors: System.Data.SqlClient.SqlErrorCollection
Class: 16
LineNumber: 1
Number: 6602
Procedure: sp_xml_preparedocument
Server: ETEC-SQL
State: 2
Source: .Net SqlClient Data Provider ErrorCode: -2146232060
Message: The error description is 'Switch from current encoding to specified encoding not supported.'. The XML parse error 0xc00ce56f occurred on line number 1, near the XML text " ".
Data: System.Collections.ListDictionaryInternal TargetSite: Void OnError(System.Data.SqlClient.SqlException, Boolean)
HelpLink: NULL
StackTrace Information =================== at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString) at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result) at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe) at System.Data.SqlClient.SqlCommand.ExecuteNonQuery() at Microsoft.SqlServer.Management.SqlIMail.Server.DataAccess.DataAccessAdapter.PostResponse(Response r, Guid convHandle) at Microsoft.SqlServer.Management.SqlIMail.IMailProcess.ThreadCallBack.PostResponseIfNeeded(MailInfo mi, Response r) at Microsoft.SqlServer.Management.SqlIMail.IMailProcess.ThreadCallBack.MailOperation(Object o)
======================================================================================================================================================================
ERROR-3
---------
Invalid XML message format received on the ExternalMailQueue.
conversation_handle: 1451E177-8C64-DD11-991D-001A644FD5EE.
message_type_name: {//www.microsoft.com/databasemail/messages}SendMailStatus.
message body: ?????????•??????????????????????????????????????????????•????????????????????????????????????????????=????????????????????????????????????†???????††?????????•??????????†?????????•?????????????•???????????????†????????????????????†????????????•???????????? .
September 18, 2008 at 2:45 am
I'm getting this too - on a sql agent notification. Did you ever find out what was wrong?
Cheers,
Matt
January 27, 2011 at 11:04 am
I am getting this error as well. I get it when running msdb.dbo.sp_send_dbmail. It doesn't seem to matter if I switch the @body_format from 'HTML' to 'TEXT' either.
Did you get this resolved?
I did find a stored proc that was out of date compared to our other production servers. But (redgate)SQL Compare now shows them all the same.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply