"Cannot read CDW log from the destination server...."

Question

"Cannot read CDW log from the destination server...."

Barkingdog

SSCoach

Points: 18670
More actions
June 8, 2005 at 3:09 pm

#362881

Test environment that shadows the real one: old sql2k server uses D:\mssql\data while new server uses C:\mssql\data. I'm using the Copy Database Wizard under EM because it is easy to use. The copy job was well underway when a dialog box appeared on the Source server: "cannot read DWL log from the destination server".
Any idea what the source of this? Available disk space too small?
I ran chkdsk on the disks on both servers and no corruption was reported on either server.)
TIA,

Bill

Viewing 4 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply

Steve Rodgers SSC Journeyman Points: 84 More actions · Answer 1

Hi,

I received the same error following a migration from Win2000 -> Server2003 whenever one of our support guys tries to view a DTS package log SEM shows the error message. My only workaround at the moment is to grant the user dbo on the msdb database.

Steve.

dbaforever Hall of Fame Points: 3740 More actions · Answer 2

I encountered this message just today as I was testing permissions for one of our developers.

********************************************

The solution is to grant the user db_datareader permissions within the msdb database.

Then the user/programmer will be able to view the DTS Package log.

********************************************

Thanks, John

Himabala Grasshopper Points: 18 More actions · Answer 3

Still more interesting solution.

Instead of granting the user db_dataread on the whole msdb (system) database, grant the user public permission on the database (msdb) and then grant the user select permission on sysdtssteplog table in the database (msdb).