I have some reports that are retrieving there data from COM+ components. It works fine when no errors are encountered but if the component hits a snag and exits, the RAS reports that no rowset could be found (which is fine) but then, on the next call to that component, it will get hung up and just sit there. It hangs so badly that I cannot even restart it with the service manager; I need to attach the C++ debugger to querysrv.exe and then kill the process that way. There are no error messages from the server. I have no problem with the Crystal 9 report creat tool; it will simply complain about not finding the rowset, but will not die.
These components are set up as Main apartment threaded and are in a COM+ library application. I'm using Crystal 9 Enterprise. Is it possible I have an imcompatible threading model for the RAS?
These components are set up as Main apartment threaded and are in a COM+ library application. I'm using Crystal 9 Enterprise. Is it possible I have an imcompatible threading model for the RAS?
