Skip to main content
B
23-Emerald III
BenLoosli23-Emerald III
23-Emerald III
January 13, 2023
Solved

Windchill fails to start as a service

  • January 13, 2023
  • 4 replies
  • 8969 views

After doing the upgrade to Windchill, now running 12.0.2.8, I am trying to follow the steps outlined in this CS article on running Windchill as a service.

Article - CS17799 - How to run Apache, Tomcat, Windchill Directory Server and Windchill as Microsoft Windows service in Windchill (ptc.com)

The build says it is successful but does issue warnings when running. 

PTC tech support sent me this CS article:

Article - CS357485 - After executing ant -f bin/gwt.xml command on Windchill shell throws warnings WARNING: An illegal reflective access operation has occurred in Windchill PDMLink (ptc.com)

However, When I go to start the service, it gives an error and will not start.

I can start Windchill manually from a command prompt, but that does no good if IT does a server reboot overnight and I have to manually restart Windchill.

Has anyone else had this issue with Windchill12.0? I did not have any issues with all prior versions of Windchill (7, 9. 9.1, 10, 11, 11.1) that I have installed.

Best answer by BenLoosli

Working with tech support, we finally identified the cause and have it fixed.

The registry settings under Apache had bad values for JavaHome and Jvm. For some reason they were pointing to <Windchill loadpoint>\{Java_home}\(the files needed). Corrected to point to c:\Program Files\Java\jdk-11.0.13 and then the jvm.dll.

Once I corrected these, Windchill starts as a service.

 

4 replies

R
rleir17-Peridot
17-Peridot
January 17, 2023

What are the warnings? What is the error?

B
23-Emerald III
BenLoosli23-Emerald IIIAuthor
23-Emerald III
January 17, 2023

Installed Windchill as a service, set to Automatic start and rebooted.

Windchill did not start.

Opened services and clicked on Windchill and pressed Start.

Got an error message:

Windows could not start the Windchill on the Local Computer.

For more information, review the System Event Log. If this is a

non-Microsoft service, contact the service vendor, and refer to

service-specific error code 1.

 

System Event log says Windchill has an Incorrect function.

HelesicPetr
22-Sapphire II
HelesicPetr22-Sapphire II
22-Sapphire II
January 17, 2023

Hi @BenLoosli 

 

Check the user who run the service.

I have had experience that the user does not have correct rights/access. 

The NTSERVICE user was used in the past but in Windchill 12.1+ it has been changed and I usually change the user to the NTSRVICE and the windchill service works. 

 

PS: the change of the service installation could be changed in the previous versions 12.0+. 

 

PetrH

B
23-Emerald III
BenLoosli23-Emerald IIIAuthor
23-Emerald III
January 17, 2023

All are being run from my 1 logon to Windows and I do have administrator privileges.

 

HelesicPetr
22-Sapphire II
HelesicPetr22-Sapphire II
22-Sapphire II
January 17, 2023

Hi @BenLoosli 

You can think that you have but my experience is different.

Try to set this one>

HelesicPetr_0-1673968183773.png

 

PetrH

P
Pascal_Brunet14-Alexandrite
14-Alexandrite
January 20, 2023

Hello,

 

i had similar problem in 12.0.0.3. I solved it by replacing local system by an administrator account. Check my original note i created last time it happened to me.

 

svc_plm is not an account i created myself on the server. It is an account created by our Server team in the Enterprise Active Directory: 

Pascal_Brunet_0-1674233164083.png

 

Hope it can help.

 

Best regards,

Pascal

 

 

B
23-Emerald III
BenLoosli23-Emerald IIIAuthorAnswer
23-Emerald III
February 8, 2023

Working with tech support, we finally identified the cause and have it fixed.

The registry settings under Apache had bad values for JavaHome and Jvm. For some reason they were pointing to <Windchill loadpoint>\{Java_home}\(the files needed). Corrected to point to c:\Program Files\Java\jdk-11.0.13 and then the jvm.dll.

Once I corrected these, Windchill starts as a service.

 

    Terms & ConditionsCookie settingsAccessibility statement