Here is a sample of what I'm trying to do. The email that is sent is blank:

DECLARE @tableHTML NVARCHAR(MAX) ;

SET @tableHTML =

N'<H1>DB Growth</H1>' +

...

I'm fairly certain that it's the renaming of the tables that is causing the problems. The step to rename main table to staging took over 2 hours this morning....

An update.  The application support vendor simply needed to specify port 1433 as stated in the KB article mentioned in the beginning (Servername\instance, 1433).  All works well.  However, you are...

Repair has never been checked on this plan.  Some of the errors in my original post came from the system log and the cluster log.  That's about all I have...

It may not be the prettiest, but it works for me:

Sub Fulldatabasebackup

    strDBServerName = "."

    Set objSQLServer = CreateObject("SQLDMO.SQLServer")

    Set objDatabase = CreateObject("SQLDMO.Database")

    objSQLServer.LoginSecure = True

    objSQLServer.Connect strDBServerName

    Set...

Nevermind.  I've figured it out.

I see that in BOL now....thanks

The owner of the DTS package is from a non-trusted domain. When we created a new package it gave ownership of the package to an account with sysadmin..this is...

Thanks...there are some issues with AD and replication. We're going to remove AD for other reasons. I was able to get SQLServerAgent to start anyhow by using a...

I learned the hard way. Had to disable IIS before the SP could be applied. I was able to apply it the weekend of 4/5 after disabling IIS.

...

TShay, thanks but if you'll read back to my previous posts you'll notice that I've upgraded to 2.7SP1 and it still hasn't worked. Did you have any problems with...

Upgrading to mdac 2.7SP1 did not do the trick for me. Still getting the authentication message. The only thing left that I know of that could be causing...

What version of MDAC were you running prior to upgrading to SP3? I rebooted my machine prior to the install as well but that didn't fix my problem.

Everything in the KB article you mentioned checks out on the system ok. However, this KB article doesn't specifically state that upgrading to MDAC 2.7SP1 as a potential fix...

Does Microsoft have it documented to upgrade to MDAC 2.7SP1 and then run setup?