MS SQL login from Navision 4.0 client

kfokfo Member Posts: 2
I have copied then file xp_ndo.dll to the binn libary on MS SQL Server ver. 8 (date 15. sept. 2004)

I have Add the extended stored xp_ndo_enumusersids and xp_ndo_enumusergroups, with permission exec permission to guest and public

But, when i start the client and try to connect with windows login, i get the following error:

"cannot find then function xp_ndo_enumusergroups in the libary ..MSSQL\Binn\xp_ndo.dll. Reason 127(error not found)"

](*,)

Comments

  • ShenpenShenpen Member Posts: 386
    Strange... never had problem with that. I suggest to contact Microsoft on PartnerSource, Support.

    Do It Yourself is they key. Standard code might work - your code surely works.
  • NobodyNobody Member Posts: 93
    :)

    The stored procedure pointing to the DLL has to reside in the MASTER database not the Navision database.
  • kinekine Member Posts: 12,562
    Restart the SQL Server service... :-)
    Kamil Sacek
    MVP - Dynamics NAV
    My BLOG
    NAVERTICA a.s.
  • GoMaDGoMaD Member Posts: 313
    check the version of the dll
    Now, let's see what we can see.
    ...
    Everybody on-line.
    ...
    Looking good!
  • wizard_of_clausewizard_of_clause Member Posts: 6
    have previous version's (3.60) databases installed, which work ok.

    added the xp_ndo.dll from the 4.00 CD, into the master db (where else could extended stored procedures be added? :-s ), restarted the services...

    same story as in the original post from kfo.

    basically, I did all that is suggested by the instructions on the 4.00 CD. does anyone have any additional information on this function? Is this something completely new compared to 3.60? I googled a bit around and got 3 hits on "xp_ndo_enumusergroups", and all 3 are questions on forums without relevant answers.
    The difference between theory and practice is smaller in theory than it is in practice.
  • kinekine Member Posts: 12,562
    It is working without problems. Check if there is "xp_ndo_enumusergroups" and "xp_ndo_enumusersids" extended procedure with the correct permissions.

    To test it, you can try to run this SQL query in Query Analyzer:
    exec xp_ndo_enumusergroups
    
    and
    exec xp_ndo_enumusersids
    

    If there is some problem, remove the stored proc. and re-register them...

    It must return table with SIDs and users or groups...
    Kamil Sacek
    MVP - Dynamics NAV
    My BLOG
    NAVERTICA a.s.
  • wizard_of_clausewizard_of_clause Member Posts: 6
    I am looking at MBS Navision 4.0 SP1 COURSE: 8404B Installation and configuration training.

    Not a single hit on "xp_ndo_enumusergroups".

    On page 125 it says to manually create "xp_ndo_enumusersids", that's all. One sp and nothing else. As far as I recall this procedure is the same as in v3.60. As I already pointed out, the documentation is incomplete and to get things working "without problem" one has to turn elsewhere.

    However, I tried to add the same dll under the suggested name xp_ndo_enumusergroups" and bingo. :?

    The curious thing is, that I already tried this, with permissions and all, and it didn't work. :-k So I guess I have to thank kine for insisting.
    The difference between theory and practice is smaller in theory than it is in practice.
  • degrem_mdegrem_m Member Posts: 1
    Hi,

    I had got the same errors.



    But Now it's ok, I added in Master from Sql server 2005 two Extend Store Procedure

    xp_ndo_enumusersids and xp_ndo_enumusersgroups with the same dll ( MSSQL\Binn\xp_ndo.dll)

    or
    excute sp_addextenddcpro "xp_ndo_enumusergroups" , "xp_ndo.dll"
    excute sp_addextenddcpro "xp_ndo_enumusersids " , "xp_ndo.dll"

    Thanks too Mehdi & Ariella
    Michel DEGREMONT
  • stellastella Member Posts: 1
    "add the file to the extended stored procedures
    already installed on SQL Server. (The name of the extended stored procedure must be xp_ndo_enumusergroups)."

    How to add the file to the extended store procedures ?
  • I know it is an old post, but if someone has the same issue as me... (be carefule) The stored procedure name is cas sensitive.
Sign In or Register to comment.