Post reply

ADP Connection Failure

  • February 22, 2007 at 3:46 pm

    #68711

    I have several Access adp's connected to SQL Server 2000 databases on server x4.  These have been in use for years.   Starting this week none of those adp's will open a table.   I receive a "Connection Failure" error message.  The ODBC connections are ok.   The only change in our change in our environment this week has been the Microsoft updates.   I can connect with an adp to a SQL Server 2000 database on server x1 using the same settings as the adp's connected to server x4.   Does anyone have a suggestion on why all of the sudden I can no longer connect to server x4 with adp's?

  • February 22, 2007 at 4:56 pm

    #691288

    Is it possible that it somehow times out because the table is too big now?

    Have you tried recompiling the objects linked to that table?

    ... Just throwing ideas in here, I never had that particular problem.

  • February 22, 2007 at 8:53 pm

    #691300

    Thanks for the tip.  We rebooted the surver and the problem is now fixed.

  • February 23, 2007 at 6:12 am

    #691365

    A bit extreme... but as long as it works .

     

    BTW rebooting clears the proccache and the data in memory... so maybe that would have been enough.

  • December 2, 2008 at 6:59 am

    #906201

    BTW rebooting clears the proccache and the data in memory... so maybe that would have been enough.

    Would this also clear any locks on an .mdb run locally?

  • December 2, 2008 at 7:15 am

    #906214

    Only if sql does a clean shutdown... and that all other connected apps to the mdb file are closed. Then if the lock is still on then you have to manually delete it.

  • December 2, 2008 at 7:16 am

    #906215

    It is a different issue with mdb's. Those are locked by a file with the same name and extension *.ldb. Deleting that file should release locks.

  • December 2, 2008 at 7:35 am

    #906221

    Another bit of info, as far as I remember, if the ldb file is in use, it cannot be deleted (easily anyways) without closing the access applications using it.

  • December 2, 2008 at 9:54 am

    #906332

    I'm experiencing a far more unusual problem than the .ldb. Basically, its not even appearing when I try to open the corresponding .mdb.

    see http://www.sqlservercentral.com/Forums/FindPost612028.aspx for a complete explanation.

    I have a great desire to fully understand what tool can be used implement the opening of this locked .mdb. It was copied from another machine, and so it exists independently from its original location.

    Any help / solutions?

  • December 3, 2008 at 8:46 am

    #906938

    You may need a copy of the original that can be made while the original is "unlocked". Alternatively, if you can get into the mdb, you might be able to export all the objects to a fresh empty database file, and then convert to a project.

    Steve

    (aka smunson)

    :):):)

    Steve (aka sgmunson) 🙂 🙂 🙂
    Rent Servers for Income (picks and shovels strategy)

Viewing 10 posts - 1 through 9 (of 9 total)

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