Results 1 to 4 of 4

Thread: Error 429 on propertybag

  1. #1

    Thread Starter
    Addicted Member
    Join Date
    Mar 2009

    Error 429 on propertybag


    A client of us gets an error "429: activeX component can't create object", I narrowed it down to the following line:

    Set pb = New PropertyBag

    full code of the function, which is part of a class clsDatabaseImage (which stores the image as a propertybag into the database):
    Public Function ReadRecord(ByRef rs As Recordset) As Boolean
      Dim abBuffer()  As Byte
      Dim PB          As PropertyBag  
      ReadRecord = False
    On Error GoTo ErrorHandling
      If Not rs.EOF Then
        With rs
          property_lImageID = fn_FieldAsLong(.Fields!ImageID)
          property_sDescription = fn_FieldAsString(.Fields!Description)
          property_sOriginalFilename = fn_FieldAsString(.Fields!OriginalFilename)
          If IsNull(rs.Fields!ImageData) Then
            Set property_picPicture = Nothing
            abBuffer() = rs.Fields!ImageData
            Set PB = New PropertyBag
            PB.Contents = abBuffer()
            Set property_picPicture = PB.ReadProperty(csPropertyBagNameImageData)
            Set PB = Nothing
          End If
        End With 'With rs
        ReadRecord = True
      End If
      Exit Function
      Call ClearValue
      Err.Raise csErr_ReadRecord, "clsDatabaseImage.ReadRecord", csErr_MessageReadRecordset & vbCrLf & _
                                                                 " ImageID=" & property_lImageID & vbCrLf & _
                                                                  "Error " & Err.Number & " : " & Err.Description
    End Function
    Some info on the system of the client:

    OS                                Windows Server 2008 R2 v6.1.3505 Service Pack 1
    Terminal server              Yes
    Architecture processor    Intel
    Type processor              Intel(R) Xeon(R) CPU           E5645  @ 2.40GHz  (8 procs)
                                        Intel64 Family 6 Model 44 Stepping 2
    ------ Systeem versions ------
    JetEngine     v3.51                                             
    comctl32.dll  v5.82.7601.18837    Axxxx          530.432 bytes  C:\Windows\SysWOW64\
    comdlg32.dll  v6.1.7601.17514     Axxxx          485.888 bytes  C:\Windows\SysWOW64\
    gdi32.dll     v6.1.7601.23591     Axxxx          312.832 bytes  C:\Windows\SysWOW64\
    kernel32.dll  v6.1.7601.23572     Axxxx        1.114.112 bytes  C:\Windows\SysWOW64\
    ole32.dll     v6.1.7601.19131     Axxxx        1.413.632 bytes  C:\Windows\SysWOW64\
    oleaut32.dll  v6.1.7601.23569     Axxxx          581.632 bytes  C:\Windows\SysWOW64\
    shell32.dll   v6.1.7601.18952     Axxxx       12.875.776 bytes  C:\Windows\SysWOW64\
    user32.dll    v6.1.7601.23594     Axxxx          833.024 bytes  C:\Windows\SysWOW64\
    version.dll   v6.1.7600.16385     Axxxx           21.504 bytes  C:\Windows\SysWOW64\
    wininet.dll   v11.0.9600.18538    Axxxx        2.444.800 bytes  C:\Windows\SysWOW64\
    winspool.drv  v6.1.7601.17514     Axxxx          320.000 bytes  C:\Windows\SysWOW64\
    wsock32.dll   v6.1.7600.16385     Axxxx           15.360 bytes  C:\Windows\SysWOW64\
    msvbvm60.dll  v6.0.98.15          Axxxx        1.386.496 bytes  C:\Windows\SysWOW64\
    stdole2.tlb   v6.1.7600.16385     Axxxx           16.896 bytes  C:\Windows\SysWOW64\
    olepro32.dll  v6.1.7601.23452     Axxxx           90.624 bytes  C:\Windows\SysWOW64\
    asycfilt.dll  v6.1.7601.23569     Axxxx           67.584 bytes  C:\Windows\SysWOW64\
    comcat.dll    v6.1.7600.16385     Axxxx            7.168 bytes  C:\Windows\SysWOW64\
    dbgrid32.ocx  v5.1.45.25          Axxxx          520.192 bytes  C:\Windows\SysWOW64\
    mscomctl.ocx  v6.1.98.46          Axxxx        1.070.232 bytes  C:\Windows\SysWOW64\
    mscomct2.ocx  v6.1.98.12          Axxxx          656.200 bytes  C:\Windows\SysWOW64\
    msinet.ocx    v6.1.97.82          Axxxx          132.880 bytes  C:\Windows\SysWOW64\
    ------ References & Objects versies ------
    {00020430-0000-0000-C000-000000000046}#2.0#0  v6.1.7600.16385     Axxxx           16.896 bytes  C:\Windows\SysWOW64\stdole2.tlb
    {00025E01-0000-0000-C000-000000000046}#4.0#0  v3.51.1608.0        Axxxx          570.128 bytes  C:\Program Files (x86)\Common Files\Microsoft Shared\DAO\DAO350.DLL
    {3050F1C5-98B5-11CF-BB82-00AA00BDCE0B}#4.0#0  v11.0.9600.18538    Axxxx        2.724.864 bytes  C:\Windows\SysWOW64\mshtml.tlb
    {F5078F18-C551-11D3-89B9-0000F81FE221}#6.0#0  v6.30.7601.18980    Axxxx        1.391.104 bytes  C:\Windows\System32\msxml6.dll
    {48E59290-9880-11CF-9754-00AA00C00908}#1.0#0  v6.1.97.82          Axxxx          132.880 bytes  C:\Windows\SysWow64\MSINET.OCX
    {EAB22AC0-30C1-11CF-A7EB-0000C05BAE0B}#1.1#0  v11.0.9600.18538    Axxxx       13.653.504 bytes  C:\Windows\SysWOW64\ieframe.dll
    {831FDD16-0C5C-11D2-A9FC-0000F8754DA1}#2.1#0  NOT FOUND
    {86CF1D34-0C5F-11D2-A9FC-0000F8754DA1}#2.0#0  v6.1.98.12          Axxxx          656.200 bytes  C:\Windows\SysWow64\MSCOMCT2.OCX
    {00028C01-0000-0000-0000-000000000046}#1.0#0  v5.1.45.25          Axxxx          520.192 bytes  C:\WINDOWS\SysWow64\DBGRID32.OCX
    Any idea what can cause this?

  2. #2
    Join Date
    Feb 2006

    Re: Error 429 on propertybag

    The PropertyBag class is defined in type library C:\Windows\System32\msvbvm60.dll\3. Without the VB6 runtime you wouldn't even get this far. It is possible that the typelib registration is corrupt on the failing machine. There are a lot of dubious setups floating around that tend to break things. Often these are based on rickety 3rd party legacy scripted setup technologies where things can go very wrong if the hand-crafted scripts they rely upon are off just a little bit.

    It seems more likely that you have the wrong line of code.

  3. #3
    Frenzied Member
    Join Date
    Aug 2010

    Re: Error 429 on propertybag

    This is a long shot (maybe even impossible if you can't out-scope the intrinsic classes - I've never tried) but perhaps you have a another class named PropertyBag that can't be created from a different unregistered component? What happens if you declare all of your PropertyBag references as VBRUN.PropertyBag instead?

  4. #4
    Join Date
    Feb 2006

    Re: Error 429 on propertybag

    Seems unlikely since it works on other machines.

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