Cancel
Showing results for 
Search instead for 
Did you mean: 

Teamcenter 8.3 - Reference set not changed error

Solution Partner Creator Solution Partner Creator
Solution Partner Creator

I'm working on upgrading a client's Teamcenter install and the first step performed was to duplicate their current server.  This includes TC8.3.3 and NX7.5.4  After the creating the new server, the clients production database was added and they started performing validation to make sure the duplication was successful.

 

The problem they have found is that when opening some of their assemblies in NX an error occurs stating "Reference Set Not Changed".  Then a list of sub parts are given with the message "The following reference sets were not changed to match that found in the Teamcenter product structure:"

 

Afer the list of parts the following message is given "This may be beacuse the component parts are not laoded yet or because the reference sets do not exist.  It is possible you mis-typed the reference set names when editing in Teamcenter."

 

This does not occur on the clients production system so I'm not sure why this it now occurs.  Any help is greatly appreciated.

2 REPLIES

Re: Teamcenter 8.3 - Reference set not changed error

Solution Partner Phenom Solution Partner Phenom
Solution Partner Phenom
Likely they modified Customer Defaults (NX) directly on the Production server so those modifications only live directly in UGII_ROOT_DIR on Prod? You may need to create a site.dpv from Prod and migrate it over to the cloned server. This is usually the case when a customer doesn't use NXcustom to store modifications to NX in a shared location.

Randy Ellsworth, Teamcenter Architect, Applied CAx, LLC
NX 11 | SW 2016 | Creo 4 | TcUA 11.4
Evaluating: AW 3.4

Re: Teamcenter 8.3 - Reference set not changed error

Solution Partner Creator Solution Partner Creator
Solution Partner Creator

Thanks Randy.  We beleive you are correct but have limited access to the production server so we weren't able to verify using the site preferences corrected the problem.  The client gave us the green light to continue with the upgrade since it's only a dry run.  For the production upgrade, we'll get the site preferences.