NAV2009-WinServer2008X64-SQL2008 : xp_ndo_x64.DLL

(0) Share

Report

Posted on by Community Member

hi all,

i installed NAV 2009 on WinServer2008X64-SQL2008

follwing the standard steps, i created the extended stored procedure 'xp_ndo_enumusergroups'

the installation steps sais we should copy xp_ndo_x64.DLL to the SQL \BINN folder, then use it in the extended stored procedure.

the sql management cannot see c:\sql\BINN most likely because of clustering.

so i'm placing the xp_ndo on D:\ and point to it from the extended stored procedure, press ok.

after pressing ok, when checking it back, the file path is not stored

anyone have experience in this subject, is there any workaround or it's not possible to install NAV in a clustered environment?

Thanks

*This post is locked for comments

I have the same question (0)

All responses (7)

Answers (0)

Daniel Rimmelzwaan 3,485 on at

Like (0)

Report

I don't know if that would cause any issues, if it has to display the full path or not. It should be an easy test though. Did you try to connect to NAV with a Windows user?

If I'm not mistaken you can copy the dll onto both cluster nodes and install them in there, and it should work from there.

Was this reply helpful? Yes No
Holger Schaper 20 on at

Like (0)

Report

Hi Romeo

I have the same problem that the file path to the dll is not stored.

(WinServer2008 64 bit, MS SQL-Server 2008).

do you have any solutions for this problem ??

Thanks Holger

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report
Alter the security model to Standard instead of Enhanced to be able to use windows group authentication

Place the DLL on the two SQL servers’ nodes on D:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\Binn\

Create the two stored procedures in the master database on Server using the following script
USE masterEXEC sp_addextendedproc xp_ndo_enumusergroups, 'D:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\Binn\xp_ndo_x64.dll'GOGRANT EXECUTE ON [xp_ndo_enumusergroups]TO PUBLICGOUSE masterEXEC sp_addextendedproc xp_ndo_enumusersids, 'D:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\Binn\xp_ndo_x64.dll'GOGRANT EXECUTE ON [xp_ndo_enumusersids]TO PUBLICGO

Was this reply helpful? Yes No
Daniel Rimmelzwaan 3,485 on at

Like (0)

Report

Hi Romeo, thanks for following up, that will help other people.

Windows authentication works on both standard and enhanced security.

The path depends on where the program files are. Wherever the Binn folder is, that's where the DLL should go. It doesn't really matter though, as long as it is in a folder that is the same for both clusters, and as long as the actual dll is present on both clusters.

The script is good, just all jumbled together. Just for reference, here is the same script (for SQL Server 2005, change the path to where the binn folder is) a little less compressed:
USE master
EXEC sp_addextendedproc xp_ndo_enumusergroups, 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\xp_ndo_64.dll'
GO
GRANT EXECUTE
ON [xp_ndo_enumusergroups]
TO PUBLIC
GO
USE master
EXEC sp_addextendedproc xp_ndo_enumusersids, 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\xp_ndo_64.dll'
GO
GRANT EXECUTE
ON [xp_ndo_enumusersids]
TO PUBLIC
GO

Was this reply helpful? Yes No
Mike Nancekivell 20 on at

Like (0)

Report

I have a similar scenario and wondering if someone could shed some light

I have a 2 node Windows Server 2008/SQL 2008 Cluster.

I was doing some failover testing yesterday and had an error referencing those 2 stored procedures when trying to run NAV from any desktop using windows auth while Node 2 was the active machine. (just rebooted node 1) Node 1 works flawlessly. I'm wondering if anything needs to be done on the node 2. I checked SQL and the extended procedures are there and the path is common to both machines. They are using a shared J drive where the DLL is located. Not sure what I'm missing on this. Again no problems on Node 1 just when we failover to node 2

Any thoughts?

Was this reply helpful? Yes No
Daniel Rimmelzwaan 3,485 on at

Like (0)

Report

The instructions are to put the dll into the 'Binn' folder in the SQL Server installation folder, which is usually on the C drive. Doing it like that, putting the actual dll on both physical clusters, I've never seen an issue with the ESP's. I would suggest you install it like that and see if that fixes it.

Was this reply helpful? Yes No
John DeAguiar on at

Like (0)

Report

FYI I'm noticing some variations in the naming of this DLL. The scripts above expect xp_ndo_x64.dll in one case and xp_ndo_64.dll in another. This small variation in names messed me up for a while. On my SQL Server 2008 R2 64-bit installation, the DLL name was xp_ndo_x64.dll.

Was this reply helpful? Yes No