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
- :
- Re: SQLServerSelectLogin2 Problem
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
‎Sep 12, 2016
11:23 AM
SQLServerSelectLogin2 Problem
I am using the same parameters for SQLServerSelectLogin2 in 3 InstallScriptMSI projects. All 3 were working and now the 'Browse' list of database servers is empty for one of the projects. I compared the InstallScript code between projects and it is identical. What could have happened?
Thanks
Thanks
(3) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 14, 2016
10:55 PM
Would it be possible for you to post a project that replicates the behavior so that I can look into the issue?
Thank you.
Thank you.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 15, 2016
09:30 AM
Great! Thanks.
I will send project via PM later today.
I will send project via PM later today.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 16, 2016
08:23 AM
Thanks Hidenori for pointing out simple mistake in my InstallScript code.
As you pointed out, the first parameter for SQLServerSelectLogin2 must specify a connection name present in the ISSQLConnection table.
I see now that the reason it worked at one time and quit is because I removed some unused SQL scripts from the SQL view and that (properly) removed an entry from the ISSQLConnection table.
All is well now 🙂 Thanks Again!
As you pointed out, the first parameter for SQLServerSelectLogin2 must specify a connection name present in the ISSQLConnection table.
I see now that the reason it worked at one time and quit is because I removed some unused SQL scripts from the SQL view and that (properly) removed an entry from the ISSQLConnection table.
All is well now 🙂 Thanks Again!