Community Tip - Your Friends List is a way to easily have access to the community members that you interact with the most! X
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).
do you have wt.method.minPort to wt.method.maxPort open
Mathew, it's
wt.method.maxPort=5011
Right. Are they open on the firewall
Yes.
I don't know then. I've had problems when checking "remember password/credentials." Does it work after you kill the session
Nope. It does not work after killing sessions. I have made changes with PTC support, unistalled and installed latest JRE, etc. rebooted MS, nothing has helped. They too are looking into it (R&D is now involved).
Anyway, appreciate all your inputs. I should be updating this discussion once we find the solution.
Good luck. Sorry I couldn't help.
Are you running https? See if you can get it to work under http
Ok, here is the soution.
I've WC installed on my local machine (test box) so I changed the host file to point server to 127.0.0.1
Pointing it to the actual IP address solved the issue.
I talked to PTC on this and they confirmed this happens only with worfkflow template. All others templates work fine even if you set the server pointing to 127.0.0.1
Hope this helps others if they face similar issue.
Hello Parthiv Ved,
Same issue is observed on my machine.
All appletes are working fine expect the workflow.
whre i should made changes to solve this.
Please guide us.
Regards,
Vivek
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
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.