Help! Timberline Data Source connection

[juran]

Dear All,

I wrote a program which uses ADODB.Connection to connect to Timberline Data Source. It worked fine on my development machine. However, when I wrapped up a setup kit to the user. The user got an error as follow:

Description: [Timberline][ODBC Driver][DLL]ODBC Driver not activated for
this application [TS 3271]
Number:-2147467259
Source:Microsoft OLE DB Provider for ODBC Drivers

My code caused the error is:

conn.Open "DSN=Timeberline Data Source"

I am wondering if anybody had experienced the same or similar error message before. Any suggestions would be highly appreciated.

Best regards,

Juran

 

[abaerst]

Juran,
I wish that I had an answer for you, but I only have additional information for the problem. I am experiencing the same issue. I am accessing Timberline via a SQL Server DTS job. I can create the job and run it fine from Enterprise manager, but when I schedule the job and have it run automatically I get the error that you described. Have you had any sucess solving this issue?

abaerst

 

[mirtheil]

You're probably missing the Timberline driver. Can you create a DSN through the ODBC Administrator? Has the Data Source referenced in your code been created?
Does Timberline work on the user's machine?

info@mirtheil.com
Custom VB and Btrieve development.
Certified Pervasive Developer
Certified Pervasive Technician

 

[abaerst]

Well here is the weird part. I have installed a complete version of Timberline just to make sure that I have the ODBC driver. I can create a DSN with no problems. I can see the tables in Timberline. I can attach to the tables via Access. I have written an entire SQL Server DTS job that extracts information from Timberline and moves it to SQL Server. I can run that job with no problems if I kick it off manually, but as soon as I attempt to automate the DTS job through the scheduler I run into this error.

Error string: [Timberline][Timberline ODBC Driver][File Library]Timberline ODBC Driver not activated.
Error source: Microsoft OLE DB Provider for ODBC Drivers

It's the same job, but the big difference is that it is running as one user when I kick it off manually and another when the service starts it automatically. I have done my best to make sure that the service user has at least equivalent permissions as I do, but I still get this error. It feels like a permission error, but the source of the error hasn't made itself apparent yet.

abaerst

 

[drobbinssql]

Abaerst and Juran,

Did you ever resolve this issue? I have the issue and wanted to see if we could help each other.

Dave

 

[abaerst]

I solved the issue sort of. There were two key parts of the solution. 1) Permissions and 2) the method of running the DTS job. I'm not sure about the details of your situation so I will give you both and you determine if either is helpful. As far as issue #1 goes, I'm usually against wide open access, but I beat myself up so badly trying to get this Timberline job to start properly that I was ready to try anything. I changed the SQL Agent user to 'sa'. That opened to pipeline and allowed the job to run. My suspicion that permissions were involved were confirmed. I don't plan to leave the user as 'sa', but that's the starting point. The other issue is a little more peculiar. I was starting the DTS job using the CmdExec method like this:

DTSRun /~Z0xC7D7BFA6493F7A9A42D894515B2173A1CAEE9DCC21362515A08C23CDGH88EE7926900603CB1B5564528D1BA445C26E9EEAA3C0D26744CC81AF1AE20794F4559CBEC96B9226596EB2566968AC359B031B7E9EB3E9C3A9E214A9F5AEFDDAE3CCC10A8572C63BA5E5EEE9967E

but in talking to a tech from our parent company, he said that he ran into nothing but trouble initiating Timberline jobs using that method. He suggested using the xp_cmdshell stored proc. The xp_cmdshell proc must be run from the master database as opposed to the user db where the user data resides. Here is an example:

xp_cmdshell 'DTSRun /S servername /U sa /P xxxxxxxx /N "Job Name"'

You can use the GUID instead of the /N switch, but it becomes a royal pain tracking down the GUID every time you make a change to the job and want to retest.

One or the other or the combination of both solved my problem. I'm still not 100% satisfied with the solution and expect to perform some further forensics to figure out how to get away from running as 'sa'.

I hope some of this information is useful. I found the whole process very frustrating and unrewarding. I hope that I can spare others that grief.

Aloha and Mahalo

abaerst

 

[brianne]

This message is for juran. I am having the same issue with the Timberline ODBC. I am trying to connect with an ADODB connection. I receive the same error.
Error Type:
Microsoft OLE DB Provider for ODBC Drivers (0x80004005)
[Timberline][Timberline ODBC Driver][File Library]Timberline ODBC Driver not activated.

Did you ever resolve your problem?

 

[jibberski]

That message states Timberline ODBC driver is not activated.. You'll have to reinstall Timberline with ODBC checked. Don't forget to look up your activation code!

-Jibber

 

[jibberski]

Timberline Knowledgebase#: KB145302