1. Home
  2. Support
Article - CS148181

Windchill could not start up - nothing happens for "windchill start" command OR not all of MethodServer/BackgroundMethodServer started in Windchill

Modified: 22-Oct-2025   


Applies To

  • Windchill PDMLink 9.1 to 13.1

Description

  • Windchill Start does nothing
    • No ServerManager or MethodServer logs generated (or only one ServerManager*-GC.log file 0 bytes in size)
  • Only one or some of the MethodServer or BackgroundMethodServer can start up.
  • Not all of the MethodServer or BackgroundMethodServer can start up.
  • It starts only MethodServer or only BackgroundMethodServer randomly. 
  • Solr server is not able to start up with no logs generated under <SolrServer>/solr/server/logs, only GC log file with 0 bytes in size.
  • windchill wt.auth.Authentication command throws error:
wt.util.WTRemoteException: Unable to invoke remote method; nested exception is:
wt.util.WTRemoteException: Unable to locate method server; nested exception is:
wt.util.WTRemoteException: Unable to locate method server; nested exception is:
wt.util.WTRemoteException: Unable to get server; nested exception is:
wt.util.WTRemoteException: Unable to locate server manager; nested exception is:
java.rmi.ConnectException: Connection refused to host: <hostname>; nested exception is:
java.net.ConnectException: Connection refused: connect​
  • Simple command like java -version may throw error
Error occurred during initialization of VM
Could not reserve enough space for object heap
Could not create the Java virtual machine.
  • Following article CS26192 and running ServerManager launch command shows error:
Error occurred during initialization of VM
Could not reserve enough space for object heap
Could not create the Java virtual machine.
  • Replica server unable to start after installation
  • Windchill failed to start up after upgrading Operation System, below error occurring in Methodserver.log  
    ERROR [wt.jmx.core.SharedScheduledExecutor.worker] wt.jmx.notif.serverManager.unavailable  - Time=2025-10-17 18:17:22.848 +0800, Name=ServerManagerFailureNotifier, SourceObjectName=com.ptc:wt.subsystem=Monitors,wt.monitorType=ServerManager, class=class javax.management.Notification, type=wt.manager.jmx.ServerManagerMonitorMBean.PingServerManager.failure, message=ServerManager has stopped, JVM Name=13576@TP2SVR01, ServerManager Monitor=[AllowInitialAutoStartup=false,AvgPingResponseSeconds=0.0015062833333333331,FailedPingsUntilRestart=0,LastPingResponseSeconds=0.0014149,LastResetTime=,LoggerLevel=INFO,LoggerName=wt.manager.jmx.ServerManagerMonitor,PercentageServerManagerUpTime=85.71428571428571,PingIntervalSeconds=90,ServerManagerPings=7]
WARN  [wt.jmx.core.SharedScheduledExecutor.worker] wt.manager.jmx.ServerManagerMonitor  - ServerManager has stopped
...
WARN  [RMI Unreferenced-57] wt.method.server  - Uncaught exception on thread:
  • Can't access to Windchill from client with error: 
    Service Unavailable
This is a printer-friendly version of Article 148181 and may be out of date. For the latest version click CS148181