Previous Topic

Next Topic

Book Contents

Book Index

Troubleshooting

This chapter deals with errors seen while using bcdDocuments and ways to avoid and correct them

If you are experiencing problems using bcdDocuments the best way to convey information to Belding Computing, so that we may diagnose and correct errors, is to send us a recipe for duplicating the error or problem. Please send us a description of the problem to support@beldingcd.com.

In This Chapter

Error Messages

Previous Topic

Next Topic

Book Contents

Book Index

Error Messages

1. Error message "Could not open macro storage"

This error message is produced by MS Word and has been seen when using bcdDocuments to make a document from a template. Possible causes of the error message are discussed here kb247028.

In the instance we examined the cause of the error was a fault with Microsoft file NORMAL.DOT. The solution, suggested by the Microsoft article, was to rename NORMAL.DOT to NORMAL_OLD.DOT. After renaming this file MS Word created a new instance of NORMAL.DOT and the problem was no longer present.

2. Error Message "Call was rejected by Callee"

When bcdDocuments requests a service from MS Word using the COM interface provided by MS Word and Word is busy, because it has a dialog open waiting for a user response this may be seen. The solution is to find the open Word dialog and respond to it.

3. Error Message "Missing document variables ..."

This error message is produced by bcdDocuments and appears when you try to make a document with a template that has been damaged and document variables used by bcdDocuments have been deleted. In the document being made a long error message will be inserted advising you to open the document template using bcdDocuments' Document Assistant. Doing this will replace the missing document variables and remove the error.

bcdDocuments uses document variables invisibly inside templates to achieve efficiency when making documents from templates.

See Also

Troubleshooting