Windchill ODATA

[AP_14462145]

I am using Windchill PDMLink Release 13.1 and Datecode with CPS 13.1.2.0

We installed Windchill PDMLink 13.1 using the PTC Solution Installer (PSI). The installation completed successfully and the Windchill application URL was accessible and working on Day 1.After restarting the server on Day 2, Windchill fails to start and the application returns HTTP 500 errors. The MethodServer does not initialize correctly.During startup, we consistently encounter the following exception:org.springframework.beans.factory.BeanCreationException: Cannot find class com.ptc.odata.windchill.entity.cache.ODataDataSourceServiceThe missing class is referenced in:Windchill/codebase/config/mvc/odataUICore-configs.xml.This indicates that the Windchill OData UI Core / REST-related module JARs are missing or were not installed correctly. The configuration XML exists, but the corresponding OData classes are not present on the classpath, suggesting a partial or inconsistent installation.We attempted recovery steps including server restart, cache cleanup, and rerunning the PTC Solution Installer. However, when attempting to update or repair the installation, PSI only allows the “New Product Installation option and does not detect or support repair of the existing installation.


Here are the errors that I faced
Exception " org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerMapping': Cannot find class [com.ptc.odata.windchill.entity.cache.ODataDataSourceService] for bean with name 'odata.dataSourceService' defined in file [C:\PTC\Windchill_13.1\Windchill\codebase\config\mvc\odataUICore-configs.xml] Related cause: org.springframework.beans.factory.CannotLoadBeanClassException: Cannot find class [com.ptc.odata.windchill.entity.cache.ODataDataSourceService] for bean with name 'odata.dataSourceService' defined in file [C:\PTC\Windchill_13.1\Windchill\codebase\config\mvc\odataUICore-configs.xml]" We request guidance on identifying the missing Windchill/OData modules, whether the issue can be repaired without a full reinstall, or if a clean uninstall and reinstall is required, along with the recommended procedure.

[TDT]

Hi @AP_14462145,

Could you check whether there are any errors in the installation logs?

[AP_14462145]

Hi @TDT 

Yes, we reviewed the installation and runtime logs. There are no fatal errors during Windchill startup, and services start successfully. However, we do see runtime errors when accessing the UI.

In the MethodServer logs, we observe OData-related BeanCreationException errors due to a missing OData class, and we also see Solr index server ping failures (connection refused on port 8085 – sanitized).

ERROR wt.index.StandardIndexPolicyManager -" Exception while pinging the index server
Server refused connection to Solr index server on port 8085"

Thank you

[TDT]

I would suggest placing the missing/incorrect OOTB JAR files in the required location and verifying whether the server starts without any errors.

If the issue persists, I would recommend proceeding with a clean reinstallation.

[AP_14462145]

Thank you for the suggestion. We verified the classpath under codebase/WEB-INF/lib and confirmed that while restWeb.jar is present, no OData-specific OOTB JARs are available. The missing class com.ptc.odata.windchill.entity.cache.ODataDataSourceService is not found in any deployed JARs, which aligns with the runtime BeanCreationException and the incomplete OData REST Services status shown in windchill version.

We also attempted to recover or upgrade the missing OData/REST components using the PTC installer. However, the installer does not allow repairing or adding the missing module to the existing installation and instead forces selection of a new product installation, rather than an upgrade or component recovery. This is preventing us from restoring the missing OOTB modules through the installer in the current setup.

Please let us know if there is a supported way to repair or re-register missing OData/REST components without proceeding with a full new product installation.