Skip to main content
P
ParthivVed1-Visitor
1-Visitor
September 21, 2011
Question

Windchill 10.0 M010 Workflow window would not launch.

  • September 21, 2011
  • 11 replies
  • 4836 views

In 'Workflow Template Administration' window, when you try to create a new Template or edit existing one, you get the login screen but then nothing loads. You see windows 'loading' sign but no window loads for you to create or edit any workflows. I enabled Java console for message and here is what it says: (Note that all other Java applet windows for L/C Template Administration, Policy Administration, etc loads alrgiht).

basic: Applet started
basic: Told clients applet is started
network: Cache entry not found [url: http://<domain>/crossdomain.xml, version: null]
network: Connecting http://<domain>/crossdomain.xml with proxy=DIRECT
I have case opened with PTC support since few days now. We tried many things together, but nothing has helped. Ad per PTC support, this Workflow issue is faced by 7 out of 10 people. And everythime, they have to try different methods to resolve it. There is no surefire way to solve it. They have contacted R&D on this.
Has any of you faced similar issue? If so, were you able to solve it? How?
Thanks in advance for your advise on this.

11 replies

M
MatthewKnight1-Visitor
1-Visitor
September 21, 2011

do you have wt.method.minPort to wt.method.maxPort open

P
ParthivVed1-VisitorAuthor
1-Visitor
September 21, 2011

Mathew, it's

wt.method.maxPort=5011

M
MatthewKnight1-Visitor
1-Visitor
September 21, 2011

Right. Are they open on the firewall

P
PascalDICHELLO1-Visitor
1-Visitor
November 11, 2014

Hello,

Add this lines on this file

C:\Program Files (x86)\Java\jre6\lib\security\java.policy

grant codeBase "http://nameserver/Windchill/-" { permission java.security.AllPermission; };

permission java.net.SocketPermission "ip_adress_server_windchill:*","connect";

Regards

Pascal

J
jessh12-Amethyst
12-Amethyst
November 11, 2014

First off, the crossdomain.xml stuff is perfectly normal and can be ignored.

Secondly, I'm pretty sure this issue has been fixed in a later MOR. By which SPR or the like, I have no idea, but I'm pretty sure if you did a test install of 10.1 M050 (or 10.2 M020) you'd find the issue had been resolved -- without any java.policy changes.

Terms & ConditionsAccessibility statement