Error Copying from 2000 to 2005

Hello. I'm getting a frustrating error trying to copy a database from SQL
2000 to SQL 2005 using the copy wizard. The attempt fails with two errors in
the event log on the SQL 2005 server. I am running SQL 2005 64-bit Edition o
n
Windows Server 2003 64 on a Intel Xeon EMT. I continue to receive the error
even after an upgrade to SP1:
Faulting application dtexec.exe, version 2005.90.1399.0, stamp 43500d1a,
faulting module kernel32.dll, version 5.2.3790.1830, stamp 42438b79, debug?
0, fault address 0x0000000000027d0d.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
&&
Faulting application dtexec.exe, version 2005.90.1399.0, stamp 43500d1a,
faulting module kernel32.dll, version 5.2.3790.1830, stamp 42438b79, debug?
0, fault address 0x0000000000027d0d.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
From this link:
http://www.dbtalk.net/microsoft-pub...
-a-165165.html
It would seem that others are also having this issue - but nothing from
Microsoft on it. I'm not sure how to move forward. And yes, I do realize tha
t
Its probably simplier to offline the database and copy the files, but that i
s
not what I want to do. I want to use a feature of the product we purchased.
Has anyone run into and FIXED this issue before.
Thanks!
Errol NealHi
Try RESTORE command
"Errol Neal" <ErrolNeal@.discussions.microsoft.com> wrote in message
news:5F4BA321-C5BB-4427-A6C8-014E1F22995D@.microsoft.com...
> Hello. I'm getting a frustrating error trying to copy a database from SQL
> 2000 to SQL 2005 using the copy wizard. The attempt fails with two errors
> in
> the event log on the SQL 2005 server. I am running SQL 2005 64-bit Edition
> on
> Windows Server 2003 64 on a Intel Xeon EMT. I continue to receive the
> error
> even after an upgrade to SP1:
> Faulting application dtexec.exe, version 2005.90.1399.0, stamp 43500d1a,
> faulting module kernel32.dll, version 5.2.3790.1830, stamp 42438b79,
> debug?
> 0, fault address 0x0000000000027d0d.
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> &&
> Faulting application dtexec.exe, version 2005.90.1399.0, stamp 43500d1a,
> faulting module kernel32.dll, version 5.2.3790.1830, stamp 42438b79,
> debug?
> 0, fault address 0x0000000000027d0d.
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> From this link:
> http://www.dbtalk.net/microsoft-pub...0-a-165165.html
> It would seem that others are also having this issue - but nothing from
> Microsoft on it. I'm not sure how to move forward. And yes, I do realize
> that
> Its probably simplier to offline the database and copy the files, but that
> is
> not what I want to do. I want to use a feature of the product we
> purchased.
> Has anyone run into and FIXED this issue before.
> Thanks!
> Errol Neal|||Just an update, if someone is looking for solution:
Make sure SQLServer domain user you are running SQL SERVER on new
server has access to old SQL server. Usually you need to add SQL User
domain account to Local Administrator group on the old server.