Hello. I have a snap-in that was developed before MMC 3.0. On Windows 2003 Server R2 system (that already has MMC 3.0 by default), when I launch mmc console with my snap-in I get the following error message box: MMC has detected an error in a snap-in. It is recommended that you shut down and restart MMC. And options of actions to take: * Report this error to Microsoft and then shut down MMC. * Continue running and ignore errors with this snap-on for the rest of the session. * Continue running and always ignore errors with this snap-in, regardless of user or session. When I choose second option, all works ok, without any problems. I found the following new feature in MMC 3.0 description: * Improved detection and reporting of snap-in problems is possible. MMC found some problem with my snap-in, right? But what is the problem? How can I troubleshoot it? This message is not very descriptive. Is there a way how can I learn details of a problem it found? best regards, Michael
AFAIK on of the methods of one of the interfaces you have implemented in your snap-in returned a failure HRESULT or caused an exception. I have noticed that older versions of MMC tended to silently handle such situations and continue running and the newer versions do report an error. The problem can be located by adding ASSERT(SUCCEEDED(hResult)) before returning it from your methods and/or by debug printing names of the functions in the begging of their execution. Microsoft has a special news group named microsoft.public.platformsdk.mmc for questions related to MMC. "Michael" wrote in message news:uw$5R2%23PHHA.4296@TK2MSFTNGP05.phx.gbl... > Hello. > > I have a snap-in that was developed before MMC 3.0. On Windows 2003 Server > R2 system (that already has MMC 3.0 by default), when I launch mmc console > with my snap-in I get the following error message box: > > MMC has detected an error in a snap-in. It is recommended that you shut > down and restart MMC. > > And options of actions to take: > > * Report this error to Microsoft and then shut down MMC. > * Continue running and ignore errors with this snap-on for the rest of the > session. > * Continue running and always ignore errors with this snap-in, regardless > of user or session. > > When I choose second option, all works ok, without any problems. > > I found the following new feature in MMC 3.0 description: > * Improved detection and reporting of snap-in problems is possible. > > MMC found some problem with my snap-in, right? But what is the problem? > How can I troubleshoot it? This message is not very descriptive. Is there > a way how can I learn details of a problem it found? > > best regards, > Michael >
