Results 1 to 2 of 2

Thread: Big DCom Problem

  1. #1

    Thread Starter
    Lively Member satti charvak's Avatar
    Join Date
    Apr 2001
    Location
    noida, india
    Posts
    90

    Angry Big DCom Problem

    Hello Expert,

    i've written a DCOM server using
    i. vb6.0
    ii. win2000
    iii. In the dcomcnfg dialogbox i made the following settings
    a. On the general tab: Authetication level - default
    b. On the location tab: Run application on the local machine
    c. On the endpoints tab: connection level tcp/ip
    iv. On the client machine i copied the ".vbr" & ".tlb" files and
    registered them using following command

    ------------------------------------------------------------------
    CLIREG32 <PROJECT.VBR> -d -l -s <server name> -t <project.tlb>
    ------------------------------------------------------------------
    No error\message was reported while registering.

    v. The registry on the client as well as the server machine is
    showing the entry of the DCOM Server by name as well as by
    CLASS ID
    vi. On the client computer i created a standard EXE project and
    created the instance of the DCOM Server using 'createobject'
    statement.
    vii. ERROR MESSAGE ----
    ------------------------------------------------------------------
    "RUN TIME ERROR 429: ACTIVEX COMPONENT CAN'T CREATE OBJECT"
    ------------------------------------------------------------------

  2. #2
    Fanatic Member
    Join Date
    Jan 2001
    Location
    Vietnam
    Posts
    613
    RUN TIME ERROR 429: ACTIVEX COMPONENT CAN'T CREATE OBJECT
    If you encounter this error, it usually means that the object is not installed or registered correctly, either on the client system, the server or both. It is probable that at one point during the development process the DCOM component worked perfectly, but when the component was moved to the production environment, it stopped worked. The first thing you should do is to make sure that the component installed on the test server is the same one as on the production server. The way to do this is by scanning the Registry on both systems for the component's GUID. If the component is installed on the system but there isn't a Registry entry, then simply reregister the component. To do this, use the REGSVR32.EXE

    Regards,
    TheBao

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width