Odbc error

Dear all
My one user has installed sql server 2000 enterprise edition , SP3
(8.00.0860) on my computer.
I have created one odbc connection to sql server.
When he want to connect to sql user via odbc in application he gets
following error
Statement(s) could not be prepared
Unable to close cursor
[Microsoft][ODBC SQL Server Driver]Invalid cursor stat
What can be the problem?
RegardsWhat language is the application written in? At least the failing module?
I have seen similar errors in both T/SQL (implying a Stored Procedure) and C
(api level calls) modules.
I suspect it needs to be relinked with your new modules. To me, it sounds
like the api calls either are for a different ODBC release or have messed up
pointers.
If you can supply error numbers and complete error messages, it woulld help
--
Joseph R.P. Maloney, CSP,CCP,CDP
"amish" wrote:
> Dear all
> My one user has installed sql server 2000 enterprise edition , SP3
> (8.00.0860) on my computer.
> I have created one odbc connection to sql server.
> When he want to connect to sql user via odbc in application he gets
> following error
> Statement(s) could not be prepared
> Unable to close cursor
> [Microsoft][ODBC SQL Server Driver]Invalid cursor stat
> What can be the problem?
> Regards
>

ODBC connection to remote computer giving invalid instance() message

I am trying to set up a ODBC connection to a remote database using the ODBC data source administrator. I am getting an error message complaining of an invalid instance(). The database I am trying to connect to does have a default instance and a named instance. Do I need to specify the instance name somewhere in the connection settings? I tried specifying the server name as <Remote computer IP Address>/<Instance Name> but this didn't work. Any ideas?Hi,

make sure SQL Server Browser is running, otherwise you will have to name the port after the service name like in:

Data Source=Servername,SomePortnumber --> Data Source=SomeServer,1455 (e.g. for any non-default port settings)

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de|||

Note that it should be "<Remote computer IP Address>\<Instance Name>" rather than "<Remote computer IP Address>/<Instance Name>".

Can you connect to the default instance? What protocols are enabled? What's the actual error msg? Any firewall issue? Search firewall and browser posts on the forum would help.

|||Thanks for ideas. I think I needed to sleep on this one a bit! I looked at it again this morning and unticked the 'dynamically determine port' option in the network lib config of the ODBC connection setup and specified the port no. the instance is listening on. This worked!

ODBC connection to a seperate machine

I'm curious, can you set up a ODBC connection on one server, that points
to another computer on the network where the database is? I've tried
the computer name as //server2, but it doesn't seem to find it, yet, I
can get to it via the RDC within WinXP Pro.
Thanks,
Steve"Steve Grosz" <boise_bound@.hotmail.com> wrote in message
news:eZknx$7UEHA.2520@.TK2MSFTNGP10.phx.gbl...
> I'm curious, can you set up a ODBC connection on one server, that points
> to another computer on the network where the database is? I've tried
> the computer name as //server2, but it doesn't seem to find it, yet, I
> can get to it via the RDC within WinXP Pro.
I do not believe that is allowed as which security credentials would be used
from the ODBC connection from server1 to server2? There are work-arounds,
for example you could use a linked server from SQL Server (say on server1)
and access the database on server2 from server1.
Stevesql

ODBC connection to a seperate machine

I'm curious, can you set up a ODBC connection on one server, that points
to another computer on the network where the database is? I've tried
the computer name as //server2, but it doesn't seem to find it, yet, I
can get to it via the RDC within WinXP Pro.
Thanks,
Steve
"Steve Grosz" <boise_bound@.hotmail.com> wrote in message
news:eZknx$7UEHA.2520@.TK2MSFTNGP10.phx.gbl...
> I'm curious, can you set up a ODBC connection on one server, that points
> to another computer on the network where the database is? I've tried
> the computer name as //server2, but it doesn't seem to find it, yet, I
> can get to it via the RDC within WinXP Pro.
I do not believe that is allowed as which security credentials would be used
from the ODBC connection from server1 to server2? There are work-arounds,
for example you could use a linked server from SQL Server (say on server1)
and access the database on server2 from server1.
Steve

ODBC connection for client application to SQL Server 2005 Express installed on network computer

Hi All,

I've developed an application that connects to a SQL Server 2005 Express database. I created a DSN to connect to the database through ODBC. Currently, I am testing locally and everything works fine.

I would now like to install my application on another workstation and connect remotely to the database located on my development machine.

The client workstation does not have SQL Server 2005 Express installed on it because I would just like my application to connect remotely by creating the DSN and using ODBC. What I'm missing here are the database drivers. The "SQL Natice Client" is not available on this client workstation. How can I deploy the necessary drivers with my installation file so that I may create the required DSN name using the SQL Native Client driver?

Thanks!
Deployment of the SNAC can be found here:

http://msdn2.microsoft.com/en-us/library/ms131334.aspx

If you don′t use the new features of SQL Server 2005, you can also use the MDAC driver which is compatible with the Pre SQL 2005 features of SQL Server 2005.

My best practice is not to use the DSN rather than using direct connection strings which can be configured in configuration files.

HTH, Jens SUessmeyer.

http://www.sqlserver2005.de
|||Thanks for the reply.

I can't seem to find the sqlncli.msi file on my drive. I have the Express edition installed. Is there somewhere else I can find this installer for the SNAC driver?

If not, which version of MDAC do I need, and how would I build my DSN? I agree with using connection strings instead of DSN's, unfortunately that is a decision I'm unable to change.

|||

SNAC: http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=d09c1d60-a13c-4479-9b91-9e8b9d835cdc
it

Just get the newest MDAC, since it makes no difference if you get 2.7 or 2.8 but getting the newest will keep you away from old bugs :-)

The connectionstrings can be found on www.connectionstring.com (Where I also posted an example for the SNAC one :-) )

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

|||Excellent,

I got it working using MDAC.

Thanks!

Obtain "trusted connection" ?

Hi all!

I have a new computer, clean, I installed WinXP, and I want to connect a SQL Server (other computer in the same network)
For this I installed the client tools from SQL SERVER 2000 kit. Ok.
When I try to connect to the server, I can't connect through "trusted connection", only whit user name and password.
I mention that I set the sql server in mixed mode autentification.

When I try to connect from other computer (my laptop, or other computer from this network) I can connect both types of connection: trusted and with

sa (for example)

The question is:

How I can set up a "trusted connection" at SQL Server?

The computer is completely new, clean and has win xp with sp2.

Any opinion are considered.

Thanks in advance.

koci.You still need to add the login of the trusted connection to the server logins and grant it permission to use specific databases. SQL Server will not let you in purely on good looks and charm, even in the "trusted" mode.|||SQL Server will not let you in purely on good looks and charm, even in the "trusted" mode.

I have it on good authority that SQL Server will let you in if you know how to mix a good margarita. :D

Regards,

hmscott|||Thank's for the answers, I solved the problem.:)