Hi All,

I have the following case:

1- Production environment (SharePoint 2010, Office 2013, Firefox 33.0.2):

A- user can choose a document link

B- the browser will show a pop-up window to ask to either check-out or open document as read-only

C- In case of check-out user is able to edit the document and save it to the document library

2- Testing environment  (SharePoint 2010, Office 2013, Firefox 33.0.2) [same user, same client machine and browser]:

A- user can choose a document link

B- the browser (again same browser and same machine) downloads the document localy

C- user can only edit the document locally (no connection to document library)

I read about some solutions related to downloading IE tab but my case is different as I can successfully check-out and edit a document from one SharePoint document library and fail in the other from the same client/browser.

Kindly provide your support as I suspect that there is an update that is causing this (never had this problem while testing the previous release which was one month ago).

Note: both environments have the same settings under( Document Library Settings -> Advanced Settings and ->Versioning Settings)

Many thanks,

AFESD

Check IE internet options

• Go: Tools > Internet Options > Security Tab > Click Sites button > Advanced > verify that development farm URL or at least its domain is there. For example: "http:/*.domain.com".  Note: I left out one forward slash intentionally - so that this isn't rendered as a URL.

Check Web Application Browser File Handling

1. Log into CA
2. Go: CA > Application Management > Manage Web Applications > Select web application > General Settings > Browser File Handling
3. Compare this setting between production and development farms.
4. Verify they are the same: configured as Permissive.

Check User Permissions

• A user having only Read permission to the document library will be able to edit the document locally only without being able to save it back to the SharePoint document library.
• Verify that user permissions are consistent between the production and development farms: both enable the user Read/Write (AKA Contribute).

References

• SharePoint: Browser File Handling Deep Dive

Thanks for the reply but unfortunately the problem still exists.

- Check Web Application Browser File Handling: Both production and development sites were already added, I removed the development site and added it again. Opened a new browser instant, tried, No change. (Note: I could not repeat the same point on FireFox as I could not find an equivalent settings).

- Check Web Application Browser File Handling: both sites were set to Strict, I changed both to Permissive after reading documentation. Opened a new browser instant, tried, No change.

- Check User Permissions: I am using sp administrator user in both cases, but still checked document library permissions and made sure both are having Full Control.

Any other ideas?

Thanks again.

• IE: flush cache; CTRL+F5
• Try remoting directly to the machine hosting a dev farm server and then repeating testing.
• SP farm administrators are not automatically able to login to site collections - verify that your sp admin account has been added to the target site collection's administrators group.
• Also: repeat testing using standard user account configured with identical permissions on both farms.

Begin to bound the problem scope:

• IE: flush cache; CTRL+F5
• Try remoting directly to the machine hosting a dev farm server and then repeating testing.
• SP farm administrators are not automatically able to login to site collections - verify that your sp admin account has been added to the target site collection's administrators group.
• Also: repeat testing using standard user account configured with identical permissions on both farms.

• Edited by Stephan Bren 15 hours 24 minutes ago

I really tried everything possible!
I flushed the cash on both user machine and remote development server before repeating the test.
I used normal users with appropriate rights and made sure that sp admin user has the needed right and repeated the test on both user machine and remote development server.
Still unlucky!

Is it possible that a latest update can be the reason for this?