|
|
By Atiq, on October 30th, 2010%
Solving ReportViewer Rendering Issue on IIS7
Applies to:
Internet Information Services 7.0 (IIS7) Microsoft Report Viewer Redistributable 2005
Symptoms:
Unable to render ReportViewer on ASP.NET Web pages while running on IIS7. You have no problem viewing your reports when running on debug mode with your Visual Studio 2005. You are able to view your reports on Report Manager but not able to view them on IIS7. You encounter . . . → Read More: Solving ReportViewer Rendering Issue on IIS7
By Atiq, on October 30th, 2010%
IIS versions before 7.0 did not require <handlers> for AJAX to work. If you are installing AJAX on new IIS7 servers, you will have to make sure you have the following code in your web.config:
<!– The system.webServer section is required for running ASP.NET AJAX under Internet Information Services 7.0. It is not necessary for previous version of IIS. –> <system.webServer> <validation validateIntegratedModeConfiguration=”false”/> <modules> <remove name=”ScriptModule”/> <add name=”ScriptModule” preCondition=”managedHandler” type=”System.Web.Handlers.ScriptModule, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35″/> </modules> <handlers> <remove name=”WebServiceHandlerFactory-Integrated”/> <remove name=”ScriptHandlerFactory”/> <remove name=”ScriptHandlerFactoryAppServices”/> <remove name=”ScriptResource”/> <add name=”ScriptHandlerFactory” verb=”*” path=”*.asmx” preCondition=”integratedMode” type=”System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35″/> <add name=”ScriptHandlerFactoryAppServices” verb=”*” path=”*_AppService.axd” preCondition=”integratedMode” type=”System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35″/> <add name=”ScriptResource” verb=”GET,HEAD” path=”ScriptResource.axd” preCondition=”integratedMode” type=”System.Web.Handlers.ScriptResourceHandler, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35″/> </handlers> </system.webServer>
By Atiq, on October 30th, 2010%
 Problem: Server Error in ‘/’ Application. ——————————————————————– The ‘Microsoft.Jet.OLEDB.4.0′ provider is not registered on the local machine. Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: System.InvalidOperationException: The ‘Microsoft.Jet.OLEDB.4.0′ provider is not registered on the local machine.
Solution:
You will get this error on . . . → Read More: How To Fix ‘Microsoft.Jet.OLEDB.4.0′ error
By Atiq, on October 30th, 2010%
HTTP Error 500.19 – Internal Server Error The requested page cannot be accessed because the related configuration data for the page is invalid. 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”. 226: <system.webServer> 227: <handlers> . . . → Read More: How To Fix overrideMode=”Deny” Error (HTTP Error 500.19)
By Atiq, on October 30th, 2010%
If you need a domain URL redirection from yourdomain.com to www.testdomain.com or vise versa, you can do something like this:
Place either of these (depending on what you’d like done. And edit to match your domain) inside the <system.webServer></system.webServer> tags in the web.config of the domain.
<rewrite><rules> <rule name=”Add WWW prefix” > <match url=”(.*)” ignoreCase=”true” /> <conditions> <add input=”{HTTP_HOST}” pattern=”^testdomain\.com” /> </conditions> <action type=”Redirect” url=”http://www.testdomain.com/{R:1}” redirectType=”Permanent” /> </rule>
—————–
<rule . . . → Read More: How to Create Rewrite Rule in web.config
By Atiq, on October 30th, 2010%
Internet Information Services 7 (IIS7) doesn’t use metabase-like file from IIS6. Instead the settings and configuration are stored in schema files and applicationHost.config files.
Since the configuration files are different, the old IIS6 tools will not be able to backup IIS7 settings.
This is the new script that you can use to backup your IIS7 web servers.
1. Using notepad or any text editor create a file backupiis7.cmd
. . . → Read More: Backup IIS7 ApplicationHost.config and Settings
By Administrator, on September 27th, 2010%
In our first community post we covered a workaround you can apply immediately on your sites and applications to prevent attackers from exploiting it. Today, we are revising it to include an additional defensive measure. This additional step can be done at a server-wide level, and should take less than 5 minutes to implement. Importantly, this step does not replace the other steps in the original workaround, rather it should be done in addition to the steps already in it. Below are instructions on how to enable it. . . . → Read More: ASP.NET Security Vulnerability Workaround
|
|
|