Troubleshooting

Performance issues Running a virus scan software in real-time on items while they are being migrated will reduce CMM performance. Siemens PLM recommends that you exclude the CMM Scratch and Report directories from virus scans while the migration is being performed. If you are running CMM Solo, exclude the directory that contains the SourceCAD data from virus scans while the migration is being performed. Memory issues When running CMMSolo.cmd or CMMBatch.cmd, what does the Java error “out of memory” mean? Memory is controlled by the maximum memory setting passed to Java when the program starts. You can edit the CMMSolo.cmd or the CMMBatch.cmd file to increase the allowed memory by increasing the –Xmx value. When setting this value, you need to make sure that the machine you are running on has enough available memory and that the setting you choose will not starve the other processes running on that machine. set JAVA_COMMAND=%JAVA_COMMAND% -Xms512m -Xmx4096m %JAVA_HOME%\bin\java -Xms512m -Xmx4096m -DCMMBaseDir=%CMM_BASE_DIR%... Heap size When starting CMM Solo, what does the message “Invalid maximum heap size:” mean? This error occurs if you are using a 32-bit Java JRE installation with your CMM installation. The best solution is to uninstall CMM and then reinstall pointing to a 64-bit java JRE installation. If you cannot use 64-bit Java JRE, you can modify the CMMSolo.cmd file by changing the Xmx value to 1300. set JAVA_COMMAND=%JAVA_COMMAND% -Xms512m -Xmx1300m Session form not installed What does the error message “Unable to create or update CMM Session” mean? This indicate that the latest CMM template was not installed into the Teamcenter database. To resolve this, the Teamcenter administrator must install the template, using the Teamcenter Environment Manager. CMM Solo load time When I select a directory to load Pro/ENGINEER or Creo data for CMM Solo to migrate, it takes a very long time for the migration selection to appear. When selecting an entire directory to migrate, CMM has to first analyze the data to determine the complete product structure hierarchy. This can take a very long time for large directories. To improve performance, either select the specific items that you want to migrate or reduce the number of items in the directory you have selected. Best practices

Best practices Zombie processes My CMM run has crashed and left some zombie processes still running. What do I do? CMM provides a script to terminate most processes that may be left by a crash during a migration session. The _STOP_CMM.bat script is in the CMMScratch directory or in the Dispatcher's staging area's Task directory. Run this script to terminate the processes related to this CMM session. Change ownership issues When I run a migration through Dispatcher Client and set the ownership to CAD, the ownership is not set correctly. Setting ownership to CAD in the Dispatcher Client Service.properties file is designed to make the owner of the migrated NX dataset the same as the user and group that owns the source CAD dataset. If you have set the ownership to CAD correctly and are not seeing this ownership, it is most likely an issue with your Access Control rules. See the Dispatcher Client section for information on setting Access Control rules. Dispatcher Client performance issues I am running Dispatcher Client and I see that each item I submit runs its own session. This causes wasted time in starting and stopping CMM services. To improve performance, submit large numbers of items to a single Dispatcher session by using the CMM Submit to Dispatcher command, or by using the CMMBatch –submit option. This eliminates the multiple CMM service startups. See the Dispatcher Client section for additional information. Open migrated assembly in NX When I open a migrated assembly in NX in unmanaged mode, I see the message Part is not a valid version of component part for a child part or assembly. In addition, the child may not load into NX. This is most likely because the child was remigrated after the parent assembly was migrated, but the parent assembly has not been remigrated. So the parent is out-of-date relative to the children. To solve this problem, you can do either of the following:

• Remigrate the parent assembly.
• Change the way the assembly is loaded. In the Assembly Load Options dialog box, Load Behavior group, select Allow Replacement. This lets the children load, but still displays a warning. Once you save the top level assembly in NX, the warning no longer appears. Open migrated assembly in NX when Reuse Lookup Table is on When I open a migrated assembly in NX in unmanaged mode, I see the message Failed to find file using current search options for a child part or assembly. In addition, the child does not load into NX. This is because the child parts and assemblies are located in different directories. To locate dependent items in different directories, in the Assembly Load Options dialog box, Part Versions group, set the Load option to From Search Folder and add all of the necessary CMM scratch folders to the search list. Best practices

Best practices The list of scratch folders can be found in the Reuse Lookup Table options page in CMMSolo. Once you have added all of the folders, you can select the Save Load Options option in the Assembly Load Options dialog box. Best practices

Best practices