I'm under the gun, (thinking it would be pretty straight forward) to upgrade from nx 8.5 to nx 10. We've got Teamcenter 10.1.4
On my test machine, i installed nx10, but cannot for the life of me get team center to open nx10 manager. It keeps opening nx8.5 (or erroring after i uninstalled it)
I've futzed w/ every environment variable and config file i can find,
changing from nx8~1.5 to C:\PROGRA~1\Siemens\NX10~1.0
If i edit the start_nxmanager.bat to V28.0, that's great, the error message changes but still nothin'.
"Teamcenter integration for nx initialize failure
nx cannot be starteed as teamcenter ingetration for nx(nx0tcin) database feature is not installed in teamcenter database."
I feel like i need to re-install everything, but I don't want to have to re-install teamcenter for all my users when it should just be a matter of pointing teamcenter at a different file.
Debugging has shown it is opening the ugs_router.exe in nx10\ugii\
I have been into several things,
Maybe i cooked something else in the install on this machine?
NX is using the file extension in Windows to determine where the ugs_router.exe is located. However, a little known fact is that the location of start_nxmanager.bat is actually stored in the registry. This can be difficult to debug when you have multiple clients running on the same machine.
I have a work around I like to use to set the registry key correctly depending on which client I'm launching. The hack will go into either portal\portal.bat or rac\otwportal.bat depending on your flavor of client (TEM vs OTW). Another hack in these same files is to ensure that FMS_HOME is set correctly and no previous FCC/TCCS is running from another environment.
What this does...
@echo off rem setlocal rem TPR is short for TC_PORTAL_ROOT to reduce command line length title Teamcenter Rich Client call "C:\Siemens\SDPROD\NXONLY\otw\otw_init.bat" set TPR=C:\Siemens\SDPROD\NXONLY\rac set FMS_HOME=C:\Siemens\SDPROD\NXONLY\tccs rem use AUX_PATH env var for any additional required paths rem save original path for external applications set ORIGINAL_PATH=%PATH% rem for optimal startup performance, keep the PATH length at a minimum set PATH=%SYSTEMROOT%\system32;%FMS_HOME%\bin;%FMS_HOME%\lib;%TPR%;%AUX_PATH% set JAVA_HOME=%TC_JRE_HOME% set JRE_HOME=%TC_JRE_HOME% %FMS_HOME%\bin\fccstat -stop reg add HKCR\ugmportalfile\Shell\Open\command /d "%TPR%\start_nxmanager.bat" /f :start_portal cd /d %TPR% set CLASSPATH=.; set VM_XMX=512m @echo Starting Teamcenter Rich Client... start Teamcenter.exe %* -vm "%JRE_HOME%\bin\javaw.exe" -vmargs -Xmx%VM_XMX% -XX:MaxPermSize=128m -Xbootclasspath/a:"%JRE_HOME%\lib\plugin.jar";"%JRE_HOME%\lib\deploy.jar";"%JRE_HOME%\lib\javaws.jar"
The attached image highlights my edits.
Then you must have done a TEM installation. The code shown was for otwportal.bat. You'll need to modify portal.bat instead using the highlighted lines from the previosly attached image.
BTW, the solution to your error is posted in an article by @CemAlpay titled "NX 10 integration to TC". Where your error was: "Teamcenter integration for nx initialize failure nx cannot be starteed as teamcenter ingetration for nx(nx0tcin) database feature is not installed in teamcenter database"
Is your Teamcenter version before Tc10.1.2? Then you might need the file mentioned by Cem.
- run tem.bat
- uncheck "NX Manager for Rich Client"
- let it complete
- exit tem
- run tem.bat
- check "NX Manager for Rich Client"
- make sure to point to the NX10.
- let it complete
- reapply 10.1.4 patch