Cancel
Showing results for 
Search instead for 
Did you mean: 

Teamcenter Integration with NX failed after updating NX version

Experimenter
Experimenter

We work with Teamcenter 11.2.0, and recently updated NX9.0.3 to NX11.0.2.

After reinstalling the NX integration via TEM, with Windows 7 users we found no problem opening TC items with NX, but with some users with Windows 10 a problem appears saying that a conection to the server wasn't possible and NX is never opened:

error_screen.jpgInitialization Failure

The system variables are set to the correct path and the star_nxmanager also has the correct path to the NX 11 installation. Any thoughts about why Windows 10 may be interfering with the server communication?

 

Thank you in advanced.

 

ROBERTO RAMÍREZ

NX 11.0.2 | TC 11.2.0 

ROBERTO RAMÍREZ, Analysis & Tooling engineer, FRISA Forge
Production: NX11.0.2 | TC 11.2.0 | TC Vis Base 11.2
Testing: NX12.0.0 | TC 11.4.0
7 REPLIES

Re: Teamcenter Integration with NX failed after updating NX version

Legend
Legend

Hello, what Server Manager you use on your server? Try to open from browser http://SCTC1:8080 on problem computer with Windows 10, what you see on screen?

Re: Teamcenter Integration with NX failed after updating NX version

Experimenter
Experimenter

Hi @Arthur3,

 

Thanks for the reply, the Server Manager info is the following:

 

image.png

 

And the screen when trying to open http://SCTC1:8080:

 

image.png

ROBERTO RAMÍREZ, Analysis & Tooling engineer, FRISA Forge
Production: NX11.0.2 | TC 11.2.0 | TC Vis Base 11.2
Testing: NX12.0.0 | TC 11.4.0

Re: Teamcenter Integration with NX failed after updating NX version

Legend
Legend

Try test ugs_router, from Windows command prompt:

 

set UGII_UGMGR_COMMUNICATION=http
set UGII_UGMGR_HTTP_URL=http://hostname : port/tc
%UGII_ROOT_DIR%\ugs_router -ugm

 

and also check on errors ugs_router.syslog on your buisness logic server in %temp% directory

Re: Teamcenter Integration with NX failed after updating NX version

Solution Partner Phenom Solution Partner Phenom
Solution Partner Phenom
@Arthur3, I hate that emoticons are created automatically in this forum...
The URL address should read http://servername : port/tc without spaces. Replace servername with the name of your web server and replace port with the web port number (default is either 80 or 8080 depending on the web application server) and replace tc with the name of your web application (default is tc).

Randy Ellsworth, Teamcenter Architect, Applied CAx, LLC
NX 11 | SW 2016 | Creo 4 | TcUA 11.4
Evaluating: AW 3.4

Re: Teamcenter Integration with NX failed after updating NX version

Solution Partner Phenom Solution Partner Phenom
Solution Partner Phenom
@Arthur3 asked which server manager you are running. He was referring to Teamcenter either J2EE (pool manager) or .NET (server manager) and not the Windows server manager. Since you're running JBoss as your web application server (J2EE) then you're likely running J2EE Pool Manager too.

A refused connection usually indicates a blocked port (firewall). Since it works on Win7 then I'm guessing there is no firewall issue on the server. This is a client issue. Turn off the Win10 firewall temporarily and try again.

Randy Ellsworth, Teamcenter Architect, Applied CAx, LLC
NX 11 | SW 2016 | Creo 4 | TcUA 11.4
Evaluating: AW 3.4

Re: Teamcenter Integration with NX failed after updating NX version

Legend
Legend

RandyEllsworth thank you for the additions to my message

Re: Teamcenter Integration with NX failed after updating NX version

Experimenter
Experimenter

@Arthur3, @RandyEllsworth Thank you very much for your support.

 

Yes, we use J2EE Pool Manager, sorry for the mixup.

 

@Arthur3, we did the test you mentioned (ugs_router) with no success and the syslog only showed a failed connection.

 

Following your recommendation, @RandyEllsworth, we proceeded to test the connection without the firewall and the integration with NX was succesful. The clients were running a 10.2 release of Kaspersky Antivirus, incompatible with Windows 10, and upgrading to the 10.3 version solved the problem.

 

Thanks again, kind regards.

ROBERTO RAMÍREZ, Analysis & Tooling engineer, FRISA Forge
Production: NX11.0.2 | TC 11.2.0 | TC Vis Base 11.2
Testing: NX12.0.0 | TC 11.4.0