I have a SharePoint 2016 installation with Forms Based Authentication installed and an Office Application Server.
When some users try to open PowerPoint presentation (Office 365) in the desktop application (They don't like to edit in the online version) it fails to open saying that they PowerPoint failed to open the document.
typically they would have a pop-up asking if it's okay to open in chrome and then a popup that requires them to log in with forms-based authentication, this means that it's working.
Recently these users stopped getting any popups.
We HAVE set up the trust center to allow forms based log ins from this site.
We HAVE cleared out the cache.
I have also tried giving them a different FBA account.
Has anyone encountered anything like this before?
Related
This error **Add-in Error** We couldn't connect to the 'Office Store' catalog server for this add-in. is shown when user tries to access the add-in.
See image
Steps to reproduce:
Open new excel file
Download the app from app-store.
Also tried removing the add-in and then re-adding it from the store but the same error persists.
Office won't be able to connect to the add-ins catalog unless there's a live internet connection, so when you see this error message, start your browser and make sure you can bring up a page or two that you haven't visited before. Or better yet, try to navigate to the add-in's web page. You can also try using any troubleshooting tools like Fiddler to see what happens under the hood.
This may be for a variety of reasons:
No internet connection
Blocked by firewall
Access disabled by a security policy
Add-in installation disabled by an administrator for Office applications
I installed SharePoint Designer 2013 and opened a site from our company's Office 365 SharePoint Online. When I try to make any changes in seattle.master (or any other html file) and save, it is showing following error message:
Server error: Access denied.
I setup my own user with full control (owner), so it seems to have enough rights.
Am I missing something?
Try enabling custom script on the site where you are trying to save the file.
You can do this using SPO Shell
Set-SPOSite https://contoso.sharepoint.com -DenyAddAndCustomizePages 0
Had this issue a couple days ago and this seemed to fix it.
I've got a mysterious edge case with some Word 2016 users on Windows using my Word add-in.
I realize much more info might be required...but I also feel this is an issue that might have some proven ways to diagnose - or someone may know of a root cause.
My simple Word add-in pulls data from a MySQL db on my web server (via php) and stores it in localstorage. Works great in Word 2016 on multiple computers. A handful of users can't, essentially, download data and my solution throws errors for them.
I've even had 2 users on the same machine - one who can use my add-in, one who cannot (so each logging into different Windows accounts at the same institution. The user who was able to happily use my app is in IT and maybe had different settings).
My nose tells me there is an Internet Explorer security setting getting in the way...we've verified that localstorage is allowed.
When a user with the problem opens Internet Explorer directly, they're able to download data and use the app (part of it works outside of Word). As I understand it, Word 2016 Add-ins use Internet Explorer 11 to render html/js/css - and a setting changed in a user's IE11 settings area will cascade to Word 2016 add-ins.
Some of the weird details I've picked up:
Opening a new browser window from inside Word (clicking on a link in my add-in that opens a full web browser) prompts a "A website wants to open web content using this program on your computer" and points to Internet Explorer's Protected Mode. I've experimented with turning this on myself and can't recreate the issue.
The user isn't signed into O365. That doesn't seem to make a difference either.
Debugging via F12Chooser shows an [object error] with an error code of "-2147024891" and a "stack" message of "Error: Access is denied..." at the point where data would be pulled...I can't get much more out of the console.
The add-in is able to hit Firebase (I'm using Google's Firebase for authentication) and I get a response from their server...but not my ajax call to my php file.
Any thought or direction appreciated.
I am unable to edit the sharepoint 2013 documents in the browser or the application. This is occurring in all the sites under the farm.
Browser:
It opens perfectly but is non editable
Application:
It opens in Read-only mode. Asks me to save a local copy to edit and it saves locally.
I have tried the following solutions and still it doesn't work:
Changed excel setting
I do not have KB3055034 update
Deactivated "Open Documents in Client Applications by Default" to open documents in the Web App to edit documents in the browser by default
Thanks for your help in advance!
We have several sites that use Forms Based authentication (FBA) within SharePoint. Many of them have been running for months without issues. Within the last week or two we have noticed the following behavior for users trying to access a Read Only Microsoft office document (currently only verified with the 2007 versions of Excel and Word).
The behavior we are seeing exhibited:
The Document starts to open
Within the Office application an IE Window opens with the FBA login screen. There is also a Hyperlink in the top left saying Skip to main content
Clicking cancel several times will open the document
If you identify the site as an IE Trusted site the login screen with the Office app, everything works as before (not an option for the majority of our sites)
Non offices files, like PDFs, do not exhibit this behavior
Non IE Browsers that we have tested (FireFox, Chrome) do not exhibit this behavior.
Is anyone else seeing this issue? I assume it was an update sent from Microsoft that has resulted in this issue, since we are seeing it on multiple sites where the code has not been updated.
Thanks
The issue we ran into is there was a policy file applied on our network that caused the UAC prompt to be disabled for Vista/Win 7. When this happens, protected mode gets turned off for the IE browsers, which caused the issues we were seeing.
If you want Office integration to work under forms authentication you should do the following:
Turn on client integration in Central Administration for the forms-auth-enabled application
Use persistent cookies for authentication in the forms-auth-enabled application
On the client computer, add the site to trusted sites in IE
If you still see a login screen embedded in Office documents that you open, try the following on the client computer (if Windows 7):
Go to Control Panel, User Accounts
Click Manage User Account Control Settings
Change slider to Never Notify
Click OK and reboot the computer