Please, consider this scenario:
I open file A.pptx and take it in view mode
Click on "Edit in browser" button and file opens in edit mode correctly.
Then, open file B.pptx in view mode.
Click on "Edit in browser" button and OWA opens file A.pptx contents in edit mode but using file B.pptx properties.
I think it's some related with cache but I cannot solve it.
Any help will be appreciated. Thanks.
UPDATE 20151222:
I was able to reproduce this behavior using Excel Web App getting same results.
It seems like it's something related with "SessionID" based on some Event Viewer log entries:
Event Viewer - 1
Here's the code fragment I'm using to generate these IDs:
Code Fragment
Thanks any help.
Related
I tried searching for this question but couldn't really find a similar problem.
I have an excel file in which I created a custom ribbon tab and made copies of this file.
Image of the tab
In some of those copies, the tab has gone missing. I was earlier using Excel 2016 and recently migrated to Microsoft 365 and downloaded the latest version of Office. I am not sure if this is causing the problem since some files do still have the custom ribbon.
Thanks a lot for your help in advance.
Regards
Do you get any UI errors when the tab is missed?
By default, if an add-in attempts to manipulate the Microsoft Office user interface (UI) and fails, no error message is displayed. However, you can configure Microsoft Office applications to display messages for errors that relate to the UI. You can use these messages to help determine why a custom ribbon does not appear, or why a ribbon appears but no controls appear.
To show VSTO Add-in user interface errors you need:
Start the application.
Click the File tab.
Click Options.
In the categories pane, click Advanced.
In the details pane, select Show VSTO Add-in user interface errors, and then click OK.
If you deal with documents with embedded customizations, make sure the protected mode is off when the document is opened. See What is Protected View? for more information.
I am new in using WatiN and couple it with C# for my automation needs. I am faced with a situation here. I need to run an executable from a server location. After having clicked on the download link in the IE, I have a file download pop-up in front of me and a "File Download - Security Warning" on top. The UI presents me with 3 options of Run, Save and Cancel.
I want to click the Run button to run the exe directly (and not hit Save to download it to some location). I have added the dialog handler for my filedownloadhandler to my IE instance. Please find the screen-shot attached
Is there a way in WatiN to accomplish this? Any sample code is highly appreciated.
Thanks.!
Capture Run
Try this
Use your existing dialog handler add and remove but the type of handler you would add would be
WatiN.Core.DialogHandlers.FileDownloadHandler dialogHandler1 = new WatiN.Core.DialogHandlers.FileDownloadHandler(WatiN.Core.DialogHandlers.FileDownloadOptionEnum.Run);
Note that this won't work with IE 9. I have an open post on this (Download Handler for IE9).
Hope this helps.
Cheers.
On my sharepoint site I am unable to add an existing basic webpart to a page where I've added webparts before. I am a site owner. I am using IE 8. I also work remotely using VPN.
The strange thing is IE won't even open up the EDIT MODE.
When I use Google Chrome, it is able to open up EDIT MODE, and it was also able to open up the Add Web Part popup, but when you actually select a web part and press ADD...nothing gets added to the main page.
The extra strange thing is from Google Chrome, I am able to delete and modify existing webparts.
I've upgraded to IE 9 and the same issue still happens.
i assume the similar issue you would be facing with firefox it seems your css is not compliant with IE8 try using ie8 in campatibility mode or use following querystring parameter at end of ur url
toolpaneview=2 and see what is the result
I had that problem and it appeared that a CSS file was messing up with the Ribbon controls.
Try to disable a CSS file at a time.
Regards,
Pedro
We had this issue (or at least a very similar one) where, in edit page mode, clicking on 'Add a Web Part' had no effect. I was assuming that it is a JavaScript issue. In, I beleive, the same day, it effected both my Production and DEV Site Collections, in IE8, Firefox and Chrome. We restarted all of our servers and ran the config wizard. No good.
We were able to create new pages which seem to be uneffected.
For an existing page, our workaround is to edit the properties of the page, then, down at the bottom, select 'Open Page in Maintenance View'. Select one of the Web Parts and Close it. Note: It seems as though if you unselected the 'Allow Close' checkbox, it wont be on this list. Then click on the 'Go Back to Web Part Page'. Click on the zone where the closed Web Part was. You may now be able to 'Add a Web Part'. If so, the last Web Part folder on the left will be 'Closed Web Parts' which I beleive you can put back (Open) the closed Web Part.
I have see this issue occur when someone else has the current page open in edit mode. Until that person either checks in or undoes there checkout you will not be able to edit the page.
I have a very strange issue I just cannot figure out. I am not able to enter Edit Mode on my custom pages. Appending my URL with ?ToolPaneView=2 does nothing. Manipulating the Site Actions button to custom content and changing the MenuItem_EditPage to get the Edit Page button back bring the page into some kind of edit mode with the "Exit Edit Mode" button but still no toolbar or ability to manipulate web parts.
Anyone seen this before?
Thanks
My experience was that the page was created with the SharePoint Server Publishing feature turned on. The site feature was later deactivated and the page could not be edited. Re-activating the feature enabled editing.
I had it once when the page was checked out by the system user.
Discard the current check-out (and lose changes) and I could edit the page again.
So we couldn't open .pdf in the browser in our SP2010 site. I set the setting to permissive browser file handling in central admin. I then found out that there's a bug that if a site is created from a custom template the pdf files uploaded to that site will still prompt for either Save or Cancel. I ran a hotfix on the server
http://support.microsoft.com/kb/2459108
Consider the following scenario:
You set Browser File Handling to Permissive for a web application in the General settings page in SharePoint 2010 Central Administration.
You create a document library, and then upload an html document.
You open the html document in the browser.
Note You are not prompted to download the html document and it is rendered in the browser.
You select to include the content when you save the SharePoint site as a template.
You use the template to create a new SharePoint site in the same web application.
In this scenario, the Browser File Handling list setting for the document library in the new site is set to Strict. Additionally, when you open the html document, you are prompted to download the file.
Now when I click on a pdf with firefox I can open it directly but with internet explorer (8 and 9, default settings) I still can't do it, what's the solution here?
Edit: Maybe it always worked in firefox, anyway, when I create a new library it works as expected. How can I run this setting on all libraries?
There's a different, more subtle, but simpler root cause of this problem.
After much web searching and many hours with MSFT support, as hard as this may be to believe, it turns out that the root cause of my "SharePoint won't open PDF documents" problem was actually an Adobe extension/add-on. The symptom was an Adobe error msg "failed to open" after clicking the PDF list item in a document library. The culprit, an Adobe extension/add-on: "Adobe Acrobat SharePoint OpenDocuments Component".
I do not know how this got installed. What I do (finally) know is that this component actually does the exact opposite of what its name implies, i.e., it apparently prevents PDF documents from opening up when clicked in a SharePoint 2010 document library.
After various failed attempts to solve this problem (including changing "Browser File Handler" settings on the web app server from "Strict" to "Permissive" and other fixes suggested below and elsewhere on various blogs and web sites), nothing fixed the problem until we disabled this Adobe extension/add-on. Then, problem solved.
Note that you may not see this component in the "Tools > Manage Add-Ons" list until after attempting to open a PDF document from the library: apparently the add-on isn't activated (won't appear in that list) until an 'open' attempt is made. SO - if at first you don't see the component listed, try to open a PDF file and check the list again. If this component appears, disable it, and your problem is likely to go away.
Baffling, at best; or worse, actually nefarious on Adobe's part ...?
I'd still like to know how to get the PDF to open in a separate browser tab in IE vs. displacing the active tab. If anyone can help with that, please let me know! No custom coding solutions, PLEASE!
There is a better way to handle "Browser File Handle" issue. Take a look at my blog here: http://www.pdfsharepoint.com/sharepoint-2010-and-pdf-integration-series-part-1/
Solution #2 addresses Pdf extension without exposing entire Web Application to "Permissive" browsing. Setting "Browsing File Handle" to "permissive" opens too many vulnerabilities with other file extensions.
Thanks,
Dmitry
I have the same problem - originally installed Office Web apps, then turned that off, turned on the open in client application, then changed the setting on each doc library to open in browser .. Still have a problem with PDFs though.
If somebody includes a link to them in an announcement, then that person can open, other not. But only in IE - in FF there is no problme
Just change the Browser File Handling for the Web Application from the central admin as:
Central Administration > Application Management > Manage Web Applications
go to your Web Application example "http://sharepoint:80, just select it
from the top ribbon click "General Settings"
go down to "Browser File Handling" and change it to "Permissive"
If am not clear go to http://www.pdfsharepoint.com/sharepoint-2010-and-pdf-integration-series-part-1/
try this:
Make sure you're the site collection admin. Go into the site (not the central admin) and then go to site settings then go to site collection features. In there you will find the setting for " Open Documents in Client Applications by Default " it will probably be deactivated. Active it and you're good to go. users will then open attachments in their windows assigned applications, not the sharepoint web apps.
Also, try going into adobe reader and in the settings there is an option to open with the browser. check or uncheck it based on what you want it to do.
Encryption and SharePoint don't play well together
Right click My Documents or source folder
Select Properties > Advanced (button)
Uncheck "Encrypt contents to secure data"
This should solve many SharePoint problems you might have, including files not opening properly.
Appreciate this is an old post but still very relevant today. I spent a while trying to get this to work - just thought I'd share my findings.
This is specific to Adobe Acrobat. If you use a different PDF viewer, such as SumatraPDF the issue does not occur.
1. To prevent the 'Open, Save, Save As' dialog box in Internet Explorer:
This is specific to the versions of Acrobat. Set the following key/value:
Key: HKLM\SOFTWARE\Policies\Adobe\Acrobat Reader\*acrobat_version_number*\FeatureLockDown\cSharePoint
Value Name: bDisableSharePointFeatures
Value Type: REG_DWORD
Value: 0x1 (hex)
e.g.
For Acrobat X:
HKLM\SOFTWARE\Policies\Adobe\Acrobat Reader\11.0\FeatureLockDown\cSharePoint
2. To disable PDFs opening in the browser
This is specific to the versions of Acrobat. Set the following key/value:
Key: HKCU\Software\Adobe\Acrobat Reader\acrobat_version_number\Originals
Value Name: bBrowserIntegration
Value Type: REG_DWORD
Value: 0x0 (hex)
e.g.
For Acrobat X:
HKCU\Software\Adobe\Acrobat Reader\11.0\Originals
Thanks,
References:
Adobe Acrobat - Lockable Settings
Adobe Acrobat - General Application Settings