copy database error 12291 and 208

microsoft.public.sqlserver.tools

1 Sep 2006 11:49 AM

Philippe

Hi,
when trying to copy a database from SQLSERVER 2000 To SQLSERVVER 2005
using Copy Database Wizard (CDW) it fails and give two errors in events:

Source: SQLISPackage Event ID: 12291
and
Event Source: SQLSERVERAGENT Event ID: 208

using text error reporting i find :

"StackTrace: at
Microsoft.SqlServer.Management.Common.ConnectionManager.Connect()
at
Microsoft.SqlServer.Dts.Tasks.TransferObjectsTask.TransferObjectsTask.OpenConnection(Server&
server, ServerProperty serverProp)
InnerException-->An error has occurred while establishing a connection
to the server. When connecting to SQL Server 2005, this failure may be
caused by the fact that under the default settings SQL Server does not
allow remote connections. (provider: Named Pipes Provider, error: 40 -
Could not open a connection to SQL Server)"

First erver is running Windows 2000 server,SQLSERVER 2000
destination server is running Windows 2003 server and SQLSERVER 2005.

remote connections named Pipes and TCP/IP connection are allowed,

I you have an idea .. :)
Thanks

Philippe

1 Sep 2006 12:02 PM

Hari Prasad

Hi,

Go to SQL Server Surface Area configurationf rom SQL Server 2005 program
groups:-

1. Click Start, point to Programs, point to Microsoft SQL Server 2005,
   point to Configuration Tools, and then click SQL Server
   Surface Area Configuration.
2. On the SQL Server 2005 Surface Area Configuration page, click Surface
   Area Configuration for Services and Connections.
3. On the Surface Area Configuration for Services and Connections page,
   expand Database Engine, click Remote Connections, click
   Local and remote connections, click the appropriate protocol to enable
   for your environment, and then click Apply.

Stop and Start the SQL Server service.

If you are running SQL Server 2005 by using an instance name and you are not
using a specific TCP/IP port number in your connection string, you must
enable
the SQL Server Browser service to allow for remote connections

After doing this changes try again

Thanks
Hari
SQL Server MVP

Show quote

"Philippe" <"phil_c <nopub> wrote in message
news:44f81e47$0$27351$636a55ce@news.free.fr...
> Hi,
> when trying to copy a database from SQLSERVER 2000 To SQLSERVVER 2005
> using Copy Database Wizard (CDW) it fails and give two errors in events:
>
> Source: SQLISPackage Event ID: 12291
> and
> Event Source: SQLSERVERAGENT Event ID: 208
>
> using text error reporting i find :
>
> "StackTrace: at
> Microsoft.SqlServer.Management.Common.ConnectionManager.Connect()
> at
> Microsoft.SqlServer.Dts.Tasks.TransferObjectsTask.TransferObjectsTask.OpenConnection(Server&
> server, ServerProperty serverProp)
> InnerException-->An error has occurred while establishing a connection to
> the server. When connecting to SQL Server 2005, this failure may be
> caused by the fact that under the default settings SQL Server does not
> allow remote connections. (provider: Named Pipes Provider, error: 40 -
> Could not open a connection to SQL Server)"
>
> First erver is running Windows 2000 server,SQLSERVER 2000
> destination server is running Windows 2003 server and SQLSERVER 2005.
>
> remote connections named Pipes and TCP/IP connection are allowed,
>
> I you have an idea .. :)
> Thanks
>
> Philippe

1 Sep 2006 12:44 PM

Philippe

Hari Prasad a écrit :
Show quote

> Hi,
>
> Go to SQL Server Surface Area configurationf rom SQL Server 2005 program
> groups:-
>
> 1. Click Start, point to Programs, point to Microsoft SQL Server 2005,
>    point to Configuration Tools, and then click SQL Server
>    Surface Area Configuration.
> 2. On the SQL Server 2005 Surface Area Configuration page, click Surface
>    Area Configuration for Services and Connections.
> 3. On the Surface Area Configuration for Services and Connections page,
>    expand Database Engine, click Remote Connections, click
>    Local and remote connections, click the appropriate protocol to enable
>    for your environment, and then click Apply.
>
> Stop and Start the SQL Server service.
>
>
> If you are running SQL Server 2005 by using an instance name and you are not
> using a specific TCP/IP port number in your connection string, you must
> enable
> the SQL Server Browser service to allow for remote connections
>
> After doing this changes try again
>
> Thanks
> Hari
> SQL Server MVP
>
> "Philippe" <"phil_c <nopub> wrote in message
> news:44f81e47$0$27351$636a55ce@news.free.fr...
>> Hi,
>> when trying to copy a database from SQLSERVER 2000 To SQLSERVVER 2005
>> using Copy Database Wizard (CDW) it fails and give two errors in events:
>>
>> Source: SQLISPackage Event ID: 12291
>> and
>> Event Source: SQLSERVERAGENT Event ID: 208
>>
>> using text error reporting i find :
>>
>> "StackTrace: at
>> Microsoft.SqlServer.Management.Common.ConnectionManager.Connect()
>> at
>> Microsoft.SqlServer.Dts.Tasks.TransferObjectsTask.TransferObjectsTask.OpenConnection(Server&
>> server, ServerProperty serverProp)
>> InnerException-->An error has occurred while establishing a connection to
>> the server. When connecting to SQL Server 2005, this failure may be
>> caused by the fact that under the default settings SQL Server does not
>> allow remote connections. (provider: Named Pipes Provider, error: 40 -
>> Could not open a connection to SQL Server)"
>>
>> First erver is running Windows 2000 server,SQLSERVER 2000
>> destination server is running Windows 2003 server and SQLSERVER 2005.
>>
>> remote connections named Pipes and TCP/IP connection are allowed,
>>
>> I you have an idea .. :)
>> Thanks
>>
>> Philippe
>
>

Thanks you for your fast answer,
I tried to doso, TCP/IP and Named Pipes are allowed for remote
connection as needed and the SQL Server Browser service is enabled.

I tried again but it failed at the last step (running sql agent) whith
the same error message.

(I can acces without problem to the both databases whith
ServerManagement Studio)

Philippe

6 Sep 2006 5:13 PM

Sethu Srinivasan [MSFT]

Hello Philippe,
The last step in Copy Database Wizard executes a SSIS package in a SQL Agent
Job ( Job executed by SQL Server Agent service). Please make sure the SQL
Server Agent service start up account credentials has sufficient permissions
to access source and target SQL Server. and databases.

If you could send us a detailed repro scenario through Connect web site,
our product team could take a look at this issue

https://connect.microsoft.com/SQLServer/Feedback

Click on Submit Feedback

Please include the following details
SQL Server Version, Edition
Copy Database Wizard Log files

--
Thanks
Sethu Srinivasan, Software Design Engineer, SQL Server Manageability
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm.

Show quote

"Philippe" <"phil_c <nopub> wrote in message
news:44f82b0e$0$6438$636a55ce@news.free.fr...
> Hari Prasad a écrit :
>> Hi,
>>
>> Go to SQL Server Surface Area configurationf rom SQL Server 2005 program
>> groups:-
>>
>> 1. Click Start, point to Programs, point to Microsoft SQL Server 2005,
>>    point to Configuration Tools, and then click SQL Server
>>    Surface Area Configuration.
>> 2. On the SQL Server 2005 Surface Area Configuration page, click Surface
>>    Area Configuration for Services and Connections.
>> 3. On the Surface Area Configuration for Services and Connections page,
>>    expand Database Engine, click Remote Connections, click
>>    Local and remote connections, click the appropriate protocol to enable
>>    for your environment, and then click Apply.
>>
>> Stop and Start the SQL Server service.
>>
>>
>> If you are running SQL Server 2005 by using an instance name and you are
>> not
>> using a specific TCP/IP port number in your connection string, you must
>> enable
>> the SQL Server Browser service to allow for remote connections
>>
>> After doing this changes try again
>>
>> Thanks
>> Hari
>> SQL Server MVP
>>
>> "Philippe" <"phil_c <nopub> wrote in message
>> news:44f81e47$0$27351$636a55ce@news.free.fr...
>>> Hi,
>>> when trying to copy a database from SQLSERVER 2000 To SQLSERVVER 2005
>>> using Copy Database Wizard (CDW) it fails and give two errors in events:
>>>
>>> Source: SQLISPackage Event ID: 12291
>>> and
>>> Event Source: SQLSERVERAGENT Event ID: 208
>>>
>>> using text error reporting i find :
>>>
>>> "StackTrace: at
>>> Microsoft.SqlServer.Management.Common.ConnectionManager.Connect()
>>> at
>>> Microsoft.SqlServer.Dts.Tasks.TransferObjectsTask.TransferObjectsTask.OpenConnection(Server&
>>> server, ServerProperty serverProp)
>>> InnerException-->An error has occurred while establishing a connection
>>> to the server. When connecting to SQL Server 2005, this failure may be
>>> caused by the fact that under the default settings SQL Server does not
>>> allow remote connections. (provider: Named Pipes Provider, error: 40 -
>>> Could not open a connection to SQL Server)"
>>>
>>> First erver is running Windows 2000 server,SQLSERVER 2000
>>> destination server is running Windows 2003 server and SQLSERVER 2005.
>>>
>>> remote connections named Pipes and TCP/IP connection are allowed,
>>>
>>> I you have an idea .. :)
>>> Thanks
>>>
>>> Philippe
>>
>>
>
> Thanks you for your fast answer,
> I tried to doso, TCP/IP and Named Pipes are allowed for remote connection
> as needed and the SQL Server Browser service is enabled.
>
> I tried again but it failed at the last step (running sql agent) whith the
> same error message.
>
> (I can acces without problem to the both databases whith ServerManagement
> Studio)
>
> Philippe

1 Sep 2006 9:50 PM

Erland Sommarskog

Philippe <"phil_c (nopub) writes:
Show quote

> when trying to copy a database from SQLSERVER 2000 To SQLSERVVER 2005
> using Copy Database Wizard (CDW) it fails and give two errors in events:
>
> Source: SQLISPackage Event ID:     12291
> and
> Event Source:     SQLSERVERAGENT Event ID: 208
>
> using text error reporting i find :
>
> "StackTrace: at
> Microsoft.SqlServer.Management.Common.ConnectionManager.Connect()
>   at
>...
> First erver is running Windows 2000 server,SQLSERVER 2000
> destination server is running Windows 2003 server and SQLSERVER 2005.
>
> remote connections named Pipes and TCP/IP connection are allowed,

That's kind of strange error since the job always have been running
on the destination server everytime I've tried it. And it can't run
on the source server anyway, since the source is SQL 2000.

So why would Integration Services not be able to connect locally? Hm,
exactly how did you specify the target server?

And from which machine did you initiate the copy? From the destination
server? Or a third machine?

And which method did you pick? SMO Method or attach/detach?

(I did just try SMO - it failed with an exception "the DefaultSchema
property is not available on SQL 2000" - it reinforces my opinion
that the CDW is still an early beta.)

By the way, always make it a habit to send the CDW log to text file.

--
Erland Sommarskog, SQL Server MVP, esq***@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

2 Sep 2006 5:50 PM

Erland Sommarskog

Erland Sommarskog (esq***@sommarskog.se) writes:

> (I did just try SMO - it failed with an exception "the DefaultSchema
> property is not available on SQL 2000" - it reinforces my opinion
> that the CDW is still an early beta.)

I did some research on that. Apparently there was something spooky with
the database I tried. (One of my several junk databases for various
funny tests.) I tried to reproduce it by starting from scratch, but I did
not succeed. I did not dig too deep into it, though.