Quantcast
Channel: Flexera Community Forums
Viewing all 4553 articles
Browse latest View live

Major upgrade leaves old version in add/remove list

$
0
0
I’m making a major upgrade. I have changed the product code but left upgrade code untouched. When I try to install the new installer on previous version (which is already installed on the target machine) the previous version is left in Windows’ Programs and Features list (i.e. “Add remove programs”). The only difference is that it has no icon. Well, it has an icon (default icon) but the original custom made icon is gone.

The new installer seems to uninstall the previous version since I see messages like “Uninstalling previous version” and “Removing shortcuts” during installation of the new version. Shortcuts disappear and I see files being deleted so the new version detects the older version.

I have configured an upgrade path so that all previous versions are major upgraded (i.e. uninstalled before installing the newest version).

Before InstallShield I used Visual Studio’s Setup project and the product version of my product is 6.0.x for Visual Studio Setup projects. They are major upgraded without any problems (e.g. 6.0.5 is upgraded to 6.1.0). The first InstallShield based version is 6.1.0.

I'm trying to delete the related registry key (i.e. so that the previous version disappears from "Programs and Features" list) using a InstallScript custom action but RegDBDeleteKey fails. FormatMessage provides an empty string on RegDBDeleteKey return value. This isn't the best solution since previous version's install files (C:\Program Files x86\InstallShield Installation Information folder) stay on the target system as "garbage".

Does anyone have any ideas what might be causing this? I've seen people complain about the same problem even back in 2008. I hope this isn't the same problem/bug in InstallShield 2014...

InstallShield 2014 setup.exe takes more time compared to IS 12

$
0
0
InstallShield 2014 setup.exe takes more time compared to IS 12.

I had ported an IS 12 project to IS 2014 premier version.
While silent installation with same set of parameters I found that New Setup.exe takes more time to get installed.
While MSI running time is same.but time taken by setup.exe to run .msi is increased considerably.
The analysis found that setup is creating .tmp files and some other files in windows %temp% folder before running .msi.
But these operations are less in case of IS 12 moreover no .tmp files are getting created in IS 12 installer.

Following is the process explorer logs for extra operations in IS 2014

12:04:03.0177839 AM setup.exe 3668 WriteFile C:\Users\Client\AppData\Local\Temp\issDDD9.tmp SUCCESS Offset: 92,160, Length: 10,240
12:04:03.0178508 AM setup.exe 3668 WriteFile C:\Users\Client\AppData\Local\Temp\issDDD9.tmp SUCCESS Offset: 102,400, Length: 10,240
12:04:03.0179253 AM setup.exe 3668 WriteFile C:\Users\Client\AppData\Local\Temp\issDDD9.tmp SUCCESS Offset: 112,640, Length: 10,240
12:04:03.0180520 AM setup.exe 3668 WriteFile C:\Users\Client\AppData\Local\Temp\issDDD9.tmp SUCCESS Offset: 122,880, Length: 10,240, Priority: Normal
12:04:03.0182536 AM setup.exe 3668 WriteFile C:\Users\Client\AppData\Local\Temp\issDDD9.tmp SUCCESS Offset: 133,120, Length: 10,240
12:04:03.0183313 AM setup.exe 3668 WriteFile C:\Users\Client\AppData\Local\Temp\issDDD9.tmp SUCCESS Offset: 143,360, Length: 10,240
12:04:03.0184340 AM setup.exe 3668 WriteFile C:\Users\Client\AppData\Local\Temp\issDDD9.tmp SUCCESS Offset: 153,600, Length: 10,240
12:04:03.0185025 AM setup.exe 3668 WriteFile C:\Users\Client\AppData\Local\Temp\issDDD9.tmp SUCCESS Offset: 163,840, Length: 10,240
12:04:03.0185691 AM setup.exe 3668 WriteFile C:\Users\Client\AppData\Local\Temp\issDDD9.tmp SUCCESS Offset: 174,080, Length: 10,240
12:04:03.0186593 AM setup.exe 3668 WriteFile C:\Users\Client\AppData\Local\Temp\issDDD9.tmp SUCCESS Offset: 184,320, Length: 10,240
12:04:03.0187677 AM setup.exe 3668 WriteFile C:\Users\Client\AppData\Local\Temp\issDDD9.tmp SUCCESS Offset: 194,560, Length: 10,240, Priority: Normal
12:04:03.0189879 AM setup.exe 3668 WriteFile C:\Users\Client\AppData\Local\Temp\issDDD9.tmp SUCCESS Offset: 204,800, Length: 10,240
:
:
:
12:04:03.0905978 AM setup.exe 3668 CreateFile C:\Users\Client\AppData\Local\Temp\{37626276-B7B7-4EED-818A-F1BE8ED40A2A}\IsConfig.ini SUCCESS Desired Access: Generic Read, Disposition: Open, Options: Synchronous IO Non-Alert, Non-Directory File, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a, OpenResult: Opened
12:04:03.0906931 AM setup.exe 3668 LockFile C:\Users\Client\AppData\Local\Temp\{37626276-B7B7-4EED-818A-F1BE8ED40A2A}\IsConfig.ini SUCCESS Exclusive: False, Offset: 0, Length: 4,294,967,295, Fail Immediately: False
12:04:03.0907197 AM setup.exe 3668 QueryStandardInformationFile C:\Users\Client\AppData\Local\Temp\{37626276-B7B7-4EED-818A-F1BE8ED40A2A}\IsConfig.ini SUCCESS AllocationSize: 672, EndOfFile: 669, NumberOfLinks: 1, DeletePending: False, Directory: False
12:04:03.0907674 AM setup.exe 3668 ReadFile C:\Users\Client\AppData\Local\Temp\{37626276-B7B7-4EED-818A-F1BE8ED40A2A}\IsConfig.ini SUCCESS Offset: 0, Length: 669, Priority: Normal
12:04:03.0908710 AM setup.exe 3668 UnlockFileSingle C:\Users\Client\AppData\Local\Temp\{37626276-B7B7-4EED-818A-F1BE8ED40A2A}\IsConfig.ini SUCCESS Offset: 0, Length: 4,294,967,295
12:04:03.0908928 AM setup.exe 3668 CloseFile C:\Users\Client\AppData\Local\Temp\{37626276-B7B7-4EED-818A-F1BE8ED40A2A}\IsConfig.ini SUCCESS
12:04:03.0910342 AM setup.exe 3668 CloseFile C:\Users\Client\AppData\Local\Temp\issDDD9.tmp SUCCESS
12:04:03.0914248 AM setup.exe 3668 CreateFile C:\Users\Client\AppData\Local\Temp\{42F97B6F-1E30-415A-A1A1-C363702B140E} SUCCESS Desired Access: Read Data/List Directory, Synchronize, Disposition: Create, Options: Directory, Synchronous IO Non-Alert, Open Reparse Point, Attributes: N, ShareMode: Read, Write, AllocationSize: 0, OpenResult: Created
12:04:03.0918120 AM Explorer.EXE 320 NotifyChangeDirectory C:\Users\Client\AppData\Local\Temp SUCCESS Filter: FILE_NOTIFY_CHANGE_DIR_NAME
12:04:03.0922202 AM Explorer.EXE 320 NotifyChangeDirectory C:\Users\Client\AppData\Local SUCCESS Filter: FILE_NOTIFY_CHANGE_FILE_NAME, FILE_NOTIFY_CHANGE_ATTRIBUTES, FILE_NOTIFY_CHANGE_LAST_WRITE
12:04:03.0932159 AM setup.exe 3668 CloseFile C:\Users\Client\AppData\Local\Temp\{42F97B6F-1E30-415A-A1A1-C363702B140E} SUCCESS
12:04:03.0936920 AM setup.exe 3668 CreateFile C:\Users\Client\AppData\Local\Temp\{8D2C264F-648C-4E84-8415-1D6C6F5F79D4}\_ISMSIDEL.INI NAME NOT FOUND Desired Access: Generic Read, Disposition: Open, Options: Synchronous IO Non-Alert, Non-Directory File, Disallow Exclusive, Attributes: R, ShareMode: Read, AllocationSize: n/a
12:04:03.0940746 AM setup.exe 3668 CreateFile C:\Users\Client\AppData\Local\Temp\{8D2C264F-648C-4E84-8415-1D6C6F5F79D4}\_ISMSIDEL.INI SUCCESS Desired Access: Generic Write, Read Attributes, Disposition: OverwriteIf, Options: Synchronous IO Non-Alert, Non-Directory File, Disallow Exclusive, Attributes: N, ShareMode: Read, AllocationSize: 0, OpenResult: Created
12:04:03.0946678 AM Explorer.EXE 320 NotifyChangeDirectory C:\Users\Client\AppData\Local\Temp SUCCESS Filter: FILE_NOTIFY_CHANGE_FILE_NAME, FILE_NOTIFY_CHANGE_ATTRIBUTES, FILE_NOTIFY_CHANGE_LAST_WRITE
12:04:03.0948752 AM setup.exe 3668 WriteFile C:\Users\Client\AppData\Local\Temp\{8D2C264F-648C-4E84-8415-1D6C6F5F79D4}\_ISMSIDEL.INI SUCCESS Offset: 0, Length: 2, Priority: Normal
12:04:03.0950543 AM setup.exe 3668 WriteFile C:\Users\Client\AppData\Local\Temp\{8D2C264F-648C-4E84-8415-1D6C6F5F79D4}\_ISMSIDEL.INI SUCCESS Offset: 2, Length: 22, Priority: Normal
12:04:03.0951580 AM setup.exe 3668 WriteFile C:\Users\Client\AppData\Local\Temp\{8D2C264F-648C-4E84-8415-1D6C6F5F79D4}\_ISMSIDEL.INI SUCCESS Offset: 24, Length: 228, Priority: Normal
12:04:03.0952210 AM setup.exe 3668 CloseFile C:\Users\Client\AppData\Local\Temp\{8D2C264F-648C-4E84-8415-1D6C6F5F79D4}\_ISMSIDEL.INI SUCCESS
12:04:03.0957128 AM setup.exe 3668 CreateFile C:\Users\Client\AppData\Local\Temp\issDDD9.tmp SUCCESS Desired Access: Generic Read, Disposition: Open, Options: Synchronous IO Non-Alert, Non-Directory File, Disallow Exclusive, Attributes: N, ShareMode: Read, AllocationSize: n/a, OpenResult: Opened
12:04:03.0958136 AM setup.exe 3668 CreateFileMapping C:\Users\Client\AppData\Local\Temp\issDDD9.tmp FILE LOCKED WITH ONLY READERS SyncType: SyncTypeCreateSection, PageProtection: PAGE_READONLY
12:04:03.0958312 AM setup.exe 3668 QueryStandardInformationFile C:\Users\Client\AppData\Local\Temp\issDDD9.tmp SUCCESS AllocationSize: 4,407,296, EndOfFile: 4,406,977, NumberOfLinks: 1, DeletePending: False, Directory: False
12:04:03.0958673 AM setup.exe 3668 CreateFileMapping C:\Users\Client\AppData\Local\Temp\issDDD9.tmp SUCCESS SyncType: SyncTypeOther
12:04:03.0959595 AM setup.exe 3668 CloseFile C:\Users\Client\AppData\Local\Temp\issDDD9.tmp SUCCESS
12:04:03.0963351 AM setup.exe 3668 CreateFile C:\Users\Client\AppData\Local\Temp\issDDD9.tmp SUCCESS Desired Access: Generic Read, Disposition: Open, Options: Synchronous IO Non-Alert, Non-Directory File, Disallow Exclusive, Attributes: N, ShareMode: Read, Write, AllocationSize: n/a, OpenResult: Opened
12:04:03.0964250 AM setup.exe 3668 ReadFile C:\Users\Client\AppData\Local\Temp\issDDD9.tmp SUCCESS Offset: 604,160, Length: 46, Priority: Normal
12:04:03.0965197 AM setup.exe 3668 ReadFile C:\Users\Client\AppData\Local\Temp\issDDD9.tmp SUCCESS Offset: 604,206, Length: 24
12:04:03.0965581 AM setup.exe 3668 ReadFile C:\Users\Client\AppData\Local\Temp\issDDD9.tmp SUCCESS Offset: 604,230, Length: 18
12:04:03.0965942 AM setup.exe 3668 ReadFile C:\Users\Client\AppData\Local\Temp\issDDD9.tmp SUCCESS Offset: 791,435, Length: 24
12:04:03.0966269 AM setup.exe 3668 ReadFile C:\Users\Client\AppData\Local\Temp\issDDD9.tmp SUCCESS Offset: 791,459, Length: 16
12:04:03.0966601 AM setup.exe 3668 ReadFile C:\Users\Client\AppData\Local\Temp\issDDD9.tmp SUCCESS Offset: 1,077,291, Length: 24
12:04:03.0967052 AM setup.exe 3668 ReadFile C:\Users\Client\AppData\Local\Temp\issDDD9.tmp SUCCESS Offset: 1,077,315, Length: 24
12:04:03.0967404 AM setup.exe 3668 ReadFile C:\Users\Client\AppData\Local\Temp\issDDD9.tmp SUCCESS Offset: 1,155,287, Length: 24
12:04:03.0967657 AM setup.exe 3668 ReadFile C:\Users\Client\AppData\Local\Temp\issDDD9.tmp SUCCESS Offset: 1,155,311, Length: 24
12:04:03.0967993 AM setup.exe 3668 ReadFile C:\Users\Client\AppData\Local\Temp\issDDD9.tmp SUCCESS Offset: 1,291,348, Length: 24
12:04:03.0968252 AM setup.exe 3668 ReadFile C:\Users\Client\AppData\Local\Temp\issDDD9.tmp SUCCESS Offset: 1,291,372, Length: 34
12:04:03.0968614 AM setup.exe 3668 ReadFile C:\Users\Client\AppData\Local\Temp\issDDD9.tmp SUCCESS Offset: 1,453,129, Length: 24
12:04:03.0968931 AM setup.exe 3668 ReadFile C:\Users\Client\AppData\Local\Temp\issDDD9.tmp SUCCESS Offset: 1,453,153, Length: 34
12:04:03.0969270 AM setup.exe 3668 ReadFile C:\Users\Client\AppData\Local\Temp\issDDD9.tmp SUCCESS Offset: 1,615,039, Length: 24
12:04:03.0969558 AM setup.exe 3668 ReadFile C:\Users\Client\AppData\Local\Temp\issDDD9.tmp SUCCESS Offset: 1,615,063, Length: 34
12:04:03.0969929 AM setup.exe 3668 ReadFile C:\Users\Client\AppData\Local\Temp\issDDD9.tmp SUCCESS Offset: 1,780,723, Length: 24
12:04:03.0970204 AM setup.exe 3668 ReadFile C:\Users\Client\AppData\Local\Temp\issDDD9.tmp SUCCESS Offset: 1,780,747, Length: 34
12:04:03.0970578 AM setup.exe 3668 ReadFile C:\Users\Client\AppData\Local\Temp\issDDD9.tmp SUCCESS Offset: 1,947,027, Length: 24
12:04:03.0970879 AM setup.exe 3668 ReadFile C:\Users\Client\AppData\Local\Temp\issDDD9.tmp SUCCESS Offset: 1,947,051, Length: 34
12:04:03.0971253 AM setup.exe 3668 ReadFile C:\Users\Client\AppData\Local\Temp\issDDD9.tmp SUCCESS Offset: 2,146,494, Length: 24
12:04:03.0971845 AM setup.exe 3668 ReadFile C:\Users\Client\AppData\Local\Temp\issDDD9.tmp SUCCESS Offset: 2,146,518, Length: 34
12:04:03.0972226 AM setup.exe 3668 ReadFile C:\Users\Client\AppData\Local\Temp\issDDD9.tmp SUCCESS Offset: 2,312,305, Length: 24
12:04:03.0972492 AM setup.exe 3668 ReadFile C:\Users\Client\AppData\Local\Temp\issDDD9.tmp SUCCESS Offset: 2,312,329, Length: 34
12:04:03.0972901 AM setup.exe 3668 ReadFile C:\Users\Client\AppData\Local\Temp\issDDD9.tmp SUCCESS Offset: 2,479,368, Length: 24

.......


Does anyone has any idea on this or how to avoid these extra operations in IS 2014.

Thanks.

Prevent 64 bits installer to start on 32 bits platform

$
0
0
Hi,
We have an installer dedicated to 64 bits OS (done with IA 2008).
We bundle a 64 bits VM with the installer, that will be installed and used by our application.

If we launch this installer on 32 bits, we have the error message "Windows error 216 occured while loading the java VM".
I would like replace this error by a clearer message like "System architecture not supported".

I didn't find how to do add a system architecture check: the error appears before the real installer starting...
Does someone have a solution?
Thanks in advance
Nathalie

Running custom action executable

$
0
0
Hi.

For a variety of reasons, my installation package needs the "Required execution level" parameter to be set at Administrator execution level. However, I also need to run some custom action executables which are compiled at Invoker level. My problem is that when the package is executed, it runs these custom action executables at Administrator level even though they do not require it. This changes the behavior of the executables (e.g. on Windows 8, due to the File system redirector and the default disabling of the EnableLinkedConnections parameter in the system registry).

Is there a way to indicate that a custom action executable should be run at different execution level?

Thanks!

Cannot open Dynamic Link Dialog

$
0
0
Hello,

newly I have the problem, that I cannot open the dynamic link dialog anymore.
Can someone help?

Regards,

Christian

Suppress errors in Chained Msi

$
0
0
Hello,

I want to use chained msi to install the SQL Server Client.
When on the targetsystem is a newer version installed, the complete Installation breaks.
The Install condition I use is "Not Installed AND VersionNT64" in case of Installation on 64 bit systems
and "Not Installed AND Not VersionNT64" for the 32 bit version

How can I prevent the complete Installation from breaking down the installation when there is only a newer version (which is probably OK)?

Regards,

Christian

MSOFFICE version in Installation Requirements

$
0
0
I have a VB.NET application that uses the MS Office PIA. The program has been tested with both Office 2010 and Office 2013. In the Installation Requirements list of products, only Office 2010 is shown, and the text to display if not present is: Microsoft Office 2010 or greater needs to be installed for this installation to continue.

With Office 2013 present and not Office 2010, the message appears even though Office 2013 is greater than Office 2010. When I look at the Installation Designer / General Information / Install Conditions, I see MSOFFICE2010. I don't know what should be there in order to check for 2010 or greater, nor how to put the check into the condition properties when it is expanded. Can anyone help me to modify this to allow the installation for either MSOFFICE 2010 or 2013? I also notice that MS Office 2013 is not an option in the selection list when using the Installation Requirements list of products.

Another version of this product is already installed. ...

$
0
0
I created my VS 2013 application and added the InstallShield project to the solution. I created an installer, which works fine for the initial install. If I rebuild the InstallShield project and run setup.exe a 2nd time, I get "Another version of this product is already installed" error message. Rebuilding the project changes the package code, and because the product version, product code, and upgrade code remain the same, the new setup.exe (with new package code) should execute without this error. What am I missing? Does the InstallShield LE with VS 2013 have a limitation? I have tried setting upgrade paths and removed prevent downgrades, which didn't help.

If the application is already installed, I want the installer to overwrite the existing files and not add a 2nd entry into the add/remove programs.

Unable to minor Upgrade having Merge module Jre with Dynamic Linking

$
0
0
Hello,

I have Basic Msi project which contains Jre as Merge Module. In previous release in Jre Merge module i have done done dynamic linking addressing folder of Jre 1.7 _55 (which is around 123mb)
Now in next release i am using Jre1.8_11 (125mb) binaries. Obviously there are lot of changes in the previous Jre 1.7 and Jre 1.8 , some files and folders are removed and modified etc.
So this time, same structure, component i am using in merge module and basic msi. This time Dynamic linking is adressing to Jre1.8_11.
But Minor Upgrade of Basic Msi is not working at all. It is not updating any file from Jre 1.7_55 to Jre 1.8_11.
Has anybody used Jre merge module or faced this problem then pls let me know the solution.

Thanks
Gunjan

Passing Values from Advanced UI to Package

$
0
0
Hi,

I have an Advanced UI project and I want to pass three values in an on click event (button) to my install package which is an MSI. I see the set propertyin the on click actions but this won't actually pass the values into the MSI I want to run.

Could some give me some suggestions as to how to do this?

Cheers

set minimum space check in installation

$
0
0
Hi,

I am using Install Shield Express Edition 2013.
I have created a setup with following steps-
install welcome>license agreement>destination folder>setup progress>setup complete success.
Now when i reach destination folder window, disk out of space message/dialog in not prompting, if the drive i select for installation in full.Though i am not able to proceed to next window on click of 'Next', but no space alert is not showing up.

Can anybody please help on this?Do i have to write any custom action on it?

Thanks

Shortcut not added to Mac OSX Dock

Is there a limitation on the number of Ethernet interfaces that lmhostid will detect?

$
0
0
I have set up a virtual machine in our private cloud to serve as our license server. I have set up 16 virtual NICs on this VM, i.e. eth0, eth1...eth15.

I have a valid FlexLM license file that matches the MAC/hostid on eth2, and that license server is working properly and can serve licenses.

When I issue the command "lmhostid" on this VM i receive the following output.

[jmarcedwards@890fafa6-00fe-ea3e-d161-cf87e6329f54 bin]$ lmhostid
lmhostid - Copyright (c) 1989-2011 Flexera Software, Inc. All Rights Reserved.
The FLEXnet host ID of this machine is ""90b8d0f5c245 90b8d0b02466 90b8d035643d 90b8d07115ce 90b8d03c1c3b 90b8d09e78f9 90b8d0c0899a 90b8d03b6bbe 90b8d048b894 90b8d0c5b0b1""
Only use ONE from the list of hostids.
[jmarcedwards@890fafa6-00fe-ea3e-d161-cf87e6329f54 bin]$

Note that ONLY eth0-eth9 (the first 10 Ethernet interfaces) are listed. eth10-eth15 are not listed.

I'm suspicious that there is a limitation on the number of interfaces that can be on a FlexLM server. I'm suspicious that if I tried to use the eth10-eth15 interfaces, that lmgrd would not serve these licenses.

Any thoughts>

Kind regards, Marc

RegDBKeyExist / Registry strangeness

$
0
0
I'm totally stumped on this one. I was creating a prerequisite for these drivers but it would keep prompting to install even if it was there. So I tried RegDBKeyExist in the Installscript and it wouldn't find it either. The odd part is if I create a value in the registry location I'm testing for RegDBSetKeyValueEx will report success but the value never appears. However then RegDBKeyExist will find the registry key. I tried to catch an error code but all it gives me is -1. If I take the DBSetkey out then the DBKeyExist fails again. Has anyone encountered this before cause I'm pulling out my hair now!

This is the registry key I'm looking for:
sRegKey = "SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Uninstall\\B97004A400E30DCF940971EFA7A0C13C6B0A4B66";

The target machine is Win7 64bit. The above registry key only exists in this one location under HKLM and not under the Wow6432node. I even created a string value in the key above by hand and RegDBGetKeyValueEx fails to find it no matter what. To make things stranger I tried checking for registry keys above and below the one above.

sRegKey = "SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Uninstall\\{FBD367D1-642F-47CF-B79B-9BE48FB34007}"; RegDBKeyExist won't find it.

sRegKey = "SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Uninstall\\AddressBook"; RegDBKeyExist finds it.

The other odd thing is the installer for this driver doesn't even see itself. I can run the installer over and over and it will always want to install even if it is already.

Please help me return to sanity. Thx!!!

jeff:confused:

Crash in ISSetup.dll during installation

$
0
0
I have "Installshield 2013 - Professional edition". Created project with "InstallScript MSI Project". During installation setup is crashing in ISSetup.dll module. This happens as soon as installScript engine starts. It is happening on Windows Server 2008 R2. Here is the stack.

0018b584 10079afc 00000001 0f208f5f 028011f0 ISSetup!DllUnregisterServer+0x71000
0018b668 1007af11 ffffffff 00000000 00000000 ISSetup!DllUnregisterServer+0x71b8f
0018b83c 76ecf3bf 00000003 00000000 00000002 ISSetup!DllUnregisterServer+0x72fa4
0018b858 76ecf422 00000040 00000000 00000000 ntdll!RtlDosApplyFileIsolationRedirection_Ustr+0x435
0018b8fc 76ecf1e1 0018b930 0018bae4 0018bca8 ntdll!RtlDosApplyFileIsolationRedirection_Ustr+0x498
0018baf0 00420045 00390042 00310034 0030002d ntdll!RtlDosApplyFileIsolationRedirection_Ustr+0x257

Here is the module detail.
Loaded symbol image file: ISSetup.dll
Image path: C:\Windows\Temp\{E481F3FF-3701-44A3-A899-1FBA057545AB}\ISSetup.dll
Image name: ISSetup.dll
Timestamp: Thu May 30 09:19:45 2013 (51A6CC59)
CheckSum: 001623DC
ImageSize: 00167000
File version: 20.0.0.376
Product version: 20.0.0.0
File flags: 1 (Mask 3F) Debug
File OS: 40004 NT Win32
File type: 1.0 App
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: Flexera Software LLC
ProductName: InstallShield
InternalName: Kernel
OriginalFilename: iKernel.dll
ProductVersion: 20.0
FileVersion: 20.0.376
FileDescription: InstallShield (R) Setup Engine
LegalCopyright: Copyright (c) 2013 Flexera Software LLC. All Rights Reserved.

I tried upgrading this to SP1 but that did not solve the problem. What can I do? How to debug this issue?

-vikas

Adobe Reader 11.0.08 Upgrade

$
0
0
Hi All,

I am in the process of an upgrade package for Reader 11.0.08.

I have created the package and it installs fine.

However, even though I have used the Adobe Customization Wizard, the installer will still not remove the 11.0.07 product.

So, when I go into Control Panal > Programs I see two versions.

I am sure it's a simple setting within the MSI, but I am not sure where to find it.

Thanks!

DeleteDir does not remove the target dir completely

$
0
0
DeleteDir does not remove the target dir completely. It is not a root dir, not in the current dir or does not have readonly files.
Can someone help?

IVsQueryEditQuerySave2::QueryEditFiles() is not called

$
0
0
While editing any file, IVsQueryEditQuerySave2::QueryEditFiles() should be called so that source control plugins can make the necessary arrangements (like checkout the file).

But it seems that this API is not getting called even if user tries to edit the .isl file or .csproj file.

This causes all the source control operation to fail and hence any user who is using Installshield in VS2012/VS2013 is not able to manage his code in source control repository.

Could you please confirm if its a bug and something which can be fixed?

Thanks and Regards,
Ganesh Agrawal

Custom Action does not work on XP after upgrade to 2014

$
0
0
Upgraded an InstallShield 2012 project to 2014. I am experiencing a custom action failing with a return value 3 on two XP machines but it works on a Windows 7 and a 2008R2. The custom action is written in C++ and we've been using it without incident for many years. One difference is the custom action code has been upgraded from VS2008 to VS2012. I've suspected a VS2013 dependency exists but dependency walker does not show any such dependencies. Any thoughts on what could be happening is most appreciated.

Cannot create app pool in Server 2008 R2

$
0
0
I built an install package that creates a web app with app pool. If I run the install on Windows Server 2012, it completes without any problems. If I run it on Windows Server 2008 R2, it fails when creating the AppPool.

Below is the relevant section of the msi log.



Action 15:52:32: ISIISInstall.
MSI (s) (58:AC) [15:52:32:477]: Executing op: CustomActionSchedule(Action=ISIISInstall,ActionType=3073,Source=BinaryData,Target=ISIISInstall,CustomActionData=C:\Users\demenyjo\AppData\Local\Temp\IIS7739.tmp)
MSI (s) (58:98) [15:52:32:482]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI794B.tmp, Entrypoint: ISIISInstall
MSI (s) (58:14) [15:52:32:482]: Generating random cookie.
MSI (s) (58:14) [15:52:32:485]: Created Custom Action Server with PID 4248 (0x1098).
MSI (s) (58:80) [15:52:32:549]: Running as a service.
MSI (s) (58:80) [15:52:32:552]: Hello, I'm your 32bit Elevated custom action server.
InstallShield 15:52:32: User legacy object preference is the following: . This is based on the value of the following property: IISPREFERLEGACYOBJECTS
InstallShield 15:52:32: InitIISObject
InstallShield 15:52:32: Legacy objects are supported
Action 15:52:32: Progress Custom Action.
Action 15:52:32: Progress Custom Action. Creating application pool MyAppPool
InstallShield 15:52:32: CreateAppPoolFunction
InstallShield 15:52:32: GetAdminSection for section 'system.applicationHost/applicationPools' and path 'MACHINE/WEBROOT/APPHOST' and commitpath 'MACHINE/WEBROOT/APPHOST'.
InstallShield 15:52:32: GetAdminSection returned: -2147024846
InstallShield 15:52:32: Error: already using the main configuration file.
InstallShield 15:52:32: Parent element is NULL while searching collection
InstallShield 15:52:32: AppPool does not exist, attempt to create it.
InstallShield 15:52:32: GetAdminSection for section 'system.applicationHost/applicationPools' and path 'MACHINE/WEBROOT/APPHOST' and commitpath 'MACHINE/WEBROOT/APPHOST'.
InstallShield 15:52:32: GetAdminSection returned: -2147024846
InstallShield 15:52:32: Error: already using the main configuration file.
InstallShield 15:52:32: Element is NULL. Can't get collection
InstallShield 15:52:32: Collection is NULL. CreateNewElement failed for: add
InstallShield 15:52:32: PutPropertyValue: sProperty name sValue MyAppPool bIsPath 0
InstallShield 15:52:32: PutPropertyCommon: sProperty name sValue MyAppPool bIsPath 0
InstallShield 15:52:32: Element is NULL while looking for the following property: name
InstallShield 15:52:32: PutPropertyCommon: no property returned for name, don't try to set it now
InstallShield 15:52:32: spCollection NULL in CIisFunctionsVista::AddElement.
InstallShield 15:52:32: pElement NULL in CIisFunctionsVista::AddElement
CustomAction ISIISInstall returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
Action ended 15:52:32: InstallFinalize. Return value 3.
Viewing all 4553 articles
Browse latest View live