Driver''s SQLSetConnectAttr failed from script component

Hi

I am currently trying to get a script component to write data into a openedge database.

I am stumped by the below message.

Validation error. Bulk Load ProjPeriod Bplan: Script Component [9378]: System.Data.Odbc.OdbcException:

ERROR [HYC00] [DataDirect][ODBC Progress OpenEdge Wire Protocol driver]Optional feature not implemented. ERROR [HY000] [DataDirect][ODBC Progress OpenEdge Wire Protocol driver][OPENEDGE]Server rejects connection on attach.

ERROR [IM006] [DataDirect][ODBC Progress OpenEdge Wire Protocol driver]Driver's SQLSetConnectAttr failed. ERROR [HYC00] [DataDirect][ODBC Progress OpenEdge Wire Protocol driver]Optional feature not implemented. ERROR [HY000] [DataDirect][ODBC Progress OpenEdge Wire Protocol driver][OPENEDGE]Server rejects connection on attach.

ERROR [IM006] [DataDirect][ODBC Progress OpenEdge Wire Protocol driver]Driver's SQLSetConnectAttr failed. at Microsoft.SqlServer.Dts.Pipeline.ScriptComponentHost.HandleUserException(Exception e) at Microsoft.SqlServer.Dts.Pipeline.ScriptComponentHost.AcquireConnections(Object transaction) at Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostAcquireConnections(IDTSManagedComponentWrapper90 wrapper, Object transaction) Package.dtsx 0 0

The two areas’ that I have found that might be causing this is transaction and codepage, however I have tried setting these appropriately with no success.

Any help would be much appreciated.

Cheers,

Ken C

Does the connection work correctly if you use the connection manager from a DataReader source?

|||

Hi jwelch

As far as I can tell, using this connection from connection manager with Datareader does work.

I created the connection and used in a datareader and it displayed the field names from the supplied sql.

Cheers,

Ken

|||

Hi Again

A bit wierd.... I changed the Fetch Array Size, in the odbc connection to 0 .....this seemed to remove the error from ssis. (This seemed to work for somone else connecting to Oracle db)

Since then i have put the value back to 50 and the error messege has not returned ?

Will develop futher and post back

Cheers

driver's sqlallochandle on sql_handle_env failed

i have just installed sql clinet
(Microsoft SQL Enterprise Manager Microsoft Corporation Version: 8.0)
on windows XP sp2 . whenever i try to reg new sql servers through Enterprise
Mgr it gives me this error . it looks like its associated with ODBC . need to
figure out whats the problem
Thanks & Regards
Sid
Try applying SQL Server 2000 SP4 + Cumulative Hotfix Build 2187.
http://www.microsoft.com/downloads/details.aspx?FamilyID=8e2dfc8d-c20e-4446-99a9-b7f0213f8bc5&DisplayLang=en
http://www.microsoft.com/downloads/details.aspx?FamilyID=9c9ab140-bdee-44df-b7a3-e6849297754a&displaylang=en
http://www.microsoft.com/downloads/details.aspx?FamilyID=1705bd2f-1fb8-4ec8-b3db-0935361308c7&displaylang=en
http://www.microsoft.com/downloads/details.aspx?familyid=A643980A-26A4-44C1-9B50-53E20E7210B5&displaylang=en
http://www.microsoft.com/downloads/details.aspx?FamilyId=243A8A89-74D6-48FD-933F-32FF9D8459C2&displaylang=en
http://www.microsoft.com/downloads/details.aspx?FamilyId=2BB62F35-D041-42AC-98DA-6EC97168BE21&displaylang=en
Sincerely,
Anthony Thomas

"moharil" <sid_m15@.yahoo.com> wrote in message
news:DCFB87D2-813A-4707-8D8B-9EDB6E781058@.microsoft.com...
> i have just installed sql clinet
> (Microsoft SQL Enterprise Manager Microsoft Corporation Version: 8.0)
> on windows XP sp2 . whenever i try to reg new sql servers through
Enterprise
> Mgr it gives me this error . it looks like its associated with ODBC . need
to
> figure out whats the problem
> --
> Thanks & Regards
> Sid

Driver's SQLAllocHandle on SQL_HANDLE_DBC failed error

I am seeing a few of the below listed error message on our application
servers that are connecting to our SQL 2005 servers. What do they mean and
how can I resolve them ?
[Microsoft][ODBC Driver Manager] Driver's SQLAllocHandle on SQL_HANDLE_DBC
failed
Hi
You can call SQLGetDiagRec with a HandleType of SQL_HANDLE_DBC and a Handle
of you ConnectionHandle to get more information about the error. See
http://msdn2.microsoft.com/en-us/library/ms711810.aspx
John
"Hassan" wrote:

> I am seeing a few of the below listed error message on our application
> servers that are connecting to our SQL 2005 servers. What do they mean and
> how can I resolve them ?
> [Microsoft][ODBC Driver Manager] Driver's SQLAllocHandle on SQL_HANDLE_DBC
> failed
>
>
>

Driver's SQLAllocHandle on SQL_HANDLE_DBC failed error

I am seeing a few of the below listed error message on our application
servers that are connecting to our SQL 2005 servers. What do they mean and
how can I resolve them ?
[Microsoft][ODBC Driver Manager] Driver's SQLAllocHandle on SQL_HAND
LE_DBC
failedHi
You can call SQLGetDiagRec with a HandleType of SQL_HANDLE_DBC and a Handle
of you ConnectionHandle to get more information about the error. See
http://msdn2.microsoft.com/en-us/library/ms711810.aspx
John
"Hassan" wrote:

> I am seeing a few of the below listed error message on our application
> servers that are connecting to our SQL 2005 servers. What do they mean and
> how can I resolve them ?
> [Microsoft][ODBC Driver Manager] Driver's SQLAllocHandle on SQL_HA
NDLE_DBC
> failed
>
>
>

Driver's SQLAllocHandle on SQL_HANDLE_DBC failed error

I am seeing a few of the below listed error message on our application
servers that are connecting to our SQL 2005 servers. What do they mean and
how can I resolve them ?
[Microsoft][ODBC Driver Manager] Driver's SQLAllocHandle on SQL_HANDLE_DBC
failedHi
You can call SQLGetDiagRec with a HandleType of SQL_HANDLE_DBC and a Handle
of you ConnectionHandle to get more information about the error. See
http://msdn2.microsoft.com/en-us/library/ms711810.aspx
John
"Hassan" wrote:
> I am seeing a few of the below listed error message on our application
> servers that are connecting to our SQL 2005 servers. What do they mean and
> how can I resolve them ?
> [Microsoft][ODBC Driver Manager] Driver's SQLAllocHandle on SQL_HANDLE_DBC
> failed
>
>
>

Drivers for DTS to Oracle

If I want to use DTS export table to Oracle from SQL Server, what all
drivers I need. One is I believe MS ODBC Driver to connect to Oracle.
Does any other Oracle client library required.
You are going to need the Oracle client drivers from Oracle also as I
remember (SQL *Net)

Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.SQLIS.com - You thought DTS was good. here we show you the new stuff.
www.konesans.com - Consultancy from the people who know
"Data Cruncher" <dcruncher4@.netscape.net> wrote in message
news:1119907568.126869.35880@.g43g2000cwa.googlegro ups.com...
> If I want to use DTS export table to Oracle from SQL Server, what all
> drivers I need. One is I believe MS ODBC Driver to connect to Oracle.
> Does any other Oracle client library required.
>

Drivers for DTS to Oracle

If I want to use DTS export table to Oracle from SQL Server, what all
drivers I need. One is I believe MS ODBC Driver to connect to Oracle.
Does any other Oracle client library required.You are going to need the Oracle client drivers from Oracle also as I
remember (SQL *Net)
Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.SQLIS.com - You thought DTS was good. here we show you the new stuff.
www.konesans.com - Consultancy from the people who know
"Data Cruncher" <dcruncher4@.netscape.net> wrote in message
news:1119907568.126869.35880@.g43g2000cwa.googlegroups.com...
> If I want to use DTS export table to Oracle from SQL Server, what all
> drivers I need. One is I believe MS ODBC Driver to connect to Oracle.
> Does any other Oracle client library required.
>

Drivers for DTS to Oracle

If I want to use DTS export table to Oracle from SQL Server, what all
drivers I need. One is I believe MS ODBC Driver to connect to Oracle.
Does any other Oracle client library required.You are going to need the Oracle client drivers from Oracle also as I
remember (SQL *Net)
Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.SQLIS.com - You thought DTS was good. here we show you the new stuff.
www.konesans.com - Consultancy from the people who know
"Data Cruncher" <dcruncher4@.netscape.net> wrote in message
news:1119907568.126869.35880@.g43g2000cwa.googlegroups.com...
> If I want to use DTS export table to Oracle from SQL Server, what all
> drivers I need. One is I believe MS ODBC Driver to connect to Oracle.
> Does any other Oracle client library required.
>

Driver to connect to Informix via DTS?

Hi, folks!

I want to pump data from Informix to SQL Server using DTS to fill / fresh up my SQL-Server data warehouse every day.

In the SQL documentation I found "Don't use the ODBC driver from Informix"

Which is a good choice of ODBC/OLE-DB drivers to deal with Informix via SQL servers DTS?

Regards from Berlin!

SeBaFluDownload Informix driver from IBM website and set it up on your machine to create a DTS package. I have used it to create a DTS package and run it for over a year now.|||What was the error with current driver?
That was a general recommendation, but to followup the data import/export as referred comaptible driver must be used.|||Hi, Joe!

Originally posted by joejcheng
Download Informix driver from IBM website and set it up on your machine to create a DTS package. I have used it to create a DTS package and run it for over a year now.

OK, let's try it <s>...

... but may be I'm stupid - but I can't find any ODBC driver at the IBM site - can You advice me to the related URL?

Many thanx from Berlin!

SeBaFlu

Driver questions running with DB2 as datasource

I need some help and feedbacks from other users that are currently running Reporting Services using DB2 as a database. I have been testing OLE DB and ODBC from Microsoft and IBM, and recently DB2 .Net Data provider from IBM.

We are currently running DB2 on z/os v 7, gateway v.8 fixpack 10. We will mainly be calling Stored Procedures on the DB2 and passing recordsets back to the client.

First I installed IBM DB2 ODBC DRIVER v. 7.01.00.88, but I did not get this too work with reporting Services calling Stored Procedures, so I had too upgrade the driver to v8.01.10.812 to get it to work.

I have been in contact with Microsoft and they recommend using Microsoft OLE DB Provider for DB2 (30.sept 2005). I have tried too get this driver too work but I have problems configuring it. I think that it has something too do with some packages that the driver tries too create on DB2. I get error messages both on the DB2 and in the Data access Tool that runs a wizard setting up the driver. '—The package creation process has failed on resource "mytest", Data description mismatch SQLSTATE:HY000, SQLCODE: -292'

IBM have also developed a IBM DB2 Data provider for .Net Framework 2.0. This is the only driver that I can use too browse the database in the Server Explorer in VS. If you edit the RSReportDesigner.config file you can also use this driver in Report Server projects. Just add <Extension Name="DB2" Type="IBM.Data.DB2.DB2Connection,IBM.Data.DB2, Version=9.0.0.2, Culture=neutral, PublicKeyToken=7c307b91aa13d208" /> too the data section of the xml file.

So too wrap it all up. Which provider should I use? Are there any recommendations out there?

Thanks

B

well i've a question.

how to get IBM DB2 Data Provider for .Net Framework 2.0

Driver questions running with DB2 as datasource

I need some help and feedbacks from other users that are currently running Reporting Services using DB2 as a database. I have been testing OLE DB and ODBC from Microsoft and IBM, and recently DB2 .Net Data provider from IBM.

We are currently running DB2 on z/os v 7, gateway v.8 fixpack 10. We will mainly be calling Stored Procedures on the DB2 and passing recordsets back to the client.

First I installed IBM DB2 ODBC DRIVER v. 7.01.00.88, but I did not get this too work with reporting Services calling Stored Procedures, so I had too upgrade the driver to v8.01.10.812 to get it to work.

I have been in contact with Microsoft and they recommend using Microsoft OLE DB Provider for DB2 (30.sept 2005). I have tried too get this driver too work but I have problems configuring it. I think that it has something too do with some packages that the driver tries too create on DB2. I get error messages both on the DB2 and in the Data access Tool that runs a wizard setting up the driver. '—The package creation process has failed on resource "mytest", Data description mismatch SQLSTATE:HY000, SQLCODE: -292'

IBM have also developed a IBM DB2 Data provider for .Net Framework 2.0. This is the only driver that I can use too browse the database in the Server Explorer in VS. If you edit the RSReportDesigner.config file you can also use this driver in Report Server projects. Just add <Extension Name="DB2" Type="IBM.Data.DB2.DB2Connection,IBM.Data.DB2, Version=9.0.0.2, Culture=neutral, PublicKeyToken=7c307b91aa13d208" /> too the data section of the xml file.

So too wrap it all up. Which provider should I use? Are there any recommendations out there?

Thanks

B

well i've a question.

how to get IBM DB2 Data Provider for .Net Framework 2.0

Driver Not Capable - Error

I'm getting this error and I don't know where to begin. Our environment is
SQL Server 2000 sp3a on Win Server 2003.
I get the error when running an insert statement in a sql job that executes
as the admin. The insert is a simple one from one table to another.
Ultimately, I need to insert from a VIEW that is set up w/ a linked server
pulling data from FoxPro.
Here is the error message:
Executed as user: DOMAIN\admin. The operation could not be performed because
the OLE DB provider 'MSDASQL' was unable to begin a distributed transaction.
[SQLSTATE 42000] (Error 7391) Driver not capable] [SQLSTATE 01000] (Error
7312) OLE DB error trace [OLE/DB Provider 'MSDASQL'
ITransactionJoin::JoinTransaction returned 0x8004d00a]. [SQLSTATE 01000]
(Error 7300). The step failed.
I made a change a few days ago to resolve a memory issue. The change was I
disabled Allow InProcess on the OLE DB for ODBC Drivers provider. Doesn't
seem like this error would be related and I haven't been able to prove
otherwise when enabling the option, for instance.
Any help is appreciated. Thank you, PhilNo resolution yet but I believe the problem is in a trigger on the table I a
m
inserting to. The trigger has sql code that uses views built on a linked
server getting data from foxpro.
"phil" wrote:

> I'm getting this error and I don't know where to begin. Our environment i
s
> SQL Server 2000 sp3a on Win Server 2003.
> I get the error when running an insert statement in a sql job that execute
s
> as the admin. The insert is a simple one from one table to another.
> Ultimately, I need to insert from a VIEW that is set up w/ a linked server
> pulling data from FoxPro.
> Here is the error message:
> Executed as user: DOMAIN\admin. The operation could not be performed becau
se
> the OLE DB provider 'MSDASQL' was unable to begin a distributed transactio
n.
> [SQLSTATE 42000] (Error 7391) Driver not capable] [SQLSTATE 01000] (Error
> 7312) OLE DB error trace [OLE/DB Provider 'MSDASQL'
> ITransactionJoin::JoinTransaction returned 0x8004d00a]. [SQLSTATE 01000]
> (Error 7300). The step failed.
> I made a change a few days ago to resolve a memory issue. The change was
I
> disabled Allow InProcess on the OLE DB for ODBC Drivers provider. Doesn't
> seem like this error would be related and I haven't been able to prove
> otherwise when enabling the option, for instance.
> Any help is appreciated. Thank you, Phil

Driver Install Location

I have read most of the documentation on installing the JDBC driver and need
a bit of clarification on what and where files gets installed.
First: Am I correct to assume that installation takes place on the client
machine and than NO files are actually installed on the server hosting SQL
Server?
Second: If the JRE is installed on the client, is it only the class jars,
msutil.jar, mssqlserver.jar, msbase.jar that are responsible for enabling the
JDBC connection.
Kind regards for any reply
| Thread-Topic: Driver Install Location
| thread-index: AcS7ky47eyc/czQMQSKYX1iOSRQzOQ==
| X-WBNR-Posting-Host: 24.169.110.115
| From: "=?Utf-8?B?Q2hyaXM=?=" <Chris@.discussions.microsoft.com>
| Subject: Driver Install Location
| Date: Tue, 26 Oct 2004 12:37:08 -0700
| Lines: 12
| Message-ID: <E20ADC31-1528-4F55-8A5A-C3FE05250257@.microsoft.com>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.public.sqlserver.jdbcdriver
| NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
| Path: cpmsftngxa10.phx.gbl!TK2MSFTNGXA03.phx.gbl
| Xref: cpmsftngxa10.phx.gbl microsoft.public.sqlserver.jdbcdriver:6425
| X-Tomcat-NG: microsoft.public.sqlserver.jdbcdriver
|
| I have read most of the documentation on installing the JDBC driver and
need
| a bit of clarification on what and where files gets installed.
|
| First: Am I correct to assume that installation takes place on the client
| machine and than NO files are actually installed on the server hosting
SQL
| Server?
|
| Second: If the JRE is installed on the client, is it only the class jars,
| msutil.jar, mssqlserver.jar, msbase.jar that are responsible for enabling
the
| JDBC connection.
|
| Kind regards for any reply
|
Hello,
The Microsoft JDBC driver is a client installation. You will need to add
the three .jar files to your CLASSPATH on the client machine as well. If
you are using an application server, then the .jar files will need to be
installed on this machine. The installation location and CLASSPATH
configuration steps vary depending on the app server you are using.
The only server component that you may need is the sqljdbc.dll file, which
enables JTA support (transactions). If your application will require this,
then you will need to copy this file from C:\program files\Microsoft SQL
Server 2000 Driver for JDBC\SQLServer JTA\ (or C:\program files\Microsoft
SQL Server 2000 Driver for JDBC\SQLServer JTA 64-bit\ in the case of 64-bit
machines) into the C:\program files\Microsoft SQL Server\MSSQL\Binn\
directory of your SQL Server 2000 installation. Then, you must run the
instjdbc.sql script from C:\program files\Microsoft SQL Server 2000 Driver
for JDBC\SQLServer JTA\ to install the extended stored procedures. You can
use Query Analyzer or osql.exe to run the script.
The JDBC documentation (.pdf) describes the CLASSPATH configuration and JTA
installation in more detail. Look for the following topics:
"Setting the CLASSPATH"
"Installing Stored Procedures for JTA"
Carb Simien, MCSE MCDBA MCAD
Microsoft Developer Support - Web Data
Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection
Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/security.

Driver for paradox

Hi, I'm looking for driver to transfer data for paradox DB to sql DB,
It's the last version of the paradox and the DTS in the sql doesn't
help,
Someone have advice?Hi
The latest Microsoft driver for paradox should be in the latest version of
MDAC, if this is not suitable you should contact Borland.
John
"noam" wrote:

> Hi, I'm looking for driver to transfer data for paradox DB to sql DB,
> It's the last version of the paradox and the DTS in the sql doesn't
> help,
> Someone have advice?
>|||Hi
The latest Microsoft driver for paradox should be in the latest version of
MDAC, if this is not suitable you should contact Borland.
John
"noam" wrote:

> Hi, I'm looking for driver to transfer data for paradox DB to sql DB,
> It's the last version of the paradox and the DTS in the sql doesn't
> help,
> Someone have advice?
>

Driver for paradox

Hi, I'm looking for driver to transfer data for paradox DB to sql DB,
It's the last version of the paradox and the DTS in the sql doesn't
help,
Someone have advice?Hi
The latest Microsoft driver for paradox should be in the latest version of
MDAC, if this is not suitable you should contact Borland.
John
"noam" wrote:
> Hi, I'm looking for driver to transfer data for paradox DB to sql DB,
> It's the last version of the paradox and the DTS in the sql doesn't
> help,
> Someone have advice?
>

Driver caching db?

Hello,
I'm not sure if this message belongs in microsoft.public.sqlserver.msde
or is more appropriate here. Please accept my apologies if I have the
wrong list.
I've written ODBC source in C++ that accesses an MSDE instance on a
local machine. I perform the usual steps:
1. Allocate an SQLHENV
2. Allocate the SQLHDBC
3. Connect
4. Execute a statement to "use " my database
5. Issue a simple query
6. Process results
7. Disconnect SQLHDBC
8. Free SQLHDBC
9. Free SQLHENV
10. Exit application
Then I try to attach to the database in SQL Server Enterprise Manager
which returns the following error:
"Error 5123: CREATE FILE encountered operating system error 32 (The
process cannot access the file because it is being used by another
process.) while attempting to open or create the physical file:
'C:\mydb.mdf'.
Do I need to do something different to force the driver to unload the
database when the application ends?
Thanks,
John
The driver does not touch the database file directly. The SQL Server
process will open (and lock) the database file.
Is the database hosted in a different SQL instance, than the one you are
connecting to in Enterprise Manager?
Brannon
"JohnD" <john_nospam@.tech-testing.com> wrote in message
news:hqpUc.8189$YU1.7939@.newssvr22.news.prodigy.co m...
> Hello,
> I'm not sure if this message belongs in microsoft.public.sqlserver.msde
> or is more appropriate here. Please accept my apologies if I have the
> wrong list.
> I've written ODBC source in C++ that accesses an MSDE instance on a
> local machine. I perform the usual steps:
> 1. Allocate an SQLHENV
> 2. Allocate the SQLHDBC
> 3. Connect
> 4. Execute a statement to "use " my database
> 5. Issue a simple query
> 6. Process results
> 7. Disconnect SQLHDBC
> 8. Free SQLHDBC
> 9. Free SQLHENV
> 10. Exit application
> Then I try to attach to the database in SQL Server Enterprise Manager
> which returns the following error:
> "Error 5123: CREATE FILE encountered operating system error 32 (The
> process cannot access the file because it is being used by another
> process.) while attempting to open or create the physical file:
> 'C:\mydb.mdf'.
> Do I need to do something different to force the driver to unload the
> database when the application ends?
> Thanks,
> John
|||Brannon Jones wrote:
> Is the database hosted in a different SQL instance, than the one you are
> connecting to in Enterprise Manager?
Yes it is. I'm assuming (really I didn't know this...) that this makes
a different?
The application is using a default SQLSERVER instance and the attaching
is occurring in another DBINSTANCE.
|||I don't think you can attach a single database to two different SQL
instances. The first instance that loads the database locks it for
exclusive access. So the second instance that tries to load the database
wont be able to.
Brannon
"JohnD" <john_nospam@.tech-testing.com> wrote in message
news:d6vUc.1687$lY3.1035@.newssvr23.news.prodigy.co m...
> Brannon Jones wrote:
> Yes it is. I'm assuming (really I didn't know this...) that this makes
> a different?
> The application is using a default SQLSERVER instance and the attaching
> is occurring in another DBINSTANCE.
|||Brannon Jones wrote:

> I don't think you can attach a single database to two different SQL
> instances. The first instance that loads the database locks it for
> exclusive access. So the second instance that tries to load the database
> wont be able to.
Which explains why I have to stop the instance in order for the other
instance to attach to it.
Thank you very much Brannon for the clarification.

Driver caching db?

Hello,
I'm not sure if this message belongs in microsoft.public.sqlserver.msde
or is more appropriate here. Please accept my apologies if I have the
wrong list.
I've written ODBC source in C++ that accesses an MSDE instance on a
local machine. I perform the usual steps:
1. Allocate an SQLHENV
2. Allocate the SQLHDBC
3. Connect
4. Execute a statement to "use " my database
5. Issue a simple query
6. Process results
7. Disconnect SQLHDBC
8. Free SQLHDBC
9. Free SQLHENV
10. Exit application
Then I try to attach to the database in SQL Server Enterprise Manager
which returns the following error:
"Error 5123: CREATE FILE encountered operating system error 32 (The
process cannot access the file because it is being used by another
process.) while attempting to open or create the physical file:
'C:\mydb.mdf'.
Do I need to do something different to force the driver to unload the
database when the application ends?
Thanks,
JohnThe driver does not touch the database file directly. The SQL Server
process will open (and lock) the database file.
Is the database hosted in a different SQL instance, than the one you are
connecting to in Enterprise Manager?
Brannon
"JohnD" <john_nospam@.tech-testing.com> wrote in message
news:hqpUc.8189$YU1.7939@.newssvr22.news.prodigy.com...
> Hello,
> I'm not sure if this message belongs in microsoft.public.sqlserver.msde
> or is more appropriate here. Please accept my apologies if I have the
> wrong list.
> I've written ODBC source in C++ that accesses an MSDE instance on a
> local machine. I perform the usual steps:
> 1. Allocate an SQLHENV
> 2. Allocate the SQLHDBC
> 3. Connect
> 4. Execute a statement to "use " my database
> 5. Issue a simple query
> 6. Process results
> 7. Disconnect SQLHDBC
> 8. Free SQLHDBC
> 9. Free SQLHENV
> 10. Exit application
> Then I try to attach to the database in SQL Server Enterprise Manager
> which returns the following error:
> "Error 5123: CREATE FILE encountered operating system error 32 (The
> process cannot access the file because it is being used by another
> process.) while attempting to open or create the physical file:
> 'C:\mydb.mdf'.
> Do I need to do something different to force the driver to unload the
> database when the application ends?
> Thanks,
> John|||Brannon Jones wrote:
> Is the database hosted in a different SQL instance, than the one you are
> connecting to in Enterprise Manager?
Yes it is. I'm assuming (really I didn't know this...) that this makes
a different?
The application is using a default SQLSERVER instance and the attaching
is occurring in another DBINSTANCE.|||I don't think you can attach a single database to two different SQL
instances. The first instance that loads the database locks it for
exclusive access. So the second instance that tries to load the database
wont be able to.
Brannon
"JohnD" <john_nospam@.tech-testing.com> wrote in message
news:d6vUc.1687$lY3.1035@.newssvr23.news.prodigy.com...
> Brannon Jones wrote:
> Yes it is. I'm assuming (really I didn't know this...) that this makes
> a different?
> The application is using a default SQLSERVER instance and the attaching
> is occurring in another DBINSTANCE.|||Brannon Jones wrote:

> I don't think you can attach a single database to two different SQL
> instances. The first instance that loads the database locks it for
> exclusive access. So the second instance that tries to load the database
> wont be able to.
Which explains why I have to stop the instance in order for the other
instance to attach to it.
Thank you very much Brannon for the clarification.

Driver

Hi All,
I’m developing a simple program which will connect to a SQL Server
2000, but when I install the SQL Server I got a message inform me that I
cannot complete, once I check the ODBC drivers I cannot find any of them.
I’m using a Win XP home edition, although I’ve tried to install the
MDAC it inform me that it cannot be run in such version.
Any help, Thanks in advance.
Kind Regards,
MohammadWhat version of MDAC did you try to install? Make sure it's
one of the later versions. You probably want to check your
MDAC installation with component checker as well. You can
download the tool and MDAC versions from:
http://msdn.microsoft.com/data/mdac...ds/default.aspx
-Sue
On Tue, 4 Oct 2005 04:25:02 -0700, "Mohammed"
<Mohammed@.discussions.microsoft.com> wrote:

>Hi All,
> Im developing a simple program which will connect to a SQL Server
>2000, but when I install the SQL Server I got a message inform me that I
>cannot complete, once I check the ODBC drivers I cannot find any of them.
> Im using a Win XP home edition, although Ive tried to install the
>MDAC it inform me that it cannot be run in such version.
> Any help, Thanks in advance.
>Kind Regards,
>Mohammad
>

Driver

Hi All,
I’m developing a simple program which will connect to a SQL Server
2000, but when I install the SQL Server I got a message inform me that I
cannot complete, once I check the ODBC drivers I cannot find any of them.
I’m using a Win XP home edition, although I’ve tried to install the
MDAC it inform me that it cannot be run in such version.
Any help, Thanks in advance.
Kind Regards,
Mohammad
What version of MDAC did you try to install? Make sure it's
one of the later versions. You probably want to check your
MDAC installation with component checker as well. You can
download the tool and MDAC versions from:
http://msdn.microsoft.com/data/mdac/...s/default.aspx
-Sue
On Tue, 4 Oct 2005 04:25:02 -0700, "Mohammed"
<Mohammed@.discussions.microsoft.com> wrote:

>Hi All,
> Im developing a simple program which will connect to a SQL Server
>2000, but when I install the SQL Server I got a message inform me that I
>cannot complete, once I check the ODBC drivers I cannot find any of them.
> Im using a Win XP home edition, although Ive tried to install the
>MDAC it inform me that it cannot be run in such version.
> Any help, Thanks in advance.
>Kind Regards,
>Mohammad
>