I have been trying for a couple days to get Windows Management Framework 3.0 to install on my Windows 7 Enterprise, SP1 desktop machine. The installation seems to go fine, and at the end it requests a reboot as it should. After the reboot, it says installation has failed and rolls everything back out.
In the System Setup Logs it shows the following error:
Package KB2506143 failed to be changed to the Installed state. Status: 0x80070005.
I definitely meet the pre-requisites. I have uninstalled .NET 4.5 and 4.0 and re-installed both, with reboots in between. It always comes back with that same error.
Any ideas?
Make sure you run the installation as Administrator. It's not sufficient to be logged on with an account that has local admin privileges; you need to select Run as administrator from the context menu, or run it from an elevated command prompt. I ran into that error the first time I tried to install Management Framework 3.0 by just double-clicking the downloaded .exe file. It worked when I launched it from an elevated prompt (Run as administrator would have the same effect).
For me the problem was the .Net Framework WoW64 features were missing. More specifically mscoree.dll couldn't be found. Installing the NetFx2-ServerCore-WoW64 & NetFx3-ServerCore-WoW64 features fixed the problem for me.
http://josheinstein.com/blog/2011/09/solved-this-program-cant-start-because-mscoree-dll-is-missing-from-your-computer/
Related
I have removed .Net Framework feature from "Server Manager -> Remove Roles and features Wizard".
(This image is from a different server)
Later I noticed that this activity has affected many windows features (Server manager, IIS Manager, Turn on off windows features etc..).
After removed .Net Framework feature I was not able to find the Server Manager application.
I tried answer in this link and able to restore ServerManager.exe but once I try to load the server manager it's giving below error,
I may be able to resolve this if I can re enable .Net frame work feature. But not sure how to do that without using server manager(since I cannot open sever manager).
Appreciate any solutions or suggestions regarding this.
Finally able to re enable .Net feature and access server manager by following below steps,
Open command prompt
Run the command: dism /online /enable-feature /featurename:NetFx4ServerFeatures /ALL and press return.
Type PowerShell and press enter.
Run the command: Install-WindowsFeature PowerShellRoot,PowerShell,PowerShell-ISE.
Restart the server.
Credit belongs to this blogger:
https://glennopedia.com/2020/02/14/why-you-shouldnt-remove-net-in-windows-server/
This kind of errors are caused due to lack of .NET framework on your machine or if you installed old version of framework. You need to install an appropriate .NET Framework on your computer.
Updating .NET framework on your computer will solve your problem maximum.
Install it from the Microsoft website.
Run as Administrator , the server manager will open.
Now you can try to add.
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 am using Visual Studio 2015, on Windows 10 - I am having an issue running the Nuget Console, it wants Powershell 2.0. I do infact have powershell installed, but its version 5.0
I don't really understand why 5 wouldn't be compatible with 2? or why nuget cant find 5 when 2 is not installed?
I've tried install 2, didn't work
I've tried the usual change permissions for nuget package signing, didn't work either
Any one got a suggestion? I'm sure it must be possible!
I need to download the latest Google Custom Search API, and it seems that Nuget is the only way to do it, but if not, then a link to direct download of the API would be just as useful for now! (I've got almost everything from google API, except search lol)
I've also tried installing the (Google Search API) packages manually via PowerShell 5.0, but it cant find them, as far as I am aware, the repositories should already be added, but perhaps not?
Full Error Message:
Error: The Package Manager Console requires PowerShell 2.0 runtime, which is
not detected on this machine. Please install the PowerShell 2.0 from
support.microsoft.com/kb/968929 and restart Visual Studio
You need to install Powershell 2.0. On Windows 10 you can follow these steps:
Go to This Pc
Click Uninstall or change a program on computer tab
Click Turn Windows features on or off
Mark Poweshell 2.0 for installation
Click OK
Or open powershell as admin and :
PS> Install-WindowsFeature PowerShell-V2
I built a .Net 2.0 Application for Windows XP but I made it in Windows 7.
The application contains a Mysql.data connection and CrystalReport. When I try to run it on Windows XP, the application does not run, giving an error message of:
The application failed to initialize properly (0xc000007b).
I tried to rebuild application in Windows XP, but when I rebuilt and ran it in Visual Studio, the following error occurs:
Could not load file or assembly or one of its dependencies. The module was expected to contain an assembly manifest.
How can I fix this?
Please try the following:
1.Uninstall the .NET Framework 3.5 from Add/Remove Programs (in the Control Panel) on Windows XP or Programs and Features on Windows Vista/Windows 7.
Even if the uninstall fails, go on to step 2.
2.After the Framework 3.5 has been uninstalled or if it failed, download and run the .NET Framework removal tool.
Here's the link to Aaron Stebner's Framework Removal tool on Windows Live Skydrive:
http://cid-27e6a35d1a492af7.skydrive.live.com/self.aspx/Blog_Tools/dotnetfx_cleanup_tool.zip?wa=wsignin1.0&sa=17797669
Aaron Stebner is a Microsoft employee. The tool he's developed is linked on that page and makes easy work of cleaning up damaged .NET Frameworks from your system so they can be reinstalled. When you run the tool, choose the .NET Framework 3.5 from the list and choose to cleanup. After this is done, reinstall the .NET Framework 3.5 that Design 3 needs by running the Expression Design 3 setup package again. It will detect that the .NET Framework 3.5 is missing and reinstall it for you. After that's done, try running Design 3 again.
3.If that still fails to resolve the problem, go to START, RUN and type CMD to run a command prompt. Type CHKDSK /R and hit ENTER. Hit the letter Y and restart the machine. Allow the machine to do the check disk scan. After this is done and it goes back into Windows, try Expression Design again.
more information here
I am running tests successfully on Windows XP but not even got a single successful build while running through Windows 2003.
Any one knows whether it is compatible or not as I read on some site that WatiN is fully tested on XP and not on other Windows editions.
I'd ordinarily post this as a comment on Sam's answer, but I'm trying to make a stack trace searchable, so here goes...
WatiN.Core.Exceptions.IENotFoundException : Could not find an IE window matching constraint: Timeout while waiting to attach to newly created instance of IE.. Search expired after '30' seconds.
at WatiN.Core.IE.CreateIEPartiallyInitializedInNewProcess()
at WatiN.Core.IE.CreateNewIEAndGoToUri(Uri uri, IDialogHandler logonDialogHandler, Boolean createInNewProcess)
at WatiN.Core.IE..ctor(String url, Boolean createInNewProcess)
c:\...\WithVendorSite.cs(42,0): at WithVendorSite.VerifyCanLogIn(TargetSite target)
I developed my test on Windows 7 against WatiN 2.0.10.928 but the test was continually getting stuck with a blank browser with about:blank in the address bar when run on Windows Server 2008 with latest WUs, and Enhanced Security Configuration turned off and running the tests elevated (Run as Administrator).
The problem in my case (thanks Sam) was the absence of Microsoft.mshtml.dll in the bin directory (I had figured out Interop.shdocvw.dll was necessary from error messages I'd encountered on the Windows 7 side).
After adding Microsoft.mshtml.dll, things run happily with ESC turned back [but the test process needs to run elevated].
I run our WatiN integration test suite (hundreds of tests) on Windows 2003 with IE6. Works fine, no special tricks done. What is the exception you are getting? Are you sure mshtml.dll (the COM dll somewhere in the windows directory) is registered correctly on this machine? Do you have the Microsoft.mshtml.dll (interop assembly) and interop.shdocvw.dll in the same directory as WatiN.Core.dll?
Update: Its officially supported, from the faq
Which windows versions are supported?
Windows 2000, Windows XP, Windows 2003
and Windows 2008.
Original post:
I use it on vista all the time. I haven't used it on windows server 2003 though.
Have you tried logging on interactively into the server and trying to run the tests manually? It may be because of the account that your build server is running under or some particular security settings you have setup. Have you checked to see if IE is stopping you from viewing the page due to it not being in the trusted sites list?
I was using Watin 1.3 on Windows XP but the same on Win 7 having problem....
Officially Watin 1.3 works on O.S. Xp and earlier on Win XP
But Watin 2.1 works fine on Win 7 and XP.
Officially Watin 2.1 supports any Microsoft O.S.