Copy Database Wizard Timeout Error

Hi,

I am copying a database from one server to the other. Both have SQL 2005. When using the CDW, I get the following error after 10 minutes:

Event Name: OnError

Message: An exception occurred while executing a Transact-SQL statement or batch.

StackTrace: at Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteWithResults(String sqlCommand)

at Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteWithResults(StringCollection sqlCommands)

at Microsoft.SqlServer.Dts.Tasks.TransferObjectsTask.TransferObjectsTask.TransferDatabasesUsingSMOTransfer()

InnerException-->Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

CREATE DATABASE failed. Some file names listed could not be created. Check related errors.

It always errors at 10 minutes. But, when I run the Create Database statement from my query analyzer, it works and it takes about 18 minutes.

How do I get the CDW to wait longer than 10 minutes before returning an error?

I have set my remote query timeout to 20 minutes and that didn't seem to have any effect.

Thanks,

--ExoStatic

Have you installed Service PAck 2? CDW is much improved.

Download SQL Server 2005 Service Pack 2 at:

http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/servicepacks/sp2.mspx

...probably doesn't matter but the job runs on the destination server so it timeouts are relevent they may need to be set on that server.

|||

We have greatly improved SMO transfer in CDW with Service Pack 2. I strongly suggest you try that. Also, you could try using the detach/attach method instead of SMO Transfer. I believe it is faster and more reliable.

After installing Service Pack 2, please let us know if your problem persists. You may still have to change some settings on your server.

Paul A. Mestemaker II
Program Manager
Microsoft SQL Server Manageability
http://blogs.msdn.com/sqlrem/

|||

if you use Detach/attach method you still need to migrate the Login from Source Server. You can also try Backup/Restore method which is best in such scenario. in this method also the Logins has to be taken care.

To transfer login Refer :http://support.microsoft.com/default.aspx/kb/246133

Madhu

sqlsql

copy database error (finding folder, login timeout)

Hello, just got SQL Server 2005 installed on a new production box and am
trying desperately to get data to it from an old SQL2000 production box -
unfortunately for me each time i try to use the copy database tools in order
to copy the database i get to the step where i am to "configure the package"
and the following popup appears:
While trying to find a folder on SQL an OLE DB error was encountered with
error code 0x80004005 (Login timeout expired).
I'm using the credentials of users who have sysAdmin priviledges.
Obviously this is leading to much hair pulling, screaming and near laptop
hurling. Someone please tell me what i'm doing wrong!?Matt
Why not just RESTORE the 'old' database (SQL Server 2000) to SQL Server
2005?
"Matt Pallatt" <matt.pallatt@.cmwnorth.com> wrote in message
news:OdKJlO5uGHA.4512@.TK2MSFTNGP05.phx.gbl...
> Hello, just got SQL Server 2005 installed on a new production box and am
> trying desperately to get data to it from an old SQL2000 production box -
> unfortunately for me each time i try to use the copy database tools in
> order to copy the database i get to the step where i am to "configure the
> package" and the following popup appears:
> While trying to find a folder on SQL an OLE DB error was encountered with
> error code 0x80004005 (Login timeout expired).
> I'm using the credentials of users who have sysAdmin priviledges.
> Obviously this is leading to much hair pulling, screaming and near laptop
> hurling. Someone please tell me what i'm doing wrong!?
>|||I unfortunately have no upload access to the box to get a backup onto it to
be able to restore an old DB
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:OB$rmW5uGHA.4612@.TK2MSFTNGP02.phx.gbl...
> Matt
> Why not just RESTORE the 'old' database (SQL Server 2000) to SQL Server
> 2005?
>
> "Matt Pallatt" <matt.pallatt@.cmwnorth.com> wrote in message
> news:OdKJlO5uGHA.4512@.TK2MSFTNGP05.phx.gbl...
>|||Matt
I understood you use SQL Server200 as you wrote, did not you?
What tool dp you use to transfer the data? SSIS,DTS?
"Matt Pallatt" <matt.pallatt@.cmwnorth.com> wrote in message
news:u4riyy5uGHA.3552@.TK2MSFTNGP03.phx.gbl...[vbcol=seagreen]
>I unfortunately have no upload access to the box to get a backup onto it to
>be able to restore an old DB
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:OB$rmW5uGHA.4612@.TK2MSFTNGP02.phx.gbl...
>|||I think that this "I unfortunately have no upload access to the box" is the
clue to the situation.
SQL Server 'should' have permissions to the file system on the local server.
This error "While trying to find a folder on SQL an OLE DB error was
encountered with error code 0x80004005 (Login timeout expired)." makes it
seem like a file system permission issue.
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"Matt Pallatt" <matt.pallatt@.cmwnorth.com> wrote in message
news:u4riyy5uGHA.3552@.TK2MSFTNGP03.phx.gbl...
>I unfortunately have no upload access to the box to get a backup onto it to
>be able to restore an old DB
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:OB$rmW5uGHA.4612@.TK2MSFTNGP02.phx.gbl...
>

copy database error (finding folder, login timeout)

Hello, just got SQL Server 2005 installed on a new production box and am
trying desperately to get data to it from an old SQL2000 production box -
unfortunately for me each time i try to use the copy database tools in order
to copy the database i get to the step where i am to "configure the package"
and the following popup appears:
While trying to find a folder on SQL an OLE DB error was encountered with
error code 0x80004005 (Login timeout expired).
I'm using the credentials of users who have sysAdmin priviledges.
Obviously this is leading to much hair pulling, screaming and near laptop
hurling. Someone please tell me what i'm doing wrong!?Matt
Why not just RESTORE the 'old' database (SQL Server 2000) to SQL Server
2005?
"Matt Pallatt" <matt.pallatt@.cmwnorth.com> wrote in message
news:OdKJlO5uGHA.4512@.TK2MSFTNGP05.phx.gbl...
> Hello, just got SQL Server 2005 installed on a new production box and am
> trying desperately to get data to it from an old SQL2000 production box -
> unfortunately for me each time i try to use the copy database tools in
> order to copy the database i get to the step where i am to "configure the
> package" and the following popup appears:
> While trying to find a folder on SQL an OLE DB error was encountered with
> error code 0x80004005 (Login timeout expired).
> I'm using the credentials of users who have sysAdmin priviledges.
> Obviously this is leading to much hair pulling, screaming and near laptop
> hurling. Someone please tell me what i'm doing wrong!?
>|||I unfortunately have no upload access to the box to get a backup onto it to
be able to restore an old DB :(
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:OB$rmW5uGHA.4612@.TK2MSFTNGP02.phx.gbl...
> Matt
> Why not just RESTORE the 'old' database (SQL Server 2000) to SQL Server
> 2005?
>
> "Matt Pallatt" <matt.pallatt@.cmwnorth.com> wrote in message
> news:OdKJlO5uGHA.4512@.TK2MSFTNGP05.phx.gbl...
>> Hello, just got SQL Server 2005 installed on a new production box and am
>> trying desperately to get data to it from an old SQL2000 production box -
>> unfortunately for me each time i try to use the copy database tools in
>> order to copy the database i get to the step where i am to "configure the
>> package" and the following popup appears:
>> While trying to find a folder on SQL an OLE DB error was encountered with
>> error code 0x80004005 (Login timeout expired).
>> I'm using the credentials of users who have sysAdmin priviledges.
>> Obviously this is leading to much hair pulling, screaming and near laptop
>> hurling. Someone please tell me what i'm doing wrong!?
>>
>|||Matt
>> trying desperately to get data to it from an old SQL2000 production
>> box - unfortunately for me each time i try to use the copy database
>> tools in order to copy the database i get to the step where i am to
>> "configure the package" and the following popup appears:
I understood you use SQL Server200 as you wrote, did not you?
What tool dp you use to transfer the data? SSIS,DTS?
"Matt Pallatt" <matt.pallatt@.cmwnorth.com> wrote in message
news:u4riyy5uGHA.3552@.TK2MSFTNGP03.phx.gbl...
>I unfortunately have no upload access to the box to get a backup onto it to
>be able to restore an old DB :(
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:OB$rmW5uGHA.4612@.TK2MSFTNGP02.phx.gbl...
>> Matt
>> Why not just RESTORE the 'old' database (SQL Server 2000) to SQL Server
>> 2005?
>>
>> "Matt Pallatt" <matt.pallatt@.cmwnorth.com> wrote in message
>> news:OdKJlO5uGHA.4512@.TK2MSFTNGP05.phx.gbl...
>> Hello, just got SQL Server 2005 installed on a new production box and am
>> trying desperately to get data to it from an old SQL2000 production
>> box - unfortunately for me each time i try to use the copy database
>> tools in order to copy the database i get to the step where i am to
>> "configure the package" and the following popup appears:
>> While trying to find a folder on SQL an OLE DB error was encountered
>> with error code 0x80004005 (Login timeout expired).
>> I'm using the credentials of users who have sysAdmin priviledges.
>> Obviously this is leading to much hair pulling, screaming and near
>> laptop hurling. Someone please tell me what i'm doing wrong!?
>>
>>
>|||I think that this "I unfortunately have no upload access to the box" is the
clue to the situation.
SQL Server 'should' have permissions to the file system on the local server.
This error "While trying to find a folder on SQL an OLE DB error was
encountered with error code 0x80004005 (Login timeout expired)." makes it
seem like a file system permission issue.
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"Matt Pallatt" <matt.pallatt@.cmwnorth.com> wrote in message
news:u4riyy5uGHA.3552@.TK2MSFTNGP03.phx.gbl...
>I unfortunately have no upload access to the box to get a backup onto it to
>be able to restore an old DB :(
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:OB$rmW5uGHA.4612@.TK2MSFTNGP02.phx.gbl...
>> Matt
>> Why not just RESTORE the 'old' database (SQL Server 2000) to SQL Server
>> 2005?
>>
>> "Matt Pallatt" <matt.pallatt@.cmwnorth.com> wrote in message
>> news:OdKJlO5uGHA.4512@.TK2MSFTNGP05.phx.gbl...
>> Hello, just got SQL Server 2005 installed on a new production box and am
>> trying desperately to get data to it from an old SQL2000 production
>> box - unfortunately for me each time i try to use the copy database
>> tools in order to copy the database i get to the step where i am to
>> "configure the package" and the following popup appears:
>> While trying to find a folder on SQL an OLE DB error was encountered
>> with error code 0x80004005 (Login timeout expired).
>> I'm using the credentials of users who have sysAdmin priviledges.
>> Obviously this is leading to much hair pulling, screaming and near
>> laptop hurling. Someone please tell me what i'm doing wrong!?
>>
>>
>