Monday, March 12, 2012

invalid cursor state

I am unable to save modifications to changes in a database. I get the following error:
- Unable to preserve security settings for user 'RIMSUser'.
ODBC error: [Microsoft][ODBC SQL Server Driver]Invalid cursor state
Any suggestions?
Hi Dslaby,
From your description, I understand that you would like to make your
modifications successfully without error message "Invalid cursor state".
Have I fully understood you? If there is anything I misunderstood, please
feel free to let me know.
Before we go any further, I would like to collect more information from you:
1. Could you let me know what the front-end program that you ran the your
query is? Access or others?
2. Which SQL Statement you run? Did you try other SQL statements? Such as
Select, Insert into, Update, etc.. Will they get the same results?
3. Do you have the correct security authority to do modifications in SQL
Server? Could you login SQL Server as 'RIMSUser' in Query Analyzer and make
modifications for database?
4. Have you updated to the latest service pack for SQL Server and ODBC
Driver?
Moreover, you could get the latest updates from
Microsoft Data Access Components (MDAC) 2.8
http://www.microsoft.com/downloads/d...fe3-c795-4b7d-
b037-185d0506396c&DisplayLang=en
Microsoft SQL Server 2000 Service Pack 3a
http://www.microsoft.com/downloads/d...52c-0488-4e46-
afbf-acace5369fa3&DisplayLang=en
Please apply my questions and suggestions above and let me know the
results, and feel free to post it in the group.
Sincerely yours,
Michael Cheng
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, many thanks.
|||1. I'm using Enterprise Manager
2. I've tried to modify the database fields in Enterprise Manager
3. I'm an administrator and logged on in using integrated security
4. I've kept the service packs up to date in SQL
Thanks.
|||Hi Dslaby,
I don't know what your means about 'database fields', Does it mean
'datatype of the coloumn'?
In this case, it is an known issue especially when you are trying to change
it from FLOAT to INTEGER. We have an hotfix, however, This fix is not
publicly available through the Microsoft website as it has not gone through
full Microsoft regression testing. If you would like confirmation that
this fix is designed to address your specific problem, or if you would like
to confirm whether there are any special compatibility or installation
issues associated with this fix, you are encouraged to speak to a Support
Professional in Product Support Services, by contacting us at
1-(800)936-5800 or by choosing one of the options listed at
http://support.microsoft.com/default...d=sz;en-us;top
As a workaround, you could make your change by Query Analyzer
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,
Michael Cheng
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, many thanks.
|||I was trying to change the length of a varchar from 250 to 1000. Now I get this message:
- Unable to create index 'PK_tblJobBoard'.
ODBC error: [Microsoft][ODBC SQL Server Driver]Invalid cursor state
I am unable to do any modifications to any of the database objects in Enterprise Manager. I'll try reinstalling SQL 2000.
|||Hi Dslaby,
ThereYou could try to do modification by Query Analyzer and you should
using ALTER statement like this if you want to alter column attribute
ALTER TABLE tableName ALTER COLUMN columnName columnType
(tableName, columnName and columnType should be changed according to your
own database settings)
More information about ALTER statement could be found at BooksOnline title
"ALTER TABLE" or MSDN Online:
ALTER TABLE
http://msdn.microsoft.com/library/de...us/tsqlref/ts_
aa-az_3ied.asp
After you apply SQL Server 2000 Service Pack 3 (SP3) hotfix build versions
between 8.00.0859 and 8.00.0875, you will encounter this kind of message
when using SQL Enterprise Manager to alter table column. Based on my
testing, a SQL Server without service pack (build version 8.00.0194) and
latest hotfix (builder version 8.00.0927) will not encounter this kind of
issue.
(You could use select @.@.version to find your SQL Server Versions by using
Query Analyzer)
In Summary, I recommand you using Query Analyzer to modify table column or
contact Product Support Services for latest update.
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,
Michael Cheng
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, many thanks.
|||PS. Does the technet CD subscription have the latest version?
Thanks.
|||I have build .859 from SP3a installed. How do I know the latest build versions on PSS?
Also, I installed SQL Reporting. Did this install require a re-install of SP3a?
Thanks.
|||Hi Dslaby,
System Requirements for Reporting Services could be found at:
http://www.microsoft.com/sql/reporti...fo/sysreqs.asp
from which you could see that you must update to Service Pace 3a or higher
to install SQL Server Reporting Services
However, The hotfix I have mentioned is not publicly available through the
Microsoft website as it has not gone through full Microsoft regression
testing. If you would like confirmation that this fix is designed to
address your specific problem, or if you would like to confirm whether
there are any special compatibility or installation issues associated with
this fix, you are encouraged to speak to a Support Professional in Product
Support Services, by contacting us at 1-(800)936-5800 or by choosing one of
the options listed at
http://support.microsoft.com/default...d=sz;en-us;top
Based on my test, build 927 has eliminate this kind of issue.
Bottom line - have a good backup strategy.
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,
Michael Cheng
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, many thanks.
|||I called the support number and they are unable to send me the patch without an article number. Could you email the patch? Thanks.

No comments:

Post a Comment