[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name on Linked Server

Hi Folks,
I'm having a strange situation here between 2 Linked MS SQL 2K servers.
One of the servers died recently and I rebuilt it.
All seems to be working fine, except that when I create views that access tables on the other (linked) server, I can not modify any data, because I get the [Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name server.database.dbo.TableName error.
The View does work fine otherwise, ie displays the data in it, I just can't modify.
The Linked Servers are done with the sa user between these 2 servers.

Any ideas what could be causing this error?
Thanks!-- bump --
no one ideas on this?|||I'm also having problems with this - mine is in relation to a labeler printer, it is present in my ODBC and the test is successful. However, when I go to print I get the following error: [microsoft][ODBC SQL Server Driver][SQL SERVER] Invalid object name 'table name' ODBC -- call failed

I can't seem to see what the problem is as my project server works from this client.

[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name

hi
i m connect to the sQL SERVER using system DSN in JREPORT
but it is not working
get the following error
[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name

Quote:

Originally Posted by daxter

hi
i m connect to the sQL SERVER using system DSN in JREPORT
but it is not working
get the following error
[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name

Try using

\Control Panel\Administrative Tools\Data Sources (ODBC)

And System DNS tab up the top of that window

[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name

From Enterpise Manager I create a user, giving all available rights. I have created a DB and set this user to be everything for it (except deny). I create tables as this user on the above DB. When I try to access these tables with an app using ODBC, the specific error appears.
Please assist fellas - situation critical.
Thanx.Refer to this KBA (http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/Q218/9/95.asp&NoWebContent=1) to resolve the issue.|||Thanx for the info but it didn't work.|||If you created the objects as the user, then they are owned by the user, and will be named [ownername].[objectname].

If your sql code does not specify a ownername sqlserver assumes dbo ownership, and your objects don't exists as dbo.[objectname].

Either specify the owner name when you reference the objects,
or instead of granting all individual rights to the user just grant it dbo access to the database. Then any objects it creates will be dbo owned and will not need to be fully referenced.

blindman

[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name

I have a ms sqlserver 2000 database installed on my Windows NT4 PC.

I want to access this database from a java program using JDBC - ODBC

Here are the relavent lines of code from my java source code file.

Note : I am attempting to access the sample database "Northwind Traders" that came with the installation.

Class.forName("sun.jdbc.odbc.JdbcOdbcDriver").newInstance();
datasource = "NORTHDS";
url = "jdbc:odbc:" + datasource;
con = DriverManager.getConnection(url,username,password) ;
query = "SELECT * from " + datasource + "." + username + "." + tablename;
ResultSet rs = stmt.executeQuery(query);

The connection succeeds but the query fails with :
java.sql.SQLException: [Microsoft][ODBC SQL Server Driver][SQL
Server]Invalid object name 'NORTHDS.username.Customers'.

Using the program "Microsoft Access" I was able to verify that the "Customers" table is intact.

Any ideas ?Take a look at the following:

In your select statement there are a couple of potential problems that you need to verify.

select * from datasource.username.table ... which is returning 'NORTHDS.username.Customers'

should be

select * from Northwind.dbo.Customers ... (unless you renamed the database ...)

In other words, check to make sure your are referencing the correct database/owner/table in your select statement. It appears that the variables you are using are incorrect. tablename appears to be ok, but the username variable is returning username. Also, the datasource variable may not be your database name.

[Microsoft][ODBC SQL Server Driver][SQL Server]I/O error (bad page ID)

Hi!

Im having this error when doing a query to a SQL Server 2000 Database:

Microsoft OLE DB Provider for ODBC Drivers error
'80004005'

[Microsoft][ODBC SQL Server Driver][SQL Server]I/O error
(bad page ID) detected during read at offset
0x000000003ac000 in file 'E:\Program FIles\Microsoft SQL
Server\MSSQL\Data\sitioIAC_Data.MDF'.

It doesnt happend in some queryes trough a ASP file.

What could it be??

Thank You
JuanRun DBCC CHECKDB against that table(s) with REPAIR_ALLOW_DATA_LOSS option. Refer to BOL for more information on DBCC CHECKDB & CHECKTABLE topics.

[Microsoft][ODBC SQL Server Driver][SQL Server]Could not find stored procedure

I am new to SQL Server and stored procedures and here is my problem.

I am stepping into a stored procedure ‘storedProced1’ using T-SQL debugger. ‘storedProced1’ is calling ‘storedProced2’. When I step into the following line where storedProced2’ is being executed,

exec storedProced2 @.Parameter1, @. Parameter2, @. Parameter3

I got the following message in the immediate window.

[Microsoft][ODBC SQL Server Driver][SQL Server]Could not find stored procedure 'storedProced2’.

@.RETURN_VALUE = N/A

But “storedProced2” does exists. What am I doing wrong?

Make sure that the procedure exists within the actual database and make sure that you are using the right owner declaration for this, this calling the procedure with the Routine_Schema and Routine_Name from the following query.

SELECT Routine_schema, ROutine_name
From INFORMATION_SCHEMA.Routines
WHere Routine_Name = 'storedProced2'

--> Calling EXEC <SchemaName>.<Objectname>

HTH, jens K. Suessmeyer.

http://www.sqlserver2005.de

[Microsoft][ODBC SQL Server Driver][Named Pipes] ConnectionWrite (WrapperWrite())

Hi,

I got the error message "[Microsoft][ODBC SQL Server Driver][Named Pipes] ConnectionWrite (WrapperWrite())" from my VB6 application that connects to SQL Server 2000.

How to fix this?

Can you post the full error. The posted message is too generic.
http://groups.google.com/groups/search?q=ConnectionWrite+%28WrapperWrite%28%29&qt_s=Search

[Microsoft][ODBC SQL Server Driver][DBNETLIB]General network error

We have built an application (VB 6 with a SQL 2000 backend database)
in-house and from time to time, we get the dbnetlib error message. This erro
r
message seems to happen when the machine is just idle and is driving me nuts
.
The error message doesnt seem to have the issue while the user is actively
using the application. Could this problem have something to do with
connection pooling? If anyone has any ideas, it would be much appreciated.
Thanks in advance!
Mike HartmanWe have seen this from time-to-time. It seems that the connection "ages out"
after a long period of dormancy. The solution I use is to occasionally poll
the server to make sure it knows that the application is still alive. I
don't think it's a connection pooling issue. It looks like the transport
layer is being closed at the server end (in my case).
USE <initial catalog>
is enough to do the job.
hth
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
----
---
"Mike" <Mike@.discussions.microsoft.com> wrote in message
news:772A11BE-EF7D-4088-8654-9C29D15F1FCC@.microsoft.com...
> We have built an application (VB 6 with a SQL 2000 backend database)
> in-house and from time to time, we get the dbnetlib error message. This
> error
> message seems to happen when the machine is just idle and is driving me
> nuts.
> The error message doesnt seem to have the issue while the user is actively
> using the application. Could this problem have something to do with
> connection pooling? If anyone has any ideas, it would be much appreciated.
> Thanks in advance!
> Mike Hartman

[Microsoft][ODBC SQL Server Driver][DBNETLIB]General network error

We have built an application (VB 6 with a SQL 2000 backend database)
in-house and from time to time, we get the dbnetlib error message. This error
message seems to happen when the machine is just idle and is driving me nuts.
The error message doesnt seem to have the issue while the user is actively
using the application. Could this problem have something to do with
connection pooling? If anyone has any ideas, it would be much appreciated.
Thanks in advance!
Mike Hartman
We have seen this from time-to-time. It seems that the connection "ages out"
after a long period of dormancy. The solution I use is to occasionally poll
the server to make sure it knows that the application is still alive. I
don't think it's a connection pooling issue. It looks like the transport
layer is being closed at the server end (in my case).
USE <initial catalog>
is enough to do the job.
hth
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
------
"Mike" <Mike@.discussions.microsoft.com> wrote in message
news:772A11BE-EF7D-4088-8654-9C29D15F1FCC@.microsoft.com...
> We have built an application (VB 6 with a SQL 2000 backend database)
> in-house and from time to time, we get the dbnetlib error message. This
> error
> message seems to happen when the machine is just idle and is driving me
> nuts.
> The error message doesnt seem to have the issue while the user is actively
> using the application. Could this problem have something to do with
> connection pooling? If anyone has any ideas, it would be much appreciated.
> Thanks in advance!
> Mike Hartman

[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionWrite (send()).

We are randomly experiencing this error when connecting to SQL W2K from web
servers using ODBC. I see numerous links on the web but real answers.
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionWrite (send()).
Hi Brent,
I would make a network trace on the client and the server. I'll bet you
can't reproduce this if the client and server are on the same machine.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionWrite (send()).

We are randomly experiencing this error when connecting to SQL W2K from web
servers using ODBC. I see numerous links on the web but real answers.
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionWrite (se
nd()).Hi Brent,
I would make a network trace on the client and the server. I'll bet you
can't reproduce this if the client and server are on the same machine.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead(recv())DId you enable remote con

Dear All

I am using sql server 2000 SP4. Os is win2003 server. I was able to register sql server from my server using Enterprise manager. but i am not able to register the same from any client machine. pls help me

raffi

Hi,

DId you enable remote connections yet ? Have a look at my screencast on my site. You will find a tutorial to enable remote connections for your SQL Server 2005. By default this is turned off.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de

[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead(recv())

Dear All

I am using sql server 2000 SP4. Os is win2003 server. I was able to register sql server from my server using Enterprise manager. but i am not able to register the same from any client machine. pls help me

raffi

Hi,

DId you enable remote connections yet ? Have a look at my screencast on my site. You will find a tutorial to enable remote connections for your SQL Server 2005. By default this is turned off.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de

[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckForDat

Could you please explain this error, and a work around?
Thank you.
Mike
Hi
Maybe http://support.microsoft.com/default...b;en-us;246598 will
solve this. What/where is this happening? If you have a specific query that
fails you may want to post it along with DDL and example data.
Other things to try:
Check the SQL Server log and Windows Event log to see if other message
appear when you get this error.
Check you have a recent and complete version of MDAC.
John
"Mike" <Mike@.discussions.microsoft.com> wrote in message
news:953DFD7E-06DE-4187-B0EE-0160697BB8E3@.microsoft.com...
> Could you please explain this error, and a work around?
> Thank you.
> --
> Mike

[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckForDat

Could you please explain this error, and a work around?
Thank you.
--
MikeHi
Maybe http://support.microsoft.com/default.aspx?scid=kb;en-us;246598 will
solve this. What/where is this happening? If you have a specific query that
fails you may want to post it along with DDL and example data.
Other things to try:
Check the SQL Server log and Windows Event log to see if other message
appear when you get this error.
Check you have a recent and complete version of MDAC.
John
"Mike" <Mike@.discussions.microsoft.com> wrote in message
news:953DFD7E-06DE-4187-B0EE-0160697BB8E3@.microsoft.com...
> Could you please explain this error, and a work around?
> Thank you.
> --
> Mike

[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckForDat

Could you please explain this error, and a work around?
Thank you.
--
MikeHi
Maybe http://support.microsoft.com/defaul...kb;en-us;246598 will
solve this. What/where is this happening? If you have a specific query that
fails you may want to post it along with DDL and example data.
Other things to try:
Check the SQL Server log and Windows Event log to see if other message
appear when you get this error.
Check you have a recent and complete version of MDAC.
John
"Mike" <Mike@.discussions.microsoft.com> wrote in message
news:953DFD7E-06DE-4187-B0EE-0160697BB8E3@.microsoft.com...
> Could you please explain this error, and a work around?
> Thank you.
> --
> Mike

[Microsoft][ODBC SQL Server Driver] Timeout Expired

Hello,
I installed MS SQL Server 2000 Evaluation Edition on
Windows XP Pro PC. I have database on the same PC. When I
am running a query(view) from Query Analyser I
get "[Microsoft][ODBC SQL Server Driver] Timeout Expired"
error message . When I am running the same view on
smaller amount of data it works.
Could you please help me with that?
Thanks
DJ
hi
goto the server properties.then there is a property called connection time.
check it and give the appropiate time on this

[Microsoft][ODBC SQL Server Driver] Timeout expired

I am getting this error when I try and look at the Top 1000 records of a view
that I have created, in Enterprise Manager. If I copy the SQL for the View
into Query Analyzer, it returns results fine (in approx. 2 minutes). In the
Enterprise Manager Properties Advanced window, I have set Query timeout to
both 0 (never times out?) and 60000 (100 minutes?) to no avail. Any
suggestions would be greatly appreciated.
What is the exact error number and message? There are several types of
timeouts. If you are not specifying the correct parameter, it will continue
to timeout on that type.
Sincerely,
Anthony Thomas

"Gary W. Hinkel" <GaryWHinkel@.discussions.microsoft.com> wrote in message
news:E43E35ED-809B-4DF4-8869-0EE3A49F9EEF@.microsoft.com...
I am getting this error when I try and look at the Top 1000 records of a
view
that I have created, in Enterprise Manager. If I copy the SQL for the View
into Query Analyzer, it returns results fine (in approx. 2 minutes). In the
Enterprise Manager Properties Advanced window, I have set Query timeout to
both 0 (never times out?) and 60000 (100 minutes?) to no avail. Any
suggestions would be greatly appreciated.
|||Unfortunately, there is no error number, and the error message is the subject
line of this post. Also, I am not specifying any parameters at all, as this
is happening in Enterrpise Manager, Views, right-click on view, Open View,
Return Top.
"AnthonyThomas" wrote:

> What is the exact error number and message? There are several types of
> timeouts. If you are not specifying the correct parameter, it will continue
> to timeout on that type.
> Sincerely,
>
> Anthony Thomas
>
> --
> "Gary W. Hinkel" <GaryWHinkel@.discussions.microsoft.com> wrote in message
> news:E43E35ED-809B-4DF4-8869-0EE3A49F9EEF@.microsoft.com...
> I am getting this error when I try and look at the Top 1000 records of a
> view
> that I have created, in Enterprise Manager. If I copy the SQL for the View
> into Query Analyzer, it returns results fine (in approx. 2 minutes). In the
> Enterprise Manager Properties Advanced window, I have set Query timeout to
> both 0 (never times out?) and 60000 (100 minutes?) to no avail. Any
> suggestions would be greatly appreciated.
>
>
|||If you've changed the SQLEM, Tools, Options, Advanced Tab, Query Timeout
value to 0 and you are still getting the message, then you are probably being
blocked by current processes and are getting a LOCK TIMEOUT (which is really
a Lock Wait timeout). You do not have the ability to modify the Lock Timout
setting through EM; however, you can through Query Analyzer.
The Properties, Advanced Window does not exist for SQLEM. There is a
Properties, Connections, Remote Connections area for the currently selected
database, but that property is a timeout setting for RPC queries, not SQLEM
DMO.
Sincerely,
Anthony Thomas
"Gary W. Hinkel" wrote:
[vbcol=seagreen]
> Unfortunately, there is no error number, and the error message is the subject
> line of this post. Also, I am not specifying any parameters at all, as this
> is happening in Enterrpise Manager, Views, right-click on view, Open View,
> Return Top.
> "AnthonyThomas" wrote:
|||Thanks for all your assisstance Anthony. This has cleared things up for me
as far as SQLEM is concerned (ie: I won't use it to display views, I'll use
QA instead).
I had initially thought that if I could resolve the timeout issue in SQLEM,
then the same issues in getting data into MapPoint, Excel, etc. through an
ODBC connection could be resolved as well.
Now at least, I can focus my efforts on getting the View data into
MapPoint/Excel etc.
Thanks again Anthony.
Sincerely,
Gary W. Hinkel
"AnthonyThomas" wrote:
[vbcol=seagreen]
> If you've changed the SQLEM, Tools, Options, Advanced Tab, Query Timeout
> value to 0 and you are still getting the message, then you are probably being
> blocked by current processes and are getting a LOCK TIMEOUT (which is really
> a Lock Wait timeout). You do not have the ability to modify the Lock Timout
> setting through EM; however, you can through Query Analyzer.
> The Properties, Advanced Window does not exist for SQLEM. There is a
> Properties, Connections, Remote Connections area for the currently selected
> database, but that property is a timeout setting for RPC queries, not SQLEM
> DMO.
> Sincerely,
>
> Anthony Thomas
>
> "Gary W. Hinkel" wrote:

[Microsoft][ODBC SQL Server Driver] Timeout Expired

Hello,
I installed MS SQL Server 2000 Evaluation Edition on
Windows XP Pro. I have database on the same PC. When I
am running a query(view) from Query Analyser I
get "[Microsoft][ODBC SQL Server Driver] Timeout Expired"
error message . When I am running the same view on
smaller amount of data it works.

:confused:

Could you please help me with that?
Thanks
DJCheck out this page.

http://support.microsoft.com/default.aspx?scid=kb;EN-US;313661|||The link in the previous post is for a connection timeout using SQL Server 7. It does not apply to running a query on SQL Server 2000.|||SQL Server 2000's default timeout period it 600 seconds (10 minutes). If you change it to zero (0), that's infinite. How long is it taking to timeout?

If you run a long query through the Enterprise Manager, it will timeout after 30 seconds. MS's answer to this is to use the Query Analyzer (which should not timeout). I've run a 14-hour query through SQL Query Analyzer before.

[Microsoft][ODBC SQL Server Driver] Timeout expired

I am getting this error when I try and look at the Top 1000 records of a vie
w
that I have created, in Enterprise Manager. If I copy the SQL for the View
into Query Analyzer, it returns results fine (in approx. 2 minutes). In the
Enterprise Manager Properties Advanced window, I have set Query timeout to
both 0 (never times out?) and 60000 (100 minutes?) to no avail. Any
suggestions would be greatly appreciated.What is the exact error number and message? There are several types of
timeouts. If you are not specifying the correct parameter, it will continue
to timeout on that type.
Sincerely,
Anthony Thomas
"Gary W. Hinkel" <GaryWHinkel@.discussions.microsoft.com> wrote in message
news:E43E35ED-809B-4DF4-8869-0EE3A49F9EEF@.microsoft.com...
I am getting this error when I try and look at the Top 1000 records of a
view
that I have created, in Enterprise Manager. If I copy the SQL for the View
into Query Analyzer, it returns results fine (in approx. 2 minutes). In the
Enterprise Manager Properties Advanced window, I have set Query timeout to
both 0 (never times out?) and 60000 (100 minutes?) to no avail. Any
suggestions would be greatly appreciated.|||Unfortunately, there is no error number, and the error message is the subjec
t
line of this post. Also, I am not specifying any parameters at all, as this
is happening in Enterrpise Manager, Views, right-click on view, Open View,
Return Top.
"AnthonyThomas" wrote:

> What is the exact error number and message? There are several types of
> timeouts. If you are not specifying the correct parameter, it will contin
ue
> to timeout on that type.
> Sincerely,
>
> Anthony Thomas
>
> --
> "Gary W. Hinkel" <GaryWHinkel@.discussions.microsoft.com> wrote in message
> news:E43E35ED-809B-4DF4-8869-0EE3A49F9EEF@.microsoft.com...
> I am getting this error when I try and look at the Top 1000 records of a
> view
> that I have created, in Enterprise Manager. If I copy the SQL for the Vie
w
> into Query Analyzer, it returns results fine (in approx. 2 minutes). In t
he
> Enterprise Manager Properties Advanced window, I have set Query timeout to
> both 0 (never times out?) and 60000 (100 minutes?) to no avail. Any
> suggestions would be greatly appreciated.
>
>|||If you've changed the SQLEM, Tools, Options, Advanced Tab, Query Timeout
value to 0 and you are still getting the message, then you are probably bein
g
blocked by current processes and are getting a LOCK TIMEOUT (which is really
a Lock Wait timeout). You do not have the ability to modify the Lock Timout
setting through EM; however, you can through Query Analyzer.
The Properties, Advanced Window does not exist for SQLEM. There is a
Properties, Connections, Remote Connections area for the currently selected
database, but that property is a timeout setting for RPC queries, not SQLEM
DMO.
Sincerely,
Anthony Thomas
"Gary W. Hinkel" wrote:
[vbcol=seagreen]
> Unfortunately, there is no error number, and the error message is the subj
ect
> line of this post. Also, I am not specifying any parameters at all, as th
is
> is happening in Enterrpise Manager, Views, right-click on view, Open View,
> Return Top.
> "AnthonyThomas" wrote:
>|||Thanks for all your assisstance Anthony. This has cleared things up for me
as far as SQLEM is concerned (ie: I won't use it to display views, I'll use
QA instead).
I had initially thought that if I could resolve the timeout issue in SQLEM,
then the same issues in getting data into MapPoint, Excel, etc. through an
ODBC connection could be resolved as well.
Now at least, I can focus my efforts on getting the View data into
MapPoint/Excel etc.
Thanks again Anthony.
Sincerely,
Gary W. Hinkel
"AnthonyThomas" wrote:
[vbcol=seagreen]
> If you've changed the SQLEM, Tools, Options, Advanced Tab, Query Timeout
> value to 0 and you are still getting the message, then you are probably be
ing
> blocked by current processes and are getting a LOCK TIMEOUT (which is real
ly
> a Lock Wait timeout). You do not have the ability to modify the Lock Timo
ut
> setting through EM; however, you can through Query Analyzer.
> The Properties, Advanced Window does not exist for SQLEM. There is a
> Properties, Connections, Remote Connections area for the currently selecte
d
> database, but that property is a timeout setting for RPC queries, not SQLE
M
> DMO.
> Sincerely,
>
> Anthony Thomas
>
> "Gary W. Hinkel" wrote:
>

[Microsoft][ODBC SQL Server Driver] Timeout expired

I am getting this error when I try and look at the Top 1000 records of a view
that I have created, in Enterprise Manager. If I copy the SQL for the View
into Query Analyzer, it returns results fine (in approx. 2 minutes). In the
Enterprise Manager Properties Advanced window, I have set Query timeout to
both 0 (never times out?) and 60000 (100 minutes?) to no avail. Any
suggestions would be greatly appreciated.What is the exact error number and message? There are several types of
timeouts. If you are not specifying the correct parameter, it will continue
to timeout on that type.
Sincerely,
Anthony Thomas
"Gary W. Hinkel" <GaryWHinkel@.discussions.microsoft.com> wrote in message
news:E43E35ED-809B-4DF4-8869-0EE3A49F9EEF@.microsoft.com...
I am getting this error when I try and look at the Top 1000 records of a
view
that I have created, in Enterprise Manager. If I copy the SQL for the View
into Query Analyzer, it returns results fine (in approx. 2 minutes). In the
Enterprise Manager Properties Advanced window, I have set Query timeout to
both 0 (never times out?) and 60000 (100 minutes?) to no avail. Any
suggestions would be greatly appreciated.|||Unfortunately, there is no error number, and the error message is the subject
line of this post. Also, I am not specifying any parameters at all, as this
is happening in Enterrpise Manager, Views, right-click on view, Open View,
Return Top.
"AnthonyThomas" wrote:
> What is the exact error number and message? There are several types of
> timeouts. If you are not specifying the correct parameter, it will continue
> to timeout on that type.
> Sincerely,
>
> Anthony Thomas
>
> --
> "Gary W. Hinkel" <GaryWHinkel@.discussions.microsoft.com> wrote in message
> news:E43E35ED-809B-4DF4-8869-0EE3A49F9EEF@.microsoft.com...
> I am getting this error when I try and look at the Top 1000 records of a
> view
> that I have created, in Enterprise Manager. If I copy the SQL for the View
> into Query Analyzer, it returns results fine (in approx. 2 minutes). In the
> Enterprise Manager Properties Advanced window, I have set Query timeout to
> both 0 (never times out?) and 60000 (100 minutes?) to no avail. Any
> suggestions would be greatly appreciated.
>
>|||If you've changed the SQLEM, Tools, Options, Advanced Tab, Query Timeout
value to 0 and you are still getting the message, then you are probably being
blocked by current processes and are getting a LOCK TIMEOUT (which is really
a Lock Wait timeout). You do not have the ability to modify the Lock Timout
setting through EM; however, you can through Query Analyzer.
The Properties, Advanced Window does not exist for SQLEM. There is a
Properties, Connections, Remote Connections area for the currently selected
database, but that property is a timeout setting for RPC queries, not SQLEM
DMO.
Sincerely,
Anthony Thomas
"Gary W. Hinkel" wrote:
> Unfortunately, there is no error number, and the error message is the subject
> line of this post. Also, I am not specifying any parameters at all, as this
> is happening in Enterrpise Manager, Views, right-click on view, Open View,
> Return Top.
> "AnthonyThomas" wrote:
> > What is the exact error number and message? There are several types of
> > timeouts. If you are not specifying the correct parameter, it will continue
> > to timeout on that type.
> >
> > Sincerely,
> >
> >
> > Anthony Thomas
> >
> >
> > --
> >
> > "Gary W. Hinkel" <GaryWHinkel@.discussions.microsoft.com> wrote in message
> > news:E43E35ED-809B-4DF4-8869-0EE3A49F9EEF@.microsoft.com...
> > I am getting this error when I try and look at the Top 1000 records of a
> > view
> > that I have created, in Enterprise Manager. If I copy the SQL for the View
> > into Query Analyzer, it returns results fine (in approx. 2 minutes). In the
> > Enterprise Manager Properties Advanced window, I have set Query timeout to
> > both 0 (never times out?) and 60000 (100 minutes?) to no avail. Any
> > suggestions would be greatly appreciated.
> >
> >
> >|||Thanks for all your assisstance Anthony. This has cleared things up for me
as far as SQLEM is concerned (ie: I won't use it to display views, I'll use
QA instead).
I had initially thought that if I could resolve the timeout issue in SQLEM,
then the same issues in getting data into MapPoint, Excel, etc. through an
ODBC connection could be resolved as well.
Now at least, I can focus my efforts on getting the View data into
MapPoint/Excel etc.
Thanks again Anthony.
Sincerely,
Gary W. Hinkel
"AnthonyThomas" wrote:
> If you've changed the SQLEM, Tools, Options, Advanced Tab, Query Timeout
> value to 0 and you are still getting the message, then you are probably being
> blocked by current processes and are getting a LOCK TIMEOUT (which is really
> a Lock Wait timeout). You do not have the ability to modify the Lock Timout
> setting through EM; however, you can through Query Analyzer.
> The Properties, Advanced Window does not exist for SQLEM. There is a
> Properties, Connections, Remote Connections area for the currently selected
> database, but that property is a timeout setting for RPC queries, not SQLEM
> DMO.
> Sincerely,
>
> Anthony Thomas
>
> "Gary W. Hinkel" wrote:
> > Unfortunately, there is no error number, and the error message is the subject
> > line of this post. Also, I am not specifying any parameters at all, as this
> > is happening in Enterrpise Manager, Views, right-click on view, Open View,
> > Return Top.
> >
> > "AnthonyThomas" wrote:
> >
> > > What is the exact error number and message? There are several types of
> > > timeouts. If you are not specifying the correct parameter, it will continue
> > > to timeout on that type.
> > >
> > > Sincerely,
> > >
> > >
> > > Anthony Thomas
> > >
> > >
> > > --
> > >
> > > "Gary W. Hinkel" <GaryWHinkel@.discussions.microsoft.com> wrote in message
> > > news:E43E35ED-809B-4DF4-8869-0EE3A49F9EEF@.microsoft.com...
> > > I am getting this error when I try and look at the Top 1000 records of a
> > > view
> > > that I have created, in Enterprise Manager. If I copy the SQL for the View
> > > into Query Analyzer, it returns results fine (in approx. 2 minutes). In the
> > > Enterprise Manager Properties Advanced window, I have set Query timeout to
> > > both 0 (never times out?) and 60000 (100 minutes?) to no avail. Any
> > > suggestions would be greatly appreciated.
> > >
> > >
> > >

[Microsoft][ODBC SQL Server Driver] Timeout Expired

Hello,
I installed MS SQL Server 2000 Evaluation Edition on
Windows XP Pro PC. I have database on the same PC. When I
am running a query(view) from Query Analyser I
get "[Microsoft][ODBC SQL Server Driver] Timeout Expired"
error message . When I am running the same view on
smaller amount of data it works.
Could you please help me with that?
Thanks
DJhi
goto the server properties.then there is a property called connection time
.
check it and give the appropiate time on this

[Microsoft][ODBC SQL Server Driver] Invalid Descriptor Index

Hi,
I am using MFC ODBC classes in my VC++ application for database accesss (on
a SQL Server/Access Database).
Some times after opening a Recordset (containing bound columns generated
using the ClassWizard) I have to use the
CRecordset::GetFieldValue( LPCTSTR lpszName, CDBVariant& varValue, short
nFieldType = DEFAULT_FIELD_TYPE )
method of the CRecordset object to obtain field values. The above method
works fine with ODBC drivers for Jet but when I use ODBC for SQL Server it
throws the following exception
State:S1002,Native:0,Origin:[Microsoft][
ODBC SQL Server Driver] Invalid
Descriptor Index
I don't understand why the Microsoft SQL Server ODBC Driver is throwing this
exception.
Please help me!
SameerHi Sameer,
Thanks for posting in the community.
From your description, I understand that when you use the CRecordset::GetFie
ldValue
method t oobtain the field values after opening a binding columns recordset,
you will
receive the exception of Invalid Descriptor Index for ODBC SQL Server Driver
. However, the
problem doesn't occur with ODBC drivers for Jet.
Before we start, please notice that the issue is related to MFC programming
which is
gracefully handling in this queue. However, it's my pleasure to let me see i
f I can address
your problem and give some solutions. For quickly and efficiently solve your
problem, it's
better to post this issue in the corresponding queues such as ADO/VC/VC++ ne
wsgroup.
I'm not 100% sure why the exception was genereted when using ODBC SQL Server
Drivers.
Based on my research, per the ODBC docs SQLGetData throws that error if it's
called and
all the columns are already bound when it is generated using the ClassWizard
.
So the bottom line is that if you're using a CRecordset that was created wit
h
the AppWizard, don't use GetFieldValue. Instead, go to the record that you
want and then look at the data member of the recordset to get the field valu
e.
Please apply my suggestions above and let me know if this helps resolve your
problem. If
there is anything more I can do to assist you, please feel free to post it i
n the group.
If the problem still persists and you'd like to get the most qualified pool
of respondents,
please repost this issue to the corresponding queues I mentioned above. Addi
tionally,
other partners who read the newsgroups regularly can either share their know
ledge or learn
from your interaction with us. I hope the problem can be resolved quickly.
Best regards,
Billy Yao
Microsoft Online Support
----
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.

[Microsoft][ODBC SQL Server Driver] Invalid cursor stateevery time I save in enterprise ma

Hi,
every time I save after a change in any table through enterprise nmanager
I receive this error:
[Microsoft][ODBC SQL Server Driver] Invalid cursor state
If I generate a script instead-of saving directly
and if I execute this script through the query analyzer all works fine!
My windows 2003 is english
my SQL Server is french
my default language is french
I've found the same error on another server which is in the same config.
any idea?
thanks.
Jerome.
> every time I save after a change in any table through enterprise nmanager
> I receive this error:
> [Microsoft][ODBC SQL Server Driver] Invalid cursor state
So why not use scripts in Query Analyzer? IMHO, there are only a few cases
where Enterprise Manager should be used...
http://www.aspfaq.com/2515
http://www.aspfaq.com/2455
http://www.aspfaq.com/
(Reverse address to reply.)
|||enterprise manager is easy to use.
When I update or add a column, I can do this very quickly in enterprise
manager
using query analyzer is an overhead for me :-)
"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:%23hCrneyyEHA.2624@.TK2MSFTNGP11.phx.gbl...
> So why not use scripts in Query Analyzer? IMHO, there are only a few
> cases
> where Enterprise Manager should be used...
> http://www.aspfaq.com/2515
> http://www.aspfaq.com/2455
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>
|||This is over your head?
ALTER TABLE <tablename> ADD <columnname> <DATATYPE>
http://www.aspfaq.com/
(Reverse address to reply.)
"Jj" <willgart_A_@.hotmail_A_.com> wrote in message
news:eat5rhyyEHA.4028@.TK2MSFTNGP15.phx.gbl...[vbcol=seagreen]
> enterprise manager is easy to use.
> When I update or add a column, I can do this very quickly in enterprise
> manager
> using query analyzer is an overhead for me :-)
>
> "Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
> news:%23hCrneyyEHA.2624@.TK2MSFTNGP11.phx.gbl...
nmanager
>
|||yep
specially when you have a lot of columns to change/add/remove :-)
"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:ebp1VjyyEHA.2540@.TK2MSFTNGP09.phx.gbl...
> This is over your head?
> ALTER TABLE <tablename> ADD <columnname> <DATATYPE>
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>
>
> "Jj" <willgart_A_@.hotmail_A_.com> wrote in message
> news:eat5rhyyEHA.4028@.TK2MSFTNGP15.phx.gbl...
> nmanager
>
|||> yep
> specially when you have a lot of columns to change/add/remove :-)
Okay, so is there something especially painful about learning them? It
certainly can't HURT you to have this knowledge; surely someday you will
have to connect to SQL Server without using a GUI as a crutch...
|||There are different combinations of service packs that lend
themselves to having this error more often - e.g between
8.00.0859 and 8.00.0875 you can get the error more often,
version 8.00.0927 or no SP3 version 8.00.0194 you don't,
etc.
The bottom line is what Aaron keeps telling you - you should
be using Query Analyzer for this type of thing. It was
designed more for this type of activity.
-Sue
On Mon, 15 Nov 2004 11:17:34 -0500, "Jj"
<willgart_A_@.hotmail_A_.com> wrote:

>yep
>specially when you have a lot of columns to change/add/remove :-)
>"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
>news:ebp1VjyyEHA.2540@.TK2MSFTNGP09.phx.gbl...
>
|||I've the version 859
what is the 927 version? SP4? intermediate release?
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:isshp0916fff78e8q6i0rn7n1lh5a0meen@.4ax.com...
> There are different combinations of service packs that lend
> themselves to having this error more often - e.g between
> 8.00.0859 and 8.00.0875 you can get the error more often,
> version 8.00.0927 or no SP3 version 8.00.0194 you don't,
> etc.
> The bottom line is what Aaron keeps telling you - you should
> be using Query Analyzer for this type of thing. It was
> designed more for this type of activity.
> -Sue
> On Mon, 15 Nov 2004 11:17:34 -0500, "Jj"
> <willgart_A_@.hotmail_A_.com> wrote:
>
|||> what is the 927 version? SP4? intermediate release?
Hotfix. Only certain ones are available without contacting PSS directly.
http://www.aspfaq.com/2160
http://www.aspfaq.com/
(Reverse address to reply.)
|||Hot fix for the following:
http://support.microsoft.com/?kbid=839688
But then you will be managing hot fixes based upon not
wanting to use Query Analyzer for writing T-SQL to maintain
your databases. Doesn't seem like a good path to go down.
So if another slammer comes out, would your company want you
to patch it and use T-SQL for table changes or would they
want you to leave the box vulnerable so you could use
Enterprise Manager to make all your table changes?
-Sue
On Mon, 15 Nov 2004 13:40:43 -0500, "Jj"
<willgart_A_@.hotmail_A_.com> wrote:

>I've the version 859
>what is the 927 version? SP4? intermediate release?
>"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
>news:isshp0916fff78e8q6i0rn7n1lh5a0meen@.4ax.com.. .
>

[Microsoft][ODBC SQL Server Driver] Invalid cursor stateevery time I save in enterprise ma

Hi,
every time I save after a change in any table through enterprise nmanager
I receive this error:
[Microsoft][ODBC SQL Server Driver] Invalid cursor state
If I generate a script instead-of saving directly
and if I execute this script through the query analyzer all works fine!
My windows 2003 is english
my SQL Server is french
my default language is french
I've found the same error on another server which is in the same config.
any idea?
thanks.
Jerome.> every time I save after a change in any table through enterprise nmanager
> I receive this error:
> [Microsoft][ODBC SQL Server Driver] Invalid cursor state
So why not use scripts in Query Analyzer? IMHO, there are only a few cases
where Enterprise Manager should be used...
http://www.aspfaq.com/2515
http://www.aspfaq.com/2455
--
http://www.aspfaq.com/
(Reverse address to reply.)|||enterprise manager is easy to use.
When I update or add a column, I can do this very quickly in enterprise
manager
using query analyzer is an overhead for me :-)
"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:%23hCrneyyEHA.2624@.TK2MSFTNGP11.phx.gbl...
>> every time I save after a change in any table through enterprise nmanager
>> I receive this error:
>> [Microsoft][ODBC SQL Server Driver] Invalid cursor state
> So why not use scripts in Query Analyzer? IMHO, there are only a few
> cases
> where Enterprise Manager should be used...
> http://www.aspfaq.com/2515
> http://www.aspfaq.com/2455
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>|||This is over your head?
ALTER TABLE <tablename> ADD <columnname> <DATATYPE>
--
http://www.aspfaq.com/
(Reverse address to reply.)
"Jéjé" <willgart_A_@.hotmail_A_.com> wrote in message
news:eat5rhyyEHA.4028@.TK2MSFTNGP15.phx.gbl...
> enterprise manager is easy to use.
> When I update or add a column, I can do this very quickly in enterprise
> manager
> using query analyzer is an overhead for me :-)
>
> "Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
> news:%23hCrneyyEHA.2624@.TK2MSFTNGP11.phx.gbl...
> >> every time I save after a change in any table through enterprise
nmanager
> >> I receive this error:
> >> [Microsoft][ODBC SQL Server Driver] Invalid cursor state
> >
> > So why not use scripts in Query Analyzer? IMHO, there are only a few
> > cases
> > where Enterprise Manager should be used...
> >
> > http://www.aspfaq.com/2515
> > http://www.aspfaq.com/2455
> >
> > --
> > http://www.aspfaq.com/
> > (Reverse address to reply.)
> >
> >
>|||yep
specially when you have a lot of columns to change/add/remove :-)
"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:ebp1VjyyEHA.2540@.TK2MSFTNGP09.phx.gbl...
> This is over your head?
> ALTER TABLE <tablename> ADD <columnname> <DATATYPE>
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>
>
> "Jéjé" <willgart_A_@.hotmail_A_.com> wrote in message
> news:eat5rhyyEHA.4028@.TK2MSFTNGP15.phx.gbl...
>> enterprise manager is easy to use.
>> When I update or add a column, I can do this very quickly in enterprise
>> manager
>> using query analyzer is an overhead for me :-)
>>
>> "Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
>> news:%23hCrneyyEHA.2624@.TK2MSFTNGP11.phx.gbl...
>> >> every time I save after a change in any table through enterprise
> nmanager
>> >> I receive this error:
>> >> [Microsoft][ODBC SQL Server Driver] Invalid cursor state
>> >
>> > So why not use scripts in Query Analyzer? IMHO, there are only a few
>> > cases
>> > where Enterprise Manager should be used...
>> >
>> > http://www.aspfaq.com/2515
>> > http://www.aspfaq.com/2455
>> >
>> > --
>> > http://www.aspfaq.com/
>> > (Reverse address to reply.)
>> >
>> >
>>
>|||> yep
> specially when you have a lot of columns to change/add/remove :-)
Okay, so is there something especially painful about learning them? It
certainly can't HURT you to have this knowledge; surely someday you will
have to connect to SQL Server without using a GUI as a crutch...|||There are different combinations of service packs that lend
themselves to having this error more often - e.g between
8.00.0859 and 8.00.0875 you can get the error more often,
version 8.00.0927 or no SP3 version 8.00.0194 you don't,
etc.
The bottom line is what Aaron keeps telling you - you should
be using Query Analyzer for this type of thing. It was
designed more for this type of activity.
-Sue
On Mon, 15 Nov 2004 11:17:34 -0500, "Jéjé"
<willgart_A_@.hotmail_A_.com> wrote:
>yep
>specially when you have a lot of columns to change/add/remove :-)
>"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
>news:ebp1VjyyEHA.2540@.TK2MSFTNGP09.phx.gbl...
>> This is over your head?
>> ALTER TABLE <tablename> ADD <columnname> <DATATYPE>
>> --
>> http://www.aspfaq.com/
>> (Reverse address to reply.)
>>
>>
>> "Jéjé" <willgart_A_@.hotmail_A_.com> wrote in message
>> news:eat5rhyyEHA.4028@.TK2MSFTNGP15.phx.gbl...
>> enterprise manager is easy to use.
>> When I update or add a column, I can do this very quickly in enterprise
>> manager
>> using query analyzer is an overhead for me :-)
>>
>> "Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
>> news:%23hCrneyyEHA.2624@.TK2MSFTNGP11.phx.gbl...
>> >> every time I save after a change in any table through enterprise
>> nmanager
>> >> I receive this error:
>> >> [Microsoft][ODBC SQL Server Driver] Invalid cursor state
>> >
>> > So why not use scripts in Query Analyzer? IMHO, there are only a few
>> > cases
>> > where Enterprise Manager should be used...
>> >
>> > http://www.aspfaq.com/2515
>> > http://www.aspfaq.com/2455
>> >
>> > --
>> > http://www.aspfaq.com/
>> > (Reverse address to reply.)
>> >
>> >
>>
>>
>|||I've the version 859
what is the 927 version? SP4? intermediate release?
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:isshp0916fff78e8q6i0rn7n1lh5a0meen@.4ax.com...
> There are different combinations of service packs that lend
> themselves to having this error more often - e.g between
> 8.00.0859 and 8.00.0875 you can get the error more often,
> version 8.00.0927 or no SP3 version 8.00.0194 you don't,
> etc.
> The bottom line is what Aaron keeps telling you - you should
> be using Query Analyzer for this type of thing. It was
> designed more for this type of activity.
> -Sue
> On Mon, 15 Nov 2004 11:17:34 -0500, "Jéjé"
> <willgart_A_@.hotmail_A_.com> wrote:
>>yep
>>specially when you have a lot of columns to change/add/remove :-)
>>"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
>>news:ebp1VjyyEHA.2540@.TK2MSFTNGP09.phx.gbl...
>> This is over your head?
>> ALTER TABLE <tablename> ADD <columnname> <DATATYPE>
>> --
>> http://www.aspfaq.com/
>> (Reverse address to reply.)
>>
>>
>> "Jéjé" <willgart_A_@.hotmail_A_.com> wrote in message
>> news:eat5rhyyEHA.4028@.TK2MSFTNGP15.phx.gbl...
>> enterprise manager is easy to use.
>> When I update or add a column, I can do this very quickly in enterprise
>> manager
>> using query analyzer is an overhead for me :-)
>>
>> "Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
>> news:%23hCrneyyEHA.2624@.TK2MSFTNGP11.phx.gbl...
>> >> every time I save after a change in any table through enterprise
>> nmanager
>> >> I receive this error:
>> >> [Microsoft][ODBC SQL Server Driver] Invalid cursor state
>> >
>> > So why not use scripts in Query Analyzer? IMHO, there are only a few
>> > cases
>> > where Enterprise Manager should be used...
>> >
>> > http://www.aspfaq.com/2515
>> > http://www.aspfaq.com/2455
>> >
>> > --
>> > http://www.aspfaq.com/
>> > (Reverse address to reply.)
>> >
>> >
>>
>>
>|||> what is the 927 version? SP4? intermediate release?
Hotfix. Only certain ones are available without contacting PSS directly.
http://www.aspfaq.com/2160
--
http://www.aspfaq.com/
(Reverse address to reply.)|||Hot fix for the following:
http://support.microsoft.com/?kbid=839688
But then you will be managing hot fixes based upon not
wanting to use Query Analyzer for writing T-SQL to maintain
your databases. Doesn't seem like a good path to go down.
So if another slammer comes out, would your company want you
to patch it and use T-SQL for table changes or would they
want you to leave the box vulnerable so you could use
Enterprise Manager to make all your table changes?
-Sue
On Mon, 15 Nov 2004 13:40:43 -0500, "Jéjé"
<willgart_A_@.hotmail_A_.com> wrote:
>I've the version 859
>what is the 927 version? SP4? intermediate release?
>"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
>news:isshp0916fff78e8q6i0rn7n1lh5a0meen@.4ax.com...
>> There are different combinations of service packs that lend
>> themselves to having this error more often - e.g between
>> 8.00.0859 and 8.00.0875 you can get the error more often,
>> version 8.00.0927 or no SP3 version 8.00.0194 you don't,
>> etc.
>> The bottom line is what Aaron keeps telling you - you should
>> be using Query Analyzer for this type of thing. It was
>> designed more for this type of activity.
>> -Sue
>> On Mon, 15 Nov 2004 11:17:34 -0500, "Jéjé"
>> <willgart_A_@.hotmail_A_.com> wrote:
>>yep
>>specially when you have a lot of columns to change/add/remove :-)
>>"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
>>news:ebp1VjyyEHA.2540@.TK2MSFTNGP09.phx.gbl...
>> This is over your head?
>> ALTER TABLE <tablename> ADD <columnname> <DATATYPE>
>> --
>> http://www.aspfaq.com/
>> (Reverse address to reply.)
>>
>>
>> "Jéjé" <willgart_A_@.hotmail_A_.com> wrote in message
>> news:eat5rhyyEHA.4028@.TK2MSFTNGP15.phx.gbl...
>> enterprise manager is easy to use.
>> When I update or add a column, I can do this very quickly in enterprise
>> manager
>> using query analyzer is an overhead for me :-)
>>
>> "Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
>> news:%23hCrneyyEHA.2624@.TK2MSFTNGP11.phx.gbl...
>> >> every time I save after a change in any table through enterprise
>> nmanager
>> >> I receive this error:
>> >> [Microsoft][ODBC SQL Server Driver] Invalid cursor state
>> >
>> > So why not use scripts in Query Analyzer? IMHO, there are only a few
>> > cases
>> > where Enterprise Manager should be used...
>> >
>> > http://www.aspfaq.com/2515
>> > http://www.aspfaq.com/2455
>> >
>> > --
>> > http://www.aspfaq.com/
>> > (Reverse address to reply.)
>> >
>> >
>>
>>
>>
>|||ok ok...
I'll try to change my working method ;-)
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:9tuhp0p5ab2leg6t7527kfe6r68n014ia8@.4ax.com...
> Hot fix for the following:
> http://support.microsoft.com/?kbid=839688
> But then you will be managing hot fixes based upon not
> wanting to use Query Analyzer for writing T-SQL to maintain
> your databases. Doesn't seem like a good path to go down.
> So if another slammer comes out, would your company want you
> to patch it and use T-SQL for table changes or would they
> want you to leave the box vulnerable so you could use
> Enterprise Manager to make all your table changes?
> -Sue
> On Mon, 15 Nov 2004 13:40:43 -0500, "Jéjé"
> <willgart_A_@.hotmail_A_.com> wrote:
>>I've the version 859
>>what is the 927 version? SP4? intermediate release?
>>"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
>>news:isshp0916fff78e8q6i0rn7n1lh5a0meen@.4ax.com...
>> There are different combinations of service packs that lend
>> themselves to having this error more often - e.g between
>> 8.00.0859 and 8.00.0875 you can get the error more often,
>> version 8.00.0927 or no SP3 version 8.00.0194 you don't,
>> etc.
>> The bottom line is what Aaron keeps telling you - you should
>> be using Query Analyzer for this type of thing. It was
>> designed more for this type of activity.
>> -Sue
>> On Mon, 15 Nov 2004 11:17:34 -0500, "Jéjé"
>> <willgart_A_@.hotmail_A_.com> wrote:
>>yep
>>specially when you have a lot of columns to change/add/remove :-)
>>"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
>>news:ebp1VjyyEHA.2540@.TK2MSFTNGP09.phx.gbl...
>> This is over your head?
>> ALTER TABLE <tablename> ADD <columnname> <DATATYPE>
>> --
>> http://www.aspfaq.com/
>> (Reverse address to reply.)
>>
>>
>> "Jéjé" <willgart_A_@.hotmail_A_.com> wrote in message
>> news:eat5rhyyEHA.4028@.TK2MSFTNGP15.phx.gbl...
>> enterprise manager is easy to use.
>> When I update or add a column, I can do this very quickly in
>> enterprise
>> manager
>> using query analyzer is an overhead for me :-)
>>
>> "Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
>> news:%23hCrneyyEHA.2624@.TK2MSFTNGP11.phx.gbl...
>> >> every time I save after a change in any table through enterprise
>> nmanager
>> >> I receive this error:
>> >> [Microsoft][ODBC SQL Server Driver] Invalid cursor state
>> >
>> > So why not use scripts in Query Analyzer? IMHO, there are only a
>> > few
>> > cases
>> > where Enterprise Manager should be used...
>> >
>> > http://www.aspfaq.com/2515
>> > http://www.aspfaq.com/2455
>> >
>> > --
>> > http://www.aspfaq.com/
>> > (Reverse address to reply.)
>> >
>> >
>>
>>
>>
>|||Related question:
Because of this same problem I have started using the query analyzer for my
query changes. I cannot find a reference for how to use ALTER to
rearrange(MOVE) columns within a table. Can someone show me an example
syntax of how to do this in TSQL?
"Jéjé" wrote:
> ok ok...
> I'll try to change my working method ;-)
>
> "Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
> news:9tuhp0p5ab2leg6t7527kfe6r68n014ia8@.4ax.com...
> > Hot fix for the following:
> > http://support.microsoft.com/?kbid=839688
> >
> > But then you will be managing hot fixes based upon not
> > wanting to use Query Analyzer for writing T-SQL to maintain
> > your databases. Doesn't seem like a good path to go down.
> > So if another slammer comes out, would your company want you
> > to patch it and use T-SQL for table changes or would they
> > want you to leave the box vulnerable so you could use
> > Enterprise Manager to make all your table changes?
> >
> > -Sue
> >
> > On Mon, 15 Nov 2004 13:40:43 -0500, "Jéjé"
> > <willgart_A_@.hotmail_A_.com> wrote:
> >
> >>I've the version 859
> >>what is the 927 version? SP4? intermediate release?
> >>
> >>"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
> >>news:isshp0916fff78e8q6i0rn7n1lh5a0meen@.4ax.com...
> >> There are different combinations of service packs that lend
> >> themselves to having this error more often - e.g between
> >> 8.00.0859 and 8.00.0875 you can get the error more often,
> >> version 8.00.0927 or no SP3 version 8.00.0194 you don't,
> >> etc.
> >> The bottom line is what Aaron keeps telling you - you should
> >> be using Query Analyzer for this type of thing. It was
> >> designed more for this type of activity.
> >>
> >> -Sue
> >>
> >> On Mon, 15 Nov 2004 11:17:34 -0500, "Jéjé"
> >> <willgart_A_@.hotmail_A_.com> wrote:
> >>
> >>yep
> >>specially when you have a lot of columns to change/add/remove :-)
> >>
> >>"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
> >>news:ebp1VjyyEHA.2540@.TK2MSFTNGP09.phx.gbl...
> >> This is over your head?
> >>
> >> ALTER TABLE <tablename> ADD <columnname> <DATATYPE>
> >>
> >> --
> >> http://www.aspfaq.com/
> >> (Reverse address to reply.)
> >>
> >>
> >>
> >>
> >> "Jéjé" <willgart_A_@.hotmail_A_.com> wrote in message
> >> news:eat5rhyyEHA.4028@.TK2MSFTNGP15.phx.gbl...
> >> enterprise manager is easy to use.
> >> When I update or add a column, I can do this very quickly in
> >> enterprise
> >> manager
> >>
> >> using query analyzer is an overhead for me :-)
> >>
> >>
> >> "Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
> >> news:%23hCrneyyEHA.2624@.TK2MSFTNGP11.phx.gbl...
> >> >> every time I save after a change in any table through enterprise
> >> nmanager
> >> >> I receive this error:
> >> >> [Microsoft][ODBC SQL Server Driver] Invalid cursor state
> >> >
> >> > So why not use scripts in Query Analyzer? IMHO, there are only a
> >> > few
> >> > cases
> >> > where Enterprise Manager should be used...
> >> >
> >> > http://www.aspfaq.com/2515
> >> > http://www.aspfaq.com/2455
> >> >
> >> > --
> >> > http://www.aspfaq.com/
> >> > (Reverse address to reply.)
> >> >
> >> >
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >
>
>|||you have to copy your table in a new one which has the right order
then delete the first table and rename the temporary table to the right name
(all in a transaction)
or you can use enterprise manager to change the order and ask to generate
the SQL statement instead-of saving the change. then execute this syntax.
"Don" <Don@.discussions.microsoft.com> wrote in message
news:140DD312-365C-45C3-9280-8082FAE8F62C@.microsoft.com...
> Related question:
> Because of this same problem I have started using the query analyzer for
> my
> query changes. I cannot find a reference for how to use ALTER to
> rearrange(MOVE) columns within a table. Can someone show me an example
> syntax of how to do this in TSQL?
> "Jéjé" wrote:
>> ok ok...
>> I'll try to change my working method ;-)
>>
>> "Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
>> news:9tuhp0p5ab2leg6t7527kfe6r68n014ia8@.4ax.com...
>> > Hot fix for the following:
>> > http://support.microsoft.com/?kbid=839688
>> >
>> > But then you will be managing hot fixes based upon not
>> > wanting to use Query Analyzer for writing T-SQL to maintain
>> > your databases. Doesn't seem like a good path to go down.
>> > So if another slammer comes out, would your company want you
>> > to patch it and use T-SQL for table changes or would they
>> > want you to leave the box vulnerable so you could use
>> > Enterprise Manager to make all your table changes?
>> >
>> > -Sue
>> >
>> > On Mon, 15 Nov 2004 13:40:43 -0500, "Jéjé"
>> > <willgart_A_@.hotmail_A_.com> wrote:
>> >
>> >>I've the version 859
>> >>what is the 927 version? SP4? intermediate release?
>> >>
>> >>"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
>> >>news:isshp0916fff78e8q6i0rn7n1lh5a0meen@.4ax.com...
>> >> There are different combinations of service packs that lend
>> >> themselves to having this error more often - e.g between
>> >> 8.00.0859 and 8.00.0875 you can get the error more often,
>> >> version 8.00.0927 or no SP3 version 8.00.0194 you don't,
>> >> etc.
>> >> The bottom line is what Aaron keeps telling you - you should
>> >> be using Query Analyzer for this type of thing. It was
>> >> designed more for this type of activity.
>> >>
>> >> -Sue
>> >>
>> >> On Mon, 15 Nov 2004 11:17:34 -0500, "Jéjé"
>> >> <willgart_A_@.hotmail_A_.com> wrote:
>> >>
>> >>yep
>> >>specially when you have a lot of columns to change/add/remove :-)
>> >>
>> >>"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
>> >>news:ebp1VjyyEHA.2540@.TK2MSFTNGP09.phx.gbl...
>> >> This is over your head?
>> >>
>> >> ALTER TABLE <tablename> ADD <columnname> <DATATYPE>
>> >>
>> >> --
>> >> http://www.aspfaq.com/
>> >> (Reverse address to reply.)
>> >>
>> >>
>> >>
>> >>
>> >> "Jéjé" <willgart_A_@.hotmail_A_.com> wrote in message
>> >> news:eat5rhyyEHA.4028@.TK2MSFTNGP15.phx.gbl...
>> >> enterprise manager is easy to use.
>> >> When I update or add a column, I can do this very quickly in
>> >> enterprise
>> >> manager
>> >>
>> >> using query analyzer is an overhead for me :-)
>> >>
>> >>
>> >> "Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
>> >> news:%23hCrneyyEHA.2624@.TK2MSFTNGP11.phx.gbl...
>> >> >> every time I save after a change in any table through
>> >> >> enterprise
>> >> nmanager
>> >> >> I receive this error:
>> >> >> [Microsoft][ODBC SQL Server Driver] Invalid cursor state
>> >> >
>> >> > So why not use scripts in Query Analyzer? IMHO, there are only
>> >> > a
>> >> > few
>> >> > cases
>> >> > where Enterprise Manager should be used...
>> >> >
>> >> > http://www.aspfaq.com/2515
>> >> > http://www.aspfaq.com/2455
>> >> >
>> >> > --
>> >> > http://www.aspfaq.com/
>> >> > (Reverse address to reply.)
>> >> >
>> >> >
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >
>>

[Microsoft][ODBC SQL Server Driver] Invalid cursor stateevery time I save in enterpris

Hi,
every time I save after a change in any table through enterprise nmanager
I receive this error:
[Microsoft][ODBC SQL Server Driver] Invalid cursor state
If I generate a script instead-of saving directly
and if I execute this script through the query analyzer all works fine!
My windows 2003 is english
my SQL Server is french
my default language is french
I've found the same error on another server which is in the same config.
any idea?
thanks.
Jerome.> every time I save after a change in any table through enterprise nmanager
> I receive this error:
> [Microsoft][ODBC SQL Server Driver] Invalid cursor state
So why not use scripts in Query Analyzer? IMHO, there are only a few cases
where Enterprise Manager should be used...
http://www.aspfaq.com/2515
http://www.aspfaq.com/2455
http://www.aspfaq.com/
(Reverse address to reply.)|||enterprise manager is easy to use.
When I update or add a column, I can do this very quickly in enterprise
manager
using query analyzer is an overhead for me :-)
"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:%23hCrneyyEHA.2624@.TK2MSFTNGP11.phx.gbl...
> So why not use scripts in Query Analyzer? IMHO, there are only a few
> cases
> where Enterprise Manager should be used...
> http://www.aspfaq.com/2515
> http://www.aspfaq.com/2455
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>|||This is over your head?
ALTER TABLE <tablename> ADD <columnname> <DATATYPE>
http://www.aspfaq.com/
(Reverse address to reply.)
"Jj" <willgart_A_@.hotmail_A_.com> wrote in message
news:eat5rhyyEHA.4028@.TK2MSFTNGP15.phx.gbl...
> enterprise manager is easy to use.
> When I update or add a column, I can do this very quickly in enterprise
> manager
> using query analyzer is an overhead for me :-)
>
> "Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
> news:%23hCrneyyEHA.2624@.TK2MSFTNGP11.phx.gbl...
nmanager[vbcol=seagreen]
>|||yep
specially when you have a lot of columns to change/add/remove :-)
"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:ebp1VjyyEHA.2540@.TK2MSFTNGP09.phx.gbl...
> This is over your head?
> ALTER TABLE <tablename> ADD <columnname> <DATATYPE>
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>
>
> "Jj" <willgart_A_@.hotmail_A_.com> wrote in message
> news:eat5rhyyEHA.4028@.TK2MSFTNGP15.phx.gbl...
> nmanager
>|||> yep
> specially when you have a lot of columns to change/add/remove :-)
Okay, so is there something especially painful about learning them? It
certainly can't HURT you to have this knowledge; surely someday you will
have to connect to SQL Server without using a GUI as a crutch...|||There are different combinations of service packs that lend
themselves to having this error more often - e.g between
8.00.0859 and 8.00.0875 you can get the error more often,
version 8.00.0927 or no SP3 version 8.00.0194 you don't,
etc.
The bottom line is what Aaron keeps telling you - you should
be using Query Analyzer for this type of thing. It was
designed more for this type of activity.
-Sue
On Mon, 15 Nov 2004 11:17:34 -0500, "Jj"
<willgart_A_@.hotmail_A_.com> wrote:

>yep
>specially when you have a lot of columns to change/add/remove :-)
>"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
>news:ebp1VjyyEHA.2540@.TK2MSFTNGP09.phx.gbl...
>|||I've the version 859
what is the 927 version? SP4? intermediate release?
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:isshp0916fff78e8q6i0rn7n1lh5a0meen@.
4ax.com...
> There are different combinations of service packs that lend
> themselves to having this error more often - e.g between
> 8.00.0859 and 8.00.0875 you can get the error more often,
> version 8.00.0927 or no SP3 version 8.00.0194 you don't,
> etc.
> The bottom line is what Aaron keeps telling you - you should
> be using Query Analyzer for this type of thing. It was
> designed more for this type of activity.
> -Sue
> On Mon, 15 Nov 2004 11:17:34 -0500, "Jj"
> <willgart_A_@.hotmail_A_.com> wrote:
>
>|||> what is the 927 version? SP4? intermediate release?
Hotfix. Only certain ones are available without contacting PSS directly.
http://www.aspfaq.com/2160
http://www.aspfaq.com/
(Reverse address to reply.)|||Hot fix for the following:
http://support.microsoft.com/?kbid=839688
But then you will be managing hot fixes based upon not
wanting to use Query Analyzer for writing T-SQL to maintain
your databases. Doesn't seem like a good path to go down.
So if another slammer comes out, would your company want you
to patch it and use T-SQL for table changes or would they
want you to leave the box vulnerable so you could use
Enterprise Manager to make all your table changes?
-Sue
On Mon, 15 Nov 2004 13:40:43 -0500, "Jj"
<willgart_A_@.hotmail_A_.com> wrote:

>I've the version 859
>what is the 927 version? SP4? intermediate release?
>"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
> news:isshp0916fff78e8q6i0rn7n1lh5a0meen@.
4ax.com...
>

[Microsoft][ODBC SQL Server Driver] error

Hi All,
A strange thing has been happening for a month or so when I retrive data via
QA. Sometimes the queries fail to run and I receive the following error
messages.
[Microsoft][ODBC SQL Server Driver]Protocol error in TDS stream
[Microsoft][ODBC SQL Server Driver]TDS buffer length too large
[Microsoft][ODBC SQL Server Driver]Unknown token received from SQL Server
Re-reunning the query does not help only if I re-connect to the server. I
have checked Books Online and the only info is the following.
'The TDS stream from the server is invalid. This error is typically caused
by a problem on the server. Check the SQL Server error log.'
To tell you the truth I have not found anything suspicious.
Could you help me with it? Any help is welcome.
Thanks.
Kolos
Make you have applied the latest service packs. You also
need to apply the service packs on the client where you run
Query Analyzer.
-Sue
On Wed, 28 Feb 2007 01:52:09 -0800, Kolos
<Kolos@.discussions.microsoft.com> wrote:

>Hi All,
>A strange thing has been happening for a month or so when I retrive data via
>QA. Sometimes the queries fail to run and I receive the following error
>messages.
>[Microsoft][ODBC SQL Server Driver]Protocol error in TDS stream
>[Microsoft][ODBC SQL Server Driver]TDS buffer length too large
>[Microsoft][ODBC SQL Server Driver]Unknown token received from SQL Server
>Re-reunning the query does not help only if I re-connect to the server. I
>have checked Books Online and the only info is the following.
>'The TDS stream from the server is invalid. This error is typically caused
>by a problem on the server. Check the SQL Server error log.'
>To tell you the truth I have not found anything suspicious.
>Could you help me with it? Any help is welcome.
>Thanks.
>Kolos

[Microsoft][ODBC SQL Server Driver] error

Hi All,
A strange thing has been happening for a month or so when I retrive data via
QA. Sometimes the queries fail to run and I receive the following error
messages.
[Microsoft][ODBC SQL Server Driver]Protocol error in TDS stream
[Microsoft][ODBC SQL Server Driver]TDS buffer length too large
[Microsoft][ODBC SQL Server Driver]Unknown token received from SQL S
erver
Re-reunning the query does not help only if I re-connect to the server. I
have checked Books Online and the only info is the following.
'The TDS stream from the server is invalid. This error is typically caused
by a problem on the server. Check the SQL Server error log.'
To tell you the truth I have not found anything suspicious.
Could you help me with it? Any help is welcome.
Thanks.
KolosMake you have applied the latest service packs. You also
need to apply the service packs on the client where you run
Query Analyzer.
-Sue
On Wed, 28 Feb 2007 01:52:09 -0800, Kolos
<Kolos@.discussions.microsoft.com> wrote:

>Hi All,
>A strange thing has been happening for a month or so when I retrive data vi
a
>QA. Sometimes the queries fail to run and I receive the following error
>messages.
>[Microsoft][ODBC SQL Server Driver]Protocol error in TDS stream
>[Microsoft][ODBC SQL Server Driver]TDS buffer length too large
>[Microsoft][ODBC SQL Server Driver]Unknown token received from SQL
Server
>Re-reunning the query does not help only if I re-connect to the server. I
>have checked Books Online and the only info is the following.
>'The TDS stream from the server is invalid. This error is typically caused
>by a problem on the server. Check the SQL Server error log.'
>To tell you the truth I have not found anything suspicious.
>Could you help me with it? Any help is welcome.
>Thanks.
>Kolos

[Microsoft][ODBC Microsoft Access Driver] Too few parameters. Expected 2

Heres my code:

<%
'Dimension variables
Dim adoCon 'Holds the Database Connection Object
Dim rsAddLinks 'Holds the recordset for the new record to be added
Dim strSQL 'Holds the SQL query to query the database

'Create an ADO connection object
Set adoCon = Server.CreateObject("ADODB.Connection")

'Set an active connection to the Connection object using a DSN-less connection
adoCon.Open "DRIVER={Microsoft Access Driver (*.mdb)}; DBQ=" & Server.MapPath("links.mdb")

'Create an ADO recordset object
Set rsAddLinks = Server.CreateObject("ADODB.Recordset")

'Initialise the strSQL variable with an SQL statement to query the database
strSQL = "SELECT tblLinks.URL, tblLinks.Description FROM tblLinks;"

'Set the cursor type we are using so we can navigate through the recordset
rsAddLinks.CursorType = 2

'Set the lock type so that the record is locked by ADO when it is updated
rsAddLinks.LockType = 3

'Open the recordset with the SQL query
rsAddLinks.Open strSQL, adoCon

'Tell the recordset we are adding a new record to it
rsAddLinks.AddNew

'Add a new record to the recordset
rsAddLinks.Fields("URL") = Request.Form("url")
rsAddLinks.Fields("Description") = Request.Form("description")

'Write the updated recordset to the database
rsAddLinks.Update

'Reset server objects
rsAddLinks.Close
Set rsAddLinks = Nothing
Set adoCon = Nothing

'Redirect to the guestbook.asp page
Response.Redirect "links.asp"
%>

When i run the code I get: [Microsoft][ODBC Microsoft Access Driver] Too few parameters. Expected 2

Can someone please help?

--NickTry replacing % in place of *.|||Ok, thanks, but now it says

[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified

Can you help me on this?

--Nick

PS: If your wondering, im reletively new at asp thats why I havent been able to figure this out myself.|||By all means refer to this KBA (http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/Q169/3/77.asp&NoWebContent=1) to get rid of the issues and follwup.|||That really didn't help me much.|||thanks for all your help. I figured it out! i was linking to the page directly when i should have been using the page b4 it that links to it...

if that makes any scence

[Microsoft][ODBC Microsoft Access Driver] System resource exceeded

odbc_pconnect() [function.odbc-pconnect]: SQL error: [Microsoft][ODBC Microsoft Access Driver] System resource exceeded., SQL state S1001 in SQLConnect

we got the error with access 2000 database and PHP as prog. language .

we created dsn for the connection.

reboot solves the problem. but we need another solution better than this.

You might be running a query that is returning too many records.

Try limiting the query by usng the WHERE clause. Try adding more memory to your computer

Also shifting to SQL Server 2005 for larger databases would improve performance.

Regards,

http://www.Designing-Systems.com

|||You might also want to check out that you do not keep creating new connections instead of reusing existing ones. Check your PSP settings
(if you haven't already) and see whether you have pooling support from PHP or ODBC driver manager.|||

Hi there,

we solved this problem after converting access db to mysql. It solves problem for this.

thanks

|||

If the problem is any of the problems suggested by the above posters, then shifting underlying database representation will just defer the problem until your database gets larger. While your current solution has clearly reduced the pressure to fix the problem, looking into reducing query load, connection usage, and memory overhead on the client side will certainly be beneficial for building a strategy to grow your database.

Hope this helps,

John (MSFT)

|||

We solved this issue. Please close this thread.

Thank you

Jitendra Chavan

[Microsoft][ODBC Microsoft Access Driver] System resource exceeded

odbc_pconnect() [function.odbc-pconnect]: SQL error: [Microsoft][ODBC Microsoft Access Driver] System resource exceeded., SQL state S1001 in SQLConnect

we got the error with access 2000 database and PHP as prog. language .

we created dsn for the connection.

reboot solves the problem. but we need another solution better than this.

You might be running a query that is returning too many records.

Try limiting the query by usng the WHERE clause. Try adding more memory to your computer

Also shifting to SQL Server 2005 for larger databases would improve performance.

Regards,

http://www.Designing-Systems.com

|||You might also want to check out that you do not keep creating new connections instead of reusing existing ones. Check your PSP settings
(if you haven't already) and see whether you have pooling support from PHP or ODBC driver manager.|||

Hi there,

we solved this problem after converting access db to mysql. It solves problem for this.

thanks

|||

If the problem is any of the problems suggested by the above posters, then shifting underlying database representation will just defer the problem until your database gets larger. While your current solution has clearly reduced the pressure to fix the problem, looking into reducing query load, connection usage, and memory overhead on the client side will certainly be beneficial for building a strategy to grow your database.

Hope this helps,

John (MSFT)

|||

We solved this issue. Please close this thread.

Thank you

Jitendra Chavan

[Microsoft][ODBC Microsoft Access Driver] System resource exceeded

odbc_pconnect() [function.odbc-pconnect]: SQL error: [Microsoft][ODBC Microsoft Access Driver] System resource exceeded., SQL state S1001 in SQLConnect

we got the error with access 2000 database and PHP as prog. language .

we created dsn for the connection.

reboot solves the problem. but we need another solution better than this.

You might be running a query that is returning too many records.

Try limiting the query by usng the WHERE clause. Try adding more memory to your computer

Also shifting to SQL Server 2005 for larger databases would improve performance.

Regards,

http://www.Designing-Systems.com

|||You might also want to check out that you do not keep creating new connections instead of reusing existing ones. Check your PSP settings
(if you haven't already) and see whether you have pooling support from PHP or ODBC driver manager.|||

Hi there,

we solved this problem after converting access db to mysql. It solves problem for this.

thanks

|||

If the problem is any of the problems suggested by the above posters, then shifting underlying database representation will just defer the problem until your database gets larger. While your current solution has clearly reduced the pressure to fix the problem, looking into reducing query load, connection usage, and memory overhead on the client side will certainly be beneficial for building a strategy to grow your database.

Hope this helps,

John (MSFT)

|||

We solved this issue. Please close this thread.

Thank you

Jitendra Chavan

[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified

trying to install sql server2005 on a windows 2003 server box.

getting msg below at the sql server . i looked at other posts on trying to uninstall SQL Native Access Client and norton antivirus. i could never find the snac on the add - remove programs and this server does not have a virus protection program yet.

here's the history of the installs on the server:

wanted to test a 2005 upgrade so:

1) installed sql server 2000 then sp4 then restored some databases to it - all OK

2) tried to upgrade to sql 2005 but ran into problems and left it at that.

had a disk drive crash on the d drive so lost the installs but not the operating system

when the drive was replaced, left alone for a while

then wanted to test a straight 2005 install

1) removed the broken 2005 attempt

2) removed the 2000

3) installed 2005 and got the error on the subject line:

TITLE: Microsoft SQL Server 2005 Setup

SQL Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified Refer to server error logs and setup logs for more information. For details on how to view setup logs, see "How to View Setup Log Files" in SQL Server Books Online.

i've gone through as many of the forums that i can and have tried several things - like uninstalling 2005 and installing pieces and parts but but nothing seems to work.

Thanks!

Dan <><

It sounds like the SNAC version you have might be corrupt or incompatible.

Go to Add or Remove Programs and find the listing for "Microsoft SQL Native Client". Remove this component.

Then try the install again.

Michelle

|||

Thank you so much for replying. last attempt was to install just the sql server commonent - no others like analysis services or integration services.

i looked at the add / remove programs both before, during and after the sql server database services failed attempt and the add/remove has never shown a program called MS sql native access client (SNAC).

when i start the install, the installing prerequisites window shows the two components that will be installed: snac and the sql server 2005 setup support files. the snac goes to a green arrow almost immediately while the 2005 setup files takes a few seconds. i dont know if that helps or not.

the add remove programs just has:

microsoft .net framwork 2.0|||

It definatel looks like the problems is the "Microsoft SQL Server Native Client" layer. At this point your machine thinks that it is already installed but the install is broken.

Follow the directions in the following article to clean up the machine and then try again.

http://support.microsoft.com/kb/909967

Michelle

|||

uninstall manually - did the following (shows issues with some of the directions)

it said to delete the local security groups. but i never could figure out how to do. the article it mensions didnt (at least to me) show how to delete. so i just went on|||

i went out to the website and downloaded the .msi file for snac. it was slightly different from the .msi that came on the DVD (3511k vs 3516k).

the dvd version when i clicked on the msi file just returned me back to windows explorer.

the snac from microsoft's website executed and finally installed the snac.

the install worked perfectly after that.

thanks for your help

|||

Actually that was a good work around as downloading a newer version would have forced the install to run again where as in the previous case it was failing quickly becuase it thought it was laready installed.

Glad you got you machine back.

Michelle

|||

Hi,

I've been handling SQL Server upgrades for many years. The most dangerous path for an upgrade is to directly upgrade 2000 to 2005 (or 7.0 to 2000). That's because you create the risk of destroying the databases on the existing server and causing data loss.

The best approach embraces the fact that we typically upgrade a windows server when the mfg warranty on the hardware has expired. So, you have a new box and windows server. If you don't, the store the backups on another resource (disk, tape, flash drive, etc...) and copy from or restore from that resource. Rebuild the Windows server or uninstall SQL Server 2000. (I would have fresh windows to insure the best chance of success.)

Install SQL 2005 & configure on the new W03 SP1 server. migrate the users. (this worked easily with 2K but MS has hosed that functionality in 2005 from what I can see; you must use a script they provided that is flaky. You will need to manually create the users it fails to migrate.) Backup the dbs on 2K, shut down 2K on the old machine and restore the dbs to 2005. associate the users with the logins.

Now you have a fullly upgraded database server and your databases are unhosed. This may not be elegant but it guarantees the MS upgrade process won't destroy your databases or bring down your business for days.

If you have a completely hosed system, then rebuild the system (and the drives) and follow the steps above to a successful conclusion.

z.

[Microsoft][ ODBC SQL Server Drive ] Timeout expired

I am running a VB application which makes connection to the SQL server
database using DSN connection using ODBC. This application pulls data using
stored procedure. The application does not insert / delete / update data.
The application was working fine since it has been installed (more than ONE
year). Suddendly it has started generating runtime error '-2147217871
(80040e31)'. I have taken the following actions so far to identify the
problem:
1. Checked user permission set on the database. Its fine. ODBC test
connection is successful.
2. Debugged VB source. It successfully makes connection to the database but
generated error while executing Command object which is using a stored
procedure which pulls the data into the grid.
3. Changed the timeout property of the Command object to 60 seconds. Still
generating error.
4. Copy pasted Query from stored procedure into Query Analyzer. The query
ran within 10 seconds generating desired resultset. Hence, Table index /
fragmentation problem is ruled out.
5. Copy data and Object from Live database into another database on the same
server using DTS wizard. Changed database name in the ODBC configuration
pointing it to the new database having same data & objects (including users &
permissions). The application ran succussefully without generating any
error. Hence database server problem is ruled out.
6. The stored procedure used by the command object in VB code fails to
execute.
Any help on how to fix this problem?
Manish Acharya
Systems Analyst & database developer
Task Transactions Ltd., New Zealand.
Have you considered taking ODBC or SQL Server Profiler traces? These might
give more clues.
"Manish Acharya" <Manish Acharya@.discussions.microsoft.com> wrote in message
news:B4ACB30B-2D2B-4473-A802-6CB2E145BD82@.microsoft.com...
>I am running a VB application which makes connection to the SQL server
> database using DSN connection using ODBC. This application pulls data
> using
> stored procedure. The application does not insert / delete / update data.
> The application was working fine since it has been installed (more than
> ONE
> year). Suddendly it has started generating runtime error '-2147217871
> (80040e31)'. I have taken the following actions so far to identify the
> problem:
> 1. Checked user permission set on the database. Its fine. ODBC test
> connection is successful.
> 2. Debugged VB source. It successfully makes connection to the database
> but
> generated error while executing Command object which is using a stored
> procedure which pulls the data into the grid.
> 3. Changed the timeout property of the Command object to 60 seconds.
> Still
> generating error.
> 4. Copy pasted Query from stored procedure into Query Analyzer. The query
> ran within 10 seconds generating desired resultset. Hence, Table index /
> fragmentation problem is ruled out.
> 5. Copy data and Object from Live database into another database on the
> same
> server using DTS wizard. Changed database name in the ODBC configuration
> pointing it to the new database having same data & objects (including
> users &
> permissions). The application ran succussefully without generating any
> error. Hence database server problem is ruled out.
> 6. The stored procedure used by the command object in VB code fails to
> execute.
> Any help on how to fix this problem?
> Manish Acharya
> Systems Analyst & database developer
> Task Transactions Ltd., New Zealand.
|||Thanks Chris for your response. I have been working on SQL server profiler
traces to identify this problem. My experience on using SQL server profiler
is a bit limited and I see this as an opportunity to hone my skills in this
area. Your reply confirms that I am on the right direction. I will post the
solution in this discussion group once I crack it.
Cheers.
Manish Acharya.
"Chris Lee[MS]" wrote:

> Have you considered taking ODBC or SQL Server Profiler traces? These might
> give more clues.
> "Manish Acharya" <Manish Acharya@.discussions.microsoft.com> wrote in message
> news:B4ACB30B-2D2B-4473-A802-6CB2E145BD82@.microsoft.com...
>
>
|||Hi Manish Acharya,
Had you find the solution for the problem above? I have the same problem
like you, so hope you can shared the solution with us.
Thank you.

[Microsoft][ ODBC SQL Server Drive ] Timeout expired

I am running a VB application which makes connection to the SQL server
database using DSN connection using ODBC. This application pulls data using
stored procedure. The application does not insert / delete / update data.
The application was working fine since it has been installed (more than ONE
year). Suddendly it has started generating runtime error '-2147217871
(80040e31)'. I have taken the following actions so far to identify the
problem:
1. Checked user permission set on the database. Its fine. ODBC test
connection is successful.
2. Debugged VB source. It successfully makes connection to the database but
generated error while executing Command object which is using a stored
procedure which pulls the data into the grid.
3. Changed the timeout property of the Command object to 60 seconds. Still
generating error.
4. Copy pasted Query from stored procedure into Query Analyzer. The query
ran within 10 seconds generating desired resultset. Hence, Table index /
fragmentation problem is ruled out.
5. Copy data and Object from Live database into another database on the same
server using DTS wizard. Changed database name in the ODBC configuration
pointing it to the new database having same data & objects (including users
&
permissions). The application ran succussefully without generating any
error. Hence database server problem is ruled out.
6. The stored procedure used by the command object in VB code fails to
execute.
Any help on how to fix this problem?
Manish Acharya
Systems Analyst & database developer
Task Transactions Ltd., New Zealand.Have you considered taking ODBC or SQL Server Profiler traces? These might
give more clues.
"Manish Acharya" <Manish Acharya@.discussions.microsoft.com> wrote in message
news:B4ACB30B-2D2B-4473-A802-6CB2E145BD82@.microsoft.com...
>I am running a VB application which makes connection to the SQL server
> database using DSN connection using ODBC. This application pulls data
> using
> stored procedure. The application does not insert / delete / update data.
> The application was working fine since it has been installed (more than
> ONE
> year). Suddendly it has started generating runtime error '-2147217871
> (80040e31)'. I have taken the following actions so far to identify the
> problem:
> 1. Checked user permission set on the database. Its fine. ODBC test
> connection is successful.
> 2. Debugged VB source. It successfully makes connection to the database
> but
> generated error while executing Command object which is using a stored
> procedure which pulls the data into the grid.
> 3. Changed the timeout property of the Command object to 60 seconds.
> Still
> generating error.
> 4. Copy pasted Query from stored procedure into Query Analyzer. The query
> ran within 10 seconds generating desired resultset. Hence, Table index /
> fragmentation problem is ruled out.
> 5. Copy data and Object from Live database into another database on the
> same
> server using DTS wizard. Changed database name in the ODBC configuration
> pointing it to the new database having same data & objects (including
> users &
> permissions). The application ran succussefully without generating any
> error. Hence database server problem is ruled out.
> 6. The stored procedure used by the command object in VB code fails to
> execute.
> Any help on how to fix this problem?
> Manish Acharya
> Systems Analyst & database developer
> Task Transactions Ltd., New Zealand.|||Thanks Chris for your response. I have been working on SQL server profiler
traces to identify this problem. My experience on using SQL server profiler
is a bit limited and I see this as an opportunity to hone my skills in this
area. Your reply confirms that I am on the right direction. I will post th
e
solution in this discussion group once I crack it.
Cheers.
Manish Acharya.
"Chris Lee[MS]" wrote:

> Have you considered taking ODBC or SQL Server Profiler traces? These might
> give more clues.
> "Manish Acharya" <Manish Acharya@.discussions.microsoft.com> wrote in messa
ge
> news:B4ACB30B-2D2B-4473-A802-6CB2E145BD82@.microsoft.com...
>
>|||Hi Manish Acharya,
Had you find the solution for the problem above? I have the same problem
like you, so hope you can shared the solution with us.
Thank you.