2000 to 2003 upgrade breaks IIS--dcom event ID 10004 error

Gentlemen:

I was running IIS 5.0 on my 2000 server, and everything was working fine. I
did an in-place upgrade to 2003 Server (std.), and it went ok but now my
website is busted. When I try to login to a web page it cannot find it and
the server registers the following error in the event log:

"DCOM got error....and was unable to login .IWAM\computername in order to
run the server. Event ID 10004"

I did some checking for solutions from Microsoft, and did confirm that
IWAM_computername has logon as batch job right, and that it is in the IIS-WPG
group.

Can someone offer advice on what I should be checking next? Like I said,
everything was working fine prior to the upgrade.

RE: 2000 to 2003 upgrade breaks IIS--dcom event ID 10004 error

Got my problem fixed! I had to go into IIS manager and turn OFF "run www
services in IIS 5.0 Isolation mode".

Which leads to a second question: is it ok to turn off this security option?
"zooeyhallne" wrote:

> Gentlemen:
>
> I was running IIS 5.0 on my 2000 server, and everything was working fine. I
> did an in-place upgrade to 2003 Server (std.), and it went ok but now my
> website is busted. When I try to login to a web page it cannot find it and
> the server registers the following error in the event log:
>
> "DCOM got error....and was unable to login .IWAM\computername in order to
> run the server. Event ID 10004"
>
> I did some checking for solutions from Microsoft, and did confirm that
> IWAM_computername has logon as batch job right, and that it is in the IIS-WPG
> group.
>
> Can someone offer advice on what I should be checking next? Like I said,
> everything was working fine prior to the upgrade.

Re: 2000 to 2003 upgrade breaks IIS--dcom event ID 10004 error

Yes. You actually run in a more secure mode when you turn OFF "Run WWW
services in IIS 5.0 Isolation mode".

By default, in-place upgrades will leave IIS6 configured in IIS5
Compatibility Mode. You are now running in IIS6's native Worker
Process Isolation Mode, which gives you the ability to enjoy full
benefits of IIS6.


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//




On Oct 30, 10:26 am, zooeyhallne
wrote:
> Got my problem fixed! I had to go into IIS manager and turn OFF "run www
> services in IIS 5.0 Isolation mode".
>
> Which leads to a second question: is it ok to turn off this security option?
>
>
>
> "zooeyhallne" wrote:
> > Gentlemen:
>
> > I was running IIS 5.0 on my 2000 server, and everything was working fine. I
> > did an in-place upgrade to 2003 Server (std.), and it went ok but now my
> > website is busted. When I try to login to a web page it cannot find it and
> > the server registers the following error in the event log:
>
> > "DCOM got error....and was unable to login .IWAM\computername in order to
> > run the server. Event ID 10004"
>
> > I did some checking for solutions from Microsoft, and did confirm that
> > IWAM_computername has logon as batch job right, and that it is in the IIS-WPG
> > group.
>
> > Can someone offer advice on what I should be checking next? Like I said,
> > everything was working fine prior to the upgrade.- Hide quoted text -
>
> - Show quoted text -