One of our guys discovered this:
If you build a .NET dll named "Security.DLL", SQL Server will try to load it (apparently from the assembly path!) before it's own Security.DLL, and fail. This results in no one being authenticated to SQLServer until you rename your .NET DLL.
Chip H.
If you build a .NET dll named "Security.DLL", SQL Server will try to load it (apparently from the assembly path!) before it's own Security.DLL, and fail. This results in no one being authenticated to SQLServer until you rename your .NET DLL.
Chip H.