Conference pamsrc::objectbroker_dtc

23.0. "miss behaving ObjectExplorer" by EMNTAL::STADELMANN (Sepp @ZUO 760-2609) Thu Feb 13 1997 09:29

    Bug No. 1
    
    Windows 95 (service Pack 2)
    
    When I toke the task manager to stop xole, a window pop's up and asked
    me to save xole1.xo. I was friendly and did allow to save, even not
    knowing what xole1.xo is all about. Then the task manager window come
    up twice within 40 seconds indicating that the shutdown of this
    xole.exe cant happen and I have still to wait. 
    
    I toggeled waiting for another 20 seconds and then the next time I used
    the stop button. 
    
    This enforced my windows 95 to shutwdown. Not very nice indeed.
    
    Bug No. 2
    
    After restarting Windows 95 I went straigth to the just saved
    Xole1.xo and did a doubble click on it.
    
    The ObjectBroker OLE Agent Server Main Window pops up and immeditately
    an error message Box as well.
    
    Microsoft Visual C++ Debug Library
    Debug Assertion Failed!
    
    Program: E:\ORB\BIN\XOLE.EXE
    File: XoleDocument.cpp
    Line: 2235
    
    For more information on how your program can cause an assertion
    failure, see the Visual C++ documentation on asserts.
    
    Press Retry to debug  the application
    <ABORT>
    
    gest me another error mess, again abort stops the ObjectBroker Agent
    Server.
    
    Bug No. 3
    
    I launched now the ObjectExplorer, it launches Dirsrvm and obbnamsrv
    and the ObjectBroker OLE Agent Server (at least thats what task manager
    shows.
    
    I went down to \ObjectBroker\Advertisements\ and doubbleclikced on
    CheckAccount Object
    
    Now it takes a while (because I have rebooted due to the shutdown
    before) (my bank11s.exe is not yet running) when an error message box
    pop's up
    
    ObjectBroker OLE Agent Server
    Dispatch Invoke Failed
    ObjectBroker Object SystemException: minor code [76263730][maybe]
    Source. DIBANK_Account.acctType
    Status Code: 80020006
    <OK>
    
    ObjectBroker OLE Agent Server
    Dispatch Invoke Failed
    ObjectBroker Object SystemException: minor code [76263730][maybe]
    Source. DIBANK_Account.balance
    Status Code: 80020006
    <OK>
    
    ObjectBroker OLE Agent Server - CheckAccount comes up with a
    CheckAccont Window synthesized but it's Type and Balance is Undefined.
    
    What is all wrong behind my operatio?
    
    What do I have to do before I can doubble cklick on an Object in the
    Advertisemtn name space ?
    
    Then I doubble cklicked bank11s.exe, the server starts OK.
    
    In ObjectBroker OLE Agent Server i played arround with the pull down
    window on the tool bar and selected alternatively between *Bank11Demo
    andSynthesized. The synthesized CheckAccount Window changed its content
    but also after some switched for an back; o wonder why, bank11s.exe
    terminated.
    
    I shut down the synthesized CheckAccount Window and tryed to reopen it.
    After some 20 seconds
    
    ObjectBroker OLE Agent Server
    Unable to open the metadata library e:\orb\data\Transformation
    Agent\xole.mlb
    status = 80030021
    <OK>
    
    ObjectBroker OLE Agent Server
    Unable to open the metadata library e:\orb\data\Transformation
    Agent\xole.ilb
    status = 80030021
    <OK>
    
    ObjectBroker OLE Agent Server
    XoleQuickKey file cannot be opened
    Error code: b
    <OK>
    
    ObjectBroker OLE Agent Server
    Unable to hash a unique key for this instance
    The Oref for this instance appears to be the same as another
    <OK>
    
    .... same as another ....
    
    ObjectBroker OLE Agent Server
    Failed to get instance UUID for this object
    <OK>
    
    now I am through, back to work with the miss behaving ObjectExplorer
    
    The next cklick in ObjectExplorer 
    
    Server Busy
    
    This acction cannot be completetd because the other programm is b usy.
    Click the appropriate button on the task bar to activate the busy
    program and correct the problem.
    
    <retry> does bring me back the same as soon as I just want to move
    ObjectExplorer
    
    In the Task Manager I have now a second Xole Application
    
    I am using now the task manager to stop ObjectExplorer 
    
    and so on 
    
    
    Sepp,
    
    
    
    
    
    Sepp

    Okay here's my cut at this...
    
    The agent server shouldn't have asked you to save your DocView to
    Xole1.xo.  I'm not sure why it did, but I will ptr this problem so
    that we can track it.  
    
    Without the .xo file you wouldn't have hit the assertion.  There is a
    way to create an .xo file though using the file/shortcut option,
    that should work although there is a bug with the naming of the
    resulting doc view.
    
    When you then create an agent without the bank11s server running,
    the agent will display errors when it tries to access the
    attributes of this bank account.  I agree this is not the nicest
    way to find out though. I have ptr'ed this one to have the server
    provide a simple message that the server is down and not to access
    it again until an refresh is called for.
    
    THe open metadata lib errors were because another xole.exe server
    was running and had the metadata library open.  For now, run only
    one server at a time.  If a server gets hung, stop it before
    starting another.
    
    bob

    Thanks for the answer,
    
    Howerver I have 3 Bugs (in my mind) reported in .0 
    
    Sepp,

    Bug 2 was a result of activating the .xo file created when you stopped
    the server on win95.  The file created is probably corrupt.  When we
    fix bug 1 hopefully that will prevent you from getting to bug 2. 
    
    bob

    Thank you bob, 
    
    I will further use and test the DTC product. If you have someting
    better just let me know. If I would understand more of the architecture
    and design I could track down more easy and give more usefule input.
    It's difficult sometimes to say what precises steps you did and in
    which order if the fault happens close to the end of a session.
    
    
    Sepp,