
Hi @Bikram Pal ,
According to my research, there are some possible causes for this issue:
- One possible cause is that the new web front end server is not configured properly to communicate with the Office Online Server. You may need to check the following steps on the new server:
- Install the Office Online Server prerequisites and updates.
- Run the New-OfficeWebAppsFarm or New-OfficeWebAppsHost cmdlets to create a new Office Online Server farm or join an existing one.
- Configure the bindings and zones for the Office Online Server farm.
- Run the New-SPWOPIBinding cmdlet to create a new binding between SharePoint and Office Online Server.
- Verify that the SharePoint and Office Online Server certificates are trusted by each other.
- Another possible cause is that the SharePoint services related to document viewing are not running or not started on the new server. You may need to check the following services on the new server:
- PowerPoint Service
- Word Viewing Service
- Excel Calculation Service
- Excel Services Application Web Service Application
- Secure Store Service
- Visio Graphics Service
- The third possible cause is that the file types or file extensions are not supported by the Office Online Server or SharePoint. You may need to check the following settings on the new server:
- Verify that the file types and file extensions are enabled in the SharePoint Central Administration site.
- Verify that the file types and file extensions are supported by the Office Online Server. You can use the Get-OfficeWebAppsFarm cmdlet to see the supported file types.
There are some articles for your reference:
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.