Jump to content

WAS service was unable to start with error "Cannot create a file when that file already exists."

Featured Replies

Posted

Symptom

 

 

 

We had an issue where IIS was throwing below error.

 

 

 

Creating an instance of the COM component with CLSID from the IClassFactory failed due to the following error: 800700b7

 

 

 

Please find below screen shot for reference.

 

 

 

 

570x257vv2.png.1e63f4bd01c7d6e7eb92e33c10104cc5.png

 

 

WAS service was unable to start with error "Cannot create a file when that file already exists".

 

 

 

Please find below screen shot for reference.

 

 

 

mediumvv2px400.png.77f96329d906bce5bed37b08af5b975e.png

 

 

 

Cause

 

 

 

Duplicate schema configuration xml file exists in "C:\Windows\System32\inetsrv\config\schema" folder.

 

 

 

Please find below screen shot for your reference.

 

 

 

mediumvv2px400.png.e16ee9f7930560535c878c5e256c02ab.png

 

Resolution

 

 

 

Remove the duplicate schema configuration xml file from "C:\Windows\System32\inetsrv\config\schema" folder and restart WAS service.

 

 

 

In this example, please remove the below highlighted files from "C:\Windows\System32\inetsrv\config\schema" folder.

 

 

 

 

 

mediumvv2px400.png.80f07af6d4e5ed04b2870bd750925067.png

 

NOTE: This same error shown when WAS fails to start can happen for different but similar schema file related issues, so it is imperative to identify which schema file is causing the issue - and Procmon trace can help with that.

 

Continue reading...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...