Showing results for 
Search instead for 
Do you mean 
Reply
Solved! Go to solution

Killing a user process from corporate server

Hi guys,

 

This may seem very basic to you Smiley Happy

Sometimes a TC Rich client gets messed up(because of Java or NX errors or whatever) and user needs to close the Teamcenter forcibly by ending the process with Task Manager.

Then they restart the rich client, try to log on and get an error message saying "A connection is already established"

When I run "list_users" in the corporate server, I see the user still listed there even though he does not run TC.

Which is the most convenient way to delete that user from thinking he is still logged on to the server?

(TAO is already closed on the client)

 

Cem ALPAY

12 REPLIES

Re: Killing a user process from corporate server

TCCS or FMS is still running in the background, you need to stop them too using the appropriate utility.

 

For Tc 10.1 this is %TC_ROOT%\tccs\bin\fccstat

Stefan Pendl, Systemmanager CAx, HAIDLMAIR GmbH
Production: NX10.0.3, VERICUT 8.0, FBM, MRL 3.1.4 | TcUA 10.1 MP7 Patch 0 (10.1.7.0) | TcVis 10.1
Development: VB.NET, Tcl/Tk    Testing: NX11.0 EAP, NX12.0 EAP

How to Get the Most from Your Signature in the Community

Re: Killing a user process from corporate server

Try running "clearlocks -verbose".

If it does not work, try "clearlocks <hostname of the user> -assert_dead -u=infodba -p=<password> -g=dba".

Solution
Solution
Accepted by topic author CemAlpay
‎08-26-2015 04:32 AM

Re: Killing a user process from corporate server

Naturally, clearlocks won't work as the session is still valid and the utility should be avoided in a 4tier environment as other valid sessions might be killed due to an access timeout (like users gone to lunch or in a long meeting). The right way to kill a session is to use the admin console.

 

JMX

  • http://<server>:<port>/
  • manager/manager (default user and password)

.NET

  • http://<server>:<port>/tc/admin
  • admin/admin (default user and password)

 

Best,

/Randy


Randy Ellsworth, Teamcenter Architect, Applied CAx, LLC
NX 11.0.1.mp01 | SW 2016 | TcUA 11.2.3
Evaluating:AW 3.2

Re: Killing a user process from corporate server

Hi Randy,

I tried to log in to .Net, it asks for a user/pass, not admin/admin.
Also not infodba, it doesn't work either.
Where can I see which user is admin to do this process?

Sayg?lar?mla,

Cem ALPAY, Y?netici
??GEN YAZILIM LTD. ?T?.
TEL: 0216 550 52 06

[IMZA_22]

Re: Killing a user process from corporate server

The Server Administration Console is a web application created during the installation of the .NET Web Tier. The default port is 8080, the default user is admin and the default password is admin. You *might* be able to uninstall and reinstall the .NET Web Tier to get back to the defaults. Good luck!


Randy Ellsworth, Teamcenter Architect, Applied CAx, LLC
NX 11.0.1.mp01 | SW 2016 | TcUA 11.2.3
Evaluating:AW 3.2

Re: Killing a user process from corporate server

Try logging into the admin console from the Teamcenter server using  http://localhost:<port>/tc/admin

 

This way it will use the local account credentials and won't ask the password. Then locate the process from the list and use the options on the webpage to stop the tcserver process.

 

Regards,

Uday Takbhate

Siemens Canada

 

 

Re: Killing a user process from corporate server

Has anyone automated the process of killing stale user processes?

Any ideas on how to do this?

Re: Killing a user process from corporate server

I created a simple .NET application that the user can user to kill their process.

It uses their AD account login ID (matches Tc login ID).

It sends the request from the users computer to an application running on a server.  The server application parses the "Show Servers" pool manager webpage to find the tcserver process.  Once the process has been identified, it calls the shutdown page for that process to end the user's pool connection.

Re: Killing a user process from corporate server

Does it loop if there is more than one process? You can avoid this by disabling shared session so that the same user doesn't try to reconnect to the existing process and creates a new process instead.

Randy Ellsworth, Teamcenter Architect, Applied CAx, LLC
NX 11.0.1.mp01 | SW 2016 | TcUA 11.2.3
Evaluating:AW 3.2