Sembrerebbe di sì Spark è alive.

http://www.microsoft.com/web/downloads/platform.aspx

The Error Pages icon was missing from Internet Information Services Manager on my Vista machine.

This feature will need to be turned on in Windows Features:
Control Panel > Programs and Features > Turn Windows features on or off

Check the box next to:
Internet Information Services > World Wide Web Service > Common Http Features > HTTP Errors.

Unable to start debugging on the web server.

Server side-error occurred on sending debug HTTP request. Make sure the server is operating correctly. Verify there is no syntax errors in the web.config by doing a Debug.Start without Debugging. You also want to refer to the ASP.NET and ATL Server debugging topic in the online documentation.

Microsoft Vista Business, IIS 7.0, Visual Studio 2005

I was getting this error whilst trying to debug a Visual Studio 2005 .NET v2.0 project which uses the local IIS rather than the built in Visual Studio Development Server.

I tried many things to fix this error, permissions, updates, reg_iis, etc. However what worked for me was by changing the Application Pool for my application from DefaultAppPool to Classic .NET AppPool.

Why does this work? By default the DefaultAppPool runs in Integrated Managed Pipeline Mode and the Classic .NET AppPool runs in Classic Managed Pipeline Mode.

Integrated Managed Pipeline Mode
This is new in IIS 7.0 and essentially wraps IIS and ASP.NET into one process model.

Classic Managed Pipeline Mode
This is backwards compatibility mode for IIS 7.0 and handles requests in an IIS 6.0 worker process. IIS and ASP.NET are separated.

So why did this break my app?
My app was originally upgraded from an earlier version of .NET to .NET 2.0 and so is not IIS 7.0 compliant. I will need to migrate it so it can utilise the new integrated mode in IIS 7.0. This migration process is documented here.
http://learn.iis.net/page.aspx/381/aspnet-20-breaking-changes-on-iis-70/

Update
The HTTP Error I was receiving was 500.24. By following the article above all I needed to do to add the below to the web.config and now my app runs correctly in Integrated Managed Pipeline Mode.

<system.webServer>
<validation validateIntegratedModeConfiguration=”false” />
</system.webServer>

چنانکه همه می‌دانیم برنامه های ایرانی بر اساس محدودیت تعداد کاربران به فروش می‌رسند که در اینجا نمی‌خواهم در ارتباط با اینکه این موضوع خوب است یا بد صحبت کنم. می خواهم راهی را برای محدود کرد تعداد کاربران همزمان به برنامه نویس ها نشان بدهم.

—————————————————————-

این مطلب زیر نظر مجوز GFDL منتشر می‌شود. و کلیه حقوق آن برای همگان آزاد است، بدین شرط که به کلیه شرایط موجود در مجوز GFDL ( که یک نسخه از متن انگلیسی مجوز GFDL در این محل و یک ترجمه غیر رسمی (فارسی) از متن مجوز GFDL که در مرداد ۱۳۸۳ توسط کاوه رنجبر تهیه شده است در این محل ) قرار دارد پایبند باشد.

GNU Logo

عنوان و لینک مطلب اصلی : Tip #88: Did you know… To not stress your server, limit the number of concurrent requests

عنوان مطلب بازنویسی شده : محدود کردن تعداد کاربران همزمان یک برنامه تحت وب

بخش ثانی : ندارد

تاریخ انتشار : 19/04/1388 مطابق با 10/07/2009

تاریخ بازنویسی : 23/04/1388 مطابق با 14/07/2009

شماره نسخه اصلی : نسخه یک

شماره نسخه بازنویسی : نسخه دو

نویسنده : Carlos Aguilar Mares

بازنویس : ناصر حاجلو

ای-میل بازنویس : n.hajloo@gmail.com

Copyright (c) 2009 Carlos Aguilar Mares & Nasser Hajloo.

Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation;

with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled “GNU Free Documentation License”.

—————————————————————-

راه‌های زیادی برای محدود کردن تعداد کاربران وجود دارد که هر کدام مزیتها ومعایب خودشان را دارند. چندی پیش مایکروسافت، یک add-on برای IIS با نام IIS SEO  ارائه کرد که استفاده آن برای وبسایت‌ها توصیه می‌شود. این add-on یک امکان برای محدود کردن تعداد کاربران دراختیار شما می‌گذارد که در زیر با آن آشنا می‌شویم.

پیش از ادامه باید متذکر شوم که این مطلب را  کارلوس آگویلار مارس در وب‌سایت Tips & Tricks for ASP.NET, IIS, and Visual Web Developer نوشته و می‌توانید اصل مطلب را به زبان انگلیسی اینجا مطالعه کنید. ( در اصل مطلب توضیحاتی در ارتباط با مزایای محدود کردن تعداد کاربران و نیز قابلیت‌هایی که در آینده به نسخه اصلی اضافه خواهد شد هم نوشته شده که من از ذکر آنها خودداری کردم.)

برای محدود کردن تعداد (درخواست) کاربران همزمان به روش زیر عمل کنید:

به صفحه Site Analysis Reports بروید. ( نیاز به نصب add-onی با نام IIS SEO دارد )

بر روی Edit Feature Settings  کلیک کنید.

انتخاب Edit Feature Settings ( عکس از منبع اصلی مطلب )

از پنجره باز شده در قسمت Maximum Number of Concurrent Requests  تعداد مورد نظرتان را بین یک تا شانزده مشخص کنید ( مقدار پیش فرض هشت است )

محدود کردن تعداد کاربران همزمان ( عکس از منبع اصلی مطلب )

اگر شما راه دیگری می‌شناسید آن را با ما قسمت کنید. تا با مقایسه روش‌های متفاوت ، آن را که مناسب تر است انتخاب کنیم.

The release of IIS 7.0 coincides with the ten-year anniversary of the release of the first version of IIS, in Windows NT® 4.0. In 2001, four versions later, IIS 5.0 became the most prevalent Web server on the Internet, though months later it fell victim to the infamous Code Red and Nimbda worms. IIS 6.0, released in Windows Server® 2003, was a major rewrite of the server, focused entirely on improving security, reliability, and performance. Since then, IIS 6.0 has proven to be a rock-solid Web server, achieving high reliability and security track records with only a single critical security bulletin since its release (which was not exploitable remotely).

The vision for IIS 7.0 was to take the speed, reliability, and security of the IIS 6.0 codebase and turn it into a highly extensible and manageable Web server platform powerful enough to run Web applications of the future. The result is the most ambitious Microsoft Web server yet, delivering the largest number of architectural improvements in the history of IIS.
At the core of the IIS 7.0 release is a completely modular Web server, comprised of more than 40 features that can be assembled into small-footprint Web servers optimized for the desired role in your application topology. These features are built on top of a new extensibility layer that allows developers to extend or replace virtually any aspect of the server, in native code or with the Microsoft® .NET Framework. IIS 7.0 offers extensibility throughout its runtime, management, and operational features to help you build end-to-end solutions for your specific needs. On top of the core platform, IIS 7.0 tackles many of the problems associated with the manageability and operation of the server. It features a brand new configuration system that enables fully delegated management of sites and finally makes xcopy deployment of Web applications a reality. The new management APIs and diagnostic features make deployment, administration, and troubleshooting of the server significantly easier and more convenient than ever before.

Integration with ASP.NET in IIS 6.0 and IIS 7.0

 source: http://msdn.microsoft.com/en-us/magazine/cc163453.aspx

I have an Active Directory domain service account that has permissions to a share on our SAN that will host IIS web site content.  I needed to allow IIS to access the share via the service account.  Here’s how to do it in IIS 7.0 on Windows Server 2008:

1. Open Server Manager > Roles > Web Server (IIS) > Internet Information Services (IIS) Manager > ServerName > Sites > WebSiteName
2. Double click Authentication > Anonymous Authentication > Edit
3. Under Anonymous user identity, select Specific User > Set
4. Enter the user name and password > OK > OK 
5. Restart the web site

When you host a .NET application on a remote network share, you may receive a System.SecurityException exception error message or a security warning message.

The Code Access Security Policy tool (CASPOL) enables administrators to modify security policy for the machine policy level, the user policy level, and the enterprise policy level.

Caspol is used to fully trust a remote share, since by default network shares only get LocalIntranet permissions.

The solution for the System.SecurityException exception error message is to use caspol to grant a .NET application the FullTrust right to a network share. To do this:

1. Launch a command prompt with administrative credentials

2. Change to the C:\Windows\Microsoft.NET\Framework\v2.0.50727 directory.

3. Run the following command:

caspol -m -ag 1 -url “file://\\server\share\*” FullTrust -exclusive on

Replace \\server\share\ with the path to your .NET application located on the remote network share.

Running the above command allowed me to resolve the following IIS 7.0 error:

SecurityException: Request for the permission of type ‘System.Web.AspNetHostingPermission, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089′ failed

By the way, .NET Framework 3.5 SP1 allows managed code to be launched from a network share.

References:

http://support.microsoft.com/?id=320268

http://blogs.msdn.com/shawnfa/archive/2004/12/30/344554.aspx

http://books.google.com/books?id=VJOtwMawoswC&pg=PA576&lpg=PA576&dq=iis+7.0+caspol.exe&source=bl&ots=W88GOo1Cfp&sig=U8sBtcNzbaSgPTghAp519S9O3sM&hl=en&ei=o1zSSeafEobmnQfHrbzlBQ&sa=X&oi=book_result&resnum=1&ct=result

http://www.iislogs.com/articles/23/

http://support.microsoft.com/kb/837909

http://www.sharepointblogs.com/ssa/archive/2007/09/06/using-caspol-exe-to-add-assemblies-to-full-trust-assembly-list.aspx

http://www.dotnetjunkies.ddj.com/quickstart/howto/doc/security/SecScripting.aspx

I received the below error whilst trying to debug an ASP.NET app using Visual Studio 2005 on Windows Vista using IIS 7.0

The web server is not configured correctly. See help for common configuration errors. Running the web page outside of the debugger may provide further information.

Turns out that compilation debug = true needs to be specified in the web.config

<compilation debug=”true”>

To export a backup copy of your IIS 7.0 configuration on a Windows 2008 Server:

Open Server Manager

Expand Roles – Web Server (IIS) – Internet Information Services (IIS) Manager

Highlight the web server name

From the Management category, double click Shared Configuration

Under Actions, select Export Configuration. Accept or change the default export path of C:\Windows\system32\inetsrv\config\export

Click the Connect As button, and enter administrative credentials. If the server is a domain member, you may need to enter your credentials in the format domain\username or username@domain.com

Enter the encryption keys password twice and press OK

You should now have three files in the C:\Windows\system32\inetsrv\config\export directory: administration.config, applicationHost.config, and configEncKey.key. Save the files in a safe place.

Um dos maiores pesadelos dos administradores de redes sao os ataques de negação de serviço DoS (Denial of Service) onde um atacante se aproveita de debilidades ou do modelo para comunicação OSI e seus protocolos ou de falhas de sistemas de informação, com o intuito de paralisar redes de dados.

Pois bem, a Microsoft, e eu lembro bem teve ja durante alguns anos os seus sistemas como dos mais vulneraveis a ataques DoS, até falhas causadas por simples emissão de pacotes ICMP já chegaram a criar problemas graves a diversas redes. Hoje a situação é bem diferente, continuamos claro com o mesmo modelo OSI que nao oferece todas as garantias de confiabilidade em se tratando de protecção contra ataques de negação de serviço, mas por outro lado algumas ferramentas têm sido criadas para ajudar os administradores de redes a protegerem as suas redes de ataques deste genero.

O modulo ‘Dynamic IP Restrictions’ para IIS 7.0 é um desses casos. Ele oferece a possibilidade de se:
- Bloquear requisições excessivamente concorrentes que podem aumentar substancialmente o tráfego da rede.
- Bloquear requisições baseadas num certo periodo temporal.
- Especificar que tipo de resposta dar a requisições, que sao negadas (respostas 403, 404, até customizadas).
- Gravar em arquivo log requisições negadas.
- Ver lista de IPs bloqueados.
- Suporte a IPV6.

Tutorial

در حال ارتقا برنامه شرکت از نسخه ۲۰۰۵ به ۲۰۰۸ ، مشکلاتی پیش آمد که بعضی از آنها راقبلا  در اینجا آوردم. اما بعضی مکلات بصورت پنهان باقی مانده بود و زیاد خودنمایی نمی کرد، چون اصلا کسی به سمت آن هم نرفته بود . مثلا برنامه ما بدون هیچ مشکلی در IIS 6.0 اجرا میشد و پس از ارتقای نسخه هم هیچ مشکلی پیش نیامد. به تازگی روی یکی از سیستمهای شرکت ویندوز ویستا را به جهت تست یکسری موارد ارزیابی نشده نصب کردیم و خواستیم تا برنامه شرکت را روی IIS 7.0 نصب و اجرا کنیم.

خود من به شخصه قبلا خیلی کم از IIS استفاده کردم و در راهبری IIS قوی نیستم، اما در شرکت افرادی هستند که خیلی خوب روی IIS کار کرده اند به همین دلیل هیچ وقت فکر نمی کردیم که به مشکلی هم بر بخوریم . اولین باری که من برنامه را روی IIS 7.0 ( که روی ویستا هست ) نصب کردم اصلا برنامه اجرا نشد و بخاطر ضعف دانشی که از IIS داشتم مشکل را با کسی مطرح نکردم و خواستم تا مشکل را با یک جستجوی ساده روی اینترنت حل کنم. بخاطر کمبود وقتت بررسی مشکل به فراموشی سپرده شد تا اینکه بنا به دلایلی محبور به اجرای برنامه روی IIS 7.0 شدیم.

تا پیش از این (‌نسخه II 7.0 به قبل ) همه وب سایت ها و برنامه ها در یک WebSite مادر با نام Default Web Site نصب و اجرا میشد و این محدودیت های بسیاری را ایجاد می کرد ( مثلا شما نمی توانید در آن واحد بیش از یک اینستنس را اجرا کنید و مشکلات مشابه ) در IIS 7.0 این مشلات برطرف شده و شما می توانید تعداد متعددی از وب سایت های وادر را داشته باشید و وب سایت های مشتریان را نسبت به نوع یا میزان دسترسی و یا چه و چه در وب سایت های مختلف قرار بدهید .

پنجره ایجاد یک WebApplication در IIS 7.0

یکی از مزایای IIS 7.0 استفاده از یک Application Pool یکپارچه است به این مفهوم که برنامه یا وب سایت نصب شده بصورت یکپارچه از این Application Pool استفاده می کند . با این که این خاصیت مزیت بزرگی محسوب می شود بیشتر برنامه ها و یا وب سایت هایی که در Visual Studio 2005 ایجاد شده اند نمی توانند بصورت یکپارچه از Application Pool استفاده کنند . برای همین باید از Application Pool قدیمی که در نسخه IIS 6.0 به قبل بود استفاده کنند . که بصورت کاملا جداگانه از خود IIS به برنامه دسترسی داشت .

به همین دلیل بیشتر برنامه هایی که ما در شرکت تولید کرده بودیم روی IIS 7.0 اجرا نمیشد . برای حل این مشکل و اجرای صحیح برنامه ها و وب سایت هایی که در نسخه های قبلی IIS بخوبی اجرا می‌شدند باید Application Pool دیگری برای وب سایت استفاده کنید . برای رفع این مشکل بصورت زیر عمل کنید .

     ۱-     بر روی Web Site مادری که می خواهید برنامه تان در آن اجرا شود کلیک راست کرده و گزینه Add Application را انتخاب کنید . ( مثلا روی Default Web Site )

     ۲-     از پنجره ای که باز می شود یک نام ( Alias ) برای برنامه تان انتخاب کرده و در قسمت روبریی بر روی Select کلیک کنید تا پنجره  Select Application Pool باز شود

     ۳-     بعد از باز شدن این پنجره از منوی پایین افتادنی بر روی Classic .net AppPool کلیک کنید تا انتخاب شود و پس از انتخاب بر روی OK کلیک کنید .

پنجره تغییر Default ApplicationPool به Classic .net ApplicationPool

     ۴-     مسیر برنامه تان را روی هارد مشخص کرده و بر روی OK کلیک کنید .

با اتمام این مراحل اگر مشکل دیگری نداشته باشید برنامه شما باید بصورت صحیح اجرا شود .

Hi All, Recently I come to situation where I need to Configure Reporting services on server having configuration: Window server 2008 and IIS 7.

I need to configure reports in manner, so User can access this reports thru External IP Address.

I found one interestign thing with IIS 7.0, so user can access reports externally.

To able to access the reports externally, do the steps as mentioned below:

1. Create Virtual Directory in IIS 7.0 :

2. Go to Handler Mappings :

3. Double Click on “Handler Mapping”. You will get screen like the given below:

4. Now see Top Right Corner: Click On “Add Managed Handler”. Here you need to fill up the info like:

Fill this info as:

Request path:      Reserved.ReportViewerWebControl.axd
Type:                    Microsoft.Reporting.WebForms.HttpHandler
Name:                  Reserved-ReportViewerWebControl-axd

Thats it. Now try with External IP.

You can access the reports with  External IP too.

Introduction

IIS 7.0 allows for extending the server by modules which are developed in two ways:

• Using managed code, and the ASP.NET server extensibility APIs
• Using native code, and the IIS 7.0 native server extensibility APIs

In the past, ASP.NET modules were limited in functionality, as the ASP.NET request processing pipeline was separate from the main server request pipeline.

In IIS 7.0, managed modules become virtually as powerful as native modules with the Integrated Pipeline architecture. Most important, the services that managed modules provide can now be applied to all requests to the server, not just to requests to ASP.NET content like ASPX pages. Managed modules are configured and managed in a consistent manner with native modules, and can execute in the same processing stages and orderings as native modules. Finally, managed modules can perform a wider set of operations to manipulate request processing via several added and enhanced ASP.NET APIs.

This article illustrates extending the server with a managed module in order to add the ability to perform basic authentication against an arbitrary credential store, such as the provider-based credential infrastructure in the ASP.NET 2.0 Membership system.

This allows replacing the built in basic authentication support in IIS 7.0, which is tied to the Windows credential store, with one that supports arbitrary credential stores, or any of the existing Membership providers shipped with ASP.NET 2.0 like SQL Server, SQL Express, or Active Directory.

This article examines the following tasks:

• Developing a managed module using ASP.NET APIs
• Deploying a managed module on the server

To learn more about the basics of developing IIS 7.0 modules and handlers, see Developing IIS7 modules and handlers with the .NET framework.

You can also find lots of resources and tips on writing IIS 7.0 modules on the blog, http://www.mvolo.com/, as well as download existing IIS 7.0 modules for your applications. For some examples, see Redirecting requests to your application with the HttpRedirection module,  Nice looking directory listings for your IIS website with DirectoryListingModule, Displaying pretty file icons in your ASP.NET applications with IconHandler, and Stopping hot-linking with IIS and ASP.NET.

Note: The code provided in this article is written in C#.

Prerequisites

To follow the steps in this document, you must have the following IIS features installed:

ASP.NET

Install ASP.NET via the Windows Vista Control Panel. Select “Programs” – “Turn on or off Windows features”. Then open “Internet Information Services” – “World Wide Web Services” – “Application Development Features” and check “ASP.NET”.

If you have a Windows Server® 2008 build, open “Server Manager” – “Roles” and select “Web Server (IIS)”. Click “Add role services”. Under “Application Development” check “ASP.NET”.

Background Information on Basic Authentication

Basic authentication is an authentication scheme defined in the HTTP.1 protocol (RFC 2617). It uses a standard challenge-based mechanism that works as follows at a high level:

• Browser makes request to a URL with no credentials
• If the server requires authentication for that URL, it responds with a 401 Access Denied message, and includes a header that indicates that the basic authentication scheme is supported
• Browser receives the response, and if configured, will prompt the user for a username/password that it will include in plain text inside a request header for the next request to the URL
• Server receives the username / password inside a header, and uses them for authentication

Note: While a detailed discussion of this authentication protocol is outside the scope of this article, its worth mentioning that the basic authentication scheme requires SSL to be secure, as it sends the username/password in plain text.

IIS 7.0 and previous releases include support for basic authentication against the Windows accounts stored in the local account store or Active Directory for domain accounts. We want to enable our user to authenticate using basic authentication, but to validate credentials using ASP.NET 2.0 Membership service instead. This gives the freedom to store user information in a variety of existing Membership providers, such as SQL server, without being tied to Windows accounts.

Task 1: Developing a Module using .NET

In this task, we examine the development of an authentication module that supports the HTTP.1 basic authentication scheme. This module was developed using the standard ASP.NET module pattern available since ASP.NET v1.0. This same pattern is used to build ASP.NET modules that extend the IIS 7.0 server. In fact, existing ASP.NET modules written for previous versions of IIS can be used on IIS 7.0, and take advantage of better ASP.NET integration to provide more power to the web applications which use them.

Note: The full code for the module is provided in Appendix A.

A managed module is a .NET class that implements the System.Web.IHttpModule interface. The primary function of this class is to register for one or more events that occur within IIS 7.0 request processing pipeline, and then perform some useful work when IIS 7.0 invokes the module’s event handlers for those events.

Lets create a new source file named “BasicAuthenticationModule.cs”, and create the module class (the complete source code is provided in Appendix A):

public class BasicAuthenticationModule : System.Web.IHttpModule
{
void Init(HttpApplication context)
{
}
void Dispose()
{
}
}The primary function of the Init method is wiring the module’s event handler methods to the appropriate request pipeline events. The module’s class provides the event handle methods, and they implement the desired functionality provided by the module. This is discussed further in detail.

The Dispose method is used to clean up any module state when the module instance is discarded. It is typically not implemented unless the module uses specific resources that require to be released.

Init()

After creating the class, the next step is to implement the Init method. The only requirement is to register the module for one or more request pipeline events. Wire up module methods, which follow the System.EventHandler delegate signature, to the desired pipeline events exposed on the provided System.Web.HttpApplication instance:

public void Init(HttpApplication context)
{
//
// Subscribe to the authenticate event to perform the
// authentication.
//
context.AuthenticateRequest += new
EventHandler(this.AuthenticateUser);

//
// Subscribe to the EndRequest event to issue the
// challenge if necessary.
//
context.EndRequest += new
EventHandler(this.IssueAuthenticationChallenge);
}
The AuthenticateUser method is invoked on every request during the AuthenticateRequest event. We utilize it to authenticate the user based on the credential information present in the request.

The IssueAuthenticationChallenge method is invoked on every request during the EndRequest event. It is responsible for issuing a basic authentication challenge back to the client whenever the authorization module rejects a request, and authentication is needed.

AuthenticateUser()

Implement the AuthenticateUser method. This method does the following:

• Extract the basic credentials if present from the incoming request headers. To see the implementation of this step, see the ExtractBasicAuthenticationCredentials utility method.
• Attempts to validate the provided credentials via Membership (using the default membership provider configured). To see the implementation of this step, see the ValidateCredentials utility method.
• Creates a user principal identifying the user if the authentication is successful, and associates it with the request.

At the end of this processing, if the module was successfully able to obtain and validate the user credentials, it will produce an authenticated user principal that other modules and application code later use in access control decisions. For example, the URL authorization module examines the user in the next pipeline event in order to enforce the authorization rules configured by the application.

IssueAuthenticationChallenge()

Implement the IssueAuthenticationChallenge method. This method does the following:

• Check the response status code to determine whether this request was rejected.
• If so, issue a basic authentication challenge header to the response to trigger the client to authenticate.

Utility Methods

Implement the utility methods that the module uses, including:

• ExtractBasicAuthenticationCredentials. This method extracts the basic authentication credentials from the Authorize request header, as specified in the basic authentication scheme.
• ValidateCredentials. This method attempts to validate user credentials by using Membership. The Membership API abstracts the underlying credential store, and allows the credential store implementations to be configured by adding / removing Membership providers through configuration.

Note: In this sample, the Membership validation is commented out, and instead the module simply checks whether the username and password are both equal to the string “test”. This is done for clarity, and is not intended for production deployments. You are invited to enable Membership-based credential validation by simply un-commenting the Membership code inside ValidateCredentials, and configuring a Membership provider for your application. See Appendix C for more information.

Task 2: Deploy the module to the application

After creating the module in the first task, we next add it to the application.

Deploy to Application

First, deploy the module to the application. Here, you have several options:

• Copy the source file containing the module into the /App_Code directory of the application. This does not require compiling the module – ASP.NET automatically compiles and loads the module type when the application starts up. Simply save this source code as BasicAuthenticationModule.cs inside the /App_Code directory of your application. Do this if you do not feel comfortable with the other steps.
• Compile the module into an assembly, and drop this assembly in the /BIN directory of the application. This is the most typical option if you only want this module to be available to this application, and you do not want to ship the source of the module with your application. Compile the module source file by running the following from a command line prompt:

  <PATH_TO_FX_SDK>csc.exe /out:BasicAuthenticationModule.dll /target:library BasicAuthenticationModule.cs

  Where <PATH_TO_FX_SDK> is the path to the .NET Framework SDK that contains the CSC.EXE compiler.

• Compile the module into a strongly named assembly, and register this assembly in the GAC. This is a good option if you want multiple applications on your machine to use this module. To learn more about building strongly named assemblies, see this MSDN article .

Before making configuration changes in the application’s web.config file, we must unlock some of the configuration sections that are locked at the server level by default. Run the following from an Elevated command prompt (Start > Right click on Cmd.exe and choose “Run as Administrator”):

%windir%system32inetsrvAPPCMD.EXE unlock config /section:windowsAuthentication
%windir%system32inetsrvAPPCMD.EXE unlock config /section:anonymousAuthentication
After running these commands, you will be able to define these configuration sections in your application’s web.config file.

Configure your module to run in the application. Start by creating a new web.config file, which will contain the configuration necessary to enable and use the new module. Start by adding the text below and saving it to the root of your application (%systemdrive%inetpubwwwrootweb.config if using the root application in the Default Web Site).

<configuration>
<system.webServer>
<modules>
</modules>
<security>
<authentication>
<windowsAuthentication enabled=”false”/>
<anonymousAuthentication enabled=”false”/>
</authentication>
</security>
</system.webServer>
</configuration>
Before enabling the new basic authentication module, disable all the other IIS 7.0 authentication modules. By default, only Windows authentication and anonymous authentication are enabled. Because we do not want the browser to attempt authenticating with your Windows credentials or allow anonymous users, we disable both the Windows Authentication module and the Anonymous authentication module.

Now enable the module by adding it to the list of modules loaded by our application. Open web.config once again and add the entry inside to the <modules> tag

<add name=”MyBasicAuthenticationModule” type=”IIS7Demos.BasicAuthenticationModule” /> You can also deploy the module by using either the IIS 7.0 Administration Tool, or the APPCMD.EXE command line tool.

The final contents of the application’s web.config file after these changes are provided in Appendix B.

Congratulations, you have finished configuring the custom basic authentication module.

Let’s try it! Open Internet Explorer, and make a request to the application at the following URL:

http://localhost/

You should see the basic authentication login dialog. Enter “test” in the “User name:” field and “test” in the “Password:” field to get access. Note that if you copy HTML, JPG, or any other content to your application, they too will be protected by your new BasicAuthenticationModule.

Summary

In this article, you learned how to develop and deploy a custom managed module for an application, and enable that module to provide services for all requests to the application.

You also witnessed the power of developing server components in managed code. This allowed developing a basic authentication service that is decoupled from the Windows credential storage.

If you are adventurous, configure this module to leverage the power of the ASP.NET 2.0 Membership application services to support pluggable credential stores. See Appendix C for more information.

Find many resources and tips on writing IIS 7.0 modules in the blog, http://www.mvolo.com/, as well as download existing IIS 7.0 modules for your applications. For some examples, see Redirecting requests to your application with the HttpRedirection module,  Nice looking directory listings for your IIS website with DirectoryListingModule, Displaying pretty file icons in your ASP.NET applications with IconHandler, and Stopping hot-linking with IIS and ASP.NET.

Appendix A: Basic Authentication Module Source Code

Save this source code as BasicAuthenticationModule.cs inside the /App_Code directory to quickly deploy it to your application.

NOTE: If you are using Notepad, make sure to set Save As: All Files to avoid saving the file as BasicAuthenticationModule.cs.txt.

#region Using directives
using System;
using System.Collections;
using System.Text;
using System.Web;
using System.Web.Security;
using System.Security.Principal;
using System.IO;
#endregion

namespace IIS7Demos
{
///
/// This module performs basic authentication.
/// For details on basic authentication see RFC 2617.
///
/// The basic operational flow is:
///
///     On AuthenticateRequest:
///         extract the basic authentication credentials
///         verify the credentials
///         if succesfull, create the user principal with these credentials
///
///     On SendResponseHeaders:
///         if the request is being rejected with an unauthorized status code (401),
///         add the basic authentication challenge to trigger basic authentication.
///
///

public class BasicAuthenticationModule : IHttpModule
{
#region member declarations
public const String     HttpAuthorizationHeader = “Authorization”;  // HTTP1.1 Authorization header
public const String     HttpBasicSchemeName = “Basic”; // HTTP1.1 Basic Challenge Scheme Name
public const Char       HttpCredentialSeparator = ‘:’; // HTTP1.1 Credential username and password separator
public const int        HttpNotAuthorizedStatusCode = 401; // HTTP1.1 Not authorized response status code
public const String     HttpWWWAuthenticateHeader = “WWW-Authenticate”; // HTTP1.1 Basic Challenge Scheme Name
public const String     Realm = “demo”; // HTTP.1.1 Basic Challenge Realm
#endregion

#region Main Event Processing Callbacks
public void AuthenticateUser(Object source, EventArgs e)
{
HttpApplication application = (HttpApplication)source;
HttpContext context = application.Context;
String userName = null;
String password = null;
String realm = null;
String authorizationHeader = context.Request.Headers[HttpAuthorizationHeader];

//
//  Extract the basic authentication credentials from the request
//
if (!ExtractBasicCredentials(authorizationHeader, ref userName, ref password))
return;
//
// Validate the user credentials
//
if (!ValidateCredentials(userName, password, realm))
return;

//
// Create the user principal and associate it with the request
//
context.User = new GenericPrincipal(new GenericIdentity(userName), null);
}

public void IssueAuthenticationChallenge(Object source, EventArgs e)
{
HttpApplication application = (HttpApplication)source;
HttpContext context = application.Context;

//
// Issue a basic challenge if necessary
//

if (context.Response.StatusCode == HttpNotAuthorizedStatusCode)
{
context.Response.AddHeader(HttpWWWAuthenticateHeader, “Basic realm =”" + Realm + “”");
}
}
#endregion

#region Utility Methods
protected virtual bool ValidateCredentials(String userName, String password, String realm)
{
//
//  Validate the credentials using Membership (refault provider)
//
// NOTE: Membership is commented out for clarity reasons.
// !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
// WARNING: DO NOT USE THE CODE BELOW IN PRODUCTION
// !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
// return Membership.ValidateUser(userName, password);
if (userName.Equals(“test”) && password.Equals(“test”))
{
return true;
}
else
{
return false;
}
}

protected virtual bool ExtractBasicCredentials(String authorizationHeader, ref String username, ref String password)
{
if ((authorizationHeader == null) || (authorizationHeader.Equals(String.Empty)))
return false;
String verifiedAuthorizationHeader = authorizationHeader.Trim();
if (verifiedAuthorizationHeader.IndexOf(HttpBasicSchemeName) != 0)
return false;

// get the credential payload
verifiedAuthorizationHeader = verifiedAuthorizationHeader.Substring(HttpBasicSchemeName.Length, verifiedAuthorizationHeader.Length – HttpBasicSchemeName.Length).Trim();
// decode the base 64 encoded credential payload
byte[] credentialBase64DecodedArray = Convert.FromBase64String(verifiedAuthorizationHeader);
UTF8Encoding encoding = new UTF8Encoding();
String decodedAuthorizationHeader = encoding.GetString(credentialBase64DecodedArray, 0, credentialBase64DecodedArray.Length);

// get the username, password, and realm
int separatorPosition = decodedAuthorizationHeader.IndexOf(HttpCredentialSeparator);

if (separatorPosition <= 0)
return false;
username = decodedAuthorizationHeader.Substring(0, separatorPosition).Trim();
password = decodedAuthorizationHeader.Substring(separatorPosition + 1, (decodedAuthorizationHeader.Length – separatorPosition – 1)).Trim();

if (username.Equals(String.Empty) || password.Equals(String.Empty))
return false;

return true;
}
#endregion

#region IHttpModule Members
public void Init(HttpApplication context)
{
//
// Subscribe to the authenticate event to perform the
// authentication.
//
context.AuthenticateRequest += new
EventHandler(this.AuthenticateUser);
//
// Subscribe to the EndRequest event to issue the
// challenge if necessary.
//
context.EndRequest += new
EventHandler(this.IssueAuthenticationChallenge);
}
public void Dispose()
{
//
// Do nothing here
//
}
#endregion

}
}

Appendix B: Web.config for Basic Auth Module

Save this configuration as web.config file in the root of your application:

<configuration>
<system.webServer>
<modules>
<add name=”MyBasicAuthenticationModule” type=”IIS7Demos.BasicAuthenticationModule” />
</modules>
<security>
<authentication>
<windowsAuthentication enabled=”false”/>
<anonymousAuthentication enabled=”false”/>
</authentication>
</security>
</system.webServer>
</configuration>

Appendix C: Configuring Membership

The ASP.NET 2.0 Membership service enables applications to quickly implement credential validation and user management required by most authentication and access control schemes. Membership isolates the application code from the actual credential store implementation, and provides a number of options for integrating with existing credential stores.

To take advantage of Membership for this module sample, uncomment a call to Membership.ValidateUser inside the ValidateCredentials method, and configure a Membership provider for your application. You can learn more about configuring Membership in this MSDN article.

The Official Microsoft IIS Site

Este artigo demonstra de maneira simples e rápida como enviar uma mensagem usando o CDOSYS, modificando o host para envio de e-mail, o remetente, o destinatário e por fim o texto no corpo do e-mail….

Observações:

mail.exemplo.com = Servidor smtp que será usado para envio da mensagem

destino@exemplo.com = Endereço de e-mail que será alcançado pela mensagem

origem@exemplo.com = Endereço de e-mail autorizado pelo servidor SMTP para envio deste mensagem

Subject = Título do E-mail

HTMLBody= Texto que vai no corpo do e-mail

‘—

‘Cria Objetos
Dim objMessage, objConfig
Set objMessage = Server.createObject(“CDO.Message”)
Set objConfig = Server.createObject(“CDO.Configuration”)

‘Cria Configuração
with objConfig.Fields
.Item(“http://schemas.microsoft.com/cdo/configuration/sendusing”) = 2
.Item(“http://schemas.microsoft.com/cdo/configuration/smtpserver”) = “mail.exemplo.com”
.Item(“http://schemas.microsoft.com/cdo/configuration/smtpconnectiontimeout”) = 10
.Update()
End with

‘Envia E-mail
with objMessage
.Configuration = objConfig
.to = “destino@exemplo.com”
.From = “origem@exemplo.com”
.Subject = “E-mail de teste”
.HTMLBody = “E-mail de teste com CDOSYS”
.Send()
End with

‘Destroi objetos
Set objMessage = Nothing
Set objConfig = Nothing

[]´s

RolfBoard

Erro:

Unable to bind to the underlying transport for x.x.x.x. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.

Este erro ocorre normalmente quando uma interface, ou o ip do server em questão foi alterado, prejudicando o controle do bind que gravou em registro este dado e não conseguiu dinâmicamente alterar. Este erro também é comum em casos de 2 aplicações que tentam fazer bind no mesmo serviço, exemplo um Apache com um IIS na mesma máquina.. veja isso é um exemplo…

Para que volte ao normal é necessário forçar o bind usando o httpcfg, uma ferramenta de edição do http.sys, que controla a lista de ip´s permitidos no bind.

• Primeiro execute a remoção do ip ou dos ip´s antigos da máquina com o seguinte comando:

httpcfg delete iplisten -i x.x.x.x, onde “x” é o endereço antigo

• Depois adicione o endereço “0.0.0.0″, significando de qualquer origem para qualquer destino

httpcfg set iplisten -i 0.0.0.0

Após este procedimento, execute os seguintes comandos:

net stop http

net start http

iisreset

Verifique se a porta desejada subiu corretamente através do comando:

netstat -na | findstr 80

[]´s

Rodolfo

]]> http://kiranpatils.wordpress.com/2008/09/29/hosting-a-wcf-service-in-iis-70/ Mon, 29 Sep 2008 06:46:53 +0000 kiranpatils http://kiranpatils.wordpress.com/2008/09/29/hosting-a-wcf-service-in-iis-70/

If you would like to deploy your WCF Service within following environment:

1. Windows Server 2008
2. IIS 7.0

Or facing following Error:

Server Error in Application “DEFAULT WEB SITE/ EmployeeService “Internet Information Services 7.0

Error Summary

HTTP Error 404.3 – Not Found

The page you are requesting cannot be served because of the extension configuration. If the page is a script, add a handler. If the file should be downloaded, add a MIME map. Detailed Error InformationModule StaticFileModule

Notification ExecuteRequestHandler

Handler StaticFile

Error Code 0×80070032

Requested URL http://localhost:80/EmployeeService/ EmployeeService.svc

Physical Path

C:\inetpub\wwwroot\Pepperio.Net.Services\/EmployeeService \EmployeeService.svc

Logon Method Anonymous

Logon User Anonymous

Most likely causes:

It is possible that a handler mapping is missing. By default, the static file handler processes all content.

The feature you are trying to use may not be installed.

The appropriate MIME map is not enabled for the Web site or application. (Warning: Do not create a MIME map for content that users should not download, such as .ASPX pages or .config files.)

If ASP.NET is not installed.

Things you can try:

In system.webServer/handlers:

Ensure that the expected handler for the current page is mapped.

Pay extra attention to preconditions (for example, runtimeVersion, pipelineMode, bitness) and compare them to the settings for your application pool.

Pay extra attention to typographical errors in the expected handler line.

Please verify that the feature you are trying to use is installed.

Verify that the MIME map is enabled or add the MIME map for the Web site using the command-line tool appcmd.exe.

To set a MIME type, use the following syntax: %SystemRoot%\windows\system32\inetsrv\appcmd set config /section:staticContent /+[fileExtension='string',mimeType='string']

The variable fileExtension string is the file name extension and the variable mimeType string is the file type description.

For example, to add a MIME map for a file which has the extension “.xyz”: appcmd set config /section:staticContent /+[fileExtension='.xyz',mimeType='text/plain']

Warning: Ensure that this MIME mapping is needed for your Web server before adding it to the list. Configuration files such as .CONFIG or dynamic scripting pages such as .ASP or .ASPX, should not be downloaded directly and should always be processed through a handler. Other files such as database files or those used to store configuration, like .XML or .MDF, are sometimes used to store configuration information. Determine if clients can download these file types before enabling them.

Install ASP.NET.

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.

And looking some work around for it then this article for you…..go ahead…

For deploying WCF you need to do one way from the following one:

1. You have to run servicemodelreg -i as an administrator using VS 2008 Command prompt (you can find it in <WINDOWSDRIVE>:\Windows\WinFx\v3.0\Windows Communication Foundation).

Credit goes to: http://www.u2u.info/Blogs/Peter/Lists/Posts/Post.aspx?ID=151

2. If you want to do it from scratch…just follow this article:

http://blah.winsmarts.com/2008-4-Host_a_WCF_Service_in_IIS_7_-and-amp;_Windows_2008_-_The_right_way.aspx

That’s it…

Let me know if you face some problem…may be i can help..

-Kiran

Update: This application will help you track down which applications are using which ports on Windows – very helpful for debugging if the steps below don’t solve your problem, or if IIS is not the only application answering on port 80: http://winnetstat.zapto.org/

Also, if you don’t specifically need all the features of XAMPP, but would like to run PHP/MySQL applications through IIS, give Web Platform Installer a try. Through WPI, you can choose to install PHP directly within IIS (so that IIS can serve both ASP.NET and PHP applications on port 80, for example) and you can also have a ton of applications installed and configured automatically for you, such as Drupal, WordPress, and Moodle (among many others). However, if you are still looking to run XAMPP specifically, or just run an Apache instance along with IIS, check out the instructions below. Thanks for visiting!

Original Post:

Found out the hard way that the default XAMPP install for Windows will attempt to install Apache as a service configured to run on Port 80 (no surprise, and probably good default behavior). But, if you’re like me, and have IIS already installed and running, for whatever reason, you’ll probably want to configure XAMPP to run Apache on a different port.

I initially tried merely modifying the httpd.conf file located (on my system) at C:\xampp\apache\conf, but the service would still not run. So, through a bit of searching on the interwebs, I found out what exactly needs to be changed to allow XAMPP to co-exist with IIS configured to run on Port 80, and Apache (in my case) to run on Port 8080 (and SSL running on Port 4499):

C:\xampp\apache\conf\httpd.conf:

• Search for “Listen 80″, change to “Listen 8080″
• Search for “ServerName localhost:80″, change to “ServerName localhost:8080″

C:\xampp\apache\conf\extra\httpd-ssl.conf

• Search for “Listen 443″, change to “Listen 4499″
• Search for “<VirtualHost _default_:443>”, change to “<VirtualHost _default_:4499>”
• Search for “ServerName localhost:443″, change to “ServerName localhost:4499″

Then, you should be able to start Apache successfully through the XAMPP control panel.

Let me know if this works for you; I’m just starting to mess with XAMPP on Windows (I’ve been using it on Linux for a while).

Performance

A good metric listed below is the “efficiency” or “cost” of the number of requests per CPU cycle (RPS / CPU Utilization %).  Using this metric, IIS 7.0/W2K8 RTM is over 10% more efficient then IIS 6.0/WS03 SP2in handling live web platform traffic for the site

Listed below the graphical data results is the methodology used in this performance analysis.

Server Efficiency (RPS/ CPU %) – Efficiency of serving live web platform traffic

W2K3 SP2     4.36   “requests per CPU cycle”

W2K8 RTM   4.84   ~ 10.9% increased efficiency

CPU Utilization (%)

W2K3 SP2     44.8%

W2K8 RTM   52.8%   ~ 17.9% degradation (This is impacted by the increased RPS the W2K8 servers are handling)

Web Service – Total Methods Requests/Sec (RPS)

W2K3 SP2     194

W2K8 RTM    255   ~ 31.4% more traffic is being sent to the W2K8 RTM servers

Web Service – Current Connections

W2K3 SP2     280

W2K8 RTM   294   ~ 5% increase

 Load Balancing – Current Client Connections

W2K3 SP2     116

W2K8 RTM   116   Equal – as the hardware load balancer maintains the same amount of outstanding open client connections.

.NET CLR Memory – % Time in GC

W2K3 SP2    1.1%

W2K8 RTM   2.5%  No significant degradation in “Time in GC”

Performance Overview and methodology:

Site: www.microsoft.com 

During this assessment the live www.microsoft.com site was comprised on 80 servers.  There were four load balanced clusters of twenty servers each, located in multiple datacenters.  This performance analysis was developed by using a single twenty server cluster on the www.microsoft.com site.  The cluster is comprised of 19 Windows Server 2008 RTM servers (W2K8 RTM) and a single Windows Server 2003 SP2 (W2K3 SP2) server all taking live internet facing traffic.  This Lone Windows Server 2003 has become quite famous.  In fact, he actually has his own blog located at http://blogs.technet.com/windowsserver/pages/about-lone-server.aspx

Hardware:

  Model: HP DL585 G1 (4 dual-core CPUs)

  RAM: 32GB 

AppPool Mode’s in IIS 7.0

·         Integrated mode[ASp.NET]

·         Classic .NET AppPool

In Previous versions of IIS, the Session of ASP wasnt accessible to ASP.nET. the reason behind in IIS 6 there were two different ISAP dlls[aspnet_ISAPI.dll and asp.dll] for ASP and ASP.NET so they couldnt share the Session and Application objects

Solution : was we can force the asp extension to use ASP.NET handler in IIS 6.0

This is default feature in  IIS 7.0, which is known as Integrated mode

Migrating the Application Configuration
If you simply move the application to IIS7.0 server. it runs this below command.

if you want to disable and not have to run the application
add this to application web.config file
<system.webServer>
<validation validateIntegratedModeConfiguration=”false” />   
</system.webServer

Command to run the ASP.NET application under IIS 7.0 Integration mode

%windir%\system32\inetsrv\APPCMD.EXE migrate config <Application Path>

Where <Application Path> is the virtual path of the application containing the site name, such as “Default Web Site/app1″.

Moving Back to Classic ASP.NET integration Mode

configure your application pool to run under Classic mode

Selecting ASP.NET Version for an Application

ASP.NET v1.1 application on /app1:
ASP.NET v2.0 application on /app2:’

Unfortunately, due to the limitation of the ability to load only one CLR version into a single worker process

Taking Advantage of Integrated ASP.NET Mode
Your ASP.NET application should be using those components which make use of this feature.

Ai seguenti link si possono iniziare a intravedere le nuove potenzialità del nuovo application server della Microsoft, per ora mi  segno solo l’Application Request Routing e L’Url Rewriting.

Download de software hier:  inetmgr

Supported Operating Systems: Windows Server 2003 Service Pack 1; Windows Vista Service Pack 1; Windows XP Service Pack 2

• You must have the Microsoft .NET Framework version 2.0 or greater installed.
• If you are installing on Windows Vista:
  You must have Windows Vista Service Pack 1 beta installed
  You must have the Internet Information Services 7.0 Management Console installed.
• If you are installing on Windows XP:
  You must have Windows XP Service Pack 2 installed
  If you are installing on Windows Server 2003:
  You must have Windows Server 2003 Service Pack 1 installed

Zodra je de software hebt gedownload en je PC voldoet aan de bovenstaande voorwaarden, kun je de IIS 7.0 manager installeren.

Daarna hoef je alleen nog maar verbinding te maken met de iis server, site of application.

Microsoft has created a new FTP service that has been completely rewritten for Windows Server 2008. This new FTP service incorporates many new features that enable web authors to publish content better than before, and offers web administrators more security and deployment options. This new FTP service supports a wide range of features and improvements, and the following list contains several of the improvements in this version:

• Integration with IIS 7.0: IIS 7.0 has a brand-new administration interface and configuration store, and the new FTP service is tightly integrated with this new design. The old IIS 6 metabase is gone, and a new configuration store that is based on the .NET XML-based *.config format has taken its place. In addition, IIS 7.0 has a new administration tool, and the new FTP server plugs seamlessly into that paradigm.
• Support for new Internet standards: One of the most significant features in the new FTP server is support for FTP over SSL. The new FTP server also supports other Internet improvements such as UTF8, IPv6, and adaptive networking bandwidth usage.
• Shared hosting improvements: By fully integrating into IIS 7.0, the new FTP server makes it possible to host FTP and Web content from the same site by simply adding an FTP binding to an existing Web site. In addition, the FTP server now has virtual host name support, making it possible to host multiple FTP sites on the same IP address. The new FTP server also has improved user isolation, now making it possible to isolate users through per-user virtual directories.
• Extensibility and custom authentication: The new FTP server supports developer extensibility, making it possible for software vendors to write custom providers for FTP authentication. Microsoft is using this extensibility feature to implement two new methods for using non-Windows accounts for FTP authentication for IIS Managers and .NET Membership.
• Improved logging support: FTP logging has been enhanced to include all FTP-related traffic, unique tracking for FTP sessions, FTP sub-statuses, additional detail fields in FTP logs, and much more.
• New supportability features: IIS 7.0 has a new option to display detailed error messages for local users, and the FTP server supports this by providing detailed error responses when logging on locally to an FTP server. The FTP server also logs detailed information using Event Tracing for Windows (ETW), which provides additional detailed information for troubleshooting.

Download hier de FTP Service for IIS 7.0:

• 32 Bit: ftp7_x86_rtw.msi
• 64 Bit: ftp7_x64_rtw.msi

Zodra de software binnen is, kan er worden begonnen met de installatie. Dit is gewoon recht toe recht aan “next, next en finish”.

Hier kun je nog wat features kiezen.

Mocht je de “oude” FTP server al geïnstalleerd hebben staan dan moet je deze verwijderen. Wat ik wel jammer vind is dat hij dit pas aan het einde van de wizard aangeeft.

Open de ServerManager en klik op Roles. Scroll naar de IIS role en klik op Remove Role Services.

Haal het vinkje weg bij FTP Publishing Service.

Even opnieuw opstarten en je kunt de installatie wizard opnieuw starten.

Nadat de wizard klaar is kun je deze sluiten.

Als je vervolgens de Servermanager start en naar de IIS tab gaat, zie je dat er een aantal nieuwe mogelijkheden zijn.

Jammer dat de FTP Service voor IIS 7.0 niet in de final release van Windows Server 2008 is verwerkt.

Erros encontrados no Log de eventos para este problema:

Event Type: Message
Event Source: Active Server Pages
Event Category: None
Event ID: 5
Date: Date
Time: Time
User: N/A
Computer: Computer_Name
Description:
Error: The Template Persistent Cache initialization failed for Application Pool ‘Application_Pool_Name’ because of the following error: Could not create a Disk Cache Sub-directory for the Application Pool. The data may have additional error codes

————-

Event Type: Warning
Event Source: W3SVC
Event Category: None
Event ID: 1009
Date: Date
Time: Time
User: N/A
Computer: Computer_Name
Description:
A process serving application pool ‘Application_Pool_Name’ terminated unexpectedly. The process id was ‘5288′. The process exit code was ‘0xffffffff’

——————

Estes erros ocorrem normalmente quando um membro de domínio é promovido para controlador de domínio, durante o processo de instalação as permissões do %systemroot% são reiniciadas e reordenadas .

Para contornar este problema será necessário setar manualmente as permissões dos seguintes diretórios:

• systemroot\Help\IISHelp\Common
• systemroot\System32\Inetsrv\ASP Compiled Templates
• systemroot\IIS Temporary Compressed Files

Da seguinte forma:

%systemroot%\Help\IISHelp

Para este diretório adicione o grupo IIS_WPG, e coloque as seguintes permissões:

- Read and Execute
- List Folder Contents
- Read

%systemroot%\system32\inetsrv

Para este diretório adicione o grupo IIS_WPG, e coloque a seguinte permissão:

- Full Control

%systemroot%

Para este diretório adicione o grupo IIS_WPG, e coloque a seguinte permissão:

- Full Control

%systemroot%\Help\iishelp

Para este diretório adicione o grupo IIS_WPG, e coloque as seguintes permissões:

- Read and Execute
- List Folder Contents
- Read

obs.: Procure evitar a replicação de objetos (herança) durante o processo de configuração a não ser que você tenha certeza do que está fazendo, se não todo o trabalho acima será em vão e outros problemas surgirão em seu Server.

Realizado todos estes passos, realize um restart do seu webserver e verifique nos logs, após navegação do conteúdo, se o problema persiste.

Segue link com um artigo da microsoft contendo informações a respeito de um problema similar.

http://support.microsoft.com/kb/332097/

that’s all…

Rodolfo

‘******************************************************************************************************************************
‘*** Script Name: sendmail.vbs
‘*** Criado e Revisado por Rodolfo Angelino Rodrigues
‘*** Data:  08/04/2008
‘******************************************************************************************************************************

Option Explicit
On Error Resume Next

Dim objSendMail, oArgs, ArgNum
Dim strTo, strFrom, strSubject, strBody

Set oArgs = WScript.Arguments
ArgNum = 0

While ArgNum < oArgs.Count
Select Case LCase(oArgs(ArgNum))
Case “-to”,”-t”:
ArgNum = ArgNum + 1
strTo = oArgs(ArgNum)
Case “-from”,”-f”:
ArgNum = ArgNum + 1
strFrom = oArgs(ArgNum)
Case “-subject”,”-s”:
ArgNum = ArgNum + 1
strSubject = oArgs(ArgNum)
Case “-body”,”-b”:
ArgNum = ArgNum + 1
strBody = oArgs(ArgNum)
Case “-help”,”-?”:
Call DisplayUsage
Case Else:
Call DisplayUsage
End Select
ArgNum = ArgNum + 1
Wend

If oArgs.Count=0 Or strTo=”" Or strFrom=”" Or _
strSubject=”" Or strBody=”" Then
Call DisplayUsage
Else
Set objSendMail = CreateObject(“CDONTS.NewMail”)
objSendMail.From = strFrom
objSendMail.To = strTo
objSendMail.Subject = strSubject
objSendMail.Body = strBody
objSendMail.BodyFormat = 0
objSendMail.MailFormat = 0
objSendMail.Send
Set objSendMail = Nothing
End If

‘******************************************************************************************************************************
‘*** Mostra o uso em linha de comando do script
‘******************************************************************************************************************************
Sub DisplayUsage
WScript.Echo “Usage:”
WScript.Echo “  sendmail -t <to address> -f <from address> -s ” & _
Chr(34) & “<subject>” & Chr(34) & ” -b ” & Chr(34) & _
“<message body>” & Chr(34)
WScript.Echo “  sendmail [-help|-?]“
WScript.Echo “”
WSCript.Quit
End Sub
‘******************************************************************************************************************************

WebDav-laajennukset IIS 7.0:n sallivat paremmat julkaisuominaisuudet verkkopalveluille. Nyt julkaistut laajennukset mahdollistavat saittikohtaisen käytön ja hallinnan IIS 7.0 ja Windows Server 2008 alustalla.

Lataa x86-versio: http://www.microsoft.com/downloads/details.aspx?FamilyID=036269fa-0040-4ccd-ad3d-78da1ee132fb&DisplayLang=en

Lataa x64-versio: http://www.microsoft.com/downloads/details.aspx?FamilyID=13e97aaa-fb1b-4cf8-b95f-19ae02321385&DisplayLang=en