Connection objects are not available in DTS Designer

Problem Description: The following error is popping up and not allowing opening or running any of the DTS packages. Connection objects are not available in DTS Designer.

"Error in the DLL"
"Need to run the object to perform this operation"

We have reinstalled the MS SQL Server 2000 Standard Edition with Service pack 3 and MSO3031 hot fix. Still the issue continues.
Operating System:Windows 2000You really should open up an MS ticket for this. It's $250. They don't charge you if it's actually their issue. Are there any other errors in the application, system, or SQL Server error logs?|||Thanks For you help
This seems to be related to MDAC issue. Latest MDAC 2.8 was resolved the problem but it is not clear why the MDAC 2.7 was created the problem.sqlsql

Connection management

hello, I'm using Visual Foxpro and ODBC / sql server 2000.
How should i manage conections ? opening and closing it on each form ? or
opening at the begining of application and closing it at application finish
?
Thanks
Open then close not on each form, but lower.
At each transaction, on add open connection then close it.
On Select open connection then close it.
Joe
"Pedro Jose Caceres" wrote:

> hello, I'm using Visual Foxpro and ODBC / sql server 2000.
> How should i manage conections ? opening and closing it on each form ? or
> opening at the begining of application and closing it at application finish
> ?
> Thanks
>
>

Connection management

hello, I'm using Visual Foxpro and ODBC / sql server 2000.
How should i manage conections ? opening and closing it on each form ? or
opening at the begining of application and closing it at application finish
?
ThanksOpen then close not on each form, but lower.
At each transaction, on add open connection then close it.
On Select open connection then close it.
Joe
"Pedro Jose Caceres" wrote:

> hello, I'm using Visual Foxpro and ODBC / sql server 2000.
> How should i manage conections ? opening and closing it on each form ? or
> opening at the begining of application and closing it at application fini
sh
> ?
> Thanks
>
>

Connection failed:

Hi Guys,

I encountered an error while opening my third SQL Connection in Enterprise Manager

--------
Microsoft SQL Server Login
--------
Connection failed:
SQLState: '01000'
SQL Server Error: 232
[Microsoft][ODBC SQL Server Driver][Shared Memory]ConnectionWrite (WrapperWrite()).
Connection failed:
SQLState: '08S01'
SQL Server Error: 11
[Microsoft][ODBC SQL Server Driver][Shared Memory]General network error. Check your network documentation.

--------
OK
--------

I am using the following
SQL Server 2000 Enterprise Edition (SP4)
Windows 2000 Professional (SP4)

first two connections are with Query Analyzer, the third attempt is when opening a table inside Enterprise Manager

anyone experienced this?Sounds like you have to enable the shared memory protocol for the instance in cliconfg.exe.|||hi MCrowley

yeah, but the problem is, I can't remember what I did (gosh, too much for making experiments :) )

Is there a way on how to reverse this effect?

Thanks|||Is the Shared Memory protocol enabled in Cliconfg.exe?|||Is the Shared Memory protocol enabled in Cliconfg.exe? ;)|||The first thing I would do if I were in your position would be to check the setting of Shared Memory Protocol in cliconfg.exe and make sure it is enabled.

Just my .02 :)|||gosh,

sorry for the very late reply

yes, its enabled, what does this option do by the way?

thanks|||Shared memory is a protocol that can be used by applications running on the same box as SQL Server. Now that it is enabled, do you still get the same error?

Connection and SERVER

Hello Gurus out there!

I want to know what would be the best method in opening a connection to server:

1. a connection (declared globally) that is open once during Login and access thru all forms and be closed only when application is terminated
What is the advantage/disadvantage of this method in my SQL Server 2k resources or in any RDBMS?

2. a connection is opened only when needed but everytime i execute a query against the database i have to open also that connection and terminate when it is not used...What is the advantage/disadvantage of this method in my SQL Server 2k resources or in any RDBMS?

Secondly, how can we know the resources used by the users that are connected to my SQL SERVER in terms of memory usage and CPU?

Im using VB/FOxPro and I want to know the best practice in terms of opening a connection to the database coz Im expecting to have 20 or more users online simultanously and hook to my server as soon as we are finished with our system.

I hope you can light up our minds with these concerns.

Thanks,

bernieIt is most common to maintain a connection for the life of a traditional application. This is because "connecting" takes time, and keeping a session alive (that isn't doing anything at the moment) usually doesn't.

I'm not saying that this is the only way nor the right way but it is commonly done, at least for non-web-based apps.|||Originally posted by sundialsvcs
It is most common to maintain a connection for the life of a traditional application. This is because "connecting" takes time, and keeping a session alive (that isn't doing anything at the moment) usually doesn't.

I'm not saying that this is the only way nor the right way but it is commonly done, at least for non-web-based apps.

Are you trying to say then that I would keep a live connection as long as application is running? Yes, im aware the connection to server takes a quite time thats why i hesitate using On/Off connection because im expecting to use queries frequently in our app esp we are developing an integrated accounting system...

So i would pressume that the SQL Server can accomodate that 30 connections live simultaneously and can execute the same speed to all users...Am I right with my presumption?

THANKS Sundial!!!