[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference rocks::dec_edi

Title:DEC/EDI
Notice:DEC/EDI V2.1 - see note 2002
Moderator:METSYS::BABER
Created:Wed Jun 06 1990
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:3150
Total number of notes:13466

3062.0. "OBB_INV_SRVPRCDIED" by NETRIX::"[email protected]" (jan-ake olsson) Wed Mar 19 1997 09:06

Hi!

Got following test message when trying to connect to DEC/EDI or by
running the network tester program on the PC:

An ObjectBroker System Exception occured.
This can arise due to incorrect configuration on 
your PC, or a problem with the DEC/EDI GUI Server:
CORBA_NO_IMPLEMENT
OBB_INV_SRVPRCDIED (e), Process '52A' no longer exist
for implementation. 
'7b83fa07cc31.02.c0.47.f9.02.00.00.00.00'.

The customer is running DEC/EDI for UNIX with Objectbroker versions
as the SPD.

The funny thing is that this things was working when i left the site
last friday after having installed the CC on several PC's. After that
the customer have taken the server down to singleuser mode for backup
and then starting up to init 3 again. They have tried to start the server
on from init 0 if there where some process not starting properly from
single user mode but it still doesn't work. 

Any ideas had been very much appreciated as I don't have the real deep
knowledge about this application.

Best regards
     Jan-Ake

[Posted by WWW Notes gateway]
T.RTitleUserPersonal
Name		DateLines
3062.1Try this...SYSTEM::POADhttp://www.digital.com/info/ediWed Mar 19 1997 10:389
    Jan-Ake,
    
    It looks like there is some confusion about which processes are trying
    to communicate across the net. I don't know if the PC has been
    re-started since the server restart, but try that. If that doesn't
    work, try stoping all the GUI IMPL ObjectBroker servers on the Server.
    If that doesn't work restart the ObjectBroker agent on the server.
    
    	Chris
3062.2Doesn't help!NETRIX::"[email protected]"jan-ake olssonThu Mar 20 1997 16:2913
Hi!

Well, we have tried out those things you mentioned but it didn't
work.

I have been loged in at the customer system this afternoon and have
discovered a couple of files in the /sbin/rc3.d directory, 
sqlbugchk.log and sqs_manage.log, which doesnt look to funny...I believe
we could have a RDB and SQL services problem as well. 

Regards
      Jan-Ake
[Posted by WWW Notes gateway]
3062.3Try re-starting SQL ServicesMETSYS::POADhttp://www.digital.com/info/ediThu Mar 20 1997 18:5015
    It's possible that SQL Services has got it's knickers in a twist.
    
    You may want to try restarting SQL Services. To do this you seem to
    need to delete the configuration file first:
    
    First I shut SQL Services down, then I do the following. Note: the
    directories may be different on your machine:
    
      > cd /usr/lib/dbs/sqs
      > rename the sqs_config_file to something else
      > cd /usr/local/sqs
      > sqs_manage -i sqs_create.sqs
      > sqs_manage -i sqs_startup.sqs
    
    		Chris
3062.4Still doesn't workNETRIX::"[email protected]"janneFri Mar 21 1997 09:5822
Hi!

I have reconfigured the sql services but it still doesn't work.

Status as now:
- EDI client to EDI server, works ok and have done so all the time.
- Command Center using Network tester:
  - Objectbroker, still the same problem, same error message as before.
  - ODBC, same error message but got TEST Succedded when accepting
    the error message.
- Objectbroker test on the server, entering the object id in the 
objectbroker tester on the PC-client, test works ok.

Where is the problem???

I would really need some urgent help on this matter. We got a partner
waiting to get to the system and work.

Regards

      Jan-Ake
[Posted by WWW Notes gateway]
3062.5METSYS::THOMPSONWed Apr 02 1997 17:206
Hi,

What's the latest on this? I've only just got back to the office.

Mar
k
3062.6Dealt withMETSYS::POADhttp://www.digital.com/info/ediWed Apr 02 1997 19:424
    I've dealt with it off-line and it has been solved. It was due to
    incorrect ObjectBroker proxies being set up.
    
    	Chris