hi folks,
i have captured an app that has datasources, nothing seems wrong with them but when i install them i get this error:-

"error 1919. error configuring data source: cpblims, odbc error 11: driver's configDSN, COnfig driver,
or config translator failed. verify that the file cpblims exists and that you can access it"

i read a couple of posts saying install mdac, this is allready on the build so i have began to worry. the registry entries for odbc.ini are present also.
i have pasted the attributes and table entry below, any help is much appreciated on this on:-

odbcDataSource table entry:- "cpblims","ODBCDataSource","cpblims","Microsoft ODBC for Oracle","0"

attributes:-
Description=cpblims
Attributes=W
ServerName=rvlpcpb.world
Translation Option=0
Application Attributes=T
PrefetchCount=10
Lobs=T
ResultSets=T
Longs=F
DisableMTS=F
Failover=T
QueryTimeout=T
CloseCursor=F
FailoverRetryCount=10
FailoverDelay=10
DSN=cpblims
UID=cpblims
SERVER=rvlpcpb.world
BufferSize=65535
SynonymColumns=1
Remarks=0
StdDayOfWeek=1
GuessTheColDef=0
StripTrailingZero=0
UserID=
Translation DLL=
PWD=

0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Answers

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
0

I have run into the same problems with a Oracle ODBC Driver from 9i (9.2.something).

I created an empty MSI file using Wise, then added the ODBC Data Sources, which failed to install on another machine as expected.
Then I did the Schieb way, but that still gives me the error and not having any ODBC Data Sources in de System DSN tab.

This is the message I get in the Event Viewer:

Product: XLReporting ODBC Data Sources -- Error 1919.
Error configuring ODBC data source: xlrepcopy, ODBC error 6: Onderdeel is niet gevonden in het register..
Verify that the file xlrepcopy exists and that you can access it.


"Onderdeel is niet gevonden in het register" is Dutch and stand for "Part is not found in the register". Not too sure about "part" but it's a direct translation.

The MSI is pushed using Altiris and executed under a username that has local administrator permissions.

What can still be wrong here?

Answered 01/06/2006 by: Prism
Yellow Belt

Please log in to comment
0

thanks guys, worked a treat.

Answered 12/20/2005 by: misk
Orange Senior Belt

Please log in to comment
1

Setting up the ODBC connection via the reg table (instead of the odbcdatasource table) as schieb suggests is a good solution as it means that the MSI doesn't worry about 3rd party ODBC drivers (such as Oracle) acutally being installed first.

You will obviously need Oracle drivers ultimately installed for the app to work but it doesn't matter about installation order - which is probably what's causing the error message.

There are no drawbacks to this method that I know of...

Regards,
Rob.

Answered 12/17/2005 by: MSIPackager
Third Degree Black Belt

Please log in to comment
0

Whenever I get a 1919 error I delete the odbc entries from the odbc tab in Wise. Then export the odbc info from HKLM\sotware\odbc on a clean install of the program. Now import that .reg into the registry section of Wise. This is fixed 1919's for me everytime from what I remember.

Also, Oracle has been installed already right?

Answered 12/16/2005 by: schieb
Purple Belt

Please log in to comment
Answer this question or Comment on this question for clarity