Wow! This error was a persistent error. Tried so many things to fix this. Uninstalled .net, ran a uninstall cleaner, ran a registry cleaner(three different ones) and nothing worked! I finally came across a very helpful post, Google searched Office 2010 Error 1935. Second Page (I know right, you got to be desperate to go to the second results page) and BAM! there was the EASIEST fix I have done, and this one worked for me!
*Disclaimer, this post is without warranty, etc. etc. I am not responsible for your computer crashing, or you losing all your pictures and documents, try this at your own risk.*
Step 1: Windows+R>regedit then hit enter
Step 2: Locate HKCU\Software\Microsoft
Step 3: Locate Key/s named Office and/or OfficeSoftwareProtectionPlatform (only Office was listed for me)
Step 4: Delete key/s, then reboot, install office and profit!
Again, this was my experience and this worked for me. Mileage may vary. Good luck, and happy troubleshooting!
Big thanks to Sammit over at http://sammit.net/how-to-fix-error-1935-when-installing-microsoft-office-2007-or-2010/ for posting this easy solution and saving the day!
-Oscar
Update 1: I had to disabled Ad Aware Anti-Virus as it was causing issue with installing certain programs. Ended up removing it all together and going a different route. Make sure you disable antivirus as well to see if that is the issue.
Sunday, December 28, 2014
Friday, December 26, 2014
DCPROMO fails with: 'Failed to configure the service NETLOGON as requested' Server 2003
We have been working with a client on getting rid of the 2003 domain controllers. Came across one domain controller that wouldn't demote. Ran dcpromo and got this:
The operation failed because:
Failed to configure the service NETLOGON as requested
The reason for my clients failure was because the primary DNS server was the server itself. So DC1 with an IP of 10.0.0.0, had the first DNS entry as 10.0.0.0.
After I changed it to the new DNS server IP, I ran dcpromo again and it worked like a charm, no reboot needed. I did do a ipconfig /flushdns, just because though. Also, according to Microsoft you should not have a domain/DNS server pointing to itself as the first entry. The first DNS entry should be another DNS server, and use the local host address of 127.0.0.1 as the second entry. I won't go into detail as why, but a quick search should give you all you need. Enjoy!
The operation failed because:
Failed to configure the service NETLOGON as requested
The reason for my clients failure was because the primary DNS server was the server itself. So DC1 with an IP of 10.0.0.0, had the first DNS entry as 10.0.0.0.
After I changed it to the new DNS server IP, I ran dcpromo again and it worked like a charm, no reboot needed. I did do a ipconfig /flushdns, just because though. Also, according to Microsoft you should not have a domain/DNS server pointing to itself as the first entry. The first DNS entry should be another DNS server, and use the local host address of 127.0.0.1 as the second entry. I won't go into detail as why, but a quick search should give you all you need. Enjoy!
Subscribe to:
Posts (Atom)