Troubleshooting Office files and custom solutions with the telemetry log. 13 minutes to read.In this articleUse the Telemetry Log for Office 2013 to determine compatibility issues with Office 2013 and solutions built for previous versions of Office.The following article describes the Telemetry Log and how to use it.
For more information about specific results displayed in the Telemetry Log, see.Over the course of many releases, Microsoft has provided tools and frameworks for customizing, automating, and extending Office. This has enabled businesses and users to build solutions or add-ins for Office applications to improve their productivity and efficiency. These solutions can range in complexity from simple Visual Basic for Applications (VBA) macros to robust.NET Framework customizations. Many users who have these solutions rely on them to complete business-critical tasks and may not even know that they are using a customization that is added to their Office applications.With such a proliferation of Office solutions, upgrading versions of Office can be complex.
Enterprises and users do not know whether their important and valuable solutions are completely compatible with the new version. Their solutions might use features and computer code that are available in previous versions of Office that have been deprecated in later versions. If a solution that uses a deprecated feature is loaded into the 'host' application, the solution might behave differently, cause an error, fail to load, or cause the host application to fail.The Telemetry Log for Office 2013, a tool built upon Excel 2013, helps developers and experienced users diagnose compatibility issues by displaying events that occur within select Office 2013 applications. Using this tool, users can determine potential issues with add-ins that they use in their work environment, giving enterprise decision-makers the information that they need to decide whether to upgrade to Office 2013. The Telemetry Log also gives detailed feedback about specific changes or deprecations in the object models for the Office 2013 applications, which helps developers quickly identify and refactor problematic code or controls. IT professionals can view trends in solution health across multiple clients by using the Telemetry Dashboard for Office 2013, a companion tool to the Telemetry Log.For more information, see. How the Telemetry Log worksWhen an Office file or solution is loaded, used, closed, or raises an error in one of the selected Office 2013 applications, the application adds a record in a local data store (a database on the same computer) that includes information about the event.
The record includes a title for the event, the application that logged the event, the time, the name of the file or solution, the severity, and a short description of any errors that may have occurred. When refreshed, the Telemetry Log workbook displays a list of the records contained in the local data store. NoteThe default location for the local data store is%Users%Current userAppDataLocalMicrosoftOffice15.0Telemetry. The default maximum size for the data store is 5 MB (5,120 KB).Selected Office 2013 applications have a run-time logging API that creates a record in the local data store every time that a file or solution raises one of the following events:.OnLoad: A record is logged in the local data store when a file or solution is loaded into specific Office 2013 applications. The run-time error logging records the file name, location, and other information in the local data store when an OnLoad event is raised.OnClose: A record is logged when a file or solution is closed within the application.
Sep 11, 2015 - If the version of Microsoft Office you are using is 2010 or 2013, you should do the following steps: In Control Panel, open Administrative Tools. Start Event Viewer. In the list of event logs, select Application. On the View menu, click Filter. In the Event source list, select VSTO 4.0. The problem is they always have to manually log in to Word after logging into Windows. We don't have roaming profiles and use ADFS. Ideally there is a policy or script which can autologin the user into Office 2016 after logging into WIndows.
The record includes the name of the solution or file, its location, and the application that logged the event.OnError: A record is logged when an error is found in a solution for certain Office 2013 applications. The record includes the name of the solution or file and the run-time failure or compatibility issue that the user encountered. When possible, errors are mapped to known compatibility issues and are displayed as such in the Telemetry Log.The Telemetry Log displays information about a large list of files and solution types for a selection of Office 2013 applications. The type of files and solutions that are monitored by the run-time logging APIs vary by application. See the Table 1 for more information about what kinds of solutions are monitored. NoteIt is not necessary to save the Telemetry Log workbook in Excel 2013 to keep a record of the results, because the information is stored in the local data store (which is separate from the Telemetry Log). However, saving the workbook does not damage the Telemetry Log.The Telemetry Log displays some simple information about the recorded events.
Each record displayed in the Telemetry Log contains a title and lists the severity of the event displayed. For errors, the records also include a description of the error together with steps to address the issue. Keep in mind that not all of the records displayed represent errors caused by Office solutions; the Telemetry Log also shows when solutions and files are loaded or closed successfully.For example, the issue titled 'OM Hidden: Comment.Initial Property' appears if a solution or macro-enabled file opened in Word 2013 attempts to get the initials of a commenter who is associated with a comment. Word 2013 features an improved commenting experience that does not display commenter initials by default. The APIs associated with the older commenting model have been hidden in the Word 2013 object model but remain available for backwards-compatibility.
The 'OM Hidden: Comment.Initial' issue in the indicates the file that attempted to use the API, the application that raised the event (Word 2013), the time and date of the event, and short description about the error and how to fix it.Figure 1. Office Telemetry Log. NoteThe System Info worksheet in the Telemetry Log contains information about the computer on which Office 2013 is installed.
The worksheet displays the following information:. User name. Full computer name.
Architecture of the operating system (x64/64-bit or x86/32-bit). Version of Windows that is installed on the computer.
Time zone for the computer's internal clock. Version of the Telemetry Log. Version of Office that is installed on the computer.This information can be useful when you are interpreting the issues and events listed on the Events worksheet.In the Telemetry Log, a level of severity is displayed together with the known issues. From the previous example, an issue in which a part of the object model has been hidden most often has an 'Informative' level of severity. On the other hand, other known issues might be more serious and require more immediate action. The severity of the issues displayed in the Telemetry Log can be one of the following:.Information The issue may not have an immediate effect on application compatibility, but the user may have to take an action later.
Many issues of the 'OM hidden' type have this severity level.Warning The issue could cause data loss or result in reduced visual fidelity.Critical The issue could cause significant loss of functionality or lead the application to crash.Table 2. Types of events displayed in the Telemetry LogUse the following table (Table 2) to interpret the records that are displayed in the Telemetry Log. Event IDTitleSeverityDescription1Document loaded successfullyThe file listed in the File column was opened in the Office application without any issues.2Document failed to loadWarningThe application was unable to load the file. There may be some underlying compatibility issue.For more information about how to repair a corrupted workbook in Excel 2013, see.For more information about how to repair a corrupted document in Word 2013, see.3Template loaded successfullyThe template file listed in the File column was opened in the Office application without any issues.4Template failed to loadWarningThe application was unable to load the template file. There may be some underlying compatibility issue or the template availability may have changed.For more information about how to repair a corrupted workbook in Excel 2013, see.For more information about how to repair a corrupted document in Word 2013, see.5Add-in loaded successfullyThe add-in listed in the File column loaded within the Office application successfully.
Image: Avosb/iStockYou've been working on an important document in Microsoft Word, and now it's missing. You've searched your default document location, your entire hard drive, and the Recycle Bin, but the Word document is still nowhere to be found. Is it gone for good? Do you have to recreate the document from scratch?
No, at least not yet. You may still be able to locate and revive the Word document by taking certain precautions ahead of time and looking for the right files in the right places.SEE: (Tech Pro Research). More about Windows.Your Word documents, like other files, can lose their way.
Sometimes you may create or revise a document and simply forget to save it; other times, your computer may freeze, crash, or otherwise hiccup, preventing your document from saving properly. In these cases, you may lose the entire Word document or just the latest changes, or the file itself may become corrupted and unreadable. Whatever the scenario, you can often recover the entire file—complete with the latest changes.To start, let's assume you've already checked your hard drive and your Recycle Bin for the file, either by the specific name or a wildcard combination, but you came up empty.
Here's one tip: Do you use in Windows 10 to back up important folders, including those for your Word documents? If so, open your backup drive to look for the document in the proper location. Here's another tip: Do you sync your documents through OneDrive or another online service? Most cloud-based storage sites offer a Recycle Bin or Trash folder where you can restore deleted files. In the case of OneDrive, open your online storage space. You can search across all folders for your document by name or wildcard combination.
![2016 2016](/uploads/1/2/5/6/125627290/838616822.jpg)
Otherwise, click the entry for Recycle Bin. OneDrive and other storage sites hold onto your deleted files for up to 30 days—you can sort your deleted files by name, location, deleted date, or size.
If you find the document, select it, and click the Restore button ( Figure A). Figure ANext, there are steps you can take in Word before you lose a document so that you can more easily find a backup version of it. In Word, open the File menu, select Options, and then click Advanced. Scroll down the Advanced screen until you see the section for Save. Check the option for Always Create Backup Copy ( Figure B).Figure BIf a document ever goes missing, open your default document location. Browse or search for files that start with the name Backup of and have the extension wbk. If you find the appropriate backup of your lost document, just double-click it to open it in Word ( Figure C).Figure CHere's another setting in Word that should be enabled.
Return to the Word Options menu and click Save. Make sure the option to save AutoRecover information is checked—this option can come to your rescue if a document is ever saved without its latest changes. Set the number of minutes to save the file. Note the AutoRecover file location ( Figure D).Figure DIf you find your lost document but without the latest changes, click the File menu in Word (2016 or 2013). Click the Manage Document button and select Recover Unsaved Documents ( Figure E).Figure EIn the Open window, look for any files with an ASD extension. Open the right file in Microsoft Word to see if your document appears with the latest changes ( Figure F).Figure FThrough File Explorer, you can also check the AutoRecover file location, which is typically C:Usersyour usernameAppDataRoamingMicrosoftWord.
Look for and open a folder with the name of your document. You can open the ASD file itself in Word, or more easily click on the shortcut with the docx extension to open the recovery file ( Figure G).Figure GSometimes a lost or unsaved Word document may still exist as a temp file. Open File Explorer and search your hard drive for.tmp files. Switch the view to Details so you can sort the files. After all the results appear, click the Date Modified header to sort the files by date, starting with the latest ones first. Look for files tagged with the date your document went missing. Avoid any files with a size of 0KB.
Open each potential file in Word to see if you find your lost document ( Figure H).Figure H.