19-Tanzanite

Solved

Recent Chrome Update Possibly Affects Windchill

Forum|Forum|5 years ago
June 5, 2020
11 replies
38268 views

This is more of a post letting others know what I encountered today with my Chrome-Windchill connection, but if anyone knows what is going on that would be great to know. It seems that Chrome recently updated their browser, mine is showing 83.0.4103.97, and I am now having issues with it. I have cleared all the history out of Chrome and it still has the issue. The issue has been seen across multiple computers, is that during the creation of a CN, when you go in and edit the task during that creation a blank window pops up with the spinning circle of death. I am on Windchill 11.2.1.0. The only error that is in any of the logs is:

2020-06-05 07:51:47,667 ERROR [ajp-nio-127.0.0.1-8015-exec-1] com.ptc.windchill.enterprise.change2.tags.ChangePropagationTag <USERNAME> - action oid was null

I have opened a support call and am waiting to hear back from them.

I don't know if anyone else has seen this yet or not.

Best answer by DeviVijayakumar

This is apparently a bug in the Chromium engine (Status of their bug - fixed in Chrome 85.0.4182.0)

S

STEVEG

21-Topaz I

I updated my version of Chrome and it went to the same as yours.

My version of Windchill is 11.0 M030 CPS18 on my test server.

I was able to complete an ECN without a problem so it might be your version of Windchill.

B

BrianToussaint

Author

19-Tanzanite

Thank you. That is what I am afraid of. But it was working just before the update and the last 5 months. I have not made any changes to the system recently. I'm still waiting to hear back from support.

S

STEVEG

21-Topaz I

Then it might be the combination of those 2 versions of software.

A

aacciano3

14-Alexandrite

Brian,

I am at the same Chrome build and 11.1 M020 and I have the same issue.

I actually discovered that it affects also the global enumeration (edit or create a new global enumeration) and any popup that is embedded in the same windows.

Also, if in a CH info page, you try to set state of the resulting objects, it works the first time and if you cancel it, it won't work anymore.

Can you please confirm you also see these additional issues at your end?

I'd like to open a case with PTC, so if you can share your case number I can reference it to my case.

J

JHall

1-Visitor

I'm beginning to see it as well.
My version of Windchill is 11.0 M030 CPS18
My Chrome version is Version 83.0.4103.97 (Official Build) (64-bit)

The 'breadcrumb' has vanished.  The link appears correctly in Edge, Firefox, and Brave. Below is a screen shot showing the 'breadcrumb' missing in Chrome, but correct in other Browsers.

James

S

ScottMorris

17-Peridot

Every time I've lost the breadcrumb links, I clear the cache in Chrome and restart the browser. Almost always takes care of this issue. Appears to have corrected the issue on WC 11.1 M020 CPS11 with Chrome Version 83.0.4103.97

J

jmomber

12-Amethyst

We are experiencing the same issue, although we are on 11.0 M030 CPS something. I was searching the knowledge base prior to opening a ticket and found your post. 😀 The most common issue for us is the spinning wheel of death when trying to view a "Resolve Conflicts" task. We've also had to tell our users to use alternate browsers. Browsers are so fun!

A

aacciano3

14-Alexandrite

@wsaad @JeffZemsky
Are you guys able to chime in? Is it something that PTC is already aware of?

Seems all Windchill customers are having this issue with Chrome.

I am not sure if the customers using the new Edge (the one using Chromium engine) are affected as well.

We have few cases opened.

Thanks for your help.

J

JeffZemsky

17-Peridot

@aacciano3 I've asked the team to look into it.

L

LawrenceS

18-Opal

I work at the same company as @STEVEG (WC11.0) and it looks like this is now an issue with us when we update Chrome and restart the browser. The only issue we have noticed so far is we getting hte spinning circle of death when a user starts a CN and tries to edit the Implementation Plan on the second page of the CN.

To be clear it worked on my machine with the previous version of Chrome, then I checked my chrome version while helping a user and chrome automatically updated to the latest version mentioned in this post. It still worked fine, until I came back to it, restarted the Chrome browser, and now it fails for me. The culprit is pretty darn clear!

I also tested in the latest version of the Chromium based Edge and it fails the same way as Chrome. Hmm, looks like the old saying of not putting all our eggs in one basket holds true to dependent browsers too! 😀

Thankfully my favorite ol' bessy/IE is still go'n strong! 😎

B

bsullivan

1-Visitor

Seeing Same issue on Just Rehosted Development Server 11.0 M030 CPS17

Works fine with Edge

Works fine Cognos In Cognito Mode

Brian Sullivan

B

bsullivan

1-Visitor

Sorry. I meant Chrome not Cognos

B

bsullivan

1-Visitor

Brian,

I was able to solve by clearing the Chrome Browser Cache from within Chrome. I had initially tried clearing cache from Control Panel/Internet Options which did not help.

Clearing Cache within Chrome did work for me!

Select "Customize and control Google Chrome" AKA the Three Dots in Upper Right Corner of Browser
Select Settings
Select Privacy and Setttings
Clear Browsing Data
Top 4 Selected and Selected Clear Data

Then started to work

Brian Sullivan

B

BrianToussaint

Author

19-Tanzanite

@bsullivan - I did that with the original user when it first happened and it did not clear things up.

B

BjoernRueegg

17-Peridot

Could please somebody verify if they still can create a new subtype in the Type and Attribute Manager? E.g. create a subtype for a WTDocument. I have the same spinning circle.

I belief the Chrome problem has something to do with the lightbox.

HelesicPetr

22-Sapphire II

Hello,

Yes, you right. I cant create it in new build of chrome.

Many light boxes (window in window) are involved.

Also the creation of new sub-type is involved as new attributes and many others things.

PetrH

S

ScottMorris

17-Peridot

Yes, I experienced this yesterday. Cannot create new Reusable Attribute in latest version of Google Chrome for Windows 10 on Windchill 11.1 M020 CPS11.

D

davehaigh

13-Aquamarine

Chrome just rolled out a new version Monday June 15th 83.0.4103.106

It appears to work for me. It automatically updated to this version when I checked the version I was running.

I got this message when checking the version

After restarting Chrome it now says this.

A

aacciano3

14-Alexandrite

@davehaigh

I tested the new version.

For me, it worked only the first time (e.g. set state on resulting objects).

After that doesn't work anymore...

HelesicPetr

22-Sapphire II

You right.

The next build behaves same way as the previous one in my case.

The first try to open the lightbox window worked, then it doesn't.

Same behavior if you clear the cahced files.

I tried the new version, customer tried new version of chrome with same issue.

Chrome version 83.0.4103.106

PetrH

B

BjoernRueegg

17-Peridot

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 🥳

K

KimH_275064

12-Amethyst

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?

B

BjoernRueegg

17-Peridot

@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?

K

KimH_275064

12-Amethyst

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?