Error: Access is denied. Verify that either the Default Content Access Account has access to this repository, or add a crawl rule to crawl this repository. If the repository being crawled is a SharePoint repository, verify that the account you are using has "Full Read" permissions on the SharePoint Web Application being crawled.

Error:

Access is denied. Verify that either the Default Content Access Account has access to this repository, or add a crawl rule to crawl this repository. If the repository being crawled is a SharePoint repository, verify that the account you are using has "Full Read" permissions on the SharePoint Web Application being crawled.

Reason:

This error will occur, at the time of crawling the SharePoint application content. because, you may have provided a URL to access the SharePoint web application like http://kmportal.sensoft2000.com (just an example).

When the search engine tried to crawl the content using the kmportal.sensoft2000.com URL, the server will reject the request. because, it will take the request as "LoopBackRequest".

Solution:

So you need to disable the LoopBackRequest in registry. To do this, just follow my instructions:

1. Go to command window and type regedit.exe

2. Once opened the registry editor, just navigate to "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa"

3. Right click on "Lsa" and create a new 32bit DWORD value

4. Rename it as "DisableLoopbackCheck" (Note: you cannot rename it actually. so, once created the DWORD value, directly paste/type as "DisableLoopbackCheck".

5. Then again modify the value of "DisableLoopbackCheck" as "1"
6. Close the registry editor.
7. Now start to crawl the content. 


Thats it...

Issue: Multiple login prompts while browsing a SharePoint application

Issue:

Sometimes, you will be prompted to type the Login credentials to enter into the SharePoint application.

(Amazingly, this will not occur in Firefox)

Reason:

Because, all your browser requests may be processed through the proxy. So the response will be passed through the proxy and the converted HTML output will be displayed in browser. So, the browser will trying to access the SharePoint application's resources (like images, css) directly through the HTTP. By default, nobody can access the SharePoint resources directly in the browser and they can be accessed only if he is the authorized person.

I meant, this kind of access is equivalent to access a image directly from SharePoint image library in browser like, http://sensoft2000-sharepoint.blogspot.com/Images/Logo.jpg (Just an example).

Solution:

You have to add the URL in trusted sites zone of the IE and the URL should be added in exception list. 


Just follow the below mentioned steps to fix this issue.

• Open the IE browser
• Go to Tools and click internet options
• Then Click "Security" tab
• Select "Trusted Sites"
• Click "Sites" button
• Type your URL in the text box and click "Add" button.
• Click "Close" button
• Click "Apply" button
• Go to "Connections" tab
• Click "LAN Settings" button
• Here your "Proxy Server" check box may be checked already.If not, Select it
• Click "Advanced" button
• Now, you will see a Text area in the "Exceptions" panel.
• Here you have to add your URL. for example, if your URL is like http://moss.sensoft2000.com (example), then you need to add the URL as mentioned in the below screenshot *.sensoft2000.com. 

Thats it...

Error: Cannot navigate to the requested page while User Profile Synchronization is running. Please wait for the current Synchronization run to finish.

Error:

Cannot navigate to the requested page while User Profile Synchronization is running. Please wait for the current Synchronization run to finish.

Reason:

You will get this error, in case if you are trying to "Import the User profiles" in SharePoint 2010. Sometimes, "The user profile sync" job may not be running or it may be in "Starting" stage for a long time. 

You can check this status in central admin as I said below. 

• In central admin, go to "Monitoring" link 
• Then go to "Review Job definitions"  under "Timer Jobs"
• Then click the "Running Jobs" link in left hand side.

Here you can see that the sync job will be running continuously. Reason is the required services may not be ready after the SharePoint 2010 installation.

So, what to do?

Solution:

Solution is very simple. Just login into the SharePoint server and go to the command prompt with administrator privileges (right click on the "Command Prompt" icon and select the 'Run as Administrator' option).

Then,  just type "IISReset" to reset the IIS.

Now you can come and check the Running Jobs link as I mentioned above. 

Thats it...

Error: The context has expired and can no longer be used. (Exception from HRESULT: 0x80090317)

Error:


The context has expired and can no longer be used. (Exception from HRESULT: 0x80090317) 


Reason:
1. Security context of your session may be expired.
2. You/somebody may have changed the date/time in the server.


Solution:
1. Just change/update the Date/Time in the SharePoint server.
2. Increase the Security context in SharePoint central admin. This can be done by following the below steps:

• Go to central admin
• Go to  "Application management section"
• Go to "Web Application General Settings"
• Go to "Web page Security validation" section & increase the timeout field. Or, you can simply disable this option.

Thats it...

Error: CREATE TABLE permission denied in database . at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)

Error:
CREATE TABLE permission denied in database . at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)

Reason:

You will get this error, when you are trying to create a new SharePoint web application using the ATTACHED DATABASE through the central admin. Because, your central admin user (that is current user to create a website) may not having a permission to create tables dynamically in the SQL Server. 

Solution:

Solution is very simple. Just attach the database in SQL Server using the current user of the central admin as the owner of the DB. (But it takes long time for me to find out the exact reason).

For example, If your current central admin logged-in username is "domain\senthil" (Assumes, senthil is going to create a new web application) , then you should attach the database using the "domain\senthil" username.

You can change the owner of the database during the "Attach databases" as per the below screenshot.

Thats It...