Community Tip - Want the oppurtunity to discuss enhancements to PTC products? Join a working group! X
https://www.ptc.com/en/support/article/CS409940?source=search
You didn't say what version but here is a few more articles from older versions:
https://www.ptc.com/en/support/article/CS327186?source=search
https://www.ptc.com/en/support/article/CS374938?source=search
Let me know which one seems like the cause.
I am trying to upgrade to 12.1.2. The error I am getting is different than these articles, I have verified these fixes.
I also have a similiar issue. did you manage to find a solution . Upgrading from 11.2 to 12.1
Hi @Lufunofuno
The error seams that the manager is trying to remove some license group.
So before the upgrade remove all users from licenses groups and try it again.
PetrH
Hi Petr,
Added all users to the particpant admin and manully removed them from each license group. I also did this for other groups.
However, ther issue is still there. I am wondering if i need to manullyfind and delete the memebershiplink from SQL side.
Update in the issue,
Having a closer look at that the error, I picked up that the upgrade manager was trying to remove membership for the Base, Advanced and Premium License. It seems there was something wrong in the database, specifically the membership link table that cause it to fail. The first sign to look out for in this kind error is when the Thingworx view and contribute groups are disconnected.
I opted for a double upgrade: 11.2 >12.0 >12.1. This was successfully run during the test upgrades
I found that I had to fix the disconnected groups in the source before exporting the data before each upgrade pass. I think this is quite Bizzare and PTC are not able to point to what the isse is exactly and why I cant fix it once and for all.
The final workaround upgrade process from 11.2 to 12.1 that I used:
**This will be in a system with both 12.0 and 12.1 installed . they can run concurrently and each has its own services except the Ldap and Database
1. Run WinDU
2. Run WinRU and fix flagged issues
3. Run WinDU again ( seems to register entries in the database that the issues were resolved- I could be wrong)
4. Export Database base and ldap (if targe has its own ldap)
5. Add customisation to target and run make jar rebuilds for 12.0
6. import data to database and ldap
7 Run Upgrade manager first pass to 12.0
8 Run post uograde tasks to validate data
9. back up current database and ldap( create a checkpoint half
10 Run steps 1- 3 for the new source(12,0)
11. Run step 5 on the new targer 12.1
12. Run Upgrade Manager for 12.1
Pay careful attention to what you start or stop since you have two windchill installations on the same server. I advise that you use CMD to run windchill shell from each installation.
If anyone managed an easier process, please do let me know.
Hi @SK_10990210,
I wanted to follow up with you on your post to see if you received a solution for this topic.
If so, please mark the appropriate reply as the Accepted Solution or if you managed to resolve this by yourselves, please document the solution in this topic for the benefit of other members who may have the same question.
Of course, if you have more to share on your issue, please let the Community know so that we can continue to support.
Thanks,
Community Moderation Team.