Skip to main content
B
BrianLumb7-Bedrock
7-Bedrock
March 5, 2014
Question

Windchill 10.1 and Java

  • March 5, 2014
  • 3 replies
  • 9334 views

Hi All,

I am wondering what the correct Java build should be used with Windchill 10.1 on client machines running Windows 7 64bit.

We are using Creo 2.0 M080 with Windchill 10.1 M040.

There are some users that are losing connection and some work is not being saved properly. This is leading to a mismatch in cache data between the Server Workspace and the Client Workspace.

We are not sure if this a Java issue but trying to check different avenues where an error may occur.

Thank you.

Brian

3 replies

J
jessh12-Amethyst
12-Amethyst
March 5, 2014

Unless you're using an applet at the time, the version of Java on the client is not relevant to Creo/Windchill connectivity issues.

B
BrianLumb7-BedrockAuthor
7-Bedrock
March 6, 2014

Hi jess,

Thank you for the information.

So I am assuming that this means that when Windchill launches the embedded browser within Creo that the version of Java is of no consequence?

What about the version of IE itself? Should it be 64bit if I am running 64bit Creo on Win7 64bit or is 32bit okay?

IE 9, 10, or 11? Is there a build that should not be used because of compatibility issues?

Thank you again for your assistance.

J
jessh12-Amethyst
12-Amethyst
March 6, 2014

Yes, the version of Java on the client is of no consequence most of the time. The exception is when you're running an applet (e.g. using an applet for non-CAD document upload, whereas you could just use the browser's upload mechanism instead albeit with fewer features).

I don't know all the Creo compatibility ins and outs. Those are best examined on the product support matrices on the technical support site.

X
xmurray3-Newcomer
3-Newcomer
February 26, 2016

Did you ever find a good solution to this?  We are experiencing the same issue.  Where a user saves their work, and checks it in without any apparent errors but the next day the work is all gone and it is as if the day never happened.  All the files are back to the previous saved version.

I just wiped out the install and reloaded Creo2 M200 and we are using Windchill 10.1 M040 and IE9 browser.  He has tons of problems every day and it is hard to understand what is happening. 

S
21-Topaz I
STEVEG21-Topaz I
21-Topaz I
February 29, 2016

When was the last time they cleared out all the workspaces, cache, etc?

When one of my users have strange things happening in their workspace the first thing I ask them to do is to run through a procedure to actually delete the PTC directory.  Basically: Check everything in, delete all workspaces through Creo except one, copy any setting changes (web_favorites.xml), close creo and delete the PTC directory.  Restart Creo.

Most of the time it clears up the problem.

X
xmurray3-Newcomer
3-Newcomer
February 29, 2016

Yes, I have had him do this.  The rest of the team have far fewer issues so I don't understand it.  He often gets corrupted workspaces and he is not opening more than one instance of Creo or logging on as a different user ever so I am not sure why there is so much corruption.  We have copied the Config .pro from another user and are also closely watching his process for setting attributes and checking in and out to see if it is something he is doing.  I really thought the complete wipe and re-install of the newest build of Creo would help but he already had an issue losing work...again, since the new install.   Then at some point he went to make a new workspace and the system just hung with  the little swirly thing going around.  Checking the server connection shows it is still on-line, so there is some issue.  maybe we need to completely wipe his whole computer and re-install windows.

D
doehr1-Visitor
1-Visitor
March 1, 2016

Windchill 10.1 datecode M040 happens to be our exact version. We found that we can't go any higher than IE 10 and Java 7.51. Creo 2.0 should be compatible to it since we've been able to get Creo 1 and Creo 3 to work with those versions.

Terms & ConditionsAccessibility statement