Analyze Office Migration Planning Manager Reports for Office 2010
Applies to: Office 2010
Topic Last Modified: 2011-08-29
Use the OMPM Reports tool to review and report on compatibility results that are identified by the Office Migration Planning Manager (OMPM) file scanner. You use the OMPM Reports tool after you deploy OMPM, scan files for compatibility issues, and then import the results into a database. If you have not performed these steps, see Office Migration Planning Manager overview for Office 2010 to get started.
In this article:
Configure OMPM Reports
Review Scan Coverage and Errors
Review Office 2010 Compatibility
Analyze Excel, Word, or PowerPoint files that use macros
Review Access Compatibility
Important
The OMPM tool has been updated as of July 2011, The release is available at the Microsoft Download Center (https://go.microsoft.com/fwlink/p/?LinkId=199599). Numerous fixes and enhancements are available for the OMPM File Scanner, the Office File Converter (OFC) tool, and the Version Extraction Tool (VET). If you are using a previous version of OMPM, you cannot re-use existing client scan results, databases, or any exported data by using the new version of OMPM. You must create new databases and re-scan clients by using the new version.
You can use OMPM Reports to perform the following actions:
Review OMPM File Scanner results for Office 97 through Office 2003 files for a specific scan, or for a specific computer
Create a list of files with conversion issues
Export the list of files that have conversion issues to an XML file that can be used by the Office File Converter (OFC) or the Version Extraction Tool (VET)
Configure OMPM Reports
OMPM Reports (OMPM.accdr) is in the Report folder in the OMPM download package.
Important
Use of OMPM.accdr requires the 32-bit version of Access 2007 or Access 2010. If you are using the 64-bit version of Access 2010, you receive the following error message when you attempt to view reports: “Execution of this application has stopped due to a run-time error. The application can't continue and will be shut down.”
To use OMPM Reports
In the Reports folder where you installed OMPM, double-click OMPM.accdr. Click Yes at the security prompt.
On the OMPM Welcome page, in the Server drop-down box, select the computer that is running the Microsoft SQL Server or Microsoft SQL Server 2005 Express Edition database that you are using to store scan data. If the server is not the default for a computer, it must be specified as the named instance in the form <ComputerName>\<ServerName>. By default, SQL Server installs itself as the default instance on a server, but SQL Server 2005 Express Edition installs itself by using SQLEXPRESS as the named instance.
In the Database drop-down box, select the name of the database. Click Connect. If you have already connected to a database, OMPM Reports automatically opens the database. If you want to connect to a different database, click Connect.
Review Scan Coverage and Errors
Use the following procedure to review the scan results for a specific scan. Only scanner coverage and errors are reported. Use the Office 2010 Compatibility report to review the upgrade issues that are identified by the scanner.
To review scan coverage and errors
On the OMPM Welcome page, select Scan Coverage and Errors. This brings up the Scan Results page.
Select a Run ID at the top of the Scan Results page to view the results for that run of the OMPM File Scanner.
To view the scan results for a specific computer, select the computer in Scan results for each computer in the run selected above. The scan results appear in Scan errors for the run and computer selected above.
Severity levels
The severity levels in the following table map to the kinds of errors that might occur during a bulk conversion of files to the Office 2010 format.
| Issue Level ID | Description |
|---|---|
1 (Red) |
Known issues that can cause significant data loss such as Microsoft Word 2010 edit version loss, or cause a conversion to fail. |
2 (Yellow) |
Files convert to the Office 2010 format. However, some format or minor data loss issues might occur. |
3 (Green) |
Light cosmetic issues, no data loss. |
Errors for Word, Excel, and PowerPoint
The following table provides a complete list of the errors the scanner can generate for Microsoft Word, Microsoft Excel, and Microsoft PowerPoint.
| Issue ID | Title | Description | Issue level ID |
|---|---|---|---|
1000 |
File Deleted |
The file no longer exists at the requested location. |
1 (Red) |
1001 |
File Access Error |
The file location cannot be accessed, probably because a computer is inaccessible. |
2 (Yellow) |
1002 |
File Modified |
The file modified date does not match the modified date in the file list. |
1 (Red) |
1003 |
No Write Permissions |
The user account does not have permissions to write to the file. |
2 (Yellow) |
1010 |
Not Deep Scanned |
The file has not been deep scanned yet. |
2 (Yellow) |
1021 |
Scan Skipped: Old Last Accessed Date |
Scan of the file was skipped because the last access date of the file is earlier than the specified scan parameter |
2 (Yellow) |
1022 |
Scan Skipped: Old Last Modified Date |
Scan of the file was skipped because the last modified date of the file is earlier than the specified scan parameter |
2 (Yellow) |
1050 |
Warning: File Not Scanned |
Warning: File cannot be scanned. Review the Scan Coverage and Errors report for more information |
2 (Yellow) |
1100 |
Document contains versions |
Edited versions of the document will be removed when the file is opened in Word 2010, even in compatibility mode. |
1 (Red) |
1200 |
Send for review data |
This file has review comments and contains a hidden baseline copy of the original. Microsoft PowerPoint 2010 discards the hidden copy. Saving the file removes the hidden copy permanently. Users cannot tell which edits reviewers made if they reopened the file in previous versions. |
1 (Red) |
1201 |
Embedded documents |
There are potential performance, security, and fidelity issues with embedded documents. |
2 (Yellow) |
1202 |
VBA code |
This file contains embedded VBA code. This can create security, fidelity, performance, and solution compatibility issues. Check this file for compatibility with PowerPoint 2010. |
2 (Yellow) |
1203 |
Microsoft Script Editor (MSE) data |
When this file is opened, PowerPoint 2010 discards MSE data that was stored in shapes. Saving the file removes the data permanently. Solutions that depend on this data might break. |
1 (Red) |
1204 |
Presentation broadcast data |
When this file is opened, PowerPoint 2010 discards configuration settings for HTML broadcast presentations. Saving the file removes the settings permanently. To broadcast in an earlier version, the user must manually reenter the settings. |
1 (Red) |
1205 |
Document routing |
When this file is opened, PowerPoint 2010 discards routing information. Saving the file removes the routing information permanently. To route the presentation in an earlier version, the user must manually reenter the routing information. |
1 (Red) |
1206 |
Publish and subscribe data |
When this file is opened, PowerPoint 2010 discards Macintosh Publish and Subscribe information. Saving removes that information permanently. If an earlier version of the file is reopened, the Publish and Subscribe feature no longer function. |
2 (Yellow) |
1207 |
Large number of OLE objects |
This file contains many embedded objects. This can create security, fidelity, performance, and solution compatibility issues. Check this file for compatibility with PowerPoint 2010. |
2 (Yellow) |
1300 |
Open format not supported |
This file format will not open in Microsoft Excel 2010. |
1 (Red) |
1301 |
Save format not supported |
You cannot save to this file format in Excel 2010. |
2 (Yellow) |
1302 |
HTML will be a publish-only file format |
The HTML file format is a publish-only file format in Excel 2010. The file opens in Excel 2010, but when it is saved to an Excel 2010 format, the file is static. |
1 (Red) |
1303 |
Links in workspace files might be broken |
A workspace file (.xlw) might contain links to other workbooks. The .xlw file might be broken if the links are changed during an upgrade. |
3 (Green) |
1304 |
File format is earlier than Excel 97 |
This file format is from a version before Excel 97. It cannot be scanned for migration. |
2 (Yellow) |
1305 |
SharePoint linked lists in the file |
Linked lists are read-only in Excel 2010. |
2 (Yellow) |
1306 |
Microsoft Script Editor present in the file |
Microsoft Script Editor (MSE) is not included in Excel 2010. UI access to MSE is not available, and object model calls will return an error. |
1 (Red) |
1307 |
Linked workbooks in the file |
Linked workbooks are identified to help pinpoint upgrade issues. The path of the linked workbook and the number of occurrences are identified. Linked workbooks have different file name extensions when they are converted to the Excel 2010 file format. |
2 (Yellow) |
1308 |
Charts in the workbook |
Excel 2010 charts might not be displayed in the same as they are in Excel 2003. |
3 (Green) |
1309 |
English Language Formulas in the workbook |
English Language Formulas (ELFs) are turned on. Even though ELFs are not included in Excel 2010, they are changed to cell references so they can continue to work in Excel 2010. |
3 (Green) |
1310 |
Embedded documents in the file |
Embedded documents are not scanned for compatibility issues. |
2 (Yellow) |
1311 |
MSOWC.dll is referenced |
This file uses features of the Office 2000 Web Components (MSOWC.dll). The Office 2000 Web Components are not installed as part of the Office 2010. You might have to install them separately. |
3 (Green) |
1312 |
OWC10.dll is referenced |
This file uses features of the Office XP Web Components (MSOWC.dll). The Office XP Web Components are not installed as part of the Office 2010. You might have to install them separately. |
3 (Green) |
1313 |
OWC11.dll is referenced |
This file uses features of the Office 2003 Web Components (MSOWC.dll). The Office 2003 Web Components are not installed as part of the Office 2010.You might have to install them separately. |
3 (Green) |
Review Office 2010 Compatibility
Use the following procedure to review Office 97-2003 files for compatibility issues with Office 2010. For a list of filtering criteria that you can select from the Office 2010 Release Compatibility page in OMPM reports, see Office Migration Planning Manager 2010 reports filtering reference for Office 2010. For information about using the OFC and VET, see Convert binary Office files by using the Office File Converter (OFC) and Version Extraction Tool (VET).
To review Office 2010 compatibility
On the OMPM Welcome page, select Office 2010 Compatibility. The Office 2010 Compatibility page opens.
Do one of the following:
Load a filter that you previously saved by clicking the Load Filter button at the bottom of the page, or
Specify your file filter settings in Select a File Filter, along the left side of the page.
To apply the filter, click the Apply Filter button at the top of the 2010 Office release Compatibility page. Use the tabs on the right side of the page and follow these steps.
Select the Issue Summary tab to view a summary of the issues that were identified by the OMPM File Scanner by severity, type, and frequency. You can open the summary in a new window by clicking New Window at the bottom of the page.
To view issues and edit their severity level, click Manage Issues at the bottom of the Issue Summary page, and review or edit issues on the resulting Manage Issues dialog box. If you review the impact of an issue and the issue is not important for your document set, you can also change the issue level in this dialog box. You can use this to organize your files into processing groups of Red, Yellow, and Green status.
Select the Computer Summary tab to view a summary of the issues for each computer that was scanned. You can bring up the summary in a new window by clicking New Window at the bottom of the page. To obtain a printable report, click Report View at the bottom of the page.
Select the Scanned Files tab to view files that match the criteria set by the filter that you applied. You can bring up the summary for all files in a new window by clicking New Window at the bottom of the page. To obtain a printable report, click Report View at the bottom of the page.
Select the Created Files tab to view files that were created by using the Office File Converter or Version Extraction Tool. You can open the summary for all files in a new window by clicking New Window at the bottom of the page. To obtain a printable report, click Report View at the bottom of the page.
To save the filter, click the Save Filter button at the bottom of the page.
Export the files to an XML file for use by the Office File Converter or Version Extraction Tool by clicking the Export button at the bottom of the page.
Analyze Excel, Word, or PowerPoint files that use macros
If you enable macro scanning in Offscan.ini, OMPM 2010 provides a report that shows you the files that contain macros that use VBA code. The report shows the number of objects that the scanner identifies as changed from the current state to the Office 2010 model. If you enable 64-bit macro scanning in Offscan.ini, the macro report also contains a column that displays the number of potential issues that can occur if the current VBA code is used with 64-bit Office 2010.
To analyze Excel, Word, or PowerPoint files that use macros
On the OMPM Welcome page, click Office 2010 Compatibility.
Click the Macro Summary tab to view a summary of the issues for each file that was scanned. You can view the summary in a new window by clicking New Window at the bottom of the page. To obtain a printable report, click Report View at the bottom of the page. Only files that contain macros are included in this view.
Review the number of potential issues that are listed in the Functionality Issue Count column. The number that is listed in the column is the number of potentially changed objects that the scanner identified in the VBA code.
Review the number of potential issues that are listed in the x64 Compatibility Issue Count column. The number listed that column is the number of potentially changed objects that the scanner identified in the VBA code.
Review the files that are listed in this view with file owners to assess the need to update them to Office 2010 compatibility.
Engage with a developer to correct these files by using the Office Code Compatibility Inspector (OCCI).
Review Access Compatibility
Use the following procedure to discover issues that apply to migrating Microsoft Access versions 97 through 2003.
To review Access compatibility
On the OMPM Welcome page, select Access Compatibility. The Access Reporting page opens.
On the Access Reporting page, look at the date of the last analysis (next to Analyze). If you have run a scan after that date, or if you have never run Analyze, click Analyzer Settings on the Access Reporting page, specify the settings that you want, and then click Analyze. If you do not have to configure the settings and want to start an analysis of the scan data, click Analyze on the Access Reporting page.
Note
Clicking Analyze prompts you with the message: "Analysis can take quite a long time and should not be canceled mid-run. Are you sure you want to continue?" If your scan data covers fewer than 100,000 Access databases, the analysis usually takes only a few minutes. If there are more than 100,000 databases, the analysis can take a long time. You might prefer to run the analysis overnight.
To search the Access scan data by field, select QuickSearch on the Access Reporting page. This page lists files that OMPM has analyzed. Use QuickSearch to find a specific database file by name, or a list of databases in a specific path or on a specific computer.
To view or print interactive reports for Access data, select Reports on the Access Reporting page. The View Reports tab opens. On the left navigation pane, you can select from the following reports:
Database and Issue Details A list of issues for each database file.
Database Issues Grouped by Issue A list of all databases that are identified as having a specific issue.
Executive Summary An overview of issues for all analyzed databases, without the file-level details.
Active versus Old Databases A list of analyzed databases that shows whether they are active or inactive, based on their LastModified property.
Conversion Issue–Database is an MDE file A list of .mde files and .mdb files that have identical names.
Conversion issue–Replicated database A list of databases that use replication.
Conversion issue–Reserved name in Form/Report/Macro A list of databases that contain a reserved name in a form, report, or macro.
To view interactive charts that help you find databases that have certain attributes, select Charts on the Access Reporting page. The Database Charts screen opens. You can then select from the following charts:
Date Last Opened Database count per year opened.
Database Rating Database count by level of user intervention required.
Access Version Database count by version of Access.
File Size Database count by file size.
Conversion Issues Database count by conversion issue.
Warning Level Database count by warning level.
To view databases and database objects on a per-file basis, data, select File Details on the Access Reporting page.
To view database issues on a per-file basis, select Conversion Issues on the Access Reporting page. For a list of Access errors, see “Access errors” in this section.
Access errors
The following table is a list of all the OMPM Access Errors:
| Issue ID | Issue Text | User Intervention | Issue Type | User Intervention Priority |
|---|---|---|---|---|
1 |
Too many code or class modules |
Required |
Error |
1 |
2 |
Sort Order and System Language do not match |
Likely |
Warning |
2 |
3 |
Replicated Database |
Required |
Warning |
1 |
4 |
Database is an MDE file |
Required |
Error |
1 |
5 |
DAO 2.5/3.5 compatibility layer |
None |
Note |
3 |
6 |
Microsoft Jet SQL help |
None |
Note |
4 |
7 |
Additional References |
Likely |
Warning |
2 |
8 |
Missing References |
Likely |
Warning |
2 |
9 |
Reserved Name in Form/Report/Macro |
None |
Note |
4 |
10 |
Linked Tables |
Unlikely |
Warning |
3 |
11 |
Database in uncompiled state |
None |
Note |
4 |
12 |
Backup database |
None |
Note |
4 |
13 |
Sample database |
None |
Note |
4 |
14 |
Old database |
None |
Note |
4 |
15 |
Secure database: User Level Security |
Likely |
Error |
2 |
16 |
Secured database: Database password |
Likely |
Error |
2 |
17 |
System database |
None |
Note |
4 |
18 |
Unsupported legacy format |
Likely |
Warning |
2 |
19 |
Unsupported legacy format – forms, reports, and modules will be lost |
Required |
None |
1 |
Errors 1–17 are the complete list of errors that can be generated by the Access Conversion Toolkit. Documentation for 1–17 can be found in the Access Conversion Toolkit. The documentation is Flash-based and requires the installation of the toolkit. To install the toolkit, see Access 2003 Conversion Toolkit (https://go.microsoft.com/fwlink/p/?LinkId=131929).
Errors 18 and 19 are new to OMPM and mean:
Error 18 – Microsoft Office Access 2007 no longer opens files that were created in Access 2.0.
Error 19 – Office Access 2007 will open a file that was created in Access 95, but will not read its forms, reports, or modules.
See Also
Concepts
Office Migration Planning Manager 2010 reports filtering reference for Office 2010
Office Migration Planning Manager overview for Office 2010
Set up the Office Migration Planning Manager File Scanner for Office 2010
Run the Office Migration Planning Manager File Scanner for Office 2010
Import Office Migration Planning Manager log files into a database
Convert binary Office files by using the Office File Converter (OFC) and Version Extraction Tool (VET)