logo

Warning: The forum is now for consultation only. Please use GitHub Discussions to post any questions or comments.


Welcome Guest ! To enable all features please Login or Register.

Notification

Icon
Error
Seal Server Manager - Publish Web Site on IIS - HTTP Error 500.19 - Internal Server Error The requested page cannot be accessed...
Options
Go to last post Go to first unread
Previous Topic Next Topic
ajc  
#1 Posted : Friday, November 13, 2015 12:54:27 PM(UTC)
ajc

Rank: Newbie

Groups: Registered
Joined: 11/13/2015(UTC)
Posts: 5
Portugal
Location: Lisbon

Was thanked: 2 time(s) in 1 post(s)
On Seal Server Manager when I choose Publish Web Site on IIS everything seems wright:

12:39:39 Starting Web Site Publishing...
12:39:39 Copying files from 'C:\Program Files (x86)\Seal Report\Web' to 'C:\inetpub\wwwroot\SealNorthwind'
12:39:39 Publishing Site on IIS...
12:39:40 Web Site has been published successfully.
12:39:40 Web Site Publishing terminated.

When I try to use the new site I get an error "HTTP Error 500.19 - Internal Server Error The requested page cannot be accessed..."

The IIS presents the folowing information:
Error Summary
HTTP Error 500.19 - Internal Server Error

The requested page cannot be accessed because the related configuration data for the page is invalid.

I'm using the report "Dashboard - Sales" and connection Northwind. Can anybody help?


Detailed Error Information
==========================

Module
IIS Web Core

Notification
BeginRequest

Handler
Not yet determined

Error Code
0x80070021

Config Error
This configuration section cannot be used at this path. This happens when the section is locked at a parent level. Locking is either by default (overrideModeDefault="Deny"), or set explicitly by a location tag with overrideMode="Deny" or the legacy allowOverride="false".

Config File
\\?\C:\inetpub\wwwroot\SealNorthwind\web.config


Requested URL
http://localhost:80/SealNorthwind/Main

Physical Path
C:\inetpub\wwwroot\SealNorthwind\Main

Logon Method
Not yet determined

Logon User
Not yet determined

Config Source 42: <modules runAllManagedModulesForAllRequests="true" />
43: <handlers>
44: <remove name="ExtensionlessUrlHandler-ISAPI-4.0_32bit" />
Back to top
WWW

Wanna join the discussion?! Login to your Seal Report Forum forum accountor Register a new forum account.
Back to top  
epf  
#2 Posted : Friday, November 13, 2015 2:56:40 PM(UTC)
epf

Rank: Administration

Groups: Administrators
Joined: 12/20/2013(UTC)
Posts: 1,209
Switzerland

Thanks: 14 times
Was thanked: 206 time(s) in 199 post(s)
You have to run IIS Manager to have more information and find out the problem.
Do you have all the pre-requisites ?

The Web Report Server is a classic ASP.Net application with a dedicated application pool.
You can google the error you to find a clue...
Back to top
ajc  
#3 Posted : Monday, November 16, 2015 11:20:19 AM(UTC)
ajc

Rank: Newbie

Groups: Registered
Joined: 11/13/2015(UTC)
Posts: 5
Portugal
Location: Lisbon

Was thanked: 2 time(s) in 1 post(s)
After reinstall the ASP.NET feature of IIS on my Windows 7 I get another error (see below) when I try no navigate to the Published Site (http://localhost/Seal/Main).

Can anyone try the "Publish Web Site On IIS..." of the Seal Server Manager and tell me if it works? Thanks


HTTP Error 500.21 - Internal Server Error
Handler "ExtensionlessUrlHandler-Integrated-4.0" has a bad module "ManagedPipelineHandler" in its module list

Detailed Error Information
==========================

Module
IIS Web Core

Notification
ExecuteRequestHandler

Handler
ExtensionlessUrlHandler-Integrated-4.0

Error Code
0x8007000d



Requested URL
http://localhost:80/Seal/Main

Physical Path
C:\inetpub\wwwroot\Seal\Main

Logon Method
Anonymous

Logon User
Anonymous

Most likely causes:
===================
•Managed handler is used; however, ASP.NET is not installed or is not installed completely.
•There is a typographical error in the configuration for the handler module list.


Things you can try:
===================
•Install ASP.NET if you are using managed handler.
•Ensure that the handler module's name is specified correctly. Module names are case-sensitive and use the format modules="StaticFileModule,DefaultDocumentModule,DirectoryListingModule".

Edited by user Monday, November 16, 2015 11:22:05 AM(UTC)  | Reason: Not specified
Back to top
WWW
epf  
#4 Posted : Monday, November 16, 2015 2:34:37 PM(UTC)
epf

Rank: Administration

Groups: Administrators
Joined: 12/20/2013(UTC)
Posts: 1,209
Switzerland

Thanks: 14 times
Was thanked: 206 time(s) in 199 post(s)
Did you run the Server Manager As Administrator (right click on the icon -> Run as administrator) before publishing ?
Back to top
ajc  
#5 Posted : Monday, November 16, 2015 2:54:49 PM(UTC)
ajc

Rank: Newbie

Groups: Registered
Joined: 11/13/2015(UTC)
Posts: 5
Portugal
Location: Lisbon

Was thanked: 2 time(s) in 1 post(s)
Yes, I did use "Run as Administrator". I get:
=================================================================================================
14:46:54 Starting Web Site Publishing...
14:46:54 Copying files from 'C:\Program Files (x86)\Seal Report\Web' to 'C:\inetpub\wwwroot\Seal'
14:46:57 Creating web.config file
14:46:57 Publishing Site on IIS...
14:46:58 Creating Application
14:46:58 Web Site has been published successfully.
14:46:58 Web Site Publishing terminated.
=================================================================================================
But when I try to browse the new website http://localhost/Seal/Main I get an error page from IIS:

=============================================================================================================
Error Summary
HTTP Error 500.21 - Internal Server Error

Handler "ExtensionlessUrlHandler-Integrated-4.0" has a bad module "ManagedPipelineHandler" in its module list
=============================================================================================================
Back to top
WWW
epf  
#6 Posted : Monday, November 16, 2015 3:41:21 PM(UTC)
epf

Rank: Administration

Groups: Administrators
Joined: 12/20/2013(UTC)
Posts: 1,209
Switzerland

Thanks: 14 times
Was thanked: 206 time(s) in 199 post(s)
Looks like your ASP.Net is not well installed:
Check http://stackoverflow.com/questions/13162545/handler-extensionlessurlhandler-integrated-4-0-has-a-bad-module-managedpipeli


IIS must be installed with the following features:
IIS version 7: Application Development/ASP.Net
IIS version 8: Application Development/ASP.Net 3.5, Application Development/ASP.Net 4.5
MVC 4 extension

by default IIS does not have these extensions, check the documentation to install them...
Back to top
ajc  
#7 Posted : Monday, November 16, 2015 4:35:51 PM(UTC)
ajc

Rank: Newbie

Groups: Registered
Joined: 11/13/2015(UTC)
Posts: 5
Portugal
Location: Lisbon

Was thanked: 2 time(s) in 1 post(s)
I checked and IIS has installed the following features:
IIS version 7: Application Development/ASP.Net

Thanks for the link, but I think it does not apply to my case.
Back to top
WWW
epf  
#8 Posted : Tuesday, November 17, 2015 10:53:54 AM(UTC)
epf

Rank: Administration

Groups: Administrators
Joined: 12/20/2013(UTC)
Posts: 1,209
Switzerland

Thanks: 14 times
Was thanked: 206 time(s) in 199 post(s)
Sorry I have no other suggestion, perhaps re-install MVC4 from
http://www.asp.net/mvc/mvc4

or try on another computer.

Thanks to let us know if you find the solution...
Back to top
ajc  
#9 Posted : Wednesday, November 18, 2015 4:18:24 PM(UTC)
ajc

Rank: Newbie

Groups: Registered
Joined: 11/13/2015(UTC)
Posts: 5
Portugal
Location: Lisbon

Was thanked: 2 time(s) in 1 post(s)
The solution for this problem was:
1 - Run Command Prompt as Administrator
2 - cd c:\Windows\Microsoft.NET\Framework\v4.0.30319
3 - aspnet_regiis.exe –i
Seal Web site starts working as it should.
Back to top
WWW
thanks 2 users thanked ajc for this useful post.
epf on 11/18/2015(UTC), mirekm_m on 9/29/2016(UTC)
rede  
#10 Posted : Friday, January 26, 2024 6:16:00 PM(UTC)
rede

Rank: Newbie

Groups: Registered
Joined: 1/25/2024(UTC)
Posts: 1
United States

Thanks: 2 times
Hello,
I have a similar error when publishing to local IIS 10.0.x.
Tried executing "C:\Windows\Microsoft.NET\Framework\v4.0.30319>aspnet_regiis.exe -i" as administrator but did not resolve my error below. What should be the correct Handler Mapping for Seal report site?
I do have ASP.Net features added to my IIS already.
Thanks


From IIS Manager when open Hander Mappings for Seal site, I pop-up error like this:
______________________________________________________
Handler Mappings
There was an error while performing this operation.
Details:
Filename: \\?\C:\inetpub\wwwroot\Seal\web.config
Error:
______________________________________________________



--- My error when loading site after publish success ---
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 Information:
Module IIS Web Core
Notification BeginRequest
Handler Not yet determined
Error Code 0x8007000d
Config Error
Config File \\?\C:\inetpub\wwwroot\Seal\web.config
Requested URL http://localhost:80/Seal/Main
Physical Path C:\inetpub\wwwroot\Seal\Main
Logon Method Not yet determined
Logon User Not yet determined

Config Source:
-1:
0:


--- Below is my C:\inetpub\wwwroot\Seal\web.config content is anything missing ? ---
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<location path="." inheritInChildApplications="false">
<system.webServer>
<handlers>
<add name="aspNetCore" path="*" verb="*" modules="AspNetCoreModuleV2" resourceType="Unspecified" />
</handlers>
<aspNetCore processPath="dotnet" arguments=".\SealWebServer.dll" stdoutLogEnabled="false" stdoutLogFile=".\logs\stdout" hostingModel="inprocess" />
</system.webServer>
</location>
</configuration>
<!--ProjectGuid: dcd6c87c-a399-4aa7-8e17-696016a0e795-->
Back to top
epf  
#11 Posted : Saturday, January 27, 2024 8:54:29 AM(UTC)
epf

Rank: Administration

Groups: Administrators
Joined: 12/20/2013(UTC)
Posts: 1,209
Switzerland

Thanks: 14 times
Was thanked: 206 time(s) in 199 post(s)
For the version 7.x you need .Net 7:
https://dotnet.microsoft...n-us/download/dotnet/7.0

Choose the ASP.NET Core Runtime (Hosting Bundle)

For the Windows application, install also:
.NET Desktop Runtime

Check: https://sealreport.org/#lineRequirements
Back to top
thanks 1 user thanked epf for this useful post.
rede on 1/31/2024(UTC)
Users browsing this topic
Guest (2)
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

Powered by YAF.NET 2.2.4.11 | YAF.NET © 2003-2024, Yet Another Forum.NET
This page was generated in 0.151 seconds.