cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Community Tip - Did you get called away in the middle of writing a post? Don't worry you can find your unfinished post later in the Drafts section of your profile page. X

"ptcstatus" Fails

dgschaefer
21-Topaz II

"ptcstatus" Fails

Creo 2, M230

When I open a command prompt and try to run "ptcstatus" I get this:

'ptcstatus' is not recognized as an internal or external command,

operable program or batch file.

I've never had issues with that before, how do I fix it?


This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.
--
Doug Schaefer | Experienced Mechanical Design Engineer
LinkedIn
1 ACCEPTED SOLUTION

Accepted Solutions
TomU
23-Emerald IV
(To:dgschaefer)

Either run it from the directory ptcstatus.bat is located in (bin directory) or add the bin directory to your Windows PATH environment variable.

View solution in original post

5 REPLIES 5
TomU
23-Emerald IV
(To:dgschaefer)

Either run it from the directory ptcstatus.bat is located in (bin directory) or add the bin directory to your Windows PATH environment variable.

dgschaefer
21-Topaz II
(To:TomU)

I added it to my path variable and all is good.

I've never had to do so before with any other install, any idea why the install would fail to do it automatically?

--
Doug Schaefer | Experienced Mechanical Design Engineer
LinkedIn
TomU
23-Emerald IV
(To:dgschaefer)

No, I don't know why.  None of the more recent versions seem to modify the PATH variable anymore.

TomU
23-Emerald IV
(To:dgschaefer)

This article acknowledges the issue, but I'm not sure the statement in the resolution is correct.  I'm running Creo 3.0 M100 and it definitely did not modify the PATH variable after installation.

https://support.ptc.com/appserver/cs/view/solution.jsp?n=CS101755

There is another mention here:  https://support.ptc.com/appserver/cs/view/solution.jsp?n=CS161460

dgschaefer
21-Topaz II
(To:TomU)

I'm running Creo 2 M230 and it did not write the path statement. so saying that post M130 it's resolved is not correct.

--
Doug Schaefer | Experienced Mechanical Design Engineer
LinkedIn
Top Tags