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

Creo View messed up with Chrome

SOLVED
Highlighted
Level 12

Creo View messed up with Chrome

So Google must have pushed out another update that has broken it working with Windchill. When we try to view something in Creo View it gives us the Install Creo View Client or Stop Checking for new versions in the Creo View window. It worked yesterday. It works in IE. Nothing has changed server wise as far as which build I am using. The Chrome version is Version 42.0.2311.90 m. We are on Windchill 10.2 m020 CPS08 and Creo View 3.0 m020. Has anyone else had this happen today? Anyone with a solution?

1 ACCEPTED SOLUTION

Accepted Solutions

Re: Creo View messed up with Chrome

Brian checkout this knowledge base article.

https://support.ptc.com/appserver/cs/view/solution.jsp?n=CS197208

Useful info as well:

http://www.ghacks.net/2014/11/24/how-to-re-enable-plugins-in-chrome-that-are-blocked-by-google/

Also using this as my startup from chrome:

C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --allow-outdated-plugins --enable-npapi

Keep in mind if you update in September Chrome will no longer work with CreoView.

36 REPLIES 36

Re: Creo View messed up with Chrome

Yep, same thing here. Worked yesterday and today it doesn't. We're running Windchill 10.2 M020 CPS09 and Creo View 3.0 M031. I will open a case...

Re: Creo View messed up with Chrome

I've done that already, with both Google and PTC and am in the twiddle thumbs mode.

Just wanted to make sure it wasn't just my users.

Re: Creo View messed up with Chrome

Brian checkout this knowledge base article.

https://support.ptc.com/appserver/cs/view/solution.jsp?n=CS197208

Useful info as well:

http://www.ghacks.net/2014/11/24/how-to-re-enable-plugins-in-chrome-that-are-blocked-by-google/

Also using this as my startup from chrome:

C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --allow-outdated-plugins --enable-npapi

Keep in mind if you update in September Chrome will no longer work with CreoView.

Re: Creo View messed up with Chrome

Brian, thanks for the info. PTC tech support just got back with me and said the same thing:

================================================

According to CS197208, Google Chrome has plans to discontinue NPAPI support, which is what Creo View uses to work in embedded mode. According to the Chromium website:

April 2015

In April 2015 (Chrome 42) NPAPI support will be disabled by default in Chrome and we will unpublish extensions requiring NPAPI plugins from the Chrome Web Store. All NPAPI plugins will appear as if they are not installed, as they will not appear in the navigator.plugins list nor will they be instantiated (even as a placeholder). Although plugin vendors are working hard to move to alternate technologies, a small number of users still rely on plugins that haven’t completed the transition yet. We will provide an override for advanced users (via chrome://flags/#enable-npapi) and enterprises (via Enterprise Policy) to temporarily re-enable NPAPI (via the page action UI) while they wait for mission-critical plugins to make the transition. In addition, setting any of the plugin Enterprise policies (e.g. EnabledPlugins, PluginsAllowedForUrls) will temporarily re-enable NPAPI.

So, it appears your next step here would be to access chrome://flags/#enable-npapi and re-enable NPAPI for the time being. This should work until September 2015 when Chrome 45 is released.

================================================

For those who can't read CS197208, here is the relevant part:

cv.PNG

Re: Creo View messed up with Chrome

I'm still surprised an announcement wasn't sent out from support warning of this coming problem. This would have allowed us to be proactive instead of reactive. The article was written almost 3 months ago.

Re: Creo View messed up with Chrome

Agreed, a little warning would have been nice. It isn't like there is nothing else to do on a Friday. At least it isn't Monday.

This is fine mess. Can't drag and drop documents in IE11 without Java. Can't open up Creo View in Windchill, even though it isn't September. Tech support has work around that works on their computer, but doesn't on mine. Tried Firefox and that was a complete mess.

Re: Creo View messed up with Chrome

Enabling the flag did work for me. I hope PTC can come up with a better solution before September. What if IE and Firefox follow suit. Then where will we be?

Re: Creo View messed up with Chrome

If you look at CS192427, you will see that IE will only support IE11 after January 2016.

Re: Creo View messed up with Chrome

We just put in a ticket about it not working in Chrome and their response was that the version checker plug-in didn't work in 64 bit, and even with the flag set I can confirm that it doesn't work.