Cancel
Showing results for 
Search instead for 
Did you mean: 

2- Tier or 4-Tier clients dont work: POM has not started

Hello,

we are hardly trying to get our academic version of Teamcenter running with clients.

Configuration:

Win 2016 Server

MSSQL 2016 Standard

Teamcenter 11.2 with 11.6 upgrade

Java 8.201

All firewalls are down.

 

At first we tried 2-Tier. The client installation works on the Server. But not on the client-computer, there the login window shows the error: pom.jpgPOM has not started.

The database is accessible from the client, I tried by a simple .udl file. Is it necessary that the Client windows user can access the database or is it sufficient that infodba can?

Here now some lines from the syslog file:

INFO  - 2019/03/27-17:05:12.772 UTC - InitializeModule.POM - library libsa is delay loaded - Teamcenter.Metamodel.MetaFrameWork at D:\workdir\tc11601_win64\src\core\metaframework\BusinessObjectRegistryImpl.cxx(2706)
INFO  - 2019/03/27-17:05:12.772 UTC - InitializeModule.POM - POM V10.0.1.0  compiled on Jan 28 2019 - Teamcenter.POM at D:\workdir\tc11601_win64\src\foundation\pom\pom\pom_init.cxx(461)
INFO  - 2019/03/27-17:05:12.772 UTC - InitializeModule.POM - Compiled:  -D__OCI  -D__ODBC  - Teamcenter.POM at D:\workdir\tc11601_win64\src\foundation\pom\pom\pom_init.cxx(471)
Session is running in codeset 1252 17
INFO  - 2019/03/27-17:05:12.776 UTC - InitializeModule.POM - Default encryption configuration. - Teamcenter.FoundationBase at D:\workdir\tc11601_win64\src\foundation\base\Crypto.cxx(106)
INFO  - 2019/03/27-17:05:12.776 UTC - InitializeModule.POM - Using ODBC driver: DRIVER=SQL Server to attempt to connect.
 - Teamcenter.POM at D:\workdir\tc11601_win64\src\foundation\pom\eim\eim_trans_util.cxx(861)
ERROR - 2019/03/27-17:05:31.589 UTC - InitializeModule.POM - Connection to the database failed with :0 - Teamcenter.POM at D:\workdir\tc11601_win64\src\foundation\pom\eim\eim_trans_util.cxx(987)
ODBC error. SQLSTATE: 08001 Native error: 17
Message: [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server existiert nicht oder Zugriff verweigert.
Approx SQL was "CONNECT"
ODBC error. SQLSTATE: 01000 Native error: 64
Message: [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()).
CONNECT;
INFO  - 2019/03/27-17:05:31.589 UTC - InitializeModule.POM - ===>Took 18.812 seconds to execute that SQL (returning 0 rows) - Teamcenter.POM at D:\workdir\tc11601_win64\src\foundation\pom\eim\eim_enquire.cxx(6219)
WARN  - 2019/03/27-17:05:31.589 UTC - InitializeModule.POM - 17 - Connect failed (17) for 'infodba' at DATABASE=tc;SERVER=tcserver\TCSQL - Teamcenter.POM at D:\workdir\tc11601_win64\src\foundation\pom\eim\eim_trans_util.cxx(1040)
INFO  - 2019/03/27-17:05:31.589 UTC - InitializeModule.POM - Using ODBC driver: DRIVER=SQL Server to attempt to connect.
 - Teamcenter.POM at D:\workdir\tc11601_win64\src\foundation\pom\eim\eim_trans_util.cxx(861)
ERROR - 2019/03/27-17:05:52.087 UTC - InitializeModule.POM - Connection to the database failed with :0 - Teamcenter.POM at D:\workdir\tc11601_win64\src\foundation\pom\eim\eim_trans_util.cxx(987)
ODBC error. SQLSTATE: 08001 Native error: 17
Message: [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server existiert nicht oder Zugriff verweigert.
Approx SQL was "CONNECT"
ODBC error. SQLSTATE: 01000 Native error: 64
Message: [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()).

and

Teamcenter could not connect to the DBMS specified in the
TC_DB_CONNECT environment variable.
This could be because the DBMS is not online or the server
is not accessible from your node.

(Please finde the whole logfile attached below)

 

I dont understand why it cant connect to the database, can someone help me to understand how to check?

 

Then, frustrated as we were, we tried to install a 4-Tier client.

That one also does not start the rich client (even not the client installation on the Server):

Capture.PNG

We reinstalled java, but that is also not working. The webclient is working!

 

Thanks!

8 REPLIES 8

Re: 2- Tier or 4-Tier clients dont work: POM has not started

Gears Phenom Gears Phenom
Gears Phenom

@JensKlussmann - this could be a many number of reasons. But in your log, it is stating that SQL server doesn't exist or access is denied. 

Message: [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server existiert nicht oder Zugriff verweigert.

 

Check your TC_DB_CONNECT string in the tc_profilevars.bat (in TC_DATA) is pointing to the correct DB server. If that looks correct then it could possibly be that the password could be expired, wrong, or locked in the database. That would need the db password to be re-encrypted to update tc_profilevars to connect. 

 

After correcting, verify connection to the database on the server. In a Admin TC CMD prompt on the server. Type in:

install -ayt

It should return "Site already installed".  If not, that is a problem and more debugging is required.

 

 

 

Jamie Griffis | PLM Solution Architect | Engineering USA

Re: 2- Tier or 4-Tier clients dont work: POM has not started

Thanks Jamie,

 

before I will check that, on simple question:

 

The 2-Tier client, installed on the TC-Server is working without any problems... its just the 2-Tier clients on other computers that do not work. So I think that the password could not be expired or so!?

 

The command install -ayt already returns "Site is already installed".

 

Is it somehow possible to check the db connection from the client side? I did with a .udl file and it worked.

Re: 2- Tier or 4-Tier clients dont work: POM has not started

Thanks Jamie,

the server has a 2-Tier client installation also and that is working fine. The

install -ayt

returns a "Site already installed". It is just the separate client computers that cannot connect.

 

I checked th tc_profilevars.bat and it was pointing to the correct server.

 

Trying to find a solution I did a full reinstall of the Server and Client on the Server computer, renaming the Server before that, to a different Name "teamcenter".

We have a large university network that is not fully accessible to me and I suppose the problem lies anywhere in there.

Now, after reinstalling the server and 2T client on the Server are working fine (as before). But still the 2T client installed on a different computer still cannot connect, the error Message is now different, "The inquiry ID is invalid".

Searching the logfile I find entries like:

ERROR - 2019/04/08-14:59:00.673 UTC - InitializeModule.PRELOAD_TYPES - 6 - FSC_Download error: 6 CURLE_COULDNT_RESOLVE_HOST: The host domain name to which you are trying to connect could not be resolved. - Teamcenter.Organization.sa at D:\workdir\tc11601_win64\src\core\sa\fscinterface.cxx(1621)
ERROR - 2019/04/08-14:59:00.829 UTC - InitializeModule.PRELOAD_TYPES - 41178: FSC proxy error: "6 CURLE_COULDNT_RESOLVE_HOST: The host domain name to which you are trying to connect could not be resolved.". - Failed to download Metadata Cache File - Teamcenter.MetaModel.sharedcache at D:\workdir\tc11601_win64\src\core\sharedcache\SharedMetadataCacheMgr.cxx(414)
ERROR - 2019/04/08-14:59:00.845 UTC - InitializeModule.PRELOAD_TYPES - 41178: FSC proxy error: "6 CURLE_COULDNT_RESOLVE_HOST: The host domain name to which you are trying to connect could not be resolved.". - Failed in processDeployFile - Teamcenter.MetaModel.sharedcache at D:\workdir\tc11601_win64\src\core\sharedcache\SharedMetadataCacheMgr.cxx(245)

Contents of the error store:-
       ERROR 41178 FSC proxy error: "6 CURLE_COULDNT_RESOLVE_HOST: The host domain name to which you are trying to connect could not be resolved.".

ERROR - 2019/04/08-14:59:00.845 UTC - InitializeModule.PRELOAD_TYPES - 41178: FSC proxy error: "6 CURLE_COULDNT_RESOLVE_HOST: The host domain name to which you are trying to connect could not be resolved.". - ITK_init_module_prelogin with error 0 - Teamcenter.CoreModelGeneral.tc at D:\workdir\tc11601_win64\src\core\tc\infomanager_itk.cxx(2152)
INFO  - 2019/04/08-14:59:00.860 UTC - PL130302.14376 - xercesc_3_2 has been initialized. - Teamcenter.SOA.Server
INFO  - 2019/04/08-14:59:00.860 UTC - PL130302.14376 - ServerID: TcServer1 - Teamcenter.Soa.Communication
INFO  - 2019/04/08-14:59:00.860 UTC - PL130302.14376 - Using code page ibm-5348_P100-1997 for local encoding of service request/response - Teamcenter.SOA.Server
INFO  - 2019/04/08-14:59:00.860 UTC - PL130302.14376 - INIT:: confused by module PRELOAD_TYPES in state 3 - Teamcenter.POM at D:\workdir\tc11601_win64\src\foundation\pom\init\init.cxx(307)
INFO  - 2019/04/08-14:59:00.860 UTC - PL130302.14376 - INIT:: confused by module PRELOAD_TYPES in state 3 - Teamcenter.POM at D:\workdir\tc11601_win64\src\foundation\pom\init\init.cxx(307)
INFO  - 2019/04/08-14:59:01.157 UTC - PL130302.14376 - INIT:: confused by module PRELOAD_TYPES in state 3 - Teamcenter.POM at D:\workdir\tc11601_win64\src\foundation\pom\init\init.cxx(307)
INFO  - 2019/04/08-14:59:01.157 UTC - PL130302.14376 - INIT:: confused by module PRELOAD_TYPES in state 3 - Teamcenter.POM at D:\workdir\tc11601_win64\src\foundation\pom\init\init.cxx(307)
Successfully loaded dynamic module C:\Siemens5\Teamcenter11\bin\libpreviousxerces.dll
INFO  - 2019/04/08-14:59:01.172 UTC - PL130302.14376 - xercesc_2_7 has been initialized. - Teamcenter.PreviousXerces
INFO  - 2019/04/08-14:59:01.204 UTC - PL130302.14376 - TC_TMP_DIR environment variable not found. - Teamcenter.Organization.sa at D:\workdir\tc11601_win64\src\core\sa\filetickets.cxx(1154)
INFO  - 2019/04/08-14:59:01.204 UTC - PL130302.14376 - The Transient Volume Root Directory at C:\Users\ch5000\AppData\Local\Temp\ch50002TierTV already exists. - Teamcenter.Organization.sa at D:\workdir\tc11601_win64\src\core\sa\filetickets.cxx(4906)
INFO  - 2019/04/08-14:59:01.204 UTC - PL130302.14376 - Transient volume write access verified using file: C:\Users\ch5000\AppData\Local\Temp\ch50002TierTV\tvrdtestfile_15856_1554735541 - Teamcenter.Organization.sa at D:\workdir\tc11601_win64\src\core\sa\filetickets.cxx(4971)
INFO  - 2019/04/08-14:59:01.204 UTC - PL130302.14376 - The Transient Volume Root Directory is C:\Users\ch5000\AppData\Local\Temp\ch50002TierTV  - Teamcenter.Organization.sa at D:\workdir\tc11601_win64\src\core\sa\filetickets.cxx(1281)
INFO  - 2019/04/08-14:59:01.204 UTC - PL130302.14376 - Teamcenter Server is ready. - Teamcenter.SOA.tcserver_itk_main
INFO  - 2019/04/08-14:59:01.204 UTC - PL130302.14376 - CORBA server is starting - Teamcenter.SOA.tcserver_itk_main
INFO  - 2019/04/08-14:59:18.941 UTC - .UnknownClient.00001 - Service Request:  Core-2011-06-Session:login - Teamcenter.Soa.Communication
INFO  - 2019/04/08-14:59:19.097 UTC - .UnknownClient.00001 - metadata dataset version [5] metadata DB change version [5] - Teamcenter.MetaModel.sharedcache at D:\workdir\tc11601_win64\src\core\sharedcache\SharedMetadataCacheMgr.cxx(94)
INFO  - 2019/04/08-14:59:19.097 UTC - .UnknownClient.00001 - segmentPath [C:\Users\ch5000\AppData\Local\Temp\V11000.2.0.71_20190128.00\2440018629\Metadata\Version5.mem] [does not exist] - Teamcenter.MetaModel.sharedcache at D:\workdir\tc11601_win64\src\core\sharedcache\SharedMetadataCacheMgr.cxx(234)
ERROR - 2019/04/08-14:59:19.097 UTC - .UnknownClient.00001 - 515023: The enquiry ID is invalid.
ERROR - 2019/04/08-14:59:19.097 UTC - .UnknownClient.00001 - 515023: The enquiry ID is invalid. - Failed to download Metadata Cache File - Teamcenter.MetaModel.sharedcache at D:\workdir\tc11601_win64\src\core\sharedcache\SharedMetadataCacheMgr.cxx(414)
ERROR - 2019/04/08-14:59:19.097 UTC - .UnknownClient.00001 - 515023: The enquiry ID is invalid. - Failed in processDeployFile - Teamcenter.MetaModel.sharedcache at D:\workdir\tc11601_win64\src\core\sharedcache\SharedMetadataCacheMgr.cxx(245)

Contents of the error store:-
ERROR515023 The enquiry ID is invalid.

It still points to a network problem, isn't it?

I've checked the ipconfig for both, the server and the client computer:

IP address is same until third field, subnetmask, default gateway, dhcp and dns servers are all the same...

 

Any more hints?

Re: 2- Tier or 4-Tier clients dont work: POM has not started

Thanks Jamie,

the server has a 2-Tier client installation also and that is working fine. The

install -ayt

returns a "Site already installed". It is just the separate client computers that cannot connect.


I checked th tc_profilevars.bat and it was pointing to the correct server.


Trying to find a solution I did a full reinstall of the Server and Client on the Server computer, renaming the Server before that, to a different Name "teamcenter".

We have a large university network that is not fully accessible to me and I suppose the problem lies anywhere in there.

Now, after reinstalling the server and 2T client on the Server are working fine (as before). But still the 2T client installed on a different computer still cannot connect, the error Message is now different, "The inquiry ID is invalid".

Searching the logfile I find entries like:

ERROR - 2019/04/08-14:59:00.673 UTC - InitializeModule.PRELOAD_TYPES - 6 - FSC_Download error: 6 CURLE_COULDNT_RESOLVE_HOST: The host domain name to which you are trying to connect could not be resolved. - Teamcenter.Organization.sa at D:\workdir\tc11601_win64\src\core\sa\fscinterface.cxx(1621)
ERROR - 2019/04/08-14:59:00.829 UTC - InitializeModule.PRELOAD_TYPES - 41178: FSC proxy error: "6 CURLE_COULDNT_RESOLVE_HOST: The host domain name to which you are trying to connect could not be resolved.". - Failed to download Metadata Cache File - Teamcenter.MetaModel.sharedcache at D:\workdir\tc11601_win64\src\core\sharedcache\SharedMetadataCacheMgr.cxx(414)
ERROR - 2019/04/08-14:59:00.845 UTC - InitializeModule.PRELOAD_TYPES - 41178: FSC proxy error: "6 CURLE_COULDNT_RESOLVE_HOST: The host domain name to which you are trying to connect could not be resolved.". - Failed in processDeployFile - Teamcenter.MetaModel.sharedcache at D:\workdir\tc11601_win64\src\core\sharedcache\SharedMetadataCacheMgr.cxx(245)

Contents of the error store:-
ERROR 41178 FSC proxy error: "6 CURLE_COULDNT_RESOLVE_HOST: The host domain name to which you are trying to connect could not be resolved.".

ERROR - 2019/04/08-14:59:00.845 UTC - InitializeModule.PRELOAD_TYPES - 41178: FSC proxy error: "6 CURLE_COULDNT_RESOLVE_HOST: The host domain name to which you are trying to connect could not be resolved.". - ITK_init_module_prelogin with error 0 - Teamcenter.CoreModelGeneral.tc at D:\workdir\tc11601_win64\src\core\tc\infomanager_itk.cxx(2152)
INFO - 2019/04/08-14:59:00.860 UTC - PL130302.14376 - xercesc_3_2 has been initialized. - Teamcenter.SOA.Server
INFO - 2019/04/08-14:59:00.860 UTC - PL130302.14376 - ServerID: TcServer1 - Teamcenter.Soa.Communication
INFO - 2019/04/08-14:59:00.860 UTC - PL130302.14376 - Using code page ibm-5348_P100-1997 for local encoding of service request/response - Teamcenter.SOA.Server
INFO - 2019/04/08-14:59:00.860 UTC - PL130302.14376 - INIT:: confused by module PRELOAD_TYPES in state 3 - Teamcenter.POM at D:\workdir\tc11601_win64\src\foundation\pom\init\init.cxx(307)
INFO - 2019/04/08-14:59:00.860 UTC - PL130302.14376 - INIT:: confused by module PRELOAD_TYPES in state 3 - Teamcenter.POM at D:\workdir\tc11601_win64\src\foundation\pom\init\init.cxx(307)
INFO - 2019/04/08-14:59:01.157 UTC - PL130302.14376 - INIT:: confused by module PRELOAD_TYPES in state 3 - Teamcenter.POM at D:\workdir\tc11601_win64\src\foundation\pom\init\init.cxx(307)
INFO - 2019/04/08-14:59:01.157 UTC - PL130302.14376 - INIT:: confused by module PRELOAD_TYPES in state 3 - Teamcenter.POM at D:\workdir\tc11601_win64\src\foundation\pom\init\init.cxx(307)
Successfully loaded dynamic module C:\Siemens5\Teamcenter11\bin\libpreviousxerces.dll
INFO - 2019/04/08-14:59:01.172 UTC - PL130302.14376 - xercesc_2_7 has been initialized. - Teamcenter.PreviousXerces
INFO - 2019/04/08-14:59:01.204 UTC - PL130302.14376 - TC_TMP_DIR environment variable not found. - Teamcenter.Organization.sa at D:\workdir\tc11601_win64\src\core\sa\filetickets.cxx(1154)
INFO - 2019/04/08-14:59:01.204 UTC - PL130302.14376 - The Transient Volume Root Directory at C:\Users\ch5000\AppData\Local\Temp\ch50002TierTV already exists. - Teamcenter.Organization.sa at D:\workdir\tc11601_win64\src\core\sa\filetickets.cxx(4906)
INFO - 2019/04/08-14:59:01.204 UTC - PL130302.14376 - Transient volume write access verified using file: C:\Users\ch5000\AppData\Local\Temp\ch50002TierTV\tvrdtestfile_15856_1554735541 - Teamcenter.Organization.sa at D:\workdir\tc11601_win64\src\core\sa\filetickets.cxx(4971)
INFO - 2019/04/08-14:59:01.204 UTC - PL130302.14376 - The Transient Volume Root Directory is C:\Users\ch5000\AppData\Local\Temp\ch50002TierTV - Teamcenter.Organization.sa at D:\workdir\tc11601_win64\src\core\sa\filetickets.cxx(1281)
INFO - 2019/04/08-14:59:01.204 UTC - PL130302.14376 - Teamcenter Server is ready. - Teamcenter.SOA.tcserver_itk_main
INFO - 2019/04/08-14:59:01.204 UTC - PL130302.14376 - CORBA server is starting - Teamcenter.SOA.tcserver_itk_main
INFO - 2019/04/08-14:59:18.941 UTC - .UnknownClient.00001 - Service Request: Core-2011-06-Session:login - Teamcenter.Soa.Communication
INFO - 2019/04/08-14:59:19.097 UTC - .UnknownClient.00001 - metadata dataset version [5] metadata DB change version [5] - Teamcenter.MetaModel.sharedcache at D:\workdir\tc11601_win64\src\core\sharedcache\SharedMetadataCacheMgr.cxx(94)
INFO - 2019/04/08-14:59:19.097 UTC - .UnknownClient.00001 - segmentPath [C:\Users\ch5000\AppData\Local\Temp\V11000.2.0.71_20190128.00\2440018629\Metadata\Version5.mem] [does not exist] - Teamcenter.MetaModel.sharedcache at D:\workdir\tc11601_win64\src\core\sharedcache\SharedMetadataCacheMgr.cxx(234)
ERROR - 2019/04/08-14:59:19.097 UTC - .UnknownClient.00001 - 515023: The enquiry ID is invalid.
ERROR - 2019/04/08-14:59:19.097 UTC - .UnknownClient.00001 - 515023: The enquiry ID is invalid. - Failed to download Metadata Cache File - Teamcenter.MetaModel.sharedcache at D:\workdir\tc11601_win64\src\core\sharedcache\SharedMetadataCacheMgr.cxx(414)
ERROR - 2019/04/08-14:59:19.097 UTC - .UnknownClient.00001 - 515023: The enquiry ID is invalid. - Failed in processDeployFile - Teamcenter.MetaModel.sharedcache at D:\workdir\tc11601_win64\src\core\sharedcache\SharedMetadataCacheMgr.cxx(245)

Contents of the error store:-
ERROR515023 The enquiry ID is invalid.


It still points to a network problem, isn't it?

I've checked the ipconfig for both, the server and the client computer:

IP address is same until third field, subnetmask, default gateway, dhcp and dns servers are all the same...


Any more hints?

Re: 2- Tier or 4-Tier clients dont work: POM has not started

ERROR - 2019/04/08-14:59:00.673 UTC - InitializeModule.PRELOAD_TYPES - 6 - FSC_Download error: 6 CURLE_COULDNT_RESOLVE_HOST: The host domain name to which you are trying to connect could not be resolved. - Teamcenter.Organization.sa at D:\workdir\tc11601_win64\src\core\sa\fscinterface.cxx(1621)
ERROR - 2019/04/08-14:59:00.829 UTC - InitializeModule.PRELOAD_TYPES - 41178: FSC proxy error: "6 CURLE_COULDNT_RESOLVE_HOST: The host domain name to which you are trying to connect could not be resolved.". - Failed to download Metadata Cache File - Teamcenter.MetaModel.sharedcache at D:\workdir\tc11601_win64\src\core\sharedcache\SharedMetadataCacheMgr.cxx(414)
ERROR - 2019/04/08-14:59:00.845 UTC - InitializeModule.PRELOAD_TYPES - 41178: FSC proxy error: "6 CURLE_COULDNT_RESOLVE_HOST: The host domain name to which you are trying to connect could not be resolved.". - Failed in processDeployFile - Teamcenter.MetaModel.sharedcache at D:\workdir\tc11601_win64\src\core\sharedcache\SharedMetadataCacheMgr.cxx(245)

Contents of the error store:-
ERROR 41178 FSC proxy error: "6 CURLE_COULDNT_RESOLVE_HOST: The host domain name to which you are trying to connect could not be resolved.".

ERROR - 2019/04/08-14:59:00.845 UTC - InitializeModule.PRELOAD_TYPES - 41178: FSC proxy error: "6 CURLE_COULDNT_RESOLVE_HOST: The host domain name to which you are trying to connect could not be resolved.". - ITK_init_module_prelogin with error 0 - Teamcenter.CoreModelGeneral.tc at D:\workdir\tc11601_win64\src\core\tc\infomanager_itk.cxx(2152)
INFO - 2019/04/08-14:59:00.860 UTC - PL130302.14376 - xercesc_3_2 has been initialized. - Teamcenter.SOA.Server
INFO - 2019/04/08-14:59:00.860 UTC - PL130302.14376 - ServerID: TcServer1 - Teamcenter.Soa.Communication
INFO - 2019/04/08-14:59:00.860 UTC - PL130302.14376 - Using code page ibm-5348_P100-1997 for local encoding of service request/response - Teamcenter.SOA.Server
INFO - 2019/04/08-14:59:00.860 UTC - PL130302.14376 - INIT:: confused by module PRELOAD_TYPES in state 3 - Teamcenter.POM at D:\workdir\tc11601_win64\src\foundation\pom\init\init.cxx(307)
INFO - 2019/04/08-14:59:00.860 UTC - PL130302.14376 - INIT:: confused by module PRELOAD_TYPES in state 3 - Teamcenter.POM at D:\workdir\tc11601_win64\src\foundation\pom\init\init.cxx(307)
INFO - 2019/04/08-14:59:01.157 UTC - PL130302.14376 - INIT:: confused by module PRELOAD_TYPES in state 3 - Teamcenter.POM at D:\workdir\tc11601_win64\src\foundation\pom\init\init.cxx(307)
INFO - 2019/04/08-14:59:01.157 UTC - PL130302.14376 - INIT:: confused by module PRELOAD_TYPES in state 3 - Teamcenter.POM at D:\workdir\tc11601_win64\src\foundation\pom\init\init.cxx(307)
Successfully loaded dynamic module C:\Siemens5\Teamcenter11\bin\libpreviousxerces.dll
INFO - 2019/04/08-14:59:01.172 UTC - PL130302.14376 - xercesc_2_7 has been initialized. - Teamcenter.PreviousXerces
INFO - 2019/04/08-14:59:01.204 UTC - PL130302.14376 - TC_TMP_DIR environment variable not found. - Teamcenter.Organization.sa at D:\workdir\tc11601_win64\src\core\sa\filetickets.cxx(1154)
INFO - 2019/04/08-14:59:01.204 UTC - PL130302.14376 - The Transient Volume Root Directory at C:\Users\ch5000\AppData\Local\Temp\ch50002TierTV already exists. - Teamcenter.Organization.sa at D:\workdir\tc11601_win64\src\core\sa\filetickets.cxx(4906)
INFO - 2019/04/08-14:59:01.204 UTC - PL130302.14376 - Transient volume write access verified using file: C:\Users\ch5000\AppData\Local\Temp\ch50002TierTV\tvrdtestfile_15856_1554735541 - Teamcenter.Organization.sa at D:\workdir\tc11601_win64\src\core\sa\filetickets.cxx(4971)
INFO - 2019/04/08-14:59:01.204 UTC - PL130302.14376 - The Transient Volume Root Directory is C:\Users\ch5000\AppData\Local\Temp\ch50002TierTV - Teamcenter.Organization.sa at D:\workdir\tc11601_win64\src\core\sa\filetickets.cxx(1281)
INFO - 2019/04/08-14:59:01.204 UTC - PL130302.14376 - Teamcenter Server is ready. - Teamcenter.SOA.tcserver_itk_main
INFO - 2019/04/08-14:59:01.204 UTC - PL130302.14376 - CORBA server is starting - Teamcenter.SOA.tcserver_itk_main
INFO - 2019/04/08-14:59:18.941 UTC - .UnknownClient.00001 - Service Request: Core-2011-06-Session:login - Teamcenter.Soa.Communication
INFO - 2019/04/08-14:59:19.097 UTC - .UnknownClient.00001 - metadata dataset version [5] metadata DB change version [5] - Teamcenter.MetaModel.sharedcache at D:\workdir\tc11601_win64\src\core\sharedcache\SharedMetadataCacheMgr.cxx(94)
INFO - 2019/04/08-14:59:19.097 UTC - .UnknownClient.00001 - segmentPath [C:\Users\ch5000\AppData\Local\Temp\V11000.2.0.71_20190128.00\2440018629\Metadata\Version5.mem] [does not exist] - Teamcenter.MetaModel.sharedcache at D:\workdir\tc11601_win64\src\core\sharedcache\SharedMetadataCacheMgr.cxx(234)
ERROR - 2019/04/08-14:59:19.097 UTC - .UnknownClient.00001 - 515023: The enquiry ID is invalid.
ERROR - 2019/04/08-14:59:19.097 UTC - .UnknownClient.00001 - 515023: The enquiry ID is invalid. - Failed to download Metadata Cache File - Teamcenter.MetaModel.sharedcache at D:\workdir\tc11601_win64\src\core\sharedcache\SharedMetadataCacheMgr.cxx(414)
ERROR - 2019/04/08-14:59:19.097 UTC - .UnknownClient.00001 - 515023: The enquiry ID is invalid. - Failed in processDeployFile - Teamcenter.MetaModel.sharedcache at D:\workdir\tc11601_win64\src\core\sharedcache\SharedMetadataCacheMgr.cxx(245)

Contents of the error store:-
ERROR515023 The enquiry ID is invalid.

Re: 2- Tier or 4-Tier clients dont work: POM has not started

When I want to reply, it is always marked as spam, what Do I have to do?

Re: 2- Tier or 4-Tier clients dont work: POM has not started

The server has a 2-Tier client installation also and that is working fine. The

install -ayt

returns a "Site already installed". It is just the separate client computers that cannot connect.


I checked th tc_profilevars.bat and it was pointing to the correct server.


Trying to find a solution I did a full reinstall of the Server and Client on the Server computer, renaming the Server before that, to a different Name "teamcenter".

We have a large university network that is not fully accessible to me and I suppose the problem lies anywhere in there.

Now, after reinstalling the server and 2T client on the Server are working fine (as before). But still the 2T client installed on a different computer still cannot connect, the error Message is now different, "The inquiry ID is invalid".

Re: 2- Tier or 4-Tier clients dont work: POM has not started

Solution Partner Esteemed Contributor Solution Partner Esteemed Contributor
Solution Partner Esteemed Contributor
The client (workstation) isn't able to resolve the server name (Teamcenter). This is a DNS issue (network). To test it, open a cmd window on the client and "ping /4 Teamcenter" where "Teamcenter" is the name of your server. Since you are a university and likely won't be able to resolve the DNS issue then you'll need to resort to modifying the /etc/hosts file (on EVERY client that needs to connect to Teamcenter).

https://en.wikipedia.org/wiki/Hosts_(file)
https://www.onmsft.com/how-to/how-to-modify-your-hosts-file-in-windows-10-and-why-you-might-want-to

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