asked
Exchange Server upgrade breaks SQL Server jobs
Our Systems Infrastructure team upgraded our mail servers this last weekend and now all our jobs that generated emails are no longer doing so. We updated all our mail server settings in our jobs several days before the upgrade and they were all still working fine. but after the physical upgrade they are not working. Has anyone seen this issue and have a possible resolution? I am sure it is a configuration issue on the exchange server, but I do not know where to look. Any assistance would be extremely helpful.
Need more details. What type of upgrade? In place or did they do a parallel upgrade and fail over to new servers? If new servers, I would check with my firewall folks. You stated you all made configuration changes to your jobs before the upgrade, what type of changes? Mail server IP or DNS, profile email address account, port, etc? Have you reviewed the mail log to see what error SQL is giving, timeout, invalid user, can not resolve host, etc?
One issue that has impacted me in the passed is IP restriction on the mail relay. Also if you are sending to a email distribution group then there are also restriction on that too (especially if your DBMAIL "from" account doesnt exist). You could also try testing sending a dbmail and reviewing the logs as @tim has suggested.
I think I found the issue. The new Exchange server is not resolving the @@servername used in the @from variable. I do not want to change this back to a "hard-coded" address as it does not lend itself to portability. The exchange team is setting up a connector on the exchange server to "hopefully" fix this
OK....... Looks like Exchange 2010 does not like anything other than a fully qualified email address (e.g.
servername@company.com. Thinking out loud here.....can the @company.com be appended to @@servername?
15 People are following this question.
