About gknierim

gknierim · ‎Oct 28, 2010

I was wondering if anyone knew how to do the following in an InstallScript MSI project: 1) By default when you install .NET 4.0 Framework on a 64 Bit OS (Windows 2008 R2), the aspnet_ISAPI.dll's are set to Not Allowed. How can my install set these to Allow? 2) How can I Edit the Feature settings for ISAPI restrictions to Allow unspecified ISAPI modules? Thanks, Greg

gknierim · ‎Oct 28, 2010

I must have missed that one in my search. So, it is working now. I changed the account that MSSQLSERVER was running under from Local Service to Local System and I was then able to install my program in the Program Files folder as well as creating the database files in the Program Files folder. Thanks again!

gknierim · ‎Oct 27, 2010

Yep, that did it. Thought I had that in there before but might have removed it. Everything is working good except for my other issue with the error 27506 located here: http://community.flexerasoftware.com/showthread.php?t=195515 Thanks for your help!

gknierim · ‎Oct 27, 2010

Well, I spoke too soon. Before i get to the SQLLogin interface, I am asking whether you want a Complete or Custom setup (SdSetupType2). If I select Custom and click Next, it goes to the Features screen, then the SQLLogin interface and everything works. However, if I choose Complete and click Next, it never progresses to the SQLLogin interface. I have debugged the OnSQLLogin function and it never loops through both Connections and just returns BACK and so the interface never progresses and is stuck on the Select Setup Type interface. What could be happening?

gknierim · ‎Oct 27, 2010

Thanks. Your last post did the trick. I don't understand why it has to be this way with 2 connections but I guess as long as it works. :cool:

gknierim · ‎Oct 27, 2010

I am getting this error when the install tries to create the database in the Program Files folder. If I make the installation directory other than the Program Files, the installation works and the database is created. How can I get it so that I can install the program in the Program Files directory along with the databases? I am using text replacement in my SQL script using the INSTALLDIR so it has to be a security issue. This is when I try to install on Windows 7 32 Bit. This is an InstallScript MSI project. Thanks, Greg

gknierim · ‎Oct 27, 2010

Not sure if I have made myself clear so I will try again. During install, the user specifies the server name, the SQL login account used to create the database and the database name. I have my create database script in the SQL Scripts view under a Connection. I have the Create Catalog if Absent UNCHECKED. My requirements are: Create the database during the install - not at login which I am assumming is before the user actually completes going through the dialogs. I need the database created in the installation directory and not the default Data directory that they have setup for their database server. The problem is that if I use the standard dialog SQLServerSelectLogin2 and specify the database name, it tells me it can't connect to the database because it doesn't exist. Well, duh. So I was told by IS Support to edit the dialog, hide the database catalog field and browse button and add my own edit field on the dialog. I have done that and after several hours of figuring out how to add the SQLServerSelectLogin2 function to my scripts and modifying that, I am getting the same result. So apparently that doesn't work either. So, in summary, I need to create the database during the install (not at login) and I need to be able to create it in the installatioin directory that the program is being installed to. The database will not exist on installation. My create database script checks for that and creates it if neccessary. So, how can I resolve this? This can't be that hard. Thanks, Greg

gknierim · ‎Oct 26, 2010

OK. I think I understand but where is EDIT_DATABASE defined? and do I just replace EDIT_DATABASE with what???? My Control Id, my edit box name? Do I replace all lines since I'm not using EDIT_DATABASE or just certain lines? I just want to return what is in the Edit field I added. On another note, I don't see how this is any different than using the default edit field to specify the database name. I was told by IS Support to do this. I can't use the standard catalog name field because it requires that the database name exists so this is why I am here.

gknierim · ‎Oct 26, 2010

OK. So I copied the script and inserted into my project. Now what part of this do I need to tweak?

gknierim · ‎Oct 26, 2010

I have looked all over and still can't figure this out. I am using the OnSQLLogin script to display the dialog SQLServerLogin2 to which I have added an Edit Field that will allow the user to specify the database name. The name of the edit field is Edit1 (default name) and the Control Id is 12091. The reason I can't use the standard database catelog field is that I have a createdatabase SQL Script file that I run that will create the database if it doesn't exist. I have the Create Catalog if absent unchecked. My question is how can I retrieve the value the user puts in the newly added Edit field and use that in my text replacement on my SQL Script? I know how to do the text replacement - I just can't figure out how to get the value the user entered into that field? I am using an InstallScript MSI project. Thanks, Greg

gknierim · ‎Oct 19, 2010

Thanks for the reply. I was thinking that the WOW6432 key was the 64 bit part of the registry. My mistake. So, when my install project runs on a 64 bit OS, I have to enable looking in the 64 bit part of the registry. OooooK. One would think that I would need to enable looking in the 32 Bit part of the registry (if I needed to) instead of the part of the registry that matches the OS. But whatever I guess. Maybe this will get changed in future versions when 64 Bit is the norm. Maybe I'm just hoping then. I have the install project set to x64 so that is why I thought it would default to the 64 Bit part of the registry.

gknierim · ‎Oct 18, 2010

This only happened to the one InstallScript project we have. Oddly enough, we went back later and tried to rebuild it again and we didn't get the error again. We are building this project using InstallShield 2011 Professional on Windows Server 2008 R2. The project is for one of our prerequisite checking tools that just basically uses the InstallScript to check and see if the system meets certain requirements before installing our software. It doesn't install anything on the system, just simply checks the system.

gknierim · ‎Oct 15, 2010

We created a new release and still get the same error. We are converting the project over to a MSI project since all the others are.

gknierim · ‎Oct 15, 2010

Well, we aren't checking the 64 bit part of the registry which is why I wasn't using it. However, when adding the line below BEFORE setting the HKEY_LOCAL_MACHINE, then it did find it. So it appears that it searches the 64 Bit part of the registry by default unless you add the line below. Correct? If so, this is opposite of what the documentation says: When you enable the REGDB_OPTION_WOW64_64KEY option, this affects where registry entries from registry sets are created. For example, if this option is enabled when you call the CreateRegistrySet function, the registry set is created in the 64-bit part of the registry. It is recommended that you enable this option for the specific 64-bit registry sets you want to install, then disable the option so other registry entries or sets are not incorrectly created in the 64-bit part of the registry. Anyway, it is working now by adding the REGDB_OPTIONS line below.

gknierim · ‎Oct 15, 2010

We cannot figure out why this fails: if (RegDBKeyExist(SQL_BASE_PATH) = 1) then... where SQL_BASE_PATH = "SOFTWARE\\Microsoft\\Microsoft SQL Server\\Instance Names\\SQL" We are calling RegDBSetDefaultRoot(HKEY_LOCAL_MACHINE); before this. This is on Windows Server 2008 R2 (64 Bit). I have tried the same code on Windows Server 2008 (32 Bit) and it can find the Instance Names\\SQL key. We have tried setting REGDB_OPTIONS to look in the 64 bit part of the registry but it still fails. We have tried various other registry keys of length and some work and some do not. We have tried just going up to the Instance Names in the string and it fails. If we just go up to Microsoft SQL Server, it works. Keys that work (return 1): SOFTWARE\\Microsoft\\Microsoft SQL Server SOFTWARE\\Microsoft\\Microsoft SQL Server\\100 SOFTWARE\\Microsoft\\Microsoft SQL Server\\RefCount SOFTWARE\\Microsoft\\NET Framework Setup\\NDP\\v4\\Full SOFTWARE\\Microsoft\\NET Framework Setup\\NDP\\v4\\Full\\1033 Keys that don't work (return < 0): SOFTWARE\\Microsoft\\Microsoft SQL Server\\Instance Names SOFTWARE\\Microsoft\\Microsoft SQL Server\\Instance Names\\SQL SOFTWARE\\Microsoft\\Microsoft SQL Server\\ExceptionMessageBox SOFTWARE\\Microsoft\\Microsoft SQL Server\\RefCount\\SNAC10 We have checked the permission on the various keys and they all have the same permissions. We have checked whether spaces might be an issue but they are not. it isn't a length issue as we have tried keys that are longer than above and they work. Does anyone have any ideas? Thanks, Greg

Online Status	Offline
Date Last Visited	‎Mar 18, 2019 12:11 PM

ISAPI Settings in IIS7

Re: Error 27506 -

Re: Custom Edit Field on SQL Dialog

Re: Custom Edit Field on SQL Dialog

Re: Custom Edit Field on SQL Dialog

Error 27506 -

Re: Custom Edit Field on SQL Dialog

Re: Custom Edit Field on SQL Dialog

Re: Custom Edit Field on SQL Dialog

Custom Edit Field on SQL Dialog

Re: RegDBKeyExist Fails

Re: Error 150 : Incompatible version of cab file

Re: Error 150 : Incompatible version of cab file

Re: RegDBKeyExist Fails

RegDBKeyExist Fails

Re: Run SQL Scripts based on Specific Version

Re: Subfeature Selection

Re: Features and subfeatures

Subfeature Selection

Re: Features and subfeatures

Run SQL Scripts based on Specific Version

Re: SQLServerSelect Browse List Empty

SQLServerSelect Browse List Empty

Re: How to test if IP Address is accessible

Re: How to test if IP Address is accessible