Connectivity problem with Windows Server 2003 and MDAC 2.8 SP2
Connectivity problem with Windows Server 2003 and MDAC 2.8 SP2
I'm having connectivity problems with the latest version (2.50.5) and MDAC 2.8 SP2 on windows Server 2003.
The problem started after installing WSUS (Windows Server Update Services), which has SQL Server Desktop Edition inside it. (See http://www.microsoft.com/windowsservers ... fault.mspx)
I tried deinstalling WSUS but this didn't repair it. I also tried a rollback of MDAC 2.8 SP2 but this was not supported.
The version for sqloledb.dll is 2000.086.1830.00 (srv03_sp1_rtm.050324-1447)
I can't find the file sqlncli.dll it is not on the server and not on my development system (where everything is working)
I tried deinstalling WSUS but this didn't repair it. I also tried a rollback of MDAC 2.8 SP2 but this was not supported.
The version for sqloledb.dll is 2000.086.1830.00 (srv03_sp1_rtm.050324-1447)
I can't find the file sqlncli.dll it is not on the server and not on my development system (where everything is working)
> I cannot login into SQL server, my program crashes at this point.
Try to determine in what part of Borland VCL the error happens. To do it compile your application with "Use Debug DCU" and trace Connect procedure.
> The version for sqloledb.dll is 2000.086.1830.00
Please send this dll by email to dbxsda*crlab*com
Try to determine in what part of Borland VCL the error happens. To do it compile your application with "Use Debug DCU" and trace Connect procedure.
> The version for sqloledb.dll is 2000.086.1830.00
Please send this dll by email to dbxsda*crlab*com
I've rolled back all security fixes but this didn't repair it, finally I rolled back SP1 and this fixed the problem. After reinstalling SP1 for Windows Server 2003 I had the problem again.
I've used the latest DLL 2.50.6 and can't find any other version on this server so I'm definitly using the latest version.
I was in the impression that this problem was fix with 2.50.6?
I've used the latest DLL 2.50.6 and can't find any other version on this server so I'm definitly using the latest version.
I was in the impression that this problem was fix with 2.50.6?