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

wt.LoadFromFile command errors out

Highlighted
Gravel

wt.LoadFromFile command errors out

We are moving our sever from 2003 to 2008. After rehosting PDMLink on the new server, we have been able to log in, check in, check out, revise, etc. Behaves normally.

In a windchill shell we are not able to execute the wt.LoadFromFile command, errors out - The operation: "getPrincipal" failed. Had a warning on https:<servername>/Windchill/wt.properties not found - using local properties.

Also the windchill wt.auth.Authentication errors out (same thing, but more verbose java errors)

Window 2008, PDMLink 9.1-m070, running ssl with self signed certificates.
We did this same process on our open network and everything works fine.
On our closed network we have this problem.

Any idea appreciated. So far the hot-line doesn't have a clue.

David Haigh
Phone: 925-424-3931
Fax: 925-423-7496
Lawrence Livermore National Lab
7000 East Ave, L-362
Livermore, CA 94550

Errors
=====
Load from file errors:
3 REPLIES 3
Highlighted

wt.LoadFromFile command errors out

David,

If your cert is not trusted by Java, you need to add it to the jssescacerts
keystore. This is documented on page 271 in the Windchill Installation and
Configuration Guide - Advanced 9.1. If you're on 10.X, just search for
keytool in the guide or you can find instructions on google.

In short, you need to export the cert using your web browser to your
<jre>\lib\security directory, and then run the keytool command to create
the keystore. Then restart Windchill and you should be able to
authenticate with the windchill shell.

Regards,
Bill



Highlighted

wt.LoadFromFile command errors out

The admin working on this, says this:

The keystore is correct; I have now done it at least twice (via a script and manually yesterday before going home).
I even used the keytool to see that it looks correct, delete it and re-import the certificate into it.
I don't think it's the certificate.

David Haigh
Highlighted

wt.LoadFromFile command errors out

David,

OK, that sounds pretty definitive as far as the keystore. Were all java
processes restarted after the keystore was created?

I just ran into this earlier this week with a customer. I didn't save the
entire error stack, but it was a ValidatorException of some kind.

Is it possible the cert that was used didn't include the entire chain.

Regards,
Bill



Announcements