[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

3093.0. "error reading DECEDI$SRV_CONFIGURATION.DAT" by EDITEX::16.81.112.24::Stoddart (EDI Expertise Center) Wed Apr 09 1997 21:31

Hi all,

	Me again, guess it's just my week.

	We are getting a strange error in the error log:
%DECEDI-E-NOREADSCF, error reading file DECEDI$SRV_CONFIGURATION.DAT
-DECEDI-W-COMMSERSCF, error reading connection record
-DECEDI-I-EPARTNSER, connection id = IMPEXP
-DECEDI-I-CONDLOGGED, condition logged by OBB_27800910 on node EDITEX:: 
at.....

	It's happening on every connection id.  The sympton is a server 
error when you try a trade command.

	Any ideas?

	
Lorey

P.S.  I saw this at a customer site a few weeks back.  I rebuit the file 
using the fdl, I deleted and re-enetered the connection record to no avail. 
 We were in the process of moving to another system, so I never followed up 
on it.

DEC/EDI 2.1C
VAX
VMS 6.1

T.RTitleUserPersonal
Name
DateLines
3093.1more infoCSC32::R_GOLLEHONThu Apr 10 1997 20:169
    Lorey,
    
    Did this just start happening, or does its occurrence coincide with an
    upgrade or patch install?  It is being logged by an OBB process...is
    the error being reported when you are trying to use the translation
    bypass facility via the trade command?  Do connections appear to be
    working otherwise?
    
    -Roberet
3093.2METSYS::THOMPSONFri Apr 11 1997 23:418
Hi,

If this is still on EDITEX I'll log in and have a look.
Mail me access details!

cheers

Mark
3093.3Back againEDITEX::tunsrv-remote.alf.dec.com::stoddartEDI Expertise CenterWed Jun 04 1997 22:3142
Well, it is happening again at a customer site.  There have been no 
upgrades, and I am trying to use bypass.

Here's what's in the error log:
%DECEDI-W-SRVCALLTMO, request sent to remote data server timed out
-DECEDI-I-CONDLOGGED, condition logged by OBB_0000013E on node VPUP2:: at  
4-JUN-1997 09:42:01.07

%DECEDI-W-SRVCALLTMO, request sent to remote data server timed out
-DECEDI-I-CONDLOGGED, condition logged by OBB_0000013E on node VPUP2:: at  
4-JUN-1997 09:43:01.16

%DECEDI-W-SRVCALLTMO, request sent to remote data server timed out
-DECEDI-I-CONDLOGGED, condition logged by OBB_0000013E on node VPUP2:: at  
4-JUN-1997 09:44:01.25

%DECEDI-W-SRVCALLTMO, request sent to remote data server timed out
-DECEDI-I-CONDLOGGED, condition logged by OBB_0000013E on node VPUP2:: at  
4-JUN-1997 09:45:01.33

%DECEDI-E-SRVCALLTMOMAX, maximum number of timeouts reached
-DECEDI-I-CONDLOGGED, condition logged by OBB_0000013E on node VPUP2:: at  
4-JUN-1997 09:46:01.51

%DECEDI-E-NOREADSCF, error reading file DECEDI$SRV_CONFIGURATION.DAT
-DECEDI-W-COMMSERSCF, error reading connection record
-DECEDI-I-EPARTNSER, connection id = P_ASAP
-DECEDI-I-CONDLOGGED, condition logged by OBB_0000013E on node VPUP2:: at  
4-JUN-1997 09:46:01.61

Here is the log from DCL:
$  trade post coreapp edi$page_data:asap_transmission.dat/type=transmission 
-
        /tracking_reference="ASAP"/link_id=P_ASAP
%DECEDI-E-SRVERROR, Server Error
%DECEDI-E-SRVERROR, Server Error

This is a re-occuring problem.  ANy ideas on what it is?  If I kill the OBB 
process and re-issue the trade command, it works.  Can these processes time 
out of something after a long period of time?

Lorey
3093.4No ideaSYSTEM::HELLIARhttp://samedi.reo.dec.com/Thu Jun 05 1997 14:429
    Lorey,
    
    It looks like the processes 'loose' their link to the Data Server. Why
    I have no idea? Although first suspect would be the Data Server's
    periodic house keeping activities.
    
    IPMT it.
    
    Graham
3093.5Wil log callEDITEX::tunsrv-remote.alf.dec.com::stoddartEDI ConsultantThu Jun 05 1997 17:464
Graham,
	Will do.

Lorey