Extended Stored Procedure issue

beboelke
beboelke Member Posts: 19
edited 2013-06-05 in NAV/Navision Classic Client
I recently had to reinstall SQL Server (2008 R2) and restore numerous customer databases. One of these databases, which is restored via a SQL backup rather than through an FBK (included just for the record) refuses to recognize the xp_ndo_enumuserids and xp_ndo_enumgroups ESP's. However, numerous other databases on the same SQL instance using the same version of NAV (2009 R2) have no issue. I have "reinstalled" the DLL both on my system and recreated the Extended Stored Procedures within SQL with no impact.

Has anyone ever run into this scenario?

Comments

  • bbrown
    bbrown Member Posts: 3,268
    I'd be a little surprised that any NAV database would work with those stored procs as named. Or is that just a typo in your posting here?
    There are no bugs - only undocumented features.
  • beboelke
    beboelke Member Posts: 19
    Typo in the posting. After checking them for the 20th time, I did find I have misnamed one of them :oops: , and recreating it resolved the issue. However, I still am at a complete loss to explain why only one out of ~10 databases complained.
  • bbrown
    bbrown Member Posts: 3,268
    Let me guess. You named it "xp_ndo_enumuserids" instead of "xp_ndo_enumusersids"?

    Why it only broke with one has me stumped also.
    There are no bugs - only undocumented features.
  • beboelke
    beboelke Member Posts: 19
    Correct. And I even read a posting saying to check that (granted, it was at the end of a long day), I looked at it, and didn't see it until this morning.
    ](*,)

Categories