Results 1 to 13 of 13
  1. #1
    Join Date
    Aug 2003
    Posts
    10

    Unanswered: strange error: -2147151472

    Hi,

    On the eventlog of the machine where our cluster is located, we get this error:

    The description for Event ID ( 1 ) in Source ( VBRuntime ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: Application CTHEJDE: Thread ID: 3612 ,Logged:
    Number: -2147151472
    Description: UpdateOrderHeader
    Source: CTHEBLC: clsProcessedOrder_T
    Module: clsEDIPicker - pProcessEDIFile().

    Anyone any idea why and how we can solve this ?

  2. #2
    Join Date
    Jun 2003
    Location
    Ohio
    Posts
    12,592
    Provided Answers: 1
    It looks like a VB generated error to me.

    blindman

  3. #3
    Join Date
    Jul 2003
    Location
    San Antonio, TX
    Posts
    3,662
    It's obvious that you are running a VB executable either directly on this machine or as a remote in-process OLE coming from another box (I think the latter is most likely). Make sure you have VB run-time library DLL present and registered on your cluster:

    - VB6 - MSVBVM60.DLL
    - VB5 - MSVBVM50.DLL

  4. #4
    Join Date
    Aug 2003
    Location
    Andover, MA
    Posts
    256
    The number is a COM exception. You are missing the VB Runtime, which your clsEDIPicker class needs to run.
    -bpd

  5. #5
    Join Date
    Aug 2003
    Posts
    10
    Thats not it, we have many other comonents on the same machine, who run without any probs, and they also use the vb runtime...

  6. #6
    Join Date
    Aug 2003
    Location
    Delft, The Netherlands (EU)
    Posts
    447
    Originally posted by azerty74
    Thats not it, we have many other comonents on the same machine, who run without any probs, and they also use the vb runtime...
    Correct, your VBRunTime is working perfect, since the log event is written by the VBRunTime.

    The error number looks like an ADO error, but I was unable to locate it on MSDN. Strange, especially because the error description is UpdateOrderHeader, which doesn't looks like a generic ADO error description. So, I would guess that this error is a user-defined error.

    I would dive into the application source of CTHEBLC: clsProcessedOrder_T, and locate the place of generating this error in the module clsEDIPicker - pProcessEDIFile(). If you don't have the source, I would report this log event to the application developer.
    Make everything as simple as possible, but not simpler! - A. Einstein
    DB Problems? DB Explorer, BTrieve Re-engineering, DB Conversions & ETL? Conversion Tool

  7. #7
    Join Date
    Aug 2003
    Location
    Andover, MA
    Posts
    256
    Sorry for my previous post. It is, however, a COM exception (you can tell by the negative number). When you throw a COM exception from VB, you are supposed to add the value vbObjectError to the error value (-2147221504), which was apparently done here.

    So, you need to subtract that from your error value to get the actual error code, which appears to be 70032. Still a user-defined error, but a bit closer to what you are looking for.

    The developer should have the error enum that details all of the error codes. If you have access to VB, you can open a blank project, create a reference to the DLL (tools/references), and open the Object Browser (F2). There should be a list of defined error codes listed under the DLL's globals section (hopefully).
    -bpd

  8. #8
    Join Date
    Jul 2003
    Posts
    18
    Are you using sp_OA procs to call your vb com object? If so, are you experiencing this problem during times of heavy load?

    I've had terrible problems using VB-based components from SQL - and we've had to rewrite them in C++ to make the problems go away...

  9. #9
    Join Date
    Aug 2003
    Location
    Andover, MA
    Posts
    256
    True. If you are calling from SQL, best to make them Extended Stored Procedures. Much more usable as well, as you can treat them like any other SP that way. We even have extended stored procs retrieving data from network devices from around the world. It really opens up a whole new level of coolness.
    -bpd

  10. #10
    Join Date
    Aug 2003
    Posts
    10

    Thumbs up

    thx everyone,
    we solved the problem.

  11. #11
    Join Date
    Aug 2003
    Location
    New Zealand
    Posts
    1
    Originally posted by azerty74
    thx everyone,
    we solved the problem.
    Please tell us how it was fixed

  12. #12
    Join Date
    Aug 2003
    Location
    Delft, The Netherlands (EU)
    Posts
    447
    Originally posted by patman
    Please tell us how it was fixed
    Yeah! How did you find the problem?!
    Make everything as simple as possible, but not simpler! - A. Einstein
    DB Problems? DB Explorer, BTrieve Re-engineering, DB Conversions & ETL? Conversion Tool

  13. #13
    Join Date
    Aug 2003
    Posts
    10
    I don't know exactly, but I believe the developpers reinstalled the vb-runtime on the machine and recompiled all components.

Posting Permissions

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