Sunday, March 25, 2012
Database Mirroring in SQL Server 2005
doc and have not had much success. I either get a message that a service is
not running or that the database mirror is busy. Has any had any luck with
this. If so please let me know the exact sequence of steps that I need to
follow.
Thanks
There's an extremely comprehensive article here
http://www.microsoft.com/technet/pro.../dbmirror.mspx
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Raji" <Raji@.discussions.microsoft.com> wrote in message
news:174EA9C2-9A9B-4123-A395-95E488A0B14C@.microsoft.com...
>I have been trying to setup a mirror database using the instructions in the
> doc and have not had much success. I either get a message that a service
> is
> not running or that the database mirror is busy. Has any had any luck with
> this. If so please let me know the exact sequence of steps that I need to
> follow.
> Thanks
>
Database Mirroring in SQL Server 2005
doc and have not had much success. I either get a message that a service is
not running or that the database mirror is busy. Has any had any luck with
this. If so please let me know the exact sequence of steps that I need to
follow.
ThanksThere's an extremely comprehensive article here
http://www.microsoft.com/technet/pr...5/dbmirror.mspx
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Raji" <Raji@.discussions.microsoft.com> wrote in message
news:174EA9C2-9A9B-4123-A395-95E488A0B14C@.microsoft.com...
>I have been trying to setup a mirror database using the instructions in the
> doc and have not had much success. I either get a message that a service
> is
> not running or that the database mirror is busy. Has any had any luck with
> this. If so please let me know the exact sequence of steps that I need to
> follow.
> Thanks
>
Database Mirroring in SQL Server 2005
doc and have not had much success. I either get a message that a service is
not running or that the database mirror is busy. Has any had any luck with
this. If so please let me know the exact sequence of steps that I need to
follow.
ThanksThere's an extremely comprehensive article here
http://www.microsoft.com/technet/prodtechnol/sql/2005/dbmirror.mspx
--
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Raji" <Raji@.discussions.microsoft.com> wrote in message
news:174EA9C2-9A9B-4123-A395-95E488A0B14C@.microsoft.com...
>I have been trying to setup a mirror database using the instructions in the
> doc and have not had much success. I either get a message that a service
> is
> not running or that the database mirror is busy. Has any had any luck with
> this. If so please let me know the exact sequence of steps that I need to
> follow.
> Thanks
>
Saturday, February 25, 2012
Database Mail is not working for me on 64 bit SQL 2005
has permissions to read the msdb system database?
"John D." <JohnD@.discussions.microsoft.com> wrote in message
news:28596E29-6110-4A44-806F-6E82C2A86983@.microsoft.com...
>I am trying to get Database mail working on our win 2003 EE 64 bit SQL 2005
> SP 1 EE 64bit server. I have done a ton of searching around other posts &
> have checked everything that people have said would work. Nothing has
> worked
> so far with me. The mail service is enabled, broker service is enabled &
> relay permission is allowed for the service. Here is the error message I
> am
> getting: Could not retrieve items from the queue. If I look at the
> queue,
> it does have several test messages in there waiting to be sent. Any ideas
> on
> what else I could try to get this to work?
> Thanks!
> John
>I am trying to get Database mail working on our win 2003 EE 64 bit SQL 2005
SP 1 EE 64bit server. I have done a ton of searching around other posts &
have checked everything that people have said would work. Nothing has worke
d
so far with me. The mail service is enabled, broker service is enabled &
relay permission is allowed for the service. Here is the error message I am
getting: Could not retrieve items from the queue. If I look at the queue,
it does have several test messages in there waiting to be sent. Any ideas o
n
what else I could try to get this to work?
Thanks!
John|||hmm..what login is the mail service running under? Are you sure that user
has permissions to read the msdb system database?
"John D." <JohnD@.discussions.microsoft.com> wrote in message
news:28596E29-6110-4A44-806F-6E82C2A86983@.microsoft.com...
>I am trying to get Database mail working on our win 2003 EE 64 bit SQL 2005
> SP 1 EE 64bit server. I have done a ton of searching around other posts &
> have checked everything that people have said would work. Nothing has
> worked
> so far with me. The mail service is enabled, broker service is enabled &
> relay permission is allowed for the service. Here is the error message I
> am
> getting: Could not retrieve items from the queue. If I look at the
> queue,
> it does have several test messages in there waiting to be sent. Any ideas
> on
> what else I could try to get this to work?
> Thanks!
> John
>|||Pardon my ignorance but how where do you set what login the mail service is
running under? Does it use the login that SQL Agent is running under? I
enabled it in the surface area configuration tool.
"Tim Greenwood" wrote:
> hmm..what login is the mail service running under? Are you sure that user
> has permissions to read the msdb system database?
>
> "John D." <JohnD@.discussions.microsoft.com> wrote in message
> news:28596E29-6110-4A44-806F-6E82C2A86983@.microsoft.com...
>
>|||Pardon my ignorance but how where do you set what login the mail service is
running under? Does it use the login that SQL Agent is running under? I
enabled it in the surface area configuration tool.
"Tim Greenwood" wrote:
> hmm..what login is the mail service running under? Are you sure that user
> has permissions to read the msdb system database?
>
> "John D." <JohnD@.discussions.microsoft.com> wrote in message
> news:28596E29-6110-4A44-806F-6E82C2A86983@.microsoft.com...
>
>
Friday, February 24, 2012
Database mail does not work from Sql Server Agent Job after upgrade to SP1
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 had the exact same problem with the same error on 2005. To fix it, I did the following:
1. Went into object-explorer, right-clicked on the SQL Server Agent, and selected properties. Then went to the Alert System page, and enabled the mail profile for the server agent. (you may already have this).
2. Then, went to "Database mail", right-clicked and selected "Configure Database mail." Selected "Manage profile security" and made sure my profile was set to public. THEN, and this is the kicker, clicked on the "Default Profile" field and set it to "yes".
|||I am still having issues after working through all these steps. Any other suggestions.
In general I seem to be having a lot of issues with the 64 Bit on 2005.
|||I'm having the exact same issue.
I have SQL Server Standard Edition 2005 (SP1) running and the Database Mail is not working correctly. I get a message in the SQL Agent log saying:
"SQLServer Error: 2812, Could not find stored procedure msdb.dbo.xp_sqlagent_notify"
Any solutions to this? What is this stored procedure? I can't find any documentation on it on Microsoft's site or anywhere for that matter.
|||I just started working on the mail on my test server and I have the same problem.
I have followed the instruction above to no avail. I have set up a job, when it completes it is to email me. I have set up mail and have been able to send a test mail by right clicking the db mail and selecting send test mail. I have se my self up as an operator. I have enabled db mail. The only thing I find odd is when I go to SQL server agent and select properties then select alert system the test button is grayed out.
|||Ok I found another test I could run to see if I have it configured correctly.
EXEC msdb.dbo.sp_send_dbmail
@.recipients=N'User@.Place.com',
@.subject=N'just another mail test.',
@.body=N'just another mail test.',
@.profile_name = 'EMail';
When I run this I get the response that the mail is queued. Shortly there after I get the mail. In my case there must be an issue between the jobs and the operator.
|||Ok it looks like I might have solve it for my self. Follow this link
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=322173&SiteID=1
Database mail does not work from Sql Server Agent Job after upgrade to SP1
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 had the exact same problem with the same error on 2005. To fix it, I did the following:
1. Went into object-explorer, right-clicked on the SQL Server Agent, and selected properties. Then went to the Alert System page, and enabled the mail profile for the server agent. (you may already have this).
2. Then, went to "Database mail", right-clicked and selected "Configure Database mail." Selected "Manage profile security" and made sure my profile was set to public. THEN, and this is the kicker, clicked on the "Default Profile" field and set it to "yes".
|||I am still having issues after working through all these steps. Any other suggestions.
In general I seem to be having a lot of issues with the 64 Bit on 2005.
|||
I'm having the exact same issue.
I have SQL Server Standard Edition 2005 (SP1) running and the Database Mail is not working correctly. I get a message in the SQL Agent log saying:
"SQLServer Error: 2812, Could not find stored procedure msdb.dbo.xp_sqlagent_notify"
Any solutions to this? What is this stored procedure? I can't find any documentation on it on Microsoft's site or anywhere for that matter.
|||I just started working on the mail on my test server and I have the same problem.
I have followed the instruction above to no avail. I have set up a job, when it completes it is to email me. I have set up mail and have been able to send a test mail by right clicking the db mail and selecting send test mail. I have se my self up as an operator. I have enabled db mail. The only thing I find odd is when I go to SQL server agent and select properties then select alert system the test button is grayed out.
|||Ok I found another test I could run to see if I have it configured correctly.
EXEC msdb.dbo.sp_send_dbmail
@.recipients=N'User@.Place.com',
@.subject=N'just another mail test.',
@.body=N'just another mail test.',
@.profile_name = 'EMail';
When I run this I get the response that the mail is queued. Shortly there after I get the mail. In my case there must be an issue between the jobs and the operator.
|||Ok it looks like I might have solve it for my self. Follow this link
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=322173&SiteID=1
Database Mail does not work from SQL Agent Job
Receiving Message:
[264] An attempt was made to send an email when no email session has been established
Just installed Service pack 1 and that did not help.
http://blogs.msdn.com/gopsdwarak/archive/2006/04/25/583434.aspx
Take a look at the above blog and this should address the problem you are running into.
Thanks,
Gops Dwarak
|||I have already read that blog before posting this problem. This is why I upgraded my Server to Service Pack 1. It appears to me that they did not in fact fix this in the 64-bit version unless I am doing something wrong that I am not aware of.
I 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?
|||We could not repro in our labs.
Did you restart SQL Server Agent after setting/changing the profile ?
Thanks,
Gops Dwarak
|||I got the same error after running a script (inherited from our DBA) that calls
sp_MSupdate_agenttype_default
several times with @.profile_id values in
(1, 2, 4, 6, 11).
Maybe, it helps to narrow down the problem
|||We are having the exact same problem and restarting the SQL Server Agent did not help.
We run SP1 on x86. We get both the "[264] An attempt was m..." error and the "2812, Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'...." error. Send test email works.
|||Did you perform the following 3 steps when setting up your database mail?
1. Enable database mail, create a new profile and mail account
2. Right click SQL Agent>Properties>Alerts System>Enable Mail Profile
3. Expand SQL Agent>Operators>Create New Operator
I got hung up a few times on this myself because I kept forgetting to do step 2, and I had the same exact error message you do. Once I did step 2, everything was resolved.
|||
Thank you for your reply.
Unfortunately, I have already done those three steps, and still have the same problem
|||After doing the 3 steps you need to restart the agent. That fixed the problem for me - ManmeetDatabase Mail does not work from SQL Agent Job
Receiving Message:
[264] An attempt was made to send an email when no email session has been established
Just installed Service pack 1 and that did not help.
http://blogs.msdn.com/gopsdwarak/archive/2006/04/25/583434.aspx
Take a look at the above blog and this should address the problem you are running into.
Thanks,
Gops Dwarak
|||I have already read that blog before posting this problem. This is why I upgraded my Server to Service Pack 1. It appears to me that they did not in fact fix this in the 64-bit version unless I am doing something wrong that I am not aware of.
I 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?
|||We could not repro in our labs.
Did you restart SQL Server Agent after setting/changing the profile ?
Thanks,
Gops Dwarak
|||I got the same error after running a script (inherited from our DBA) that calls
sp_MSupdate_agenttype_default
several times with @.profile_id values in
(1, 2, 4, 6, 11).
Maybe, it helps to narrow down the problem
|||We are having the exact same problem and restarting the SQL Server Agent did not help.
We run SP1 on x86. We get both the "[264] An attempt was m..." error and the "2812, Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'...." error. Send test email works.
|||Did you perform the following 3 steps when setting up your database mail?
1. Enable database mail, create a new profile and mail account
2. Right click SQL Agent>Properties>Alerts System>Enable Mail Profile
3. Expand SQL Agent>Operators>Create New Operator
I got hung up a few times on this myself because I kept forgetting to do step 2, and I had the same exact error message you do. Once I did step 2, everything was resolved.
|||
Thank you for your reply.
Unfortunately, I have already done those three steps, and still have the same problem
|||After doing the 3 steps you need to restart the agent. That fixed the problem for me - ManmeetDatabase Mail does not work from SQL Agent Job
Receiving Message:
[264] An attempt was made to send an email when no email session has been established
Just installed Service pack 1 and that did not help.
http://blogs.msdn.com/gopsdwarak/archive/2006/04/25/583434.aspx
Take a look at the above blog and this should address the problem you are running into.
Thanks,
Gops Dwarak
|||
I have already read that blog before posting this problem. This is why I upgraded my Server to Service Pack 1. It appears to me that they did not in fact fix this in the 64-bit version unless I am doing something wrong that I am not aware of.
I 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?
|||We could not repro in our labs.
Did you restart SQL Server Agent after setting/changing the profile ?
Thanks,
Gops Dwarak
|||
I got the same error after running a script (inherited from our DBA) that calls
sp_MSupdate_agenttype_default
several times with @.profile_id values in
(1, 2, 4, 6, 11).
Maybe, it helps to narrow down the problem
|||We are having the exact same problem and restarting the SQL Server Agent did not help.
We run SP1 on x86. We get both the "[264] An attempt was m..." error and the "2812, Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'...." error. Send test email works.
|||Did you perform the following 3 steps when setting up your database mail?
1. Enable database mail, create a new profile and mail account
2. Right click SQL Agent>Properties>Alerts System>Enable Mail Profile
3. Expand SQL Agent>Operators>Create New Operator
I got hung up a few times on this myself because I kept forgetting to do step 2, and I had the same exact error message you do. Once I did step 2, everything was resolved.
|||
Thank you for your reply.
Unfortunately, I have already done those three steps, and still have the same problem
|||After doing the 3 steps you need to restart the agent. That fixed the problem for me - ManmeetDatabase Mail does not work from SQL Agent Job
Receiving Message:
[264] An attempt was made to send an email when no email session has been established
Just installed Service pack 1 and that did not help.
http://blogs.msdn.com/gopsdwarak/archive/2006/04/25/583434.aspx
Take a look at the above blog and this should address the problem you are running into.
Thanks,
Gops Dwarak
|||
I have already read that blog before posting this problem. This is why I upgraded my Server to Service Pack 1. It appears to me that they did not in fact fix this in the 64-bit version unless I am doing something wrong that I am not aware of.
I 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?
|||We could not repro in our labs.
Did you restart SQL Server Agent after setting/changing the profile ?
Thanks,
Gops Dwarak
|||
I got the same error after running a script (inherited from our DBA) that calls
sp_MSupdate_agenttype_default
several times with @.profile_id values in
(1, 2, 4, 6, 11).
Maybe, it helps to narrow down the problem
|||We are having the exact same problem and restarting the SQL Server Agent did not help.
We run SP1 on x86. We get both the "[264] An attempt was m..." error and the "2812, Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'...." error. Send test email works.
|||Did you perform the following 3 steps when setting up your database mail?
1. Enable database mail, create a new profile and mail account
2. Right click SQL Agent>Properties>Alerts System>Enable Mail Profile
3. Expand SQL Agent>Operators>Create New Operator
I got hung up a few times on this myself because I kept forgetting to do step 2, and I had the same exact error message you do. Once I did step 2, everything was resolved.
|||
Thank you for your reply.
Unfortunately, I have already done those three steps, and still have the same problem
|||After doing the 3 steps you need to restart the agent. That fixed the problem for me - ManmeetDatabase Mail Confusion
the MS Book SQL 2005 Implementation and Maintenance Training Kit, on page 63,
Chapter 2 Lesson tool it states â'The default Database Mail host database is
msdb, and Service Broker is enabled on msdb by default.â'.
However when I use, SQL Server Surface Area Configuration, Surface Area
Configuration for Features, and click Service Broker, it states â'This
instance does not have a Service Broker endpoint.â'
The Database Mail has been configured. However, it is not sending e-mail
nor returning any error messages in the Database Mail Logs.
I set up the mail using Lesson 2 from the book, step by step. After it
didnâ't work, I worked thru the Troubleshooting on-line help. So,
1. should there be a service broker endpoint setup somewhere
2. any suggestions to what I do next?
ThanksPlease ignore...I had an e-mail rule for the sql service account that moved
the test e-mail out of my mail box.
"brymer28303" wrote:
> I am confused about the Service Broker and Database mail configuration. In
> the MS Book SQL 2005 Implementation and Maintenance Training Kit, on page 63,
> Chapter 2 Lesson tool it states â'The default Database Mail host database is
> msdb, and Service Broker is enabled on msdb by default.â'.
> However when I use, SQL Server Surface Area Configuration, Surface Area
> Configuration for Features, and click Service Broker, it states â'This
> instance does not have a Service Broker endpoint.â'
> The Database Mail has been configured. However, it is not sending e-mail
> nor returning any error messages in the Database Mail Logs.
> I set up the mail using Lesson 2 from the book, step by step. After it
> didnâ't work, I worked thru the Troubleshooting on-line help. So,
> 1. should there be a service broker endpoint setup somewhere
> 2. any suggestions to what I do next?
> Thanks
>
Database Mail Confusion
the MS Book SQL 2005 Implementation and Maintenance Training Kit, on page 63
,
Chapter 2 Lesson tool it states “The default Database Mail host database i
s
msdb, and Service Broker is enabled on msdb by default.”.
However when I use, SQL Server Surface Area Configuration, Surface Area
Configuration for Features, and click Service Broker, it states “This
instance does not have a Service Broker endpoint.”
The Database Mail has been configured. However, it is not sending e-mail
nor returning any error messages in the Database Mail Logs.
I set up the mail using Lesson 2 from the book, step by step. After it
didn’t work, I worked thru the Troubleshooting on-line help. So,
1. should there be a service broker endpoint setup somewhere
2. any suggestions to what I do next?
ThanksPlease ignore...I had an e-mail rule for the sql service account that moved
the test e-mail out of my mail box.
"brymer28303" wrote:
> I am confused about the Service Broker and Database mail configuration. I
n
> the MS Book SQL 2005 Implementation and Maintenance Training Kit, on page
63,
> Chapter 2 Lesson tool it states “The default Database Mail host database
is
> msdb, and Service Broker is enabled on msdb by default.”.
> However when I use, SQL Server Surface Area Configuration, Surface Area
> Configuration for Features, and click Service Broker, it states “This
> instance does not have a Service Broker endpoint.”
> The Database Mail has been configured. However, it is not sending e-mail
> nor returning any error messages in the Database Mail Logs.
> I set up the mail using Lesson 2 from the book, step by step. After it
> didn’t work, I worked thru the Troubleshooting on-line help. So,
> 1. should there be a service broker endpoint setup somewhere
> 2. any suggestions to what I do next?
> Thanks
>
Database Mail Confusion
the MS Book SQL 2005 Implementation and Maintenance Training Kit, on page 63,
Chapter 2 Lesson tool it states “The default Database Mail host database is
msdb, and Service Broker is enabled on msdb by default.”.
However when I use, SQL Server Surface Area Configuration, Surface Area
Configuration for Features, and click Service Broker, it states “This
instance does not have a Service Broker endpoint.”
The Database Mail has been configured. However, it is not sending e-mail
nor returning any error messages in the Database Mail Logs.
I set up the mail using Lesson 2 from the book, step by step. After it
didn’t work, I worked thru the Troubleshooting on-line help. So,
1.should there be a service broker endpoint setup somewhere
2.any suggestions to what I do next?
Thanks
Please ignore...I had an e-mail rule for the sql service account that moved
the test e-mail out of my mail box.
"brymer28303" wrote:
> I am confused about the Service Broker and Database mail configuration. In
> the MS Book SQL 2005 Implementation and Maintenance Training Kit, on page 63,
> Chapter 2 Lesson tool it states “The default Database Mail host database is
> msdb, and Service Broker is enabled on msdb by default.”.
> However when I use, SQL Server Surface Area Configuration, Surface Area
> Configuration for Features, and click Service Broker, it states “This
> instance does not have a Service Broker endpoint.”
> The Database Mail has been configured. However, it is not sending e-mail
> nor returning any error messages in the Database Mail Logs.
> I set up the mail using Lesson 2 from the book, step by step. After it
> didn’t work, I worked thru the Troubleshooting on-line help. So,
> 1.should there be a service broker endpoint setup somewhere
> 2.any suggestions to what I do next?
> Thanks
>
Friday, February 17, 2012
Database Logon Failed SSRS
Hi All,
My Report Server works find but after apply SQL Server 2005 Service Pack2. I can't connect to ReportServer Database. When Trying to connect from SQL Server Management Studio i get following Page.
TITLE: Connect to Server
Cannot connect to VISTA.
ADDITIONAL INFORMATION:
Client found response content type of 'text/html; charset=utf-8', but expected 'text/xml'.
The request failed with the error message:
--
<html>
<head>
<title>
SQL Server Reporting Services
</title><meta name="Generator" content="Microsoft SQL Server Reporting Services 9.00.3054.00" />
<meta name="HTTP Status" content="500" />
<meta name="ProductLocaleID" content="9" />
<meta name="CountryLocaleID" content="1033" />
<style>
BODY {FONT-FAMILY:Verdana; FONT-WEIGHT:normal; FONT-SIZE: 8pt; COLOR:black}
H1 {FONT-FAMILY:Verdana; FONT-WEIGHT:700; FONT-SIZE:15pt}
LI {FONT-FAMILY:Verdana; FONT-WEIGHT:normal; FONT-SIZE:8pt; DISPLAY:inline}
.ProductInfo {FONT-FAMILY:Verdana; FONT-WEIGHT:bold; FONT-SIZE: 8pt; COLOR:gray}
A:link {FONT-SIZE: 8pt; FONT-FAMILY:Verdana; COLOR
3366CC; TEXT-DECORATION:none}
A:hover {FONT-SIZE: 8pt; FONT-FAMILY:Verdana; COLOR
FF3300; TEXT-DECORATION:underline}
A:visited {FONT-SIZE: 8pt; FONT-FAMILY:Verdana; COLOR
3366CC; TEXT-DECORATION:none}
A:visited:hover {FONT-SIZE: 8pt; FONT-FAMILY:Verdana; color
FF3300; TEXT-DECORATION:underline}
</style>
</head><body bgcolor="white">
<h1>
Reporting Services Error<hr width="100%" size="1" color="silver" />
</h1><ul>
<li>The report server cannot open a connection to the report server database. The logon failed. (rsReportServerDatabaseLogonFailed) <a href="http://go.microsoft.com/fwlink/?LinkId=20476&EvtSrc=Microsoft.ReportingServices.Diagnostics.Utilities.ErrorStrings&EvtID=rsReportServerDatabaseLogonFailed&ProdName=Microsoft%20SQL%20Server%20Reporting%20Services&ProdVer=9.00.3054.00" target="_blank">Get Online Help</a></li><ul>
<li>For more information about this error navigate to the report server on the local server machine, or enable remote errors</li>
</ul><hr width="100%" size="1" color="silver" /><span class="ProductInfo">SQL Server Reporting Services</span>
</ul>
</body>
--. (Microsoft.SqlServer.Management.UI.RSClient)
BUTTONS:
OK
Colud anyone help me to resolve this issue please?
Thank you very much.
Regards,
Balwant Patel
Try using the Reporting Services Configuration Utility (Database tab) to generate a database script and apply this script manually to your ReportServer database.|||Did you just put on SP2? I had the same error very shortly after I put either SP2 or a hotfix (can't remember which), and it was fixed after a complete system restart and hasn't returned.
|||Make sure that the Service Accoutn the Reporting Server is running under has appropiate permissions to access the Report Server Database.Jens K. Suessmeyer.
http://www.sqlserver2005.de
|||
Hi Teo,
Thank you very much for your response... I tried with Database script but it doesn't work.
Regards,
Balwant Patel.
|||Hi gnieboer,
Thank you very much for response...I also restarted my system after apply SQL Server 2005 SP2 but I can't get rid of the problem.
Regards,
Balwant Patel
|||Hi Suessmeyer,
I check permission on Report Server Database...It is fine
Regards,
Balwant Patel
|||Which account has been granted access to the Report Server database, the ReportService Account (Windows Service) or the ASP_Net Worker process ?
Jens K. Suessmeyer.
http://www.sqlserver2005.de
|||Hi suessmeyer,
I m using Windows Service Account
Regards,
Balwant Patel
|||Make sure that the the ASPNET account is a member of the SQLServer2005ReportingServicesWebServiceUser$<computername> $MSSQLSERVER Windows group and NT Authority\System is a member of the SQLServer2005ReportServerUser$<computername>$MSSQLSERVER group.|||Hi Teo,
Yes, ASPNET Account & Authority\System are members of above groups...
I dont know what's the problem with it...
Regards,
Balwant Patel.