Replace the occurences of ABC\ in job script to XYZ\ and execute the script. It shldn't gv any errors now.

MJ

Is it updated with SP3. Check the upgrade matrix at http://msdn.microsoft.com/en-us/library/ms143393(SQL.90).aspx

MJ

Madhu,

It looks you have some job on source server which was owned by windows ID.

Please check tht by running :

select suser_sname(owner_sid)As JobOwner from sysjobs

where suser_sname(owner_sid)<>'sa'

and in the job script...

Try running it manually under management studio.

MJ

Did you tried logging job history to file option as someone suggested above?

MJ

Yep. I saw that this got fixed in SP1 Beta

as per

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

MJ

Whats the sql server version and edition?

Mj

It looks its

Annual Subscription, Support & Maintenance (Per Unit)-1200$

as per http://www.mysql.com/tcosavings

MJ

Check for any open transactions in it. If none then it might allow you to shrink the database.

MJ

Have you tried putting it in emergency mode? Do you have contents of sysdtspackages table with you?

MJ

Nope. It does tht in the background due to its nature.

MJ

Try this:

Change the filename of N'sysft_ftMYDB' :

MOVE N'sysft_ftMYDB' TO N'c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\MYDB_2_sysft_ftMYDB.mdf'

Give extension to the physical filename(mdf or ldf) based on type of file.

HTH,

MJ

As per

http://www.sqlservercentral.com/articles/SQL+Server+2005+-+Security/sqlserver2005logins/2474/

CHECK_EXPIRATION and CHECK_POLICY tell SQL Server to enforce the settings on password found in the computer's effective local security policy. Since Group Policy overrides the local security policy,...

Set the database file autogrowth in increments like 100 MB, 200 MB based on what is suitable and acceptable as per your server disk subystem.

MJ

Eric, have a look at new roles available for managing dts:

http://technet.microsoft.com/en-us/library/ms141053(SQL.90).aspx

HTH,

MJ