cancel
Showing results for 
Search instead for 
Did you mean: 

FCC failed to start or restart

Legend
Legend

Hello Team,

 

Thin client is working fine, But while running the Rich 4Tier Client I am getting FCC issue,

 

Manualy i tried to start FCC but not getting start, please refer below snaperror.png

 

Also FCCCache is folder also not generating in the User folder,

 

I tried clearing cache as well (TAO/RAC/Siemens)

 

FSC & Server manager is running fine. Please suggest

 

Regards,

Ganesh

8 REPLIES

Re: FCC failed to start or restart

Siemens Valued Contributor Siemens Valued Contributor
Siemens Valued Contributor

Do you see any error in the logs? How about setting FMS_HOME to nothing?

You can set it in portal.bat.

 

 

Best Regards

Projyal Dev

Re: FCC failed to start or restart

Legend
Legend

Please find the fcc log below,

and fms home is correctly set.

 

ERROR - None - 2016/12/21-07:28:27,010 UTC - at-uat-team - Unable to connect to origin server url: http://172.31.96.111:4544/configMultiSiteConfigRequest?client=192.168.1.243. Possible causes: incorrect URL, network problems, unavailable origin server, or forward proxy configuration problem (a direct connection was attempted) com.teamcenter.net.proxy.http.ProxiedHttpClient
com.teamcenter.net.proxy.http.DestinationException: Unable to connect to origin server url: http://172.31.96.111:4544/configMultiSiteConfigRequest?client=192.168.1.243. Possible causes: incorrect URL, network problems, unavailable origin server, or forward proxy configuration problem (a direct connection was attempted)
at com.teamcenter.net.proxy.http.ProxiedHttpClient.executeDirectConfig(ProxiedHttpClient.java:741)
at com.teamcenter.net.proxy.http.ProxiedHttpClient.httpConnect(ProxiedHttpClient.java:667)
at com.teamcenter.net.proxy.http.ProxiedHttpClient.tryDest(ProxiedHttpClient.java:632)
at com.teamcenter.net.proxy.http.ProxiedHttpClient.executeMethodInternal(ProxiedHttpClient.java:510)
at com.teamcenter.net.proxy.http.ProxiedHttpClient.executeMethod(ProxiedHttpClient.java:326)
at com.teamcenter.net.proxy.http.ProxiedHttpClient.executeMethod(ProxiedHttpClient.java:271)
at com.teamcenter.fms.clientcache.FSCConfigReader.getConfigFromFSC(FSCConfigReader.java:171)
at com.teamcenter.fms.clientcache.FSCConfigReader.getMultiSiteFCCDefaultsFromFSC(FSCConfigReader.java:292)
at com.teamcenter.fms.clientcache.FCCConfigManager.getFSCConfigString(FCCConfigManager.java:309)
at com.teamcenter.fms.clientcache.FCCConfigManager.getConfigFromParentFSC(FCCConfigManager.java:261)
at com.teamcenter.fms.clientcache.FCCConfigManager.getFSCConfig(FCCConfigManager.java:224)
at com.teamcenter.fms.clientcache.FCCConfigManager.getNewConfiguration(FCCConfigManager.java:131)
at com.teamcenter.fms.clientcache.FCCConfigManager.getConfig(FCCConfigManager.java:94)
at com.teamcenter.fms.clientcache.FMSClientCache.config(FMSClientCache.java:325)
at com.teamcenter.fms.clientcache.FMSClientCache.run(FMSClientCache.java:170)
at java.lang.Thread.run(Unknown Source)
Caused by: java.net.ConnectException: Unable to connect to origin server url: http://172.31.96.111:4544/configMultiSiteConfigRequest?client=192.168.1.243. Possible causes: incorrect URL, network problems, unavailable origin server, or forward proxy configuration problem (a direct connection was attempted)
... 16 more
INFO - None - 2016/12/21-07:28:27,010 UTC - at-uat-team - TcModelEventManager shutting down.
INFO - None - 2016/12/21-07:28:27,010 UTC - at-uat-team - TCCS shutting down TcServerProxy.
INFO - None - 2016/12/21-07:28:27,025 UTC - at-uat-team - TcModelEventManager shutting down.
INFO - None - 2016/12/21-07:28:27,025 UTC - at-uat-team - TcModelEventManager Thread Manager waiting for TcMEM threads to stop.
INFO - None - 2016/12/21-07:28:27,025 UTC - at-uat-team - TcServerProxy Thread Manager waiting for TSP threads to stop.
INFO - None - 2016/12/21-07:28:27,338 UTC - at-uat-team - TcModelEventManager shutting down.
INFO - None - 2016/12/21-07:28:27,338 UTC - at-uat-team - All TcMEM threads successfully stopped.
INFO - None - 2016/12/21-07:28:27,354 UTC - at-uat-team - All TSP threads successfully stopped.
INFO - None - 2016/12/21-07:28:27,650 UTC - at-uat-team - TCCS shutdown: All applications are shutdown.
INFO - None - 2016/12/21-07:28:27,650 UTC - at-uat-team - Exiting TCCS ...
INFO - None - 2016/12/21-07:28:27,650 UTC - at-uat-team - TCCS JVM Shutdown detected (hookShutdown).
INFO - None - 2016/12/21-07:28:27,650 UTC - at-uat-team - TCCS process lock released. Shutdown complete (hookShutdown).

Re: FCC failed to start or restart

Siemens Valued Contributor Siemens Valued Contributor
Siemens Valued Contributor

Looks like it is not able to connect to the FSC.

 

Please check the following:

  1. If you need to set proxy information. Set it in FSC.properties file.
  2. Can you actually ping the FSC server from your machine?
  3. Do you have to use https?

 

Best Regards

Projyal Dev

Re: FCC failed to start or restart

Legend
Legend

Yes it was connection problem and was unable to access the http:\\{server IP}:4544

now its accessible and fcc started

thanks,

 

regards,

Ganesh

Re: FCC failed to start or restart

Experimenter
Experimenter

hello, I met the same problem .  It was unable to access the http:\\{server IP}:4544. I tried a lot ,but failed.Could you tell  me how to solve  with this problem? Thanks very much.

Re: FCC failed to start or restart

Legend
Legend

You need to enable the Port 4544 for the server. so that all clients can connect to server

Re: FCC failed to start or restart

Experimenter
Experimenter

Hey, I am too having same issue, could anyone please tell me how to restart the FSC from services. For me it doesn't starts and sends a messages to screen, it failed. And how to enable port. Thanks in Advance

Re: FCC failed to start or restart

Experimenter
Experimenter

Thanks for your patience! I found that the client computer which can register normally couldn't ping port 4544successfully (telnet 192.168.0.21 4544) but can read the infomation from internet (get read infomation from http://pdmserver:4544/configMultiSiteConfigRequest).On the other hand, some normal client computers can't ping port 4544 but can read  infomation from http://pdmserver:4544/configMultiSiteConfigRequest. I am very confused. I have set the 4544 port on the server. Could you give me a hand to analyze that?Looking forward to receiving your suggestions.Thank you very much.

Yours 

xiaobai