GETTING STARTED?

Hello All,
I have a SQL Server database up and running on my domain... I want that to
act as a replication server for my other 2 database servers... is there a
specific place anyone would recommend that I go.. to start this off on the
right foot.. in regards to LEARNING the way to set this up... and to get a
good understanding of how replication works.. including how to minimize
traffice and resource usage?
thanks..
I'd recommend Hilary's book (see my signature below), BOL and the (3-day)
Microsoft course 2591. These'll each give you the required foundation. Apart
from that, loads of practice scenarios on a test server. Probably everyone
else on this newsgroup has been through an (often difficult) learning
process with replication and will be willing to help, so post as many
questions as you can in this group about all things which seem unclear.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||THANKS!!
"Paul Ibison" wrote:

> I'd recommend Hilary's book (see my signature below), BOL and the (3-day)
> Microsoft course 2591. These'll each give you the required foundation. Apart
> from that, loads of practice scenarios on a test server. Probably everyone
> else on this newsgroup has been through an (often difficult) learning
> process with replication and will be willing to help, so post as many
> questions as you can in this group about all things which seem unclear.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
sql

Getting Started - What do I need to use SSIS?

OK. I am new to SSIS. I do not have control over the servers, so I have to provide a list of what features we need installed and such.

In order to use SSIS to import data files (from multiple flat file sources), what do I need installed?

I have SQL Server 2005 installed on a server. But the Business Intelligence Development Studio isn't present. Do I need to install that on the server? How about any services?

Also, can I/Should I install Business Intelligence Development Studio on my local development machine? What about licensing requirements for it?

Thank you for your help in this matter. Usually I have full control over the server and I can just poke through the install to get what I need.

Wow -- this is a big question, and you're going to get a lot of answers from different people.

The "Business Intelligence Development Studio" (BIDS) does not have to be installed on the server. The output from BIDS is a mangled XML file with a .DTSX extension. This file is processed by either the DTExec or DTExecui utility on the server. These utilities are installed along with SQL Server by default (in the Binn folder, I believe).

As a minimum, you'll need BIDS installed on your development machine. Because of licensing issues, DTExec and DTExecui only run on licensed servers. This means that, although you can create and run DTSX packages from your development machine from within BIDS, you won't be able to emulate server behavior on your local machine unless you've got a licensed copy of DTExec/DTExecui on your machine. IOW, you won't be able to run your packages at the Windows level without DTExec and DTExecui licensed on your development machine (this has hung up a lot of people -- the "insufficient product level" issue has been posted dozens of times on this forum)

Most of the SSIS tutorials you'll find on the Internet are laughably simplistic, and ignore real-world situations. You'll find dozens of brain-dead examples that import a well behaved 2- or 3-column flat file into an existing SQL Server table. While these examples are good for getting started, it'll take you 10 minutes of working with your own data to encounter a real-world situation such as permissions, ill-behaved data (missing delimiters, for instance), and issues with non-compliant data (such as column that look like dates, but aren't acceptable to SQL Server).

That's what this forum is all about. Lots of good help here.

|||

Thank you for the response. That answers a lot of my questions. I couldn't find anything that talked about getting started with this.

I'll go find the CD's to install BIDS locally. I think I can test everything well enough through BIDS before deploying to the server. This is also a new app, so we will have a full testing phase on the server to catch anything I miss.

I'll definately be back if I get stuck on writing the SSIS packages. I have 15+ file formats to massage all into the same table... :)

|||

That's precisely the sort of situation where the majority of examples you'll find will be of little help. Stuffing 15 or more formats into a single table will be challenging, depending on what you have to deal with.

Obviously, as with anything else, start with something you expect will be easy, such as plain text to a varchar or char column, and work up to the more challenging issues. In my case, I had some trouble with date values -- some of the columns I import are given as numbers (20070104), while others are text "01042007", and some include punctuation (01/03/2007 or 1-3-07). Cooercing these values into a format that's acceptable to SQL Server can be a challenge, sometimes.

Good luck! Jamie Thomsons blog (SSIS Junkie at http://blogs.conchango.com/jamiethomson/) is an invaluable source. By and large the support you'll get on this forum is top-notch and you shouldn't have too much trouble getting over the initial humps.

BTW: SSIS continues to surprise me an obvious paradox: while it's very powerful, it's got some of the quirkiest quirks I've ever seen in a Microsoft product. For instance, although the Script Task editor looks a lot like the standard Visual Studio editor, many of the menu commands do nothing -- you can't, for instance, "build" your script to check for errors. The only way I've found to validate my VB code is to actually run the package, or, at least, run the Script Task (right-click on a task in the Control Flow tab and select "Execute Task" from the shortcut menu) by itself to see if it's working.

Just a few of those "oh, so that's how it works" surprises now and then, but basically a good development platform. Much, much more powerful and flexible than DTS, to be sure.

sql

Getting rsOperationNotSupported when running report

I had started a project with SQL Server 2005 Express and quickly realized that it would not let me access DB's on other servers so I removed Express and Installed Workgroup Edition. When I try to run reports I still get "rsOperationNotSupported" when connecting to the remote database.

What gives? Do I need to move up to Std Edition for this?

In what way did SQL Server 2005 Express "not let you access DB's on other servers"? Have you tried setting up linked servers?

and even without that, what issues did you experience ... even if you are talking about "Mgmt Studio Express" or something rather than SQL Server Express? (I do this for most of my working day, and on one machine I definitely have SQL Server Express talking to many servers, on another I definitely have Mgmt Studio Express talking to many servers)

To answer your current question, though, ten to one the instance id for your new installation is incorrectly specified in the rs configuration somehow -- it's still pointing to the old instance.

>L<

|||

After talking to MS Support, was told that Workgroup Edidtion does not support remote data sources but Std Edition does. Will remove Workgroup and see if installing Std does the trick.

|||

Hey Tom, thanks in advance for clarifying this... is this something specific about *hosting RS* on each edition? Because I definitely access remote data from Express all the time -- I have never tried Workgroup. I must be doing something different from what you mean...

OTOH, it's true that I generally set up the remote sources as linked servers, and have one local SQL Server database "hosting" the calls for reports. This is because typically there are a lot of different datasources for each report, and I find it more convenient to have a local database caching some data, drawing other data live, but coordinating the whole thing without the reports' knowing where the data comes from.

Funny. I never would have realized that there were additional benefits re editions <s>.

>L<

|||

Found out what was going on. First SQL Server 2005 Std Edition is required if the datasource your accessing is on another server. Installed an instance of SQL Server 2005 Standard and everything worked (that is after I installed SP2).

On a related note for those insterested, I was also trying to get an instance of Reporting Services 2000 on a SQL Server 2000 Std Edition to work that I already had a license for on another server which was running Windows Server 2003. Reporting Services for SQL Server 2000 which apparently requires ASP 1.1. I had recently updated the server to run SharePoint Services v3 which requires ASP 2.0 or higher. Needless to say, they can't play together well. FYI.

Thanks to the feedback. I started me thinking in the right direction.

sql

Getting rsOperationNotSupported when running report

I had started a project with SQL Server 2005 Express and quickly realized that it would not let me access DB's on other servers so I removed Express and Installed Workgroup Edition. When I try to run reports I still get "rsOperationNotSupported" when connecting to the remote database.

What gives? Do I need to move up to Std Edition for this?

In what way did SQL Server 2005 Express "not let you access DB's on other servers"? Have you tried setting up linked servers?

and even without that, what issues did you experience ... even if you are talking about "Mgmt Studio Express" or something rather than SQL Server Express? (I do this for most of my working day, and on one machine I definitely have SQL Server Express talking to many servers, on another I definitely have Mgmt Studio Express talking to many servers)

To answer your current question, though, ten to one the instance id for your new installation is incorrectly specified in the rs configuration somehow -- it's still pointing to the old instance.

>L<

|||

After talking to MS Support, was told that Workgroup Edidtion does not support remote data sources but Std Edition does. Will remove Workgroup and see if installing Std does the trick.

|||

Hey Tom, thanks in advance for clarifying this... is this something specific about *hosting RS* on each edition? Because I definitely access remote data from Express all the time -- I have never tried Workgroup. I must be doing something different from what you mean...

OTOH, it's true that I generally set up the remote sources as linked servers, and have one local SQL Server database "hosting" the calls for reports. This is because typically there are a lot of different datasources for each report, and I find it more convenient to have a local database caching some data, drawing other data live, but coordinating the whole thing without the reports' knowing where the data comes from.

Funny. I never would have realized that there were additional benefits re editions <s>.

>L<

|||

Found out what was going on. First SQL Server 2005 Std Edition is required if the datasource your accessing is on another server. Installed an instance of SQL Server 2005 Standard and everything worked (that is after I installed SP2).

On a related note for those insterested, I was also trying to get an instance of Reporting Services 2000 on a SQL Server 2000 Std Edition to work that I already had a license for on another server which was running Windows Server 2003. Reporting Services for SQL Server 2000 which apparently requires ASP 1.1. I had recently updated the server to run SharePoint Services v3 which requires ASP 2.0 or higher. Needless to say, they can't play together well. FYI.

Thanks to the feedback. I started me thinking in the right direction.

Getting rsOperationNotSupported when running report

I had started a project with SQL Server 2005 Express and quickly realized that it would not let me access DB's on other servers so I removed Express and Installed Workgroup Edition. When I try to run reports I still get "rsOperationNotSupported" when connecting to the remote database.

What gives? Do I need to move up to Std Edition for this?

In what way did SQL Server 2005 Express "not let you access DB's on other servers"? Have you tried setting up linked servers?

and even without that, what issues did you experience ... even if you are talking about "Mgmt Studio Express" or something rather than SQL Server Express? (I do this for most of my working day, and on one machine I definitely have SQL Server Express talking to many servers, on another I definitely have Mgmt Studio Express talking to many servers)

To answer your current question, though, ten to one the instance id for your new installation is incorrectly specified in the rs configuration somehow -- it's still pointing to the old instance.

>L<

|||

After talking to MS Support, was told that Workgroup Edidtion does not support remote data sources but Std Edition does. Will remove Workgroup and see if installing Std does the trick.

|||

Hey Tom, thanks in advance for clarifying this... is this something specific about *hosting RS* on each edition? Because I definitely access remote data from Express all the time -- I have never tried Workgroup. I must be doing something different from what you mean...

OTOH, it's true that I generally set up the remote sources as linked servers, and have one local SQL Server database "hosting" the calls for reports. This is because typically there are a lot of different datasources for each report, and I find it more convenient to have a local database caching some data, drawing other data live, but coordinating the whole thing without the reports' knowing where the data comes from.

Funny. I never would have realized that there were additional benefits re editions <s>.

>L<

|||

Found out what was going on. First SQL Server 2005 Std Edition is required if the datasource your accessing is on another server. Installed an instance of SQL Server 2005 Standard and everything worked (that is after I installed SP2).

On a related note for those insterested, I was also trying to get an instance of Reporting Services 2000 on a SQL Server 2000 Std Edition to work that I already had a license for on another server which was running Windows Server 2003. Reporting Services for SQL Server 2000 which apparently requires ASP 1.1. I had recently updated the server to run SharePoint Services v3 which requires ASP 2.0 or higher. Needless to say, they can't play together well. FYI.

Thanks to the feedback. I started me thinking in the right direction.

Getting Msg 18456 in referencing a database from a linked server

Trying to use linked server for the first time and having some problems.
I have 2 servers "ServerA" and "ServerB". From ServerA I want to be able to
access data from ServerB. I ran the following on ServerA
USE master
GO
EXEC sp_addlinkedserver 'ServerB', N'SQL Server'
GO
Then I ran the following SQL on ServerA
SELECT * FROM SERVERB.DBNAME.dbo.TABLENAME
And I get the following message:
Server: Msg 18456, Level 14, State 1, Line 1
Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
Can someone tell me how I can get past this problem?
Thanks in advance!
What security type are you using?
Standard or Windows?
Your sp_addlinkedserver will default to use "current security credentials"
to authenticate to serverb.
You should try adding your linked server passing an SQL
authentication/Valid Windows account depending on your security type.
e.g. sp_addlinkedsrvlogin ServerB ,false ,null , SQLUSER, USERPASSWORD"
Immy
"TJTODD" <Thxomasx.Toddy@.Siemensx.com> wrote in message
news:ed748v7TEHA.3420@.TK2MSFTNGP09.phx.gbl...
> Trying to use linked server for the first time and having some problems.
> I have 2 servers "ServerA" and "ServerB". From ServerA I want to be
able to
> access data from ServerB. I ran the following on ServerA
> USE master
> GO
> EXEC sp_addlinkedserver 'ServerB', N'SQL Server'
> GO
> Then I ran the following SQL on ServerA
> SELECT * FROM SERVERB.DBNAME.dbo.TABLENAME
> And I get the following message:
> Server: Msg 18456, Level 14, State 1, Line 1
> Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
> Can someone tell me how I can get past this problem?
> Thanks in advance!
>
>
|||Thanks Immy...sp_addlinkedsrvlogin was exactly what I needed!
"Immy" <imtiaz_ullah@.hotmail.com> wrote in message
news:u8xksz7TEHA.1472@.TK2MSFTNGP12.phx.gbl...
> What security type are you using?
> Standard or Windows?
> Your sp_addlinkedserver will default to use "current security
credentials"[vbcol=seagreen]
> to authenticate to serverb.
> You should try adding your linked server passing an SQL
> authentication/Valid Windows account depending on your security type.
> e.g. sp_addlinkedsrvlogin ServerB ,false ,null , SQLUSER, USERPASSWORD"
> Immy
> "TJTODD" <Thxomasx.Toddy@.Siemensx.com> wrote in message
> news:ed748v7TEHA.3420@.TK2MSFTNGP09.phx.gbl...
problems.
> able to
>

Getting Msg 18456 in referencing a database from a linked server

Trying to use linked server for the first time and having some problems.
I have 2 servers "ServerA" and "ServerB". From ServerA I want to be able to
access data from ServerB. I ran the following on ServerA
USE master
GO
EXEC sp_addlinkedserver 'ServerB', N'SQL Server'
GO
Then I ran the following SQL on ServerA
SELECT * FROM SERVERB.DBNAME.dbo.TABLENAME
And I get the following message:
Server: Msg 18456, Level 14, State 1, Line 1
Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
Can someone tell me how I can get past this problem?
Thanks in advance!What security type are you using?
Standard or Windows?
Your sp_addlinkedserver will default to use "current security credentials"
to authenticate to serverb.
You should try adding your linked server passing an SQL
authentication/Valid Windows account depending on your security type.
e.g. sp_addlinkedsrvlogin ServerB ,false ,null , SQLUSER, USERPASSWORD"
Immy
"TJTODD" <Thxomasx.Toddy@.Siemensx.com> wrote in message
news:ed748v7TEHA.3420@.TK2MSFTNGP09.phx.gbl...
> Trying to use linked server for the first time and having some problems.
>
> I have 2 servers "ServerA" and "ServerB". From ServerA I want to be
able to
> access data from ServerB. I ran the following on ServerA
> USE master
> GO
> EXEC sp_addlinkedserver 'ServerB', N'SQL Server'
> GO
>
> Then I ran the following SQL on ServerA
> SELECT * FROM SERVERB.DBNAME.dbo.TABLENAME
>
> And I get the following message:
> Server: Msg 18456, Level 14, State 1, Line 1
> Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
>
> Can someone tell me how I can get past this problem?
>
> Thanks in advance!
>
>
>|||Thanks Immy...sp_addlinkedsrvlogin was exactly what I needed!
"Immy" <imtiaz_ullah@.hotmail.com> wrote in message
news:u8xksz7TEHA.1472@.TK2MSFTNGP12.phx.gbl...
> What security type are you using?
> Standard or Windows?
> Your sp_addlinkedserver will default to use "current security
credentials"
> to authenticate to serverb.
> You should try adding your linked server passing an SQL
> authentication/Valid Windows account depending on your security type.
> e.g. sp_addlinkedsrvlogin ServerB ,false ,null , SQLUSER, USERPASSWORD"
> Immy
> "TJTODD" <Thxomasx.Toddy@.Siemensx.com> wrote in message
> news:ed748v7TEHA.3420@.TK2MSFTNGP09.phx.gbl...
> > Trying to use linked server for the first time and having some
problems.
> >
> > I have 2 servers "ServerA" and "ServerB". From ServerA I want to be
> able to
> > access data from ServerB. I ran the following on ServerA
> > USE master
> > GO
> > EXEC sp_addlinkedserver 'ServerB', N'SQL Server'
> > GO
> >
> > Then I ran the following SQL on ServerA
> > SELECT * FROM SERVERB.DBNAME.dbo.TABLENAME
> >
> > And I get the following message:
> > Server: Msg 18456, Level 14, State 1, Line 1
> > Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
> >
> > Can someone tell me how I can get past this problem?
> >
> > Thanks in advance!
> >
> >
> >
>

Getting Msg 18456 in referencing a database from a linked server

Trying to use linked server for the first time and having some problems.
I have 2 servers "ServerA" and "ServerB". From ServerA I want to be able to
access data from ServerB. I ran the following on ServerA
USE master
GO
EXEC sp_addlinkedserver 'ServerB', N'SQL Server'
GO
Then I ran the following SQL on ServerA
SELECT * FROM SERVERB.DBNAME.dbo.TABLENAME
And I get the following message:
Server: Msg 18456, Level 14, State 1, Line 1
Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
Can someone tell me how I can get past this problem?
Thanks in advance!What security type are you using?
Standard or Windows?
Your sp_addlinkedserver will default to use "current security credentials"
to authenticate to serverb.
You should try adding your linked server passing an SQL
authentication/Valid Windows account depending on your security type.
e.g. sp_addlinkedsrvlogin ServerB ,false ,null , SQLUSER, USERPASSWORD"
Immy
"TJTODD" <Thxomasx.Toddy@.Siemensx.com> wrote in message
news:ed748v7TEHA.3420@.TK2MSFTNGP09.phx.gbl...
> Trying to use linked server for the first time and having some problems.
> I have 2 servers "ServerA" and "ServerB". From ServerA I want to be
able to
> access data from ServerB. I ran the following on ServerA
> USE master
> GO
> EXEC sp_addlinkedserver 'ServerB', N'SQL Server'
> GO
> Then I ran the following SQL on ServerA
> SELECT * FROM SERVERB.DBNAME.dbo.TABLENAME
> And I get the following message:
> Server: Msg 18456, Level 14, State 1, Line 1
> Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
> Can someone tell me how I can get past this problem?
> Thanks in advance!
>
>|||Thanks Immy...sp_addlinkedsrvlogin was exactly what I needed!
"Immy" <imtiaz_ullah@.hotmail.com> wrote in message
news:u8xksz7TEHA.1472@.TK2MSFTNGP12.phx.gbl...
> What security type are you using?
> Standard or Windows?
> Your sp_addlinkedserver will default to use "current security
credentials"
> to authenticate to serverb.
> You should try adding your linked server passing an SQL
> authentication/Valid Windows account depending on your security type.
> e.g. sp_addlinkedsrvlogin ServerB ,false ,null , SQLUSER, USERPASSWORD"
> Immy
> "TJTODD" <Thxomasx.Toddy@.Siemensx.com> wrote in message
> news:ed748v7TEHA.3420@.TK2MSFTNGP09.phx.gbl...
problems.[vbcol=seagreen]
> able to
>

Getting meta-data for Linked Servers

My customer has a .NET application that reads meta data from SQL Server, Oracle, DB2, and several propritary databases. Because each DBMS stores the meta data using various techniques, they have written custom code for each DBMS. They are working on a generic ODBC/OLEDB suppport, but in the interim I was trying to use SQL Server to link to an Access database. The Access linked server works fine for queries in Query Analyzer, but I would like to be able to programatically read the metadata for an Access DB (tables, columns, types, etc) via the linked server. SQL Server's usual mechanism for storing meta-data in the Master database aparently is not used for Linked Servers.

Does SQL Server expose Linked Server meta data?

How would one retrieve this meta data if it is exposed?

Thanks,

Ben

Hi Ben,

No SQL Server does not store metadata about linked servers (excluding connection information stored in sys.servers/sysservers). You would need to interrogate the actual linked server for this. So, if it were MSAccess, you would need to refer to the system tables (such as MSysObjects) etc.

Cheers,

Rob

|||

I was afraid that was the answer.

Thanks

Getting full security log

I'm administering serveral sqlserversin our company.
Most off the servers are in different domains. For the Enterprise Manager
that's no problem, you can register any server with it's ipnumber or name.
But on all the servers which are not in the same domain, it's security log
is getting full with the audit failure entry's.
How can I avoid this ? Is the enterprise manager doing something 'under
water' ?
Thanks in advance,
T. LeerIt could just be the polling of the servers from Enterprise
Manage so you can try turning that off. In Enterprise
Manager, go to the menu to Tools, select Options. On the
General Tab, remove the check for Server State Polling.
-Sue
On Tue, 19 Oct 2004 13:21:43 +0200, "Ton"
<t.leer@.wanadoo.nl> wrote:

>I'm administering serveral sqlserversin our company.
>Most off the servers are in different domains. For the Enterprise Manager
>that's no problem, you can register any server with it's ipnumber or name.
>But on all the servers which are not in the same domain, it's security log
>is getting full with the audit failure entry's.
>How can I avoid this ? Is the enterprise manager doing something 'under
>water' ?
>Thanks in advance,
>T. Leer
>

Getting full security log

I'm administering serveral sqlserversin our company.
Most off the servers are in different domains. For the Enterprise Manager
that's no problem, you can register any server with it's ipnumber or name.
But on all the servers which are not in the same domain, it's security log
is getting full with the audit failure entry's.
How can I avoid this ? Is the enterprise manager doing something 'under
water' ?
Thanks in advance,
T. Leer
It could just be the polling of the servers from Enterprise
Manage so you can try turning that off. In Enterprise
Manager, go to the menu to Tools, select Options. On the
General Tab, remove the check for Server State Polling.
-Sue
On Tue, 19 Oct 2004 13:21:43 +0200, "Ton"
<t.leer@.wanadoo.nl> wrote:

>I'm administering serveral sqlserversin our company.
>Most off the servers are in different domains. For the Enterprise Manager
>that's no problem, you can register any server with it's ipnumber or name.
>But on all the servers which are not in the same domain, it's security log
>is getting full with the audit failure entry's.
>How can I avoid this ? Is the enterprise manager doing something 'under
>water' ?
>Thanks in advance,
>T. Leer
>

Getting error "[311] Maildispatcher Thread (ID 1444) still running" when I try to restart

H
I am using SQLMail in my SQL Servers for the alert notifications. Today it has failed due to some reasons. I was trying to restart the SQLServerAgent , I got the error "[311] Maildispatcher Thread (ID 1444) still running"
It may be as the SQL Mail is conflicting with SQLServerAgent
Can you please tell me how to resolute this issue without restarting the MSSQLServer Services
Some forums say that, remove the mail profile from the SQLServerAgent Properties. This condition is true when the SQLServerAgent is running. But when it is stopped then there is no profile desplayed in the property box
Please help..
Thanks in advanc
DJ> I am using SQLMail in my SQL Servers for the alert notifications.
> Today it has failed due to some reasons. I was trying to restart
> the SQLServerAgent , I got the error "[311] Maildispatcher Thread
> (ID 1444) still running".
> It may be as the SQL Mail is conflicting with SQLServerAgent.
> Can you please tell me how to resolute this issue without
> restarting the MSSQLServer Services.
> Some forums say that, remove the mail profile from the
> SQLServerAgent Properties. This condition is true when the
> SQLServerAgent is running. But when it is stopped then there
> is no profile desplayed in the property box.
> Please help...
> Thanks in advance
> DJ
>
--
Hi DJ,
It looks like SQL Agent was abruptly stopped whilst SQL Mail was still
running. To get SQL Agent running, remove SQL mail profile by running the
following:
EXECUTE msdb.dbo.sp_set_sqlagent_properties @.email_profile = 'N'
Once you have SQL Agent started, add back the mail profile and then
troubleshoot the SQL Mail problem as you would normally do. This article
might help:
HOW TO: Troubleshoot SQL Mail with Microsoft Exchange Server
http://support.microsoft.com/?id=153159
Regards,
--
Eric Cárdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.