Wednesday, July 9, 2014

File is locked for editing by ‘domain\username' when editing office document in SharePoint site



File is locked for editing by ‘domain\username' when editing office document in SharePoint site.

                      

Issue: Sometimes, when we try to edit a document uploaded on SharePoint, we get a file locked error: “File is locked for editing by ‘domain\username’ “, even though the file has been checked in and no one else is editing the file 

Cause: Usually a file is locked by WSS when a particular user has ‘checked out’ the file for editing purposes. A write lock is created so that no other user can edit this file simultaneously. There can be numerous reasons for this such as. below are the some of the reasons.
1.    System crashes while the file is still open.

2.    File has been closed unexpectedly.

3.    Check in was not successful.

4.    Network connection is lost while file is still open.

Ensure to check the below to resolve the issue.

1.    Check whether the file has been properly checked in or not. If not, refresh the page and try to check in the file again.

2.    Delete the local copy of the file present in the cache folder of the concerned user account (access to user’s PC required).

3.    Close all the instances of file type opened in the system. E.g. if the file type is excel, then close all the excel files currently opened.

4.    Also kill the file type service (excel in this case) using the task manager.

Solution: Please follow the below mentioned resolutions if issue still exists.

1.    Download  the wsp from the below mentioned site.
                                 https://spunlockfiles.codeplex.com/
2.    Upload it to the site collection solution gallery
3.    Activate the solution from solution gallery
4.    Activate the solution at the site collection level
5.    Add the web part named as “spfileunlock” to any page and Try to check the issue again.

Please Comment if you need Any Help.Your Feed back is always Welcome.I Am Happy to Help !!!!!

Tuesday, July 8, 2014

Web Applications using Claims authentication require an update


Web Applications using Claims authentication require an update

                   

Issue: Web Applications using Claims authentication require an update

Source of Error: This error began appearing in the Health Analyzer after creating a web application using Claims Authentication.

Cause:This can happen when you deploy a Microsoft ASP.NET 2.0-based Web application to a Web site that is hosted on a server running SharePoint 2013 and you have Internet Information Services (IIS) 7.0 or IIS 7.5 running in Integrated mode on the server
 

Resolution: Ensure to follow the below to resolve the error.

1.   Download the Windows6.1-KB979917-x64.msu (Win7) update (for Windows Server 2008 R2).
2.   Copy the setup to all your SharePoint servers -> Install it one by one.
3.   Once the install is finished then please restart all the servers.
4.   Once all the servers are up and running
5.   Click 'Reanalyze Now by means of health analyzer list
6.   Check the  error shouldn't be there in the list!


MS LINK

download the update,

Please Comment if you need Any Help.Your Feed back is always Welcome.I Am Happy to Help !!!!!

The data source no longer exists or you do not have permissions to view it. Additional details have been logged for your administrator



The data source no longer exists or you do not have permissions to view it. Additional details have been logged for your administrator

Issue: While using Performance Point’s Dashboard Designer, I received the following error. The data source no longer exists or you do not have permissions to view it. Additional details have been logged for your administrator.

Exception Details: The data source no longer exists or you do not have permissions to view it. Additional details have been logged for your administrator.
Inner Exception Message:
Stack Trace: at Zicrosoft.PerformancePoint.Scorecards.Server.PmServer.ExecuteAnalyticReportWithParameters(RepositoryLocation analyticReportViewLocation, BIDataContainer biDataContainer)
at Microsoft.PerformancePoint.Analytics.ServerRendering.OLAPBase.OlapViewBaseControl.ExtractReportViewData()
at Microsoft.PerformancePoint.Analytics.ServerRendering.OLAPBase.OlapViewBaseControl.CreateRenderedView(StringBuilder sd)
at Microsoft.PerformancePoint.Scorecards.ServerRendering.NavigableControl.RenderControl(HtmlTextWriter writer)

Performance Point Services error code 20604.

Cause: The performance point is not working as expected is of many reasons.

Solutions: Ensure to check the below to work the PP service as expected.

1.   Performance Point doesn't support claims-based authentication.

2.   Make sure the account you use to logon the server has proper permissions to the data connection list since when SharePoint open dashboard designer from client side, it use the current account of the server not the current account of the SharePoint site.

3.   Ensure  the web app pool identity have permissions to connect to performance point service application.

4.   Ensure to configure the unattended service account


6.   The service account that runs the IIS app pools had to be added as a reader in the BI Center.
 

 

Please Comment if you need Any Help.Your Feed back is always Welcome.I Am Happy to Help !!!!!

ShareThis

X