.msi file doesn't run in my pc windows 8 professional - windows

.MSI file doesn't run in my Laptop windows 8 professional any help please.
while it runs in friend's Laptop.
How can i run it
When i run my file it ask which application you want to run this file?

Maybe .msi file extension was somehow unregistered from its application (msiexec.exe), which should be already installed. Try entering this in command prompt:
msiexec /i path_to_your_install_file.msi
If this starts the installation, then you should later eventually reregister .msi files. How to do that would be another story.

Related

How to install Visual Studio Remote Tools on Server Core?

I'd like to install the Visual Studio 2013 Update 4 Remote Tools on a Windows 2012R2 Server running IIS 8.5. This is a pretty simple process outlined here: https://msdn.microsoft.com/en-us/library/bt727f1t.aspx
The problem I have is that the server I'm trying to installing this on is a Server Core, meaning, there is no GUI. The Remote Tools application is an exe that only installs via GUI.
I've tried to install it with PowerShell and it just hangs. I'm also not able to find the Remote Tools in Web Platform Installer to install it that way. Extensive Googling has turned up nothing.
Does anyone know how to install the Visual Studio Remote Tools on a Server Core so that I can debug on my DEV server? Any advice is appreciated.
Create a .bat file and enter the below. (not PowerShell) (Or just at the command line.)
rtools_setup_x64.exe" /install /quiet
word...
You don't have to install remote tools. Just copy msvsmon.exe, from your local Visual Studio installation. Then start it from remote powershell silently:
Start-Process -FilePath .\msvsmon.exe -ArgumentList '/nosecuritywarn /port:4022 /silent' -Verb runAs
Don't forget to open firewall port.
Turns out that you can simply remote into the Core server. When you do so, you'll get a command prompt only. From there, CD to the directory where the remote tools install file is. Execute the file by typing the file name at the command prompt, ie: rtools_setup_x64.exe.
This will run the installer, with a GUI, on the Core server. Its that simple, I didn't think you'd be able to get the install wizard on a Core server, however you do.

MSI wrapper from command line

Is there any MSI wrapper that works from a command line? Or even an MSI creator that could be automated?
I have a client that requires an MSI file to roll out into their windows server environment. What I need to package is a .exe file (windows Zabbix agent) that installs itself as a service from wherever the file is located when you run it.
Currently I have a self-extracting .exe that runs a batch file, and then I use a free MSI wrapper to convert it to MSI.
I'm trying to automate this so my co-workers can change zabbix config files and then run a batch that creates the package for them. I can do everything up to creating the MSI.
Try to use http://www.suiviperf.com/zabbix/.
Or check Zabbix forum, it contains similar questions:
e.g. https://www.zabbix.com/forum/showthread.php?t=22688
You can try Advanced Installer, it has a free 30 days trial for you to test. The Professional edition can help you create and MSI that wraps your EXE (one or many).
Also, it has a command line interface, so you can automate the build process for the setup package.

Installshield response file not being generated

I've built an installer using InstallShield 2011. I need to do a silent install so I ran the setup.exe with the -r flag to record the response file. However, the installer doesn't appear to actually generate a file (I've looked in the windows directory for the .iss file - in fact I've looked over my entire hard disk for .iss files)
I'm installing on Windows 7 64 bit Ultimate Edition and running from an elevated command prompt
Has anyone seen this before or have any ideas why the file isn't getting generated?

Program Files (x86) problem

I have an installer package, at the last step user can select launch application or not. the installed application is 32bit, during the installation we select the installation folder to "c:\Program Files", while it will always install application to "c:\Program Files(x86)" folder, then we meet problem, we can not launch the application, we have tested that if we choose the default installation folder(which means c:\program files") it works well. so I guess the problem is that windows launch 32bit application as 64bit, so it failed. how to solve it?
Your installer should know the path the application was installed to. You should use it, your EXE file key; for a WiX example see Well Done section of the tutorial.
If your installer package is MSI-based, then the installer is a 64 bit process, and it sees both Program Files (x86) and Program Files. I think it is the problem why you can't start your program. (A 32 bit executable will see only Program Files (x86) under the name of Program Files).

Error 1926 on setup created by InstallShield 2008

I'm compiling the setup with InstallShield 2008 - Professional and I have a problem that occurred only in some Win 7 Ultimate systems.
My setup is suppose (among others) to copy files to the "Program Files" & "System32" directories.
The problem occurred when the setup try to copy files to the "System32" directory.
The install shield raise this error message box:
"Error 1926. Could not set file security for file C:\Windows\system32\, Error: 0. Verify that you have sufficient privileges to modify the security permissions for this file. "
I run the setup "As Administrator", run it when logged on as the user administrator, and still get this error every time I ran the setup (UAC on and off).
As I wrote in the beginning this is only happens in some Windows 7 ultimate 32-bit system, on other system (xp, server 2003,vista,server 2008 including on most win 7 systems) it works fine.
Which type of project you are using Basic MSI or Installscript?
I think during file copy to the System32 folder, sometimes Installer will raise exception, because maybe the file already present with higher version and that file may in use by the O.S. Make sure that if files are not present then only copy else do not.

Resources