Cancel
Showing results for 
Search instead for 
Did you mean: 

Re: Active Workspace 3.3 Install Error: generate_metadata_cache

Siemens Creator Siemens Creator
Siemens Creator

Thank you for your information, but I still have failures in all of your checks.

 

fccstat -start command failed 

 

FMS_HOME is set correctly

I have no other environments installed

 

I tried pinging the FSC and i got an error and also tried to validate the IP, but got a webpage cannot be displayed error. 

I have attached my fmsmaster file which has my subnet and mask.

I am still not getting past this error, I am not sure what needs to be changed in order to fix my fcc and FSC.

 

Re: Active Workspace 3.3 Install Error: generate_metadata_cache

Solution Partner Phenom Solution Partner Phenom
Solution Partner Phenom
Obviously, since the checks failed then you have a communication problem. From reviewing previous entries, you server is called tc113hylaJimmy (192.168.80.133) and your client (192.168.80.134) which fails to start FCC. Assuming that you can ping 192.168.80.133 from the client (192.168.80.134) which is why you changed the server name to an IP address in the FMS Master? I assume you cannot ping tc113hylaJimmy from the client. This could be a name resolution issue.

You can confirm if this is a name resolution issue by:
Edit C:\Windows\System32\drivers\etc\hosts (no extension)
Add 192.168.80.133 tc113hylaJimmy
Add 192.168.80.134 <your client name>
Save and close

You should be able to ping tc113hylaJimmy from the client now.

Try manually starting the FCC again. Send the log or screen shots of any failure.

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

Re: Active Workspace 3.3 Install Error: generate_metadata_cache

Siemens Creator Siemens Creator
Siemens Creator

I added the two IPs and Hostnames to the host file and they were both still not able to be pinged.

 

I tried running fccstat -start again and it failed. 

 

I attached the only log that generated which is my tccs log.

Re: Active Workspace 3.3 Install Error: generate_metadata_cache

Solution Partner Phenom Solution Partner Phenom
Solution Partner Phenom
The log shows that your client IP address has changed to 192.168.203.128. The IP addresses for client (and server?) appear to be a moving target (DHCP). You need to be able to ping the server from the client before running anything where the two have to talk. Right now you're dialing the wrong number. I assume you know how to use "ipconfig" to find your IP address (same on the server) then edit etc\hosts on the client to match. Lets get ping working.

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

Re: Active Workspace 3.3 Install Error: generate_metadata_cache

Solution Partner Experimenter Solution Partner Experimenter
Solution Partner Experimenter

For some reason my account was deactivated so sorry for the late response with a different account.

 

I have updated the host file with the right IP and am now able to ping the client 192.168.203.128 and fccstat -start is now working correctly. 

 

I am still unable to ping the server 192.168.80.133, but i can ping the hostname for the server tc113hylaJimmy.

And when I ran the TEM again it still fails at the generate metadate cache step.

 

 

Here is the log from the error:

 

INFO - 2018/01/30-17:43:40.822 UTC - NoId - ******* FSC C Proxy functions will invoke the cURL ******** - Teamcenter.Organization.sa at D:\workdir\tc113w0509_64\src\core\sa\fscinterface.cxx(1062)
INFO - 2018/01/30-17:43:41.200 UTC - NoId - The FMS SiteID is -1894135600 - Teamcenter.Organization.sa at D:\workdir\tc113w0509_64\src\core\sa\filetickets.cxx(1004)
WARN - 2018/01/30-17:43:41.200 UTC - NoId - Preference Ticket_Expiration_Interval set to an invalid value. Default of 28800 seconds used. - Teamcenter.Organization.sa at D:\workdir\tc113w0509_64\src\core\sa\filetickets.cxx(1360)
ERROR - 2018/01/30-17:44:02.775 UTC - NoId - FSC_Send error on verifyFileExists step @/verifyFileExists2/nvargs/ , <fsc_error> 7 : CURLE_COULDNT_CONNECT: The destination server is offline or unreachable on this network. - Teamcenter.Organization.sa at D:\workdir\tc113w0509_64\src\core\sa\fscadmin.cxx(757)
ERROR - 2018/01/30-17:44:02.854 UTC - NoId - 14112: Unable to create file D:\Siemens\TC_Volume\dba_5a552ed4\10e3000_unk_cve00n87d098s.bin - ERROR: Metadata Cache Generation Failed. - Teamcenter.MetaModel.sharedcache at D:\workdir\tc113w0509_64\src\core\sharedcache\MetadataVersion.cxx(548)
ERROR - 2018/01/30-17:44:02.854 UTC - NoId - 14112: Unable to create file D:\Siemens\TC_Volume\dba_5a552ed4\10e3000_unk_cve00n87d098s.bin - MetadataVersion::makeCacheDataset failed. - Teamcenter.main at D:\workdir\tc113w0509_64\src\core\main\generate_metadata_cache_main.cxx(197)
INFO - 2018/01/30-17:44:02.932 UTC - NoId - The type cache map is de-initialized due to logout - Teamcenter.CoreModelGeneral.tccore at D:\workdir\tc113w0509_64\src\core\tccore\imantype_itk.cxx(1099)
INFO - 2018/01/30-17:44:02.963 UTC - NoId - The type cache map is de-initialized due to logout - Teamcenter.CoreModelGeneral.tccore at D:\workdir\tc113w0509_64\src\core\tccore\imantype_itk.cxx(1099)
NOTE - 2018/01/30-17:44:02.963 UTC - NoId - Among [1] calls for POM_refresh_instances we have [0] misses and [0] new loads - Teamcenter.POM at D:\workdir\tc113w0509_64\src\foundation\pom\pom\pom_most_interface_funs.cxx(6792)
INFO - 2018/01/30-17:44:03.074 UTC - NoId - POM shutdown complete. - Teamcenter.POM at D:\workdir\tc113w0509_64\src\foundation\pom\pom\pom_init.cxx(344)
POM enquiries statistics: created 244, undone 0, deleted 199, queried 806
@@@ End of session Tue Jan 30 12:44:05 2018 Eastern Standard Time

 

Re: Active Workspace 3.3 Install Error: generate_metadata_cache

Solution Partner Phenom Solution Partner Phenom
Solution Partner Phenom
When you ping the server hostname what does it show for the IP address? My guess is that the server changed IP (due to DHCP) which is why the FSC cannot be reached and is causing all kinds of issues. The IP address is specified in the FMS Master instead of the hostname. Best practice is to have a fixed IP address for servers but we can deal with that later.

You can try changing the IP address in the FMS Master to the hostname (since you're able to ping it). Then restart the FSC service after changing the FMS Master. Note: Make changes for the IP addresses in your client etc\hosts file as needed by pinging them occasionally (especially after reboots or disconnecting from a docking station and reconnecting - things that trigger DHCP to assign new addresses). If the IP changes then you'll need to restart your server services to avoid issues.

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

Re: Active Workspace 3.3 Install Error: generate_metadata_cache

Solution Partner Experimenter Solution Partner Experimenter
Solution Partner Experimenter

When I ping the hostname the reply I get is from ::1:  ?

 

After changing the IP to the hostname in the FSC Master file my TEM deployment worked with no issues !

 

Thanks for all your help. I really appreciate it !

Re: Active Workspace 3.3 Install Error: generate_metadata_cache

Solution Partner Phenom Solution Partner Phenom
Solution Partner Phenom
The ::1 is IPv6 for localhost. Same as 127.0.0.1 for IPv4. You may want to change the FMS Master from subnet/mask to CIDR notation. Replace the single clientmap subnet mask
<clientmap subnet="127.0.0.1" mask="0.0.0.0">
<assignedfsc fscid="FSC_tc113hylaJimmy" priority="0" />
</clientmap>

To CIDR and include both IPv4 and IPv6 notation...

IPv4 default
<clientmap cidr="0.0.0.0/0">
<assignedfsc fscid="FSC_tc113hylaJimmy" priority="0"/>
</clientmap>

IPv6 default
<clientmap cidr="0::0/0">
<assignedfsc fscid="FSC_tc113hylaJimmy" priority="0"/>
</clientmap>

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