# NEIMW241 0250 NAT6296 Fatal error in the communication. **URL:** \ **Category:** Forum\ **Tags:** Adabas-Natural, Natural, NaturalONE, NaturalONE-Full-Edition\ **Created:** [January 11, 2012, 5:46pm UTC](https://techcommunity.softwareag.com/t/neimw241-0250-nat6296-fatal-error-in-the-communication/99459 "2012-01-11T17:46:59Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Alan3](https://avatars.discourse-cdn.com/v4/letter/a/57b2e6/32.png) [@Alan3](https://techcommunity.softwareag.com/u/Alan3)\ **Post date:** [January 11, 2012, 5:46pm UTC](https://techcommunity.softwareag.com/t/neimw241-0250-nat6296-fatal-error-in-the-communication/99459/1 "2012-01-11T17:46:59Z")
Our UNIX admin has created a new Natural environment called CISNDV on a HP-UX machine with the components listed below. I have installed the NaturalONE components on a Virtual XP instance running in Win7. In NaturalONE, I mapped a Natural Server to the new CISNDV Natural environment on HP-UX. I can edit, cat, and stow through NaturalONE and see the changes saved in the CISNDV Natural environment on HP-UX. Here is what I have encountered so far: 1) On the HP-UX file system, the Natural source is showing the owner as SAG. I would expect it to use my ID as it does when I edit a Natural object through the Natural editor in our development environment. Is there a setting I need to change for the CISNDV environment? 2) When I’m in Natural editor in the CISNDV, I get the “NAT6296 Fatal error in the communication” message when I try to edit a Natural object. Is this an install issue? 3) While using the IDL Extractor for Natural in the EntireX perspective in NaturalONE, I get "“Broker Error 0013 0313: Send/receive failed for HPI1:8601 (java.io.EOFException)” when defining the RPC environment. If anyone can help with any of these issues, I would greatly appreciate it. Thanks. Alan Installed on Virtual XP running on Win7 machine: - NaturalONE 8.1.5.v00018658 - Natural for Eclipse 8.1.5.v00018658 - Service Development 8.1.5.v00006907 - EntireX Workbench 8.1.3.0000-0254 - Natural Engineer 8.1.2.v20100602\_0001 - Web Services Stack 8.0.5.0000-146 - Java 6 Update 30 Installed on HP-UX B.11.31 - Tomcat 8.0 - System Management Hub 8.1.2.177 - Natural Development Server - Natural WEB I/O - Entire Screen Builder - EntireX 8.1 SP1 - Natural v 6.3.8 PL 0 - Entire Access for TCP/IP Installed on LINUX - Oracle 11G ---
**Author:** ![Alan3](https://avatars.discourse-cdn.com/v4/letter/a/57b2e6/32.png) [@Alan3](https://techcommunity.softwareag.com/u/Alan3)\ **Post date:** [January 11, 2012, 8:40pm UTC](https://techcommunity.softwareag.com/t/neimw241-0250-nat6296-fatal-error-in-the-communication/99459/2 "2012-01-11T20:40:28Z")
Issue #2 is fixed. 1. When I’m in Natural editor in the CISNDV, I get the “NAT6296 Fatal error in the communication” message when I try to edit a Natural object. Is this an install issue? Our UNIX admin corrected a setting with Entire Screen Builder and Natural on the UNIX box. I am now able to edit a Natural object through the Natural editor. I’ll try to get more information as to what setting was corrected and post it later. ---
**Author:** ![Alan3](https://avatars.discourse-cdn.com/v4/letter/a/57b2e6/32.png) [@Alan3](https://techcommunity.softwareag.com/u/Alan3)\ **Post date:** [January 11, 2012, 8:50pm UTC](https://techcommunity.softwareag.com/t/neimw241-0250-nat6296-fatal-error-in-the-communication/99459/3 "2012-01-11T20:50:05Z")
Issue #3 was a user error on my part. 1. While using the IDL Extractor for Natural in the EntireX perspective in NaturalONE, I get "“Broker Error 0013 0313: Send/receive failed for HPI1:8601 (java.io.EOFException)” when defining the RPC environment. I was using the host name and port for Tomcat. Once I entered the actual Broker ID, I was able to create the RPC environment and create the IDL file. ---
**Author:** ![Alan3](https://avatars.discourse-cdn.com/v4/letter/a/57b2e6/32.png) [@Alan3](https://techcommunity.softwareag.com/u/Alan3)\ **Post date:** [January 11, 2012, 8:51pm UTC](https://techcommunity.softwareag.com/t/neimw241-0250-nat6296-fatal-error-in-the-communication/99459/4 "2012-01-11T20:51:40Z")
Here is the information our UNIX admin used to resolve Issue #2: Since we are now using Entire Screen Builder, we must create a separate Natural nucleus and call it “natnsw”. Here is the procedure we use to build both Natural nuclei and move them into place: $ cd $NATDIR/$NATVERS/bin/build $ unset LD\_PRELOAD $ make natural osx=yes ada=yes rpc=63 $ make install $ make clean $ make natural osx=yes ada=yes rpc=63 nsw=yes $ mv natural natnsw $ cp –p natnsw … $ rm natnsw $ cd … $ chmod 775 natnsw ---
**Author:** ![system](https://global.discourse-cdn.com/techcommunity/original/3X/c/d/cd19967bb605d28a72d77eb83a1cae22f3df2eb8.svg) [@system](https://techcommunity.softwareag.com/u/system)\ **Post date:** [April 2, 2021, 3:01pm UTC](https://techcommunity.softwareag.com/t/neimw241-0250-nat6296-fatal-error-in-the-communication/99459/5 "2021-04-02T15:01:26Z")