Post reply

Invalid cursor state

  • March 11, 2004 at 2:23 am

    #76139

    After creation of a table RS_REGION, I want to change some properties of this (still empty) table.

    I want to change a column property to not allow null values or

    I want to define a primary key on a column

    I get the following error

    'RS_REGION' table

    - Unable to modify table. 

    ODBC error: [Microsoft][ODBC SQL Server Driver]Invalid cursor state

    ??

  • March 11, 2004 at 2:27 am

    #498223

    What front-end do you use?

    --
    Frank Kalis
    Microsoft SQL Server MVP
    Webmaster: http://www.insidesql.org/blogs
    My blog: http://www.insidesql.org/blogs/frankkalis/[/url]

  • March 11, 2004 at 2:30 am

    #498224

    I use the SQL Server Enterprise Manager

  • March 11, 2004 at 2:38 am

    #498225

    Can you script your table and try via QA?

    --
    Frank Kalis
    Microsoft SQL Server MVP
    Webmaster: http://www.insidesql.org/blogs
    My blog: http://www.insidesql.org/blogs/frankkalis/[/url]

  • March 11, 2004 at 3:43 am

    #498230

    When i try it via a script in QA. It works

    Strange thing is that i can do the same changes in the Enterprise Manager in the testenvironment on my local machine

    A collegue of my who is working on the s

     

  • March 11, 2004 at 8:55 am

    #498312

    I've found the reason for the problem.

    After installation of Reporting Services on the Server, you can het this issue while using the Enterprise Manager.

    2 Solutions

    1. Use QA

    2. Install Hotfix 878 (contact MS Support)

    more info see

    http://www.aspfaq.com/show.asp?id=2515

  • March 11, 2004 at 12:53 pm

    #498358

    Thanks for posting that info!

    --
    Frank Kalis
    Microsoft SQL Server MVP
    Webmaster: http://www.insidesql.org/blogs
    My blog: http://www.insidesql.org/blogs/frankkalis/[/url]

  • May 27, 2004 at 9:51 am

    #508051

    If anyone is still reading this thread, here is a way around this issue:

    I spent over 3 hours on the phone with Microsoft yesterday about this issue. During the course of loading SQL, SP3a, and RS at least 7 times on two different servers, I discovered a workaround.

    If you follow the normal installation, RS will want to start the service with a local system account, which it calls a "service account". If you choose this it will tell you that you have to install the hotfix 821334. If you install hotfix 821334, it will SCREW UP ENTERPRISE MANAGER.

    Instead, use a domain account for both the RS service to start up and a domain account to use for authentication (really, only the RS service startup is critical) and you will NOT BE REQUIRED TO INSTALL THE HOTFIX 821334 which screws up Enterprise Manager. The install will proceed as normal and everything will work as expected.

    To me, this is a much better solution than getting hotfix 878, because we all know that hotfixes can break other things, too.

    Unfortunately, once you have installed hotfix 821334 it cannot be uninstalled. So, this only works if you are reinstalling SQL server and the whole 9 yards. However, you can do this and still use Report Services using this method.

    Great thing was, since I was the one who discovered the workaround while working with the DB support rep, MS didn't charge me for the call.

    Good luck...Alan

     

  • May 27, 2004 at 2:28 pm

    #508079

    I have 2 SQL 2000 servers I patched to .859 that started this. Something in the patch causes it and I haven't narrowed it down yet. Without reinstalling, the Hotfix further is the only thing I have heard truely corrects since they are not production issues thou I have chosen not to worry about and am fine using QA anyway.

  • May 28, 2004 at 5:47 am

    #508168

    See my post above yours. If you use DOMAIN ACCOUNTS for the service and for authentication when installing report services, you will NOT have to load the hotfix in order to use report services with SQL. And Enterprise Manager will work without problem.

     

  • June 7, 2004 at 3:44 pm

    #509340

    FYI... Hotfix 878 will correct the issue.

    http://support.microsoft.com/?kbid=838166

    It is definently happens between 818 and 859 that cuase it for me as the only server with 859 left on it is still giving the issue.

  • June 22, 2004 at 8:40 am

    #511443

    Is Hotfix 878 available anywhere without paying Microsoft $99+? It doesn't seem to be available on there site.

  • June 23, 2004 at 7:54 am

    #511618

    After a long time, Microsoft has finally decided to publish a KB on this issue:

    http://support.microsoft.com/default.aspx?kbid=831997

    The patch is not available on this page, but you can download a later version from:

    http://support.microsoft.com/?kbid=838166

    Razvan

  • September 10, 2004 at 7:38 pm

    #522664

    I just called microsoft and they emailed the hot fix to me.  I installed it, and now it seems to work fine.  Also, the guy I talked to said there is no charge when the solution requires a hotfix. I'm sure glad someone had this problem before I did, so I could find the solution here. 

    Vern

  • September 15, 2004 at 3:55 pm

    #523249

    Vern,

    Is that the same as can be downloaded here?

    http://support.microsoft.com/?kbid=838166

    Maarten

     

Viewing 15 posts - 1 through 15 (of 15 total)

You must be logged in to reply to this topic. Login to reply