PowerPoint 2003 Solution Center

Error Messages

INFO: Error or Unexpected Behavior with Office Automation When You Use Early Binding in Visual Basic
When you automate a Microsoft Office application, you may receive an error message or you may experience unexpected behavior, as follows. You may receive one of the following error messages: You may receive one of the following unexpected behaviors:...
Description of setup command-line switches for Office 2003
Describes the functionality of the switches you can use with the Office 2003 Setup program. Lists the setup command-line switches.
INFO: Translating Large Office Automation Error Values
While automating an Office application, you might receive a large error value such as -2147221494. Troubleshooting the error is greatly facilitated by determining the exact description of the error. This article discusses several methods of obtaining...

Description of the Office 2003 critical update: November 4, 2003
Describes critical update for Office 2003 that is dated November 4, 2003.
Considerations for server-side Automation of Office
Developers can use Automation in Microsoft Office to build custom solutions that use the capabilities and the features that are built into the Office product. Although such programmatic development can be implemented on a client system with relative...

Error messages when you view a PowerPoint presentation: "Hlink.dll Can't Be Loaded" or "PowerPoint Failed to Load Hlink.dll"
When you view a PowerPoint presentation, you may receive one or both of the following error messages:
You receive error messages when you try to open an Office document
Describes the issue that occurs when you receive an error message after you open a specific file in an Office program. This error message may read, "Filename is not valid," "The file could not be accessed," or "The path you entered, ' filename ', is to
List of error codes and error messages for Windows Installer processes in Office 2003 products and Office XP products
Lists the error codes and error messages that may appear may appear in the Windows Installer log file. The error code values and descriptions can help you diagnose installation problems.