Article - CS25867

Replication fails with the error "wt.fv.replica - Configuration is not initialized for master site" in the Replica server log in Windchill PDMLink

Modified: 02-Sep-2025   


Applies To

  • Windchill PDMLink 9.1 to 13.0

Description

  • Replication fails with error in MethodServer log of Replica Site/Remote File Server
wt.fv.replica - Configuration is not initialized for master site
wt.fv.replica - This is probably due to the target folder not being enabled in the Vault Configuration GUI
  • Replica Server log, at startup, the following exception is observed:
Wed 7/13/11 22:55:54: Thread-1: ERROR : wt.fv.replica - Problem connecting to host. Message:[java.net.UnknownHostException: ***.com]
Wed 7/13/11 22:55:54: Thread-1: java.net.UnknownHostException: ***.com
  • Upload file to Replica Server fails, file server method server logs:
WARN  : wt.fv.replica  - Could not get host description for hostname.domain.com from cache.
Thu 3/30/17 15:01:47: TP-Processor4: WARN  : wt.fv.replica  - This could mean that the configuration information is out of date, or that the master site does not have the correct host/site name
Thu 3/30/17 15:01:47: TP-Processor4: ERROR : wt.fv.replica  - Configuration is not initialized for master site http://xxx/Windchill/servlet/WindchillGW
Thu 3/30/17 15:01:47: TP-Processor4: ERROR : wt.fv.replica  - This is probably due to the target folder not being enabled in the Vault Configuration GUI
Thu 3/30/17 15:01:47: TP-Processor4: TRACE : wt.fv.replica  - Closing bufferedInputStream
Thu 3/30/17 15:01:47: TP-Processor4: ERROR : wt.method.client.httpgw  -  MethodRequestHandler Exception: An exception occured while processing the request.
Thu 3/30/17 15:01:47: TP-Processor4: (wt.fv.replica.replicaResource/2) wt.util.WTException: Folder not found
  • MethodServer on Replica site is not able to start up with error:
wt.fv.replica  - Could not get host description for <java.rmi.server.hostname> from cache.
wt.fv.replica  - This could mean that the configuration information is out of date, or that the master site does not have the correct host/site name
wt.fv.replica  - Stop and start the replica method server or perform broadcast configuration for this site.
wt.fv.AbstractSiteStatusImpl  - WTException occurred adding vault MBeans in treeConfiguration info is either out of date or unavailable
(wt.fv.replica.replicaResource/5) wt.util.WTException: Configuration info is either out of date or unavailable
	at wt.fv.replica.StandardReplicaService.getAllVaultsForSite(StandardReplicaService.java:1317)
	at wt.fv.AbstractSiteStatusImpl.addOrUpdateVaultsOnReplica(AbstractSiteStatusImpl.java:392)
	at wt.fv.AbstractSiteStatusImpl.addOrUpdateVaults(AbstractSiteStatusImpl.java:385)
	at wt.fv.AbstractSiteStatusImpl.onStart(AbstractSiteStatusImpl.java:236)
	at wt.jmx.core.SelfAwareMBean.start(SelfAwareMBean.java:316)
	at wt.jmx.core.SelfAwareMBean.postRegister(SelfAwareMBean.java:486)
	at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.postRegister(DefaultMBeanServerInterceptor.java:1024)
	at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:974)
	at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:900)
	at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:324)
	at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:522)
	at wt.jmx.core.MBeanRegistry.registerMBean(MBeanRegistry.java:184)
	at wt.jmx.core.SelfAwareMBean.register(SelfAwareMBean.java:191)
	at wt.fv.AbstractSiteStatusImpl.getNewRegisteredInstance(AbstractSiteStatusImpl.java:144)
	at wt.fv.MasterReplicaDataBindingController.recieveDefaultThresholdFromMaster(MasterReplicaDataBindingController.java:249)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at wt.wrmf.delivery.StandardReceiverService.executeMethodWithPayload(StandardReceiverService.java:801)
	at wt.wrmf.delivery.StandardReceiverService.executeMethod(StandardReceiverService.java:606)
	at wt.wrmf.delivery.StandardReceiverService.processActionShippingItem(StandardReceiverService.java:1120)
	at wt.wrmf.delivery.StandardReceiverService.pickUpMessageBiDi(StandardReceiverService.java:455)
	at wt.wrmf.transport.httptransport.HTTPPipeAdapter.performPushInGeneral(HTTPPipeAdapter.java:617)
	at wt.wrmf.transport.httptransport.HTTPPipe.acceptHttpTransWithResump(HTTPPipe.java:207)
  • Download file from Replica Server fails with error: HTTP Status 500-MethodRequestHandler Exception
  • Replica site displays read only
  • Unable to start Replica Server while showing SERVLET ENGINE NOT RESPONDING
This is a printer-friendly version of Article 25867 and may be out of date. For the latest version click CS25867