Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 3206
  • Last Modified:

Timberline Data dotnet access code works on XP, not in IIS - Win2k

I am trying to access data from a Timberline Database through .net. Timberline is Construction Accounting Software which uses the Pervasive DataBase Engine. We're on Timberline v9.2.1.

The database access code works correctly from the local web server launched from Visual Studio 2005, but when I view the posted page from IIS (Win2000), I get

ERROR [S1000] [TimberlineODBC][TimberlineODBCEngine ODBC Driver][DRM File Library]Message #6102 [TS 6102]
ERROR [IM006] [Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed
ERROR [01000] [Microsoft][ODBC Driver Manager] The driver doesn't support the version of ODBC behavior that the application requested (see SQLSetEnvAttr).

Other info:
- Server has Framework 1.1 and 2.0 installed, with MDAC 2.8 RTM.
- The web process (iusr_machinename) has been given full control access to the HKLM\Software\Timberline and HKLM\Software\ODBC keys, and naturally, has access to the folder/files.
- Classic ASP ADO code fails similarly, but the identical .vbs ADO code executed through wscript.exe on the server under my security context returns data successfully. (My interpretation: ODBC is working, DSNs are properly configured.)


The questions I would have would be to either 1) just tell me you've run into this exact thing and have the quick tips on how to get Timberline data in IIS (I do not know that anyone ever has), or 2) point me in the direction of how to set *any* SQL Connection Attributes (SQLSetConnectAttr) from within VisStudio, or how I can found out the offending ODBC attributes. Other help appreciated, too.

Some probably-not-important details:
- Connection String = 'Dsn=tl_odbc_std;uid=<masked>;pwd=<masked>'
- SQLText = 'SELECT * FROM JCM_MASTER__JOB'


VBS code that works: (and except for the HTML code, this segment is identical to the Classic ASP code that fails in similar fashion to the DotNet code)
Const adUseClient = 3
Set oConn = CreateObject("ADODB.Connection")
Set oRec = CreateObject("ADODB.Recordset")
oConn.open "DSN=tl_odbc_std;UID=<masked>;PWD=<masked>"

oRec.CursorLocation = adUseClient

strConCat = "Dater = " & VbCrLF
oRec.open "Select job as stuff from master_jcm_job_1 where job LIKE '%-4'", oConn

While not oRec.eof
      strConCat = strConCat & oRec("stuff") & VbCrLF
      oRec.movenext
Wend

wscript.echo strConCat
'When using ASP, employ the right method:
'response.write strConCat

oRec.close
oConn.close
0
goober7
Asked:
goober7
  • 2
1 Solution
 
JohnDesautelsCommented:
Goober7,

Here are a couple of resources I found.

http://www.tek-tips.com/viewthread.cfm?qid=1043380&page=2

http://dbforums.com/t842704.html which had this comment:  I recieved this error. Apparently Timberline had an issue with Windows 2000 service pack 4. The solution was to upgrade Timberline to 8.31 and to install the ODBC patch from thier website.

I support Yardi Property management software which has a SQL Server back-end. It is much more friendly. :-)

John

0
 
JohnDesautelsCommented:
GavinMannion,

I offered possible solutions but have no way to test them to see if they would work.

John
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now