We've been using Creo View 2.0 M010 in connection with Windchill PDMLink 10.0 M030 without issue for over a year. We've had it installed in a non-default path (D:\apps\PTC\Creo 2.0\View) as we typically keep all our CAD software and related apps isolated to that D:\apps directory. In preparation for moving from Wildfire 4 to Creo 2 Parametric M090 next month, we thought we'd go to the latest M-code of Creo View 2.0 - M040. With that all Creo 2.0 related software is installed at D:\apps\PTC\Creo 2.0 - view continues to be in a "View" folder in that location and Creo Parametric 2.0 M090 is in the "Common Files", "Parametric" etc. Problem is, with Creo View 2.0 M040 installed in that location, it no longer works with Windchill PDMLink. The viewable window on the information page for an object is black and can't be clicked on to launch View. If I uninstall Creo View 2.0 M040 and let it install to the default C:\Program Files\PTC\Creo 2.0\View folder, it works fine with Windchill. Going back and forth with this (uninstall, reinstall - alternating the paths) there is a clear correllation - default install path, it works...our preferred install path, it does not work. I tested it with Creo View 3.0 M010 and it behaves the same as 2.0 M040 - works with Windchill if installed to the default "C:\Program Files\ . . ." path, doesn't work with Windchill if installed to our preferred "D:\apps\. . .". Has anyone else seen this type of behavior? Thoughts on why it worked fine with Creo View 2.0 M010, but M040 and after it does not? In all cases, Creo View runs fine if manually started from the installation. Checking the registry, the install path is getting noted properly when installed in either location.
Windows 7 64 bit, IE 9 for browser
Additional Information - the error only occurs when connecting to Windchill PDMLink with a standalone browser (I've tried both 32 bit and 64 bit IE 9 and Google Chrome).
When connecting using the integrated browser panel in Wildfire 4 M230 or Creo 2 Parametric M090 - both set to use IE 9 as the browser - Creo View 2 M040 works fine when installed in our preferred path.
did you uninstall Creo View 2.0 M010 from D:\apps\PTC\Creo 2.0\View before you installed Creo View 2.0 M040 in D:\apps\PTC\Creo 2.0\View ?
Yeah, we did a full uninstall of Creo View 2.0 M010 before installing M040. Included a reboot and check of the registry and all seemed well. As noted in my second post, the issue only occurs when using a standalone browser. The browser panel in Pro/E WF4 and Creo 2 Parametric works fine with View M040 installed in our D:\apps directory. So now it's more of a question of why does standalone not work when integrated does when using the same install of View and the same browser (we checked both the 32 bit and 64 bit IE9 as the external browser, View M040 works with neither when installed in d:\apps\...).