Basic Troubleshooting Steps For SharePoint
Here we are explaining troubleshooting steps for Server Side Issues.
- On Production Server, First check your SharePoint Admin or SharePoint Time job is running properly or not?
- Check your web application site in IIS is in start mode or not? Please start your web application
- Check your Application Pool of your web application in IIS/Web server are stopped or not? please start your application pool.
- Please check your authentication is windows authentication or not?
- Please check your local group policy for FIPS Issue. FIPS is not supported by SharePoint-2010.
Other Important Tasks
1- By Default SharePoint-2010 does not support TLS1.0/TLS1.2.
2- List view Threshold is 5000 in SharePoint-2010 to support best SharePoint Performance.
3- To Block file like .aspx, .png, .xml etc on web application level, Configure "Block File Type " in CA- Central Administrator for SharePoint WebApplication.
4- LookUp column is used to interconnect two lists.
5- External Column is used to to work with External data from external server by BCS.
6- Metadata service application is a prerequisite for Search Service and User profile Service for
all SharePoint versions.
all SharePoint versions.
7- To work with InfoPath form, Please configure InfoPath form service in General App Setting section of Central Administrator.
Let's take a example '503 service unreachable', then what will be our approach to resolve this problem.
Let's take a example '503 service unreachable', then what will be our approach to resolve this problem.
5xx code means this is server side issue at IIS level.
Without any delay, Open the IIS by using short key 'inetmgr'. Verify that Application Pool is running or stopped. if application pool is stopped, immediately start it. Check your URL again. It should be resolved but some time that is also can not help to resolve this issue.
In this case, We have to login our Application pool with same user id and password on which this Application pool was running previously. After login the application pool, restart the application pool one more time. verify the Application URL. This time, application will work.
Let's take a another example 'this site is unreachable'. this is very common error. some time it is due to bad network connectivity. there is a technical reason that is 'some time, site is stopped in IIS due to any reason in this case error message is same'.
So need to start the site in IIS. this problem will be resolved.
Comments
Post a Comment