About bobmcm461

bobmcm461 · ‎May 21, 2014

Hello DLee, Thanks for the information. You have confirmed what I have been able to get from the documentation and some support interaction. In my case I have been able to turn on the MSI logging on the general tab, but get the prerequisites logged you have to use the /debuglog command line. Unfortunately, this has a side effect that if you have to reboot during the prerequisites, the installation does not restart upon reboot even though the prq is set to restart after reboot. Looking through the command line parameters I have not found one that will force the reboot. Thanks again, Robert M.

bobmcm461 · ‎May 20, 2014

I have been given a requirement to log if an installation prerequiste fails. I am unaware of a way to do this. Is there a way? Thanks, Robert M.

bobmcm461 · ‎Apr 21, 2014

Did you ever find a solution to this problem. I have looked through the list of errors, and the file in question is in a different component, and the installer runs correctly, but I would like to get rid of the warnings at build time if possible. thanks, Robert M.

bobmcm461 · ‎Dec 18, 2013

I have two InstallScript MSI projects that I need to combine into one project. Is there a way that I can copy and paste Features and components from one project to another?

bobmcm461 · ‎Nov 05, 2013

I am also running into the issue where DotNetCoCreateObject is failing. Has anyone else found a solution to this problem. Thanks, Robert M.

bobmcm461 · ‎Oct 23, 2013

I found the problem. InstallShield does not like 32 bit color depth. I changed the sidebar to 24 bit color depth, and the image showed up with no changes to code. Thanks, Robert M.

bobmcm461 · ‎Oct 22, 2013

Did you ever find a solution to this problem. I am running into the same problem. Everything seems to be working correctly, but the Bitmap does not show up. This is the code that I am testing. MessageBox(SUPPORTDIR ^ "Sidebar-PSPPM-1.BMP", INFORMATION); nResult = DialogSetInfo(DLG_INFO_ALTIMAGE, SUPPORTDIR ^ "Sidebar-PSPPM-1.bmp", DLG_INFO_ALTIMAGE_VERIFY_BMP); if (nResult < 0) then szMessage = SUPPORTDIR ^ "Sidebar-PSPPM-1.bmp not found"; MessageBox(szMessage, INFORMATION); abort; else MessageBox("OK", INFORMATION); endif; nResult = SdWelcome(szTitle, szMsg); I have verified that the file exists where it says, but the sidebar graphic does not show up. I just get a blank area. I've done this in the past with no problem. The only difference is that I am doing this in Test UI. Could this be an issue? Thanks, Robert M.

bobmcm461 · ‎Aug 28, 2013

I am working on an InstallScript MSI package that uses 14 SQL Scripts to create the SQL Databases. They take from 30-60 minutes to complete. By the time that the first script is completed, the progress bar is at 100 percent. Is there a way to either configure the progress bar so that it does not complete until all of the script are done or is there a way to reset the progress bar between scripts. Thanks, Robert M. NOTE: I apologize if this is a repost. I thought that I sent this post out yesterday, but I can not find it in the list.

bobmcm461 · ‎Aug 08, 2013

Hello Michael, Thanks for the information. Unfortunalty, this does not fit the situation. The project was fine, and the variables were correct when I created the project. Somehow the problem occurs later in the project's life. The project that I'm working on was correct for months. I only found out about the change when I tried to build. All of a sudden the project wouldn't build, and I am getting errors about not being able to find script files, etc. This is when I look at the predefined variables and find that they are incorrect. I have not been able to figure out a common action that might be causing this problem. It just seems to happen at random. I tried the Save_As option, but the check box for adding the project name directory was already cleared. I resaved the project and reloaded it but the directory is still incorrect. I don't know if setting, saving and then clearing it would help. I don't want to make it any worse. I'm not sure how to edit the ISM file directly. In the case of the project that I am working I have noticed that the ISProjectFolder variable is correct, so as a work around I have changed the type from 1 to 2 on the variables that incorrect, and referenced this variable in them. This at least works around the problem without having to edit the project any time that it might move. I will have to check the other projects to see if that workaround will work with them. It just seems strange that the project works fine and then changes. It's almost like the create project directory flag is getting set in some other place. Thanks, Robert M.

bobmcm461 · ‎Aug 07, 2013

I continue to have this problem come up, and looking through the forums, this problem has existed for a long time (almost 10 years). Every so often when I load the project, ISPROJECTDIR and the ISProjectDataFolder both have an extra directory level in them. For example: ISProjectFolder = "C:\CurrentDev\ProjectDirectory\" This is correct ISPROJECTDIR = "C:\CurrentDev\ProjectDirectory\ProjectDirectory" ISProjectDataFolder = "C:\CurrentDev\ProjectDirectory\ProjectDirectory" This is incorrect. There is an extra ProjectDirecory at the end of the variable. The only solution that I have seen is to go into the direct editor, and change the type from 1 to 2 and then manually edit the paths. This means that I have to fix this problem every time the project gets moved. We have a build machine where we build the installation, but we are looking to be able to get to a point where anyone who has a valid license for Installshield can get the latest version of the project and then build the project on their computer. Unfortunatly, not everyone has the exact same directory structure which means they have check out the file and then change it to be able to build. I have a number of projects that I am able to do this by using relative variables based on the ISPROJECTDIR variable. How do we get the project file to assign the correct value to the predefined variables. Any assistance would be appreciated. Thanks, Robert M.

bobmcm461 · ‎Jul 01, 2013

I'm using an InstallScript MSI, and have the same issue. When looking at the verbose log file, I found an error message that stated that removing a component from a feature is not allowed and this caused the installation to fail to update the files. This was strange as I didn't delete any components from the installation, I added one. The first time it happend, I was able to add then new file to an existing component. After that only solution that seemed to work was to move to a major upgrade. Robert M.

bobmcm461 · ‎Jun 18, 2013

Note: I have already tried creating my own Prereq, but get the same result. At the end of the SQL Server installation, the installation just stops. has anyone had any success in finding a resolution to this problem. What I have been able to find out is that the installation needs a reboot, but it just stops at that point, and terminates the entire installation. Any suggestions would be a help. Thanks, Robert M.

bobmcm461 · ‎Apr 29, 2013

I am restructuring an InstallScript MSI package. If I rename a component will this effect IS's capability of executing a succesful upgrade on a previous version of my software. I seem to remember having a problem with this, but I can't find the reference. I see something that says if I change the component code I have to do a major upgrade, but does changing the name of the component change the component code. Thanks, Robert M.

bobmcm461 · ‎Apr 16, 2013

I am just starting out with the SAB, and am a little confused about the Prerequisites. Should I copy the prerequisite files from my development machine with the IDE on it, or is there a way to automatically download the needed prerequisites. Is there any reference material on the SAB. I've written batch files to work with the IDE before, but this is my first exposure to the SAB. Thanks, Robert M.

bobmcm461 · ‎Jan 04, 2013

To resolve this issue, I have added a line of code to the OnSQLLogin function to create a new property. MsiSetProperty(ISMSI_HANDLE, "IS_SQLSERVER_SERVER_FULL", szServer); and then used this property to change the config file. Thanks, Robert M.

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

Re: Installscript MSI project - How do I log when an Installation Prerequisite Fails.

Installscript MSI project - How do I log when an Installation Prerequisite Fails.

Same Problem

Combining InstallScript MSI Projects

Re: DotNetCoCreateObject Error in IS 2012

Re: Custom image does not show up.

Re: Custom image does not show up.

SQL Scripts and Progress Bar

Re: ISPROJECTDIR duplicating directory issue.

ISPROJECTDIR duplicating directory issue.

Have the same problem.

This still seems to be a problem.

Changing Component Names

Stand Alone Builder Prerequisites

Solution

Re: Installscript MSI project - How do I log when an Installation Prerequisite Fails.

Installscript MSI project - How do I log when an Installation Prerequisite Fails.

Same Problem

Combining InstallScript MSI Projects

Re: DotNetCoCreateObject Error in IS 2012

Re: Custom image does not show up.

Re: Custom image does not show up.

SQL Scripts and Progress Bar

Re: ISPROJECTDIR duplicating directory issue.

ISPROJECTDIR duplicating directory issue.