This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- ISSQLFilteredList and ISSQLServerList does not detect SQL Server 2008 instances
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jan 27, 2010
09:24 AM
ISSQLFilteredList and ISSQLServerList does not detect SQL Server 2008 instances
Hi
I used a basic msi project. In my dialog I have a combobox that uses ISSQLFilteredList custom action to display instances of SQLServer and I also have SQLBrowse that uses ISSQLServerList to display all SQL Servers on the netwok. The problem is I don't see SQL SERVER 2008 instances. I see SQL Server 2005.
It evens put sometimes in my combobox a number 1 or sometimes a value like #TEMP0004 ( I don't know where that comes from).
Anybody know if it is an issue?
I used a basic msi project. In my dialog I have a combobox that uses ISSQLFilteredList custom action to display instances of SQLServer and I also have SQLBrowse that uses ISSQLServerList to display all SQL Servers on the netwok. The problem is I don't see SQL SERVER 2008 instances. I see SQL Server 2005.
It evens put sometimes in my combobox a number 1 or sometimes a value like #TEMP0004 ( I don't know where that comes from).
Anybody know if it is an issue?
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Feb 08, 2010
02:10 PM
Can you try to change InstallShield use the Microsoft SQL Server Native Client ODBC driver by following the steps below, and see if the problem is solved?
[LIST=1]
Go to the ISSQLDBMetaData table in the Direct Editor.
Find the "MSSQLServer" row.
Change the AdoDriverName column from "sqlolddb" to "sqlncli".
Change the DsnODBCName column from "{SQL Server}" to "{SQL Native Client}"
Rebuild your setup.
Note that the SQL Native Client ODBC driver needs to be present on the machine that your setup is running.
[LIST=1]
Note that the SQL Native Client ODBC driver needs to be present on the machine that your setup is running.