I am trying to install Oracle 12c instant 32-bit client alongside my 64-bit installation because I can't connect Visual Studio to the 64-bit version (throws BadImageFormatException). I run the installer and give it another directory for home, so it's like this:
64-bit: D:\app\MyUser\product\12.1.0\dbhome_1 (previously installed)
32-bit: D:\app\Lazar\product\12.1.0\dbhome_x84
The installer performs the checks and sends me to next step. I click install and it crashes!
Can someone please help?
I've actually run into the same problem. It looks like it is some sort of issue with the registry.
It appears to be a missing registry entry for the location of the Oracle Inventory. The below blog explains the following steps to add the missing registry key:
Open regedit
Go to HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node
Create a new key with name "Oracle"
Go to Oracle and then create a new String Value with name "inst_loc"
Give the value as "C:\Program Files (x86)\Oracle\Inventory"
Retry installation
This blog post has more detail on the fix (though not much) and is where I originally found my solution.
https://oracledba1949.wordpress.com/2016/03/11/oracle-12-1-0-2-32bit-client-installation-on-windows-2012-x64bit/
I also had the same issue and finally realized that Oracle installer doesn't support both 64bit and 32bit versions alongside. At least as you have mentioned in the question, it has got a bug. Here how I resolved the problem.
Hence both 64bit & 32bit versions unable to install alongside, first, uninstall the 64bit version.
Run the command %ORACLE_HOME%\deinstall\deinstall.bat
If any errors occur while uninstall, refer to the log and correct accordingly.
Recommend to restart the computer.
Install the 32bit version.
This will resolve your problem.
Related
I have trouble when I try to upload an Excel file, I've searched in a lot of places how to solve this, but the solution the give (only install Microsoft Access Database Engine 2010 Redistributable) doesn´t work for me. I have VS2017 and I've installed Microsoft Access Database Engine 2010 Redistributable, I´m kinda new doing this so I donn´t know what I´m missing.
Thanks
a pleasure to greet you, an hour ago I had the same problem, the only thing I did was download both versions (both the 32-bit and the 64-bit version) and the first thing I did was install the 64-bit version of normal way, downloading from the official page, but I installed the 32-bit version from Command Prompt with the following code:
CD: [path]/AccessDataEngine.exe /passive
in this way I managed to solve that error
I need to migrate an enterprise production database from a Windows source machine running Postgres 9.5 to an Ubuntu destination machine running Postgres 11.6 with < 15 mins downtime. I plan to do this with pglogical, which requires the extension being loaded on both source and destination. I am having trouble with the source side because it is Windows.
I have very little Postgres-Windows experience and can neither find any helpful literature on the specific situation nor can I figure out for myself how to presumably install from source.
I've dug and dug and so far the only answer I've been able to find is "ugh... Windows". It seems like the only way to build from source is using Visual Studio, which I don't have or know how to use.
Sources:
https://www.2ndquadrant.com/en/blog/compiling-postgresql-extensions-visual-studio-windows/
https://postgrespro.ru/list/thread-id/1835275
Alex, the 2ndQuadrant article you link to in your own comment solves this. A few of the project or build options noted there have moved a little bit in the newer VisualStudio Community editions, so I can see where you got hung-up.
Just for kicks I compiled 32-bit DLL on my oldest Windows instance. I included the /Release path so you can grab my DLL & see if it works for you. It's (a) 32-bit because I'm assuming worst-case for an old v9.5 install, and (b) targets Postgres 9.6 because that's what I had installed. Unless there were major API changes though, it should connect to v9.5 without any issues:
https://github.com/mbijon/winpglogical/tree/master
If you find you need a version that entirely matches Postgres 9.5, grab my solution files & VS Community 20xx. Load the project & update the Additional Include Directories in Project Config to target your v9.5 paths. That should be all that's needed to link v9.5 Postgres libs.
I installed MySQL workbench 8.0 in windows 7. After the installation I just clicked server status its through the error like Could not acquire management access for administration. Run-time Error: Unable to execute command chcp. Please make sure that the C:Windows\System32 directory is in your path environment variable. How can I solve this error?
I solved the same problem on enable the parameter "Beta : Use UTF-8 for worldwide language support" in Control Panel > Region > Administrative > Change system locale...
It's disturbing because it's have nothing about the PATH environment variable. But it's work.
Notice that I working on french environment and MySQL Workbench 8.0.24 version.
To resolve this problem on 64 bit system we have to follow two steps.
add environment variable path to C:\Windows\System32
we need chcp.com cmd file in C:\Windows\SysWOW64
copy it from C:\Windows\System32 path and paste in C:\Windows\SysWOW64
now close mysql workbench and reopen it.
Hope you got the answer.
I've reproduced the same issue by clicking server status:
Could not acquire management access for administration
RuntimeError: Unable to execute command chcp. Please make sure that the C:\Windows\System32 directory is in your PATH environment variable
and after click cancel was:
Error during ""
error calling Python module function WbAdmin.openAdminSection
using MySQL Server 8.0.23 & MySQL Workbench 8.0.23 for 64-bit OS Windows 10.
Notice: all environment variables were configured correct in my case.
Solved it only by reinstalling and using another version like MySQL Workbench 8.0.20, but I'd really recommend also downgrade version of server to MySQL Server 8.0.20 to avoid other bugs, e.g.: creating/deleting schemes and so on.
The same version should match all products to work correctly.
Found solution for system non english language users! After failing in all attempts seen issue here: Mysql Bug Forum, where told that the problem is in unicode python codec error. So mine solution as for cyrillic language user was to set Windows administrative language for the cases when utf-8 is unavailable, see screenshot below.
"System language old value was Russian, after changing to English (USA) everything started to work.
Also watched Workbench logs - there was a python exception for the ascii codec. Thats all, hope this will help.
Add the 'C:\Windows\System32' to the PATH environment variable.
Make sure you add it to PATH and not to Path.
The solution of this problem for me was this:
Start the workbench community installer after installing the program you will go to this window enter image description here then you start the option of MySQL Server the option of "Reconfigure" and you accept all the options and create a new password (if you didn't make it before), execute the final screen and you are ready to use workbench :D
Had the same error for Windows 10. For me solution was to reinstall MySQL Server 8.0.24 and to enable option in installer "Configure MySQL Server as a Windows Service". Didn't have this option marked in the first installation, so I assume the problem was in this(there were no service for it, so after system restart MySQL Workbench 8.0 CE gave an error).
As mentioned before there are 2 possible fixes:
Change system locale to English(US)
Use Workbench ver. 8.0.22 or lower (error appears on vers. 8.0.23+)
Just add the C:\Windows\System32 to the Path, and the problem will be solved!
Don't forget to add ";" to separate addresses.
I am packaging my app into exe with javafx-maven-plugin. x64 version works well. But then I package x86 version on 32-bit Windows 7 (running in VirtualBox if that's important) with 32-bit JDK 1.8.0_161 and 32-bit Maven. The resulting application installs, but fails to run, claiming that MSVCR100.dll is missing even though it is in the runtime\bin folder. I googled around and found out that this is a JDK bug that was supposedly fixed way back in u40. So why does this still happen?
If I copy that dll manually next to the .exe it starts on one machine (again, in VirtualBox), but for some reason silently crashed on another (real one this time, fresh installation). Found an identical problem in javafx-gradle-plugin issues, though it got resolved when building on newest Win10 version, whereas I'm building on newest Win7.
If I just install Microsoft Visual C++ 2010 Redistributable Package then everything works, obviously, but I don't want user having to do that. So how do I copy .dll with Inno Setup script and how do I figure out the reason behind silent crashing?
I don't think this is related to Windows being 32 bit and it just happens to coincide with your two testing computers. I posted a question that is related here: Failed to find library: jvm.dll. What's going on here?
What you are experiencing is likely a bug on java(fx)packager as described here: https://bugs.openjdk.java.net/browse/JDK-8191176. That bug report claims the bug started on 8u155 and was solved by 8u171 but I am experiencing the bug all the way to the latest 8u172 b03 as I describe here: https://github.com/javafxports/openjdk-jfx/issues/59
I also tried going to 8u144 before the bug existed and I found that building the installer fails because of a missing MSVC dll (surprise! surprise!). I described the problem here: Where/how to get the MSVC dlls Java 1.8.0_144 wants?
There may be another .dll on which MSVCR100.dll depends and which is not present on specific machine.
That is a reason why the Redistributable Package installs everything together.
Try to find another dependencies using http://dependencywalker.com/, it looks like you need more dlls than MSVCR100.dll.
Or simply install Redistributable Package on each machine. Installing it multiple times does not harm any application or system.
I previously installed a website on the server by running an msi package and everything worked fine. Now, when I try to run the same msi file (to Repair/Uninstall), I get a message:
When I click Cancel, I get the following message:
Anybody has an idea what happened and how it can be fixed?
I would recommend that you run the MSI with logging enabled. This can be done by using the /l*v C:\mylog.txt switch or by modifying the registry. The log will provide you with more precise information as to what is going wrong during the msi process.
The articles below describe how to enable logging and the logging process in more detail
http://support.microsoft.com/kb/223300
http://technet.microsoft.com/en-us/library/cc759262(v=WS.10).aspx
http://msdn.microsoft.com/en-us/library/aa372847(v=vs.85).aspx
Once you have the log you can use a set of MSI tools like the Orca installer database editor tool on the Windows SDK to correct any issues.
This is the link for Windows 7 SDK which contains the msi tools.
http://www.microsoft.com/en-us/download/details.aspx?id=8279
Sorry for answering my own question, but I found the problem and I want to share the solution:
After I installed the old version on the server, I changed the name of the msi file. Consequently, I could not run the old version to repair/update. I could not even install a newer version over the old version, as the installer needed the old msi to uninstall the old version.
When I changed back the filename of the old version, it allowed me to install the new version.
CONCLUSION: Don't change the name of the msi file after installation.