FIXING THE “HTTP ERROR 401.3 – UNAUTHORIZED” ISSUE IN IIS

I'm trying to test my ASP.Net website on localhost and I'm getting this error:




IIS 7 also creates "IUSR" as default user to access files via IIS. So make user IUSR has read access to files/folders.

How to check if IUSR has read Access? Right Click -> Folder -> Properties -> Security Tab See if IUSR is in Group or user names list, If No.

Click Edit -> Add -> Advanced -> Find Now -> Select IUSR and click OK four times

Download .apk and ipa files from Asp.net website via Email

Here in this article i let you know how to Download .apk and ipa files from Asp.net website (WebApplication) via email.

Step 1: 

In .aspx Add the MailBodyContent below hyperlink. This link located as .apk path

Step 2 :

In web.config add below code with in 

User Profile Synchronization Service Stuck at "Starting" - Solution

While configuring User Profile Synchronization in SharePoint 2010, User Profile Synchronization service got stuck at "Starting" state. User profile synchronization service was in starting state for long time! I've been banging my head for couple of Hours.

.

After a while, tried running the FIM client from: C:\Program Files\Microsoft Office Servers\14.0\Synchronization Service\UIShell\miisclient.exe , FIM gave an Error Message: Unable to connect to the synchronization Service. found the root cause of the issue! 

Solution was: The account I currently logged-in is a Local Administrator account, but not SharePoint Farm Admin! Logged off and logged in with Farm Admin account. Tried stopping the service which was in "Starting" state.

How to stop the User Profile Synchronization service which got stuck at "Starting" state?

In some cases,  user profile synchronization service may started and then stopped. But here, user profile synchronization service hangs! Lets seek help from our friend: PowerShell!  Get the User profile Synchronization service's GUID and pass it to Stop-SPServiceInstace cmdlet.

Get-SPServiceInstance > Services.txt

This will get all the services along with their GUID to a text file, say "services.txt". Open the file and get the GUID of  User profile Synchronization service which will be in Provisioning state.

Once you get the GUID, execute: Stop-SPServiceInstance and provide the GUID




Restart the Server

worked this time!

In an another case, when we tried re-creating the user profile service application, had the same issue. Fix for this issue was to Remove ForefrontIdentityManager certificates from these 3 locations.
Personal
Trusted Root Certification Authorities
Trusted People
This is because, when I deleted an existing user profile service, it didn't delete the certificates and when recreating it caused the issue!

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!