Jim Nicolis
asked on
WIndows 2008 R2 server wont install .NET Framework
Hello All,
I have a 2008 R2 Server that I am trying to put the new Server Version of MYOB on over the weekend
I hit a hurdle and now can not work out why
MYOB need to install the latest version of Dot net Framework on as it does during the install
This Failed and would not install
I then had a look at the server and found there were some updates needed, which included some dot net stuff
I ended up installing them but the dot net ones failed
I then Proceeded to try and install all the dot net Framework from Manual Download
This has failed as well
Not sure where to next
Please help, customers has now got 6 people not on the server at moment doing nothing...so you can imagine how happy they are
Thanks Adam
I have a 2008 R2 Server that I am trying to put the new Server Version of MYOB on over the weekend
I hit a hurdle and now can not work out why
MYOB need to install the latest version of Dot net Framework on as it does during the install
This Failed and would not install
I then had a look at the server and found there were some updates needed, which included some dot net stuff
I ended up installing them but the dot net ones failed
I then Proceeded to try and install all the dot net Framework from Manual Download
This has failed as well
Not sure where to next
Please help, customers has now got 6 people not on the server at moment doing nothing...so you can imagine how happy they are
Thanks Adam
Try .NET Framework Setup Verifier
http://blogs.msdn.com/b/astebner/archive/2008/10/13/8999004.aspx
http://cid-27e6a35d1a492af7.skydrive.live.com/self.aspx/Blog%7C_Tools/netfx%7C_setupverifier%7C_new.zip
See if it can correct what is already installed and then try the manual download again.
Remember this Server is out of support.
http://blogs.msdn.com/b/astebner/archive/2008/10/13/8999004.aspx
http://cid-27e6a35d1a492af7.skydrive.live.com/self.aspx/Blog%7C_Tools/netfx%7C_setupverifier%7C_new.zip
See if it can correct what is already installed and then try the manual download again.
Remember this Server is out of support.
ASKER
I have Downloaded and run Verifier and it has come back saying all version from 2.0 to 4 are installed and correct but its the stuff after that which I am having issues with
And yes we are moving these guys to new 2016 server but just need to sort this one now
And yes we are moving these guys to new 2016 server but just need to sort this one now
Have you tried to restart the server before you install the latest version of .NET?
ASKER
Yes
This is a screenshot of what happens when I try and install 4.5.2 Full
Error-after-install-of-4.5.2-Full.png
This is a screenshot of what happens when I try and install 4.5.2 Full
Error-after-install-of-4.5.2-Full.png
If the Verifier did not work, you have bigger problems and probably need to speed up the new server.
Some risk here: Can you remove .NET Framework ? Programs and Features, Windows Features (different name in Server 2008), restart and re-enable .NET ?
Can you temporarily mount MYOB on a solid personal computer with its database and access it from there?
Some risk here: Can you remove .NET Framework ? Programs and Features, Windows Features (different name in Server 2008), restart and re-enable .NET ?
Can you temporarily mount MYOB on a solid personal computer with its database and access it from there?
ASKER
The Verifier worked fine its just when i go to install the next version as per last image
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
+1 for the MS .NET repair tool.
Aside from that I would run DSIM repair tools:
In addition to the above scanning/restoring, I would check the health of WIM:
Aside from that I would run DSIM repair tools:
Dism /Online /Cleanup-Image /ScanHealth -- This scans the health
Dism /Online /Cleanup-Image /RestoreHealth -- Restores health
Dism /Online /Cleanup-Image /SpSuperseded -- Rolls up any servicepacks and makes the install permanent
Dism /Online /Cleanup-Image /StartComponentCleanup -- Cleans up installer files and makes them permanent
In addition to the above scanning/restoring, I would check the health of WIM:
winmgmt /verifyrepository -- If it fails, do the following
winmgmt /salvagerepository -- This will repair it.
winmgmt /verifyrepository --- to check again wmi repository had been repaired successfully
https://docs.microsoft.com/en-us/dotnet/framework/install/troubleshoot-blocked-installations-and-uninstallations