I have searched the forum how to add ODBC Data Source (DSN) to my package (wsi). Whenever I imported the ODBC via import (using wise 4.6/5/5.6), I got Windows Installer (MSI) 1919 errors. This seems to be some Wise feature....

On the forum, many people talked about adding the ODBC Data source to the registry... But I could not find an hands-on, so that's the reason for this post:

1. make the ODBC link (in my case a DSN)
2. start regedit
3. export the following keys:
HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\ODBC Data Sources]
"MYDSN"="Pervasive ODBC Client Interface"

[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\MYDSN]
"Driver"="C:\\Program Files\\PVSW\\Bin\\w3odbcci.dll"
"Description"="Pervasive ODBC Client Interface"
"ArrayFetchOn"="1"
"ArrayBufferSize"="8"
"TCPPort"="1583"
"ServerName"="serv01.1583"
"ServerDSN"="MYDSN"
"TransportHint"="TCP"
"TranslationDLL"=""
"TranslationOption"=""
"AutoDoubleQuote"="0"

For the above, I deleted other non-relevant DSN (to my package).

4. import the registry file in your package (right mouse, import... ;-))

That's all folks!
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

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

Answers

0
Wise isn't the only one - Installshield also offers the 1919 error when attempting to use the ODBC Resources section

So does REFWI (Radia extension for windows Installer) for that matter...
Answered 02/01/2007 by: gmorgan618
Blue Belt

Please log in to comment
0
You are only permitted to include certain attributes in the ODBCAttribute table. Off-hand, I'm not sure which ones are allowed and which ones aren't, but it's the disallowed attributes that are causing the 1919 error. Reduce the entries in the ODBCAttribute table to the bare minimum (not sure what that is for w3odbcci) and put the rest into the Registry table. This is why people often recommend using the registry exclusively and avoiding the ODBC tables, but if you know which attributes are allowed and which ones aren't, you can make it work.

--Josh
Answered 02/18/2007 by: mazessj
Blue Belt

Please log in to comment
0
ORIGINAL: mazessj
You are only permitted to include certain attributes in the ODBCAttribute table. Off-hand, I'm not sure which ones are allowed and which ones aren't, but it's the disallowed attributes that are causing the 1919 error. Reduce the entries in the ODBCAttribute table to the bare minimum (not sure what that is for w3odbcci) and put the rest into the Registry table. This is why people often recommend using the registry exclusively and avoiding the ODBC tables, but if you know which attributes are allowed and which ones aren't, you can make it work.
--Josh

ODBCAttribute

Shouldnt that be the ODBCSourceAttribute table?
Answered 07/31/2007 by: Tone
Second Degree Blue Belt

Please log in to comment
0
this is a common problem with odbc

remove odbc entries from the odbc page and import reg keys via the registry page


wise knowledge and type in error 1919 on your search

hope this helps
Answered 07/31/2007 by: cygan
Fifth Degree Brown Belt

Please log in to comment
0
I've not run into this problem with Installshield, gmorgan618. How are you importing the ODBC DSN?

Installing it on the machine I'm running Installshield on, then ticking it off in the ODBC section has always worked for me.

I find it even adds custom drivers pretty elegantly.
Answered 08/02/2007 by: turbokitty
Sixth Degree Black Belt

Please log in to comment
0
If I recall correct importing ODBC would work for Microsoft drivers and no others, that's why most adds it to the Registry table instead.
Answered 08/02/2007 by: AngelD
Red Belt

Please log in to comment
0
I use Installshield and add them in System Configuration - ODBC Resources. Create the Driver then the DSN. Always worked fine.
Answered 08/07/2007 by: TOBES_UK
Senior Purple Belt

Please log in to comment
0
can't add it that way, I have a dll sitting on a fileshare (so they can easily upgrade it they say).
Answered 08/21/2008 by: evasive2008
Senior Yellow Belt

Please log in to comment
0
One of the finest advantages when importing ODBC settings through the registry table is that this way it gets cleanly removed(during uninstall).
Answered 08/21/2008 by: rpfenninger
Second Degree Green Belt

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