Driver's SQLSetConnectAttr failed

Peter,

1. For NT4 package, you can use SP5. I used that for as long as it exited and has no problem with it as far as operating ASPDB.

2. We upgrade all the versions to VB6 and EP+ version to CTX for apartment threading and also Context objects to scale up. In the process, we are trying to save MB and thought that we would save customers some downloading time. I guess we were wrong. Even though the "empty" VB6 runtime loads in my W2000 with no problem at all, it caused some customers a lot of problem and wasted a lot of their time. We should offer the "simplify" packages and the "full" install package.

3. Make sure you install the EP+ packaes in the MTS ("the ball") and not via regsvr32 as the new DLLS supported transaction.

Frank

becasue of the we are trying to save some MB in the lastest

------------
Peter Wijntje at 4/5/00 6:01:20 PM

Today we've bought ASPdb Enterprise edition.

We've worked with ASPdb Free for a while and were so impressed, that we wanted to have the Enterprise edition.

We received version: 6.2629 - EP. After we deleted ASPdb Free and restarted our server (Windows NT 4.0 - Servicepack 4) we installed the enterprise edition in the folder:

c:inetpubaspdb and moved the ASPdbEnterprise.dll to the system32 folder together with the registration ID.

When we open the asp-test-ep.asp page the following error message comes up:

Error # = 0(0)
Description = [Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed
Source = Microsoft OLE DB Provider for ODBC Drivers
SQL State = IM006
Native Error = 0

After contacting the support department of ASPdb we did the following

1) Installed the VB6 Run-time Support package found on http://www.aspdb.com/vb6-init

2) Restart the computer

Same error

3) Re-Installed ADO 2.1

4) Restart the computer

Same error

5) Installed ADO 2.5

6) Restart the computer

Same error

7) Installed Service Pack 6.0a from

8) Restart the computer

Same error

Beside our Windows NT 4.0 Server (The one we're working on) we also have a new /clean Windows 2000 Server with noting else (beside the Windows 2000)installed on it.

We installed the ASPdb Enterprise on the same way we did on the Windows NT 4.0 computer.

Extract the files in c:inetpubaspdb and register the component in MTS. Copying the ASPdbEnterprise.dll in the system32 folder together with the register ID.

Same error comes up!

The latest thing we did was receiving an earlier version of ASPdb Enterprise, version 2.25.18.

Registered it in MTS and put the file ASPdbEnterprise-Server.dll in the system32 folder. AND IT'S WORKING!!! No more errors!

We (Mark at the support department and me) think that the problem lies in te VB6 upgrade. But we're not sure...

Maybe someone has had the same problem and find the solution...
In the meantime we're installing VB6 on our server to see if we can solve the problem...

Greetings,
Peter Wijntje