These links might be of assistance -

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=424890&SiteID=1

http://www.learnintegrationservices.com/VideoTutorials/SSIS-Video/1251/Pt-3-An-Overview-of-How-to-Execute-SSIS-Packages-With.aspx

Hi Alen - I've used PsExec to work around this issue in the past (http://www.microsoft.com/technet/sysinternals/utilities/psexec.mspx).

My apologies - seems as though the rest of my post was stripped out - possibly due to the XML tags.....

In the MsDtsSrvr.ini.xml file there is a tag called ServerName....

Good luck with IT 🙂

I've always used a query similar to the one below to check for job failures in the morning. You can get creative and throw this in...

When you save the package to the server; modify the protection level on the package to "Rely on server storage and roles for access control". This should do the trick.

I'm assuming you've already modified the following line in the MsDtsSrvr.ini.xml file on both nodes?

To start a named instance you will need -s parameter. i.e.

sqlservr.exe -f -s

If you still get an error, start in single user mode. i.e.

sqlservr.exe -m -s ...

Start MSSQL via the command line (sqlserv.exe) with the -f swith (minimal configuration mode) - more info in BOL. Then run an alter to move TempDB - i.e.

use master

go

ALTER DATABASE...

In MSSQL 2000 -

EXEC sp_dboption 'DatabaseName', 'single user', 'true'

GO

In MSSQL 2005 -

ALTER DATABASE [DatabaseName] SET SINGLE_USER WITH ROLLBACK IMMEDIATE

GO

ALTER DATABASE [DatabaseName] SET SINGLE_USER

GO

You could also use dynamic SQL - i.e.

declare @sql nvarchar(2000) , @dbname varchar(100)

set @dbname = 'master'

set @sql = '

select top 100 * from ' + @dbname + '.dbo.sysobjects with(nolock)'

EXEC sp_executesql...

Hi Emily,

Is there an FW between the MSSQL server and the SMTP relay? If this is the case, can you confirm w/ IT that TCP 25 is open between the...

Connect to the instance via Management Studio, right-click the server, select properties, permissions. If my memory serves me correctly you will need alter trace, and view server state.

The resources can always be added after the fact as well. But as you pointed out - hacking should be your last resort. You should be able to install a...

I'm not sure there is any easy way to go about this short of hacking the registry which could do more harm than good. I would suggest an alternative approach....

You can build your case w/ IT by confirming its an SMTP issue - i.e. RDP into the MSSQL server and attempt to send mail via telnet (http://www.amset.info/exchange/telnet-test.asp).