Copy Database from One SQL server to another fails

I am try to run a DTS package to copy a database from one SQL server to
another one.
The DTS package was running fine till yesterday morning but now I am getting
the error message
The Bulk Copy Execution Failed
Error Code 80045707
any thoughts?
drew
Does your SQL Server Service user have enough rights to copy files over the
network?
It might be a problem..
"drew" wrote:

> I am try to run a DTS package to copy a database from one SQL server to
> another one.
> The DTS package was running fine till yesterday morning but now I am getting
> the error message
> The Bulk Copy Execution Failed
> Error Code 80045707
> any thoughts?
> --
> drew
|||Yes the user right are okay, using SA on SQL and Administrator on the windows
2003 servers.
"Umut Nazlica" wrote:
[vbcol=seagreen]
> Does your SQL Server Service user have enough rights to copy files over the
> network?
> It might be a problem..
>
> "drew" wrote:
|||Hi,
Sorry if i'm not clear, what i meant is SQL Server Service on both SQL
servers are not running with Local System Account right?
"drew" wrote:
[vbcol=seagreen]
> Yes the user right are okay, using SA on SQL and Administrator on the windows
> 2003 servers.
> "Umut Nazlica" wrote:
|||The user account are okay. It seems to be a problem the database it self. If
we try and backup and the restore the database to another name on the same
SQL instance. The database hangs on the restore saying it is loading.
Regards Drew
"Umut Nazlica" wrote:
[vbcol=seagreen]
> Hi,
> Sorry if i'm not clear, what i meant is SQL Server Service on both SQL
> servers are not running with Local System Account right?
>
> "drew" wrote:
|||> The user account are okay. It seems to be a problem the database it self.
That would surprise me.

> If
> we try and backup and the restore the database to another name on the same
> SQL instance. The database hangs on the restore saying it is loading.
That is expected if you do the restore using NORECOVERY. Try using RECOVERY instead. Also, make sure
it isn't just EM that doesn't refreshed. Try logging in using Query Analyzer and access the
database.
My guess is that there has been some account changes for the Agent.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"drew" <drew@.discussions.microsoft.com> wrote in message
news:B128608B-0E23-4D66-BE8B-B40CC941B09C@.microsoft.com...[vbcol=seagreen]
> The user account are okay. It seems to be a problem the database it self. If
> we try and backup and the restore the database to another name on the same
> SQL instance. The database hangs on the restore saying it is loading.
> Regards Drew
> "Umut Nazlica" wrote:
|||We got the backup and restore working okay but still problems with the DTS
package.
We tried copying the database to another name name on the same SQL instance
but still get the problem.
If I detach the database and copy it to aother SQL server then attach it
there I again get the problem of not being able to copy it to another name on
the same SQL instance.
If I copy just the objects not the data everything is okay. If I then
compare the databases with SQL compare everything is okay.
If I try to use the DTS copy databse task to just copy the data. Using SQL
compare the permmisions on the databse tables change with the public role
being dropped and the not null constraint check becomig just not null.
Talkig with Microsoft but still not much further forward.
"Tibor Karaszi" wrote:

> That would surprise me.
>
> That is expected if you do the restore using NORECOVERY. Try using RECOVERY instead. Also, make sure
> it isn't just EM that doesn't refreshed. Try logging in using Query Analyzer and access the
> database.
> My guess is that there has been some account changes for the Agent.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "drew" <drew@.discussions.microsoft.com> wrote in message
> news:B128608B-0E23-4D66-BE8B-B40CC941B09C@.microsoft.com...
>
>
|||we final got the problem resolved with the help of Kevin at MSDN.
In the database some had created a blob bigger than 8 Meg, this caused the
DTS package to fail. hen we romved the offending records the package ran
okay.
see KB 257425
regards Drew
"drew" wrote:
[vbcol=seagreen]
> We got the backup and restore working okay but still problems with the DTS
> package.
> We tried copying the database to another name name on the same SQL instance
> but still get the problem.
> If I detach the database and copy it to aother SQL server then attach it
> there I again get the problem of not being able to copy it to another name on
> the same SQL instance.
> If I copy just the objects not the data everything is okay. If I then
> compare the databases with SQL compare everything is okay.
> If I try to use the DTS copy databse task to just copy the data. Using SQL
> compare the permmisions on the databse tables change with the public role
> being dropped and the not null constraint check becomig just not null.
> Talkig with Microsoft but still not much further forward.
> "Tibor Karaszi" wrote: