Search EggHeadCafe's Job Board
EggHeadCafe Silverlight WPF ASP.NET VB.NET C# Excel SQL Server SharePoint
search
IIS GroupsView
Inetserver Asp Db
Inetserver Asp General
Inetserver Iis
Inetserver Iis Security
Frontpage Client
Frontpage Extensions Windowsnt
Frontpage Programming

Group SummariesView
.NET Framework
Access
BizTalk
Certifications
CRM
DDK
Exchange Server
FoxPro
French
French .NET
Games
German
German .NET
Graphic Design
IIS
Internet
ISA Server
Italian
Italian .NET
Maps
MCIS
Miscellaneous
Mobile Apps
Money
MSN
Networking
Office
Ops Mgr
Publisher
Security
SharePoint
Small Business
Spanish
Spanish .NET
SQL Server
Systems Management Server
Transaction Server
Virtual PC / Virtual Server
Visual Studio
Win32
Windows 2000
Windows 2003 Server
Windows 7
Windows Live
Windows Media
Windows Update
Windows Vista
Windows XP
 

View All Microsoft Inetserver Iis Posts  Ask A New Question 

Error 500.19 on IIS 7

dbrowne posted on Monday, February 11, 2008 7:05 PM

I'm trying to run Sql Reporting Services on Windows 2008. Every server we
try to install returns the same error:

HTTP Error 500.19 - Internal Server Error
The requested page cannot be accessed because the related configuration data
for the page is invalid. Detailed Error InformationModule IIS Web Core
Notification BeginRequest
Handler Not yet determined
Error Code 0x80070005
Config Error Cannot read configuration file due to insufficient permissions
Config File \\?\C:\inetpub\wwwroot\web.config
Requested URL http://localhost:80/Reports
Physical Path c:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting
Services\ReportManager
Logon Method Not yet determined
Logon User Not yet determined

We've search extensivly and every solution we try results in the same error.
We've made sure the application is running under the Classic .net pool.
We've added IIS_IUSER to the physical folders. There is nothing that looks
out of the ordinary in the web.config file. The application is running under
2.0 .net framework. We've tried running IE under the administrator account
but still receive the same error.

I've noticed this problem happening alot with others. Does anyone know of a
solution we haven't tried?
reply

 

Hi,Please explicitly grant the IIS_IUSRS group(not IIS_IUSER) with Read

wjzhan posted on Tuesday, February 12, 2008 12:37 AM

Hi,

Please explicitly grant the IIS_IUSRS group(not IIS_IUSER) with Read
permission on the web.config file. Then restart IIS services and see if the
problem still persists. Please refer to the steps as below:

Grant the Read permission to the IIS_IUSRS group for the
ApplicationHost.config file or for the Web.config file. To do this, follow
these steps: 1.  In Windows Explorer, locate the ApplicationHost.config
file that is associated with the Web site, or locate the Web.config file
that is associated with the Web site.
2.  Right-click the ApplicationHost.config file, or right-click the
Web.config file.
3.  Click Properties.
4.  Click the Security tab, and then click Edit.
5.  Click Add.
6.  In the Enter the object names to select box, type computername
\IIS_IUSRS , click Check Names, and then click OK.

Note Computername is a placeholder for the computer name.
7.  Click to select the Read check box, and then click OK.
8.  In the ApplicationHost.config Properties dialog box or in the
Web.config Properties dialog box, click OK.

Thanks.

Sincerely,

WenJun Zhang

Microsoft Online Community Support

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

Get notification to my posts through email? Please refer to:
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at:

http://msdn.microsoft.com/subscriptions/support/default.aspx.

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

This posting is provided "AS IS" with no warranties, and confers no rights.
reply

Yes we've done that, even granting the entire folder read/write access to the

dbrowne posted on Tuesday, February 12, 2008 7:49 PM

Yes we have done that, even granting the entire folder read/write access to
the windowsdev\IIS_IUSRS group. The same error appears when browsing to the
website.
reply

This seems to be an issue with iis7/windows 2008.

dbrowne posted on Thursday, February 14, 2008 12:31 PM

This seems to be an issue with iis7/windows 2008. We've successfully
installed on windows 2003 and vista. Also note that when deploying reports
in the business intellegence studio, we are never able to successfully login
into the report server.

We have tried both a local and a domain administrator. Both are not able to
login in.

Any other thoughts?
reply

Hi,Due to Longhorn Windows 2008 server hasn't been officially released, IIS 7.

wjzhan posted on Monday, February 18, 2008 7:40 AM

Hi,

Due to Longhorn Windows 2008 server hasn't been officially released, IIS
7.0 on Longhorn isn't supported by Microsoft Customer Support Service
currently. You can report the problem to our Longhorn Beta newsgroup or
http://forums.iis.net/ to confirm it.

Newsgroup: microsoft.beta.longhorn.general

Thanks.

Sincerely,

WenJun Zhang

Microsoft Online Community Support

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

Get notification to my posts through email? Please refer to:
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at:

http://msdn.microsoft.com/subscriptions/support/default.aspx.

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

This posting is provided "AS IS" with no warranties, and confers no rights.
reply

Error 500.19 on IIS 7

Adriano da Silva posted on Friday, May 09, 2008 11:41 AM

Hello there.

I am not sure if already found a solution for this problem, but I had the same problem yesterday and after searching the net for two days a finally found the solution for this. Try the following:



1 - Open the applicationHost.config file under the %windir%\System32\intsrv\config and changed the section <Handlers> and <Modules> overrideModeDefault="Deny" to overrideModeDefault="Allow"

2- Run the appcmd.exe located on the directory above passing the following appcmd.exe migrate config "application" where application is the name of your web application.

3 - Ensure that the Application Pool which your web application is running is configured to use the .Net framework 2.0

4 - Run the aspnet_regiis.exe -i to register the Asp.net account

5 - Ensure that the Aspnet or Network Service is given the rigths to acces your application folder.

6 - Ensure that you have a default document under the Default Document in IIS.



Hope that this can help you.

good luck!



adasilva
reply

Hello there.

adasilv posted on Friday, May 09, 2008 11:45 AM

Hello there.
I am not sure if already found a solution for this problem, but I had the
same problem yesterday and after searching the net for two days a finally
found the solution for this. Try the following:

1 - Open the applicationHost.config file under the
%windir%\System32\intsrv\config and changed the section <Handlers> and
2- Run the appcmd.exe located on the directory above passing the following
appcmd.exe migrate config "application" where application is the name of your
web application.
3 - Ensure that the Application Pool which your web application is running
is configured to use the .Net framework 2.0
4 - Run the aspnet_regiis.exe -i to register the Asp.net account
5 - Ensure that the Aspnet or Network Service is given the rigths to acces
your application folder.
6 - Ensure that you have a default document under the Default Document in IIS.

Hope that this can help you.
good luck!

adasilva
--
adasilva
reply

 
 

Previous Microsoft Inetserver Iis conversation.