none
OOS documents don't work on a new farm after mounting a content database from a different farm RRS feed

  • Question

  • Our original Sharepoint server had some machine specific problems but worked for the most part.  The user profile service was broken and it was causing issues for certain users when using office online server docs.  My solution was to create a new server, in a new farm, get everything working there then restore and mount the original content database.

    Mounting the new DB worked like a champ.  All my sites and pages where there and everything seemed to work.  When I tried to open an Word or Excel file via OOS I got errors.  Word and Excel both threw errors but they were different errors.

    Word: Sorry there was a problem we can't open this document. if this happens again, try opening the document in Microsoft word

    Excel: We couldn't find the file you wanted.  Its possible the file was renamed, moved or deleted.

    The issue is with the sharepoint server, not with teh OOS server becasue the old sharepoint server loads documents fine using the same OOS server.  I checked the ULS logs and found that a WOPI reference that had the URL of the old sharepoint server.  

    Is there something WOPI related that could come across with a content database?  I don't know how this new server would have any idea who the old server is since its a new farm. 

    12/23/2019 14:23:30.16 w3wp.exe (0x1358) 0x1C60 SharePoint Foundation WOPI amrzt Medium WOPI endpoint after encoding: https://oldserver.domain.com/infotech/_vti_bin/wopi.ashx 3b66249f-7cbe-40e6-995d-75363fde6b40
    12/23/2019 14:23:30.16 w3wp.exe (0x1358) 0x1C60 SharePoint Foundation Claims Authentication amcbl Medium Trusted provider is missing. Provider: '00000003-0000-0ff1-ce00-000000000000' 3b66249f-7cbe-40e6-995d-75363fde6b40

    12/23/2019 14:23:30.16 w3wp.exe (0x18D8) 0x1CDC SharePoint Foundation Topology e5mb Medium WcfReceiveRequest: LocalAddress: 'net.pipe://newserver/SecurityTokenServiceApplication/appsts.svc' Channel: 'System.ServiceModel.Channels.ServiceChannel' Action: 'http://schemas.microsoft.com/sharepoint/2011/05/securitytokenservice/IApplicationSecurityTokenServiceContract/Issue' MessageId: 'urn:uuid:28e0b93a-215f-4a70-84ff-cb165cd9bb3b' 3b66249f-7cbe-40e6-995d-75363fde6b40

    12/23/2019 14:23:30.16 w3wp.exe (0x1358) 0x1C60 SharePoint Foundation Application Authentication aiv3e High Self-issued token request for 'wopi/oldserver.domain.com@24b39b66-fa3f-4a67-b49a-f68afcafce64' succeeded. 3b66249f-7cbe-40e6-995d-75363fde6b40

    Monday, December 23, 2019 8:07 PM

All replies

  • Hi,

    Have you added the old OOS server to the new farm? You need to reconfigure OOS server for the new farm after the mounting.

    When you integrate OOS with your SharePoint farm, a new WOPI binding would be added to the SharePoint server. The binding will be used across the farm, so it should be carried with content database if you did not disjoin the SharePoint farm from OOS farm.

    I suggest you remove the binding of the old server using PowerShell command and then reconfigure OOS server:

    Remove-SPWOPIBinding -All:$true

    A few things to notice when reconfiguring OOS for the new farm:

    1. Make sure OOS Server is able to connect with SharePoint Web Application by hitting SharePoint Web Application URL in browser from OOS Sever.

    2. For HTTPS, make sure your certificates are placed under “Trusted Certificate Authority” of OOS Server as well.

    3. Make sure you do not login as System Account.

    Here’s your reference.

    OOS Integration with SharePoint Server 2013/2016.

    https://blogs.technet.microsoft.com/jijoseph/2018/03/02/oos-integration-with-sharepoint-server-20132016/

    Best regards,

    Chelsea Wu


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    SharePoint Server 2019 has been released, you can click here to download it.
    Click here to learn new features. Visit the dedicated forum to share, explore and talk to experts about SharePoint Server 2019.

    Tuesday, December 24, 2019 4:34 AM
  • Hi,

    I'm checking how it is going on with this issue.

    Please remember to update this thread if you have any progress.

    Thank you for your understanding.

    Best regards,

    Chelsea Wu


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    SharePoint Server 2019 has been released, you can click here to download it.
    Click here to learn new features. Visit the dedicated forum to share, explore and talk to experts about SharePoint Server 2019.

    Thursday, January 2, 2020 1:31 AM