This would indicate that the sql server service accounts either do not have access to the drive/file, or that the file does not in fact exist.

From within QA, if you run

exec master..xp_cmdshell 'dir t:\Customised\Database\PFW\Util\$ConData.scr'

What results do you get?

As a side note, I would turn off AWE, it's not needed with only 4GB of RAM. Leave the /3GB switch in however.

It's the scr file which is the problem, the ftp process cannot locate it. (Error opening script file t:\Customised\Database\PFW\Util\$ConData.scr. )

Have you tried running the ftp command directly on...

Create this function in your db and call it in your select statement (ie select dbo.convertunixtime(DATE)), this will convert the unixtime (int) to the real time.

CREATE FUNCTION dbo.convertunixtime (@UNIXTime int) ...

I would also force a recompile on all of your stored procs, it's possible that the execution does not match what it would have done in sql7.

I would double check the script which is being called in the ftp process, it's not able to access the file, which, if the permissions are fine, just means that...

If you run a SELECT * from MASTER..SYSFILES that should give you the location where the files are actually running from.

How about EXEC sp_msunmarkreplinfo 'bc000026m'

or

EXEC sp_configure 'allow',1

go

reconfigure with override

go

use your_database_name

go

update sysobjects set replinfo = 0 where name = 'bc000026m'

go

EXEC...

Have you looked at using the dynamic properties task and assigning values to the execute package task from there?

Have you tried running an sp_removedbreplication just to make sure that the db is replication clean?

On an ongoing basis, I generally look at the articles and the commentary, take a gander at the script of the day.

If I have time during the day I'll go...

There's not one that I am aware of.

I've not lived there in a few years, but I'll take a look see and give you an honest opinion.

If there is another query that is running against the table/s containing those columns then you could end up with a blocking problem, if the data is not highly transactional...