When I run the installer, on the third stage it gives the error "The drive or UNC share you selected does not exist or is not accessible. Please select another". I tried pasting the installed to another drive but it didn't work. There's no option to choose installation drive while installing.
Related
I have downloaded the .msi multiple times and tried to run in a variety of ways, however, I cannot install MongoDB on my windows 10 machine. When I click the .msi, I get the first "preparing to install" pop-up and then it just goes away. Nothing happens.
I tried downloading the zip folder which contains a bunch of .exes.. but still nothing. I'm not sure how to get this to work on my local.
Thoughts?
For some reason, the latest documentation doesn't include the manual installation process.
Download the distribution ZIP and extract it to c:\mongodb\ or equivalent.
Then from the resultant bin directory you can run an administrative powershell command (be sure to replace the paths with real paths that exist on your system):
PS C:\mongodb\bin> ./mongod.exe --install --logpath="c:\\path\\to\\logfile.log" --dbpath="c:\\path\\to\\data\\on\\disc"
This will create a windows service named "MongoDB" which should start automatically. If it doesn't, you can run net start MongoDB from your admin PS prompt.
Please download Mongodb from there official sites and also there is a very easy guide to install the mongodb on various OS.
Reference:- https://docs.mongodb.com/manual/tutorial/install-mongodb-on-windows/
While trying to install Tableau, I'm getting the following error:
0x80070666 Another version of this product is already installed. Installation of this version cannot continue.
Try the following:
Computer -> Uninstall or change a program, find Tableau and remove it
Go to the drive where you install the Tableau and delete the folder (If you are using Windows try the following path: C:\Program Files\Tableau or C:/Program Files (x86)/Tableau). This is because even if you removed the program, there are still some remaining files stay in the Tableau folder.
Hope that helps!
We have a VSTO Application that is installed on many machines. If the Add-In is already installed, there is no issue. If you try to uninstall or install, you get the following error message:
The following Microsoft Office solution cannot be installed due to a general installer error: App_Name.vsto
0x80070002
This application has been working without hiccups for almost a year now. Our Sys Admin and I believe we've narrowed it down to a mandatory Windows 10 update as our base Windows 10 image has it working fine and it works on Windows 7 no issue. However, the update is already pushed out and nothing is showing up in the logs.
I know the VSTOInstaller.exe.Config file has been the cause for several of these installer issues, however I cannot find that file on any of our machines even though I KNOW I modified one machine and changed the name to VSTOInstaller.exe.Config.Old for the Business.fba error some have gotten. I assume an update somehow packaged the config file into the .exe.
The Windows 7 machines also don't have the Config file as well...
What we've tried:
Searching for an older .Config file to place in the folder
Rolling back to a previous version
Recompiling
Changing the publish destination folder and setting version back to version 1.0.0.0
Update: Placing a VSTOInstaller.Exe.Config then a VSTOInstaller.Config in the C:\Program Files\Common Files\microsoft shared\VSTO\10.0 folder
Update: Running repair then doing an uninstall/reinstall on Visual Studio Tools for Office Runtime (x64) program from Control Panel.
Update: Cleared Application Event Log
Update: Stopped Windows Update service, Renamed C:\Windows\SoftwareDistribution folder to C:\Windows\SoftwareDistributionOld, then restarted the Windows Update service.
I'm at a loss. Any help is GREATLY appreciated.
If anyone has the VSTOInstaller.exe.Config file, I'd love to try and place that in the folder to see if it works.
Version:
Word Version - 16.0.6769.2040
VS Version - 14.0.25420.1
OS Version - 1511 (OS Build 10586.494)
Turns out the error was part of a Microsoft Office update. Unsure if somehow the update listed in the question updated Office 2016 in the background somewhere.
The steps to resolution were as follows:
Uninstall O365 from the Control Panel
Download the a full removal tool and run it from https://support.office.com/en-us/article/Uninstall-Office-2016-Office-2013-or-Office-365-from-a-PC-9dd49b83-264a-477a-8fcc-2fdf5dbf61d8
At this point after those have ran, uninstall the add-in if it was installed.
Reinstall O365
Reinstall/Install the VSTO Add-In
Easier resolution than I thought and really appreciate all the assistance.
Windows 10 Update error 0x80070002 or 0x80070003
Step 1: Windows Service Checklist:
Open Windows services.msc, check the following services status (If it is different set it to the recommended settings)
[enter image description here][1]
Disable any third party antivirus applications, as it may block the Windows 10 upgrade process.
Step 2: Reset Windows updates:
Resetting windows updates, in this step we will clean up old failed updates that have been saved in the computer, let start by first disabling the windows update service.
Service Status(Start/Stop/Blank) Automatic/manual/Disabled
Background Intelligent file Transfer Started Automatic
Crytographic Service Started Automatic
DCOM service Started Automatic
RPC Started Automatic
Windows Modules Installer Started Automatic
Windows Update Started Automatic
Windows defender Blank Disabled
Windows firewall Blank Disabled
Disable Windows update service and stop the service
Now open Run command and type %windir%
Check for Software distribution folder delete the folder. (If it fails restart the computer, then try deleting it)
In Run command window type “cleanmgr” to launch disc cleanup to clean old junk files.
Restart the windows update service set it Automatic. Once completed, the windows upgrade error code 80070002 should be resolved. Try the upgrade now. Still unlucky, get in touch with us or proceed to next step
Step 3: Dism/Readiness Tool
This step is to fix core Operating system files that are corrupted and is affecting the Windows 10 upgrade and causing the error. Most of the cases running the tool or the command will fix the corrupted files, there are cases where some stubborn files remain. We can assist you in repairing them manually, post the log to us so we can check and revert back to you.
Depending on the OS, you have to choose proper tools,
For Windows 8 and higher use the following command in elevated command prompt.
Dism /Online /Cleanup-Image /ScanHealth
For windows 7: Download and run windows update readiness tool
microsoft.com/en-in/download/details.aspx?id=20858 –X64
microsoft.com/en-in/download/details.aspx?id=3132 – X86
Check the logs for the above tools in the following location
%windir%/logs/cbs
Post the log for further steps.
Please refer to this link for more info :
http://www.msofficelivesupport.com/windows-update/windows-10-update-error-0x80070002-or-0x80070003/
I'm on a Windows 7 (64-bit) box and do not have admin rights.
It appears from the MongoDB download page (see http://docs.mongodb.org/manual/tutorial/install-mongodb-on-windows/) that the latest version only an MSI install is available (no zip version).
I tried running the 3.0.4 MSI. I clicked custom so I could change the directory to install to. I used %USERPROFILE%\MyProgs\MongoDB-3.0.4, so no admin rights would be needed. It ran for a bit but then prompted me to enter admin credentials. I hit escape (like clicking on X at top right) to close the window. On other MSI installs this has worked. I tried it again and clicked "No" but in both cases received the message
MongoDB 3.0.4 2008R2Plus SSL (64 bit) setup was interrupted.
Your system has not been modified. [...]
This article does a GREAT job going through how to install MongoDB on Windows:
How to install mongoDB on windows?
My observation is that v2.4.14 is the last version that is available via the ZIP format. So for now, I'm using that version.
Is there any other way to install the MongoDB version 3.X MSI without admin rights?
NOTE: On the MongoDB Download page https://www.mongodb.org/downloads there is a link titled View Build Archive (it sends you here https://www.mongodb.org/dl/win32/x86_64-2008plus-ssl, and that site lists *.zip formatted files). I thought I had found my own solution to the question, but when I unzipped the files, and added the "bin" to my path and ran the programs (mongo, and mongod) I received an Windows Dialog that says:
mongod.exe - System Error
The program can't start because LIBEAY32.dll is missing from your
computer. Try reinstalling the program to fix the problem
I stopped here and posted this question. Thanks for any help.
For now I'm using the version that supported the zip format (v2.4.14) and that version does work.
NOTE2: The v2.4.14 zip formatted install doesn't have a file named LIBEAY32.dll), or I might have tried using that file with the newer version.
Yes, it is possible to install the latest MSI (including the one with SSL) without admin rights via command line.
msiexec /a mongodb-win32-x64-3.2.5.msi /qb TARGETDIR="C:\MongoDB"
This will copy the binaries into C:\MongoDB\MongoDB\Server\3.2\bin
I dislike long paths like that, so I create a symlink inside the folder:
cd C:\MongoDB
mklink /j bin C:\MongoDB\MongoDB\Server\3.2\bin
That will create a soft link as C:\MongoDB\bin (which you can add to your PATH environment variable).
mongo --version
mongod --version
Both should return version 3.2.5.
You can do this with most packages, we have to do similar with Python 2.7 and Node 4.4.3 MSI packages on work computers that do not have admin rights.
You can download the "legacy" version which is the unsigned non msi version as a zip. The disclaimer is listed as
The 64-bit legacy build does not include SSL encryption and lacks
newer features of Windows that enhance performance. Use this build for
Windows Server 2003, 2008, or Windows Vista
The 3.0.5 version is https://fastdl.mongodb.org/win32/mongodb-win32-x86_64-3.0.5.zip
The latest version is available as zip download.
[https://www.mongodb.com/dr/fastdl.mongodb.org/win32/mongodb-win32-x86_64-2008plus-ssl-4.0.6.zip/download][1]
Download and Unzip into folder where user has permissions e.g c:\users\xxx\mongodb.
Enter the path to bin folder (e..g c:\users\xxx\mongodb\bin) into the
environment variable 'PATH'. To access path variable press Win + R
and then enter rundll32 sysdm.cpl,EditEnvironmentVariables.
Select Path and click edit. Then enter new and there enter the path
to bin folder. Click OK and OK to save and exit.
Check Mongo version from command line using command mongo --version.
Note: Don't forget to create db folder in C drive that is required for mongo to work locally. All set.
I have installed a xampp portable package on my drive D, added the php folder path inside it on the system environment so I would be able to run php basically anywhere from the command line. but when i try to check if its working by executing the "php -v" command, it runs but i get this following error/warning messages.
"Warning: PHP Startup: Unable to load dynamic library 'xampp-portable\php\ext[:any].dll - The specified module could not be found."
*the [:any] there just means some dll filename.
and i get a lot of that warnings with just varying dll filenames,
anyway, here's the catch. when i do change my current path in the command line to somewhere in drive D, and then run the same command "php -v" it runs smoothly.
so what configuration should i do to fix this problem?
by the way, i do the same with mysql, putting its bin directory path on the system enviroment, run it in both inside drive C and drive D. and it runs smoothly. so i guess this problem is only on php.
I've posted the same question in xampp forums and this is the answer that was given to me. I'll be quoting the answer as it was and give credit to the one who answere it.
XAMPP is very proud that it don't have to set any environment
variables or registry values.
What you want to do is not possible with XAMPP portable without
mapping to a specific Drive letter. All configurations in xampp
portable have relative paths, so if you want to use cli from a
different drive letter, php can be executed, but all extensions of
them throw errors.
I would install the full version of XAMPP, map it to the current drive
letter with help of the setup_xampp.bat file and use the XAMPP control
panel Shell instead of default command line (advantage: The XAMPP
control panel shell sets local include paths to the needed XAMPP
folders).
Works for me (i can even use pear, git, composer, and other cli
scripts with the Xampp Shell if correct integrated).
best wishes, Altrea
credits to Altrea
Open your php.ini file, replace all relative paths to absolute paths. Eg: \xampp\ to C:\xampp\