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.
Related
I have downloaded DCEVM jar file. Now I want to install this jar to run Gosu queries in my Gudiewire Studio.
Please help me how to install this DCEVM jar in Guidewire Studio.
Thanks
DCEVM was first published in June 2010 as a research paper. Since then it has been widely used by Guidewire as the preferred VM for development environments. It allows you to Hot Swap (partially reload code changes to classes) without restarting the VM. In a development environment, it can help save a lot of time where a full VM restart can take several minutes. A fork of the original DCEVM is available at http://dcevm.github.io/.
The Dynamic Code Evolution Virtual Machine (DCE VM) is a modification
of the Java HotSpot™ VM that allows unlimited redefinition of loaded
classes at runtime. The current hot-swapping mechanism of the HotSpot™
VM allows only changing method bodies. Our enhanced VM allows adding
and removing fields and methods as well as changes to the super types
of a class.
You can download the suitable installer jar file for your java version and patch your existing JDK by DCEVM. Unfortunately, the only installer available is a jar file and there are caveats to using it.
First of all, you can only patch your JDK if the DCEVM version supports your JDK minor version. A lot of people don't understand this and encounter failures when they try to patch a newer update of Java with the previous version of DCEVM.
A key point to note in the image is the available versions of DCEVM. To be able to install it on Java 8, you must have Java with the update 181 installed i.e. your JDK version must equal 8u181. If you installed an update on the JDK and updated it to 8u271 or another version, the patch is not going to work.
Once you have the installer jar downloaded, you must run it with Administrator privileges on Windows for it to work. In Windows, run cmd as Administrator and then navigate to the directory where the jar is downloaded and run:
java -jar dcevm-installer.jar
For unix based systems you must run:
sudo java -jar dcevm-installer.jar
This should open a window where you need to select your correct JDK version and then click on the Replace by DCEVM button. If done correctly you'll be able to see the status as below:
DCEVM isn't required to run queries in GW Studio. DCEVM enables more capabilities to hotswap (class reloading after compile).
To run queries in GW Studio you only need start server in debug mode, open Gosu Scratchpad (Tools menu or Alt+Shift+S) and use "Run in Debug Process" button in scratchpad
C:\ java -jar dcevem.jar
It will open the DCEVM window, select the java version, and click on the install button.
For version 10.0.3 there actually 2 possible paths to run Guidewire on DCEVM, depending on the version of Java you are using. Those instructions should also work for other versions of GW
For Java 11
Visit http://dcevm.github.io/.
Click the Java 11 link.
Scroll to find the binary for your development platform, and click to download the relevant file, extract the contents of the downloaded file.
Add the DCEVM as an alternate JDK in Studio.
In Studio, click File → Project Structure
Under Platform Settings, click SDKs.
Click Add New SDK +.
Select the folder for the DCEVM, and then click OK.
In the Name text box, change the name to DCEVM.
Click OK.
Click Run → Edit Configurations.
Under Application, click Servers.
Next to JRE, click DCEVM.
Do not set the DCEVM as your project SDK.
For Java 8
Visit http://dcevm.github.io/.
Click the link under Binaries to download the appropriate DCEVM installer for your java version.
Install the DCEVM as an alternative JVM.
At a command prompt, run java -jar installer.jar, where installer.jar is the name of the file you downloaded in the previous step.
java –jar DCEVM-8u181-installer.jar
The Dynamic Code Evolution VM Installer dialog appears.
Select the installation directory for the JDK corresponding to the DCEVM version you are installing.
Click the Install DCEVM as altjvm button.
The Dynamic Code Evolution VM Installer dialog displays Yes in the Installed altjvm column for the selected JDK.
Click "X" to close the Dynamic Code Evolution VM Installer dialog.
In Studio, at the right hand side of the toolbar, select Server.
Click Run → Edit Configurations.
Under Application, click Servers.
In VM options, add -XXaltjvm=dcevm to the end of the line.
Click OK.
Both instructions above are based on the info from documentation
dfsutil is useful on workstations for checking what's going on with the DFS shares that the client is subscribed to, e.g. by running dfsutil /pktinfo.
For Windows 10 pre-October 2018 dfsutil can be downloaded as part of RSAT Tools for Windows 10, but how do I get dfsutil for current versions of Windows 10?
The RSAT Tools download page gives a link to the list of RSAT tools available via Features on Demand in newer versions of Windows 10, however there are about 20 different RSAT features which you can download, and nothing in that page clearly says which one you need for dfsutil.
So, the full answer is:
Open Windows 10 settings
Search for 'Manage optional features'
Click on 'Add a feature'
Choose the package 'RSAT: File Services Tools' and click 'Install'
Depending on the precise version of Windows 10, you will either see the package installing immediately, or if not you will need to click back once to see installation progress
Wait to see the package finish installing
That's it, dfsutil is now available from Command Prompt and PowerShell; no reboot is needed.
You can add the optional feature with this PowerShell (admin) command:
Add-WindowsCapability -Online -Name "Rsat.FileServices.Tools~~~~0.0.1.0"
This will install dfsutil and also the DFS management console (dfsmgmt.msc)
My install-shield 2010 is not opening only the splash screen is opened , it was working fine earlier.I have uninstalled it and deleted all the files in app-data,program-files and the registry,im confused if some other app might be blocking this EXE to run (Because it was working properly earlier).
it happen to me from time to time, the problems is usually because the auto reactivation of my licence failed.
their's a tools for that called TSConfig.exe in C:\Program Files (x86)\InstallShield\2015\System.
If it's not that, you can still check in the InstallShield.log in the same directory, it might give you more clues.
EDIT :
I Just found the email that the Flexera support send me back in the day
Close InstallShield
Locate tsconfig.exe on the machine (the default location is:
C:\Program Files\InstallShield\2011\System)
From a command prompt, run the following command: tsconfig.exe /return
Launch InstallShield
If prompted proceed with activation using serial
number
Platform Builder 5.0 is only supported on Windows 2000 and XP.
This question is to aid those looking for a way to run Platform Builder 5.0 on more recent operating systems.
A few reasons one might want to do that:
Corporate IT policy may not permit the use of Windows 2000/XP
With time, genuine copies of Windows 2000/XP may become increasingly hard to obtain
Depending on your overall setup and requirements, might eliminate the need for using a virtual machine for Platform Builder 5.0
You may simply wish to run a more modern and secure operating system
This answer explains how to install and run Platform Builder 5.0 on operating systems it is not officially supported on.
Windows Server 2008 and 2012
This procedure has been found to work on:
Windows Server 2008 (32-bit)
Windows Server 2012
Windows Server 2012 R2
It is recommended that you install Platform Builder before joining a Windows domain. I've had some issues getting the Platform Manager components registered while logged in as a domain user. See also the description further below.
Virus protection software might prevent the installation of .NET Framework 1.1, at least this has been a problem with Symantec Endpoint Protection. You may have to remove any security products before starting the installation (these may be re-installed later, but see the note below on the Full vs. Basic version of Symantec EP).
To install PB5, start by copying the contents of the installation CD (or mounted .iso) to a local folder, from here onwards referred to as the installation folder.
Use an .msi editor (like Orca) to remove the following entries from Microsoft Windows CE 5.0.msi in the installation folder:
OS version check (Table LaunchCondition, Action (MsiNTProductType=1 OR ...)
Emulator device driver (Table InstallExecuteSequence, Action CA_InstallVMMDriver.3D2F911E_A60A_4C07_8F7D_5306DC073E9A)
From the installation folder, run, in this order
ISScript8.msi (installs the InstallShield 8.0 script engine)
dotnetfx.exe (installs .NET Framework 1.1)
Microsoft Windows CE 5.0.msi (installs Platform Builder 5.0)
The installation may appear to hang at the Registering Platform Manager components step. It should proceed after a few minutes. If it is still stuck after, say, ten minutes, and your machine is joined to a Windows domain, then kill the installer in Task Manager, leave the domain and try installing again (you can rejoin after the installation is complete).
During the installation, you will receive a warning about compatibility issues. Select Don't show this warning again and click Run the program without getting help.
After the installation has finished, add a registry entry as follows.
If installing on a 32-bit system:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools]
"SharedFilesDir"="C:\Program Files\Common Files\Microsoft Shared\"
Otherwise (installing on a 64-bit system):
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Shared Tools]
"SharedFilesDir"="C:\Program Files (x86)\Common Files\Microsoft Shared\"
Next, install Windows CE / Platform Builder updates as required (i.e. the "monthly updates" provided by Microsoft).
Optional: If any of your Windows CE targets require CJK support, you will need to update the cenlscmp tool to avoid an error during the makeimg phase. While this bug has long been fixed in Platform Builder 6.0 (PB6), the PB5 version has been left in the dust. So for CJK support you will need to copy cenlscmp from a PB6 installation, i.e. copy C:\WINCE600\PUBLIC\COMMON\OAK\BIN\I386\cenlscmp.exe to the corresponding folder in your new WINCE500 tree. Note that I've only tested the PB6 version; it is likely that newer versions would work too.
Optional: If you need support for building SDKs, you must make a copy of the Platform Builder help files, or a hard-coded assumption in the SDK builder will cause the build to fail. Copy the directory C:\Program Files (x86)\Windows CE Platform Builder\5.00\cepb\help to C:\Program Files\Windows CE Platform Builder\5.00\cepb\help.
Launch Platform Builder.
You will see a warning about compatibility issues. Select Don't show this warning again and click Run the program without getting help.
Optional: In the main window, click Tools | Customize. Click the Build OS menu once to open it. Drag the Build and Sysgen menu item out of the menu and drop it when the cursor displays a small 'X'. This will remove a dangerous command that, if clicked by accident, will require reinstalling Platform Builder. Hit Close to dismiss the Customize dialog box.
Platform Builder 5.0 is now ready to use, including the IDE itself, the build system, the help system, the debugger, and the run-time licensing tool.
Features that I haven't tested and which may or may not work include CETK and the emulator (the latter highly unlikely to work, as the emulator device driver had to be removed from the .msi).
If you use Symantec Endpoint Protection, be aware that the Full version may prevent pbxmlutils - an important Platform Builder tool - from running. This does not appear to be an issue with the Basic version.
One last hurdle is to configure the firewall to permit debugger traffic. To do this, open Windows Firewall with Advanced Security and
Under Inbound Rules, hit New Rule...
Select Program, Next
Enter the Path %ProgramFiles% (x86)\Windows CE Platform Builder\5.00\CORECON\BIN\cesvchost.exe, click Next
Ensure Allow the connection is selected, Next
Ensure Private and Domain are selected (but not Public, unless you really need this), Next
Enter a Name, e.g. "Platform Builder 5.0 debugger - cesvchost", Finish
Repeat the above with the path %ProgramFiles% (x86)\Common Files\Microsoft Shared\Windows CE Tools\Platman\bin\cemgr.exe.
Platform Builder will now be able to receive BOOTME frames, upload images, and connect to target with the kernel debugger.
Windows 7 and 8
The procedure documented above will not work for 64-bit Windows 7 or 8 (32-bit not tested).
Modifying the .msi as described makes the installation hang at the Registering Platform Manager components step. Removing the Platform Manager components from the installer causes a number of other issues, including failed registrations of the Help system and some common controls. More importantly, with Platform Manager missing it will not be possible to install any Windows CE/Platform Builder updates, making it virtually impossible to build any non-trivial CE project.
Windows 10
Not tested.
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