Handler "Plesk_Handler_0536784851" has a bad module "ManagedPipelineHandler" in its m

[Silence]

HI There,

I have another error from other domain:

URL http://82.102.15.79/$sitepreview/wkk.pt/index.aspx

HTTP Error 500.21 - Internal Server Error
Handler "Plesk_Handler_0536784851" has a bad module "ManagedPipelineHandler" in its module list Detailed Error InformationModule IIS Web Core
Notification ExecuteRequestHandler
Handler Plesk_Handler_0536784851
Error Code 0x8007000d
Requested URL http://wkk.pt:80/index.aspx
Physical Path C:\inetpub\vhosts\wkk.pt\httpdocs\index.aspx
Logon Method Anonymous
Logon User Anonymous

Can you help?

Thanks.

 

[PedroR]

Hi Silence,

I'm facing the same problem.
My main page opens correctly. But when I try to open a virtual directory or sub-domain I get the exact same error (above).
I sent an email to plesk, and they change the Managed Pipeline Mode of plesk(default)(2.0)(pool) in IIS to "pipeline" (before was in classic).

Now, the virtual directories and sub-domains works great, but the main page opens the Default.aspx not index.html which is supposed to open.
I'm looking an answer for days.

Does anyone know how to solve this?
Thanks in advance.

 

[Silence]

Hey, just go to IIS, domain.com, handlers, Inherhit and it's done!

 

[deadeye]

Classic Support?

This is great. It has fixed my problem for now.

The big issue is when the client goes into Plesk and makes changes then Plesk gets confused and changes some settings back to Integrated and the website breaks.

When will Plesk have Classic Support as this is a massive need for most clients right now.

 

[Silence]

I don't lost time with this problem yet, but in every domains i need to do this...

Thanks

 

[f4cio]

Where exactly is that option in IIS?

I got same error on machine where I had plex client and server and then migrated few websites to that machine via IEMT ...