Sharepoint 2016 OnPrem Document Library New button behavior doesn't display Office Online apps
Somehow, a poweruser has messed up their site collection.
The farm is connected to our Office Online installation and works with other site collections. For this poweruser, when we click on a document library New button, the only option that displays is Excel and "magically" an previously created excel document pops up in excel (without clicking the excel popup link).
Is anyone familiar with this behavior or how to fix it?
Attempts: I created a new document library, but get the same effect. This effect happens on subsites as well. I create a new site collection in the same farm and it works as expected.
---
Edit: I exported the site and imported it into a clean site. The import log shows:
[1/19/2018 1:17:12 PM] [-List] [wfpub] [wfpub] [9851366e-5c8c-415d-8250-b
Parameter name: Specified value is not supported for the urlOfFile parameter.]
I suspect that the poweruser was using a "Forms" library as if it were a Document Library. The poweruser had not developed his site too much so we ended up destroying his site and creating it anew.
He's satisfied for now, but I'm still curious what could have caused a user to get themselves into so much trouble.
The farm is connected to our Office Online installation and works with other site collections. For this poweruser, when we click on a document library New button, the only option that displays is Excel and "magically" an previously created excel document pops up in excel (without clicking the excel popup link).
Is anyone familiar with this behavior or how to fix it?
Attempts: I created a new document library, but get the same effect. This effect happens on subsites as well. I create a new site collection in the same farm and it works as expected.
---
Edit: I exported the site and imported it into a clean site. The import log shows:
[1/19/2018 1:17:12 PM] [-List] [wfpub] [wfpub] [9851366e-5c8c-415d-8250-b
Parameter name: Specified value is not supported for the urlOfFile parameter.]
I suspect that the poweruser was using a "Forms" library as if it were a Document Library. The poweruser had not developed his site too much so we ended up destroying his site and creating it anew.
He's satisfied for now, but I'm still curious what could have caused a user to get themselves into so much trouble.
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER