On a Server 2008 R2 system I ran the compatibility troubleshooter to try and get an older application working, and it said that an error had occurred. It gives error codes 0x80004005, and 0x800B010E. What could be causing this? Thanks

Hi Kettch, Where did you obtain the Compatibility Troubleshooter, from Control Panel\All Control Panel Items\Troubleshooting\Programs? The errors could be tied to the application that you are trying to make it work. What is the application that you would like to run? What’s the exact error you received when you tried to run it in Windows Server 2008 R2? You may try to run it in a clean boot environment and see whether it works. Please follow the steps below to perform a clean boot. A clean boot helps eliminate software conflicts. Click Start, type msconfig in the Start Search box, and then press ENTER. If you are prompted for an administrator password or for a confirmation, type the password, or click Continue. On the General tab, click Selective Startup. Under Selective Startup, click to clear the Load Startup Items check box. Click the Services tab, click to select the Hide All Microsoft Services check box, and then click Disable All. Click OK. When you are prompted, click Restart. After the computer starts, start the installation of the features and check whether the problem is resolved. Please also disable the anti-virus software in case of any failures. After you have finished troubleshooting, follow these steps to reset the computer to start as usual: Click Start, type msconfig.exe in the Start Search box, and then press ENTER. If you are prompted for an administrator password or for confirmation, type your password, or click Continue. On the General tab, click the Normal Startup option, and then click OK. When you are prompted to restart the computer, click Restart. Additionally, please also consult the application vendor about the compatibility issue of this application. Regards, Karen JiPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. This posting is provided "AS IS" with no warranties, and confers no rights.

Some older applications may not work simply because of directories they try to write to. You can always right-click the file, go to properties, and go to the compatibility tab. On this tab you can specify the Operating System you know works. Also, does the application work if you run it as administrator? Another item to check is whether or not the Manufacturer has an update available that will enable it to work with newer Operating Systems.View my MCP Certifications

It doesn't have anything to do with the application. No matter where I start the troubleshooter from, it still comes up with the same error. A clean boot did not help.

Ah, thanks for the clarification. Can you verify that all services with a startup of Automatic are running. Not all services will stay running, but it'd be nice to know which ones aren't. Also, make sure the Operating System is fully patched.View my MCP Certifications

I've been through all of these particular possibilities. The install is relatively fresh and fully patched. All services are running properly.

Hi Kettch, Do you mean that it's not related to the application? If you run the compatibility troubleshooter, it will always give you this error? If that is the case, I'm afraid you'll have to perform an in-place upgrade because there might be some corrupt system files. It would be nice if you can find any event errors in the event log for further troubleshooting. To perform an in-place upgrade of Windows Server 2008 R2, follow these steps: Insert the Windows Server 2008 R2 installation CD/DVD, then double click to run the Setup from CD/DVD. Choose the language and click Install Now. Accept the License Agreement and Choose Upgrade. Select the same edition of Windows Server 2008 R2 that is installed on server. (Please make sure you have enough space in your System drive.) Regards, Karen Ji Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. This posting is provided "AS IS" with no warranties, and confers no rights.

Hi for me it does not work. I have tried disabling the services as explained here. still when running prgoram compatibility I get the error 0x800B010E. any idea?

Please create your own thread describing your problems rather than appending them to someone else's. Through step-by-step analysis, you may have a very different issue.View my MCP Certifications

Sorry for the delay, but I was finally able to do an in-place upgrade. However, that did not fix the problem. Does anybody have any other ideas? This is a very delicatly configured server, and if I have to wipe it and reinstall from scratch it will take a week of angry-customer-downtime to get it back to where it needs to be. There is nothing in any of the event logs, and it is not application specific.

Have you tried contacting the vendor of the application? Through speaking with them, you should be able to find out how exactly the application works including files and folders it writes to. I have seen many legacy applications require Users to have modify writes to the directly in which the application is installed. Sadly, this is horrible for security.View my MCP Certifications

It's not application specific. It returns the error regardless of which application it is run on. Another thing that we just discovered this morning is that the problem has also broken the network diagnostic wizard.

Try SFC /SCANNOW at an elevated command prompt. Something sounds very off with the installation. For the installation media of Windows Server, did you use installation media provided by Microsoft?View my MCP Certifications

I'll try the scan a little later when I have time to work on it. Right now, I can say that I used a fresh Genuine disc from Microsoft. The odd thing is that it was working before.