cancel
Showing results for 
Search instead for 
Did you mean: 

DTR Open Conflicts Not shown up in NWDS

Former Member
0 Kudos

Hi All,

We recently upgraded our ESS track from SAP_ESS 600 Component to SAP_ESS 603 SP05. We went into our NWDS resolved all the conflicts released the activities and in the consolidation imported successfully. When we try to assemble the components the Check assembly directly failed. Below is the error details

20100901010112 Info :Starting Step Check-assembly at 2010-09-01 01:01:12.0405 -4:00

20100901010112 Info :Checks for software component sap.com,SAP_ESS are performed now:

20100901010117 Info :60040DTR conflicts

20100901010117 Fatal :There are unresolved collisions, stopping export now

20100901010117 Info :Checks for software component sap.com,SAP_ESS finished succesfully

20100901010117 Info :Step Check-assembly ended with result 'fatal error' ,stopping execution at 2010-09-01 01:01:17.0658 -4:00

Looking at the DTR Conflicts its really huge. When we go into our NWDS we do not see any of these conflicts comin up. The once that came are resolved and the dev is complete. Now at this stage when moving to Q we face this issue.

Why is the DTR and NWDS Conflicts not synced up? Am I missing something else here?

Thanks,

Nagarajan.

umarsyed
Discoverer
0 Kudos

The error message "java.net.SocketTimeoutException: Read timed out" indicates that the NWDS was unable to read data from the socket within the specified timeout period. This can be caused by a number of factors, such as a slow connection, a problem with the network, or an issue with the SAP system itself.

To troubleshoot this issue, you can try the following:

  1. Check the connectivity to the SAP system. Make sure that the NWDS is able to establish a connection to the SAP system and that there are no network issues.

  2. Check the log files located in the "Logs" folder of the NWDS installation directory for any errors or warning messages that might provide more information about the cause of the problem.

  3. Check with your SAP administrator to see if there are any issues with the SAP system or the NWDS configuration that might be causing the problem.

Note : Links provided are not working @Ervin Szolke can you please share updated info if possible.

Accepted Solutions (0)

Answers (1)

Answers (1)

ErvinSzolke
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi,

I believe this is due to the difference between integration and check-in conflicts, see the documents:

Check-in conflicts:

http://help.sap.com/saphelp_nw70/helpdata/EN/8e/aa42f6c5d5fa4e994309cc5384f784/frameset.htm

Integration conflicts:

http://help.sap.com/saphelp_nw70/helpdata/EN/a5/32036a40750149a8660987784815b1/frameset.htm

Conflict Resolution – How to Analyze, Handle, and Avoid Integration Conflicts:

http://scn.sap.com/docs/DOC-1178

The prerequisite of assembly is: no conflicts, broken DCs. As soon as you resolve them the assembly will work (or at least you'll see a different error)

Best Regards,

Ervin  (http://wiki.sdn.sap.com/wiki/display/TechTSG/%28NWDI%29Home)