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 SQL Server

I use Business Objects XI R2 (BOXI) to report against a SQL Server 2000 database using an ODBC connection.
When I query the database using Enterprise Manager on the server I can make use of all functions available within SQL Server, yet when I access it via the ODBC connection I only get a very small subset of SQL Server functions available.

I can use the inbuilt BOXI functions, which work on the data locally, but would like the functions processed on the server instead.

Is this constraint a property of the ODBC driver, and if so are there other drivers which would expose all of the available SQL Server functions.

Any suggestions appreciated.

Hi Farengi,

When you refer to "functions available within SQL Server", do you mean stored procedures and user-defined functions? Or you mean the GUI-related features like graphic query design?

If we are talking about the stored procs and user-defined functions, there's no limitation per client. In fact, Enterprise Manager uses ODBC under the hood. :-)

However, the stored procs and functions are just database objects - they have permissions granted to them for the appropriate user. Are you using the same login/user in Enterprise Manager as well as in BOXI? In addition, don't forget that the names of the procs and functions is also related to their owner, thus dbo.usp_MyProc is different from JivkoD.usp_MyProc.

If you are referring to the GUI-related features, unfortunately they are specific to the Enterprise Manager and are not exposed to different client applications.

HTH,
Jivko Dobrev - MSFT
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||Hi Jivko,

Thank you for your extensive answer.

Sorry about the delay in responding to you, but I have been attending some advanced BO courses and my question, which I may not have stated correctly, was answered.

The functions I wanted to refer to (eg. max, min, stdev, stdevp, var, varp etc.) in my question, are displayed in the Business Objects sql builder interface only if they are contained in a .prm (parameter) file. This file is supplied with a frequently used subset of sql server functions, but it can be edited and added to. All that this file does is to present a list of functions to the interface.

The functions, which don't appear in the interface, can still be used in a sql statement as long as they are valid functions.

Thanks

ODBC connection to SQL Server

I use Business Objects XI R2 (BOXI) to report against a SQL Server 2000 database using an ODBC connection.
When I query the database using Enterprise Manager on the server I can make use of all functions available within SQL Server, yet when I access it via the ODBC connection I only get a very small subset of SQL Server functions available.

I can use the inbuilt BOXI functions, which work on the data locally, but would like the functions processed on the server instead.

Is this constraint a property of the ODBC driver, and if so are there other drivers which would expose all of the available SQL Server functions.

Any suggestions appreciated.

Hi Farengi,

When you refer to "functions available within SQL Server", do you mean stored procedures and user-defined functions? Or you mean the GUI-related features like graphic query design?

If we are talking about the stored procs and user-defined functions, there's no limitation per client. In fact, Enterprise Manager uses ODBC under the hood. :-)

However, the stored procs and functions are just database objects - they have permissions granted to them for the appropriate user. Are you using the same login/user in Enterprise Manager as well as in BOXI? In addition, don't forget that the names of the procs and functions is also related to their owner, thus dbo.usp_MyProc is different from JivkoD.usp_MyProc.

If you are referring to the GUI-related features, unfortunately they are specific to the Enterprise Manager and are not exposed to different client applications.

HTH,
Jivko Dobrev - MSFT
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||Hi Jivko,

Thank you for your extensive answer.

Sorry about the delay in responding to you, but I have been attending some advanced BO courses and my question, which I may not have stated correctly, was answered.

The functions I wanted to refer to (eg. max, min, stdev, stdevp, var, varp etc.) in my question, are displayed in the Business Objects sql builder interface only if they are contained in a .prm (parameter) file. This file is supplied with a frequently used subset of sql server functions, but it can be edited and added to. All that this file does is to present a list of functions to the interface.

The functions, which don't appear in the interface, can still be used in a sql statement as long as they are valid functions.

Thanks

ODBC Connection to a linked database

I'd like to set up an ODBC DSN to a table in a linked SQL Server, via
my local SQL Server.

I'm having a few problems:
1. When I use Enterprise Manager to link the remote SQL Server, it
doesn't allow me to select the database in the remote server. It only
shows one database.

2. When I use the Data Sources program to set up the ODBC DSN, it only
shows databases in the local SQL Server, not in the linked one. If I
try typing it in: [NAMEOFLINKEDSERVER].databasename - it tells me that
it is an invalid table.Thats quite normal, but you are able to use the four part notation,
which will switch to another database if specified.

E.g. ODBC Connection points automatically to Northwind ( as the default
database of the user) you can use

SELECT <columnlist> FROM Linkdservername.Databasename.Objectname

which switches to the other database to select.

HTH, Jens Suessmeyer.|||Jens,

Thank you.

I'd rather not need to change the table names in the MDB. They just
use the default database of the ODBC Data Source. How can I set the
ODBC default database to be a database in a linked server?|||if you are using a DSN, just go in the ODBC Administrator (of Windows)
and change the database to the ones needed.

HTH, jens Suessmeyer.|||Jens,

Thanks - but the ODBC Adminsitrator only shows *local* databases, not
databases on the linked server. If I try to just type it in, it tells
me that it's not a valid db, and refuses to let me do so!!!|||How did you register the linked server ? Is it a DSN bind linked server
or was it specified within a conneciton string ? ODBC Administrator
doesnt show only the local databases, it shows the servers/databases
that were specified within the DSN. Look at the server ODBC Admin to
see if connection to your linked server is specified (some people look
on their local DSN rather than looking on the remote DSNs onthe SQL
Server which uses the linked server)

HTH, Jens Suessmeyer.

ODBC Connection Problem

Hello,
I have a user who is attempting to connect to SQL Server Enterprise 2000 SP3a running on Windows 2000 Server. The client has WIndows NT 4.0 with MDAC 2.8. The problem is that when I attempt to create the ODBC link , I receive the following error:
"connection failed
sqlstate '01000'
sql server error 770
Microsoft odbc sqlserver driver tcp/ip socket connection write
secencrypt data
Connection failed
sql state '08S01'
Sql server error 18 security error
SSL/Encryption is not forced on the Server and I have many other clients who have no issues in connecting.
If anyone has any suggestions, I would appreciate it.
Thanks
Brent
I am having the exact same problem. If you ever solve it please let me know.

ODBC Connection Problem

Hello,
I have a user who is attempting to connect to SQL Server Enterprise 2000 SP3a running on Windows 2000 Server. The client has WIndows NT 4.0 with MDAC 2.8. The problem is that when I attempt to create the ODBC link , I receive the following error:
"connection failed
sqlstate '01000'
sql server error 770
Microsoft odbc sqlserver driver tcp/ip socket connection write
secencrypt data
Connection failed
sql state '08S01'
Sql server error 18 security error
SSL/Encryption is not forced on the Server and I have many other clients who have no issues in connecting.
If anyone has any suggestions, I would appreciate it.
Thanks
Brent
Run cliconfg.exe. Is "force protocol encryption" checked?
Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.
|||Nope, not ticked.
-- Cindy Gross (MSFT) wrote: --
Run cliconfg.exe. Is "force protocol encryption" checked?
Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.
|||What's the EXACT error message you get and what are you doing when you get
it (secencrypt and 770 are not SQL messages)?
Are there messages in the SQL errorlog or any of the three Windows event
logs on the client or server?
Try each of the following to see if any succeed (if it's a default
instance, ignore the \InstanceName):
np:ServerName\InstanceName
tcp:ServerName\InstanceName
tcp:ServerName\InstanceName, port
Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.

ODBC Connection Problem

Hello,
I have a user who is attempting to connect to SQL Server Enterprise 2000 SP3
a running on Windows 2000 Server. The client has WIndows NT 4.0 with MDAC 2
.8. The problem is that when I attempt to create the ODBC link , I receive
the following error:
"connection failed
sqlstate '01000'
sql server error 770
Microsoft odbc sqlserver driver tcp/ip socket connection write
secencrypt data
Connection failed
sql state '08S01'
Sql server error 18 security error
SSL/Encryption is not forced on the Server and I have many other clients who
have no issues in connecting.
If anyone has any suggestions, I would appreciate it.
Thanks
BrentI am having the exact same problem. If you ever solve it please let me
know.
grummo
---
Posted via http://www.mcse.ms
---
View this thread: http://www.mcse.ms/message527750.html

ODBC and Enterprise Manager (still) don't show databases with users other than sa

I have several Win2000 servers running SQL Server 2000, SP2 (8.00.665)
and only one of them developed this problem. When trying to set up a
new ODBC setting using any other login than sa, it doesn't show any
databases besides the system db's. When logging in with Enterprise
manager (all other logins except sa), the Databases list shows 'No
items'. All logins work fine with Query Analyzer. I already recreated
missing guest accounts in some of the databases, but that didn't help.
I've also installed the latest MDAC (2.7 SP1) and after that didn't
correct the problem, I installed SP3a. It's still not working.
I'm thinking about reinstalling SQL Server, but my client doesn't like
the idea. So if anyone has any idea what might help, I'd be greatful.
Thank you!
br,
AnnaAnna
Firstly you need to have SQL SP3 if you have not applied the patch to stop
the SQL Slammer on the server.
Are you using ODBC/ Query Analyzer from the server or the client?
I am getting a few problems as well after install MDAC 2.71 which has
somehow deleted my ODBC drivers from the Drivers tab window.
Regards
Z
Is the SQL a named instance?
"Anna N." <amnikol@.hotmail.com> wrote in message
news:6e225598.0307160146.5fadd9f2@.posting.google.com...
> I have several Win2000 servers running SQL Server 2000, SP2 (8.00.665)
> and only one of them developed this problem. When trying to set up a
> new ODBC setting using any other login than sa, it doesn't show any
> databases besides the system db's. When logging in with Enterprise
> manager (all other logins except sa), the Databases list shows 'No
> items'. All logins work fine with Query Analyzer. I already recreated
> missing guest accounts in some of the databases, but that didn't help.
> I've also installed the latest MDAC (2.7 SP1) and after that didn't
> correct the problem, I installed SP3a. It's still not working.
> I'm thinking about reinstalling SQL Server, but my client doesn't like
> the idea. So if anyone has any idea what might help, I'd be greatful.
> Thank you!
>
> br,
> Anna|||FYI:
First, I would try determine if it is an Server or Client Problem. ( The
Server has both Client and Server DLLs on it.)
To see if it is an client problem try to make the ODBC from a machine
without the problem to the Server with the problem.
If the problem is NOT there then it is an client problem.
If the problem is there confirm it by making an ODBC connect to one of the
Good Servers from the same test client.
If it is an server problem, I have nothing to suggest.
( Note my company spent over 40 man hours on an "Server Problem" that
turned out to be an client DLL issuse in SQL SP3)
If an client problem.
First check the version of SQLSRV32.dll ; is the correct one.
Link to version of SQLSRV32.dll
http://support.microsoft.com/default.aspx?scid=http%3a%2f%2fsupport.microsoft.com%2fservicedesks%2ffileversion%2fdllinfo.asp&fp=1
Then, I would try running the component checker ( on the MDAC ).
Link to info on component checker
http://support.microsoft.com/default.aspx?scid=kb;EN-US;307255
Link to download componet checker
http://www.microsoft.com/downloads/details.aspx?FamilyId=8F0A8DF6-4A21-4B43-BF53-14332EF092C9&displaylang=en
Tim S
"Zenduce" <james@.zenduce.net> wrote in message
news:%238XHwp4SDHA.1664@.TK2MSFTNGP11.phx.gbl...
> Anna
> Firstly you need to have SQL SP3 if you have not applied the patch to
stop
> the SQL Slammer on the server.
> Are you using ODBC/ Query Analyzer from the server or the client?
> I am getting a few problems as well after install MDAC 2.71 which has
> somehow deleted my ODBC drivers from the Drivers tab window.
> Regards
> Z
>
> Is the SQL a named instance?
> "Anna N." <amnikol@.hotmail.com> wrote in message
> news:6e225598.0307160146.5fadd9f2@.posting.google.com...
> > I have several Win2000 servers running SQL Server 2000, SP2 (8.00.665)
> > and only one of them developed this problem. When trying to set up a
> > new ODBC setting using any other login than sa, it doesn't show any
> > databases besides the system db's. When logging in with Enterprise
> > manager (all other logins except sa), the Databases list shows 'No
> > items'. All logins work fine with Query Analyzer. I already recreated
> > missing guest accounts in some of the databases, but that didn't help.
> > I've also installed the latest MDAC (2.7 SP1) and after that didn't
> > correct the problem, I installed SP3a. It's still not working.
> >
> > I'm thinking about reinstalling SQL Server, but my client doesn't like
> > the idea. So if anyone has any idea what might help, I'd be greatful.
> > Thank you!
> >
> >
> > br,
> > Anna
>|||"Zenduce" <james@.zenduce.net> wrote in message news:<#8XHwp4SDHA.1664@.TK2MSFTNGP11.phx.gbl>...
> Firstly you need to have SQL SP3 if you have not applied the patch to stop
> the SQL Slammer on the server.
I already have SP3a installed, as you can see from my original post.
> Are you using ODBC/ Query Analyzer from the server or the client?
Several clients.
> I am getting a few problems as well after install MDAC 2.71 which has
> somehow deleted my ODBC drivers from the Drivers tab window.
This problem emerged BEFORE installing MDAC 2.71, as you can see from
my original post.
> Is the SQL a named instance?
No.
- Anna|||"Tim S" <stahta01@.juno.com> wrote in message news:<XamRa.4637$C71.307@.fe01.atl2.webusenet.com>...
> First, I would try determine if it is an Server or Client Problem. ( The
> Server has both Client and Server DLLs on it.)
It is most definitely a server problem. I wouldn't have posted a
question without making sure where the problem is exactly.
- Anna

Obtaining Scripts

I need to script a couple of things that I do through enterprise manager...is there a way to do a process (such as clear connections/detach database) through enterprise manager and then copy the script that sql ran in the back ground?
Best way is to run profiler and capture the commands while performing your tasks on Ent. Manager.
"Jamie Elliott" wrote:

> I need to script a couple of things that I do through enterprise manager...is there a way to do a process (such as clear connections/detach database) through enterprise manager and then copy the script that sql ran in the back ground?
|||Standart Trace template will be fine ..
"Jamie Elliott" wrote:
[vbcol=seagreen]
> when setting up profiler...is there any certain setting I should give it?
> "Umut Nazlica" wrote:

Obtaining Scripts

I need to script a couple of things that I do through enterprise manager...i
s there a way to do a process (such as clear connections/detach database) th
rough enterprise manager and then copy the script that sql ran in the back g
round?Best way is to run profiler and capture the commands while performing your t
asks on Ent. Manager.
"Jamie Elliott" wrote:

> I need to script a couple of things that I do through enterprise manager...is ther
e a way to do a process (such as clear connections/detach database) through enterpri
se manager and then copy the script that sql ran in the back ground?|||Standart Trace template will be fine ..
"Jamie Elliott" wrote:
[vbcol=seagreen]
> when setting up profiler...is there any certain setting I should give it?
> "Umut Nazlica" wrote:
>