Connection Problem

I created a package with two oledb connections in the connection manager....which was running perfectly...later i deleted these connections and added two new connections....and applied these to task with the new connection..

Now i run the package i come up with the following error...connection not found

Error 1 Error loading test.dtsx: The connection "SQL-DEV.sql_dev" is not found. This error is thrown by Connections collection when the specific connection element is not found. c:\documents and settings\myname\desktop\integration services project\ssis\test.dtsx 1 1

when i double click the error it goes to xml code...i dont know what need to be done...please help

Did you name the "new" connections the same as the old connections?|||No i didnt name them with the same name as the old once but the New connections are just the same as old connections...selecting server and database..|||Is "SQL-DEV.sql_dev" the name of a new connection or one of the ones you deleted?|||

Hi Sureshv,

The problem is the Connection Managers, for whatever reason, were not completely deleted. Their metadata is still stored inside the XML source for the SSIS files.

Naming the new Connection Managers the same as the old Connection Managers will not impact this error - Connection Managers are identified by GUIDs in SSIS. If you can identify the GUID of the deleted Connection Managers (perhaps by process of elimination), and comment them out inside the metadata, the package will stop throwing the error.

Hope this helps,
Andy

|||Andy,
ALL GUI screens represent a connection manager by its name, not GUID. This is precisely why I asked the question that I did. I imagined a scenario where the metadata was not cleaned up properly and when Sureshv picked the connection manager [name] in the drop down box, it was associated with a [now] defunct GUID, hence the resulting error.

In the end I think we can agree the likely culprit is bad metadata.|||

Hi Phil,

Thanks. I've seen some tasks respond differently to this scenario. Some of them pick up the changes automatically and some don't. I've also seen metadata corruption make this completely unpredicatable.

Yep - we agree this is the culprit. It's no fun to clean up a large package with corrupt metadat either - good luck Sureshv.

Andy

|||

In general when you delete a connection manager that is being used by a task; that task keeps pointing to the deleted connection manager GUID; untill you open the task and chose a diffrent one.

To the Original poster, make sure you revist all the tasks that were using those connection managers and refresh the connection metadata. If the package has logging enable and it was using one of the deleted CM; you have to refresh it as well.

|||i dont find the old connection name with in connection managers in the xml...So what do i do? i am afraid i will break my package...any more solutions?|||Did you check and correct the package logging?|||i did not set any package logging for this package..sqlsql

Connection lost

I'm running an access application on my local server (SQL Server 2000)
On my win 2000 it worked perfectly.
On my win XP, I always get this error message :
3151: ODBC--Connection to 'MyODBC' Failed.
This happens when I want to run a procedure that fills a table with records
from other tables. There's a lot of Select in this code but always on the
same recordset. Many loops. I see my record number going fast in the bottom
of the screen but it always stops at 207. When I do it in debug, no
problem... can't find where's the problem.
I allowed the maximum quantity of memory for SQL Server (512) and I have 2
Go of memory on my computer.
Help please!
StephSteph,
First, the memory issue. If your host computer has 2 GB of memory, and there
are no other significant applications using the computer, SQL Server should
NOT be limited to 512 MB. With Enterprise Manager, check the max memory
setting for the server and check the box to allow SQL to Dynamically manage
the memory. -AND, it doesn't sound as though your issue is related to
memory. (But if you are running MSDE or SQL Express on your desktop
computer, that it a different issue.)
Second, your Access application probably 'should' be using an OLEDB (or ADO)
connection instead of ODBC.
Third, it is extremely poor use of SQL Server to be using 'Many loops' in a
procedure. SQL Server handles data in sets -and very fast and efficiently.
We 'should' not step through data one row at a time.
If you were to post your code to one of the Access newgroups, someone may be
able to help you in making it fast and efficient.
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"Stephen" <smarcoux@.cbgi.qc.ca> wrote in message
news:Oapt9$7uGHA.1296@.TK2MSFTNGP02.phx.gbl...
> I'm running an access application on my local server (SQL Server 2000)
> On my win 2000 it worked perfectly.
> On my win XP, I always get this error message :
> 3151: ODBC--Connection to 'MyODBC' Failed.
> This happens when I want to run a procedure that fills a table with
> records from other tables. There's a lot of Select in this code but always
> on the same recordset. Many loops. I see my record number going fast in
> the bottom of the screen but it always stops at 207. When I do it in
> debug, no problem... can't find where's the problem.
> I allowed the maximum quantity of memory for SQL Server (512) and I have 2
> Go of memory on my computer.
> Help please!
> Steph
>

Connection fails SQL 2000

One of our customers has SQl server 2000 installed
This has been working perfectly untill last Friday.
At this point various databases began to return errors
when querries were run on the data.
There appeasr to be no pattern to which databases still
work as I have two backup copies of the main databse they
use. The main one and one of the backups produce errors
yet the other backup, taken on the same day does not.
Looking at the error log (attached) there seems to be a
lot of "corrupt" entires.
Any suggestions
Date Source Message
---
--
---
--...
004 DC771 Module(sqlservr+000DC771) (ExecuteSql
(class CParamExchange *,class CXVariant *,
004 A9DE2 Module(sqlservr+000A9DE2)
(CXteHashMatch::ExecCompile(class CExecCompContext *)
004 A9E93 Module(sqlservr+000A9E93)
(CXteHashMatch::ExecCompile(class CExecCompContext *)
004 A70B6 Module(sqlservr+000A70B6)
(CXteHashMatch::IntermediateCompile(class IMemObj *,c
004 A8B35 Module(sqlservr+000A8B35)
(CXteHashMatch::CreateBailoutPlan(class CRemapContext
0041 F796 Module(sqlservr+0001F796)
(CSQLObject::FTransform(class CParamExchange *)+00000
0041 FDDD Module(sqlservr+0001FDDD)
(CSQLObject::FTransform2(class CSQLComment *,class CP
00415080 Module(sqlservr+00015080)
(CSQLSource::FTransform(class CParamExchange *)
+0000037C)
0041534 F Module(sqlservr+0001534F)
(CSQLSource::Execute(class CParamExchange *)+00000176
00415410 Module(sqlservr+00015410)
(CSQLSource::Execute(class CParamExchange *)
+00000343)
00415765 Module(sqlservr+00015765)
(CMsqlExecContext::Execute(class CCompPlan *,class
CParamExchange *)+000001C7)
004160 DB Module(sqlservr+000160DB)
(CMsqlExecContext::ExecuteStmts(class ExecutionContex
0041767 E Module(sqlservr+0001767E) (process_commands
(struct srv_proc *)+000001E7)
0043 B7EF Module(sqlservr+0003B7EF) (execute_rpc
(struct srv_proc *)+00000019)
00447078 Module(sqlservr+00047078)
(CCompPlan::FCompileStep(class CAlgStmt *,class
CStatement * *)+00000AE7)
004510 FE Module(sqlservr+000510FE)
(CProchdr::FCompile(class CCompPlan *,class CParamExc
0049 CB9F Module(sqlservr+0009CB9F)
(CStmtExec::XretExecute(class CMsqlExecContext *)cons
0049 CD0A Module(sqlservr+0009CD0A)
(CStmtExec::XretLocalExec(class CMsqlExecContext *,un
0049 C6F4 Module(sqlservr+0009C6F4)
(CSQLObject::FGetFromDisk(class CParamExchange *)+000
0049 DA48 Module(sqlservr+0009DA48)
(CStmtSelect::Init(class CAlgStmt *,class CCompPlan *
00563 F78 Module(sqlservr+00163F78)
(CStmtQuery::InitQuery(class CAlgStmt *,class CCompPl
00564019 Module(sqlservr+00164019)
(BuildQueryFromTree(class TREE *,class IMemObj
*,class IMemObj *,class IQueryOb
005642 CD Module(sqlservr+001642CD)
(CCvtTree::PqryFromTree(class TREE *,class IMemObj *,
0056701 F Module(sqlservr+0016701F)
(CBndOutputs::RemapValrefs(class CRemapContext *,int)
00567536 Module(sqlservr+00167536)
(CXte::ExecCompile(class CExecCompContext *)
+000000B7)
00567536 Module(sqlservr+00167536)
(CXte::ExecCompile(class CExecCompContext *)
+000000B7)
005688 A4 Module(sqlservr+001688A4) (CQuery::Prepare
(void)+00000116)
0061 DDB6 Module(sqlservr+0021DDB6)
(CSpecProc::Execute(class CParamExchange *)+00000092)
0061 DA3E Module(sqlservr+0021DA3E)
(CSpecProc::ExecuteSpecial(class CParamExchange *,uns
0063 C71D Module(sqlservr+0023C71D) (execrpc(struct
srv_proc *)+000004A8)
00703 A1C Module(sqlservr+00303A1C)
(CXteHashMatch::CreateInputScan(class IMemObj *,class
2003-11-05 12:36:10.29 server Microsoft SQL Server
2000 - 8.00.194 (Intel X86) ...
2003-11-05 12:36:10.54 server Logging SQL Server
messages in file 'd:\Program Files\Microsoft SQL
Server\MSSQ
2003-11-05 12:36:10.54 server Server Process ID is 1700.
2003-11-05 12:36:10.54 server All rights reserved.
2003-11-05 12:36:10.54 server Copyright (C) 1988-2000
Microsoft Corporation.
2003-11-05 12:36:10.99 server SQL Server is starting at
priority class 'normal'(4 CPUs detected).
2003-11-05 12:36:13.00 server SQL Server configured for
thread mode processing.
2003-11-05 12:36:13.23 server Using dynamic lock
allocation. [2500] Lock Blocks, [5000] Lock Owner Blocks.
2003-11-05 12:36:13.62 server Attempting to initialize
Distributed Transaction Coordinator.
2003-11-05 12:36:19.92 spid2 Starting up
database 'master'.
2003-11-05 12:36:27.70 spid5 Starting up
database 'model'.
2003-11-05 12:36:27.70 server Using 'SSNETLIB.DLL'
version '8.0.194'.
2003-11-05 12:36:27.73 spid2 Server name is 'WRLW2S002'.
2003-11-05 12:36:27.79 spid12 Starting up
database 'powerway'.
2003-11-05 12:36:27.79 spid11 Starting up
database 'dbWheelset_Live'.
2003-11-05 12:36:27.79 spid10 Starting up
database 'Northwind'.
2003-11-05 12:36:27.79 spid9 Starting up
database 'pubs'.
2003-11-05 12:36:27.79 spid8 Starting up
database 'msdb'.
2003-11-05 12:36:27.81 spid14 Starting up
database 'dbWheelSets_LIVE'.
2003-11-05 12:36:27.81 spid13 Starting up
database 'dbWheelSets_TEST'.
2003-11-05 12:36:27.89 spid16 Starting up
database 'dbWheelsets_ARCH_TEST'.
2003-11-05 12:36:27.89 spid15 Starting up
database 'dbWheelsets_BACKUP'.
2003-11-05 12:36:27.98 spid17 Starting up
database 'dbWheelsets_DATA_TEST'.
2003-11-05 12:36:28.43 spid5 Clearing tempdb database.
2003-11-05 12:36:28.51 spid11 Analysis of
database 'dbWheelset_Live' (7) is 100% complete
(approximately 0 mo
2003-11-05 12:36:28.65 spid12 Analysis of
database 'powerway' (8) is 100% complete (approximately 0
more seco
2003-11-05 12:36:28.87 server SQL Server is ready for
client connections
2003-11-05 12:36:28.87 server SQL server listening on
172.20.120.23:1433, 127.0.0.1:1433.
2003-11-05 12:36:28.87 server SQL server listening on
TCP, Shared Memory, Named Pipes.
2003-11-05 12:36:29.76 spid13 Analysis of
database 'dbWheelSets_TEST' (9) is 100% complete
(approximately 0 m
2003-11-05 12:36:38.67 spid5 Starting up
database 'tempdb'.
2003-11-05 12:36:41.85 spid2 Recovery complete.
2003-11-05 12:36:49.51 spid51 Using 'xpsqlbot.dll'
version '2000.80.194' to execute extended stored procedure
2003-11-05 12:36:51.96 spid51 Using 'xpstar.dll'
version '2000.80.194' to execute extended stored
procedure '
2003-11-05 13:15:27.45 spid55 Using 'sqlimage.dll'
version '4.0.5'...
2003-11-05 13:15:27.46 spid55 SqlDumpExceptionHandler:
Process 55 generated fatal exception c0000005 EXCEPTIO
2003-11-05 13:15:27.46 spid55 Error: 0, Severity: 19,
State: 0
410735 D0 Module(UMS+000035D0) (ProcessWorkRequests
(class UmsWorkQueue *)+00000264)
4107382 C Module(UMS+0000382C) (ThreadStartRoutine
(void *)+000000BC)
7 C57B382 Module(KERNEL32+0000B382)
(lstrcmpiW+000000B7)
78008454 Module(MSVCRT+00008454)
(_endthread+000000C1)Have you tried running DBCC CHECKDB
--
HTH
Ryan Waight, MCDBA, MCSE
"john kinghorn" <anonymous@.discussions.microsoft.com> wrote in message
news:076a01c3a787$7e28ea20$a401280a@.phx.gbl...
> One of our customers has SQl server 2000 installed
> This has been working perfectly untill last Friday.
> At this point various databases began to return errors
> when querries were run on the data.
> There appeasr to be no pattern to which databases still
> work as I have two backup copies of the main databse they
> use. The main one and one of the backups produce errors
> yet the other backup, taken on the same day does not.
> Looking at the error log (attached) there seems to be a
> lot of "corrupt" entires.
> Any suggestions
>
> Date Source Message
> ---
> --
> ---
> --...
> 004 DC771 Module(sqlservr+000DC771) (ExecuteSql
> (class CParamExchange *,class CXVariant *,
> 004 A9DE2 Module(sqlservr+000A9DE2)
> (CXteHashMatch::ExecCompile(class CExecCompContext *)
> 004 A9E93 Module(sqlservr+000A9E93)
> (CXteHashMatch::ExecCompile(class CExecCompContext *)
> 004 A70B6 Module(sqlservr+000A70B6)
> (CXteHashMatch::IntermediateCompile(class IMemObj *,c
> 004 A8B35 Module(sqlservr+000A8B35)
> (CXteHashMatch::CreateBailoutPlan(class CRemapContext
> 0041 F796 Module(sqlservr+0001F796)
> (CSQLObject::FTransform(class CParamExchange *)+00000
> 0041 FDDD Module(sqlservr+0001FDDD)
> (CSQLObject::FTransform2(class CSQLComment *,class CP
> 00415080 Module(sqlservr+00015080)
> (CSQLSource::FTransform(class CParamExchange *)
> +0000037C)
> 0041534 F Module(sqlservr+0001534F)
> (CSQLSource::Execute(class CParamExchange *)+00000176
> 00415410 Module(sqlservr+00015410)
> (CSQLSource::Execute(class CParamExchange *)
> +00000343)
> 00415765 Module(sqlservr+00015765)
> (CMsqlExecContext::Execute(class CCompPlan *,class
> CParamExchange *)+000001C7)
> 004160 DB Module(sqlservr+000160DB)
> (CMsqlExecContext::ExecuteStmts(class ExecutionContex
> 0041767 E Module(sqlservr+0001767E) (process_commands
> (struct srv_proc *)+000001E7)
> 0043 B7EF Module(sqlservr+0003B7EF) (execute_rpc
> (struct srv_proc *)+00000019)
> 00447078 Module(sqlservr+00047078)
> (CCompPlan::FCompileStep(class CAlgStmt *,class
> CStatement * *)+00000AE7)
> 004510 FE Module(sqlservr+000510FE)
> (CProchdr::FCompile(class CCompPlan *,class CParamExc
> 0049 CB9F Module(sqlservr+0009CB9F)
> (CStmtExec::XretExecute(class CMsqlExecContext *)cons
> 0049 CD0A Module(sqlservr+0009CD0A)
> (CStmtExec::XretLocalExec(class CMsqlExecContext *,un
> 0049 C6F4 Module(sqlservr+0009C6F4)
> (CSQLObject::FGetFromDisk(class CParamExchange *)+000
> 0049 DA48 Module(sqlservr+0009DA48)
> (CStmtSelect::Init(class CAlgStmt *,class CCompPlan *
> 00563 F78 Module(sqlservr+00163F78)
> (CStmtQuery::InitQuery(class CAlgStmt *,class CCompPl
> 00564019 Module(sqlservr+00164019)
> (BuildQueryFromTree(class TREE *,class IMemObj
> *,class IMemObj *,class IQueryOb
> 005642 CD Module(sqlservr+001642CD)
> (CCvtTree::PqryFromTree(class TREE *,class IMemObj *,
> 0056701 F Module(sqlservr+0016701F)
> (CBndOutputs::RemapValrefs(class CRemapContext *,int)
> 00567536 Module(sqlservr+00167536)
> (CXte::ExecCompile(class CExecCompContext *)
> +000000B7)
> 00567536 Module(sqlservr+00167536)
> (CXte::ExecCompile(class CExecCompContext *)
> +000000B7)
> 005688 A4 Module(sqlservr+001688A4) (CQuery::Prepare
> (void)+00000116)
> 0061 DDB6 Module(sqlservr+0021DDB6)
> (CSpecProc::Execute(class CParamExchange *)+00000092)
> 0061 DA3E Module(sqlservr+0021DA3E)
> (CSpecProc::ExecuteSpecial(class CParamExchange *,uns
> 0063 C71D Module(sqlservr+0023C71D) (execrpc(struct
> srv_proc *)+000004A8)
> 00703 A1C Module(sqlservr+00303A1C)
> (CXteHashMatch::CreateInputScan(class IMemObj *,class
> 2003-11-05 12:36:10.29 server Microsoft SQL Server
> 2000 - 8.00.194 (Intel X86) ...
> 2003-11-05 12:36:10.54 server Logging SQL Server
> messages in file 'd:\Program Files\Microsoft SQL
> Server\MSSQ
> 2003-11-05 12:36:10.54 server Server Process ID is 1700.
> 2003-11-05 12:36:10.54 server All rights reserved.
> 2003-11-05 12:36:10.54 server Copyright (C) 1988-2000
> Microsoft Corporation.
> 2003-11-05 12:36:10.99 server SQL Server is starting at
> priority class 'normal'(4 CPUs detected).
> 2003-11-05 12:36:13.00 server SQL Server configured for
> thread mode processing.
> 2003-11-05 12:36:13.23 server Using dynamic lock
> allocation. [2500] Lock Blocks, [5000] Lock Owner Blocks.
> 2003-11-05 12:36:13.62 server Attempting to initialize
> Distributed Transaction Coordinator.
> 2003-11-05 12:36:19.92 spid2 Starting up
> database 'master'.
> 2003-11-05 12:36:27.70 spid5 Starting up
> database 'model'.
> 2003-11-05 12:36:27.70 server Using 'SSNETLIB.DLL'
> version '8.0.194'.
> 2003-11-05 12:36:27.73 spid2 Server name is 'WRLW2S002'.
> 2003-11-05 12:36:27.79 spid12 Starting up
> database 'powerway'.
> 2003-11-05 12:36:27.79 spid11 Starting up
> database 'dbWheelset_Live'.
> 2003-11-05 12:36:27.79 spid10 Starting up
> database 'Northwind'.
> 2003-11-05 12:36:27.79 spid9 Starting up
> database 'pubs'.
> 2003-11-05 12:36:27.79 spid8 Starting up
> database 'msdb'.
> 2003-11-05 12:36:27.81 spid14 Starting up
> database 'dbWheelSets_LIVE'.
> 2003-11-05 12:36:27.81 spid13 Starting up
> database 'dbWheelSets_TEST'.
> 2003-11-05 12:36:27.89 spid16 Starting up
> database 'dbWheelsets_ARCH_TEST'.
> 2003-11-05 12:36:27.89 spid15 Starting up
> database 'dbWheelsets_BACKUP'.
> 2003-11-05 12:36:27.98 spid17 Starting up
> database 'dbWheelsets_DATA_TEST'.
> 2003-11-05 12:36:28.43 spid5 Clearing tempdb database.
> 2003-11-05 12:36:28.51 spid11 Analysis of
> database 'dbWheelset_Live' (7) is 100% complete
> (approximately 0 mo
> 2003-11-05 12:36:28.65 spid12 Analysis of
> database 'powerway' (8) is 100% complete (approximately 0
> more seco
> 2003-11-05 12:36:28.87 server SQL Server is ready for
> client connections
> 2003-11-05 12:36:28.87 server SQL server listening on
> 172.20.120.23:1433, 127.0.0.1:1433.
> 2003-11-05 12:36:28.87 server SQL server listening on
> TCP, Shared Memory, Named Pipes.
> 2003-11-05 12:36:29.76 spid13 Analysis of
> database 'dbWheelSets_TEST' (9) is 100% complete
> (approximately 0 m
> 2003-11-05 12:36:38.67 spid5 Starting up
> database 'tempdb'.
> 2003-11-05 12:36:41.85 spid2 Recovery complete.
> 2003-11-05 12:36:49.51 spid51 Using 'xpsqlbot.dll'
> version '2000.80.194' to execute extended stored procedure
> 2003-11-05 12:36:51.96 spid51 Using 'xpstar.dll'
> version '2000.80.194' to execute extended stored
> procedure '
> 2003-11-05 13:15:27.45 spid55 Using 'sqlimage.dll'
> version '4.0.5'...
> 2003-11-05 13:15:27.46 spid55 SqlDumpExceptionHandler:
> Process 55 generated fatal exception c0000005 EXCEPTIO
> 2003-11-05 13:15:27.46 spid55 Error: 0, Severity: 19,
> State: 0
> 410735 D0 Module(UMS+000035D0) (ProcessWorkRequests
> (class UmsWorkQueue *)+00000264)
> 4107382 C Module(UMS+0000382C) (ThreadStartRoutine
> (void *)+000000BC)
> 7 C57B382 Module(KERNEL32+0000B382)
> (lstrcmpiW+000000B7)
> 78008454 Module(MSVCRT+00008454)
> (_endthread+000000C1)
>

Connection fails and currupt log

One of our customers has SQL server 2000 installed
This has been working perfectly for over a year
Now various databases have started to return errors when queries are
run on the data from VB or Query Analyser.
A typical error is:
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckForData
(CheckForData()).
Server: Msg 11, Level 16, State 1, Line 0
General Network Error. Check your network documentation
Connection broken
Not all the database produce errors but there appears to be no pattern
to which databases still work.
I have two backup copies of the main database they use. The main
database its self and one of the backups produce errors yet the other
backup, taken on the same day does not.
Looking at the error log (attached) there seems to be a lot of
"corrupt" entires.
Any suggestions* If you see corruption, then --
1. Check system and app event logs for details on any hardware corruption.
2. contact your hardware vendors to run some tests, diagnostics, etc and
also check for firmware upgrades.
3. Only then, RESTORE from your last healthy SQL Backup.
4. If you dont have a backup, then you could try to "Repair" the database
using "dbcc checkdb".
Thanks,
Vikram
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.

Connection Error in Sql server 2005

the site having connection problem like. It will work perfectly for the 20 or 30 days after that sql server gives error on openning connection.

Then i have to restart the server. wt could be the problem of

With regrds

B anna

What are the error messages you are seeing? Are you seeing them on all client machines or just a subset of them? What edition of SQL 2005 are you using? Any additional info would be great to help debug. Thanks!

Thanks,
Sam Lester (MSFT)