[MiniFix] Fixing Could not find stored procedure 'spStartUpLocatorStatus' in Locator

Results 1 to 3 of 3
  1. #1
    Member Franc[e]sco is offline
    MemberRank
    Apr 2009 Join Date
    ItalyLocation
    74Posts

    [MiniFix] Fixing Could not find stored procedure 'spStartUpLocatorStatus' in Locator

    So, I ran into this issue and discovered that it was pretty common among people and no one really posted a proper solution to it, so here's how you fix it.

    Basically the Locator would close immediately after I start it up and log this error:
    MLocatorDBMgr::StartUpLocaterStauts - Could not find stored procedure 'spStartUpLocatorStatus'.

    MLocator::Create - DBÃʱâÈ­ ½ÇÆÐ.
    This issue is either caused by:
    1. Not setting up your Database properly (in which case you just need to get a proper database backup and restore it)
    2. Not setting your odbc's default database (most common one)


    The 2nd one was the problem in my case, and it's usually the most common cause for this error.

    Just go to start -> run, type odbcad32 and press enter.
    Then select GunzDB and click configure, then click Next.
    Re-type your password at the bottom and click Next.
    Tick "change default database to..." and select GunzDB

    Now click next and finish. Your Locator should run fine now!


  2. #2
    In Progress... FFXIV... Anju is offline
    MemberRank
    Oct 2010 Join Date
    Mist Ward 7 #38Location
    1,946Posts

    Re: [MiniFix] Fixing Could not find stored procedure 'spStartUpLocatorStatus' in Loca

    Possible that you were just missing that store procedure table.

  3. #3
    Member Franc[e]sco is offline
    MemberRank
    Apr 2009 Join Date
    ItalyLocation
    74Posts

    Re: [MiniFix] Fixing Could not find stored procedure 'spStartUpLocatorStatus' in Loca

    Quote Originally Posted by Anju View Post
    Possible that you were just missing that store procedure table.
    No. I checked my database and the procedure was there so I didn't touch a thing in the database.
    Then I fixed the odbc and it worked.
    I'm 100% sure it was that.
    I'm using sql server 2012 so maybe it now requires a default database



Advertisement