<!DOCTYPE html
  PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">

<!--
Copyright (c) 2006 UGS Corp.

All Rights Reserved.

This software and related documentation are proprietary to UGS Corp.
-->
<html>
   <head>
      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
      <title>Troubleshooting</title>
      <script language="javaScript">
        abridged="false";
        displayConditions=new Array();
      </script>
      <link type="text/css" href="../css/main_styles.css" rel="stylesheet">
   </head>
   <body class="bodydocs" onload="top.pageLoader()" bgcolor="#FFFFFF">
      <div class="title_topic1" id="xps10_pagetitle">Troubleshooting</div>
      <hr noshade="true">
      <table cellspacing="4" align="center">
         <tr valign="top">
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1">
               <p class="para_td"><a class="links" href="javascript:void(0)" onclick="top.openFile('ugcollaborate/introduction.html');return(false);">Overview</a></p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1">
               <p class="para_td"><a class="links" href="javascript:void(0)" onclick="top.openFile('ugcollaborate/getting_started.html');return(false);">How To</a></p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1">
               <p class="para_td"><a class="links" href="javascript:void(0)" onclick="top.openFile('ugcollaborate/parts_coll_functions.html');return(false);">Options</a></p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1">
               <p class="para_td">Related Topics</p>
            </td>
         </tr>
      </table><br><div class="title_division">What is the course of action when Collaborate just does not appear to be working correctly?</div>
      <p class="para_division">First, make sure everything is set up properly. This includes:</p>
      <ul>
         <li>
            <p class="para_item">Check to make sure everyone has entered the Teamcenter Community CAD conference. You can use the <b class="uiTerm">Conference Manager</b> dialog box to determine which members are presents (see  <a class="links" href="javascript:void(0)" onclick="top.openFile('ugcollaborate/conf_manage.html');return(false);">Conference Management</a>).
            </p>
         </li>
         <li>
            <p class="para_item">Check to make sure everyone has connected to Teamcenter Community. Each participant should have the Collaborate toolbars active if they have connected to the conference. You can also have everyone look at their <b class="uiTerm">Tools&rarr;Collaborate</b> menu. Only <b class="uiTerm">Disconnect from Conference</b> is active if they have previously connected to a conference manager.
            </p>
         </li>
         <li>
            <p class="para_item">Check the <b class="uiTerm">PIC</b> list to ensure that everyone has the right parts opened, and that the proper parts are being collaborated. You might have to use <b class="uiTerm">Part Name Map</b> if they have named their (similar) parts differently.
            </p>
         </li>
      </ul>
      <p class="para_division">Second, if everything appears to be set up correctly, the least onerous set of actions are:</p>
      <ul>
         <li>
            <p class="para_item">Disconnect NX from the conference. Use <b class="uiTerm">Tools&rarr;Collaborate&rarr;Disconnect from Conference</b> to disconnect and then reconnect using <b class="uiTerm">Tools&rarr;Collaborate&rarr;Connect to Teamcenter Community</b>.
            </p>
         </li>
         <li>
            <p class="para_item">Exit from the conference manager. <em>Leave</em> the conference in the <b class="uiTerm">Conference Manager</b> dialog box and rejoin the conference, then reconnect to Teamcenter Community.
            </p>
         </li>
         <li>
            <p class="para_item">Exit the Collaborate session. Make sure you save any part files that have changes you don't want to lose. Restart Collaborate and reconnect to the conference (<b class="uiTerm">Tools&rarr;Collaborate&rarr;Connect to Teamcenter Community</b>).
            </p>
         </li>
         <li>
            <p class="para_item">Restart the conference and Collaborate.</p>
         </li>
      </ul>
      <div class="title_division">How do I know if a long part transfer hangs and if it does what is the best way to recover?</div>
      <p class="para_division">The progress meter is the best way to detect if the part send has run into a problem. If you don't see any progress for a period of time and you want to stop the operation, use the <b class="uiTerm">Cancel Transfer</b> button on the progress meter. This will stop the part send operation.
      </p>
      <p class="para_division">If the Collaborate session is not responding at all, you will have to use the <b class="uiTerm">Task Manager</b> to stop the process. Since this is fairly extreme and you will lose all of your unsaved modifications, make sure the process aborts before stopping it. It is probably wise to restart the conference in these situations, even though you can just restart Collaborate and reconnect to the conference. If there was a problem in the conference manager that is causing Collaborate to abort, not ending the conference could result in the same problem reappearing immediately.
      </p>
      <div class="title_division">How do I know if I properly communicate my changes to everyone in the meeting?</div>
      <p class="para_division">There are a several ways to ensure that your changes are received and their impact understood. </p>
      <ul>
         <li>
            <p class="para_item">First, because you are in a collaboration session you will be able to simply ask the participants if they saw the change you sent. </p>
         </li>
         <li>
            <p class="para_item">Second, Teamcenter Community has an application sharing conference that you can use to show your screen to participants or their display to you. This would let you see the impact of your changes on their model as it happens. Of course, application sharing does consume network bandwidth, so you need to take care not to overload your network capacity. </p>
         </li>
      </ul>
      <div class="title_division">What if I receive one of these dialog boxes?</div>
      <p align="center"><img align="bottom" src="graphics/partsend_cancel.gif"></p>
      <p class="para_division">Cause: For some reason the part send operation received a message from the noted receiving system indicating the file transfer process did not complete successfully.</p>
      <p class="para_division">Action: Ask the receiver what message they received, as they will also receive an error dialog box.</p>
      <p align="center"><img align="bottom" src="graphics/file_transfer.gif"></p>
      <p class="para_division">Cause: Collaboratecould not create a copy of the sent part. Most likely this is due to the FTP folder being set to a directory that does not exist or you do not have write access to.</p>
      <p class="para_division">Action: Ensure $UGII_TMP_DIR exists and is writable. This error is unlikely as NX itself has this same requirement.</p>
      <p align="center"><img align="bottom" src="graphics/416_image1.gif"></p>
      <p class="para_division">Cause: A component of an assembly transfers, but it is not a version of the part used by the receiver. The part load failed. This can happen when part names are the same for different parts when using <b class="uiTerm">Part Name Mapping</b>.
      </p>
      <table border="0">
         <tr>
            <td valign="top" align="left"><img align="left" src="../graphics/note.gif" alt="Note" title="Note"></td>
            <td valign="bottom" align="left" width="100%">
               <div class="para_note">
                  <p class="para_note_body">Part versions only check for components of an assembly. Parts that are loaded outside of an assembly with the same name will simply replace the existing part version. Other file loading error messages also appear in this dialog box. </p>
               </div>
            </td>
         </tr>
      </table>
      <p class="para_division">Action:&nbsp;If due to <b class="uiTerm">Part Name Mapping</b>, unmap the part names to prevent a conflict. The receiver can create a new component with the same name if necessary, and have the file transferred again. For other errors, take action according to the error message.
      </p>
      <p class="para_division"> <img align="bottom" src="graphics/416_image2.gif" border="0">      
      </p>
      <p class="para_division">Cause: The receiver failed to load the transferred part. The sender receives notification of the part load failure.</p>
      <p class="para_division">Action: None required, information only.</p>
      <p align="center"><img align="bottom" src="graphics/416_image3.gif"></p>
      <p class="para_division">Cause: The sender added a new component to the assembly and transferred the parent assembly file.&nbsp;If the component has not been loaded, Collaborate attempts to open the component part file using the current assembly load options.&nbsp;This message displays only if a part open is required.</p>
      <p class="para_division">Action: None required, information only. The component load was successful.</p>
      <p align="center"><img align="bottom" src="graphics/416_image4.gif"></p>
      <p class="para_division">Cause: The sender added a new component to the assembly and transferred the parent assembly file. If the component has not been loaded, Collaborate attempts to open the component part file using the current <b class="uiTerm">Assembly Load</b> options.
      </p>
      <p class="para_division">Action: None required, information only. &nbsp;The component load failed, and the assembly error message appears.</p>
      <p align="center"><img align="bottom" src="graphics/416_image5.gif"></p>
      <p class="para_division">Cause: There are two possible causes:</p>
      <ul>
         <li>
            <p class="para_item">The sender deleted the component from the assembly and transferred the parent assembly file.</p>
         </li>
         <li>
            <p class="para_item">The receiver was using <b class="uiTerm">Part Name Mapping</b> for a component file, and when the sender transferred the assembly file the part deletes from the assembly. The receiver may re&ndash;map the name, or substitute the component to add it back
            </p>
         </li>
      </ul>
      <p class="para_division">Action:&nbsp;None required, information only. If the component is the receiver's work part, the work part resets to the assembly display part.</p>
      <p align="center"><img align="bottom" src="graphics/416_image6.gif"></p>
      <p class="para_division">Cause: The sender deleted all components from the assembly and transferred the parent assembly file.</p>
      <p class="para_division">Action:&nbsp;None required, information only.</p>
   </body>
</html>