Feeds:
Posts
Comments

Archive for the ‘Windows IIS’ Category

IIS7 Configuration paths

IIS7, the configuration system stores configuration in a hierarchy of files, starting with 3 root configuration files, and descending into distributed web.config configuration files that can be present in any directory of your website to affect the configuration for the url namespace to which the directory corresponds.  This hierarchy contains the following:

Framework\<version>\CONFIG\machine.config (the .NET framework machine.config file, where most .NET sections are declared)
Framework\<version>\CONFIG\web.config (the .NET framework root web.config file, where most ASP.NET sections are declared)
%windir%\system32\inetsrv\applicationHost.config (the IIS7 global web server configuration file, where all IIS7 configuration sections are declared)
delegated web.config files (the distributed configuration files that can be present in any virtual directory of your site or its subdirectory)

In this system, a configuration path has the following syntax:

MACHINE/WEBROOT/APPHOST/<SiteName>/<VirtualPath>

Where MACHINE, WEBROOT, and APPHOST correspond to the above configuration files, <SiteName> identifies the site, and <VirtualPath> identifies the virtual path.  Note that the site is no longer identified by id, as before, and instead the site name is used (in IIS7, site name is the unique identifier of a site, unlike the ServerComment in IIS6 which was not unique).

Advertisements

Read Full Post »

IIS 7.5 includes a new application as auto-start feature in its ASP.NET 4.0 implementation. This feature enables an administrator to configure an application pool to start up automatically, while temporarily not processing HTTP requests.

This allows applications requiring extensive initialization to finish loading the data they need or to complete other processes before they begin accepting HTTP requests. To use this feature, you must add code like the following to the pool’s applicationHost.config file:

<applicationPools>
<add name=”MyApplicationPool” startMode=”AlwaysRunning” />
</applicationPools>

Read Full Post »

CLR –

Stands for Common Language Runtime (CLR) is a core component of Microsoft’s .NET initiative. It is Microsoft’s implementation of the Common Language Infrastructure (CLI) standard, which defines an execution environment for program code. In the CLR, code is expressed in a form of bytecode called the Common Intermediate Language (CIL, previously known as MSIL—Microsoft Intermediate Language).

CLR diag.svg

Developers using the CLR write code in a language such as C# or VB.NET. At compile time, a .NET compiler converts such code into CIL code. At runtime, the CLR’s just-in-time compiler converts the CIL code into code native to the operating system. Alternatively, the CIL code can be compiled to native code in a separate step prior to runtime by using the Native Image Generator (NGEN). This speeds up all later runs of the software as the CIL-to-native compilation is no longer necessary.

Let see, how this CLR is enabled by administrators to switch versions without modifying the underlying IIS infrastructure. You can specify different CLR settings for individual application pools by creating custom ASPNET.config files. To use these files, you add code specifying their locations to the pool’s applicationHost.config file, as in the following example:

<applicationPools>
<add name=”MyApplicationPool” CLRConfigFile=”c:\InetPub\CLRConfigFile.txt” />
</applicationPools>

The Physical path for ApplicationHost.Config was is %windir%\system32\inetsrv\applicationHost.config

Note: This applicable for IIS 7 and 7.5 versions.

Read Full Post »

Error :-

Could not find the path of
C:\Windows\assembly\GAC_MSIL_<Dll Name>_<GAC ID>\Bin

This error occurs because of your IIS currently not supporting 64bit applications, so you need to enable the 64bit compatibility on IIS and you can resolve this by using the following steps on different IIS versions based your requirements.

In IIS6.0

Step 1: Click Start, click Run, type cmd, and then click OK.
Step 2: Type the following command to disable the 32-bit mode:

cscript %SYSTEMDRIVE%\inetpub\adminscripts\adsutil.vbs SET W3SVC/AppPools/Enable32bitAppOnWin64 0

Step 3: Type the following command to install the version of ASP.NET 2.0 and to install the script maps at the IIS root and under:

%SYSTEMROOT%\Microsoft.NET\Framework64\v2.0.50727\aspnet_regiis.exe -i

Step 4: Make sure that the status of ASP.NET version 2.0.50727 is set to Allowed in the Web service extension list in Internet Information Services Manager(if your application deployed on windows 2003 or 2008).

In IIS7.0

Step 1:Open the Internet Information Service Manager from Start Menu or Control Panel –> Administrative Tools.
Step 2: Expand the Application Pools Node then find your Website Application Pool then right click on it then click on Advanced Settings, it will popup the settings screen here you need to set false for Enable32bitApplication.This settings may affect your existing 32bit application,if you get any error on your 32 applications then you reset the above setting and create a new application pool just like existing on and use it for 64bit with appropriate Enable32bitApplication setting (value must be false).

Read Full Post »

The following steps to replicate in Windows 2003 IIS,

  1. Open Internet Information Services (IIS)
  2. Expand the domain and locate the directory which should be viewed securely
  3. Right-click this folder and select Properties. Click on the Directory Security tab and under the section entitled Secure Communications, click the Edit button

  4. In the Secure Communications window, check the checkbox for Require Secure Channel. Click OK to close this window. Click OK to close the previous window and now when going to the site, you should be asked to append https:// to the URL

Give a try ….  🙂

Read Full Post »

CreateRecordset error ‘8004181d’  There is no catalog.

/Search/query.asp, line 215

Try this:

1. Go to the Start > Programs > Administrative Tools >  Computer Management
2. Click on Services and Applications, then select Indexing Service. If there is no Indexing Service, you may need to install this Component.
3. Right click the Indexing Service, then select New > Catalog.
4. Type in the Catalog Name (that will using later in your script), and the location you need to indexing.

Read Full Post »

Web Deploy

Web Deploy (Web Deployment Tool) is an IIS extension,
containing essentially a set of tools and a managed framework for
simplifying the deployment, management and migration of Web
applications, synchronizing sites, and even entire servers.

Synchronizes, 

 

  • Content
  • IIS configuration
  • Certificates
  • Registry keys
  • ASP.NET configuration

In other words,  Web Deployment Tool (formerly called MS Deploy) is an IIS extension that enables administrators to package entire Web sites, Web servers, and applications for deployment on other computers, or just for backup purposes. Packages include all of a site’s content, including configuration settings, permissions, databases, and certificates.  WebDAV Publishing Enables users to publish content to IIS Web sites interactively and securely.

Web-based Distributed Authoring and Versioning (WebDAV) is an IIS extension, now implemented as a role service called WebDAV Publishing, which expands the capabilities of the Hypertext Transfer Protocol (HTTP) by making it possible for administrators and users to publish documents on Web sites simply by copying them to a mapped network drive.

(i.e) Using a feature called the WebDAV redirector on the client computer, you map a drive to your Web site.  Copying files to that drive automatically publishes them on the Web site.

Read Full Post »

Older Posts »