PRB: IROT::IsRunning() Returns S_FALSE for OLE 1.0 Servers

Last reviewed: May 17, 1995
Article ID: Q109544

The information in this article applies to:

Microsoft OLE Libraries for Windows and Win32s, version 2.01

Microsoft OLE Libraries, included with:

    - Microsoft Windows NT, versions 3.5 and 3.51
    - Microsoft Windows 95

SYMPTOMS

When an OLE 2.0 container application calls IRunningObjectTable::IsRunning() on the moniker for a linked OLE 1.0 object, IsRunning() returns S_FALSE even if that OLE 1.0 object is already running.

CAUSE

OLE 1.0 objects do not register themselves in the running object table while they are running.

RESOLUTION

Calling IMoniker::IsRunning() on the moniker for a linked OLE 1.0 object correctly returns S_OK if the object is indeed running.

As noted in the OLE SDK version 2.01 documentation for IRunningObjectTable::IsRunning(), clients of a moniker should not call IRunningObjectTable::IsRunning() directly; instead, they should call IMoniker::IsRunning().

Additional reference words: 2.01 3.50 4.00 irot
KBCategory: kbole
KBSubcategory: LeTwoLnk

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: May 17, 1995
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.