Teamcenter: Unable to bind to server running on localhost: 1572 1

[thomasleeclark]

Suddenly, I can't login to Teamcenter. Appears to be a problem at the remote license server.
First, after a long wait, I get the error message: Unable to bind to server running on localhost: 1572
If I try again, error message is: POM not started
Try a third time, error message is: Teamcenter Engineering has detected a serious internal error; To maintain data integrity log out and restart Teamcenter Engineering, otherwise data corruption could occur.
In the "TAO ImR" console window running in the background, the following lines repeat:
<TCServer1> not running. alive=false.
Cannot Activate <TCServer1>.
Can anyone help me with this? -thomasleeclark

 

[wecurb]

tlc, sounds like your connection to the server is toast. IT should be able to determine if it is your 'puter or their lines. Or, possibly, your profile got trashed somehow.

 

[thomasleeclark]

Thanks, wecurb. We seem to have connectivity to the server, although it is sluggish. Is there a way to examine the user profiles (without opening Teamcenter, I mean)?
Also, we installed a floating license for ProEngineer on the same server recently. Could this have caused some kind of problem? Anyone?

 

[thomasleeclark]

Regarding my problem with Teamcenter: No matter what we try, users are unable to login ("Unable to bind to server running on localhost: 1572"). Logged onto the Teamcenter server itself as infodba, we tried using the Teamcenter Environment Manager (Modify Rich Client Server settings). It shows the connection port is 1572, Activation Mode "Normal".
There must be a way to open or re-enable port 1572 for Teamcenter on the server?
John (Baker), can you help with this? (By the way, thanks for the Font Factory!)
- thomasleeclark

 

[mthomp]

firewall issue?

 

[aszepesi]

Could you attach the tcserver.syslog file from the trying login side (server or client side)?
When you have got a license error you can see it in the TAO window (allocating Teamcenter license teamcenter_author, etc.)
Server side:
Try to login in the portal interface in the server side as infodba. When it is false It may be a database connection error. You can see this error lines in the tcserver.syslog file. There are some situation when some Teamcenter operations abort. In these cases you can use the clearlocks.exe -assert_all_dead -u=infodba -p=password -g=dba utility.
Client side:
You must ping the server and you must read the %TC_DATA% shared folder.
Which Teamcenter version do you use?

 

[thomasleeclark]

Thanks, Dutra1000. I'll try your ideas. My version appears to be 2005 SR1/2007. -tlc

 

[BOPdesigner]

I have the same problem on a couple of my test systems. Logged on to GTAC and there are a couple of documents I followed. The first one "POM not started" resulted from the infodba password expiring (in oracle). So I changed the password and then you get a new error. Can't remember what it was but the result is that I had to login to SQLPlus and get the encrypted password for my new infodba password and paste it in your iman_profilevars.bat file for TC_DB_CONNECT and IMAN_DB_CONNECT. Problem still remains that now I can't login to the RAC using infodba account (and can't login to SQLPlus again with it) because it still doesn't like the password. But TcE logins for normal users are working again. If you search GTAC for POM not started you should find the first document.

 

[thomasleeclark]

Thanks, everyone. I haven't tried the solutions offered by Dutra and BOP because, lo and behold, Teamcenter is now allowing me to login! Our head of MIS suspected some Microsoft XP updates (security patches?) that he had installed April 19, so he removed them from the server and restarted everything. This seems to have worked, although we don't yet know exactly which patch was the culprit. If we learn more, I will post it. -thomasleeclark