We have SharePoint 2019 and running Office Online(v 16.0.10338.20039) as well. Recently we have encountered a strange message where it says "We can't show a preview of this item." This is only happening for all excel files. All other office related files(word, ppt, pdf, etc) are working fine.
Did someone else come across this and has a workaround solution.
When trying to open the excel file, please check the ULS logs on your OOS server. It is located at C:\ProgramData\Microsoft\OfficeWebApps\Data\Logs\ULS. That should give you more clues to troubleshoot.
Related
I'm developing an Office.js based TaskPane Add-in. Recently I see frequently following error message which appears randomly:
Sorry, there was a problem saving your document.
Tell us about this problem to help us fix it. Give feedback to
Microsoft
Session ID: 1334d772-005e-4fcf-9ef0-6d5e19b56865 Please tell Microsoft
about this problem. We have created an error report that you can send
to help us improve Word Online. This report will include a copy of
your document which we will only use to investigate the error.
How can I get insight into this "Report" which is being sent to Microsoft?
The console.log itself doesn't show anything. Is there a way to figure out what might have caused this message?
Even playing around with the Script Lab I receive the same popup error message.
The issue can be more or less reliably reproduced by
Openin
opening a new word document in Microsoft Online
Opening Script Lab Code
Opening Script Lab Run
Selecting the Code example for 'Content control basics'
Running the example
interact with the example to insert and modify content controls
After a random period of time, the message pops up
Update: Issue was addressed and fixed by the Microsoft Office Team:
https://github.com/OfficeDev/office-js/issues/54#issuecomment-364346330
I'm running Windows 10 and I have Office 365. It's my personal PC, not using Active Directory.
When I'm trying to use OneDrive and when I open it, I get this error:
We cannot synchronize your documents anymore
I tried sfc /scannow, ccleaner and others tricks. No change at all.
I'm thinking it's due to Office 365 connected to my OneDrive PRO.
Anyone have any information about this issue?
I read the microsoft forum and many people face the same issue.One of the solution I came across is:
Hey everyone. I just found what might be the solution in another discussion thread on this same forum. It is suggested to Uninstall the new OneDrive for Business. You should see it in your Programs and Features control panel.
Here is the link for further info
https://answers.microsoft.com/en-us/onedrive/forum/odfeatures/microsoft-onedrive-notification-on-desktop-we-cant/0e20fca5-832c-4928-9438-71484fba3255
Windows 8.1 and
Office 2013
If I try to open an invalid spreadsheet XML file in Excel a pop-up notification gives a brief explanation of the problem and a points to a detailed log file in the Content.MSO folder. However, when I open the detailed log file, it is empty. Earlier versions of Excel and/or Windows populated this log file with each issue encountered.
What is preventing this log file from being populated?
I'm not sure of the KB number but a fix for Office 2013 related to this issue was pushed through Windows Update around 12/12/2014. Error logging appears to be working again.
Back in the day, Outlook 2003, I wrote an app that would go out and check a users mailbox for all messages that were over a certain size, then send them a HTML report with links to those messages. They could click the link and it would take them directly to the message.
Now, new company and several versions of Outlook later, Outlook 2010 now, I am attempting to do the same. Only problem is, everything I have read states that the HREF for Outlook:inbox (or whatever) is no longer supported.
It seems odd to me that such a handy feature would be removed. Is there a workaround for this?
I have searched and searched the web but to no avail. Any help is greatly appreciated.
Geo...
MAPIFolder.FolderPath returns path to current folder.
I had two clients with a save issue in SharePoint.
When they try to save they would get a a very generic error: "Document Could not be saved"
The only way they could get them into SharePoint was by:
Saving to local File System
Using the Upload option from the SharePoint menu
Configurations
Client 1: Vista and Office 2007
Client 2: XP and Office 2003
I was able to fix client 1 by having him Map a Network Drive to the Sharepoint Site.
After mapping the network drive, somehow the OS magically knew about the SharePoint documents folder and he was able to save.
I'm not having the same luck with Client 2.
It won't even let me map the network drive. I get an error (one that I did not take a screenshot of and don't remember the exact wording...sorry). but it was an error trying to map the network drive to the SharePoint site.
So, after some Googling, I had him go to Windows Update and download all the latest patches for his OS.
He claims he did, but is still getting the problem.
Before I do another WebEx and start taking stabs in the dark to try and fix him, I was wondering if any veteran SharePoint users have run into this same issue and what they did to fix.
Or, is there some OS setting I should be looking at that needs to be toggled/modified.
I can access his SharePoint site just fine from several PCs and make modifications and save as necessary.
Did you try running the Microsoft Office Diagnostics?
Start --> Microsoft Office --> Microsoft Office Tools --> Microsoft Office Diagnostics
Let that scan and repair any issues it finds and see if that helps. That tool has fixed similar issues for me many times.