14 October, 2013

Edit Document requires a Windows SharePoint Services-compatible application




Edit Document requires a Windows SharePoint Services-compatible application and Microsoft Internet Explorer 6.0 or greater

This error can be occurred from many reason, here are some of these:
You connect to a Microsoft Windows SharePoint Services website.
You view a document library.
You try to edit a Microsoft Office document that is stored in the document library.

I have resolved this issue and tested under multiple versions i.e. office 2003, office 2007, office 2010 and office 2013

For office 2003 and office 2007 [same resolution]:
1)   Click Start, and then click Control Panel.
2)   Click Add or Remove Programs.
3)   In the list of installed programs, click Microsoft Office 2003 or Microsoft Office 2007, and then click Change.
4)   Click Reinstall or Repair.
5)   Click OK.

For office 2010:
1)   Click Start
2)   Control Panel
3)   Programs
4)   Programs and Features
5)   Click the Office program you want to repair, and then click Change.
6)   In Office 2010
7)   Click Repair
8)   Continue.

For office 2013:
1)   Click Start
2)   Control Panel
3)   Programs
4)   Programs and Features
5)   Click the Office program you want to repair, and then click Change.
6)   In Office 2013
7)   click either Quick Repair or Online Repair

If you have any queries/questions regarding the above mentioned information then please let me know. I would be more than happy to help you as well as resolves your issues, Thank you.

Recommended guidelines for lists and libraries


Limit
Maximum value
Limit type

List row size
8,000 bytes per row
Boundary

File size
2 GB
Boundary

Documents
30,000,000 per library
Supported

Major versions
400,000
Supported

Minor versions
511
Boundary

Items
30,000,000 per list
Supported

Rows size limit
6 table rows internal to the database used for a list or library item
Supported

Bulk operations
100 items per bulk operation
Boundary

List view lookup threshold
8 join operations per query
Threshold

List view threshold
5,000
Threshold

List view threshold for auditors and administrators
20,000
Threshold

Subsite
2,000 per site view
Threshold

Coauthoring in Word and PowerPoint for .docx, .pptx and .ppsx files
10 concurrent editors per document
Threshold





Security scope
50,000 per list
Threshold


12 October, 2013

Cannot logon with credentials obtained from Secure Store Provider

Problem Description:
I'm using SPD 2010 to connect to an external SQL database hosted on a different server. External data source type selection is SQL Server. I then filled up the connection properties, choose "Connect with Impersonated Windows Identity" and Secure Store Application Id. But SPD 2010 returns this error: Cannot logon with credentials obtained from Secure Store Provider

Error message:
Cannot logon with credentials obtained from Secure Store Provider

We need to set up your Secure Store service application on the server, and add a Target Application. This is an arbitrary name you assign to the set of credential mappings that you will set up in the Secure Store but getting the same error.

Troubleshooting done:
1)   I made sure that the credentials that i set in the secure store have at least db_reader access to the database.

2)   Also ensured the user making the request is a part of members group for the target application.

3)   Chekced the ULS logs and did not find anything relevant.

4)   Suspecting that there is some sort of firewall or VPN issue but, I am not sure how to proceed?

5)   Tried with different account rather than system account to ensure it reflects the same set of results.

6)   Referred the following articles again n again to make sure everything set up correctly but did not yield any results!


Thanks to Fabian Williams and Marc Anderson for the valuable articles:

http://fabiangwilliams.wordpress.com/2010/04/16/how-to-create-configure-consume-sharepoint-2010-secure-store-in-business-connectivity-services

What Resolution we have applied:-
We have created a SQL Account with SQL authentication +
Connect with impersonated custom identity and the issue has been resolved. See this useful post SharePoint 2010 using BCS with SQL Server database by Arjan Fraaij.

Reference:

Product applies to:
SharePoint Server 2010