Site in IIS has been invalidated

We are running a web farm with SharePoint 2007 and now one server
displays an error message when I try to create or extend a web
application, "The system cannot find the path specified."

In the event log an error message shows up when I restart the IIS
"The virtual site '951338969' has been invalidated and will be ignored
because valid site bindings could not be constructed, or no site
bindings exist."

In the IIS Manager there are two sites that seems to be corrupt, there
is an exclamation mark in front of each, http://img516.imageshack.us/img516/6555/iis3yn0.jpg

So I guess something in the IIS is messed up. Unfortunately I have no
backup of the metabase.

My question is, is there a way to restore the virtual sites, if I can
somehow find out why the site is invalidated? I don't know the purpose
of the corrupted sites, if someone tried to add them or of they are
existing sites that are messed up. The SharePoint installation works
fine right now, and the corrupted sites are only visible on one
server, the admin server in the SharePoint farm.

Re: Site in IIS has been invalidated

Does the path still exist?

How about for virtual paths?

And, on the primary web site? Do they work there too?

Sounds like someone deleted or moved your SharePoint Extensions folder where
that stuff gets mapped.

"Zodi" wrote in message
news:1183358541.844264.127110@q75g2000hsh.googlegroups.com.. .
> We are running a web farm with SharePoint 2007 and now one server
> displays an error message when I try to create or extend a web
> application, "The system cannot find the path specified."
>
> In the event log an error message shows up when I restart the IIS
> "The virtual site '951338969' has been invalidated and will be ignored
> because valid site bindings could not be constructed, or no site
> bindings exist."
>
> In the IIS Manager there are two sites that seems to be corrupt, there
> is an exclamation mark in front of each,
> http://img516.imageshack.us/img516/6555/iis3yn0.jpg
>
> So I guess something in the IIS is messed up. Unfortunately I have no
> backup of the metabase.
>
> My question is, is there a way to restore the virtual sites, if I can
> somehow find out why the site is invalidated? I don't know the purpose
> of the corrupted sites, if someone tried to add them or of they are
> existing sites that are messed up. The SharePoint installation works
> fine right now, and the corrupted sites are only visible on one
> server, the admin server in the SharePoint farm.
>

Re: Site in IIS has been invalidated

I removed the site 951338969 from the metabase.xml and now everything
seems to work fine. I'm just a little bit unsure if it really does.
The SharePoint Extensions folder is still there and the primary web
site works fine.

On 2 Juli, 16:08, ".._.." <....@yourmom.mil> wrote:
> Does the path still exist?
>
> How about for virtual paths?
>
> And, on the primary web site? Do they work there too?
>
> Sounds like someone deleted or moved your SharePoint Extensions folder where
> that stuff gets mapped.
>
> "Zodi" wrote in message
>
> news:1183358541.844264.127110@q75g2000hsh.googlegroups.com.. .
>
> > We are running a web farm with SharePoint 2007 and now one server
> > displays an error message when I try to create or extend a web
> > application, "The system cannot find the path specified."
>
> > In the event log an error message shows up when I restart the IIS
> > "The virtual site '951338969' has been invalidated and will be ignored
> > because valid site bindings could not be constructed, or no site
> > bindings exist."
>
> > In the IIS Manager there are two sites that seems to be corrupt, there
> > is an exclamation mark in front of each,
> >http://img516.imageshack.us/img516/6555/iis3yn0.jpg
>
> > So I guess something in the IIS is messed up. Unfortunately I have no
> > backup of the metabase.
>
> > My question is, is there a way to restore the virtual sites, if I can
> > somehow find out why the site is invalidated? I don't know the purpose
> > of the corrupted sites, if someone tried to add them or of they are
> > existing sites that are messed up. The SharePoint installation works
> > fine right now, and the corrupted sites are only visible on one
> > server, the admin server in the SharePoint farm.