I'm using Installshield2009. I want to set ALLUSERS property to per-machine, but I've went step by step, don't know where and how to set this property. Can someone help me please?
Thank you very much!
Thank you very much!
↧
How to set ALLUSERS prpperty to per-machine
↧
Unable to load project file in IA 2014
I have attached the screen shot of the same.
IAScript,loadScript exception thrown.
Kindly help in resolving this issue.
The same project I amable to laod on IA2012.. But 2014 is giving a problem
IAScript,loadScript exception thrown.
Kindly help in resolving this issue.
The same project I amable to laod on IA2012.. But 2014 is giving a problem
↧
↧
Query Regarding InstallSheild 2015
We are installing a windows service and then after its installation we are running a third party exe/msi and at the same time CompleteSuccessful Dailog appears.
We are looking for the main setup.exe to wait for the third party exe/MSi to get installed and afterwards show the CompleteSuccessful Dailog.
We are looking for the main setup.exe to wait for the third party exe/MSi to get installed and afterwards show the CompleteSuccessful Dailog.
↧
Enable/open outbound firewall ports using powershell script
We have created powershell script to open/enable outbound firewall ports instead of executing .bat file using Installshield 2015 professional edition. When we execute .bat file it will command prompt(i.e. Black window). We have created powershell script to hide command prompt window. But, rules are not created in outbound it always created in inbound rules.
Could you please anyone tell me how to created outbound ports using powershell script?
Thanks
Could you please anyone tell me how to created outbound ports using powershell script?
Thanks
↧
Config File not replacing while upgrade
Hi ,
We have created a Installscript MSI project, the version of the setup is 1.0.1.0 and it has two dlls with version 1.0.1.0 and a config file.
Now we made some content changes to that config file and build that setup with version 1.0.2.0 and the dlls versioned to 1.0.2.0, but nothing we changed to the functionality related to these dlls.
Now while upgrading from 1.0.1.0 to 1.0.2.0 the config file is not replacing while upgradation, we can see the old stuff in that config file even the dlls got replaced .
Can anyone tell me why the config file is not getting upgraded? And what we need to do to replace the config file while upgradation.
Regards,
K V Suresh
We have created a Installscript MSI project, the version of the setup is 1.0.1.0 and it has two dlls with version 1.0.1.0 and a config file.
Now we made some content changes to that config file and build that setup with version 1.0.2.0 and the dlls versioned to 1.0.2.0, but nothing we changed to the functionality related to these dlls.
Now while upgrading from 1.0.1.0 to 1.0.2.0 the config file is not replacing while upgradation, we can see the old stuff in that config file even the dlls got replaced .
Can anyone tell me why the config file is not getting upgraded? And what we need to do to replace the config file while upgradation.
Regards,
K V Suresh
↧
↧
Messagebox hidden by Wizard-Dialog
(Installshield 2014 Suite-Project)
I'm using a powershell-Action to pop up a MessageBox. The Action is scheduled under OnPackagesConfiguring.
The MessageBox is indeed opened - BUT it is hidden by the Wizard-Dialog (Installation Progress).
(Note: in my simple test the PS-Action does nothing more than showing a MessageBox)
Any help will be greatly appreciated.
I'm using a powershell-Action to pop up a MessageBox. The Action is scheduled under OnPackagesConfiguring.
The MessageBox is indeed opened - BUT it is hidden by the Wizard-Dialog (Installation Progress).
(Note: in my simple test the PS-Action does nothing more than showing a MessageBox)
Any help will be greatly appreciated.
↧
service with the start type of "Delayed Start" is not working
Hi All
I have Basic MSI which installs Windows Service.
I followed this thread to set it as "Delayed Start": How can I install a service with the start type of "Delayed Start"
It works on Windows 7 (my machine) and Windows 2012 but it's not working on Windows 2008 SP2
Did anyone else come across this issue before?
Any insight what could be the issue would be appreciated.
I am attaching install log below.
SchedSvcInstall.log
I have Basic MSI which installs Windows Service.
I followed this thread to set it as "Delayed Start": How can I install a service with the start type of "Delayed Start"
It works on Windows 7 (my machine) and Windows 2012 but it's not working on Windows 2008 SP2
Did anyone else come across this issue before?
Any insight what could be the issue would be appreciated.
I am attaching install log below.
SchedSvcInstall.log
↧
Suite: Show progress when custom action executes
I have a suite project that, when the user is doing an upgrade, checks SQL for a value when the user clicks on one of the Next buttons. The flow control of the wizard pages is based on this check.
Is there a way to show some type of status indicating that it is checking practice information and a wait icon while the code executes?
So the flow control goes like this, just in case it helps:
Install Welcome > License Agreement > Destination > SQL Options (INSERT C# custom action here if upgrade) > Support License (if upgrade and CA indicates customer maintenance license has expired) > Ready To Install
Thanks.
Is there a way to show some type of status indicating that it is checking practice information and a wait icon while the code executes?
So the flow control goes like this, just in case it helps:
Install Welcome > License Agreement > Destination > SQL Options (INSERT C# custom action here if upgrade) > Support License (if upgrade and CA indicates customer maintenance license has expired) > Ready To Install
Thanks.
↧
Suite Behavior
I am attempting to use a Suite project to create a single experience for uninstalling the currently installed packages of my Suite and reinstall the new packages (up to 4). (Lets disregard Upgrades for the moment… I will do that later. For now I need to uninstall some older versions). As suggested by Dlee65 on the 2013 forum, I have implemented Suite Actions to do the uninstall. The action is typically
C:\Program Files (x86)\InstallShield Installation Information\[ProductCodeMyProduct]\Setup.exe
With an argument of –uninst
I execute the Suite Actions on ‘Page Entered’ of a Wizard Page. This sort of works. I say sort of because if I put multiple Suite actions on a page it will only wait for the first one to complete before moving on to the next page. Seems like it should wait for each one in succession. So I made separate Wizard Pages for each package. It will uninstall the first 2 and then not proceed to the next page. If I cancel and restart it correctly proceeds to the third Wizard page and uninstalls the 3rd and 4th packages and hangs on the page for the 4th package. Can someone explain the flow of execution of a Suite? Is there a better way to do this? Even when I do get all the packages to uninstall it seems like I might have trouble switching from Maintenance mode to Install mode after Staging has been done???? Is there a way to basically direct the flow back to the beginning?
Thanks!
C:\Program Files (x86)\InstallShield Installation Information\[ProductCodeMyProduct]\Setup.exe
With an argument of –uninst
I execute the Suite Actions on ‘Page Entered’ of a Wizard Page. This sort of works. I say sort of because if I put multiple Suite actions on a page it will only wait for the first one to complete before moving on to the next page. Seems like it should wait for each one in succession. So I made separate Wizard Pages for each package. It will uninstall the first 2 and then not proceed to the next page. If I cancel and restart it correctly proceeds to the third Wizard page and uninstalls the 3rd and 4th packages and hangs on the page for the 4th package. Can someone explain the flow of execution of a Suite? Is there a better way to do this? Even when I do get all the packages to uninstall it seems like I might have trouble switching from Maintenance mode to Install mode after Staging has been done???? Is there a way to basically direct the flow back to the beginning?
Thanks!
↧
↧
Mulitple patches problem
Hi,
I'm trying to generate an msp out of the latest and previous msis as below scenario:
The problem is that we are getting an error when trying to install the second msp saying: Un-installation of the package is not supported.
And below is the error log:
**************************************
MSI (s) (78:EC) [07:57:01:214]: Final Patch Application Order:
MSI (s) (78:EC) [07:57:01:214]: {C39177DC-24FD-432E-9D50-159E7E3CC62C} - C:\temp\Agilis EmPower SBSA.msp
MSI (s) (78:EC) [07:57:01:214]: Other Patches:
MSI (s) (78:EC) [07:57:01:214]: Unknown\Absent: {9BEBFF56-7735-4618-BF01-01E96548FA81} -
MSI (s) (78:EC) [07:57:01:214]: Product: Agilis EmPower SBSA - Update 'Agilis EmPower SBSA' could not be removed. Error code 1646.
Additional information is available in the log file C:\Users\Administrator\Desktop\msp.log.
MSI (s) (78:EC) [07:57:01:214]: Windows Installer removed an update. Product Name: Agilis EmPower SBSA. Product Version: 1.3.0.0.81.159. Product Language: 1033.
Manufacturer: Diebold. Update Name: Agilis EmPower SBSA. Removal success or error status: 0.
MSI (s) (78:EC) [07:57:01:214]: Product: Agilis EmPower SBSA - Update '{C39177DC-24FD-432E-9D50-159E7E3CC62C}' could not be installed. Error code 1646.
Additional information is available in the log file C:\Users\Administrator\Desktop\msp.log.
MSI (s) (78:EC) [07:57:01:214]: Windows Installer installed an update. Product Name: Agilis EmPower SBSA. Product Version: 1.3.0.0.81.159. Product Language: 1033.
Manufacturer: Diebold. Update Name: {C39177DC-24FD-432E-9D50-159E7E3CC62C}. Installation success or error status: 1646.
MSI (s) (78:EC) [07:57:01:214]: Product: Agilis EmPower SBSA -- Installation failed.
MSI (s) (78:EC) [07:57:01:214]: Windows Installer installed the product. Product Name: Agilis EmPower SBSA. Product Version: 1.3.0.0.81.159. Product Language: 1033.
Manufacturer: Diebold. Installation success or error status: 1646.
Uninstallation of the update package is not supported.
C:\Windows\Installer\5d9684f.msi
********************************************
So is this allowed to do? or do we have to change the previous msi on each msp installation so we keep the each msp with distinct files only?
Thank you.
I'm trying to generate an msp out of the latest and previous msis as below scenario:
- The previous MSI is fixed as used as a basleline
- The latest msi is generated with the new modification on the files included everynight and and it will get a new ProductVersion on every generation (which happens with every build on the server)
- The previous msi that is the baseline is installed on the machine let's say it version 1.0.0.0
- The msp generated on the first build is installed successfully, now the product version 1.0.0.1
- The latest msi now is 1.0.0.2 and has new modifications in it and we want to generate a new msp to get those modifications to the machine, the msp is generated based on the difference between previous msi 1.0.0.0 and latest which is now 1.0.0.2.
The problem is that we are getting an error when trying to install the second msp saying: Un-installation of the package is not supported.
And below is the error log:
**************************************
MSI (s) (78:EC) [07:57:01:214]: Final Patch Application Order:
MSI (s) (78:EC) [07:57:01:214]: {C39177DC-24FD-432E-9D50-159E7E3CC62C} - C:\temp\Agilis EmPower SBSA.msp
MSI (s) (78:EC) [07:57:01:214]: Other Patches:
MSI (s) (78:EC) [07:57:01:214]: Unknown\Absent: {9BEBFF56-7735-4618-BF01-01E96548FA81} -
MSI (s) (78:EC) [07:57:01:214]: Product: Agilis EmPower SBSA - Update 'Agilis EmPower SBSA' could not be removed. Error code 1646.
Additional information is available in the log file C:\Users\Administrator\Desktop\msp.log.
MSI (s) (78:EC) [07:57:01:214]: Windows Installer removed an update. Product Name: Agilis EmPower SBSA. Product Version: 1.3.0.0.81.159. Product Language: 1033.
Manufacturer: Diebold. Update Name: Agilis EmPower SBSA. Removal success or error status: 0.
MSI (s) (78:EC) [07:57:01:214]: Product: Agilis EmPower SBSA - Update '{C39177DC-24FD-432E-9D50-159E7E3CC62C}' could not be installed. Error code 1646.
Additional information is available in the log file C:\Users\Administrator\Desktop\msp.log.
MSI (s) (78:EC) [07:57:01:214]: Windows Installer installed an update. Product Name: Agilis EmPower SBSA. Product Version: 1.3.0.0.81.159. Product Language: 1033.
Manufacturer: Diebold. Update Name: {C39177DC-24FD-432E-9D50-159E7E3CC62C}. Installation success or error status: 1646.
MSI (s) (78:EC) [07:57:01:214]: Product: Agilis EmPower SBSA -- Installation failed.
MSI (s) (78:EC) [07:57:01:214]: Windows Installer installed the product. Product Name: Agilis EmPower SBSA. Product Version: 1.3.0.0.81.159. Product Language: 1033.
Manufacturer: Diebold. Installation success or error status: 1646.
Uninstallation of the update package is not supported.
C:\Windows\Installer\5d9684f.msi
********************************************
So is this allowed to do? or do we have to change the previous msi on each msp installation so we keep the each msp with distinct files only?
Thank you.
↧
installation of microsoft visual c++ 2005 sp1 redistributable appears to have failed
We met a problem:
The installation of microsoft visual c++ 2005 sp1 redistributable package (x86) appears to have failed....
Background:
1) Old machine, WinXP + InstallShield 2012Spring
2) Currently we did upgrade: New machine, Win7 + InstallShield 2013.
3) We have an installer project in old machine, and In Redistributables, the "Microsoft Visual C++ 2005 SP1 Redistributable package (x86)" was checked.
4) Copied the installer project from old machine to new machine. Nothing change, just upgrade to 2013.
Test steps:
1) Make our installer in new machine. try to install it in a refresh PC.
2) The installer prompt a dialog, let you to install the "Visual C++ 2005 SP1 Redistributable package".
3) Click install, but the error message will be displayed.
But, in fact, it is installed okay, see screen shot below.
![Name: Install2013.jpg
Views: 27
Size: 129.6 KB]()
Above is the first problem.
The second one is:
1) Re-test. Install it from [ISSetupPrequisites] (vcredist_x86.exe), it will be installed successfully.
2) Then double click our installer.
3) It will popup say you need to install [Visual C++ 2005 SP1 Redistributable package]. But I already installed it in Step1 from [ISSetupPrequisites].
This the second problem.
If make installer in old machine. The 2 problems are not exists. It will works okay.
The installation of microsoft visual c++ 2005 sp1 redistributable package (x86) appears to have failed....
Background:
1) Old machine, WinXP + InstallShield 2012Spring
2) Currently we did upgrade: New machine, Win7 + InstallShield 2013.
3) We have an installer project in old machine, and In Redistributables, the "Microsoft Visual C++ 2005 SP1 Redistributable package (x86)" was checked.
4) Copied the installer project from old machine to new machine. Nothing change, just upgrade to 2013.
Test steps:
1) Make our installer in new machine. try to install it in a refresh PC.
2) The installer prompt a dialog, let you to install the "Visual C++ 2005 SP1 Redistributable package".
3) Click install, but the error message will be displayed.
But, in fact, it is installed okay, see screen shot below.
Above is the first problem.
The second one is:
1) Re-test. Install it from [ISSetupPrequisites] (vcredist_x86.exe), it will be installed successfully.
2) Then double click our installer.
3) It will popup say you need to install [Visual C++ 2005 SP1 Redistributable package]. But I already installed it in Step1 from [ISSetupPrequisites].
This the second problem.
If make installer in old machine. The 2 problems are not exists. It will works okay.
↧
Error 2869 while registering InterOp DLL due to use of wrong .Net framework?
A setup created with InstallShield Express 2014 gives me this error:
Error 2869. The dialog SetupError has the error style bit set, but is not an error dialog.
Doing a verbose tracing, I traced it to this error:
*****************************
MSI (s) (18:E4) [14:14:51:370]: Executing op: ActionStart(Name=_EA8D55D1504172B777FB27B5D0DD1D46.commit,,)
Actie 14:14:51: _EA8D55D1504172B777FB27B5D0DD1D46.commit.
MSI (s) (18:E4) [14:14:51:370]: Executing op: CustomActionSchedule(Action=_EA8D55D1504172B777FB27B5D0DD1D46.commit,ActionType=3585,Source=BinaryData,Target=ManagedInstall,CustomActionData=/installtype=notransaction /action=commit /LogFile= "C:\ProgramData\Network Consult\SpaceBar\FDM.Client.dll" "C:\Users\Kassa\AppData\Local\Temp\{CB395D36-8977-4984-8361-E6E734D0B3DA}\_isconfig.xml")
MSI (s) (18:E4) [14:14:51:370]: Executing op: ActionStart(Name=_EA8D55D1504172B777FB27B5D0DD1D46.rollback,,)
Actie 14:14:51: _EA8D55D1504172B777FB27B5D0DD1D46.rollback.
MSI (s) (18:E4) [14:14:51:375]: Executing op: CustomActionSchedule(Action=_EA8D55D1504172B777FB27B5D0DD1D46.rollback,ActionType=3329,Source=BinaryData,Target=ManagedInstall,CustomActionData=/installtype=notransaction /action=rollback /LogFile= "C:\ProgramData\Network Consult\SpaceBar\FDM.Client.dll" "C:\Users\Kassa\AppData\Local\Temp\{CB395D36-8977-4984-8361-E6E734D0B3DA}\_isconfig.xml")
MSI (s) (18:E4) [14:14:51:375]: Executing op: ActionStart(Name=_EA8D55D1504172B777FB27B5D0DD1D46.install,,)
Actie 14:14:51: _EA8D55D1504172B777FB27B5D0DD1D46.install.
MSI (s) (18:E4) [14:14:51:380]: Executing op: CustomActionSchedule(Action=_EA8D55D1504172B777FB27B5D0DD1D46.install,ActionType=3073,Source=BinaryData,Target=ManagedInstall,CustomActionData=/installtype=notransaction /action=install /LogFile= "C:\ProgramData\Network Consult\SpaceBar\FDM.Client.dll" "C:\Users\Kassa\AppData\Local\Temp\{CB395D36-8977-4984-8361-E6E734D0B3DA}\_isconfig.xml")
MSI (s) (18:40) [14:14:51:385]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI556A.tmp, Entrypoint: ManagedInstall
MSI (s) (18:E0) [14:14:51:385]: Generating random cookie.
MSI (s) (18:E0) [14:14:51:390]: Created Custom Action Server with PID 624 (0x270).
MSI (s) (18:94) [14:14:51:445]: Running as a service.
MSI (s) (18:94) [14:14:51:450]: Hello, I'm your 32bit Elevated Non-remapped custom action server.
MSI (c) (A4:D4) [14:14:51:475]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg
Fout 2869. In het dialoogvenster SetupError is de foutstijl ingesteld, maar dit is geen dialoogvenster met foutbericht.
MSI (c) (A4:D4) [14:15:23:226]: Product: SpaceBar GKS -- Fout 2869. In het dialoogvenster SetupError is de foutstijl ingesteld, maar dit is geen dialoogvenster met foutbericht.
Fout 1001.
MSI (s) (18!E8) [14:15:23:236]:
MSI (s) (18:40) [14:15:23:241]: Leaked MSIHANDLE (15) of type 790531 for thread 3816
MSI (s) (18:40) [14:15:23:241]: Note: 1: 2769 2: _EA8D55D1504172B777FB27B5D0DD1D46.install 3: 1
Info 2769. Aangepaste actie _EA8D55D1504172B777FB27B5D0DD1D46.install heeft 1 MSIHANDLE's niet gesloten.
CustomAction _EA8D55D1504172B777FB27B5D0DD1D46.install returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
Actie beëindigd 14:15:23: InstallFinalize. Retourwaarde 3.
MSI (s) (18:E4) [14:15:23:261]: Note: 1: 2265 2: 3: -2147287035
MSI (s) (18:E4) [14:15:23:261]: User policy value 'DisableRollback' is 0
MSI (s) (18:E4) [14:15:23:261]: Machine policy value 'DisableRollback' is 0
MSI (s) (18:E4) [14:15:23:281]: Executing op: Header(Signature=1397708873,Version=500,Timestamp=1198092761,LangId=1043,Platform=0,ScriptType=2,ScriptMajorVersion=21,ScriptMinorVersion=4,ScriptAttributes=1)
MSI (s) (18:E4) [14:15:23:281]: Executing op: DialogInfo(Type=0,Argument=1043)
MSI (s) (18:E4) [14:15:23:281]: Executing op: DialogInfo(Type=1,Argument=SpaceBar GKS)
MSI (s) (18:E4) [14:15:23:281]: Executing op: RollbackInfo(,RollbackAction=Rollback,RollbackDescription=Terugdraai-actie:,RollbackTemplate=[1],CleanupAction=RollbackCleanup,CleanupDescription=Bezig met het verwijderen van reservekopiebestanden,CleanupTemplate=Bestand: [1])
Actie 14:15:23: Rollback. Terugdraai-actie:
Rollback: _EA8D55D1504172B777FB27B5D0DD1D46.install
MSI (s) (18:E4) [14:15:23:286]: Executing op: ActionStart(Name=_EA8D55D1504172B777FB27B5D0DD1D46.install,,)
MSI (s) (18:E4) [14:15:23:286]: Executing op: ProductInfo(ProductKey={CB395D36-8977-4984-8361-E6E734D0B3DA},ProductName=SpaceBar GKS,PackageName=SpaceBar GKS.msi,Language=1043,Version=83886080,Assignment=1,ObsoleteArg=0,ProductIcon=ARPPRODUCTICON.exe,,PackageCode={F3E19353-D20D-401E-927E-CE8D601A5E80},,,InstanceType=0,LUASetting=0,RemoteURTInstalls=0,ProductDeploymentFlags=2)
Rollback: _EA8D55D1504172B777FB27B5D0DD1D46.rollback
MSI (s) (18:E4) [14:15:23:286]: Executing op: ActionStart(Name=_EA8D55D1504172B777FB27B5D0DD1D46.rollback,,)
MSI (s) (18:E4) [14:15:23:291]: Executing op: CustomActionRollback(Action=_EA8D55D1504172B777FB27B5D0DD1D46.rollback,ActionType=3329,Source=BinaryData,Target=ManagedInstall,CustomActionData=/installtype=notransaction /action=rollback /LogFile= "C:\ProgramData\Network Consult\SpaceBar\FDM.Client.dll" "C:\Users\Kassa\AppData\Local\Temp\{CB395D36-8977-4984-8361-E6E734D0B3DA}\_isconfig.xml")
MSI (s) (18:2C) [14:15:23:296]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSID21D.tmp, Entrypoint: ManagedInstall
MSI (c) (A4:D4) [14:15:23:315]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg
Fout 1001.
MSI (s) (18!FC) [14:15:24:787]:
MSI (s) (18:2C) [14:15:24:792]: Leaked MSIHANDLE (17) of type 790531 for thread 508
MSI (s) (18:2C) [14:15:24:792]: Note: 1: 2769 2: _EA8D55D1504172B777FB27B5D0DD1D46.rollback 3: 1
Info 2769. Aangepaste actie _EA8D55D1504172B777FB27B5D0DD1D46.rollback heeft 1 MSIHANDLE's niet gesloten.
CustomAction _EA8D55D1504172B777FB27B5D0DD1D46.rollback returned actual error code 1603 but will be translated to success due to continue marking
Rollback: _EA8D55D1504172B777FB27B5D0DD1D46.commit
MSI (s) (18:E4) [14:15:24:797]: Executing op: ActionStart(Name=_EA8D55D1504172B777FB27B5D0DD1D46.commit,,)
Rollback: Bezig met het schrijven van systeemregisterwaarden
**************************************
The file "C:\Users\Kassa\AppData\Local\Temp\{CB395D36-8977-4984-8361-E6E734D0B3DA}\_isconfig.xml" contains the following:
**************************
<?xml version="1.0"?>
-<configuration>
-<startup>
<supportedRuntime version="v4.6.81"/>
</startup>
</configuration>
*****************************
There is only a runtime 3.5 and 4 on the setup system, but v4.6 is installed on the system where I created the setup.
I think this is the problem!
.Net properties InstallerClass and ComInterop as both enabled on fdm.client.dll
Can I change the runtime used to register the interop of fdm.client.dll?
Or can I register it differently?
Error 2869. The dialog SetupError has the error style bit set, but is not an error dialog.
Doing a verbose tracing, I traced it to this error:
*****************************
MSI (s) (18:E4) [14:14:51:370]: Executing op: ActionStart(Name=_EA8D55D1504172B777FB27B5D0DD1D46.commit,,)
Actie 14:14:51: _EA8D55D1504172B777FB27B5D0DD1D46.commit.
MSI (s) (18:E4) [14:14:51:370]: Executing op: CustomActionSchedule(Action=_EA8D55D1504172B777FB27B5D0DD1D46.commit,ActionType=3585,Source=BinaryData,Target=ManagedInstall,CustomActionData=/installtype=notransaction /action=commit /LogFile= "C:\ProgramData\Network Consult\SpaceBar\FDM.Client.dll" "C:\Users\Kassa\AppData\Local\Temp\{CB395D36-8977-4984-8361-E6E734D0B3DA}\_isconfig.xml")
MSI (s) (18:E4) [14:14:51:370]: Executing op: ActionStart(Name=_EA8D55D1504172B777FB27B5D0DD1D46.rollback,,)
Actie 14:14:51: _EA8D55D1504172B777FB27B5D0DD1D46.rollback.
MSI (s) (18:E4) [14:14:51:375]: Executing op: CustomActionSchedule(Action=_EA8D55D1504172B777FB27B5D0DD1D46.rollback,ActionType=3329,Source=BinaryData,Target=ManagedInstall,CustomActionData=/installtype=notransaction /action=rollback /LogFile= "C:\ProgramData\Network Consult\SpaceBar\FDM.Client.dll" "C:\Users\Kassa\AppData\Local\Temp\{CB395D36-8977-4984-8361-E6E734D0B3DA}\_isconfig.xml")
MSI (s) (18:E4) [14:14:51:375]: Executing op: ActionStart(Name=_EA8D55D1504172B777FB27B5D0DD1D46.install,,)
Actie 14:14:51: _EA8D55D1504172B777FB27B5D0DD1D46.install.
MSI (s) (18:E4) [14:14:51:380]: Executing op: CustomActionSchedule(Action=_EA8D55D1504172B777FB27B5D0DD1D46.install,ActionType=3073,Source=BinaryData,Target=ManagedInstall,CustomActionData=/installtype=notransaction /action=install /LogFile= "C:\ProgramData\Network Consult\SpaceBar\FDM.Client.dll" "C:\Users\Kassa\AppData\Local\Temp\{CB395D36-8977-4984-8361-E6E734D0B3DA}\_isconfig.xml")
MSI (s) (18:40) [14:14:51:385]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI556A.tmp, Entrypoint: ManagedInstall
MSI (s) (18:E0) [14:14:51:385]: Generating random cookie.
MSI (s) (18:E0) [14:14:51:390]: Created Custom Action Server with PID 624 (0x270).
MSI (s) (18:94) [14:14:51:445]: Running as a service.
MSI (s) (18:94) [14:14:51:450]: Hello, I'm your 32bit Elevated Non-remapped custom action server.
MSI (c) (A4:D4) [14:14:51:475]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg
Fout 2869. In het dialoogvenster SetupError is de foutstijl ingesteld, maar dit is geen dialoogvenster met foutbericht.
MSI (c) (A4:D4) [14:15:23:226]: Product: SpaceBar GKS -- Fout 2869. In het dialoogvenster SetupError is de foutstijl ingesteld, maar dit is geen dialoogvenster met foutbericht.
Fout 1001.
MSI (s) (18!E8) [14:15:23:236]:
MSI (s) (18:40) [14:15:23:241]: Leaked MSIHANDLE (15) of type 790531 for thread 3816
MSI (s) (18:40) [14:15:23:241]: Note: 1: 2769 2: _EA8D55D1504172B777FB27B5D0DD1D46.install 3: 1
Info 2769. Aangepaste actie _EA8D55D1504172B777FB27B5D0DD1D46.install heeft 1 MSIHANDLE's niet gesloten.
CustomAction _EA8D55D1504172B777FB27B5D0DD1D46.install returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
Actie beëindigd 14:15:23: InstallFinalize. Retourwaarde 3.
MSI (s) (18:E4) [14:15:23:261]: Note: 1: 2265 2: 3: -2147287035
MSI (s) (18:E4) [14:15:23:261]: User policy value 'DisableRollback' is 0
MSI (s) (18:E4) [14:15:23:261]: Machine policy value 'DisableRollback' is 0
MSI (s) (18:E4) [14:15:23:281]: Executing op: Header(Signature=1397708873,Version=500,Timestamp=1198092761,LangId=1043,Platform=0,ScriptType=2,ScriptMajorVersion=21,ScriptMinorVersion=4,ScriptAttributes=1)
MSI (s) (18:E4) [14:15:23:281]: Executing op: DialogInfo(Type=0,Argument=1043)
MSI (s) (18:E4) [14:15:23:281]: Executing op: DialogInfo(Type=1,Argument=SpaceBar GKS)
MSI (s) (18:E4) [14:15:23:281]: Executing op: RollbackInfo(,RollbackAction=Rollback,RollbackDescription=Terugdraai-actie:,RollbackTemplate=[1],CleanupAction=RollbackCleanup,CleanupDescription=Bezig met het verwijderen van reservekopiebestanden,CleanupTemplate=Bestand: [1])
Actie 14:15:23: Rollback. Terugdraai-actie:
Rollback: _EA8D55D1504172B777FB27B5D0DD1D46.install
MSI (s) (18:E4) [14:15:23:286]: Executing op: ActionStart(Name=_EA8D55D1504172B777FB27B5D0DD1D46.install,,)
MSI (s) (18:E4) [14:15:23:286]: Executing op: ProductInfo(ProductKey={CB395D36-8977-4984-8361-E6E734D0B3DA},ProductName=SpaceBar GKS,PackageName=SpaceBar GKS.msi,Language=1043,Version=83886080,Assignment=1,ObsoleteArg=0,ProductIcon=ARPPRODUCTICON.exe,,PackageCode={F3E19353-D20D-401E-927E-CE8D601A5E80},,,InstanceType=0,LUASetting=0,RemoteURTInstalls=0,ProductDeploymentFlags=2)
Rollback: _EA8D55D1504172B777FB27B5D0DD1D46.rollback
MSI (s) (18:E4) [14:15:23:286]: Executing op: ActionStart(Name=_EA8D55D1504172B777FB27B5D0DD1D46.rollback,,)
MSI (s) (18:E4) [14:15:23:291]: Executing op: CustomActionRollback(Action=_EA8D55D1504172B777FB27B5D0DD1D46.rollback,ActionType=3329,Source=BinaryData,Target=ManagedInstall,CustomActionData=/installtype=notransaction /action=rollback /LogFile= "C:\ProgramData\Network Consult\SpaceBar\FDM.Client.dll" "C:\Users\Kassa\AppData\Local\Temp\{CB395D36-8977-4984-8361-E6E734D0B3DA}\_isconfig.xml")
MSI (s) (18:2C) [14:15:23:296]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSID21D.tmp, Entrypoint: ManagedInstall
MSI (c) (A4:D4) [14:15:23:315]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg
Fout 1001.
MSI (s) (18!FC) [14:15:24:787]:
MSI (s) (18:2C) [14:15:24:792]: Leaked MSIHANDLE (17) of type 790531 for thread 508
MSI (s) (18:2C) [14:15:24:792]: Note: 1: 2769 2: _EA8D55D1504172B777FB27B5D0DD1D46.rollback 3: 1
Info 2769. Aangepaste actie _EA8D55D1504172B777FB27B5D0DD1D46.rollback heeft 1 MSIHANDLE's niet gesloten.
CustomAction _EA8D55D1504172B777FB27B5D0DD1D46.rollback returned actual error code 1603 but will be translated to success due to continue marking
Rollback: _EA8D55D1504172B777FB27B5D0DD1D46.commit
MSI (s) (18:E4) [14:15:24:797]: Executing op: ActionStart(Name=_EA8D55D1504172B777FB27B5D0DD1D46.commit,,)
Rollback: Bezig met het schrijven van systeemregisterwaarden
**************************************
The file "C:\Users\Kassa\AppData\Local\Temp\{CB395D36-8977-4984-8361-E6E734D0B3DA}\_isconfig.xml" contains the following:
**************************
<?xml version="1.0"?>
-<configuration>
-<startup>
<supportedRuntime version="v4.6.81"/>
</startup>
</configuration>
*****************************
There is only a runtime 3.5 and 4 on the setup system, but v4.6 is installed on the system where I created the setup.
I think this is the problem!
.Net properties InstallerClass and ComInterop as both enabled on fdm.client.dll
Can I change the runtime used to register the interop of fdm.client.dll?
Or can I register it differently?
↧
A required process for this task failed.
Anyone seen this when trying to advance past the Target Server Details from the Application Distribution Wizard?
Looking in the log I also see this:
15:33:39 ERROR: AdminStudio.SCCM.Extension.SCCMExtensionBase.Connect - Caught Exception: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
15:33:39 ERROR: SCCMPlugin.SCCMPlugin.ConnectSccm - Caught Exception: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
Any ideas?
Looking in the log I also see this:
15:33:39 ERROR: AdminStudio.SCCM.Extension.SCCMExtensionBase.Connect - Caught Exception: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
15:33:39 ERROR: SCCMPlugin.SCCMPlugin.ConnectSccm - Caught Exception: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
Any ideas?
↧
↧
ins
Hello,
I am using IA 2014 SP1 License version for creating installer for my application. I have created installer for two locales i.e. English and Japanese. When I am trying to install it, on windows with Japanese locale, I am facing some problems, that initial screen of installer is showing correctly with Japanese text as expected, as if I proceed with first two screen using "Next" button click, 3rd screen showing in the default English language. While
I am using IA 2014 SP1 License version for creating installer for my application. I have created installer for two locales i.e. English and Japanese. When I am trying to install it, on windows with Japanese locale, I am facing some problems, that initial screen of installer is showing correctly with Japanese text as expected, as if I proceed with first two screen using "Next" button click, 3rd screen showing in the default English language. While
↧
IA Installer's localization problem
Hello,
I am using IA 2014 SP1 Licensed version for creating installer for my application. I have created installer with two locales i.e. English and Japanese. it working correctly for windows with English locale. But not behaving correctly if I choose windows with Japanese locale. some of the installation screens showing in the default English language while expected should be in Japanese.please have a look, it's really urgent.
Thanks,
Deepak
(note: tested in windows 2012 data center, win 7, win 8 OS)
I am using IA 2014 SP1 Licensed version for creating installer for my application. I have created installer with two locales i.e. English and Japanese. it working correctly for windows with English locale. But not behaving correctly if I choose windows with Japanese locale. some of the installation screens showing in the default English language while expected should be in Japanese.please have a look, it's really urgent.
Thanks,
Deepak
(note: tested in windows 2012 data center, win 7, win 8 OS)
↧
Necessary Program Resource Files Have Restricted Access
Hello,
I am running Visual Studio 2015 with InstallShield 2015 Limited Edition.
My destination install directory on the target computer is in the [ProgramFilesFolder].
Within this install directory, I have my 'Resources' folder that contains the images and text documents necessary for the program function.
Right-clicking "IntroductionTextFileEdit.txt" and selecting properties, I am able to Override system attributes and deselect Use File Hash (screen capture included).
By doing so, I am able to access, edit, and save to the target text file without issue. This is necessary for the purpose of the program.
The problem is that when I lock my computer, put it to sleep, reboot, etc., the attribute I override somehow gets reset, and my file is no longer accessible. An error is thrown saying that access to the path I specify is denied (screen capture included). The only way to correct is by reinstalling the program.
I've searched for an alternative setting somewhere in Visual Studio, and tried finding a solution online with no success.
Do I need to save the resource files in a different folder in order to allow my program full privileges to read / write, or is there a setting that I'm overlooking somewhere?
Any feedback and guidance is greatly appreciated.
Kind Regards,
Shane
I am running Visual Studio 2015 with InstallShield 2015 Limited Edition.
My destination install directory on the target computer is in the [ProgramFilesFolder].
Within this install directory, I have my 'Resources' folder that contains the images and text documents necessary for the program function.
Right-clicking "IntroductionTextFileEdit.txt" and selecting properties, I am able to Override system attributes and deselect Use File Hash (screen capture included).
By doing so, I am able to access, edit, and save to the target text file without issue. This is necessary for the purpose of the program.
The problem is that when I lock my computer, put it to sleep, reboot, etc., the attribute I override somehow gets reset, and my file is no longer accessible. An error is thrown saying that access to the path I specify is denied (screen capture included). The only way to correct is by reinstalling the program.
I've searched for an alternative setting somewhere in Visual Studio, and tried finding a solution online with no success.
Do I need to save the resource files in a different folder in order to allow my program full privileges to read / write, or is there a setting that I'm overlooking somewhere?
Any feedback and guidance is greatly appreciated.
Kind Regards,
Shane
↧
Problem returning progress bar to Suite Project
So i am working with a Basic MSI project to enable IIS features and give a progress bar back to the user. The basic MSI when run on its own, works perfectly and as expected. The problem i am having is when i add this IIS.msi package to my Suite installer, while it executes the IIS.msi package, the progress bar DOESNT move at all. I get updated progress text as each action takes place but no movement on the Suite progress bar. What am i missing? I feel like my msi isnt returning the status back to the suite. Any help from someone out there?
Code:
#include "ifx.h"
export prototype NUMBER IISComponentInstallation(HWND);
function IISComponentInstallation(hMSI)
STRING svDismLocation;
STRING svDism;
STRING svDismHost;
STRING arrFeature(10);
NUMBER nCount;
INT iResult;
HWND hRecord;
begin
svDismLocation = WINDIR ^ "\\SysNative\\dism.exe";
svDism = "Dism.exe";
svDismHost = "DismHost.exe";
nCount = 0;
arrFeature(0) = "IIS-StaticContent";
arrFeature(1) = "IIS-ManagementConsole";
arrFeature(2) = "IIS-ManagementScriptingTools";
arrFeature(3) = "IIS-ISAPIFilter";
arrFeature(4) = "IIS-ISAPIExtensions";
arrFeature(5) = "IIS-RequestFiltering";
arrFeature(6) = "IIS-NetFxExtensibility";
arrFeature(7) = "IIS-ASP";
arrFeature(8) = "IIS-DefaultDocument";
arrFeature(9) = "IIS-ASPNET";
hRecord = MsiCreateRecord(3);
// Reset the progress bar to 10 total ticks.
MsiRecordSetInteger(hRecord, 1, 0);
MsiRecordSetInteger(hRecord, 2, 10); // Total number of ticks the progress bar will contain
MsiRecordSetInteger(hRecord, 3, 0);
iResult = MsiProcessMessage(hMSI, INSTALLMESSAGE_PROGRESS, hRecord);
if( iResult = IDCANCEL ) then
return ERROR_INSTALL_USEREXIT;
endif;
while( nCount <= 9 )
// Send one progress tick.
MsiRecordSetInteger(hRecord, 1, 2);
MsiRecordSetInteger(hRecord, 2, 1);
MsiRecordSetInteger(hRecord, 3, 0);
iResult = MsiProcessMessage(hMSI, INSTALLMESSAGE_PROGRESS, hRecord);
if( iResult = IDCANCEL ) then
return ERROR_INSTALL_USEREXIT;
endif;
MsiRecordSetString(hRecord, 1, "callAddProgressInfo");
MsiRecordSetString(hRecord, 2, "Configuring " + arrFeature(nCount));
MsiRecordSetString(hRecord, 3, "Incrementing tick [1] of [2]");
iResult = MsiProcessMessage(hMSI, INSTALLMESSAGE_ACTIONSTART, hRecord);
if( iResult = IDCANCEL ) then
return ERROR_INSTALL_USEREXIT;
endif;
LaunchApplication( svDismLocation, "/Online /Enable-Feature /FeatureName:" + arrFeature(nCount) + "", "", SW_NORMAL, 30000, LAAW_OPTION_WAIT );
while( IsAppRunning( svDism ) || IsAppRunning( svDismHost ) )
Delay( 1 );
endwhile;
nCount = nCount + 1;
endwhile;
MsiCloseHandle(hRecord);
return ERROR_SUCCESS;
end;↧
↧
SUITE: OnBegin event cannot filter for Install only
I have a couple of events set to run OnBegin. I only need these events to run if we are installing, not repairing, or removing, or maintenance mode.
There isn't an option for Install Mode shown in the UI for the OnBegin events, but the 'Package Operation' condition check does appear. So I select this and set the package to my primary package and set the check for 'Install'. If my understanding is correct, this should work if the package is set to Install.
However, this is not the case. None of my events execute properly in the OnBegin event possibly because the installer has not evaluated the install state for each package yet.
Is there some other property I can check so that my events execute in OnBegin for install mode only?
Thanks.
There isn't an option for Install Mode shown in the UI for the OnBegin events, but the 'Package Operation' condition check does appear. So I select this and set the package to my primary package and set the check for 'Install'. If my understanding is correct, this should work if the package is set to Install.
However, this is not the case. None of my events execute properly in the OnBegin event possibly because the installer has not evaluated the install state for each package yet.
Is there some other property I can check so that my events execute in OnBegin for install mode only?
Thanks.
↧
How to add dll files
Hi, I just installed Installshield to deploy a project.
When I create an Installshield project, I only see the name of my project, "Getting started", "Learn more" and "Project assistant". But I can't expand the "Organize your setup", "Specify Application Data" and all the other nodes. I looked on internet an couldn't find an answer. Help would be very appreciated.
I want to add the DLL files that I linked with dynamically to my Installshield setup. That is why I need to expand the nodes (If there is a way to add the DLL without expanding the nodes, it will fix my problem too)
Thank you !
noble
When I create an Installshield project, I only see the name of my project, "Getting started", "Learn more" and "Project assistant". But I can't expand the "Organize your setup", "Specify Application Data" and all the other nodes. I looked on internet an couldn't find an answer. Help would be very appreciated.
I want to add the DLL files that I linked with dynamically to my Installshield setup. That is why I need to expand the nodes (If there is a way to add the DLL without expanding the nodes, it will fix my problem too)
Thank you !
noble
↧
Need instructions on creating an installer for a non-PNP (kernel mode) device driver
For 3 days I've been trying to create an InstallShield project that will automatically install a kernel mode device driver (non-PNP) into the system's driver store and ALSO get it to install the driver so that it appears in Device Manager after the install operation completes.
The device driver is for a SPI master controller that is present in an on-board FPGA. It is not a removable device. The driver is signed, and installs without problems when using Device Manager to "Add legacy hardware".
I can create an installer for it using DPInst.exe but that method only installs it into the driver store. Since the device is not plug-n-play, I cannot remove the hardware from my system, and then reinsert it to trigger the plug-n-play driver installation process.
I can use InstallShield to accomplish the exact same thing, i.e. - create a basic MSI project, run the device driver wizard, and package the driver and it's support files into an MSI package. When I install the MSI package, it does the exact same thing that occurs when the driver is packed with IExpress and DPInst.exe.
I don't want to become an InstallShield script expert in order to figure out how to do this. I just need to package a single driver that will automatically install when a customer executes the installer package. This is the sole reason we are considering buying InstallShield. So until I can accomplish this, I cannot in all good conscience recommend that my company spend the not-insignificant amount of money to license InstallShield.
Any assistance/guidance would be greatly appreciated.
Patrick
The device driver is for a SPI master controller that is present in an on-board FPGA. It is not a removable device. The driver is signed, and installs without problems when using Device Manager to "Add legacy hardware".
I can create an installer for it using DPInst.exe but that method only installs it into the driver store. Since the device is not plug-n-play, I cannot remove the hardware from my system, and then reinsert it to trigger the plug-n-play driver installation process.
I can use InstallShield to accomplish the exact same thing, i.e. - create a basic MSI project, run the device driver wizard, and package the driver and it's support files into an MSI package. When I install the MSI package, it does the exact same thing that occurs when the driver is packed with IExpress and DPInst.exe.
I don't want to become an InstallShield script expert in order to figure out how to do this. I just need to package a single driver that will automatically install when a customer executes the installer package. This is the sole reason we are considering buying InstallShield. So until I can accomplish this, I cannot in all good conscience recommend that my company spend the not-insignificant amount of money to license InstallShield.
Any assistance/guidance would be greatly appreciated.
Patrick
↧