Deploying to IIS - HTTP Error 503. The service is unavailable.

[Chris Swain]

I've followed the instructions at:

http://ravendb.net/documentation/docs-deployment-iis

but when I try to browse to the Raven web site I created, I get the
error:

HTTP Error 503. The service is unavailable.

I'm trying to run this on Windows 7 Ultimate. I did exactly what the
instructions said including modifying the applicationhost.config file
so that my RavenApplicationPool is alwaysrunning.

Has anyone else had this problem? Did I miss a step?

The site runs fine when I manually kick off the Raven.Server.exe.

[Ayende Rahien]

What do you see in the event log?

[Chris Swain]

It doesn't look like anything is getting logged in the Event Viewer.

> > The site runs fine when I manually kick off the Raven.Server.exe.- Hide quoted text -
>
> - Show quoted text -

[Ayende Rahien]

Hm...

503 usually means something pretty catastrophic just happened.

Can you revert any changes that you made to applicationhost.config and see if this helps?

[Chris Swain]

I reverted my changes to the applicationhost.config file. Changed the
app pool to ASP.NET v4.0. Still getting the 503 error. I recreated
the RavenApplicationPool app pool, set it to v4.0 framework version.
Still doesn't work.

Could this be a windows 7 thing?

> > > - Show quoted text -- Hide quoted text -

[Ayende Rahien]

No, I am running is on Win7 as well

[Chris Swain]

This is odd, then. I wonder if it would be benefitial to have a step
by step blog post showing how to create the site and app pool, create
any new users, set permissions, etc?

[Ayende Rahien]

Can we schedule a Skype call about this later today (in about 6 - 8 hours)?

[Chris Swain]

Got it working! Not sure why, but when I tried changing the port for
the Raven site to 8888 instead of 8080 the site worked. As far as I
know, I don't have any other sites registered to use port 8080, so
that is still a mystery. But at least the Raven IIS service is
running now.

[Ayende Rahien]

Great!

[slav]

I encountered the same problem. Things broke when I launched Raven
server from command prompt.

When you do that, Raven reserves http namespace for that port using
"netsh", and that prevents IIS from being able to handle requests to
this port.
See:
http://msdn.microsoft.com/en-us/library/ms733768.aspx
http://blogs.msdn.com/b/drnick/archive/2006/10/16/configuring-http-for-windows-vista.aspx

for more info on what it is.

All you have to do is delete the reservation using something like
"netsh http delete urlacl http://+:8080/" assuming the port you're
having problems with is 8080 and that should fix the problem
You can also see all registrations with "ntsh http show urlacl". If
there's a registraton for the port you want to you, you'll run into
503 error.

Hope this helps.

On Jul 25, 3:32 pm, Chris Swain <chrisasw...@gmail.com> wrote:
> Got it working!  Not sure why, but when I tried changing the port for
> the Raven site to 8888 instead of 8080 the site worked.  As far as I
> know, I don't have any other sites registered to use port 8080, so
> that is still a mystery.  But at least the Raven IIS service is
> running now.
>
> On Jul 24, 11:22 pm, Ayende Rahien <aye...@ayende.com> wrote:
>
> > Can we schedule a Skype call about this later today (in about 6 - 8 hours)?
>
> > On Sun, Jul 25, 2010 at 8:31 AM, Chris Swain <chrisasw...@gmail.com> wrote:
> > > This is odd, then.  I wonder if it would be benefitial to have a step
> > > by step blog post showing how to create the site and app pool, create
> > > any new users, set permissions, etc?
>
> > > On Jul 24, 9:56 pm, Ayende Rahien <aye...@ayende.com> wrote:
> > > > No, I am running is on Win7 as well
>
> > > > On Sun, Jul 25, 2010 at 7:29 AM, Chris Swain <chrisasw...@gmail.com>
> > > wrote:
> > > > > I reverted my changes to the applicationhost.config file.  Changed the

> > > > > app pool to ASP.NET v4.0.  Still getting the503error.  I recreated

> > > > > the RavenApplicationPool app pool, set it to v4.0 framework version.
> > > > > Still doesn't work.
>
> > > > > Could this be a windows 7 thing?
>
> > > > > On Jul 24, 8:24 pm, Ayende Rahien <aye...@ayende.com> wrote:
> > > > > > Hm...

> > > > > >503usually means something pretty catastrophic just happened.

> > > > > > Can you revert any changes that you made to applicationhost.config
> > > and
> > > > > see
> > > > > > if this helps?
>
> > > > > > On Sun, Jul 25, 2010 at 6:22 AM, Chris Swain <chrisasw...@gmail.com>
> > > > > wrote:
> > > > > > > It doesn't look like anything is getting logged in the Event
> > > Viewer.
>
> > > > > > > On Jul 24, 8:11 pm, Ayende Rahien <aye...@ayende.com> wrote:
> > > > > > > > What do you see in the event log?
>
> > > > > > > > On Sun, Jul 25, 2010 at 5:05 AM, Chris Swain <
> > > chrisasw...@gmail.com>
> > > > > > > wrote:
> > > > > > > > > I've followed the instructions at:
>
> > > > > > > > >http://ravendb.net/documentation/docs-deployment-iis
>
> > > > > > > > > but when I try to browse to the Raven web site I created, I get
> > > the
> > > > > > > > > error:
>

> > > > > > > > > HTTP Error503. The service is unavailable.

[Chris Swain]

Thanks. This is exactly what I needed.

On Aug 1, 8:36 am, slav <slav....@gmail.com> wrote:
> I encountered the same problem. Things broke when I launched Raven
> server from command prompt.
>
> When you do that, Raven reserves http namespace for that port using
> "netsh", and that prevents IIS from being able to handle requests to
> this port.

> See:http://msdn.microsoft.com/en-us/library/ms733768.aspxhttp://blogs.msdn.com/b/drnick/archive/2006/10/16/configuring-http-fo...

[Ayende Rahien]

Slav, 

Thanks for figuring out exactly what was wrong, I added that to the FAQ

http://ravendb.net/faq/iis-deployment-503-service-unavailable