Skip to main content
12-Amethyst
January 17, 2023
Solved

xconfmanager is not recognized

  • January 17, 2023
  • 1 reply
  • 2558 views

We updated to Windchill 12 a while back and I haven't had to change any properties since then. Now when I launch Windchill Shell and type in an xconfmanager command, I get back the error of " xconfmanager is not recognized as an internal or external command, operable program or batch file. 

 

I have looked at our site.xconf and it still appears to point out the correct windchillconfigurator.xconf file (which does exist)

<ConfigurationRef xlink:href="utilities/wca/conf/windchill/windchillconfigurator.xconf"/>

 

Can anyone give some guidance as to what else might cause this? I have gone through this article PTC Windchill Help Center

 

Best answer by mmeadows-3

That is a Windows shell error.  It means Windows doesn't know where the xconfmanager command resides.  Check your path value in the shell to ensure it includes the bold entries per your Windchill load point.

echo %path%
D:\PTC\Windchill_12.0\Windchill\bin;D:\PTC\Windchill_12.0\Windchill\ant\bin;D:\PTC\Windchill_12.0\Java\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;...

 

We can also see this if Java isn't in the path for the Windchill shell command.  We don't set the Windows environment variables.  Just do it in the shortcut for launching the Windchill shell.

 

Shortcut example

Target: D:\PTC\Windchill_12.0\Windchill\bin\windchill.exe -w "D:\PTC\Windchill_12.0\Windchill" --java="D:\PTC\Windchill_12.0\Java\bin\java.exe" shell

Start In: D:\PTC\Windchill_12.0\Windchill

 

Still debugging?  To see what is really going on, from a CMD shell:

pushd D:\PTC\Windchill_12.0\Windchill\bin

windchill --verbose shell

 

1 reply

16-Pearl
January 17, 2023

That is a Windows shell error.  It means Windows doesn't know where the xconfmanager command resides.  Check your path value in the shell to ensure it includes the bold entries per your Windchill load point.

echo %path%
D:\PTC\Windchill_12.0\Windchill\bin;D:\PTC\Windchill_12.0\Windchill\ant\bin;D:\PTC\Windchill_12.0\Java\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;...

 

We can also see this if Java isn't in the path for the Windchill shell command.  We don't set the Windows environment variables.  Just do it in the shortcut for launching the Windchill shell.

 

Shortcut example

Target: D:\PTC\Windchill_12.0\Windchill\bin\windchill.exe -w "D:\PTC\Windchill_12.0\Windchill" --java="D:\PTC\Windchill_12.0\Java\bin\java.exe" shell

Start In: D:\PTC\Windchill_12.0\Windchill

 

Still debugging?  To see what is really going on, from a CMD shell:

pushd D:\PTC\Windchill_12.0\Windchill\bin

windchill --verbose shell

 

7-Bedrock
January 17, 2023

May need to create a new shortcut for the Windchill shell - see this article.

https://www.ptc.com/en/support/article/CS158529?source=search

 

12-Amethyst
January 17, 2023

I tried to create a new shortcut and get the attached java error. Here is the shortcut path I am using:

D:\PTC\Windchill_12.0\Windchill\bin\windchill.exe -w "D:\PTC\Windchill_12.0\Windchill" --java="C:\Program Files\Amazon Corretto\jre8\bin\java.exe" shell

 

My "echo %path%" just has these two paths and then the normal system32 and powershell paths:

D:\ptc\Windchill_12.0\Java\jdk11.0.16_8\bin;C:\Program Files\Amazon Corretto\jdk1.8.0_342\bin;