I would also check any workflow you have that might be sending the data from the dso form to other forms. Turn on filter logging on the destination server.
-----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Grooms, Frederick W Sent: Monday, January 07, 2013 6:46 AM To: [email protected] Subject: Re: DSO - not starting on an upgraded server The FieldID error makes me think one of the DSO forms is incorrect. Since you have never used them on the server go ahead and delete them and re-load them The default forms should be located in the "{Install Directory}/systemforms/en" directory DistributedLogicalMapping.def DistributedMapping.def DistributedPending.def DistributedPool.def Fred -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Dave Barber Sent: Monday, January 07, 2013 8:36 AM To: [email protected] Subject: DSO - not starting on an upgraded server ** All, I have just upgraded one of our test environments, from 7.0.1 patch 012 to 7.6.04 patch 004 - applications seem to be running fine, and for the most part external application interfaces seem to be working fine. The exception is DSO - which we have never had to use on this specific box before today, but it will be required for end to end testing prior to upgrading the live system to 7.6.04. FYI, the box is running Solaris 10, database is Oracle 10g (R2 iirc), running java version 1.5.something. All server components are licensed. When you restart the services, you get the following log entries : DSO.LOG : <DIST> Distributed Server Trace Log -- ON (AR Distributed Server 7.6.04 SP4 201209051922) (Fri Jan 04 2013 11:48:17.4774) <DIST> Initializing access to the AR System server <DIST> Locating mapping and pending forms <DIST> Mapping form -- Distributed Mapping <DIST> Pending form -- Distributed Pending <DIST> Distributed Pool form -- Distributed Pool <DIST> Pending Errors form -- Distributed Pending Errors <DIST> Distributed Server Logical Mapping Form -- Distributed Logical Mapping <DIST> Distributed Server Thread Manager Started. (Fri Jan 04 2013 11:48:19.8486) <DIST> If signal is 15: "AR System Distributed Server terminated by user or accidentally." (ARDSNOTE 3000) <DIST> 11 (Fri Jan 04 2013 11:48:24.8640) <DIST> ** ERROR ** AR System Distributed Server terminated -- fatal error encountered (ARDSERR 3001) <DIST> Distributed Server Trace Log -- OFF (Fri Jan 04 2013 11:48:24.8669) ARERROR.LOG : Fri Jan 4 11:48:09 2013 11 Fri Jan 4 11:48:09 2013 Distrib : AR System Distributed Server terminated -- fatal error encountered (ARDSERR 3001) Fri Jan 4 11:48:12 2013 Distrib : Field ID specified does not exist in this form (ARWARN 51) Fri Jan 4 11:48:12 2013 Distrib : Field ID specified does not exist in this form (ARWARN 51) Fri Jan 4 11:48:17 2013 Distrib : If signal is 15: "AR System Distributed Server terminated by user or accidentally." (ARDSNOTE 3000) Signal 11 is a segmentation fault? So possibly some issue with resources, memory? The machine has 64gig ram, although that is shared as the server is 1 of 5 zones on a big bit of Sun kit. Any suggestions? Ta :) Dave Barber _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
