Sitecore 8.2 publishing service not working - sitecore

For sitecore publishing service I have followed the steps from https://jonathanrobbins.co.uk/2016/09/02/setting-up-sitecore-publishing-service and Sitecore. But I am getting below error:
HTTP Error 500.19 – Internal Server Error
The requested page cannot be accessed because the related configuration data for the page is invalid.
Module IIS Web Core
Notification Unknown
Handler Not yet determined
Error Code 0x8007000d
Config Error
Config File \?\C:\sitecorepublishing\web.config
What am I missing?

The AspNetCoreModule has to be installed on the server and is part of the ASP.NET Core Server Hosting Bundle.

Related

Azure App Service "Server Error in '/' Application"

I have a business website that has been running perfectly well on IIS using .NET 4.5, but in Azure it fails.
Now before I lead you too far down this rabbit hole, I can make the IIS fault in the same way as the Azure fault detailed below by NOT converting the website to Application. However, for the life of me I cannot find the equivalent option in Azure; how to convert to Application or equivalent?
I have uploaded to Azure using the Azure App Service Migration Assistant. The only alert was:
"IIS7+ Schema Compliance: One or more elements and/or attributes are being used which are not defined in Azure App Service IIS schema. Consider using XDT transforms."
This links to https://learn.microsoft.com/en-nz/azure/app-service/web-sites-configure which indicates various Azure Application Settings, which I have played with to no avail.
Server Error in '/' Application.
Configuration Error
Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.
Parser Error Message: It is an error to use a section registered as allowDefinition='MachineToApplication' beyond application level. This error can be caused by a virtual directory not being configured as an application in IIS.
Source Error:
An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.
Source File: D:\home\site\wwwroot\peterfinch\service.desktop\web.config Line: 143
Can anyone please provide any guidance as to what I am missing? many thanks for your time, Peter Finch
so the answer was setting virtual applications and directories for each website, and this now just worked. App Service, Application Settings, at the end of the list, Virtual applictions and directories.
This was the part that was missing, how to 'convert to application'
So resolved it myself, thanks for looking and I hope this helps someone else in the future.
/ site\wwwroot   Application x
/mysitename site\wwwroot\mysitename   Application
/mysitename/Console site\wwwroot\mysitename\Console\   Application x
/mysitename/Service.App site\wwwroot\mysitename\Service.App\  Application x
/mysitename/Service.Desktop site\wwwroot\mysitename\Service.Desktop Application x

Error 0x80070585 when running Fastcgi with IIS 8 + Python 3.4 + Django 1.8 + Windows Server 2012

I am trying to set up IIS 8 with Django 1.8.3 using Fastcgi and Python 3.4. I followed this tutorial with the following Environment Variables:
DJANGO_SETTINGS_MODULE -> value: FirstSite.settings
PYTHONPATH -> value: C:\inetpub\wwwroot\Django\FirstSite
WSGI_HANDLER -> value: django.core.wsgi.get_wsgi_application()
I changed the WSGI Handler value from django.core.handlers.wsgi.wsgihandler() to django.core.wsgi.get_wsgi_application() because the tutorial talks about a previous Django version.
I followed everything in the tutorial, and as I try to open the website on my IE browser in Windows Server 2012 R2 I get the following error:
Keep in mind 8003 is the port I configured as the tutorial showed.
HTTP Error 500.0 - Internal Server Error scriptProcessor
could not be found in application configuration
Most likely causes: •IIS received the request; however, an internal
error occurred during the processing of the request. The root cause of
this error depends on which module handles the request and what was
happening in the worker process when this error occurred.
•IIS was not able to access the web.config file for the Web site or
application. This can occur if the NTFS permissions are set
incorrectly.
•IIS was not able to process configuration for the Web site or
application.
•The authenticated user does not have permission to use this DLL.
•The request is mapped to a managed handler but the .NET Extensibility
Feature is not installed.
Things you can try:
•Ensure that the NTFS permissions for the web.config file are correct
and allow access to the Web server's machine account.
•Check the event logs to see if any additional information was logged.
•Verify the permissions for the DLL.
•Install the .NET Extensibility feature if the request is mapped to a
managed handler.
•Create a tracing rule to track failed requests for this HTTP status
code. For more information about creating a tracing rule for failed
requests, click here.
Detailed Error Information:
Module FastCgiModule
Notification ExecuteRequestHandler
Handler Django Handler
Error Code 0x80070585
Requested URL http://127.0.0.1:8003/
Physical Path C:\inetpub\wwwroot\Django\FirstSite
Logon Method Anonymous
Logon User Anonymous
More Information: This error means that there was a problem while
processing the request. The request was received by the Web server,
but during processing a fatal error occurred, causing the 500 error.
View more information »
Microsoft Knowledge Base Articles: •294807
Is there any way to fix this error? Are there any extra steps for Python 3.4?
Found my error. The Handler Mapping Executable argument was pointing to fastcgi.py instead of wfastcgi.py

Configured the WCF service on Windows Server 2012

I have windows server 2012 and sharepoint 2013 installed. Now i wanted to configured my wcf service on the server.
After Creating the new app pool & site its shows me the error as below
HTTP Error 500.19 - Internal Server Error
The configuration section 'system.serviceModel' cannot be read because it is missing a section declaration
Also i have found the solution on the link below
HTTP Error 404.17 - Not Found
where suggested to run the command "servicemodelreg -i". I have did the same and my service started working. But the sharepoint services are stopped working showing the below error
Exception message: Could not load type 'System.ServiceModel.Activation.HttpModule' from assembly 'System.ServiceModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'.
Please help me out to the resolve this problem.....
Thanks is advance

HTTP 404 ERROR while starting application in cloudfoundry

hello friends i developed a simple java web application and hosted in vmware cloudfoundry but i am unable to launch my application in the browser . it gives this error
HTTP Status 404 - /
type Status report
message /
description The requested resource (/) is not available.
Apache Tomcat/6.0.35
kindly reply me at aravnd8babu#gmail.com
Did you add the application URL in your host file? If not add a new entry i.e:
Cloudfoundry-IP applicationName.vcap.me
In your local tomcat the URL is localhost:8080/applicationName but in cloudfoundry it is applicationName.vcap.me
Run the command "vmc apps" and provide the output.

deploy web app to jetty: service_unavailable

i have a gwt app deployed to Jetty, i use maven, maven-jetty-plugin, following the instruction provided here: http://docs.codehaus.org/display/JETTY/Maven+Jetty+Plugin, my project follows the maven structure so no configuration needed, all i need is to run : mvn jetty:run, then i can see jetty server started, back to browser, i typed 127.0.0.1:8080 i saw a page with Error 404 -Not Found, saying:
No context on this server matched or handled this request.
Context known to this server are:
/console --> org.mortbay.jetty.plugin.Jetty6PluginWebAppContext#1c093b3c{/console./Users/Hj/Documents/workspace/samples/console/src/main/webapp}
and that's my webapp '/console', so i click that link, it went to 127.0.0.1:8080/console url and here is the message on that page:
HTTP ERROR: 503
Problem accessing /console. Reason: SERVICE_UNAVAILABLE
does anyone know what's wrong here? i think the web app was deployed to Jetty, how come it says service unavailable? thanks.