1. Check the /config/fmwconfig/cwallet.sso to see what its permissions are (right-click -> properties in windows, ls -la in the /config/fmwconfig directory for linux/unix
2. Be sure that permissions of read and write are available to the user and group who will be starting the inbound refinery
3. Change permissions as needed
permissions set on the file cwallet.sso at the time of the creation has only allowed the original creator to access it. So if any other user including the Administrators Group have no access to read it so it fails
This is the file which holds credential information and it needs to be accessible to users who are starting the inbound refinery
The server understood the request, but is refusing to fulfill it. Authorization will not help and the request SHOULD NOT be repeated. If the request method was not HEAD and the server wishes to make public why the request has not been fulfilled, it SHOULD describe the reason for the refusal in the entity. This status code is commonly used when the server does not wish to reveal exactly why the request has been refused, or when no other response is applicable.
The core reason here is that the server deployment has failed .
Do the following :
Stop the server and then from command line navigate to <domain_home>/bin and use the following command :
startManagedWebLogic.sh (or bat if windows) UCM_server1
Check if there are any errors reported in the command window and post that here for analysis.
Thanks for your answer. The server still can't started, This is the log:
####<In 2014-6-5, at 10:29 a.m. CST> <Error> <ServletContext-> <ecmdev> <IBR_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1401935363141> <BEA-000000> <Could not start admin server at default relative web root URL 'ibr'.
javax.servlet.ServletException: Could not start up IDC admin deployment.
Caused By: intradoc.common.ServiceException: !syFileUtilsUnableToCreateSpecifiedDir,E:/Oracle/MIDDLE~1/USER_P~1/domains/UCM_DO~1/ucm
Did you disable the 8.3 windows naming convention as specified in the installation guide?
Windows installations make the directory security structure go haywire. Are you sure that your entire oracle_root directory and *everything* under is owned by your install user? Are you sure that it's your install user that's launching the servers?
If you see any of those lock icons in your oracle_root directory, I'd propagate the owner and permissions across all children to make sure everything is owned in the correct context.
Please let us know if this helps at all.