This content has been marked as final. Show 17 replies
I have tried downgrade my client-side JRE to version 6 update 27.
I got the same error message.
I have also tried to upgrade the client JRE to version 7 update 5.
I still got the same error message.
Any ideas, please?
By the way, in any JRE version, I have no issue using the Admin Applets in the other UCM 10g instances I have on the same server.
Edited by: user6502585 on Aug 3, 2012 10:48 AM
I have tried using https and http, with IP or host name, all combinations returned the same error message.
To the best of my knowledge, nothing funky is performed on the idcplg path or the Intradoc.cfg file.
I completed the in-place upgrade process outlined by the Oracle Document.
Then, I started testing the basic functionality one by one.
Search, Check-In, Update DocInfo, IBR were working fine until I tried to access the Admin Applet in the browser.
Caused by: intradoc.common.ServiceException: !syFileUtilsFileNotFound,(null)at intradoc.client.UrlClient.doURLRequest(UrlClient.java:298)>
That bit of code logic looks for only either a 403 or a 404 response code (403 being "forbidden" and 404 being "page not found"). The system is explicitly getting a 404 error passed to it, but the download test you just did shows that the file exists, and can be downloaded.
I have to wonder if the jar is messed up. My file size is 3.16 MB (3,318,627 bytes) for 11g. Yours close to that?
Also, try dumping your Java temp cache on your local machine. This is not the same as your temporary internet files. You have to go into the Java console control in Windows Control Panel to do it.
Also.. I hope you are aware that having your content server deployed under anything but /cs/ is not a supported configuration for 11g at the moment.
The only supported configuration for HttpRelativeWebRoot is to be "/cs/"
I've never done the in-place upgrade, but it is never a good idea to begin with.
What is your HttpRelativeWebRoot at the moment?
I suspect you had your content server deployed under something like /idc ?..
Try using Fiddler to see where it tries to pull the jar file from when you try to load the applet.
Let us know.
Well, since I am upgrading from 10g, my URL is not "/cs/".
It is "/contrib/".
It seems to be running just fine when I tested the upgrade process on my Window 7 box with "/contrib/".
I would only see the URL changed to "/cs/" when I login through the WebLogic Server.
If "/cs/" is the only supported configuration, then wouldn't the whole in-place upgrade process with UA be a hoax?
I would think not many 10g instance would be named "/cs/".
I will try Fiddler to pull more details on the error.