I recently performed an in-place upgrade of UCM 10g to 11g following the UCM Upgrade documentation.
After the upgrade, the Admin Applet could not run using the browser.
I have tried on both IE8 and FireFox.
Let's use Repository Manager as an example.
I click on the icon in the Admin Applet page in the browser, an error message pop-up: apUnableToStartApplication(RepoMan) apFailedToInitialize syFileUtilsFileNotFound((null))
I tried to trace the error using the Server Output with the option "applet", but have no luck.
Using the option "applet", the Server Output is blank.
In the Java Console, I have the following error message: Caused by: intradoc.data.DataException: !apFailedToInitialize at intradoc.apps.shared.AppLauncher.init(AppLauncher.java:177) at IntradocApp.createFrame(IntradocApp.java:329)
*... 27 more* Caused by: intradoc.common.ServiceException: !syFileUtilsFileNotFound,(null) at intradoc.client.UrlClient.doURLRequest(UrlClient.java:298) at intradoc.client.UrlClient.request(UrlClient.java:107) at intradoc.apps.shared.AppLauncher.executeService(AppLauncher.java:768) at intradoc.apps.shared.AppLauncher.executeService(AppLauncher.java:714) at intradoc.apps.shared.AppLauncher.initConfig(AppLauncher.java:312) at intradoc.apps.shared.AppLauncher.init(AppLauncher.java:169)
*... 28 more*
I was able to start the applets in the server running as standalone in the directory "<domain_root>/ucm/cs/bin".
Could someone help, please?
I am using Java JDK 1.6.0 update 33 on the Server and my local machine is running 1.6.0 update 32.
I will try to find an older version to install to my local machine.
By the way, my Server is running on Solaris.
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.
In the 11g instance, take a look in the "weblayout\common" directory, and see if the file "idcapplet.jar" file exists. if not, that's the issue.
If it DOES exist, check the permissions on the file. It's likely the file system permissions are wrong.
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.
Yes, the file is the same size as yours, 3318627 bytes.
I tried clear the Java Console cache and access the Admin Applet page.
I now only have 6 image files and the "idcapplet.jar?SHA-256%......" in the Java Cache Viewer.
Still, the same error.
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.