SQL Server Agent &> General Tab &> Mail Session Is Greyed Out ??
Feb 22, 2004
Hi All,
Great forum y'all have going here.
Just wondering if anyone else has experienced this?
Enterprise Manager:
I have setup and 'sucessfully tested a MAPI session' with a mail profile via support services > sql mail. That works fine, however in sql server agent properties the mail session section on the first general tab appears to be greyed out.
scenario is:
Windows Server 2003 SBS edition
SQL Server 2000 SP3
Exchange Server 2003 is also running on the server, with Outlook 2003 client (so i suspect side chaining issue).
Any help appreciated! did not have any luck googling or using microsoft KB.
I'm not sure what happened, but all of a sudden my SQL Server Agent service won't start. When I try to start it, I get the following error in the event logs:
"SQLServerAgent could not be started. Error creating a new session".
When I look in the Agent log file, i see the following:
Execute permission denied on object sp_sqlagent_has_server_access
Execute permission denied on object sp_sqlagent_get_startup_info
Hello Everyone, I am trying to configure SQL MAIL and SQL SERVER AGENT MAIL feature of SQL SERVER 2000 with Lotus Domino server (Not Microsoft Exchange). Every thing goes fine and it works also. Problem starts when I try to restart SQL Agent Service. It hangs and the status of service remain 'starting'... Also the size of the sqlagent service process goes upto 12MB. I don't understand why? Can any one help me in solving this problem. I am using Windows 2000 Advanced Server and SQL Server 2000 with SP3. Domino client is R5.0.5 and Outlook 2000.
Hi,I've been able to successfully configure SQL Server Agent to sendnotification emails to an appropriate Operator in the event of an alertbeing fired. This all works fine on one condition - that Outlook clientis running on the server.If Outlook is not running the alerts still be fired (i.e. the OccuranceRate still increases as and when expected), but the emails beinggenerated will not be sent until the next time Outlook is opened.Clearly it's unwise to rely on Outlook being open on the server at alltimes, so I was wondering if anyone knows of a workaround to ensurethese emails are processed immediately?I'm using SQL Server 2000 SP4 and Outlook 2003.thanks,Bob.
Wondering if anyone there can tell me what I'm doing wrong (and please be gentle as I'm not at all techy).
I have a DTS scheduled on the Server Agent to run, and at the end it is to send a mail to notify me and several others that it has completed. Trouble is, it runs but doesn't send the mail.
However if I execute the DTS manually it does send the mail.
I have a idea it might be to do with the Profile in SQL Mail in Server Settings on the Properties of the server, but have no idea how to correct this. Can anybody help?
I call a stored proc from an ASP page that eventually makes a call to xp_sendmail to email a confirmation back to our visitor. It all works fine as long as the Exchange Server hasn't crashed and therefore, rendered the SQL Mail session dead. Unfortunately, when this happens (which has been all too often recently), the web visitor gets the following message:
Number: -2147217900
Description: [Microsoft][ODBC SQL Server Driver][SQL Server]SQL Mail session is not started.
SQLState: 37000
Native Error: 17966
Is there a way I can check for this in the stored proc that calls xp_sendmail so I could still return to the ASP page and prevent the web visitor from seeing this error.
Is there any way to use different email accounts for sql mail dynamically on sql server 2000?
Here is the problem:
My sql server is configured to start mail session under account 'xxnotifyxx'.
There are many jobs scheduled to run queries and send out emails to different user groups within the company as well as outside the company from 'xxnotifyxx' as a sender.
However, one of the usergroup within the company is asking for sending out their emails ( from scheduled tasks that uses xp_sendmail ) using 'publishergroup' as a sender.
As far as I know, this is not possible (sql server 2000, exchange 2000 client win2000 ) until I change the mail session configuration to start under 'publishergroup' in stead of 'xxnotifyxx'. If I do this, 9 other groups have problems with this.
Is there a work around for this kind of situation?
Hello! I created SQLServer account which suppose to launch MSSQLServer and SQL mail serveces. But when I try to stop and then run SQL Server through Command promt I see error message: " Starting SQL Mail session.... Error: 17903, Severity:18, state:1 MAPI login failure Error: 17951, Severity:18, state:1 Failed to start SQL MAil session" Please save my life. If you have any idea what I have to do to fix up problem let me know.
I've set up Database Mail on an instance of 2005 and the test mail works just fine. However, when testing a job (notify on fail, success, whatever) the mail fails to send. Job History last information reads NOTE: Failed to notify 'My Name' via email.
Checked out the Database Mail logs - nothing interesting.
Restarted the Agent service and then checked out the current Agent Log. Found message:
[260] Unable to start mail session (reason: No mail profile defined).
The 'DatabaseMailProfile' key is most certainly defined in the Registry (at 'HKEY_LOCAL_MACHINE', N'SOFTWAREMicrosoftMicrosoft SQL ServerMSSQL.1SQLServerAgent')
I'm at a loss...why is it telling me no mail profile defined? I'd be most grateful for any help if anybody else has run across this problem.
It's a Windows 2000 Server box with SQL 2000 on it. MSSQLSERVER &SQLSERVERAGENT services are logged in as valid domain user. I set up amail profile for that user, and can send email via Outlook 2003.However, when I go to the SQL Agent Properties in Enterprise Manager,Mail Profile is disabled.I've restarted the services & even tried rebooting the server. Thisworks on my other servers, but they're Windows 2003. Not sure ifthat's the problem though.Anybody have any clues?
Upgraded SQL Server 2005 x64 to Service Pack 1 expressly for the purpose of enabling Database Mail from SQL Job, which was a known bug that was listed as fixed in this Service Pack. It still does not work; in fact after installing SP1 on an x86 SQL Server Standard, Database Mail does not work from there now either, although it did prior to the upgrade! I am using Integrated Security.
Error message received: The job succeeded. The Job was invoked by User <name>. The last step to run was step 1 (Select). NOTE: Failed to notify 'Mike Schelstrate' via email.
Message in Error Log: [264] An attempt was made to send an email when no email session has been established.
Send test Email does work on both Servers.
Here is another Error message I found in the SQL Error Logs: [298] SQLServer Error: 2812, Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'. [SQLSTATE 42000] (DisableAgentXPs). Looks like this may be the root of the problem because it does not exist, I checked. How do I obtain this missing extended stored procedure?
I am looking to make the primary key auto increment by 1. I have found by looking around the internet that you need to do this in the Tables -> [Table Name] -> Columns -> [Column Name], Properties window, and I see the "Identity Increment" however all of the properties there are greyed out -- I can't access them. Any ideas on how to make this work?For some background: I'm running SQL Server 2005 with Visual Studio 2005. To create this database, I right-clicked on my project, and went to 'Add SQL Database', I filled in the columns all from within visual studio.
I cannot understand why I cannot get my sql mail to work properly. It was working fine a couple of days ago. My mail profile is setup using Outlook. The only problem is that when I go to services and check the Mssqlserver & sqlserveragent, they are now logging in as the system account, but when I attempt to change them to the administrator account it says error 1057 occured: the account name is invalid or does not exist, yet it does. Anyone have any idea how to rectify this? this is what is on the error log:Error: 17919, Severity: 18, State: 1 2001-06-05 14:09:16.33 ods Invalid session.. 2001-06-05 14:09:16.34 ods Error: 17951, Severity: 18, State: 1 2001-06-05 14:09:16.34 ods Failed to start SQL Mail session..
I would like to configure e-mail alerts on my SQL Server 2000 box.However, we also run Exchange on the same machine. I've been told therecould be conflicts/issues having Outlook on the same machine asExchange; and apparently, one needs Outlook to configure a mail profilefor SQL Server Agent.Is there, in fact, anything to worry about? If so, are there anywork-arounds beside moving Exchange to another server? (we've only gotone server, so this is not an option for us at this time).Thanks.- Dana
Hi I would like to know if it's possible to use pop3 server protocol instead of MAPI application to cause SQL Server 2000 sends email to an Administrator when anormal event comes ? i.e, configure a pop profile to receive sql server 2000 error
Hi I would like to know if it's possible to use pop3 server protocol instead of MAPI application to cause SQL Server 2000 sends email to an Administrator when anormal event comes ? i.e, configure a pop profile to receive sql server 2000 error
I have been reading everything i can find regarding sql mail and sqlagent mail.We have a win2k server, sql 2000 and NO, NO, NO exchange server(all upto date on service packs).I have tried repeatadly for days to make this work, and have had noluck so far.1. I have a valid profile that tests fine in sql agent and via sqlmail test buttons.2. I have logged in to the box under that new domain account toinstall outlook and configure all the remaining options.3. I have set both the mssqlserver service and the sqlserveragentservice to run under the domain account that coincides with our pop3email server, and restarted both of them.4. I have installed outlook 2002, and I can send and receive emailsjust fine from our sql server.5. As soon as I try to test an email from within a job, the testfails.All I wanted to do was just be notified if a job fails. The amount oftime lost on what should have been a 30 minute project isunbelievable!!!If anyone has some suggestions, other than the obvious, please let meknow.Thanks,Dave
The 2.0 version of ASPSTATE is slightly different than the 1.1 version in that one table has one additional column and another table uses a different data type and size for the key. The 2.0 version also has a couple additional stored procedures.
We'd like to manage just one session state database if possible so we're trying to figure out if Microsoft supports using the new schema for 1.1 session state access (it seems to work, but our testing has been very light).
Is there any official support line on this? If not, can anyone comment on whether or not you'd expect it to work and why?
I setup a domain user account and e-mail account for the sql agent. When I want the agent to mail me a message when something happens it puts it in the out box but does not send until I pull up the outlook express and ping the server to send recieve. If I don't have outlook express running in the taskbar, it won't send the message at all. The e-mail is configured as an internet mail component. Any suggestions??
I have a daily task set up to email a report to me. When I go to look at the jobs it says it is still executing after a number of hours. I Can't stop the job with out stopping SQL Agent. I can't stop SQL Mail. If I stop the SQL Agent I can't start it again. I try to open Outlook (98) but it won't open either. Can't view the properties of Outlook either. Only way to cure this is to reboot the server. The account we are using to start SQL and SQL Agent is a FDomain Admins account. When I try to log off the server I get and error message saying olemainthreadwndname is not responding. Any help would be very much appreciated.
My sql agent mail suddenly stops working. The mails are usually going to the people. But once in a while I have this wierd problem of mails not reaching the recipients. Happens once in 2-3 weeks, starts working fine if I restart the server. When I open the Outlook client, the outbox is also empty, but still the mails are not gone. If I Test the mail profile in the sql agent properties, it gives time out error. Everything becomes okay if I restart the server.
OS: Win 2K sp4 Server : SQL 2000 SP3 Account : Verified that the account is in Administrator Group There is only one MAPI32.DLL file and is in system32 folder.
The wierd part is everything works if I restart..any help would be much appreciated.
Hi I have sql 2005 enterprise edition 64 bit. I can't make work SQL Agent Job alerts and notifications. I have setup Database mail - sent test mail successfully I have created account for Outlook Express and tried to feed SQL agent Alert system with it. No use... Can anybody help?
Assistance PleaseI have a couple of scheduled jobs that are failing to e-mailnotifications on completion (via SQL Agent Mail).I can send a Test e-mail without any problems. I can run the jobsmanually, and the e-mail notification works effectively.Left to run according to the schedule, and no e-mail notification isgenerated.Any assistance greatly appreciated.Thanks*** Sent via Developersdex http://www.developersdex.com ***
Here's the scoop, and I've seen several posts to this effect but none of the solutions have worked. Enabled database mail. confirmed profiles and can send test database mail from Query Window. I can also right click Database mail and send test emails. Configured valid operator using same email address for the test emails above. Enabled database mail profile under SQL Agent properties > Alert System.
From what I've seen, the test button is supposed to be greyed out, and it is. However alerts do not send emails operator.
I have sql 2000 sp4 running on a cluster, we had to fail over to other cluster, and now the sql agent choice to use a mail profile is grayed out. I can go to sql mail and test the profile and it works, but I can't change it for the sql agent? Anyone seen this before
I've just installed and configured outlook 2003 with sql agent mail and I've come across a strange conundrum: messages from agent mail are not actually sent unless the outlook client is open, but the default mail folder is locked by agent when agent is started, thus preventing outlook 2003 from opening. If I try things the other way - opening the client and then configuring/restarting agent mail - then agent mail can't access the default mail folder because the client has it locked.
There doesn't seem to be any way to win here.
Anyone come across this issue and found a workaround?
Using SQL 2005, SSIS, I have an SSIS package which is scheduled as a SQL Server Agent job. The package contains a Send Mail task. This task fails when SQL Agent runs the package. The task succeeds when executed interactively from the package, logged on as the SQL Agent service account. The package as a whole succeeds when executed from "Start Debugging". An Execute SQL Task in the same package containing an sp_send_dbmail statement succeeds when SQL Agent runs the job, and the same sp_send_dbmail succeeds in Mgmt Studio query window. All these events all logged onto the server as the SQL Server/SQL Agent service account.
I would appreciate ideas on what else to check for here, so that I can use the Send Mail SSIS task in packages which are run by SQL Agent jobs.
I have installed all the required installations for SQl Server CE, however when I open SQL Management Studio, the server type option is greyed out and I do not have the option to select SQL CE server type.
I have installed SQl Management Studio Express edition (if that helps.).
