Community Tip - Did you get an answer that solved your problem? Please mark it as an Accepted Solution so others with the same problem can find the answer easily. X
Last week my users starting getting this script error when they start Creo. Is that something PTC needs to fix? I know I can add the config option web_browser_homepage or js_error_policy but I don't think that should be the solution. Isn't this something on PTC's site?
We started getting the same error messages. We have no idea. We assume this is a PTC issue or some kind of Windows update problem. I wish PTC would respond.
Out yesterday. Logged in today and got the same message.
Ok PTC. Any comment?
I mentioned in my original post that I believe that should not be the fix. Why did their site cause this issue? The fix should be on PTC's site.
As far as I remember "web site" is not one of the options in the drop-down menu to notify them of a problem like that. This was the only place I could think of.
Why did this get moved to the Assembly area? This has to do with eSupport Help webpage on PTC's site. Something changed on the site to make that dialog display.
We have had these for years. It appears to be something with the registry settings tied to the browser as tied to xtop.exe.
Internet Explorer 11.0 clients: Add the following registry keys with values of 11000 (decimal) or 2af8 (hex) via regedit or other method
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\MAIN\FeatureControl\FEATURE_BROWSER_EMULATION]
"xtop.exe"=dword:00002af8
"ptc_ie_server.exe"=dword:00002af8
"creoagent.exe"=dword:00002af8
"uwgm_client.exe"=dword:00002af8
"genlwsc.exe"=dword:00002af8
[HKEY_CURRENT_USER\SOFTWARE\Microsoft\Internet Explorer\MAIN\FeatureControl\FEATURE_BROWSER_EMULATION]
"xtop.exe"=dword:00002af8
"ptc_ie_server.exe"=dword:00002af8
"creoagent.exe"=dword:00002af8
"uwgm_client.exe"=dword:00002af8
"genlwsc.exe"=dword:00002af8
This just started happening to my users and as you can see to other companies recently. Why would it be on our end and not PTC's?
I know in our case it was because of some Windows policies that our IT had pushed out. This has been around for quite some time if you look at the case I linked you can see that it has been around as an issue for some people as far back as 2011 when the case was first crated with IE8 and has been updated right up to this past May to keep up with the browsers. There's nothing basically wrong with the PTC site in question and you can see that by opening the URL in a standalone browser.
I'll check with our IT team. Thank you.