Errors HY024 and 945

gadzilla1gadzilla1 Member Posts: 316
edited 2009-01-09 in SQL General
I'm posting the following as a POSSIBLE solution to an issue I had. I will let the experts pick this apart. If I'm way off I apologize...I just wanted to share this in case it is valid and potentially help others.

Recently I tried to access a development database from my NAV File dropdown of recently accessed databases. I clicked on 'TestDBOne' and got the error "ODBC SQL Server Driver: Database is invalid or cannot be accessed. State ID: HY024."

I searched mibuso on 'HY024' and only found one link that did not seem to apply to my situation. I checked SQL Server Management Studio and saw that TestDBOne and another SQL Reporting Services database were missing the '+' to the left under Databases...there was nothing but the database name, no tables, no data. :shock:

I googled HY024 outside mibuso and did not find a clear direction to take. On a hunch I right clicked the affected database in SQL Server Management Studio and selected properties and got another error, SQL error 945. I searched on the 945 error and found a non-NAV site that suggested restarting the SQL sever as step #1. I did so and had access to the NAV and SQL Reporting Services databases right away (the '+' to see the database detail had returned).

I don't know the reason for the corruption, but I just wanted to make sure anyone who has an issue like I had doesn't give up on days or weeks of hard work. Here's the 945 error link I used.

http://www.lcard.ru/~nail/sybase/error/9744.htm

Comments

  • garakgarak Member Posts: 3,263
    but this is for sybase SQL database server enginge. Not the MS SQL server database enginge.
    Maybe it's the same error code and error solution
    Do you make it right, it works too!
  • dmccraedmccrae Member, Microsoft Employee Posts: 144
    The most common case for this error, is that the database is in single-user mode and has an open connection on it (using that single user slot), when you try to access it on another connection, e.g. NAV.

    This might also be the case for you since the SQL Server restart will kill all connections, then you can access it with a single connection again (but no more).

    Check the access status of the database, from Management Studio or from NAV.
    Dean McCrae - Senior Software Developer, NAV Server & Tools

    This posting is provided "AS IS" with no warranties, and confers no rights.
  • garakgarak Member Posts: 3,263
    good tip dmccrae
    Do you make it right, it works too!
  • krikikriki Member, Moderator Posts: 9,112
    [Topic moved from 'NAV/Navision' forum to 'SQL General' forum]
    Regards,Alain Krikilion
    No PM,please use the forum. || May the <SOLVED>-attribute be in your title!


  • gadzilla1gadzilla1 Member Posts: 316
    Great, thanks to all for the replies and input. My main objective was to get a post out there that could be searched on for both errors. I'd feel badly if another user spun their wheels, hopefully this may help. I'll put solved in the title.

    dmccrae: where do you check the access status in Management Studio?
Sign In or Register to comment.