File = 1 indicates that you want to restore the first backup set in the backup file.  This is used if you store multiple backup sets in the same file. ...

Graham,

Have you considered leaving the dev and test databases in place and just refreshing the data using DTS?  You wouldn't have to worry about changing the owner.

Greg 

You may find that you won't need to shrink the t-log if you back it up more frequently.

Greg

Hi Kevin,

There isn't a way to automatically set a database owner when a database is created.  You'd either have to be connected as the login that you want to be...

While I don't have any experience with ArcServe for SQL Server (we use native backups), it's generally a good idea to schedule log backups as often as needed.  We backup...

Jeff,

Execute sp_enum_dtspackages in msdb.  It will list all the package names and IDs.  Just copy and past them into the parameters for sp_reassign_dtspackageowner.

Greg

DTS can copy your table schema as well as data.  That would eliminate your scripting step.

Greg

I've never had a package revert to a previous owner after changing it with sp_reassign_dtspackageowner.  That's why I use it intead of modiying the system table.

Greg

I'm not clear about what you need to do but if you can't use replication, maybe log shipping or DTS would work for you.

Greg 

It appears the permissions error is generated in the ActiveX Script task.  What is the task doing?  What connection is it using?

Greg

The package will execute in the security context of the login designated for SQL Server Agent.  Make sure that login has permission to create the text file.

Greg

I queried MS Knowledge Base for the message and got 11 articles.  Maybe one of them fits your situation.

Greg

http://search.support.microsoft.com/search/default.aspx?spid=2852&query=SQL+Server+could+not+spawn+process_loginread+thread&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=11&y=14

That would work.  Make sure you update all versions.

Greg

sp_reassign_dtspackageowner.  It's in msdb.

If the package will reside on the client's machine that you can't access, I can't think how you will be able to find the package let alone delete it.

Greg