In all seriousness, COM code is difficult to troubleshoot, but I'll give you a few things to check based on my own experience.
The most important thing is to determine whether anything in the environment has changed.
- Confirm that the server has Excel installed on it. (It cannot instantiate an Excel COM object if Excel is not installed on the server. This is possible if the Notes server was moved to a new physical machine that does not contain Excel.)
- If your Excel COM object was created for a specified version of Excel, confirm that the specified version is consistent with the version of Excel on the server.
- Confirm that the design of the Excel template is the same design that your code is expecting.
- Verify that the agent signer has rights to run restricted operations such as creating files on the server.
- Verify that the code does not have memory leaks (i.e., that it properly closes the COM objects so they are not hanging around in the server's memory). This includes error handling to make sure these objects are cleaned up properly.
If all else fails, adapt the code to run in the Notes client and try to test it locally to ensure that the code is still doing what it's supposed to do.
Do you have comments on this Ask the Expert question and response? Let us know.
Dig Deeper on Lotus Domino Designer
Related Q&A from Brad Balassaitis
Upon moving to Lotus Notes 8, some Lotus Notes users received an error message stating: 'Database has not been opened yet.' Find out why here. Continue Reading
Discover what security settings you need to fix if you encounter the Lotus Notes database error: 'database is not opened yet.' Continue Reading
Learn the Formula language code that you can use if you'd like your Lotus Notes form with embedded views to stop displaying all response documents. Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.