iis-8

I have never used Windows Authentication for ASP.NET MVC web applications before, but Forms Authentication. Recently, I have had an ASP.NET MVC 4 web application that requires a Windows Authentication implementation for users who are granted to log in my company web server. So, I have some questions regarding Windows Authentication. I am using Visual Studio 2012. How does Windows Authentication work? How do I implement Windows Authentication correctly in the web.config file? How do I test if the Windows Authentication really works for my ASP.NET MVC 4 web site? In other words, how do I test it

I have a simple webAPI build by Visual Studio 2013. It works well when I run it from VS13 but when I copy the project in local IIS it gives me the following 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 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

I'm trying to get a wcf service running in IIS8 on 2012 build 8400. When installing the web role the wcf stuff (under 3.51) wasn't to be found like in 2008. When installed the svc handler mapping was missing, so i did a: %windir%\Microsoft.NET\Framework\v3.0\WindowsCommunication Foundation\ServiceModelReg.exe –i Now the handler mapping is there, but I still get: The resource you are looking for does not have a handler associated with it. (I removed the static file handler.) The site is using the classic pipeline in order to use impersonation. More specifically: Run Server Manager (on task bar

On Windows Server 2012 R2, after installing update KB4340558 (update history) / KB4338424 (installed updates) we can no longer instantiate .NET .DLLs (interop) in classic ASP in 32-bit mode using server.createobject . We receive the error 0x800A01AD "ActiveX component can't create object" When we uninstall the update, the error disappears. Despite my best efforts, I was unable to find an alternate solution to uninstalling. We would prefer to reinstall the update and make whatever changes were necessary to Windows Server and/or the DLL's to allow the COM objects to be instantiated properly.