Send Mail Task Error

[Catadmin]

Google isn't helping a whole lot.

We're currently on SQL 2000 on our "real" environment and are in the process of having new servers with SQL 2k5 installed. Until then, we're changing over our DTS to SSIS on a sandbox server which has network connectivity but no Outlook installed. This should be fine since the Send Mail Task uses SMTP, right?

Anyway, I have a Send Mail Task which keeps coming up with the below error.

Error: 0xC002F304 at File Not Exists Email, Send Mail Task: An error occurred with the following error message: "Command not implemented. The server response was: Command not Supported".
Task failed: File Not Exists Email

Warning: 0x80019002 at <My Package Name>: The Execution method succeeded, but the number of errors raised (1) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors.

SSIS package "<My Package Name>" finished: Failure.

The email addresses are valid because we're using them in current jobs on SQL 2000. The SMTP server name is valid because we're also currently using it with the xp_SMTP_SendMail stored procedure designed specifically for SQL 2000 many moons ago by someone on SQLDev.net.

This is seriously annoying as I can't figure out the cause of the error. Any thoughts?

Thanks,


Catadmin - MCDBA, MCSA
"No, no. Yes. No, I tried that. Yes, both ways. No, I don't know. No again. Are there any more questions?"
-- Xena, "Been There, Done That"

 

[Catadmin]

AHA!

With the help of a collegue, I discovered that you can't use the ol' "mail.<domain>.com" definition of your SMTP server. It has to be the actual, literal, fully qualified servername.domain.com address.

Assuming, of course, that ther Surface Area Configuration is already set up to enable Database Mail and that it was already configured with a profile by going into SSMS, right-clicking Database Mail and choosing "Configure". I had already done that, but again, I used the old mail.<domain>.com in the Account instead of the fully qualified server name.

Once that was fixed, error message went away and the task worked wonderfully.



Catadmin - MCDBA, MCSA
"No, no. Yes. No, I tried that. Yes, both ways. No, I don't know. No again. Are there any more questions?"
-- Xena, "Been There, Done That"