Manager cannot restore topology

An error, similar to the following, is encountered when you try to start a Manager

[November 3, 2009 12:11:00 PM EST +288ms] t@1141098816 InCharge Framework
ICF-E-EINIT-While initializing the InCharge application
 ICF-ERESTOREREPOS-While attempting to restore topology from file BASEDIR/smarts/local/repos/icf/TEST_SERVER_RM.rps
 MR-CANTCREATE_INSTANCE-'SM_Printer::CAXTON' could not be created.  ; in file "/work/blackcurrent/DMT-9.0.0.X/1201/smarts/repos/mr/dyn_acc.c" at line 2829
 MR-CLASS_NOT_FOUND-Class of given name 'SM_Printer' not found; in file "/work/blackcurrent/DMT-9.0.0.X/1201/smarts/repos/mr/dyn_acc.c" at line 1709
[November 3, 2009 12:11:00 PM EST +430ms] t@1141098816 InCharge Framework
SVIF-N-SHUTDOWN-Shutting down...

This error is occurring because you have an instance of a class in the repository, but the class is not defined in the data model of the Manager. Similar errors occur for attributes, events, operations, problems, symptoms, or aggregates that are in the repository, but not defined in the data model of the Manager.

For example, a dynamic model file was previously loaded into the Manager. The dynamic model file added a new class called, SM_Printer. An instance of the SM_Printer class was discovered and added to the repository of the Manager.

Now, when you invoke the sm_server command the appropriate dynamic model file must be in the proper directory. The directory is determined by whether or not you are including the --dynamic option on the sm_server command line. If you are not loading the dynamic model enhancements into the Manager’s data model, then the SM_Printer class does not exist in the Manager’s data model. The instance of SM_Printer still exists in the repository, and the system tries to restore the instance of SM_Printer that was previously discovered. However, the class does not exist.