DOCUMENT:Q177394  02-DEC-1997  [vbwin]
TITLE   :HOWTO: Troubleshoot Run-Time Error '429' in DCOM Applications
PRODUCT :Microsoft Visual Basic for Windows
PROD/VER:WINDOWS:5.0
OPER/SYS:WINDOWS
KEYWORDS:vb5all kberrmsg

======================================================================
---------------------------------------------------------------------
The information in this article applies to:

 - Microsoft Visual Basic Professional and Enterprise Editions for
   Windows, version 5.0
---------------------------------------------------------------------

SUMMARY
=======

Attempting to access a DCOM Server from a remote client application
sometimes results in the following error:

   Run-time error '429':
   ActiveX component can't create object

This article describes the most common scenarios in which this error is
raised.

MORE INFORMATION
================

The following is a list of possible causes of Run-time error 429. It is by
no means a complete or definitive list.

Problem with Server Run Location
--------------------------------

This scenario applies to Microsoft Windows NT and Microsoft Windows 95
servers.

1. On the Server machine run the DCOM Config utility (Dcomcnfg.exe).

2. Select the DCOM Server from the Applications tab and choose the
   Properties button.

3. Select the Location tab.

4. Ensure the “Run application on this computer” setting is checked.

Incorrect Server Specified in Client Registry
---------------------------------------------

On the client machine, use the following steps to verify that the DCOM
Server machine is properly delegated. This scenario applies to Windows NT
and Windows 95 clients.

1. On the client machine run the DCOM Config utility (Dcomcnfg.exe).

2. Select the DCOM Server from the Applications tab and choose properties.

3. On the General tab be sure that there is an entry for “Remote Computer”
   and that the remote computer name is correct.

4. If the computer name is incorrect, select the Location tab.

5. Ensure the “Run application on the following computer” setting is
   checked. In the dialog box beneath this selection, type in the correct
   computer name for your DCOM Server.

You may also use the following steps to verify the remote computer name by
using the Windows Registry.

1. Run RegEdit.exe.

2. The remote server name is specified in the following registry key:

      HKEY_CLASSES_ROOT\
         APPID\
            {The CLSID of the DCOM Server}\
               RemoteServerName

Enable Remote Connections is Disabled
-------------------------------------

On Windows 95 servers only, you must be sure remote connections are enabled
in order for a remote application to access and execute a serving
application. The following steps can be used to perform this task.

1. Run DCOM Config (Dcomcnfg.exe).

2. Select the Default Security tab.

3. Check the “Enable remote connection” check box.

- or -

1. Run RegEdit.exe.

2. Locate the following registry key:

      HKEY_LOCAL_MACHINE\
         Software\
            Microsoft\
               OLE\
                  EnableRemoteConnect

3. Ensure the EnableRemoteConnect value is set to “Y” for Yes.

Remote Component not Started
----------------------------

On Windows 95 servers only, the DCOM Server application must be started
before a remote client may access it. DCOM Server applications on Windows
NT Servers do not have this limitation.

Binary Compatibility is Broken
------------------------------

1. Open the DCOM Server project.

2. From the Project menu, choose the project Properties.

3. On the Component tab ensure “Binary Compatibility” is selected.

If “Binary Compatibility” is not set, a new GUID (a.k.a ClassID) is not
created each time the DCOM Server project is compiled. If you do not
recompile the Client application after a new GUID is assigned, the DCOM
clients will break.

Use the following steps to resolve this issue:

1. Set the DCOM Server project to “Binary Compatibility.”

2. Recompile both the Server and Client application.

In the future, if you make any interface changes to your DCOM Server which
may break compatibility, the Visual Basic compiler warns you that the
component is no longer binary compatible. If you proceed to compile the
DCOM Server, thus breaking compatibility, you must recompile any client
applications which refer to that server. For more information about
compatibility see the References section below.

REFERENCES
==========

For additional information, please see the following article(s) in the
Microsoft Knowledge Base:

   ARTICLE-ID: Q161137
   TITLE     : HOWTO: Use Project and Binary Compatibility

   ARTICLE-ID: Q176799
   TITLE     : INFO: Using DCOM Config (DCOMCNFG) on Windows NT

======================================================================
Keywords          : vb5all kberrmsg
Version           : WINDOWS:5.0
Platform          : WINDOWS
Issue type        : kbhowto

=============================================================================

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.

Copyright Microsoft Corporation 1997.