Windchill 11.0 M030 CPS14 running HTTPS
Issue occour with:
So, I cannot confirm that the issue only exist for HTTP... At least not for our specific Windchill version.
@aacciano3, Yes, that is correct. Edge (Chromium) version 83 is affected as well. I guess, we can assume that all Chromium based browsers are affected.
I tried today with the latest realese of Chrome 83.0.4103.116 on Windchill 11.1 M010 and the issue doesn't occour.
In my case Chrome 83.0.4103.116
on Windchill 11.0 M030 CPS15 the issue is reproducible.
on Windchill 11.1 M020 CPS08 the issue is reproducible.
on Windchill 11.1 M020 CPS13 the issue is reproducible.
all versions are on HTTP.
@DeviVijayakumar Ist that confirmed, that no patch will be provided until the next CPS release? That can't be true, or?
I cannot confirm that it is working in HTTPS.
The issue occurs in both HTTP and HTTPS.
The issue occures in Google Chrome 83.x and 84.x (beta) and in MS Edge 83.x
@aacciano3 @KimH - I only have one user that is on the new Edge and this happened to them. If I cleared his cache and then had him open the In Private browser for Edge he has no problems now. We even closed it out and redid it a few times to make sure that it would still work. I'm wondering if we need to switch to Waterfox/Firefox. I heard that Firefox and Chrome were being mentioned as browsers of choice for Windchill 12.
@BrianToussaint , interesting that you can get it to work in Edge 83, by clearing the cache and starting in "In Private Mode". Unfortunately I am not able to reproduce this. It still does not work here.
Can you be more specific about the steps you have taken?
@KimH All I had the user do was delete all his history and related items from Edge. Close Edge and then he right clicked on the Edge icon in the task bar and selected to use the In Private browser. He then opened Windchill and started working. I had him try a CN multiple times through the point of failure that he was having in normal Edge. Then we closed it and tried again. I cannot get it to work that way in Chrome though. Sorry that I do not have Edge 83 to provide screenshots.
Thanks @BrianToussaint , I will try to play around some more.
I guess, that as soon as the user opens Edge in a normal Window, it will be broken again? At least until the cache is cleared and Edge is started "In Private" again - Correct?
@KimH - that would be my guess. Fortunately I only have one user on that browser right now so they know to open it in "In Private".
R&D has been working on this with priority and has identified a potential fix now. The fix is currently being tested. After adequate verification, we'll look into back-porting to older supported releases based on technical and other considerations.
All of you have been testing various use-cases - A list of use-cases to test from this group will help speed up the verification. Thanks!
Issue here with:
Some other use cases that may or may not be mentioned in this are:
Does not Work in following:
Above WC versions don't work in browsers:
Tried to no effect:
Thankfully still works in IE!
Yes. While the software versions are helpful, I was also looking for the UI scenarios (like the Change Notice example). Thanks for checking back.
I have many UI examples I can show you.
If you would like contact me, all the details are on C15427851.
I think I will have a hard time justifying to my management team, that we need to apply a Windchill update or maybe an upgrade project to fix an issue that occurs after an update to a web browser.
@DeviVijayakumar, It will be highly appreciated if you supply some more information about the root cause to this issue.
And by the way... I just tested the newest official build of Edge 83.0.478.54, which also the issue.
This is apparently a bug in the Chromium engine (Status of their bug - fixed in Chrome 85.0.4182.0)
According to SPR 10134786 it will be fixed for all Windchill Version in the next CPS!
the only problem we have is, that CPS 14 for Windchill 11.1 will be released end of July. That‘s in one month! So I guess all customer need to switch to Firefox or Mac Safari 🥳
Assuming X-26 = 11.0 it looks like CPS19 will fix the issue, but we have to wait 2 months for the release. On top of that we will have to buy extended support 😞
I hoped for a simple patch to solve this.
Anyway, is it confirmed that this is a Windchill issue and not something that eventually also will find its way to Firefox, if we switch browsers to get a quick fix?
Can somebody briefly describe the root cause for my understanding?
Same error happening for our user here.
Windchill 11.0 M030 CPS 06
Running in HTTPS
@DeviVijayakumar what's the status. Will there be a hotfix or do we have to wait for a month until the CPS will be available?
Anyone with technical insight to the issue who can tell if switching to Firefox is a long term fix, or if we risk the same issue in a future Firefox update?
Chromium bugs list says that this may have been fixed in Chrome 85.0.4182.0.
Has anyone tried on this version?