BUG: Remote OLE Applications Using Callbacks Fail on OSR2

Last reviewed: January 29, 1997
Article ID: Q162818
The information in this article applies to:
  • Microsoft Visual Basic Enterprise Edition, 16-bit and 32-bit, for Windows, version 4.0 on the following platform: Win95

SYMPTOMS

When a Remote OLE client using callbacks is installed on a computer running on ORS2 (Windows 95b), the client fails when a callback is initiated.

RESOLUTION

The only workaround is to remove the Dial-Up Adapter from the system configuration.

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. We are researching this bug and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

To confirm that you have OSR2 installed, from the Start menu, select Settings and click on Control Panel. Double-click on the System icon. On the General tab the system will be described as "Microsoft Windows 95 4.00.950 B"

To remove the Dial-Up Adapter, from the Start menu, select Settings and click on Control Panel. Double-click on the network icon and select the Configuration tab. Select Dial-Up Adapter and click the Remove button. Close all applications and restart your system.

NOTE: The only clients that fail are ones that use callbacks. Remote OLE clients that do not use callbacks have no problems running on OSR2. For an example of a Remote OLE application that employs callbacks, see the Visual Basic, Enterprise Edition 4.0 CD in the \VB\Samples\RemAuto\Callback directory.


KBCategory: kbole kbbuglist
KBSubcategory: IAPOLE
Additional reference words: 4.00



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: January 29, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.