Tip: How to add ODBC DSN to (Wise) package.
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:
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!
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
Answers (9)
Please log in to answer
Posted by:
evasive2008
16 years ago
can't add it that way, I have a dll sitting on a fileshare (so they can easily upgrade it they say).
Posted by:
rpfenninger
16 years ago
One of the finest advantages when importing ODBC settings through the registry table is that this way it gets cleanly removed(during uninstall).
Posted by:
gmorgan618
17 years ago
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...
So does REFWI (Radia extension for windows Installer) for that matter...
Posted by:
mazessj
17 years ago
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
--Josh
Posted by:
Tone
17 years ago
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?
Posted by:
cygan
17 years ago
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
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
Posted by:
turbokitty
17 years ago
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.
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.
Posted by:
AngelD
17 years ago
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.
Posted by:
TOBES_UK
17 years ago
I use Installshield and add them in System Configuration - ODBC Resources. Create the Driver then the DSN. Always worked fine.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.