Internet integration: state

Showing posts with label state. Show all posts

Wednesday, March 21, 2012

Invalid locale ID

Getting the following error in SQL 2005 :
Msg 7696, Level 16, State 10, Line 1
Invalid locale ID was specified. Please verify that the locale ID is correct
and corresponding language resource has been installed.
Well my question is : Is it possible to install a language or do I have to
accept the languages installed. My desired language is danish (locale id
1030) and it is not installed. I can see this by querying
sys.fulltext_languages. Well if it's not possible to install the language
then it is quite useless because I want to use the rules for the danish
language not sweduisk, english or german. It's not a new feature for me when
it is possible to choose language using Contains and Freetext if my desired
language isn't there. But here is the funny part. The language was present
in the Beta Version. What has happened ? Is Denmark wiped of the map since
then ?
Anybody knows ?
If it's not possible then let me know because then I can't use fulltext in
2005 either.
Regards

Bobby Henningsen
Bobby wrote on Wed, 25 Jan 2006 11:19:30 +0100:

> Getting the following error in SQL 2005 :
> Msg 7696, Level 16, State 10, Line 1
> Invalid locale ID was specified. Please verify that the locale ID is
> correct and corresponding language resource has been installed.
> Well my question is : Is it possible to install a language or do I have to
> accept the languages installed. My desired language is danish (locale id
> 1030) and it is not installed. I can see this by querying
> sys.fulltext_languages. Well if it's not possible to install the language
> then it is quite useless because I want to use the rules for the danish
> language not sweduisk, english or german. It's not a new feature for me
> when it is possible to choose language using Contains and Freetext if my
> desired language isn't there. But here is the funny part. The language was
> present in the Beta Version. What has happened ? Is Denmark wiped of the
> map since then ?
> Anybody knows ?
> If it's not possible then let me know because then I can't use fulltext in
> 2005 either.
http://support.microsoft.com/kb/908441/en-us
As of the Sept CTP version of SQL Server 2005 the Danish word breaker is not
installed, along with some other languages, as these are 3rd party supplied
and not from Microsoft. The above link has information on how to add the
missing languages to the CTP, which I guess should work on the final release
too. However, the actual entries needed to add to the registry are missing
for the Danish breaker, so you might need to contact MS to get them to
update this article. There is a danlr.dll in the Binn dir in SQL Server 2005
(at least on my server there is), so it looks like the file ships with SQL
Server 2005, it just doesn't get enabled.
Dan
|||Hi Dan,
thanx a bunch. It works fine. Well had to restart the machine (hmm maby
reatrting the services would do but my VPC kind of "died"). But following
the article worked just fine. So now I'm much much happier

So we can
conclude that it works in RTM. The dll's are there.
Regards

Bobby Henningsen
"Daniel Crichton" <msnews@.worldofspack.co.uk> skrev i en meddelelse
news:uY410ZaIGHA.3120@.TK2MSFTNGP10.phx.gbl...
> Bobby wrote on Wed, 25 Jan 2006 11:19:30 +0100:
>
> http://support.microsoft.com/kb/908441/en-us
> As of the Sept CTP version of SQL Server 2005 the Danish word breaker is
> not installed, along with some other languages, as these are 3rd party
> supplied and not from Microsoft. The above link has information on how to
> add the missing languages to the CTP, which I guess should work on the
> final release too. However, the actual entries needed to add to the
> registry are missing for the Danish breaker, so you might need to contact
> MS to get them to update this article. There is a danlr.dll in the Binn
> dir in SQL Server 2005 (at least on my server there is), so it looks like
> the file ships with SQL Server 2005, it just doesn't get enabled.
> Dan
>

Monday, March 19, 2012

Invalid cursor state?

quote:

> I am trying to make design changes to a SQL table i just created and I

keep

quote:

> getting this error:
> 'Drug_Alcohol' table
> - Unable to modify table.
> ODBC error: [Microsoft][ODBC SQL Server Driver]Invalid cursor state
> It says in books online that this error can be caused if the sql server

runs

quote:

> out of resources while attempting to save. The database I created is new
> and the file size is still only 4megs. I tried increasing the size, but I
> still get the error.
> Does anyone know what might be happening? The only way I can make changes
> to a table now is to recreate a new table with the updated changes and
> delete the old one. I am running SQL server 2000 with service pack 3a.
>

|||The table has 5 columns:
Drug_AlcoholID int 4
DriverID int 4 Allow Nulls
PullDate smalldatetime 4
Pulltype int 4 Allow Nulls
Results char 20 Allow Nulls
I just created the table and there is no data in it.
I get the error if I try to uncheck allow nulls, change the first field to
an identity field, delete a column, or try to add a new column.
I am using Enterprise Manager so I do not see the ALTER TABLE statement.|||Has your local Enterprise Manager (assuming client tools only) been updated
to SP3? Is it even SQL Server 2000? Make sure both client and server are
the same version. Is SQL Server in the correct compatibility mode? You
might have problems changing table properties like that through a 2000 GUI
(which can issue ALTER TABLE calls under the covers) if the underlying
database is actually in 6.5 mode, for example.
Open Query Analyzer, connect to the server, and run:
EXEC sp_dbcmptlevel 'database_name'
This should be in 70 or 80, or else you won't be able to issue many commands
resembling ALTER TABLE.
What operating system are you on locally? What type of authentication are
you using (SQL or Windows)? See http://support.microsoft.com/?id=243292
Also, if you are on a Win9x platform and are using Windows authentication,
you might consider using SQL authentication instead.
Was this database created by upsizing from Access?
Might also see http://support.microsoft.com/?id=821334
Also, most of these operations can and should be handled in Query Analyzer
(ALTER TABLE, EXEC sp_rename, etc). That way you can save your scripts,
check them into source safe, but more meaningful errors when they break,
etc.
Adding the IDENTITY property to an existing column is quite a bit of work...
the database has to make a duplicate table, copy all the rows, drop the old
table, and rename the new one, and keep the table off-limits to all other
processes throughout the task. I suggest if you want IDENTITY you decide so
up front, before the table has data in it...
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"REB" <russ@.bjorgaard.com> wrote in message
news:#76622R5DHA.564@.TK2MSFTNGP10.phx.gbl...

quote:

> The table has 5 columns:
> Drug_AlcoholID int 4
> DriverID int 4 Allow Nulls
> PullDate smalldatetime 4
> Pulltype int 4 Allow Nulls
> Results char 20 Allow Nulls
> I just created the table and there is no data in it.
> I get the error if I try to uncheck allow nulls, change the first field to
> an identity field, delete a column, or try to add a new column.
> I am using Enterprise Manager so I do not see the ALTER TABLE statement.
>

|||Thanks for the response. Using Query analyzer to make the table changes
works just fine (I just had to learn the syntax). Enterprise Manager was
installed with my SQL Server 2000 Standard edition on my test server, which
is running windows server 2003. I have SP3a installed.
Is there a seperate download to update the Enterprise Manager? When I look
under help it says my version of Enterprise Manager is 8.0|||I have been getting the same problem, too. Our scenario:
Server:
Windows Server 2003
SQL 2000 SP3a
MDAC 2.8 with KB832483 hotfix installed
Client 1:
XP Pro SP1a
MDAC 2.8 with KB832483 hotfix installed
Client 2:
XP Home SP1a
MDAC 2.8 (no hotfix installed)
(Also tried Enterprise Manager from server console)
When trying to add column, delete column, or uncheck allow nulls through Ent
erprise Manager, I get the same "Invalid Cursor State" message. This happen
s when performing these operations on any table in any database on the serve
r. However, executing a sc
ript through Query Analyzer to perform these functions causes not problems.
On the XP Pro machine, I have SQL Server 2000 Developer and DO NOT get any o
f these problems.
Regarding the 2003 server, I have verified the following:
Compatibility level of all databases is 80
Connecting to server using SQL or Windows Authentication makes no difference
Connecting using sa or a variety of db admin users makes no difference
No databases were upsized from Access (in fact, all DBs and objects were cre
ated within the last two months from either EM or QA)
My last successful attempt to perform the above operations was Jan 27. The
only configuation change to the server was Jan 29 to install the KB832483 ho
tfix. The next attempt to perform these operations was today and had the pr
oblems indicated above.
I also:
1) Reinstalled MDAC 2.8 on Server, attempted operation from Client 1 and got
error
2) Reinstalled MDAC 2.8 on Client 1, attempted operation from Client 1 and g
ot error
3) Reinstalled KB832483 hotfix on Client 1, attempted operation from Client
1 and got error
4) Reinstalled KB832483 hotfix on Server, attempted operation from Client 1
and got error
This is a development server, so I[m open to trying something radical if nee
ded. Any other suggestions?
John|||What Version of SQL Server do you have? 8.00.760(SP3)?
"JSD" <anonymous@.discussions.microsoft.com> wrote in message
news:815C57B0-77A9-4102-A772-D3849A599DD0@.microsoft.com...

quote:

> I have been getting the same problem, too. Our scenario:
> Server:
> Windows Server 2003
> SQL 2000 SP3a
> MDAC 2.8 with KB832483 hotfix installed
> Client 1:
> XP Pro SP1a
> MDAC 2.8 with KB832483 hotfix installed
> Client 2:
> XP Home SP1a
> MDAC 2.8 (no hotfix installed)
> (Also tried Enterprise Manager from server console)
>
> When trying to add column, delete column, or uncheck allow nulls through

Enterprise Manager, I get the same "Invalid Cursor State" message. This
happens when performing these operations on any table in any database on the
server. However, executing a script through Query Analyzer to perform these
functions causes not problems.

quote:

> On the XP Pro machine, I have SQL Server 2000 Developer and DO NOT get any

of these problems.

quote:

> Regarding the 2003 server, I have verified the following:
> Compatibility level of all databases is 80
> Connecting to server using SQL or Windows Authentication makes no

difference

quote:

> Connecting using sa or a variety of db admin users makes no difference
> No databases were upsized from Access (in fact, all DBs and objects were

created within the last two months from either EM or QA)

quote:

>
> My last successful attempt to perform the above operations was Jan 27.

The only configuation change to the server was Jan 29 to install the
KB832483 hotfix. The next attempt to perform these operations was today and
had the problems indicated above.

quote:

> I also:
> 1) Reinstalled MDAC 2.8 on Server, attempted operation from Client 1 and

got error

quote:

> 2) Reinstalled MDAC 2.8 on Client 1, attempted operation from Client 1 and

got error

quote:

> 3) Reinstalled KB832483 hotfix on Client 1, attempted operation from

Client 1 and got error

quote:

> 4) Reinstalled KB832483 hotfix on Server, attempted operation from Client

1 and got error

quote:

>
> This is a development server, so I[m open to trying something radical if

needed. Any other suggestions?

quote:

> John

|||What is the level of SQL Server on the clients (they should be at the same
SP level as the server)? Why have you not updated client 2 with the MDAC
hotfix?
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"JSD" <anonymous@.discussions.microsoft.com> wrote in message
news:815C57B0-77A9-4102-A772-D3849A599DD0@.microsoft.com...

quote:

> I have been getting the same problem, too. Our scenario:
> Server:
> Windows Server 2003
> SQL 2000 SP3a
> MDAC 2.8 with KB832483 hotfix installed
> Client 1:
> XP Pro SP1a
> MDAC 2.8 with KB832483 hotfix installed
> Client 2:
> XP Home SP1a
> MDAC 2.8 (no hotfix installed)
> (Also tried Enterprise Manager from server console)
>
> When trying to add column, delete column, or uncheck allow nulls through

quote:

> On the XP Pro machine, I have SQL Server 2000 Developer and DO NOT get any

of these problems.

quote:

> Regarding the 2003 server, I have verified the following:
> Compatibility level of all databases is 80
> Connecting to server using SQL or Windows Authentication makes no

difference

quote:

> Connecting using sa or a variety of db admin users makes no difference
> No databases were upsized from Access (in fact, all DBs and objects were

created within the last two months from either EM or QA)

quote:

>
> My last successful attempt to perform the above operations was Jan 27.

The only configuation change to the server was Jan 29 to install the
KB832483 hotfix. The next attempt to perform these operations was today and
had the problems indicated above.

quote:

> I also:
> 1) Reinstalled MDAC 2.8 on Server, attempted operation from Client 1 and

got error

quote:

> 2) Reinstalled MDAC 2.8 on Client 1, attempted operation from Client 1 and

got error

quote:

> 3) Reinstalled KB832483 hotfix on Client 1, attempted operation from

Client 1 and got error

quote:

> 4) Reinstalled KB832483 hotfix on Server, attempted operation from Client

1 and got error

quote:

>
> This is a development server, so I[m open to trying something radical if

needed. Any other suggestions?

quote:

> John

|||SP3 (8.00.859) is installed on the 2003 server, SP3 (8.00.760) on the SQL Se
rver Developer on Client 1. Both Client 1 and Client 2 have SP3a applied to
the client tools, also.
Client 2 belongs to a user who does not regularly keep up with MDAC updates;
therefore, the hotfix was not installed. I wanted to attempt the operation
s on Client 2 to help rule out wheter the hotfix may have caused the problem
on Client 1.
I forgot to mention that we also installed Reporting Services on the 2003 se
rver on the 29th. I e-mailed this question to MS and they didn't think that
installation caused this problem. I can't find a cross-reference to determ
ine how the 2003 server got
8.00.859, so I suspect this is due to installing Reporting Services. I'm do
ubting whether uninstalling Reporting Services would get that server back to
8.00.760.
Any ideas?|||>> I can't find a cross-reference to determine how the 2003 server got
8.00.859, so I suspect this is due to installing Reporting Services.
No, this has nothing to do with RS. 859 is the most recent *publicly*
available hotfix that I'm aware of. See
http://support.microsoft.com/?kbid=821334
You can trace specific version #s here:
http://www.aspfaq.com/2160
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/

Invalid cursor state?

I am trying to make design changes to a SQL table i just created and I keep
getting this error:
'Drug_Alcohol' table
- Unable to modify table.
ODBC error: [Microsoft][ODBC SQL Server Driver]Invalid cursor state
It says in books online that this error can be caused if the sql server runs
out of resources while attempting to save. The database I created is new
and the file size is still only 4megs. I tried increasing the size, but I
still get the error.
Does anyone know what might be happening? The only way I can make changes
to a table now is to recreate a new table with the updated changes and
delete the old one. I am running SQL server 2000 with service pack 3a.Maybe you could show the current structure of the table, sample data, and
the ALTER TABLE statement.
Or, we could guess all day...
--
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"REB" <russ@.bjorgaard.com> wrote in message
news:#VKtrpR5DHA.504@.TK2MSFTNGP11.phx.gbl...
> I am trying to make design changes to a SQL table i just created and I
keep
> getting this error:
> 'Drug_Alcohol' table
> - Unable to modify table.
> ODBC error: [Microsoft][ODBC SQL Server Driver]Invalid cursor state
> It says in books online that this error can be caused if the sql server
runs
> out of resources while attempting to save. The database I created is new
> and the file size is still only 4megs. I tried increasing the size, but I
> still get the error.
> Does anyone know what might be happening? The only way I can make changes
> to a table now is to recreate a new table with the updated changes and
> delete the old one. I am running SQL server 2000 with service pack 3a.
>|||The table has 5 columns:
Drug_AlcoholID int 4
DriverID int 4 Allow Nulls
PullDate smalldatetime 4
Pulltype int 4 Allow Nulls
Results char 20 Allow Nulls
I just created the table and there is no data in it.
I get the error if I try to uncheck allow nulls, change the first field to
an identity field, delete a column, or try to add a new column.
I am using Enterprise Manager so I do not see the ALTER TABLE statement.|||Has your local Enterprise Manager (assuming client tools only) been updated
to SP3? Is it even SQL Server 2000? Make sure both client and server are
the same version. Is SQL Server in the correct compatibility mode? You
might have problems changing table properties like that through a 2000 GUI
(which can issue ALTER TABLE calls under the covers) if the underlying
database is actually in 6.5 mode, for example.
Open Query Analyzer, connect to the server, and run:
EXEC sp_dbcmptlevel 'database_name'
This should be in 70 or 80, or else you won't be able to issue many commands
resembling ALTER TABLE.
What operating system are you on locally? What type of authentication are
you using (SQL or Windows)? See http://support.microsoft.com/?id=243292
Also, if you are on a Win9x platform and are using Windows authentication,
you might consider using SQL authentication instead.
Was this database created by upsizing from Access?
Might also see http://support.microsoft.com/?id=821334
Also, most of these operations can and should be handled in Query Analyzer
(ALTER TABLE, EXEC sp_rename, etc). That way you can save your scripts,
check them into source safe, but more meaningful errors when they break,
etc.
Adding the IDENTITY property to an existing column is quite a bit of work...
the database has to make a duplicate table, copy all the rows, drop the old
table, and rename the new one, and keep the table off-limits to all other
processes throughout the task. I suggest if you want IDENTITY you decide so
up front, before the table has data in it...
--
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"REB" <russ@.bjorgaard.com> wrote in message
news:#76622R5DHA.564@.TK2MSFTNGP10.phx.gbl...
> The table has 5 columns:
> Drug_AlcoholID int 4
> DriverID int 4 Allow Nulls
> PullDate smalldatetime 4
> Pulltype int 4 Allow Nulls
> Results char 20 Allow Nulls
> I just created the table and there is no data in it.
> I get the error if I try to uncheck allow nulls, change the first field to
> an identity field, delete a column, or try to add a new column.
> I am using Enterprise Manager so I do not see the ALTER TABLE statement.
>|||Thanks for the response. Using Query analyzer to make the table changes
works just fine (I just had to learn the syntax). Enterprise Manager was
installed with my SQL Server 2000 Standard edition on my test server, which
is running windows server 2003. I have SP3a installed.
Is there a seperate download to update the Enterprise Manager? When I look
under help it says my version of Enterprise Manager is 8.0|||I have been getting the same problem, too. Our scenario
Server
Windows Server 200
SQL 2000 SP3
MDAC 2.8 with KB832483 hotfix installe
Client 1
XP Pro SP1
MDAC 2.8 with KB832483 hotfix installe
Client 2
XP Home SP1
MDAC 2.8 (no hotfix installed
(Also tried Enterprise Manager from server console
When trying to add column, delete column, or uncheck allow nulls through Enterprise Manager, I get the same "Invalid Cursor State" message. This happens when performing these operations on any table in any database on the server. However, executing a script through Query Analyzer to perform these functions causes not problems
On the XP Pro machine, I have SQL Server 2000 Developer and DO NOT get any of these problems
Regarding the 2003 server, I have verified the following
Compatibility level of all databases is 8
Connecting to server using SQL or Windows Authentication makes no differenc
Connecting using sa or a variety of db admin users makes no differenc
No databases were upsized from Access (in fact, all DBs and objects were created within the last two months from either EM or QA
My last successful attempt to perform the above operations was Jan 27. The only configuation change to the server was Jan 29 to install the KB832483 hotfix. The next attempt to perform these operations was today and had the problems indicated above
I also
1) Reinstalled MDAC 2.8 on Server, attempted operation from Client 1 and got erro
2) Reinstalled MDAC 2.8 on Client 1, attempted operation from Client 1 and got erro
3) Reinstalled KB832483 hotfix on Client 1, attempted operation from Client 1 and got erro
4) Reinstalled KB832483 hotfix on Server, attempted operation from Client 1 and got erro
This is a development server, so I[m open to trying something radical if needed. Any other suggestions
John|||What Version of SQL Server do you have? 8.00.760(SP3)?
"JSD" <anonymous@.discussions.microsoft.com> wrote in message
news:815C57B0-77A9-4102-A772-D3849A599DD0@.microsoft.com...
> I have been getting the same problem, too. Our scenario:
> Server:
> Windows Server 2003
> SQL 2000 SP3a
> MDAC 2.8 with KB832483 hotfix installed
> Client 1:
> XP Pro SP1a
> MDAC 2.8 with KB832483 hotfix installed
> Client 2:
> XP Home SP1a
> MDAC 2.8 (no hotfix installed)
> (Also tried Enterprise Manager from server console)
>
> When trying to add column, delete column, or uncheck allow nulls through
Enterprise Manager, I get the same "Invalid Cursor State" message. This
happens when performing these operations on any table in any database on the
server. However, executing a script through Query Analyzer to perform these
functions causes not problems.
> On the XP Pro machine, I have SQL Server 2000 Developer and DO NOT get any
of these problems.
> Regarding the 2003 server, I have verified the following:
> Compatibility level of all databases is 80
> Connecting to server using SQL or Windows Authentication makes no
difference
> Connecting using sa or a variety of db admin users makes no difference
> No databases were upsized from Access (in fact, all DBs and objects were
created within the last two months from either EM or QA)
>
> My last successful attempt to perform the above operations was Jan 27.
The only configuation change to the server was Jan 29 to install the
KB832483 hotfix. The next attempt to perform these operations was today and
had the problems indicated above.
> I also:
> 1) Reinstalled MDAC 2.8 on Server, attempted operation from Client 1 and
got error
> 2) Reinstalled MDAC 2.8 on Client 1, attempted operation from Client 1 and
got error
> 3) Reinstalled KB832483 hotfix on Client 1, attempted operation from
Client 1 and got error
> 4) Reinstalled KB832483 hotfix on Server, attempted operation from Client
1 and got error
>
> This is a development server, so I[m open to trying something radical if
needed. Any other suggestions?
> John|||What is the level of SQL Server on the clients (they should be at the same
SP level as the server)? Why have you not updated client 2 with the MDAC
hotfix?
--
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"JSD" <anonymous@.discussions.microsoft.com> wrote in message
news:815C57B0-77A9-4102-A772-D3849A599DD0@.microsoft.com...
> I have been getting the same problem, too. Our scenario:
> Server:
> Windows Server 2003
> SQL 2000 SP3a
> MDAC 2.8 with KB832483 hotfix installed
> Client 1:
> XP Pro SP1a
> MDAC 2.8 with KB832483 hotfix installed
> Client 2:
> XP Home SP1a
> MDAC 2.8 (no hotfix installed)
> (Also tried Enterprise Manager from server console)
>
> When trying to add column, delete column, or uncheck allow nulls through
Enterprise Manager, I get the same "Invalid Cursor State" message. This
happens when performing these operations on any table in any database on the
server. However, executing a script through Query Analyzer to perform these
functions causes not problems.
> On the XP Pro machine, I have SQL Server 2000 Developer and DO NOT get any
of these problems.
> Regarding the 2003 server, I have verified the following:
> Compatibility level of all databases is 80
> Connecting to server using SQL or Windows Authentication makes no
difference
> Connecting using sa or a variety of db admin users makes no difference
> No databases were upsized from Access (in fact, all DBs and objects were
created within the last two months from either EM or QA)
>
> My last successful attempt to perform the above operations was Jan 27.
The only configuation change to the server was Jan 29 to install the
KB832483 hotfix. The next attempt to perform these operations was today and
had the problems indicated above.
> I also:
> 1) Reinstalled MDAC 2.8 on Server, attempted operation from Client 1 and
got error
> 2) Reinstalled MDAC 2.8 on Client 1, attempted operation from Client 1 and
got error
> 3) Reinstalled KB832483 hotfix on Client 1, attempted operation from
Client 1 and got error
> 4) Reinstalled KB832483 hotfix on Server, attempted operation from Client
1 and got error
>
> This is a development server, so I[m open to trying something radical if
needed. Any other suggestions?
> John|||SP3 (8.00.859) is installed on the 2003 server, SP3 (8.00.760) on the SQL Server Developer on Client 1. Both Client 1 and Client 2 have SP3a applied to the client tools, also
Client 2 belongs to a user who does not regularly keep up with MDAC updates; therefore, the hotfix was not installed. I wanted to attempt the operations on Client 2 to help rule out wheter the hotfix may have caused the problem on Client 1
I forgot to mention that we also installed Reporting Services on the 2003 server on the 29th. I e-mailed this question to MS and they didn't think that installation caused this problem. I can't find a cross-reference to determine how the 2003 server got 8.00.859, so I suspect this is due to installing Reporting Services. I'm doubting whether uninstalling Reporting Services would get that server back to 8.00.760
Any ideas?|||>> I can't find a cross-reference to determine how the 2003 server got
8.00.859, so I suspect this is due to installing Reporting Services.
No, this has nothing to do with RS. 859 is the most recent *publicly*
available hotfix that I'm aware of. See
http://support.microsoft.com/?kbid=821334
You can trace specific version #s here:
http://www.aspfaq.com/2160
--
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/|||Thanks for the info. I'll bookmark that page at aspfaq.com for future reference
Any other suggestions on the source of the "invalid cursor state" error?|||No, my post earlier summarized all of the reasons I'm aware of.
How about, instead of using Enterprise Manager to make DDL changes, you use
Query Analyzer?
--
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"JSD" <anonymous@.discussions.microsoft.com> wrote in message
news:78B9B85C-061F-40C4-96D1-77BCEB249BC0@.microsoft.com...
> Thanks for the info. I'll bookmark that page at aspfaq.com for future
reference.
> Any other suggestions on the source of the "invalid cursor state" error?|||To me, Query Analyzer is an acceptable alternative. The use of this server will involve some users who need to learn the fundamentals of SQL Server. While doing DDL changes in Query Analyzer is no problem for me, the EM GUI sure would make their learning easier
I think we'll end up creating a support incident for this. Any other resources you would suggest I try before taking the plunge? I spent quite a while researching this on the Web myself and this newsgroup was the only place I found any help
Aaron, thanks again for all your assistance!|||I spoke with MS support over the last couple of days. They gave me instructions on how to get hotfix 876. It is not available for public release yet, so you'll need to call them and ask for a "grace incident" so they don't charge you for the support
Anyway, they'll send a link and a password to get your own copy of the fix
I installed the hotfix and it cleared up all the problems that I reported
Good luck!|||Thanks JSD, made a note in http://www.aspfaq.com/2515
--
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"JSD" <anonymous@.discussions.microsoft.com> wrote in message
news:72E54CEF-E2F2-40F5-9D96-72BF84A04191@.microsoft.com...
> I spoke with MS support over the last couple of days. They gave me
instructions on how to get hotfix 876. It is not available for public
release yet, so you'll need to call them and ask for a "grace incident" so
they don't charge you for the support.
> Anyway, they'll send a link and a password to get your own copy of the
fix.
> I installed the hotfix and it cleared up all the problems that I reported.
> Good luck!|||I am experiencing the same behavior. Any idea when a hotfix will be
available for this issue? If not, can someone please point me toward the
telephone number I need to use for free information on where to get the
hotfix? It is really aggrevating not being able to modify any tables ...
Thank you,
Michael Carr
"Aaron Bertrand [MVP]" <aaron@.TRASHaspfaq.com> wrote in message
news:OG4cuVp7DHA.2168@.TK2MSFTNGP12.phx.gbl...
> Thanks JSD, made a note in http://www.aspfaq.com/2515|||You can ask for fix 878.
http://support.microsoft.com/?kbid=831950
http://support.microsoft.com/?scid=fh;en-us;Prodoffer41a
--
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"Michael Carr" <mcarr@.umich.edu> wrote in message
news:OtHSTcC$DHA.392@.TK2MSFTNGP12.phx.gbl...
> I am experiencing the same behavior. Any idea when a hotfix will be
> available for this issue? If not, can someone please point me toward the
> telephone number I need to use for free information on where to get the
> hotfix? It is really aggrevating not being able to modify any tables ...
> Thank you,
> Michael Carr
> "Aaron Bertrand [MVP]" <aaron@.TRASHaspfaq.com> wrote in message
> news:OG4cuVp7DHA.2168@.TK2MSFTNGP12.phx.gbl...
> > Thanks JSD, made a note in http://www.aspfaq.com/2515
>|||Hey thanks, that fixed it right up!
Michael Carr
"Aaron Bertrand [MVP]" <aaron@.TRASHaspfaq.com> wrote in message
news:#8zODhH$DHA.2592@.TK2MSFTNGP10.phx.gbl...
> You can ask for fix 878.
> http://support.microsoft.com/?kbid=831950
> http://support.microsoft.com/?scid=fh;en-us;Prodoffer41a

'Invalid cursor state' error when saving table changes

I've created a small DB (one table so far, 0 records as yet). When I try to
change the table structure via Enterprise Manager, I get the following
error:
/*
05 August 2004 16:02:36
User:
Server: HYPERION
Database: TADB
Application: MS SQLEM - Data Tools
*/
'TANumbers' table
- Unable to rename column from 'AdviceNoteID' to 'AdviceNote'.
ODBC error: [Microsoft][ODBC SQL Server Driver]Invalid cursor state
The actual change I was trying to do worked, or at least it appears to have
done.
BOL suggest that this error might be due to the fact that the DB or the Tlog
is full. With no data an no transactions so far, that is unlikely. Plus EM
reports that there is 8.43 Mb free out of 10Mb!
Any ideas anyone?
Thanks
ChrisHi CJM,
From your descriptions, I understood you could not rename your column name
by SQL Server Enterprise Manager. Have I understood you? If there is
anything I misunderstood, please feel free to let me know.
Admittedly, it is a known issue for us when using SQL Server Enterprise
Manager. You will have to use sp_rename in Query Analyzer instead. I am
sorry for the inconvenience you may encounter.
More information of how to use sp_rename could be found in BooksOnline or
MSDN Online
sp_rename
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/tsqlref/ts_
sp_ra-rz_3ns5.asp
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
---
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!|||Hi,
I'm just curious as to why *this* table on *this* DB suffers from this
problem?
I've never had a problem on this server before, so what is it about this DB
that is so different?
Chris
""Mingqing Cheng [MSFT]"" <v-mingqc@.online.microsoft.com> wrote in message
news:v5%23isS4eEHA.1060@.cpmsftngxa06.phx.gbl...
> Hi CJM,
> From your descriptions, I understood you could not rename your column name
> by SQL Server Enterprise Manager. Have I understood you? If there is
> anything I misunderstood, please feel free to let me know.
> Admittedly, it is a known issue for us when using SQL Server Enterprise
> Manager. You will have to use sp_rename in Query Analyzer instead. I am
> sorry for the inconvenience you may encounter.
> More information of how to use sp_rename could be found in BooksOnline or
> MSDN Online
> sp_rename
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/tsqlref/ts_
> sp_ra-rz_3ns5.asp
>|||Hi CJM,
This issue was reported in SP3 and higher version, it was fixed in SQL
Server 8.00.902
It is very possible that changes of columns are made successfully before
you upgrade to SQL Server SP3 .
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
---
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!|||""Mingqing Cheng [MSFT]"" <v-mingqc@.online.microsoft.com> wrote in message
news:k37x%23bDfEHA.3212@.cpmsftngxa06.phx.gbl...
> Hi CJM,
> This issue was reported in SP3 and higher version, it was fixed in SQL
> Server 8.00.902
> It is very possible that changes of columns are made successfully before
> you upgrade to SQL Server SP3 .
>
I'm a bit confused...
How do I get hold of v8.00.902? I thought I was up to date with SP3a...
Chris|||Hi Chris,
Thanks for your prompt updates!
For 8.00.0902 or higher, a supported fix is now available from Microsoft,
but it is only intended to correct the problem that is described in this
article. Apply it only to systems that are experiencing this specific
problem.
To resolve this problem, please contact Microsoft Product Support Services
to obtain the fix. For a complete list of Microsoft Product Support
Services phone numbers and information about support costs, visit the
following Microsoft Web site:
http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS
Asking hotfix will be a FREE case. If PSS staff asking a KB for this issue,
please show me the link and KB No below
FIX: Profiler RPC events truncate parameters that have a text data type to
16 characters
http://support.microsoft.com/?id=839688
You will receive Build 8.00.0927 instead from PSS, based on my testing,
this hotfix could resolved the problm as you described. BTW, I cannot find
excatly Build 8.00.0902 and its relative KB internal:(
If you want PSS Staff be notified of this newsgroup thread, show him the
following information
Tomcat IssueID: 24064701
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
---
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!|||Mingqing,
I've downloaded, installed & tested the patch and everything works fine now.
Thanks
Chris
""Mingqing Cheng [MSFT]"" <v-mingqc@.online.microsoft.com> wrote in message
news:c6mfgnofEHA.1200@.cpmsftngxa06.phx.gbl...
> Hi Chris,
> Thanks for your prompt updates!
> For 8.00.0902 or higher, a supported fix is now available from Microsoft,
> but it is only intended to correct the problem that is described in this
> article. Apply it only to systems that are experiencing this specific
> problem.
>|||Hi Chris,
It's great to hear that you have resolved it! Thanks for your kindest reply
letting me know the status of your issue.
If you encounter any questions or difficulties using SQL Server, please
feel free to post here. We are always here to be of assistance!
Thanks again for using MSDN Managed Newsgroup!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
---
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!

'Invalid cursor state' error when saving table changes

I've created a small DB (one table so far, 0 records as yet). When I try to
change the table structure via Enterprise Manager, I get the following
error:
/*
05 August 2004 16:02:36
User:
Server: HYPERION
Database: TADB
Application: MS SQLEM - Data Tools
*/
'TANumbers' table
- Unable to rename column from 'AdviceNoteID' to 'AdviceNote'.
ODBC error: [Microsoft][ODBC SQL Server Driver]Invalid cursor state
The actual change I was trying to do worked, or at least it appears to have
done.
BOL suggest that this error might be due to the fact that the DB or the Tlog
is full. With no data an no transactions so far, that is unlikely. Plus EM
reports that there is 8.43 Mb free out of 10Mb!
Any ideas anyone?
Thanks
ChrisHi CJM,
From your descriptions, I understood you could not rename your column name
by SQL Server Enterprise Manager. Have I understood you? If there is
anything I misunderstood, please feel free to let me know.
Admittedly, it is a known issue for us when using SQL Server Enterprise
Manager. You will have to use sp_rename in Query Analyzer instead. I am
sorry for the inconvenience you may encounter.
More information of how to use sp_rename could be found in BooksOnline or
MSDN Online
sp_rename
http://msdn.microsoft.com/library/d...-us/tsqlref/ts_
sp_ra-rz_3ns5.asp
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
---
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!|||Hi,
I'm just curious as to why *this* table on *this* DB suffers from this
problem?
I've never had a problem on this server before, so what is it about this DB
that is so different?
Chris
""Mingqing Cheng [MSFT]"" <v-mingqc@.online.microsoft.com> wrote in messa
ge
news:v5%23isS4eEHA.1060@.cpmsftngxa06.phx.gbl...
> Hi CJM,
> From your descriptions, I understood you could not rename your column name
> by SQL Server Enterprise Manager. Have I understood you? If there is
> anything I misunderstood, please feel free to let me know.
> Admittedly, it is a known issue for us when using SQL Server Enterprise
> Manager. You will have to use sp_rename in Query Analyzer instead. I am
> sorry for the inconvenience you may encounter.
> More information of how to use sp_rename could be found in BooksOnline or
> MSDN Online
> sp_rename
>
http://msdn.microsoft.com/library/d...-us/tsqlref/ts_
> sp_ra-rz_3ns5.asp
>|||Hi CJM,
This issue was reported in SP3 and higher version, it was fixed in SQL
Server 8.00.902
It is very possible that changes of columns are made successfully before
you upgrade to SQL Server SP3 .
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
---
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!|||""Mingqing Cheng [MSFT]"" <v-mingqc@.online.microsoft.com> wrote in messa
ge
news:k37x%23bDfEHA.3212@.cpmsftngxa06.phx.gbl...
> Hi CJM,
> This issue was reported in SP3 and higher version, it was fixed in SQL
> Server 8.00.902
> It is very possible that changes of columns are made successfully before
> you upgrade to SQL Server SP3 .
>
I'm a bit confused...
How do I get hold of v8.00.902? I thought I was up to date with SP3a...
Chris|||Hi Chris,
Thanks for your prompt updates!
For 8.00.0902 or higher, a supported fix is now available from Microsoft,
but it is only intended to correct the problem that is described in this
article. Apply it only to systems that are experiencing this specific
problem.
To resolve this problem, please contact Microsoft Product Support Services
to obtain the fix. For a complete list of Microsoft Product Support
Services phone numbers and information about support costs, visit the
following Microsoft Web site:
http://support.microsoft.com/defaul...;EN-US;CNTACTMS
Asking hotfix will be a FREE case. If PSS staff asking a KB for this issue,
please show me the link and KB No below
FIX: Profiler RPC events truncate parameters that have a text data type to
16 characters
http://support.microsoft.com/?id=839688
You will receive Build 8.00.0927 instead from PSS, based on my testing,
this hotfix could resolved the problm as you described. BTW, I cannot find
excatly Build 8.00.0902 and its relative KB internal

If you want PSS Staff be notified of this newsgroup thread, show him the
following information
Tomcat IssueID: 24064701
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
---
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!|||Mingqing,
I've downloaded, installed & tested the patch and everything works fine now.
Thanks
Chris
""Mingqing Cheng [MSFT]"" <v-mingqc@.online.microsoft.com> wrote in messa
ge
news:c6mfgnofEHA.1200@.cpmsftngxa06.phx.gbl...
> Hi Chris,
> Thanks for your prompt updates!
> For 8.00.0902 or higher, a supported fix is now available from Microsoft,
> but it is only intended to correct the problem that is described in this
> article. Apply it only to systems that are experiencing this specific
> problem.
>|||Hi Chris,
It's great to hear that you have resolved it! Thanks for your kindest reply
letting me know the status of your issue.
If you encounter any questions or difficulties using SQL Server, please
feel free to post here. We are always here to be of assistance!
Thanks again for using MSDN Managed Newsgroup!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
---
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!

'Invalid cursor state' error when saving table changes

I've created a small DB (one table so far, 0 records as yet). When I try to
change the table structure via Enterprise Manager, I get the following
error:
/*
05 August 2004 16:02:36
User:
Server: HYPERION
Database: TADB
Application: MS SQLEM - Data Tools
*/
'TANumbers' table
- Unable to rename column from 'AdviceNoteID' to 'AdviceNote'.
ODBC error: [Microsoft][ODBC SQL Server Driver]Invalid cursor state
The actual change I was trying to do worked, or at least it appears to have
done.
BOL suggest that this error might be due to the fact that the DB or the Tlog
is full. With no data an no transactions so far, that is unlikely. Plus EM
reports that there is 8.43 Mb free out of 10Mb!
Any ideas anyone?
Thanks
Chris
Hi CJM,
From your descriptions, I understood you could not rename your column name
by SQL Server Enterprise Manager. Have I understood you? If there is
anything I misunderstood, please feel free to let me know.
Admittedly, it is a known issue for us when using SQL Server Enterprise
Manager. You will have to use sp_rename in Query Analyzer instead. I am
sorry for the inconvenience you may encounter.
More information of how to use sp_rename could be found in BooksOnline or
MSDN Online
sp_rename
http://msdn.microsoft.com/library/de...us/tsqlref/ts_
sp_ra-rz_3ns5.asp
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!
|||Hi,
I'm just curious as to why *this* table on *this* DB suffers from this
problem?
I've never had a problem on this server before, so what is it about this DB
that is so different?
Chris
""Mingqing Cheng [MSFT]"" <v-mingqc@.online.microsoft.com> wrote in message
news:v5%23isS4eEHA.1060@.cpmsftngxa06.phx.gbl...
> Hi CJM,
> From your descriptions, I understood you could not rename your column name
> by SQL Server Enterprise Manager. Have I understood you? If there is
> anything I misunderstood, please feel free to let me know.
> Admittedly, it is a known issue for us when using SQL Server Enterprise
> Manager. You will have to use sp_rename in Query Analyzer instead. I am
> sorry for the inconvenience you may encounter.
> More information of how to use sp_rename could be found in BooksOnline or
> MSDN Online
> sp_rename
>
http://msdn.microsoft.com/library/de...us/tsqlref/ts_
> sp_ra-rz_3ns5.asp
>
|||Hi CJM,
This issue was reported in SP3 and higher version, it was fixed in SQL
Server 8.00.902
It is very possible that changes of columns are made successfully before
you upgrade to SQL Server SP3 .
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!
|||""Mingqing Cheng [MSFT]"" <v-mingqc@.online.microsoft.com> wrote in message
news:k37x%23bDfEHA.3212@.cpmsftngxa06.phx.gbl...
> Hi CJM,
> This issue was reported in SP3 and higher version, it was fixed in SQL
> Server 8.00.902
> It is very possible that changes of columns are made successfully before
> you upgrade to SQL Server SP3 .
>
I'm a bit confused...
How do I get hold of v8.00.902? I thought I was up to date with SP3a...
Chris
|||Hi Chris,
Thanks for your prompt updates!
For 8.00.0902 or higher, a supported fix is now available from Microsoft,
but it is only intended to correct the problem that is described in this
article. Apply it only to systems that are experiencing this specific
problem.
To resolve this problem, please contact Microsoft Product Support Services
to obtain the fix. For a complete list of Microsoft Product Support
Services phone numbers and information about support costs, visit the
following Microsoft Web site:
http://support.microsoft.com/default...EN-US;CNTACTMS
Asking hotfix will be a FREE case. If PSS staff asking a KB for this issue,
please show me the link and KB No below
FIX: Profiler RPC events truncate parameters that have a text data type to
16 characters
http://support.microsoft.com/?id=839688
You will receive Build 8.00.0927 instead from PSS, based on my testing,
this hotfix could resolved the problm as you described. BTW, I cannot find
excatly Build 8.00.0902 and its relative KB internal

If you want PSS Staff be notified of this newsgroup thread, show him the
following information
Tomcat IssueID: 24064701
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!
|||Mingqing,
I've downloaded, installed & tested the patch and everything works fine now.
Thanks
Chris
""Mingqing Cheng [MSFT]"" <v-mingqc@.online.microsoft.com> wrote in message
news:c6mfgnofEHA.1200@.cpmsftngxa06.phx.gbl...
> Hi Chris,
> Thanks for your prompt updates!
> For 8.00.0902 or higher, a supported fix is now available from Microsoft,
> but it is only intended to correct the problem that is described in this
> article. Apply it only to systems that are experiencing this specific
> problem.
>
|||Hi Chris,
It's great to hear that you have resolved it! Thanks for your kindest reply
letting me know the status of your issue.
If you encounter any questions or difficulties using SQL Server, please
feel free to post here. We are always here to be of assistance!
Thanks again for using MSDN Managed Newsgroup!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!

Invalid Cursor State Error

I know other people have posted stuff like this before, but I am still
to see a definitive answer. I have created a table in Enterprise
manager called tblUsers. I later added a column in EM and saved the
change. I then noticed I had misnamed the column, so I renamed and
when I tried to save the change I got the following message:-

'tblUsers' table
- Unable to rename column from 'fldepCode' to 'fldRepCode'.
ODBC error: [Microsoft][ODBC SQL Server Driver]Invalid cursor state

This is now regularly happening to me, and I am tired of having to
recreate tables.

I am using SQL Server 2000 with all the latest service packs and
patches. Has anyone any idea what is causing this and how I can cure
it or avoid it?"Sam Evans" <sam.evans@.fuchs-oil.com> wrote in message
news:3fb4df1d.0401070435.5eba4784@.posting.google.c om...
> I know other people have posted stuff like this before, but I am still
> to see a definitive answer. I have created a table in Enterprise
> manager called tblUsers. I later added a column in EM and saved the
> change. I then noticed I had misnamed the column, so I renamed and
> when I tried to save the change I got the following message:-
> 'tblUsers' table
> - Unable to rename column from 'fldepCode' to 'fldRepCode'.
> ODBC error: [Microsoft][ODBC SQL Server Driver]Invalid cursor state
>
> This is now regularly happening to me, and I am tired of having to
> recreate tables.
> I am using SQL Server 2000 with all the latest service packs and
> patches. Has anyone any idea what is causing this and how I can cure
> it or avoid it?

Enterprise Manager's visual design features have a bit of a history of
similar issues; the best solution is probably to use Query Analyzer:

exec sp_rename 'SomeTable.fldepCode', 'fldRepCode', 'column'

Personally, I would prefer to use QA for this sort of task, as it allows for
more control and precision.

Simon|||Many thanks for the quick reply. I know I should use the best method,
not the simplest, but i resent having to remember any syntax, however
simple, when I already have a tool that's supposed to do the job! The
best answer would be for me to write a little vb.net app that will let
me choose a stored procedure, prompt me for parameters and run the SP.
Guess what, I already have one! A quick hack beckons!

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

Invalid cursor state @ Distribution Agent

Hi! When i create a Transactional Replication between two SQL Server 2000 (with no additional Service Pack or Update) with the Enterprise Manager, i get this error (also when i restart the agent):
Invalid cursor state
(Source: ODBC Driver Manager [ODBC]; Error number: 24000)
I think it the MDAC is not the problem, because i never updated the SQL Server 2000 and there the error is from the ODBC SQL Driver. But here it′s from the Driver Manager.
Please help me!! I really despair!
Thanks
Does this apply to your case:
http://support.microsoft.com/default.aspx?kbid=831997?
HTH,
Paul Ibison

Invalid Cursor State - Column Rename/Move

Hi,
I am trying to rename columns or move column in a simple table that has data
in it.
Each time I am getting an "Invalid Cursor State" error message.
I am doing that all the time in Access 97/2000/2002/2003. Why is it not
working in SQL Server 2000?
Any idea?
Thanks
vbdev
OK. Forget it. Found the issue:
The Hotfix that you have to install to get the report services on your
server is causing this odd behavior.
Solution is to install Hotfix 878...
vbdev

Invalid Cursor State - Column Rename/Move

Hi,
I am trying to rename columns or move column in a simple table that has data
in it.
Each time I am getting an "Invalid Cursor State" error message.
I am doing that all the time in Access 97/2000/2002/2003. Why is it not
working in SQL Server 2000?
Any idea?
Thanks
vbdevOK. Forget it. Found the issue:
The Hotfix that you have to install to get the report services on your
server is causing this odd behavior.
Solution is to install Hotfix 878...
vbdev

Invalid cursor state

Hi! I want to build up a transactional replication between 2 SQL Server 2000. The Publisher is also the distributor.
I used all the wizards and after i made the subscriber, I get an error at the distribution agent:
Invalid cursor state
(Source: ODBC Driver Manager (ODBC); Error number: 24000)
What should i do now?
Please help, thank you!!
Is this error reproducible? For instance if you restart your Distribution
Agent do you get it again?
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"oselinge" <oselinge@.discussions.microsoft.com> wrote in message
news:98B5BAD5-2551-4279-9B74-40A6481FF3E1@.microsoft.com...
> Hi! I want to build up a transactional replication between 2 SQL Server
2000. The Publisher is also the distributor.
> I used all the wizards and after i made the subscriber, I get an error at
the distribution agent:
> Invalid cursor state
> (Source: ODBC Driver Manager (ODBC); Error number: 24000)
> What should i do now?
> Please help, thank you!!
|||Yes, I get it again! I often tried to restart, but everytime i got this error.
"Hilary Cotter" wrote:

> Is this error reproducible? For instance if you restart your Distribution
> Agent do you get it again?
> --
> Hilary Cotter
> Looking for a book on SQL Server replication?
> http://www.nwsu.com/0974973602.html
>
> "oselinge" <oselinge@.discussions.microsoft.com> wrote in message
> news:98B5BAD5-2551-4279-9B74-40A6481FF3E1@.microsoft.com...
> 2000. The Publisher is also the distributor.
> the distribution agent:
>
>
|||Oselinge,
usually this is an MDAC/ODBC error - hopefully this
article applies to your case:
http://support.microsoft.com/default.aspx?kbid=831997
HTH,
Paul Ibison
|||I think this is not the reason for this error.
Any other ideas?
"Paul Ibison" wrote:

> Oselinge,
> usually this is an MDAC/ODBC error - hopefully this
> article applies to your case:
> http://support.microsoft.com/default.aspx?kbid=831997
> HTH,
> Paul Ibison
>

Invalid cursor state

Invalid Cursor State

After I create a table, if I attempt to modify or insert a column using the
wizard in EM, I get the following error:
-Unable to modify table.
ODBC error: [Microsoft][ODBC SQL Server Driver]Invalid Cursor State
I have SP3a installed, Analysis Services and SQL Reporting. Any suggestions?
Thanks.
DanSounds like this KB article.
FIX: An invalid cursor state occurs after you apply Hotfix 8.00.0859 or
later in SQL Server 2000
http://support.microsoft.com/kb/831997
However, this MS PSS only fix looks like BUILD 876. BUILD 878 is public and
located here:
http://support.microsoft.com/?kbid=838166
Since these are cumulative, it would include the fix for the other.
Sincerely,
Anthony Thomas
"DLS" <DLS@.discussions.microsoft.com> wrote in message
news:2BB9D7A0-6BCE-426F-9375-7D205280F4DA@.microsoft.com...
After I create a table, if I attempt to modify or insert a column using the
wizard in EM, I get the following error:
-Unable to modify table.
ODBC error: [Microsoft][ODBC SQL Server Driver]Invalid Cursor State
I have SP3a installed, Analysis Services and SQL Reporting. Any suggestions?
Thanks.
Dan

Invalid Cursor State

All,
SQL 2000 sp3 hotfix 871, Server 2000 sp4
Any hotfix greater than 859 will have this problem. The fix is to get hotfix
876, kb article 831997 is the one you want to tell them to reference. Its f
ree.
Gary Abbott Super DBA, lolThat KB article isn't public, FYI. 878 is (see http://www.aspfaq.com/2515).
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"Gary Abbott" <anonymous@.discussions.microsoft.com> wrote in message
news:74016FAB-0BBF-4FB8-88C0-4CA6A448E68B@.microsoft.com...
> All,
> SQL 2000 sp3 hotfix 871, Server 2000 sp4
> Any hotfix greater than 859 will have this problem. The fix is to get
hotfix 876, kb article 831997 is the one you want to tell them to reference.
Its free.
> Gary Abbott Super DBA, lol|||They wouldn't give me 878, I did ask. Reading one of your earlier posts.|||Did they give you a reason? How did you come across 876?
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"Gary Abbott" <anonymous@.discussions.microsoft.com> wrote in message
news:BB74A25F-6B90-44CA-9177-F67574DFC2EF@.microsoft.com...
> They wouldn't give me 878, I did ask. Reading one of your earlier posts.

Invalid cursor state

Running a stored procedure returns
Invalid cursor state
Why does that occur ?Check if this KB article applies: http://support.microsoft.com/kb/831997
Linchi
"Hassan" wrote:

> Running a stored procedure returns
> Invalid cursor state
> Why does that occur ?
>
>|||Its SQL 2005 SP2 ;)
"Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message
news:F1843F26-586A-4C5E-8AD9-42497EB698E3@.microsoft.com...[vbcol=seagreen]
> Check if this KB article applies: http://support.microsoft.com/kb/831997
> Linchi
> "Hassan" wrote:
>

Invalid cursor state

Running a stored procedure returns
Invalid cursor state
Why does that occur ?Check if this KB article applies: http://support.microsoft.com/kb/831997
Linchi
"Hassan" wrote:
> Running a stored procedure returns
> Invalid cursor state
> Why does that occur ?
>
>|||Its SQL 2005 SP2 ;)
"Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message
news:F1843F26-586A-4C5E-8AD9-42497EB698E3@.microsoft.com...
> Check if this KB article applies: http://support.microsoft.com/kb/831997
> Linchi
> "Hassan" wrote:
>> Running a stored procedure returns
>> Invalid cursor state
>> Why does that occur ?
>>

Invalid cursor state

Problem with dsigning tables. when changing datatype, size
etc'
i get message:
ODBC error: [Microsoft][ODBC SQL Server Driver]Invalid
cursor state
microsoft is reffering to: http://support.microsoft.com/?
kbid=831997
but there is nothing there that can fix the problem
what can i do to fix it?
Thankseran,shalom
Check out if the log file is full, what is recovery model of the log file?
<eranv@.gat.co.il> wrote in message
news:369601c48812$bb6d5530$a301280a@.phx.gbl...
> Problem with dsigning tables. when changing datatype, size
> etc'
> i get message:
> ODBC error: [Microsoft][ODBC SQL Server Driver]Invalid
> cursor state
> microsoft is reffering to: http://support.microsoft.com/?
> kbid=831997
> but there is nothing there that can fix the problem
> what can i do to fix it?
> Thanks|||Uri hi and thanks for responding,
The log file is not full and the mode is set to "simple"
this error occurs on all tables and in every database. I
think it has something to do with hotfix or patch that we
installed after sp3a
we are working around that problem by recreating the
tables everytime a change is needed. you can imagin how
hard it is to work like that.
thanks again
Eran
.
>--Original Message--
>eran,shalom
>Check out if the log file is full, what is recovery model
of the log file?
>
><eranv@.gat.co.il> wrote in message
>news:369601c48812$bb6d5530$a301280a@.phx.gbl...
>> Problem with dsigning tables. when changing datatype,
size
>> etc'
>> i get message:
>> ODBC error: [Microsoft][ODBC SQL Server Driver]Invalid
>> cursor state
>> microsoft is reffering to:
http://support.microsoft.com/?
>> kbid=831997
>> but there is nothing there that can fix the problem
>> what can i do to fix it?
>> Thanks
>
>.
>|||Eran
I see, have you looked at http://support.microsoft.com/?kbid=821334
Do you have the same MDAC on the client and server?
<anonymous@.discussions.microsoft.com> wrote in message
news:acf101c48834$30264d70$a601280a@.phx.gbl...
> Uri hi and thanks for responding,
> The log file is not full and the mode is set to "simple"
> this error occurs on all tables and in every database. I
> think it has something to do with hotfix or patch that we
> installed after sp3a
> we are working around that problem by recreating the
> tables everytime a change is needed. you can imagin how
> hard it is to work like that.
> thanks again
> Eran
> .
>
> >--Original Message--
> >eran,shalom
> >Check out if the log file is full, what is recovery model
> of the log file?
> >
> >
> ><eranv@.gat.co.il> wrote in message
> >news:369601c48812$bb6d5530$a301280a@.phx.gbl...
> >> Problem with dsigning tables. when changing datatype,
> size
> >> etc'
> >> i get message:
> >> ODBC error: [Microsoft][ODBC SQL Server Driver]Invalid
> >> cursor state
> >>
> >> microsoft is reffering to:
> http://support.microsoft.com/?
> >> kbid=831997
> >> but there is nothing there that can fix the problem
> >> what can i do to fix it?
> >>
> >> Thanks
> >
> >
> >.
> >|||yes the MDAC versions are the same. the error message
occurs also when working directly on the server.
a general search led me to http://support.microsoft.com/?
kbid=831997
and i think that the link discribes an issue somewhat
relevant, however i could not find a workaround or hotfix
to correct the problem.
>--Original Message--
>Eran
>I see, have you looked at http://support.microsoft.com/?
kbid=821334
>Do you have the same MDAC on the client and server?
>
><anonymous@.discussions.microsoft.com> wrote in message
>news:acf101c48834$30264d70$a601280a@.phx.gbl...
>> Uri hi and thanks for responding,
>> The log file is not full and the mode is set to "simple"
>> this error occurs on all tables and in every database. I
>> think it has something to do with hotfix or patch that
we
>> installed after sp3a
>> we are working around that problem by recreating the
>> tables everytime a change is needed. you can imagin how
>> hard it is to work like that.
>> thanks again
>> Eran
>> .
>>
>> >--Original Message--
>> >eran,shalom
>> >Check out if the log file is full, what is recovery
model
>> of the log file?
>> >
>> >
>> ><eranv@.gat.co.il> wrote in message
>> >news:369601c48812$bb6d5530$a301280a@.phx.gbl...
>> >> Problem with dsigning tables. when changing datatype,
>> size
>> >> etc'
>> >> i get message:
>> >> ODBC error: [Microsoft][ODBC SQL Server Driver]
Invalid
>> >> cursor state
>> >>
>> >> microsoft is reffering to:
>> http://support.microsoft.com/?
>> >> kbid=831997
>> >> but there is nothing there that can fix the problem
>> >> what can i do to fix it?
>> >>
>> >> Thanks
>> >
>> >
>> >.
>> >
>
>.
>|||Eran
You may want to delete the hotfix and re-install sp3.
<anonymous@.discussions.microsoft.com> wrote in message
news:ad1f01c4883a$cd180280$a601280a@.phx.gbl...
> yes the MDAC versions are the same. the error message
> occurs also when working directly on the server.
> a general search led me to http://support.microsoft.com/?
> kbid=831997
> and i think that the link discribes an issue somewhat
> relevant, however i could not find a workaround or hotfix
> to correct the problem.
> >--Original Message--
> >Eran
> >I see, have you looked at http://support.microsoft.com/?
> kbid=821334
> >Do you have the same MDAC on the client and server?
> >
> >
> ><anonymous@.discussions.microsoft.com> wrote in message
> >news:acf101c48834$30264d70$a601280a@.phx.gbl...
> >> Uri hi and thanks for responding,
> >> The log file is not full and the mode is set to "simple"
> >> this error occurs on all tables and in every database. I
> >> think it has something to do with hotfix or patch that
> we
> >> installed after sp3a
> >> we are working around that problem by recreating the
> >> tables everytime a change is needed. you can imagin how
> >> hard it is to work like that.
> >> thanks again
> >> Eran
> >> .
> >>
> >>
> >> >--Original Message--
> >> >eran,shalom
> >> >Check out if the log file is full, what is recovery
> model
> >> of the log file?
> >> >
> >> >
> >> ><eranv@.gat.co.il> wrote in message
> >> >news:369601c48812$bb6d5530$a301280a@.phx.gbl...
> >> >> Problem with dsigning tables. when changing datatype,
> >> size
> >> >> etc'
> >> >> i get message:
> >> >> ODBC error: [Microsoft][ODBC SQL Server Driver]
> Invalid
> >> >> cursor state
> >> >>
> >> >> microsoft is reffering to:
> >> http://support.microsoft.com/?
> >> >> kbid=831997
> >> >> but there is nothing there that can fix the problem
> >> >> what can i do to fix it?
> >> >>
> >> >> Thanks
> >> >
> >> >
> >> >.
> >> >
> >
> >
> >.
> >

Invalid cursor state

[Microsoft][ODBC SQL Server Driver]Invalid cursor state
Having a few of these reported in our application logs as it calls a sql
server stored proc stemming from ODBC that references SQLFetch
The stored proc does not use a cursorPlease exhibit some patience and don't post the same question multiple
times.
What on earth does your stored procedure do? Should we guess? Do you have
any problems when you call the stored procedure directly (without using the
app)? How about if you use a different connection method (e.g. OLEDB
instead of ODBC)?
"Hassan" <hassan@.test.com> wrote in message
news:OUHYKlXUIHA.5160@.TK2MSFTNGP05.phx.gbl...
> [Microsoft][ODBC SQL Server Driver]Invalid cursor state
> Having a few of these reported in our application logs as it calls a sql
> server stored proc stemming from ODBC that references SQLFetch
> The stored proc does not use a cursor|||Hi Hassan
My guess is that it is a DTC issue, but as Aaron points out all three of the
posts you have made since April 2007 for this give very little information.
John
"Hassan" wrote:
> [Microsoft][ODBC SQL Server Driver]Invalid cursor state
> Having a few of these reported in our application logs as it calls a sql
> server stored proc stemming from ODBC that references SQLFetch
> The stored proc does not use a cursor
>

Invalid Cursor State

After I create a table, if I attempt to modify or insert a column using the
wizard in EM, I get the following error:
-Unable to modify table.
ODBC error: [Microsoft][ODBC SQL Server Driver]Invalid Cursor State
I have SP3a installed, Analysis Services and SQL Reporting. Any suggestions?
Thanks.
DanSounds like this KB article.
FIX: An invalid cursor state occurs after you apply Hotfix 8.00.0859 or
later in SQL Server 2000
http://support.microsoft.com/kb/831997
However, this MS PSS only fix looks like BUILD 876. BUILD 878 is public and
located here:
http://support.microsoft.com/?kbid=838166
Since these are cumulative, it would include the fix for the other.
Sincerely,
Anthony Thomas
--
"DLS" <DLS@.discussions.microsoft.com> wrote in message
news:2BB9D7A0-6BCE-426F-9375-7D205280F4DA@.microsoft.com...
After I create a table, if I attempt to modify or insert a column using the
wizard in EM, I get the following error:
-Unable to modify table.
ODBC error: [Microsoft][ODBC SQL Server Driver]Invalid Cursor State
I have SP3a installed, Analysis Services and SQL Reporting. Any suggestions?
Thanks.
Dan

Invalid Cursor State

Hi,

I have a stored procedure that calls 2 other stored procedures and combines the results into a temporary table. The results of the temporary table is then returned from the stored procedure.

When I execute the stored procedure in Query Analyzer, I get the exact data I want in the correct format - no errors.

When I execute that stored procedure in Omnivex SQL Link 3, I get an "Invalid Cursor State" error.

I did some digging on that error, and found that it could be related to print statements within the stored procedures. I removed all print statements from all 3 stored procedures and the error is still occuring.

Any suggestions?I suggest you post the code for the stored procedure and somebody will help you rewrite it without using a cursor. 99 times out of 100 they aren't necessary and only impede performance.|||Dude...I don't believe they are using a Cursor in the code...

What is Omnivex SQL Link 3 anyway?

EDIT: AHA

http://www.omnivex.com/index.asp

Is there code on the SQL Link side? Or does it act like ODBC...my Guess it's middleware and that's where you're problem resdies|||Good point.

I wonder if the stored proc might be returning spurious information before the final recordset. Maybe a simple SET NOCOUNT ON would solve the problem.|||That is brilliant! The SET NOCOUNT ON/OFF did the trick! Thank you so much!!!!|||"An expert is a person who has made all possible mistakes in a very narrow field." - Niels Bohr

Wednesday, March 21, 2012

Invalid locale ID

Monday, March 19, 2012

Invalid cursor state?

Invalid cursor state?

'Invalid cursor state' error when saving table changes

'Invalid cursor state' error when saving table changes

'Invalid cursor state' error when saving table changes

Invalid Cursor State Error

Invalid cursor state @ Distribution Agent

Invalid Cursor State - Column Rename/Move

Invalid Cursor State - Column Rename/Move

Invalid cursor state

Invalid cursor state

Invalid Cursor State

Invalid Cursor State

Invalid cursor state

Invalid cursor state

Invalid cursor state

Invalid cursor state

Invalid Cursor State

Invalid Cursor State

Internet integration

Blog Archive

About Me