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

Windchill 11.0 M030 CPS12 showing different versions of components in different scenarios!

Re: Windchill 11.0 M030 CPS12 showing different versions of components in different scenarios!

CPS11 is a bit of a mess.  PTC really should have incremented the build number up (M031, M040, or something else.)  Critical patch set CPS11 cannot be installed without also downloading additional CDs (WDS, Info*Engine, JDK, Services, etc.)  This goes directly against how a CPS is supposed to work.  The articles in the knowledge base and the installation guides all say that a CPS is entirely self-contained and does not require any other downloads.  For CPS11 that is definitely not the case.  (I already went round and round with PTC on this.)

Re: Windchill 11.0 M030 CPS12 showing different versions of components in different scenarios!

Just remember that it is PTC and never trust what they say they will do!

They write the rules on what they will include in patches.

 

My problem with CPS' being self contained is I do not have internet access for my production system and I have to break up the CPS download into DVD-sized chunks, burn DVDs, then load them onto the production system. No wonder I do not normally install them! Plus with the breaking for CreoView when I did the first CPS (and PTC has no solution for my system) I will avoid CPS patches as much as possible. I had to do this one for the change to HTML code from Java for file vaults.This should not have been done at a CPS, either, as it changed functionality!

 

Re: Windchill 11.0 M030 CPS12 showing different versions of components in different scenarios!

Will they be documenting the deficiencies there?

Re: Windchill 11.0 M030 CPS12 showing different versions of components in different scenarios!

Nope.  The official answer was, "...once you have those CPS11 module installed, future CPS update will not ask for any additional CD’s during the staging area unless there are some other major module rebuilt."  (emphasis mine)

 

Again, this directly contradicts the article on how critical patch sets are supposed to work and the installation guides.

CS149102.png

 

By the way, CPS12 has this same problem.  See https://www.ptc.com/en/support/article?n=CS292433

Re: Windchill 11.0 M030 CPS12 showing different versions of components in different scenarios!

Well, most of the articles PTC got are root cause analysis result in various environments and in older versions. Unfortunately, they also update these articles application versions to include all latest versions without confirming if the issue persist or it is a variant of same issue. Result: Many articles are not valid for latest versions of PTC products.

 

However, I'm still waiting for PTC answer on this particular issue. When WC11.0 M030 CPS12 is installed in a new system using PSI came bundled with CPS12, PSI asks for installer for PDMLink with datecode M030 CPS12.

 

But when WC11.0 M030 CPS12 is installed as an update over an earlier version (M030 CPS10 or earlier), PSI doesn't ask for installer for PDMLink with datecode M030 CPS12. Apparently the changes in PDMLink with datecode M030 CPS12 is not applied in this case.

Re: Windchill 11.0 M030 CPS12 showing different versions of components in different scenarios!

From the testing I've done so far it would appear that PDMLink is never updated.  Whatever version was originally installed is what it remains regardless of which CPS is later installed.

 

The M030-CPS11 "release" is a full recut to add support for Windows Server 2016.  Apparently this newer version of PDMLink is not required by the CPS11 or CPS12 critical patch sets.

 

Please let us know what tech support has to say. 

Re: Windchill 11.0 M030 CPS12 showing different versions of components in different scenarios!


@TomU wrote:

From the testing I've done so far it would appear that PDMLink is never updated.  Whatever version was originally installed is what it remains regardless of which CPS is later installed.

 


Right, that's what I observed.

 

Did you try installing Windchill using PSI coming bundled with CPS11 or CPS12? Both installs PDMLink with datecode M030 CPS11. It's odd from any angle to keep different versions of PDMLink based on the installation path chosen.

 


@TomU wrote:

 

Please let us know what tech support has to say. 


Sure, I'll inform once tech support responds, which strangely didn't happen still.

Re: Windchill 11.0 M030 CPS12 showing different versions of components in different scenarios!

Clean install of 11.0 M030-CPS11

Windchill 11.0 M030-CPS11 Install.PNG

 

Same 11.0 M030-CPS11 system after updating to CPS12

Windchill 11.0 M030-CPS12 Update.PNG

 

Clean install of 11.0 M030-CPS11 using the CPS12 installer

Windchill 11.0 M030-CPS12 Install.PNG

 

I'm getting ready right now to apply CPS12 to another system that was originally installed using F000 and has since been updated to CPS11.  Here's the before picture:

Windchill 11.0 M030 Before CPS12 Update.PNG

Re: Windchill 11.0 M030 CPS12 showing different versions of components in different scenarios!

No change.  PDMLink stayed at F000.

Windchill 11.0 M030 After CPS12 Update and Patch.PNG

Re: Windchill 11.0 M030 CPS12 showing different versions of components in different scenarios!

Finally I got response from PTC. They confirmed that it's completely Okay to go ahead with this anomaly though there are lot not answered by them.