Database Mirroring Transport is disabled in the endpoint configuration.

Hi.

I am getting this error.

Msg 1486, Level 14, State 2, Line 2
Database Mirroring Transport is disabled in the endpoint configuration.

Someone please help me.It's urgent.

I am using same PC with 2 different intsances.

This is how i have done it:

CREATE MASTER KEY ENCRYPTION BY PASSWORD = 'test@.#56'

GO

-- CREATE CERTIFICATE PRINCIPAL_CERT

CREATE CERTIFICATE PRINCIPAL_CERT

WITH SUBJECT = 'PRINCIPAL CERTIFICATE',

START_DATE = '03/07/2006',

EXPIRY_DATE = '01/01/2010'

GO

-- CREATE ENDPOINT NAMED (EPMIRRORING) USING CERTIFICATE AND ALGORITHM

CREATE ENDPOINT EPMIRRORING

STATE = STARTED

AS TCP(LISTENER_PORT = 6025, LISTENER_IP = ALL)

FOR DATA_MIRRORING (ENCRYPTION = REQUIRED ALGORITHM RC4, ROLE = ALL,

AUTHENTICATION = CERTIFICATE PRINCIPAL_CERT)

GO

Here is the of Event Log.

Date,Source,Severity,Message
08/03/2006 15:54:35,spid52,Unknown,The Database Mirroring protocol transport is now listening for connections.
08/03/2006 15:54:35,spid52,Unknown,Server is listening on [ 'any' <ipv4> 5122].
08/03/2006 15:52:57,spid53,Unknown,The Database Mirroring protocol transport is disabled or not configured.
08/03/2006 15:52:55,spid53,Unknown,The Database Mirroring protocol transport has stopped listening for connections.
08/03/2006 14:14:54,spid52,Unknown,The Database Mirroring protocol transport is now listening for connections.
08/03/2006 14:14:54,spid52,Unknown,Server is listening on [ 'any' <ipv4> 5122].
08/03/2006 14:14:37,spid53,Unknown,The Database Mirroring protocol transport is disabled or not configured.
08/03/2006 14:14:35,spid53,Unknown,The Database Mirroring protocol transport has stopped listening for connections.
08/03/2006 14:03:48,Logon,Unknown,Database Mirroring login attempt failed with error: 'Connection handshake failed. There is no compatible authentication protocol. State 21.'. [CLIENT: 10.10.1.12]
08/03/2006 14:03:46,Logon,Unknown,Database Mirroring login attempt failed with error: 'Connection handshake failed. There is no compatible authentication protocol. State 21.'. [CLIENT: 10.10.1.12]
08/03/2006 14:03:43,Logon,Unknown,Database Mirroring login attempt failed with error: 'Connection handshake failed. There is no compatible authentication protocol. State 21.'. [CLIENT: 10.10.1.12]
08/03/2006 14:03:41,Logon,Unknown,Database Mirroring login attempt failed with error: 'Connection handshake failed. There is no compatible authentication protocol. State 21.'. [CLIENT: 10.10.1.12]
08/03/2006 14:03:38,Logon,Unknown,Database Mirroring login attempt failed with error: 'Connection handshake failed. There is no compatible authentication protocol. State 21.'. [CLIENT: 10.10.1.12]
08/03/2006 14:03:36,Logon,Unknown,Database Mirroring login attempt failed with error: 'Connection handshake failed. There is no compatible authentication protocol. State 21.'. [CLIENT: 10.10.1.12]
08/03/2006 14:03:34,Logon,Unknown,Database Mirroring login attempt failed with error: 'Connection handshake failed. There is no compatible authentication protocol. State 21.'. [CLIENT: 10.10.1.12]
08/03/2006 14:03:33,Logon,Unknown,Database Mirroring login attempt failed with error: 'Connection handshake failed. There is no compatible authentication protocol. State 21.'. [CLIENT: 10.10.1.12]
08/03/2006 14:03:32,Logon,Unknown,Database Mirroring login attempt failed with error: 'Connection handshake failed. There is no compatible authentication protocol. State 21.'. [CLIENT: 10.10.1.12]
08/03/2006 14:03:30,Logon,Unknown,Database Mirroring login attempt failed with error: 'Connection handshake failed. There is no compatible authentication protocol. State 21.'. [CLIENT: 10.10.1.12]
08/03/2006 14:03:15,spid54,Unknown,The Database Mirroring protocol transport is now listening for connections.
08/03/2006 14:03:15,spid54,Unknown,Server is listening on [ 'any' <ipv4> 5022].

Any solution ?
Thanks
Mihir

Are you using SQL Server 2005 RTM or SP1?|||I am having the same problem and I running sql server 2005 sp1|||

ascetic wrote:

08/03/2006 14:03:48,Logon,Unknown,Database Mirroring login attempt failed with error: 'Connection handshake failed. There is no compatible authentication protocol. State 21.'. [CLIENT: 10.10.1.12]

This indicates either that one host is configured to use CERTIFICATE authentication, the other is configured to use WINDOWS authentication, either one is configured to use WINDOWS KERBEROS and the other is using WINDOWS NTLM.

HTH,
~ Remus

|||I'm having this issue too, though mine says "State 22" at the end.

Remus, how would I know which the hosts are configured for and how can we change this? All of my servers are running as the same user in an AD domain so they should be able to talk fine?

thanks
Pete

Database Mirroring Transport is disabled in the endpoint configuration.

Hi.

I am getting this error.

Msg 1486, Level 14, State 2, Line 2
Database Mirroring Transport is disabled in the endpoint configuration.

Someone please help me.It's urgent.

I am using same PC with 2 different intsances.

This is how i have done it:

CREATE MASTER KEY ENCRYPTION BY PASSWORD = 'test@.#56'

GO

-- CREATE CERTIFICATE PRINCIPAL_CERT

CREATE CERTIFICATE PRINCIPAL_CERT

WITH SUBJECT = 'PRINCIPAL CERTIFICATE',

START_DATE = '03/07/2006',

EXPIRY_DATE = '01/01/2010'

GO

-- CREATE ENDPOINT NAMED (EPMIRRORING) USING CERTIFICATE AND ALGORITHM

CREATE ENDPOINT EPMIRRORING

STATE = STARTED

AS TCP(LISTENER_PORT = 6025, LISTENER_IP = ALL)

FOR DATA_MIRRORING (ENCRYPTION = REQUIRED ALGORITHM RC4, ROLE = ALL,

AUTHENTICATION = CERTIFICATE PRINCIPAL_CERT)

GO

Here is the of Event Log.

Date,Source,Severity,Message
08/03/2006 15:54:35,spid52,Unknown,The Database Mirroring protocol transport is now listening for connections.
08/03/2006 15:54:35,spid52,Unknown,Server is listening on [ 'any' <ipv4> 5122].
08/03/2006 15:52:57,spid53,Unknown,The Database Mirroring protocol transport is disabled or not configured.
08/03/2006 15:52:55,spid53,Unknown,The Database Mirroring protocol transport has stopped listening for connections.
08/03/2006 14:14:54,spid52,Unknown,The Database Mirroring protocol transport is now listening for connections.
08/03/2006 14:14:54,spid52,Unknown,Server is listening on [ 'any' <ipv4> 5122].
08/03/2006 14:14:37,spid53,Unknown,The Database Mirroring protocol transport is disabled or not configured.
08/03/2006 14:14:35,spid53,Unknown,The Database Mirroring protocol transport has stopped listening for connections.
08/03/2006 14:03:48,Logon,Unknown,Database Mirroring login attempt failed with error: 'Connection handshake failed. There is no compatible authentication protocol. State 21.'. [CLIENT: 10.10.1.12]
08/03/2006 14:03:46,Logon,Unknown,Database Mirroring login attempt failed with error: 'Connection handshake failed. There is no compatible authentication protocol. State 21.'. [CLIENT: 10.10.1.12]
08/03/2006 14:03:43,Logon,Unknown,Database Mirroring login attempt failed with error: 'Connection handshake failed. There is no compatible authentication protocol. State 21.'. [CLIENT: 10.10.1.12]
08/03/2006 14:03:41,Logon,Unknown,Database Mirroring login attempt failed with error: 'Connection handshake failed. There is no compatible authentication protocol. State 21.'. [CLIENT: 10.10.1.12]
08/03/2006 14:03:38,Logon,Unknown,Database Mirroring login attempt failed with error: 'Connection handshake failed. There is no compatible authentication protocol. State 21.'. [CLIENT: 10.10.1.12]
08/03/2006 14:03:36,Logon,Unknown,Database Mirroring login attempt failed with error: 'Connection handshake failed. There is no compatible authentication protocol. State 21.'. [CLIENT: 10.10.1.12]
08/03/2006 14:03:34,Logon,Unknown,Database Mirroring login attempt failed with error: 'Connection handshake failed. There is no compatible authentication protocol. State 21.'. [CLIENT: 10.10.1.12]
08/03/2006 14:03:33,Logon,Unknown,Database Mirroring login attempt failed with error: 'Connection handshake failed. There is no compatible authentication protocol. State 21.'. [CLIENT: 10.10.1.12]
08/03/2006 14:03:32,Logon,Unknown,Database Mirroring login attempt failed with error: 'Connection handshake failed. There is no compatible authentication protocol. State 21.'. [CLIENT: 10.10.1.12]
08/03/2006 14:03:30,Logon,Unknown,Database Mirroring login attempt failed with error: 'Connection handshake failed. There is no compatible authentication protocol. State 21.'. [CLIENT: 10.10.1.12]
08/03/2006 14:03:15,spid54,Unknown,The Database Mirroring protocol transport is now listening for connections.
08/03/2006 14:03:15,spid54,Unknown,Server is listening on [ 'any' <ipv4> 5022].

Any solution ?
Thanks
Mihir

Are you using SQL Server 2005 RTM or SP1?|||I am having the same problem and I running sql server 2005 sp1|||

ascetic wrote:

08/03/2006 14:03:48,Logon,Unknown,Database Mirroring login attempt failed with error: 'Connection handshake failed. There is no compatible authentication protocol. State 21.'. [CLIENT: 10.10.1.12]

This indicates either that one host is configured to use CERTIFICATE authentication, the other is configured to use WINDOWS authentication, either one is configured to use WINDOWS KERBEROS and the other is using WINDOWS NTLM.

HTH,
~ Remus

|||I'm having this issue too, though mine says "State 22" at the end.

Remus, how would I know which the hosts are configured for and how can we change this? All of my servers are running as the same user in an AD domain so they should be able to talk fine?

thanks
Pete
sql

Database Mirroring Monitor

Hi there!

I've some trouble with monitoring a database mirroring session. I am testing a lot configuration possiblities, and i use the database mirroring monitor to view the mirroring states.

But in some (most) of my configurations, i only get following informations in the database mirroring monitor:

Oldest unsend transaction, Unrestored Log, Current Restore rate and the Witness Adress. I am working in High safety mode with automatic failover.

Question 1: What are the reasons that all the other indicators (Unsend log, Current send rate, Mirror commit overhead) are not shown?

Question 2: In the moment, i am using certificates for the mirroring communication. I think, my client (who the database mirroring monitor is running) connects with the usual windows authentication to the server and only selects from sys.database_mirroring or something else. So there is no need to create inbound certificates on the partners for the client who is connecting with the mirroring monitor?

Torsten

1. The counters that you say you cannot see are ones that are specific to the principal. Make sure that your connection from the monitor to the principal is good.

2.OK, sounds a little strange. Looks like the certs are what is messing things up. So, the connection from the monitor into the partners should be SA to make everything run nicely. But if the conneciton cannot be SA, then the monitor can come in as a normal login and get the data as long as the login is a member of the DBM_Monitor security group in MSDB. Note: the job that updates the base table for monitoring must be running as well.

Thanks,

Mark

|||

Hi Mark,

1. The connection is good, all related users have logins on the principle, are member of the dbm_monitor group, and are in sysadmin group.

In my opinion its not a problem of the database mirroring monitor, because the main stored procedure doesn't even show the results:

sp_dbmmonitorresults 'EASYRIS_41', 0,1

--> EASYRIS_41 1 4 1 NULL NULL NULL NULL NULL NULL NULL NULL 2006-06-21 12:38:44.547 2006-06-21 12:38:44.547 2006-06-21 14:38:44.547

Furthermore i've recognized that the Database Mirroring Monitor Job is located on the MIRROR (thats because the mirror has been the principal when i set up the session). Should the job run on BOTH partners? Furthermore the job is runnning under 'sa'. sa is not member of dbm_monitor group, and i can not put him into the group.

What is the exact recommendation? Is there any documentation i've not seen?

Thanks and sorry for the extra work ;-)

Torsten

|||

yes, you must run the job on both servers. if the job is running under SA then that's fine.

The user that the monitor logs in as can be in the dbm_monitor group if you do not want it to be SA. If it is SA, then the monitor should be able to update the info anyway...

mark

Database Mail Confusion

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?
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

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 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

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
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
>

Database Mail Configuration? Very Urgent

Hi!!!!

I'm a hobbyist Developer....

I'm would like to know how to send mails from Database Mail option in SQL Server 2005. I wil be glad if i can get a step-by-step procedure or any KB....

Moreover what i did was,

i tried to setup the database and i got the error message when i tried to send DB mails....

"An attempt was made to send an email when no email session has been established"

wil be thankful if i get help ASAP.

Thanks,

Jeffrey

Hi all....Why am i not getting any help? Seems that not even a single expert is having a look at this question.....

Please help me ASAP.......

TIA

Jeffrey

|||

I'm no expert; but, did you set up your email configuration?

I've set up my account / configuration; but, I'm getting the following error:

The mail could not be sent to the recipients because of the mail server failure. (Sending Mail using Account 1 (2006-06-22T02:27:43). Exception Message: Cannot send mails to mail server. (The SMTP server requires a secure connection or the client was not authenticated. The server response was: authentication required - for help go to http://help.yahoo.com/help/us/sbc/dsl/mail/pop/pop-11.html). )

SBCGlobal (my ISP) says they don't support SQL Server 2005 DB Mail?

Anyone else have this problem?

|||

Hi Steve,

I'm getting the same message as you are - sure would like to know what it means!!

Dave

|||

I got hung up on this one too, and what I found was when I set up the mail account to send mail in SQL Server I had used the wrong name for the Account Name and Display Name. Many e-mail accounts have an "Alias" name to them and they may not be what the actual e-mail address looks like. So if your mail account address looks like SVCMail@.myISP.com, it may have an alias name of SVCSQLMail. It is critical that the alias name is right otherwise it won't work.

You can also try right clicking Database Mail/Send Test Message to see if the mail works at all. I have found that the mail does work quite often by using this method but then a job will fail to send mail if you try to set an alert for a job. That is pretty much how I discovered that if the Description and Alias name is wrong, it will fail to send mail under a job.

As far as the ISP not supporting SQL 2005 mail, it is probably not an issue because SQL 2005 just uses SMTP mail. There is also SQL Mail which uses the Outlook Client but that should not be an issue either as long as it is configured correctly.

Database Mail Configuration? Very Urgent

Hi!!!!

I'm a hobbyist Developer....

I'm would like to know how to send mails from Database Mail option in SQL Server 2005. I wil be glad if i can get a step-by-step procedure or any KB....

Moreover what i did was,

i tried to setup the database and i got the error message when i tried to send DB mails....

"An attempt was made to send an email when no email session has been established"

wil be thankful if i get help ASAP.

Thanks,

Jeffrey

Hi all....Why am i not getting any help? Seems that not even a single expert is having a look at this question.....

Please help me ASAP.......

TIA

Jeffrey

|||

I'm no expert; but, did you set up your email configuration?

I've set up my account / configuration; but, I'm getting the following error:

The mail could not be sent to the recipients because of the mail server failure. (Sending Mail using Account 1 (2006-06-22T02:27:43). Exception Message: Cannot send mails to mail server. (The SMTP server requires a secure connection or the client was not authenticated. The server response was: authentication required - for help go to http://help.yahoo.com/help/us/sbc/dsl/mail/pop/pop-11.html). )

SBCGlobal (my ISP) says they don't support SQL Server 2005 DB Mail?

Anyone else have this problem?

|||

Hi Steve,

I'm getting the same message as you are - sure would like to know what it means!!

Dave

|||

I got hung up on this one too, and what I found was when I set up the mail account to send mail in SQL Server I had used the wrong name for the Account Name and Display Name. Many e-mail accounts have an "Alias" name to them and they may not be what the actual e-mail address looks like. So if your mail account address looks like SVCMail@.myISP.com, it may have an alias name of SVCSQLMail. It is critical that the alias name is right otherwise it won't work.

You can also try right clicking Database Mail/Send Test Message to see if the mail works at all. I have found that the mail does work quite often by using this method but then a job will fail to send mail if you try to set an alert for a job. That is pretty much how I discovered that if the Description and Alias name is wrong, it will fail to send mail under a job.

As far as the ISP not supporting SQL 2005 mail, it is probably not an issue because SQL 2005 just uses SMTP mail. There is also SQL Mail which uses the Outlook Client but that should not be an issue either as long as it is configured correctly.

Database Mail Configuration? Very Urgent

Hi!!!!

I'm a hobbyist Developer....

I'm would like to know how to send mails from Database Mail option in SQL Server 2005. I wil be glad if i can get a step-by-step procedure or any KB....

Moreover what i did was,

i tried to setup the database and i got the error message when i tried to send DB mails....

"An attempt was made to send an email when no email session has been established"

wil be thankful if i get help ASAP.

Thanks,

Jeffrey

Hi all....Why am i not getting any help? Seems that not even a single expert is having a look at this question.....

Please help me ASAP.......

TIA

Jeffrey

|||

I'm no expert; but, did you set up your email configuration?

I've set up my account / configuration; but, I'm getting the following error:

The mail could not be sent to the recipients because of the mail server failure. (Sending Mail using Account 1 (2006-06-22T02:27:43). Exception Message: Cannot send mails to mail server. (The SMTP server requires a secure connection or the client was not authenticated. The server response was: authentication required - for help go to http://help.yahoo.com/help/us/sbc/dsl/mail/pop/pop-11.html). )

SBCGlobal (my ISP) says they don't support SQL Server 2005 DB Mail?

Anyone else have this problem?

|||

Hi Steve,

I'm getting the same message as you are - sure would like to know what it means!!

Dave

|||

I got hung up on this one too, and what I found was when I set up the mail account to send mail in SQL Server I had used the wrong name for the Account Name and Display Name. Many e-mail accounts have an "Alias" name to them and they may not be what the actual e-mail address looks like. So if your mail account address looks like SVCMail@.myISP.com, it may have an alias name of SVCSQLMail. It is critical that the alias name is right otherwise it won't work.

You can also try right clicking Database Mail/Send Test Message to see if the mail works at all. I have found that the mail does work quite often by using this method but then a job will fail to send mail if you try to set an alert for a job. That is pretty much how I discovered that if the Description and Alias name is wrong, it will fail to send mail under a job.

As far as the ISP not supporting SQL 2005 mail, it is probably not an issue because SQL 2005 just uses SMTP mail. There is also SQL Mail which uses the Outlook Client but that should not be an issue either as long as it is configured correctly.

Database mail configuration

I have configured database mail using the wizard, but when I try to send a test message I receive the following error:

The mail could not be sent to the recipients because of the mail server failure. (Sending Mail using Account 3 Exception Message: Cannot send mails to mail server. (Failure sending mail.)

Is there some more configuration I must do? I have enabled mail using the surface area configurator.

Thanks

I would try using xpsmtp mail and forget standard SQL mail...it is a pain in the rear. You can get it (yes it is free) here http://www.sqldev.net/xp/xpsmtp.htm

It is easy to set up and use and has teriffic documentation.

I know this is not an answer to your question but I hope this helps some.

Regards,

Brad Feaker
|||We are using SQL Server 2005 and its database mail option, not the old SQL mail that 7 and 2000 use.|||Sorry about that - I should have noticed your mention of the Surface Area Configurator. My bad! I don't have any experience setting up SQL Mail in 2005 yet. Hope you get an answer soon. No one seems to be able to answer my question either...Good luck!!!
|||

Hi Tim,

I had the same problem as yours and I solved it configuring the Relay options of my SMTP server.

HTH,

Database Mail

Dear Folks,
I am trying to finish my configuration of Database Mail on my sp1 build 2153 sql server. I believe to have set it up properly but i still can't get a test message through. My error message reads:

The mail could not be sent to the recipients because of the mail server failure. (Sending Mail using Account 3 (2006-08-09T15:14:00). Exception Message: Cannot send mails to mail server. (Transaction failed. The server response was: Mail from <account email address> rejected for policy reasons.). )

Everything that needs to be enabled, i.e. service broker, SQL Server Agent properties, deafult profile in msdb table, services restarted. Is this message a result of Sql server policy or the smtp server? Is there a process in the transaction Sql server initiates that could be causing the policy violation that i need to tell the email admin about?
Thanks for your reply.
-C
This turned out to be a DNS or relay issue. When i got the right IP address, it worked fine. I tried IP previously, the same message came back. The mail server is in another domain, which complicated the issue.

Database Log File

Hello there
i have a huge problem here our database .mdb file is 240 m.b
the log file is 20 g.b
so is there a missing configuration or a database problem
or what should i do to reduce the log file
Amir Fahmy
Hi Amir
Most likely you have the db set up with FULL recover mode and you do not
perform backup log file. Set the db with SIMPLE recovery mode and then
shrink the log.
"Amir Fahmy" <AmirFahmy@.discussions.microsoft.com> wrote in message
news:43248209-E33C-489A-AC88-D98EF4AABD84@.microsoft.com...
> Hello there
> i have a huge problem here our database .mdb file is 240 m.b
> the log file is 20 g.b
> so is there a missing configuration or a database problem
> or what should i do to reduce the log file
> Amir Fahmy
|||Hi David
I agree with you. I did give the answer as for solving the problem
immediatly as disk could run out of space. Then I should mention that he
needs to undestand those thing as you said.
"David Portas" <REMOVE_BEFORE_REPLYING_dportas@.acm.org> wrote in message
news:%23q1SVQvwHHA.484@.TK2MSFTNGP06.phx.gbl...
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:eIisJLvwHHA.4568@.TK2MSFTNGP03.phx.gbl...
> Hi Uri,
> What you have said is of course the most likely explanation. However, Amir
> should not attempt what you have suggested unless he understands the
> meaning of different recovery models, log backups and the impact on his
> ability to recover from a disaster. If he did understand those things then
> I suspect he wouldn't need to ask the question. So that's why I replied as
> I did rather than give a direct answer that won't necessarily be
> appropriate for every eventuality.
> --
> David Portas, SQL Server MVP
> Whenever possible please post enough code to reproduce your problem.
> Including CREATE TABLE and INSERT statements usually helps.
> State what version of SQL Server you are using and specify the content
> of any error messages.
> SQL Server Books Online:
> http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
> --
>

Database Log File

Hello there
i have a huge problem here our database .mdb file is 240 m.b
the log file is 20 g.b
so is there a missing configuration or a database problem
or what should i do to reduce the log file
Amir FahmyHi Amir
Most likely you have the db set up with FULL recover mode and you do not
perform backup log file. Set the db with SIMPLE recovery mode and then
shrink the log.
"Amir Fahmy" <AmirFahmy@.discussions.microsoft.com> wrote in message
news:43248209-E33C-489A-AC88-D98EF4AABD84@.microsoft.com...
> Hello there
> i have a huge problem here our database .mdb file is 240 m.b
> the log file is 20 g.b
> so is there a missing configuration or a database problem
> or what should i do to reduce the log file
> Amir Fahmy|||"Amir Fahmy" <AmirFahmy@.discussions.microsoft.com> wrote in message
news:43248209-E33C-489A-AC88-D98EF4AABD84@.microsoft.com...
> Hello there
> i have a huge problem here our database .mdb file is 240 m.b
> the log file is 20 g.b
> so is there a missing configuration or a database problem
> or what should i do to reduce the log file
> Amir Fahmy
When did you last backup the log? What recovery model are you using?
If you don't understand log backup and recovery then lookup those topics in
Books Online.
--
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
--|||"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:eIisJLvwHHA.4568@.TK2MSFTNGP03.phx.gbl...
> Hi Amir
> Most likely you have the db set up with FULL recover mode and you do not
> perform backup log file. Set the db with SIMPLE recovery mode and then
> shrink the log.
>
Hi Uri,
What you have said is of course the most likely explanation. However, Amir
should not attempt what you have suggested unless he understands the meaning
of different recovery models, log backups and the impact on his ability to
recover from a disaster. If he did understand those things then I suspect he
wouldn't need to ask the question. So that's why I replied as I did rather
than give a direct answer that won't necessarily be appropriate for every
eventuality.
--
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
--|||Hi David
I agree with you. I did give the answer as for solving the problem
immediatly as disk could run out of space. Then I should mention that he
needs to undestand those thing as you said.
"David Portas" <REMOVE_BEFORE_REPLYING_dportas@.acm.org> wrote in message
news:%23q1SVQvwHHA.484@.TK2MSFTNGP06.phx.gbl...
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:eIisJLvwHHA.4568@.TK2MSFTNGP03.phx.gbl...
>> Hi Amir
>> Most likely you have the db set up with FULL recover mode and you do not
>> perform backup log file. Set the db with SIMPLE recovery mode and then
>> shrink the log.
> Hi Uri,
> What you have said is of course the most likely explanation. However, Amir
> should not attempt what you have suggested unless he understands the
> meaning of different recovery models, log backups and the impact on his
> ability to recover from a disaster. If he did understand those things then
> I suspect he wouldn't need to ask the question. So that's why I replied as
> I did rather than give a direct answer that won't necessarily be
> appropriate for every eventuality.
> --
> David Portas, SQL Server MVP
> Whenever possible please post enough code to reproduce your problem.
> Including CREATE TABLE and INSERT statements usually helps.
> State what version of SQL Server you are using and specify the content
> of any error messages.
> SQL Server Books Online:
> http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
> --
>

Database Log File

Hello there
i have a huge problem here our database .mdb file is 240 m.b
the log file is 20 g.b
so is there a missing configuration or a database problem
or what should i do to reduce the log file
Amir FahmyHi Amir
Most likely you have the db set up with FULL recover mode and you do not
perform backup log file. Set the db with SIMPLE recovery mode and then
shrink the log.
"Amir Fahmy" <AmirFahmy@.discussions.microsoft.com> wrote in message
news:43248209-E33C-489A-AC88-D98EF4AABD84@.microsoft.com...
> Hello there
> i have a huge problem here our database .mdb file is 240 m.b
> the log file is 20 g.b
> so is there a missing configuration or a database problem
> or what should i do to reduce the log file
> Amir Fahmy|||"Amir Fahmy" <AmirFahmy@.discussions.microsoft.com> wrote in message
news:43248209-E33C-489A-AC88-D98EF4AABD84@.microsoft.com...
> Hello there
> i have a huge problem here our database .mdb file is 240 m.b
> the log file is 20 g.b
> so is there a missing configuration or a database problem
> or what should i do to reduce the log file
> Amir Fahmy
When did you last backup the log? What recovery model are you using?
If you don't understand log backup and recovery then lookup those topics in
Books Online.
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
--|||"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:eIisJLvwHHA.4568@.TK2MSFTNGP03.phx.gbl...
> Hi Amir
> Most likely you have the db set up with FULL recover mode and you do not
> perform backup log file. Set the db with SIMPLE recovery mode and then
> shrink the log.
>
Hi Uri,
What you have said is of course the most likely explanation. However, Amir
should not attempt what you have suggested unless he understands the meaning
of different recovery models, log backups and the impact on his ability to
recover from a disaster. If he did understand those things then I suspect he
wouldn't need to ask the question. So that's why I replied as I did rather
than give a direct answer that won't necessarily be appropriate for every
eventuality.
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
--|||Hi David
I agree with you. I did give the answer as for solving the problem
immediatly as disk could run out of space. Then I should mention that he
needs to undestand those thing as you said.
"David Portas" <REMOVE_BEFORE_REPLYING_dportas@.acm.org> wrote in message
news:%23q1SVQvwHHA.484@.TK2MSFTNGP06.phx.gbl...
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:eIisJLvwHHA.4568@.TK2MSFTNGP03.phx.gbl...
> Hi Uri,
> What you have said is of course the most likely explanation. However, Amir
> should not attempt what you have suggested unless he understands the
> meaning of different recovery models, log backups and the impact on his
> ability to recover from a disaster. If he did understand those things then
> I suspect he wouldn't need to ask the question. So that's why I replied as
> I did rather than give a direct answer that won't necessarily be
> appropriate for every eventuality.
> --
> David Portas, SQL Server MVP
> Whenever possible please post enough code to reproduce your problem.
> Including CREATE TABLE and INSERT statements usually helps.
> State what version of SQL Server you are using and specify the content
> of any error messages.
> SQL Server Books Online:
> http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
> --
>

Database list comes slow, what tod o?

Hey there,

a question about my configuration.
We have a sql server 7, where all our database are. If i use enterprise manager from sql server 7, I get no problems with downloading the list of the db's. But when I connect with the EM of sql server 2000, it takes about 10 minutes to get the list. I got that with win2000 and with winXp.
My college doesn't has that problem.
Does anyone has a sollution for it?
Or is it better to use the EM 70?
ThanksHi,
Here it is in fact slow due to several reasons and one of these reasons could be the problem. Generally, and most of the time the low speed in the system could be caused by the small capacity on your hard disk drive and the small capacity of the memory. The more space you have the faster database you have as you know. I had the same problem one month back whenever select a large view table it takes long time to inquire about its fields. The server we have was running out of space and getting all the time with memory loading. A week ago we purchased a new server big performance and now I face no problem from this point of view, this could be one of the reasons.
There is another reason but I have no idea if this is applied on your case or not!! it is known that whenever migrating from SQL7 to SQL 2K SERVER we have to update the compatibility level by executing the following command EXEC sp_dbcmptlevel <your dbname>,80

I wish ya good luck.

Alzebdeh

Originally posted by Nux
Hey there,

a question about my configuration.
We have a sql server 7, where all our database are. If i use enterprise manager from sql server 7, I get no problems with downloading the list of the db's. But when I connect with the EM of sql server 2000, it takes about 10 minutes to get the list. I got that with win2000 and with winXp.
My college doesn't has that problem.
Does anyone has a sollution for it?
Or is it better to use the EM 70?
Thanks