March 2, 2004 at 3:00 pm
My client is able to send mail from the SQL Server 7.0 machine only when Outlook is opened. SQL Mail service is running all the time. This is a Windows domain environment with Exchange server on the LAN.
Thank you.
Michael
March 3, 2004 at 2:52 am
Does Outlook need to be opened on your other servers. Did this server ever send mail without Outlook opened.
If you look at forum archives you will find a lot of postings about SQL Mail problems. We have had a number at our site. This is not the most reliable bit of software Microsoft have released.
Presumably you are running SQL services using a domain account, that is also local admin on your SQL box. It can be difficult to get all SQL functionality working properly if you do not use this configuration.
If the problem only affects one box, the most likely cause is a corrupt mail profile. Our experience is that mail can work OK for months, then become corrupt. Sometimes a reboot can clear the problem, sometimes it can cause it... It is worth working with your Exchange admin people to check if they can find anything wrong with the profile.
If nothing can be found, try deleting and re-creating the profile. Sometimes when you do this, you must give the profile a new name. In our worst case, we had to re-install NT to get tings working (but this was on a DEV machine that had received a lot of other abuse).
All information provided is a personal opinion which may not match reality.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
March 3, 2004 at 7:20 am
It's important to log into the machine as the account that starts SQL Server before you configure any mail.
Also, there used to be an issue with NT and SQL Server 7 where mail messages got stuck in the outbox until logging on and opening the inbox. The solution is to replace "system32\mapi32.dll" with a later version. I think there's a Microsoft document on their website.
Donhttp://www.biadvantage.com
March 3, 2004 at 8:16 am
U can check that the SQL Agent is not running under system account and also check that the profile you have attached doesn't have any password.
This will solve the problem.
March 3, 2004 at 8:21 am
You didn't state which version of Outlook you were using. There are problems with some versions of Outlook (2000+) and the security patches installed when using with SQL Server 7.0. I seem to recall to either stick to Outlook 98 or Outlook 2000 without any patches applied.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply