I have a Basic MSI Project that has several prereqs. I set the launch conditions for the MSI to be Win Vista SP2, Win 7 SP1, Win 8+ and their corresponding Server OSs. Now, when running the installer on Win XP, the launch condition fails and I get a pop up message. That's great, however I was finding that I had some prereqs that were popping up before that point and would need to be installed before realizing that I can't even install the program on the OS. So, to fix this problem I went through each prereq and set the OSs that the prereq would run under to the same as the launch conditions. This worked for every prereq except one. I can't seem to figure out why this one prereq is still showing up on XP. Listed below is the prereq in question and it's conditions tab contents.
I'm not sure why, but for some reason InstallShield was pulling a prerequisite with different conditions during the build. I've checked Tools -> Options-> Prereq tab and it had the correct path there. When I fixed the prereq in another location everything worked fine. So I guess the issue is resolved now.
Related
We have an installer built with Advanced Installer. We are installing IIS from the Windows Feature Bundle. Weird thing is when we run the installer on a fresh Virtual Machine, it works and we can see IIS. However, when client runs it on their computer (they have domain computer) they cannot start the IIS. In fact IIS doesn't show up on the menu. Note: the installer did NOT show any error message. When we looked at the windows features it looks like the IIS should have installed, but can't find it in the menu:
Moreover, we have compared the two logs of successful and unsuccessful installation, and surprisingly there were no significant difference that might indicate of any kind of error for the IIS installation.
Here's a screenshot of our advanced installer configuration:
Any idea what is going wrong? Or how can we even look for the problem?
You can check whether IIS is installed in the system through the command, press "Win + R" → enter "inetmgr" → OK, if the IIS manager window appears, it means it is installed, otherwise it is not installed.
Everything used to work fine, but I haven't been using Virtual Box for several weeks. Now all of the sudden, I get the following exception when trying to start my Windows 10(32-Bit) VM. Note - Things were working fine several weeks ago. As far as I can tell, I haven't changed anything on my system that would cause this. The exception details are as follow:
VirtualBox - Error In supR3HardenedWinReSpawn (rc=-5640)
Please try reinstalling VirtualBox. where supR3HardenedWinReSpawn
what: 1 VERR_SUP_VP_THREAD_NOT_ALONE (-5640) - Process Verification
Failure: The process has more than one thread
I have been researching this for some time, to avail. Any help would be greatly appreciated.
There is a workaround:
Open VMbox manager
Run your VM with option "Detachable start"
Wait a while and then use "Show" to show the screen
Detachable start option
Show the screen
My setup:
Oracle VM Box 6.0 running on Win10,
VM is Ubuntu 18.04
If you are using vagrant to boot up your Virtual machine, then in most cases the error is due to improper shutdown of the VM. A fix that worked for me is to execute vagrant halt or similar commands multiple times until you have a clean boot.
In case anyone is in the same predicament, I will share what finally fixed my issue. I found a post during my hours and hours of searching that said you have to enable virtualization in BIOS settings. I checked my machine and virtualization was enabled, so I went on searching. At a loss for what to try next, I finally tried turning virtualization off, just to see. No change, but when I went to turn it back on, just as a flook I turned Turbo off, and what do you know - All of the suddent I can start my VM. So the solution, in case it saves someone time:
Uninstall Virtual Box (Latest Version)
Reboot your machine and enter BIOS
Make sure anything with the term 'Virtualization' is turned on
Make sure anything with the term 'Turbo' is turned off
Reboot your machine
Install Virtual Box
Hopefully this saves some poor soul what I had to go through to get this thing working.
METHOD A
If you are using WindHawk, exit it and re-try.
Method B
download previous version from https://www.virtualbox.org/wiki/Download_Old_Builds
install & extensions
Try to re-run your guest OS.
Try to do these steps:
1. Uninstall the VirtualBox program.
2. In your C:\users\\ might have two folders called ".VirtualBox" and "VirtualBox VMs": Delete them
3. Restart your PC
4. Install VirtualBox again
5. Add again your VM
6. It must working fine!
These steps worked for me!
Workaround 1:
Just increase the RAM size from virtual box settings
Right Click on OS image .
Settings->System->MotherBoard
Increase the base memory
Workaround 2:
Change the Paravirtualization Interface from default to none
Right Click on OS image .
Settings->System->Acceleration
Change acceleration from default to none.
The above one's was basically a workaround , which can work in some but not in all.
The best thing would be to reinstall virtual box with latest version which virtual box has tried to rectify the bug and use the same vdi files which was made by Virtual Box .
One of the most common causes that will cause this type of behaviour is a missing driver (VBoxDrv.inf). It’s possible that due to some permission issues, the installation of this crucial driver doesn’t complete during the initial installation. In this case, you can fix the problem by installing the VBoxDrv.inf manually.
1.Fix the directory problem Press Windows key + R to open up a Run dialog box. Inside the text box, type ‘regedit’ and press Enter to open up Registry Editor. When you’re prompted by the User Account Control (UAC), click Yes to grant admin access.
Once you’re inside the Registry Editor, use the left-hand section to navigate to the
following location: HKEY_LOCAL_MACHINE\system\currentcontrolset\services\vboxdrv
After you arrive at the correct location, move over to the right-hand section and
double-click on ImagePath the path associated should be \C:\Program
Files\Oracle\VirtualBox\drivers\vboxdrv\VBoxDrv.sys
if not replace with the above path and click ok.
Install the VBoxDRV.inf OPen location C:\Program Files\Oracle\VirtualBox\drivers\vboxdrv right-click on VBoxDrv.inf and choose Install from the context menu.
Then in cmd run command "sc start vboxdrv"
Restart system. This should work.
I have a Visual C++ MFC app. When I update the RC file menus via resource editor, sometimes it isn't reflected when I run the app. Other times, the updated menus work on the development machine, but not on other machines. Note: the other machines had a previous version of the software installed. I simply copied and pasted the release folder over from one machine to another. Using the Wix installer we use to install everything (AFTER UNINSTALLING FROM CONTROL PANEL) doesn't seem to work either. What I missing? How do I get my menus to behave correctly? Why do things work on some PCs and not on others?
I know this isnt a dev question per se, but is there a timeline on a 5.2 build that can be installed on Win 10?
I think the issue i am seeing is just with the installer so an in place upgrade to Win 10 might work fine, but a clean install fails as it doesnt acknowledge IIS 10 or whatever version comes with Win 10.
Thanks!
Official answer - Windows 10 is not yet supported by the currently available Acumatica ERP installers, however the issue has already been fixed internally (AC-56069 - fixed in 4.20.2262, 5.10.0785, 5.20.1012 and newer). Following workaround can be used in the meantime:
Download the Orca tool to edit the MSI file: http://adriank.org/wp-content/uploads/2015/01/Orca.zip
Open the
MSI file using this tool (might be able to right click on MSI and
open with Orca)
Go to the LaunchCondition table
Drop/delete the IIS version condition (inside MSI, the LaunchCondition entry is IISVERSION >="#7"; system does a string comparison and "10" is
smaller than "7")
Save and close Orca
Run the setup
I can't give you an "official" answer but I can give you a work around.
If you download a utility called LessMSI you can extract the installation files. They will come out in a folder called "SourceDir". Simply take these and replace the files in your default installation folder or run them from another location.
Then you can proceed as normal.
The installer only checks if pre-reqs are installed and then copy's the files to the output location. If you have IIS already setup with dotnet support then the rest will be fine.
I do this frequently if I have to install a site with a specific version in order to upgrade or test a client's snapshot.
I have 4.1,4.2,5.1,5.2 running on my Windows 10 workstation as I type
i'm trying to install visual studio 2013 into my windows 7 32 bit system. I've encountered the below error during installation
"This update package could not be opened. Verify that the update package exists and that you can
access it, or contact the application vendor to verify that this is a valid Windows Installer
update package."
Help me out
it is windows so i am guessing: the installer package is corrupt or follow this link: http://kb.eset.de/esetkb/index?page=content&id=SOLN561
try to make some md5 sums of your files and google for them.
Normally this issue will occur if you are having permission issue or compatibility issue.
For permission issue:
Right click on the executable and run it with run as administrator option and check.
If above is not working then check for the compatibility issue by following the steps below:
To Run the installation program in compatibility mode:
1. Right-click the installation file's icon.
2. Click Properties > Compatibility .
3. Select the compatibility mode for Windows XP.
4. Click OK .
5. Run the installation program.
After it's installed, run the program in Windows XP compatibility mode by doing the same with the installed program.
If you have an older application for Windows XP or Vista that doesn't run in Windows 7, you may be able to get it working properly by running the program in compatibility mode.
1. To begin, find the application or shortcut that is causing the problem, then right click on it and select Properties.
2. Then, select Compatibility from the tabbed menu at the top of the properties page:
3. Now, check the "Run this program in compatibility mode for..." box and select the OS you wish to emulate. For most applications, it will be Windows XP SP2. Once you are done, click OK.
4. When you next launch the application it should run under compatibility mode using the OS you selected. If it still fails to run correctly, try another OS selection in step 3 and try again.