Updated: 2007-05-17

This article discusses problems and solutions for using Office Migration Planning Manager (OMPM) to assess your environment and to convert files.

OMPM database import fails

Microsoft recommends importing 100 cabinet (CAB) files or less. Importing more than 100 full CAB files, or more than 1,000,000 XML scan logs, can cause the import to fail.

Import operations also fail on computers that run 64-bit operating systems.

OMPM Reports does not start

You must install either Access 2007 or Access 2007 Run-Time on the computer that is running OMPM Reports. Access Run-Time is available at Access Run-Time download (http://go.microsoft.com/fwlink/?LinkId=83030).

OMPM Reports fails

OMPM Reports might fail when the current filter returns more than 1,000,000 records. To avoid this problem, set the filters to reduce the number of records that are returned, or use more than one OMPM database. You can also query the OMPM database directly to handle large data sets.

OMPM Reports takes a long time to return results

OMPM Reports can take more than 30 seconds to return results for filters that return more than 110,000 records. You can increase the speed of the OMPM Reports query by setting the filters to return fewer records. You can also query the OMPM database directly.

Office File Converter (OFC) fails

OFC does not work if you set the TimeOut value in ofc.ini to 0. Use a positive number to assign the number of seconds for this property.

During a bulk conversion, some files might cause a dialog box to appear that indicates that OFC has failed. OFC has not failed; it will continue to the next file in the conversion.

See Also

500 Internal Server Error

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at webmaster@informationworker.forsenergy.ru to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.

Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.