我讨厌IIS - “服务器应用程序不可用”错误信息 [英] I hate IIS - "Server Application Unavailable" error message

查看:72
本文介绍了我讨厌IIS - “服务器应用程序不可用”错误信息的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

是的,我在过去两天试图解决这个问题浪费了。

是的,这是在Win2003服务器上。

是的,这台机器是一个域控制器。


是的,我看过像这样的几十篇KB文章:
http://support.microsoft.com/default...;en-us;Q315158

但问题是其中99%用于ASP .NET 1.x而且这个
是我刚安装的.NET 2.x,试图让.net工作

第一次。我已经看到了所有的HACKS让.net 1.x正常工作......但是

这是针对.net 2.x所以这些毫无价值的知识库文章对我没有任何帮助。


示例 -
http://support.microsoft.com/default...;en-us;Q315158


RESOLUTION

To解决此问题,请使用下列方法之一:?

创建一个具有正确权限的弱帐户,然后

配置计算机的< processModelsection。配置文件使用

该帐户。

·在Machine.config文件的< processModelsection

中将userName属性设置为SYSTEM。

·配置Machine.config文件的< processModelsection以

使用管理员帐户。

这是无用的!!!!!没有userName .net 2.x中

Machine.config文件中的属性。如果这是一个已知问题那么

为什么安装程序不会警告我或自动修复它。对不起,但

您的软件最近很糟糕。!!!!!!!


事件日志中包含以下消息:


< quote>

aspnet_wp.exe无法启动。失败的错误代码是

800700CB。当工作进程帐户具有读取.NET Framework文件的权限不足时,可能会导致此错误。请确保.NET Framework已正确安装,并且安装目录上的ACL允许访问已配置的帐户。

< ; / quote>

对不起微软 - 但你得到了WORSE和WORSE。怎么样

软件简单有效????


毫无疑问,Linux正在踢你的屁股,我大约30岁

秒离开你过度复杂的错误告别

废话并自己过渡到linux。

解决方案

框架版本混合可能吗?您是否检查了

网站属性上的ASP.NET标签页,并确保将其设置为正确的版本?您是否转到了Web服务扩展程序并确保启用了正确的扩展程序?

如果没有其他工作,请尝试为asp.net重新注册2.0
(aspnet_regiis.exe)


冷静下来,2.0比1.1更好,值得一试。


Otavio

" Kevin Liebowicz" < li ******* @ lycos.com写了留言

news:11 ********************* @ w5g2000hsg .googlegrou ps.com ...

是的,我在过去两天试图解决这个问题浪费了。

是的,这是在Win2003服务器上。

是的,这台机器是域控制器。


是的,我看过像这样的几十篇KB文章:
http://support.microsoft.com/default...;en-us ; Q315158


但问题是其中99%是针对ASP .NET 1.x而且这个

是.NET 2。我刚安装的x试图让.net第一次为

工作。我已经看到了所有的HACKS让.net 1.x正常工作......但是

这是针对.net 2.x所以这些毫无价值的知识库文章对我没有任何帮助。


示例 -
http://support.microsoft.com/default...;en-us;Q315158


RESOLUTION

To解决此问题,请使用下列方法之一:?

创建一个具有正确权限的弱帐户,然后

配置计算机的< processModelsection。配置文件使用

该帐户。

·在Machine.config文件的< processModelsection

中将userName属性设置为SYSTEM。

·配置Machine.config文件的< processModelsection以

使用管理员帐户。

这是无用的!!!!!没有userName .net 2.x中

Machine.config文件中的属性。如果这是一个已知问题那么

为什么安装程序不会警告我或自动修复它。对不起,但

您的软件最近很糟糕。!!!!!!!


事件日志中包含以下消息:


< quote>

aspnet_wp.exe无法启动。失败的错误代码是

800700CB。当工作进程帐户具有读取.NET Framework文件的权限不足时,可能会导致此错误。请确保.NET Framework已正确安装,并且安装目录上的ACL允许访问已配置的帐户。

< ; / quote>

对不起微软 - 但你得到了WORSE和WORSE。怎么样

软件简单有效????


毫无疑问,Linux正在踢你的屁股,我大约30岁

秒离开你过度复杂的错误告别

废话并自己过渡到linux。


re:

!是的,这是在Win2003服务器上。

!是的,这台机器是域控制器。


坏主意。


一般来说,不建议在域控制器上运行Web服务器,

,因为机器的危害是域名的妥协。


但是,如果你真的*需要这样做......


re:

!没有userName .net 2.x中Machine.config文件中的属性


是的,有。


< processModel enable ="真QUOT;的userName = QUOT; SYSTEM"密码= QUOT;自动生成" />


....如果你真的*想要运行ASP.NET

作为SYSTEM帐户,应该为你报道一个域控制器,虽然我会加密该部分。


更好的是,我不会将ASP.NET作为系统帐户运行。见下文...


re:

!事件日志中包含以下消息:


It难怪会发生这种情况。


re:

!软件怎么样才能真正起作用?


如果你故意在域控制器上运行ASP.NET,那么不推荐使用
的东西,不要责怪微软

如果你不能RTFM实施变通方法。

http://msdn2.microsoft.com/en-us/library/7w2sway1.aspx

比使用系统帐户更好的是指定一个明确的帐户。


这解决了在域控制器上运行ASP.NET的安全性问题。


为此,请按照本文中的说明进行操作...


如何:为ASP.NET 2.0应用程序创建服务帐户:
http://msdn2.microsoft.com/en-us/library/ms998297 .aspx


试一试。这真的很容易。


Juan T. Llibre,asp.net MVP

asp.net faq: http://asp.net.do/faq/

foros de asp.net,en espa?ol: http://asp.net.do/ foros /

==================================== ==

" Kevin Liebowicz" < li ******* @ lycos.com写了留言新闻:11 ********************* @ w5g2000hsg.googlegrou ps.com ...

是的,我在过去两天试图解决这个问题浪费了。

是的,这是在Win2003服务器上。

是的,这台机器是一个域控制器。


是的,我看过像这样的几十篇KB文章:
http://support.microsoft.com/default...;en-us;Q315158


但问题是其中99%是针对ASP .NET 1.x而且这个
是我刚安装的.NET 2.x让.net第一次为

工作。我已经看到了所有的HACKS让.net 1.x正常工作......但是

这是针对.net 2.x所以这些毫无价值的知识库文章对我没有任何帮助。


示例 -
http://support.microsoft.com/default...;en-us;Q315158


RESOLUTION

To解决此问题,请使用下列方法之一:?

创建一个具有正确权限的弱帐户,然后

配置计算机的< processModelsection。配置文件使用

该帐户。

·在Machine.config文件的< processModelsection

中将userName属性设置为SYSTEM。

·配置Machine.config文件的< processModelsection以

使用管理员帐户。

这是无用的!!!!!没有userName .net 2.x中

Machine.config文件中的属性。如果这是一个已知问题那么

为什么安装程序不会警告我或自动修复它。对不起,但

您的软件最近很糟糕。!!!!!!!


事件日志中包含以下消息:


< quote>

aspnet_wp.exe无法启动。失败的错误代码是

800700CB。当工作进程帐户具有读取.NET Framework文件的权限不足时,可能会导致此错误。请确保.NET Framework已正确安装,并且安装目录上的ACL允许访问已配置的帐户。

< ; / quote>

对不起微软 - 但你得到了WORSE和WORSE。怎么样

软件简单有效????


毫无疑问,Linux正在踢你的屁股,我大约30岁

秒离开你过度复杂的错误告别

废话并自己过渡到linux。


Ouch Juan。我正在为这个家伙的葬礼祈祷。 :-)


-

Gregory A. Beamer

MVP; MCP:+ I,SE,SD,DBA
http://gregorybeamer.spaces。 live.com

合着者:Microsoft Expression Web Bible(即将发布)


************ ************************************

在盒子外面思考!

******************************************* *****

Juan T. Llibre < no *********** @ nowhere.comwrote in message

news:ej ************** @ TK2MSFTNGP03.phx。 gbl ...


re:

!是的,这是在Win2003服务器上。

!是的,这台机器是一个域控制器。


坏主意。


一般情况下,不建议运行你的Web服务器一个域名

控制器,

因为对机器的妥协是域名的妥协。


但是,如果你*真的*需要这样做...


re:

!没有userName .net中的Machine.config文件中的属性

2.x.


是的,有。


< processModel enable =" true"的userName = QUOT; SYSTEM"密码= QUOT;自动生成" />


...应该为你报道,如果你真的*想要运行ASP.NET

作为SYSTEM账号域控制器,虽然我会加密

部分。


更好的是,我不会将ASP.NET作为系统帐户运行。见下文...


re:

!事件日志中包含以下消息:


It难怪会发生这种情况。


re:

!软件怎么样才能真正起作用?


如果你故意在域控制器上运行ASP.NET,那么不推荐使用
的东西,不要责怪微软

如果你不能RTFM实施变通方法。

http://msdn2.microsoft.com/en-us/library/7w2sway1.aspx


比使用系统帐户更好的是指定一个明确的

帐户。


这可以解决在域控制器上运行ASP.NET的安全问题。


为此,请按照本文中的说明进行操作...


如何:为ASP.NET 2.0应用程序创建服务帐户:
http://msdn2.microsoft.com/en-us/library/ ms998297.aspx


试一试。这真的很容易。


Juan T. Llibre,asp.net MVP

asp.net faq: http://asp.net.do/faq/

foros de asp.net,en espa?ol: http://asp.net.do/ foros /

==================================== ==

" Kevin Liebowicz" < li ******* @ lycos.com写了留言

news:11 ********************* @ w5g2000hsg .googlegrou ps.com ...

是的,我在过去两天试图解决这个问题浪费了。

是的,这是在Win2003服务器上。

是的,这台机器是域控制器。


是的,我看过像这样的几十篇KB文章:
http://support.microsoft.com/default...;en-us ; Q315158


但问题是其中99%是针对ASP .NET 1.x而且这个

是.NET 2。我刚安装的x试图让.net第一次为

工作。我已经看到了所有的HACKS让.net 1.x正常工作......但是

这是针对.net 2.x所以这些毫无价值的知识库文章对我没有任何帮助。


示例 -
http://support.microsoft.com/default...;en-us;Q315158


RESOLUTION

To解决此问题,请使用下列方法之一:?

创建一个具有正确权限的弱帐户,然后

配置计算机的< processModelsection。配置文件使用

该帐户。

·在Machine.config文件的< processModelsection

中将userName属性设置为SYSTEM。

·配置Machine.config文件的< processModelsection以

使用管理员帐户。


这是无用的! !!!!没有userName .net 2.x中

Machine.config文件中的属性。如果这是一个已知问题那么

为什么安装程序不会警告我或自动修复它。对不起,但

您的软件最近很糟糕。!!!!!!!


事件日志中包含以下消息:


< quote>

aspnet_wp.exe无法启动。失败的错误代码是

800700CB。当工作进程帐户具有读取.NET Framework文件的权限不足时,可能会导致此错误。请确保.NET Framework已正确安装,并且安装目录上的ACL允许访问已配置的帐户。

< ; / quote>


对不起微软 - 但你得到了WORSE和WORSE。怎么样

软件简单有效????


毫无疑问,Linux正在踢你的屁股,我大约30岁

秒离开你过度复杂的错误告别

废话并自己过渡到linux。



Yes, I wasted the past two days trying to fix this.
Yes, this is on a Win2003 Server.
Yes, this machine is a domain controller.

Yes, I seen the dozens of KB articles like this one:
http://support.microsoft.com/default...;en-us;Q315158

But the problem is that 99% of these are for ASP .NET 1.x and this
is .NET 2.x which I just installed to try and get .net working for the
first time ever. I''ve see all the HACKS to get .net 1.x working... but
this is for .net 2.x so these worthless KB articles do nothing for me.

Example -
http://support.microsoft.com/default...;en-us;Q315158

RESOLUTION
To work around this problem, use one of the following methods: ·
Create a weak account that has the correct permissions, and then
configure the <processModelsection of the Machine.config file to use
that account.
· Set the userName attribute to SYSTEM in the <processModelsection
of the Machine.config file.
· Configure the <processModelsection of the Machine.config file to
use an administrator account.
THIS IS USELESS !!!!! There is no "userName" attribute in the
Machine.config file in .net 2.x. And if this is a known problem then
why doesn''t the installer warn me or fix it automatically. Sorry, but
your software sucks lately.!!!!!!!

The event log is filled with messages like:

<quote>
aspnet_wp.exe could not be started. The error code for the failure is
800700CB. This error can be caused when the worker process account has
insufficient rights to read the .NET Framework files. Please ensure
that the .NET Framework is correctly installed and that the ACLs on
the installation directory allow access to the configured account.
</quote>
Sorry Microsoft - But you are getting WORSE and WORSE. How about
software that simply works????

It''s no wonder that Linux is kicking your butt and I''m about 30
seconds away from saying goodbye to your over-complicated bug ridden
crap and making the transition to linux myself.

解决方案

Framework versions mixup maybe? Did you check the ASP.NET tab page on the
site properties and made sure it is set to the right version? Did you go to
the Web Service Extensions and made sure the proper extensions are enabled?
If nothing else works, try re-registering 2.0 for asp.net
(aspnet_regiis.exe)

Calm down, 2.0 is way better than 1.1 and it is worth the trouble.

Otavio
"Kevin Liebowicz" <li*******@lycos.comwrote in message
news:11*********************@w5g2000hsg.googlegrou ps.com...
Yes, I wasted the past two days trying to fix this.
Yes, this is on a Win2003 Server.
Yes, this machine is a domain controller.

Yes, I seen the dozens of KB articles like this one:
http://support.microsoft.com/default...;en-us;Q315158

But the problem is that 99% of these are for ASP .NET 1.x and this
is .NET 2.x which I just installed to try and get .net working for the
first time ever. I''ve see all the HACKS to get .net 1.x working... but
this is for .net 2.x so these worthless KB articles do nothing for me.

Example -
http://support.microsoft.com/default...;en-us;Q315158

RESOLUTION
To work around this problem, use one of the following methods: ·
Create a weak account that has the correct permissions, and then
configure the <processModelsection of the Machine.config file to use
that account.
· Set the userName attribute to SYSTEM in the <processModelsection
of the Machine.config file.
· Configure the <processModelsection of the Machine.config file to
use an administrator account.
THIS IS USELESS !!!!! There is no "userName" attribute in the
Machine.config file in .net 2.x. And if this is a known problem then
why doesn''t the installer warn me or fix it automatically. Sorry, but
your software sucks lately.!!!!!!!

The event log is filled with messages like:

<quote>
aspnet_wp.exe could not be started. The error code for the failure is
800700CB. This error can be caused when the worker process account has
insufficient rights to read the .NET Framework files. Please ensure
that the .NET Framework is correctly installed and that the ACLs on
the installation directory allow access to the configured account.
</quote>
Sorry Microsoft - But you are getting WORSE and WORSE. How about
software that simply works????

It''s no wonder that Linux is kicking your butt and I''m about 30
seconds away from saying goodbye to your over-complicated bug ridden
crap and making the transition to linux myself.


re:
!Yes, this is on a Win2003 Server.
!Yes, this machine is a domain controller.

Bad idea.

In general, it''s not advisable to run your Web server on a domain controller,
because a compromise of the machine is a compromise of the domain.

But, if you *really* need to do that...

re:
!There is no "userName" attribute in the Machine.config file in .net 2.x.

Yes, there is.

<processModel enable="true" userName="SYSTEM" password="AutoGenerate" />

....ought to cover it for you, if you *really* want to run ASP.NET
as the SYSTEM account on a domain controller, although I would encrypt the section.

Even better, I would NOT run ASP.NET as the System account. See below...

re:
!The event log is filled with messages like:

It''s no wonder that is happening.

re:
!How about software that simply works????

If you deliberately run ASP.NET on a domain controller,
something which is not recommended, don''t blame Microsoft
if you can''t RTFM to implement the workaround.

http://msdn2.microsoft.com/en-us/library/7w2sway1.aspx

Even better than using the System account would be specifing an explicit account.

That works around the security problems which
running ASP.NET on a domain controller exposes you to.

To do that, follow the instructions in this article...

How To: Create a Service Account for an ASP.NET 2.0 Application:
http://msdn2.microsoft.com/en-us/library/ms998297.aspx

Try it. It''s really easy to do.


Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en espa?ol : http://asp.net.do/foros/
======================================
"Kevin Liebowicz" <li*******@lycos.comwrote in message news:11*********************@w5g2000hsg.googlegrou ps.com...
Yes, I wasted the past two days trying to fix this.
Yes, this is on a Win2003 Server.
Yes, this machine is a domain controller.

Yes, I seen the dozens of KB articles like this one:
http://support.microsoft.com/default...;en-us;Q315158

But the problem is that 99% of these are for ASP .NET 1.x and this
is .NET 2.x which I just installed to try and get .net working for the
first time ever. I''ve see all the HACKS to get .net 1.x working... but
this is for .net 2.x so these worthless KB articles do nothing for me.

Example -
http://support.microsoft.com/default...;en-us;Q315158

RESOLUTION
To work around this problem, use one of the following methods: ·
Create a weak account that has the correct permissions, and then
configure the <processModelsection of the Machine.config file to use
that account.
· Set the userName attribute to SYSTEM in the <processModelsection
of the Machine.config file.
· Configure the <processModelsection of the Machine.config file to
use an administrator account.
THIS IS USELESS !!!!! There is no "userName" attribute in the
Machine.config file in .net 2.x. And if this is a known problem then
why doesn''t the installer warn me or fix it automatically. Sorry, but
your software sucks lately.!!!!!!!

The event log is filled with messages like:

<quote>
aspnet_wp.exe could not be started. The error code for the failure is
800700CB. This error can be caused when the worker process account has
insufficient rights to read the .NET Framework files. Please ensure
that the .NET Framework is correctly installed and that the ACLs on
the installation directory allow access to the configured account.
</quote>
Sorry Microsoft - But you are getting WORSE and WORSE. How about
software that simply works????

It''s no wonder that Linux is kicking your butt and I''m about 30
seconds away from saying goodbye to your over-complicated bug ridden
crap and making the transition to linux myself.


Ouch Juan. I am praying for this guy''s funeral. :-)

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
http://gregorybeamer.spaces.live.com
Co-author: Microsoft Expression Web Bible (upcoming)

************************************************
Think outside the box!
************************************************
"Juan T. Llibre" <no***********@nowhere.comwrote in message
news:ej**************@TK2MSFTNGP03.phx.gbl...

re:
!Yes, this is on a Win2003 Server.
!Yes, this machine is a domain controller.

Bad idea.

In general, it''s not advisable to run your Web server on a domain
controller,
because a compromise of the machine is a compromise of the domain.

But, if you *really* need to do that...

re:
!There is no "userName" attribute in the Machine.config file in .net
2.x.

Yes, there is.

<processModel enable="true" userName="SYSTEM" password="AutoGenerate" />

...ought to cover it for you, if you *really* want to run ASP.NET
as the SYSTEM account on a domain controller, although I would encrypt the
section.

Even better, I would NOT run ASP.NET as the System account. See below...

re:
!The event log is filled with messages like:

It''s no wonder that is happening.

re:
!How about software that simply works????

If you deliberately run ASP.NET on a domain controller,
something which is not recommended, don''t blame Microsoft
if you can''t RTFM to implement the workaround.

http://msdn2.microsoft.com/en-us/library/7w2sway1.aspx

Even better than using the System account would be specifing an explicit
account.

That works around the security problems which
running ASP.NET on a domain controller exposes you to.

To do that, follow the instructions in this article...

How To: Create a Service Account for an ASP.NET 2.0 Application:
http://msdn2.microsoft.com/en-us/library/ms998297.aspx

Try it. It''s really easy to do.


Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en espa?ol : http://asp.net.do/foros/
======================================
"Kevin Liebowicz" <li*******@lycos.comwrote in message
news:11*********************@w5g2000hsg.googlegrou ps.com...
Yes, I wasted the past two days trying to fix this.
Yes, this is on a Win2003 Server.
Yes, this machine is a domain controller.

Yes, I seen the dozens of KB articles like this one:
http://support.microsoft.com/default...;en-us;Q315158

But the problem is that 99% of these are for ASP .NET 1.x and this
is .NET 2.x which I just installed to try and get .net working for the
first time ever. I''ve see all the HACKS to get .net 1.x working... but
this is for .net 2.x so these worthless KB articles do nothing for me.

Example -
http://support.microsoft.com/default...;en-us;Q315158

RESOLUTION
To work around this problem, use one of the following methods: ·
Create a weak account that has the correct permissions, and then
configure the <processModelsection of the Machine.config file to use
that account.
· Set the userName attribute to SYSTEM in the <processModelsection
of the Machine.config file.
· Configure the <processModelsection of the Machine.config file to
use an administrator account.
THIS IS USELESS !!!!! There is no "userName" attribute in the
Machine.config file in .net 2.x. And if this is a known problem then
why doesn''t the installer warn me or fix it automatically. Sorry, but
your software sucks lately.!!!!!!!

The event log is filled with messages like:

<quote>
aspnet_wp.exe could not be started. The error code for the failure is
800700CB. This error can be caused when the worker process account has
insufficient rights to read the .NET Framework files. Please ensure
that the .NET Framework is correctly installed and that the ACLs on
the installation directory allow access to the configured account.
</quote>
Sorry Microsoft - But you are getting WORSE and WORSE. How about
software that simply works????

It''s no wonder that Linux is kicking your butt and I''m about 30
seconds away from saying goodbye to your over-complicated bug ridden
crap and making the transition to linux myself.



这篇关于我讨厌IIS - “服务器应用程序不可用”错误信息的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆