Skip to Content
author's profile photo
Former Member

SBOAddonReg.dll

Does the SBOAddonReg.dll has any dependencies? I always get an "Could not load SBOAddonReg.dll" error, when i want to install my addon with installshield. This also happens when i want to install the screenpainter software. 😔

Regards

Clemens

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

2 Answers

  • Best Answer
    author's profile photo
    Former Member
    Jul 29, 2004 at 08:08 AM

    Hi Clemens:

    Regarding to your installation problem of Screen Painter, you need to install SBO SDK 6.5 first. The dll SBOAddonReg.dll is included in it. After you install it, you can install Screen Painter successfully!

    Best Regards,

    Nicky He

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Clemens,

      thinking about it, we did have the same problem on machines which had a previous installation of a 6.2 client on them.

      Registration works fine with a 6.5 client installation on a SAP clean system.

      Maybe that can help somehow.

      In a lot of cases formatting your hard drive will solve those problems. It is just so totally inconvenient. Maybe this is a dll conflict.

      HTH Lutz Morrien

  • author's profile photo
    Former Member
    Jul 25, 2004 at 10:24 AM

    Hi,

    As a part of <b>microsoft tools</b> you can find "<b>Depends</b>"

    a tool that will show you what DLLs does the SBOAddonReg.dll have reference to.

    it is all win32 DLLs - since the SBOAddonReg.dll only add a couple of entries to the registry and handles SAP Business One folders.

    regards,

    Yaniv G.

    SDK Consultant,

    SPA Manage Israel

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Thanks for the info with depends! When i run depends.exe to analyze sboaddonreg.dll it finds a dll called mpr.dll with the message : Warning: At least one module has an unresolved import due to a missing export function in a delay-load dependent module.

      What does that mean????

      Regards

      Clemens