I am trying to install MongoDB on Windows 7 Enterprise (32bit) VM running in VirtualBox on Windows7 Ultimate 64bit.
The MongoD.exe start up reports a missing Microsoft Hotfix, KB2731284. I downloaded and installed the hot fix on the VM. The hotfix was not required on the Host PC.
Mongod.exe still reported it was not installed. Ran the hotfix a second time and it reported that it was already installed.
I tried uninstalling an reinstalling mongoDB, no luck.
Stuck, any ideas?
MongoDB.com lists stackoverflow as the support portal.
per SO
I think you can run MongoDb without applying the Hotfix, but I would not recommend it. In long time you may run into problems. They have included some fixes in MongoDB to workaround the problem.
On Windows 7 and Windows Server 2008 R2 when applying the hotfix you get a better file allocation performance what is relevant for MongoDB
So when using mongo 2.6.0 there is workaround implemented.
Related
I am having trouble installing mongodb compass 1.34.0 on windows 11 and the error shows up saying "Error while validating preferences from: Command Line". Is there a solution to this?
I tried redownloading the application and restarting the laptop, however nothing changed.
I just downloaded latest version of Mongo Compass, and I had the exact same error. My solution was to download de MSI installer instead of the .exe
I have a google VM instance which was running flawlessly. It has Centos-7 and Plesk installed in it.
I just stopped it, upgraded machine type (to better CPU and RAM) and started it again. My server stopped responding at all. No websites are running, I can't connect to SSH & Google Cloud SDK Shell is unable to reach server. It says NETWORK ERROR, CONNECTION TIMED OUT. My all other instances works well.
I tried rebooting & resetting multiple times. Reading out stuff from internet since last 6 hours but for no luck. I also tried to clone disk of the instance and creating new instance with the cloned disk but for no luck. Same network connection issue. May be something in OS got corrupted? Please suggest. I have a number of websites hosted on the server which are down due to this. Thanks a lot in advance.
I took screenshot of my VM using Google Cloud Shell. It is as follows:
I connected with serial console which is as follows:
While creating a ticket with google, I found that they've posted some information under "Known Issues". I am pasting the whole stuff as there is no direct link to reach there. The symptoms they told were exactly what was happening to me:
Below is Known Issue Posted by Google:
Description:
We are experiencing an issue with Google Compute Engine instances running RHEL and CentOS 7 and 8. More details on this issue are available in the following article and bugs: https://access.redhat.com/solutions/5272311 https://bugzilla.redhat.com/show_bug.cgi?id=1861977 (RHEL 8) https://bugzilla.redhat.com/show_bug.cgi?id=1862045 (RHEL 7) Symptoms: Instances running RHEL and CentOS 7 and 8 that run yum update may fail to boot after restart with errors messages referring to a combination of: "X64 Exception Type - 0D(#GP - General Protection) CPU Apic ID", "FXSAVE_STATE" or "Find image based on IP". This issue affects instances with specific versions of the shim package installed. To find the currently installed shim version, use the following command: rpm -q shim-x64 Affected shim versions: CentOS 7: shim-x64-15-7.el7_9.x86_64 CentOS 8: shim-x64-15-13.el8.x86_64 RHEL 7: shim-x64-15-7.el7_8.x86_64 RHEL 8: shim-x64-15-14.el8_2.x86_64 Workaround: Do not update or reboot instances running RHEL or CentOS 7 and 8. If you are on an affected shim version, run yum downgrade shim\* grub2\* mokutil to downgrade to the correct version. This command may not work on CentOS 8. If you have already rebooted, you will need to attach the disk to another instance, chroot into the disk, then run the yum downgrade command. We will provide an update by Thursday, 2020-07-30 14:00 US/Pacific with current details.
Start time:
July 30, 2020 at 9:08:34 PM GMT+5
How to diagnose:
Instances running RHEL and CentOS 7 and 8 that run yum update may fail to boot after restart with errors messages referring to a combination of: "X64 Exception Type - 0D(#GP - General Protection) CPU Apic ID", "FXSAVE_STATE" or "Find image based on IP". This issue affects instances with specific versions of the shim package installed. To find the currently installed shim version, use the following command: rpm -q shim-x64 Affected shim versions: CentOS 7: shim-x64-15-7.el7_9.x86_64 CentOS 8: shim-x64-15-13.el8.x86_64 RHEL 7: shim-x64-15-7.el7_8.x86_64 RHEL 8: shim-x64-15-14.el8_2.x86_64
Workaround:
Do not update or reboot instances running RHEL or CentOS 7 and 8. If you are on an affected shim version, run yum downgrade shim\* grub2\* mokutil to downgrade to the correct version. This command may not work on CentOS 8. If you have already rebooted, you will need to attach the disk to another instance, chroot into the disk, then run the yum downgrade command.
I'm trying to install MongoDb 3.6.2 2008R2 plus on my 64bit Window 10 (build no 1709) but the setup after some time says "setup wizard ended prematurely because of an error.your system has not been modified.To. Install this program at a later time run setup wizard again.click finish button to exit the setup." Any one know any fix regarding this issue?
I solved this problem by declining to install Compass together with Mongo in the installer wizard.
I have the same issue. I solved it by choosing the following way:-
Choose Custom Installation
Uncheck Compass Installation with MongoDb
Finish the Setup
Again start setup and click on change the installation
Tick Compass Installation with MongoDb
Finish the Setup
I had same problem and solved it by removing these folders that created on previous setup and running the setup again:
%USERPROFILE%\AppData\Roaming\MongoDB Compass Community
%USERPROFILE%\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\MongoDB Inc
%USERPROFILE%\AppData\Local\MongoDBCompassCommunity
and some files like this in Prefetch folder:
C:\Windows\Prefetch\MONGODBCOMPASSCOMMUNITY.EXE-0044164A.pf
I tried the suggestion above but none works for me. Instead, I ended up downloading the archive version and extract that and place that in the folder structure below (on Windows 10, 64 bit)
C:\Program Files\MongoDB\Server\3.6.5\
Then I configured the system environment path and it works fine. As this is for testing, it would be fine for now.
I unselected ".NET Framework 3.5 (includes .NET 2.0 and 3.0)" in the Windows Features (Turn Windows features on or off). After restarting mongodb and Compass got installed successfully.
I tried to install MongoDB Enterprise 2008R2 for Windows 10 64-bit and had the exact same problem.
I already had Compass installed, so here is what I did:
Uninstall Compass
Select install when needed (this will get you to the next page where you're prompted to install Compass or not. If you choose Install Everything you WON'T get the option to NOT install Compass (the other comments here might be earlier versions of Mongo... I'm not sure).
Install
Now re-install Compass.
That fixed it for me.
My MongoDB Compass won't launch. It was working an hour ago, but now it just shows this screen forever.
I've tried rebooting. And even uninstalling and re-installing Compass. But every time I launch it, it just shows the loading screen and never proceeds. If I go to Connect > Connect to..., it just opens another window that does the same thing.
Version 1.10.9
Windows 10 x64
How can I get this program to launch correctly? What should I investigate to try to figure this out?
Had the same issue today, with the Version 1.10.9 on Mac OSX. I then reinstalled MongoDB Compass Community Edition to the latest Beta version (Version 1.11.0-beta.1), the loading proceeded and everything went fine.
Same here. I tried uninstalling/reinstalling. No joy.
I reinstalled an older version 1.8.2 which worked fine. Must be an issue with the latest release.
Edit: I upgraded to 1.10.9 this morning and reverted to 1.8.2 after coming across this issue.
After having the same issue today (november 24:th) i used the latest stable version (1.10.10) and it solved the problem. I´m on Mac OS Sierra (10.12.6).
On window 7, i found the issue was because of two reason and both were related to power shell.
First problem was because of execution policy related to power shell script, which can be solved by running the following with administrator privilege.
Set-ExecutionPolicy RemoteSigned
After this, please check the power shell version, in case you are trying to install latest version of mongodb on window 7, power cell version needs to me minimum of 3.0, in my case it was 2.0 and because of that installation was getting stuck. After upgrading power shell to latest, installation went through quickly.
I managed to surprisingly fix this issue by restarting my computer. I was on Ubuntu 18.04, Compass v1.x (somewhere this year).
I understand that the poster is on Windows but this was the first hit on Google.
This seems to be forever error, even in 3.6.3 version, that i've tried today. There are questions about the error everywhere.
The link below
Installation/Update of MongoDB 3.6.2 on Windows Hangs
explains the problem - the install trying to run execute the PowerShell script to download/install MongoDB Compass, which seems to hang due to insufficient rights.
DO NOT install Compass, or install it later with appropriate rights.
The same problem here.
My MongoDB version v4.2.1, compass-1.23 on Win 10 OS.
In MongoDB Compass screen panel, I went to View-> Toggle DevTools.
In Console section there was error indication in red :
"""Error: Command failed: powershell (...'powershell' is not recognized as an internal ..."""
Powershell can be added to environment variables paths:
Please check this:
Powershell' is not recognized as an internal or external command, operable program or batch file
So, I closed MongoDB Compass window. Then I added path to environment variables:
C:\Windows\System32\WindowsPowerShell\v1.0\
And it solved my problem.
You can also add this line too, to enable MongoDB cmd line commands (your location and version can be different):
C:\Program Files\MongoDB\Server\4.2\bin\
Please check this: How to Install MongoDB on Windows 7/8/10 | How to Install Mongo Compass as separate installer
I'm following the online installation example (https://www.youtube.com/watch?v=7ElSGLkprkY) to install PeopleSoft with PeopleTools on Windows 7 with SQLServer 2008 R2.
My PS and PT installation version differs from the online videos since I'm using most recent available versions:
PeopleSoft HM 9.2
PeopleTools 8.55
Tuxedo 12.1.3.0.0 with VS2012
WebLogic 12.1.3.0.0 64bit
JDK 7u55 x64
SQL Server 2008 R2
I could install each element with no error, excepted one VIEW during HC database creation (PS_EP_APPRMOB_PNDG), but I could re-create the view manually by slightly modifying the SQL query.
Now I'm trying to configure the Web (PIA) Server and I encounter an error while creating the domain. The piainstall_HC.log file contains following:
Tue Sep 20 09:48:32 CEST 2016:Starting PIA installation...
PS_HOME: c:\PT8.55
Install Action : CREATE_NEW_DOMAIN
Creating Domain...
Deploying Web Applications...
Deploying WebLogic Extension files...
Deploying PeopleSoft Site files...
Deploying PeopleSoft Site Doc files...
Completed.
PS_CFG_HOME: C:\PS_CFG_HOME
PIA_INSTALL_FAIL
After intensive googling, I found that some other people got a similar issue which was caused by a wrong version of the JDK: the JRockit jvm was required.
Of course I tried to use JRockit JDK 64bit, but I still get the same error. I also tried several other oracle JDK versions, among others the JDK 7u55 x64, which is provided with PeopleTools installation elements.
Unfortunately, I definitively get the same error and cannot find any other logfile which could give more information on the root cause.
Did someone experienced the same issue and could fix it ?
Thanks for help
I finally could fix the issue.
It seems that my error was to install the wrong weblogic version: originally, I installed weblogic by using the "setup_fmw_12.1.3.0.0_ohs_win64.exe" installer which was provided with PeopleTools.
It appears that the other one (fmw_12.1.3.0.0_wls.jar) was expected. After installing this version (with "Coherence"), the domain could be created successfully.