IIS set the Identity in Application pool

when the config the site into iis its also add the system login and password, otherwise its not connect the database server see the below image

SQL Server 'SA' login error resolve

This is about the sql server 2008 r2 "SA" login error solving as belows

ASP.NET Ajax exception – Two components with the same id can’t be added to the application

There’s a couple of exceptions to look out for when you start developing custom ASP.NET Ajax client controls.  They are:

Microsoft JScript runtime error: Sys.InvalidOperationException: Two components with the same id ‘ctl00_MainContentPlaceHolder__eventsRepeater_ctl01_ke1′ can’t be added to the application.

and…

Microsoft JScript runtime error: Sys.InvalidOperationException: A control is already associated with the element.

These errors can be caused when you have a custom control/component which gets added and then re-added at some later point in time – such as when you have a partial page render.  This is being caused because the Sys.Control or Sys.Component gets registered with the Sys.Application when you call the initialize method of your component like so:

MarkItUp.Web.MyCustomControl.callBaseMethod(this, ‘initialize’) ;

Under the hood, the Sys.Application keeps a list of all the components that are registered with it – that’s how $find works.  So when you call ‘initialize’, Sys.Application looks at the list of components that it currently knows about and if yours already exists then you will likely see one of the errors listed above.

The trick is to make sure that you call dispose on your control’s base when you are finished:

dispose : function() { 

    $clearHandlers(this.get_element()) ; 

    // any other cleanup work

    MarkItUp.Web.MyCustomControl.callBaseMethod(this, ‘dispose’) ;

}

ASP.NET Ignores IE7 Compatibility Mode Tag in Web.config

 looks at the <system.web> section of Web.config instead of the <system.webServer> section (which is used by IIS7, unless it's running in compatibility mode). To render this meta tag on every page of your site when running IIS6, I believe the best option is to add it to your MasterPage. I ended up adding the following code block to the OnPreRender event of my MasterPage:

Page.Header.Controls.AddAt(0, new HtmlMeta { HttpEquiv = "X-UA-Compatible", Content = "IE=EmulateIE7" });

The reason I used AddAt instead of just plain Add is because the X-UA-Compatible meta tag apparently has to be the first thing in the page header in order for it to be respected.

Hope this helps someone in the same boat!