Remote coral failed
eap at gloworm.Stanford.EDU
Tue Aug 26 12:31:15 PDT 2003
I'm running Java Web Start 1.0 build fsc-b20,
Java Runtime product version 1.3.0.
I opened JWS, removed coral from the cache and
re-loaded it and it seems to work fine. I don't
know why I didn't try that last night! I did go
to the web link and try that, thinking it would
re-load something, but I guess not.
On Tue, 26 Aug 2003, Bill Murray wrote:
> We were having problems with the certificates used to sign the jar files
> with JRE 1.4.2. To solve the problem, we decided it was time to get an
> authentic digital id from VeriSign. We are now using that to sign our
> jar files. Until your email, I believed that was working great. However,
> we are still having problems with the certificates used to sign two of
> our security jar files from a third-party. We are actively pursuing this
> with them. This should only be a problem with JRE 1.4.2.
> Based on your error message, I'm assuming that you are not using 1.4.2.
> Perhaps, WebStart did not successfully download all of our newly-signed
> jars. Could you go to WebStart, delete Remote Coral, and force it to
> download everything again? Please let me know the results as soon as
> For reference, which version of the JRE are you using?
> On Mon, 25 Aug 2003, Eric Perozziello wrote:
> > Hi Bill,
> > I just logged into coral, and it downloaded a new version.
> > Now the new version will not launch.
> > Here is the error message:
> > An error occurred while launching/running the application.
> > Title: Coral Remote (SNF)
> > Vendor: Stanford Nanofabrication Facility
> > Category: Launch File Error
> > JAR resources in JNLP file are not signed by same certificate
More information about the coral