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

Windows 7 and PDMLink 9.1 M050 Workflow Administrator

PDMLink 9.1 M050 Order of Startup

That's really interesting because the recommendation I got from at least
some PTC folks was to start Apache first, then Tomcat, then Windchill.
Some suggested it really doesn't matter.

I have seen that error this thread started with though but had not
experienced a problem with startup.

RE: Windows 7 and PDMLink 9.1 M050 Workflow Administrator

A similar workaround, and maybe less painful than dropping to 256 colors, is to turn off ClearType (Control Panel -> Display -> Adjust ClearType text). This may also help PTC get to the root of the problem.

I didn't have any luck resolving the issue by setting the sun.java2d.noddraw and sun.java2d.d3d properties.

- Jon Langlois

NetIDEAS, Inc.


In Reply to Greg Montgomery:

Bill,
I have seen that. The workaround that I found was to dumb down my Windows7
display mode from True Color 32 bit down to 256 colors. It's not a great
solution but it will at allow you to work with the Workflow Admin page. And
it should also give PTC the clue they need to resolve it. It seems like the
Java 2D graphics API and Windows 7 display drivers are not happy together.

On Windows 7 to change the display mode it's : RMB on wallpaper > Screen
Resolution > List all modes

Greg Montgomery


On Wed, Feb 9, 2011 at 11:05 AM, Bill O'Rourke
@<->wrote:

> Our NASA center is pushing Windows 7 out to the community and we have found
> that when you go to the Workflow Administrator to view or edit a workflow, a
> blank screen appears. There are no errors thrown in the Java console(we are
> using 1.6.0_23). We have a call in with PTC, but so far they are stumped.
> Just curious if anyone else has seen this. Thanks and Happy Mardi Gras to
> everyone!
>
> *Send lawyers, guns, and money...the sh!t has hit the fan! *

Windows 7 and PDMLink 9.1 M050 Workflow Administrator

This issue certainly isn't general to all Windows 7 machines.

I just tested this on my new Windows 7 laptop with 32-bit / True Color
on and without disabling ClearType. This was with R9.1 M060, though I
don't suspect anything is different between M050 and M060 here -- I just
keep the latest MOR installed on my laptop at any given time. This was
also with Java 6 Update 24, but I don't suspect there's a difference
between Update 23 and 24 here, either -- I just keep the latest Java
Update installed as well.

It worked fine. There may be other sun.java2d properties that need to
be tinkered with, but overall this appears to be a Java Plug-In issue
related to specific drivers involved.

--
Jess Holle

Highlighted

Windows 7 and PDMLink 9.1 M050 Workflow Administrator

Hello

This issue is related to older graphics hardware combined with a newer java version that uses 3D acceleration. On my laptop W7, it works with java 1.6_07, not with 23 and 24. I haven’t tested with other java updates.

I opened a call 7620646 and was provided with these three possible workarounds:

1- The issue that you have is related to an outdated Video Driver and it should be resolved by updating into upgrading to the latest release. => for me, the most recent driver still got the same error
2- Add the following JVM options via the Java control panel: => I believe this also helped.
-Dsun.java2d.d3d=false
-Dsun.java2d.noddraw=true
3- Use previous java Runtime Environment. => this certainly helps. 1.6_07 works.

One of the emails indicates the following:
“please notice that you can safely use the jre is 1.6.0.18 with the Windchill 9.1M040. The issue that you have is related to an outdated Video Driver and it should be resolved by updating into upgrading to the latest release. A similar issue has been also detected with the driver type: ATI Mobility Radeon HD 3400.”

Tony

RE: Windows 7 and PDMLink 9.1 M050 Workflow Administrator

We also tried all of the java commands with no luck, and I tried the ClearType change, but got the same results. It may well be our video drivers, and going back to the earlier version of Java is not feasible. Since this only affects a hndful of folks(there are only 4 of us who are authorized to use the Workflow Manager), we found a workaround by consoling in to the server, and doing our work there on the workflows. We just found it strange that the Workflow Manager display has problems, yet the Process/Routing displays from the details pages work just fine.

Send lawyers, guns, and money...the sh!t has hit the fan!