Unable to creation a SQL database profile

I recently upgraded to 3.6.10 of scheduler and I'm unable to create a connection to any SQL database (2005 is what I'm trying). The error says DBMS MSS is not supported in your current installation.

That sounds like you don't have SQL Server 2000 client (DBLIB) installed on the system and that's why it cannot be found. Please try using either ODBC or ADO/OLE interfaces to connect to your SQL Server database

That is kind of kind of strange because it works fine 3.4.26. We're trying to connect to sql 2005. I have tried to use ADO but still can't connect. I used SQLOLEDB as the provider and get the same error.

Is there a DBLIB for 2005 that we can download somewhere?

Thanks,
Nick

Your old computer seems to have SQL Server 2000 client installed, and your new one doesn't it. That's why you can connect from 3.4 using MSS interface, but not from 3.6

DBLIB has been discontinued after SQL 2000. Yet, it can be still installed from SQL Server resource CD. Microsoft wants you to use the new ADO.NET or OLE.DB drivers for connection to SQL Server, for which you need to have SQL Server client installed.

On the other hand, every Windows system by default has SQL Server ODBC driver pre-installed by Microsoft. May I suggest using the ODBC interface? That is by far the easiest method, no extra stuff is needed to be installed. To use an ODBC interface, please don't forget to configure connection profile in Control Panel / Administrative Tools / Data Sources (ODBC), you can point to that profile in 24x7 settings.

3.6 is being upgraded to the same machine that 3.4 was on. Are most clients using 3.6 using ODBC connections? We are just trying to avoid using ODBC.

Thanks

Are you saying that exactly the same connection settings that used to work in 3.4 don't work anymore in 3.6?

AFAIK, there haven't been any changes in database connection handling between 3.4 and 3.6, other that added support for ADO.NET/OLED.DB connections.

Out of curiosity, why are you "trying to avoid using ODBC?" Any particular reason?

Exactly the same.

We feel that using the ODBC driver will be inefficient.

Please search your system for file NTWDBLIB.DLL. If you find it, and it is in the system search path, you should be able to connect using the MSS interface.
If you find SQLOLEDB.DLL in the system search path, you should be able to connect using the ADO/OLEDB interface (worst option, among 3 available choices).
If you find SQLSRV32.DLL in the system search path, you should be able to connect using the ODBC interface, which is just as good as other interfaces

Thanks for all your help. We have decided to make all the sql jobs, VB scripts. We have been having nightly issues with the sql queues hanging. Hopefully this will give us some idea of what is going on.

Nick