Cannot start weblogic 8.1 User is not permitted to boot the server

Hi,
Sorry to cross-post, but I didn't seem to get any feedback on this in the 'security' newsgroup.
I have installed Weblogic 8.1SP3 on two identical workstations as well as deployed our application. On one server WL8.1 starts up fine. On another, it says "BEA-090404 user weblogic 8.1 is not permitted to boot the server".
The OS'es are identical: Windows XP Pro SP2.
The only difference I can think of: one is logged into a windows-domain, the other directly onto the PC.
I've ran diffs-ignoring-whitespace (i.e. diff -w) on the important-looking files (.ldift and config.xml) and don't see any differences that would warrant such difference.
Any suggestions?
thanks,
bill

when you installed the WLS , which admin user did you >create ?Admin user 'weblogic'. Actually someon did this long ago and checked in the generated config files (boot.properties) into our source tree?
So, in which mode do you start the WLS ? development or >production ?This I don't know.
Our setup is as follows:
1) We install weblogic (server only)
2) Run our ant scripts
3) Ant populates and deploys the config files and pe.ear file to a new domain.
4) we start weblogic from a script in that domain: startWeblogic.cmd
<Jul 20, 2007 8:17:35 AM CDT> <Info> <Configuration Management> <BEA-150016> <This server is being started as the administration server.>
<Jul 20, 2007 8:17:35 AM CDT> <Info> <Management>
We use a few app servers and use a similar paradigm: install, deploy from build tree, start from script.
My question: where do you specify that 'user weblogic is member of the administrator group' ?

Similar Messages

User weblogic is not permitted to boot the server

Hi,
I am new to OES and after running the configtool, creating the ASIAuthorizationProvider and ASIRoleMapperProvider (both has Defaul Identity Directory: wls_dir and Application Deployment Parent: //app/policy/wls_app), binding the SSM, i get this error when starting the WLS admin server:
15:33:26.312 EVENT Starting Jetty/4.2.25
15:33:26.859 WARN!! Delete existing temp dir C:\BEA_HOME_10\ales32-ssm\wls-ssm\i
nstance\wls_ssm\work\jar_temp\Jetty__8000__ for WebApplicationContext[/,jar:file
:/C:/BEA_HOME_10/ales32-ssm/wls-ssm/webapp/arme.war!/]
15:33:30.515 EVENT Started WebApplicationContext[,ARMEService]
15:33:32.562 EVENT Started SocketListener on 0.0.0.0:8000
15:33:32.562 EVENT Started org.mortbay.jetty.Server@176bf9e
ARME is started now
<Mar 5, 2010 3:33:33 PM SGT> <Notice> <Security> <BEA-090082> <Security initiali
zing using security realm wls.>
<Mar 5, 2010 3:33:34 PM SGT> <Critical> <Security> <BEA-090404> <User weblogic i
s not permitted to boot the server; The server policy may have changed in such a
way that the user is no longer able to boot the server.Reboot the server with t
he administrative user account or contact the system administrator to update the
server policy definitions.>
<Mar 5, 2010 3:33:34 PM SGT> <Critical> <WebLogicServer> <BEA-000386> <Server su
bsystem failed. Reason: weblogic.security.SecurityInitializationException: User
weblogic is not permitted to boot the server; The server policy may have changed
in such a way that the user is no longer able to boot the server.Reboot the ser
ver with the administrative user account or contact the system administrator to
update the server policy definitions.
weblogic.security.SecurityInitializationException: User weblogic is not permitte
d to boot the server; The server policy may have changed in such a way that the
user is no longer able to boot the server.Reboot the server with the administrat
ive user account or contact the system administrator to update the server policy
definitions.
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.do
BootAuthorization(Unknown Source)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.in
itialize(Unknown Source)
at weblogic.security.service.SecurityServiceManager.initialize(Unknown S
ource)
at weblogic.security.SecurityService.start(SecurityService.java:141)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
Truncated. see log file for complete stacktrace
>
<Mar 5, 2010 3:33:34 PM SGT> <Notice> <WebLogicServer> <BEA-000365> <Server stat
e changed to FAILED>
<Mar 5, 2010 3:33:34 PM SGT> <Error> <WebLogicServer> <BEA-000383> <A critical s
ervice failed. The server will shut itself down>
<Mar 5, 2010 3:33:34 PM SGT> <Notice> <WebLogicServer> <BEA-000365> <Server stat
e changed to FORCE_SHUTTING_DOWN>
Stopping PointBase server...
PointBase server stopped.
from the WLS AdminServer.log:
####<Mar 5, 2010 3:33:05 PM SGT> <Info> <Socket> <SGBLM010> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1267774385687> <BEA-000436> <Allocating 3 reader threads.>
####<Mar 5, 2010 3:33:05 PM SGT> <Info> <Socket> <SGBLM010> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1267774385687> <BEA-000446> <Native IO Enabled.>
####<Mar 5, 2010 3:33:06 PM SGT> <Info> <IIOP> <SGBLM010> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1267774386531> <BEA-002014> <IIOP subsystem enabled.>
####<Mar 5, 2010 3:33:11 PM SGT> <Info> <Security> <SGBLM010> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1267774391656> <BEA-000000> <Starting OpenJPA 1.0.0.1>
####<Mar 5, 2010 3:33:17 PM SGT> <Info> <Security> <SGBLM010> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1267774397171> <BEA-090516> <The Authenticator provider has preexisting LDAP data.>
####<Mar 5, 2010 3:33:33 PM SGT> <Info> <Security> <SGBLM010> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1267774413421> <BEA-090516> <The CredentialMapper provider has preexisting LDAP data.>
####<Mar 5, 2010 3:33:33 PM SGT> <Info> <Security> <SGBLM010> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1267774413500> <BEA-090663> <The DeployableRoleMapper "com.bea.security.providers.authorization.asi.RoleProviderStub" implements the deprecated DeployableRoleProvider interface.>
####<Mar 5, 2010 3:33:33 PM SGT> <Info> <Security> <SGBLM010> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1267774413531> <BEA-090662> <The DeployableAuthorizer "com.bea.security.providers.authorization.asi.AuthorizationProviderStub" implements the deprecated DeployableAuthorizationProvider interface.>
####<Mar 5, 2010 3:33:33 PM SGT> <Info> <Security> <SGBLM010> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1267774413796> <BEA-090093> <No pre-WLS 8.1 Keystore providers are configured for server AdminServer for security realm wls.>
####<Mar 5, 2010 3:33:33 PM SGT> <Notice> <Security> <SGBLM010> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1267774413796> <BEA-090082> <Security initializing using security realm wls.>
####<Mar 5, 2010 3:33:34 PM SGT> <Critical> <Security> <SGBLM010> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1267774414234> <BEA-090404> <User weblogic is not permitted to boot the server; The server policy may have changed in such a way that the user is no longer able to boot the server.Reboot the server with the administrative user account or contact the system administrator to update the server policy definitions.>
####<Mar 5, 2010 3:33:34 PM SGT> <Critical> <WebLogicServer> <SGBLM010> <AdminServer> <main> <<WLS Kernel>> <> <> <1267774414234> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: User weblogic is not permitted to boot the server; The server policy may have changed in such a way that the user is no longer able to boot the server.Reboot the server with the administrative user account or contact the system administrator to update the server policy definitions.
weblogic.security.SecurityInitializationException: User weblogic is not permitted to boot the server; The server policy may have changed in such a way that the user is no longer able to boot the server.Reboot the server with the administrative user account or contact the system administrator to update the server policy definitions.
     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(Unknown Source)
     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(Unknown Source)
     at weblogic.security.service.SecurityServiceManager.initialize(Unknown Source)
     at weblogic.security.SecurityService.start(SecurityService.java:141)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
>
####<Mar 5, 2010 3:33:34 PM SGT> <Notice> <WebLogicServer> <SGBLM010> <AdminServer> <main> <<WLS Kernel>> <> <> <1267774414328> <BEA-000365> <Server state changed to FAILED>
####<Mar 5, 2010 3:33:34 PM SGT> <Error> <WebLogicServer> <SGBLM010> <AdminServer> <main> <<WLS Kernel>> <> <> <1267774414328> <BEA-000383> <A critical service failed. The server will shut itself down>
####<Mar 5, 2010 3:33:34 PM SGT> <Notice> <WebLogicServer> <SGBLM010> <AdminServer> <main> <<WLS Kernel>> <> <> <1267774414328> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
####<Mar 5, 2010 3:33:34 PM SGT> <Info> <WebLogicServer> <SGBLM010> <AdminServer> <main> <<WLS Kernel>> <> <> <1267774414359> <BEA-000236> <Stopping execute threads.>
also, i just noticed that when staring OES admin server i get the following from the logs:
system_console.log:
2010-03-05 15:19:04,218 [JettySSLListener1-1] ERROR com.wles.soap.BLM.BlmBindingImpl - getUndistributedAttributeChanges has not been implemented properly.
2010-03-05 15:27:17,656 [Thread-31] WARN com.bea.security.ssl.axis.AxisClientSocketFactory - Error during SSL handshake; host: SGBLM010, port: 8,000.
2010-03-05 15:27:17,687 [Thread-31] ERROR com.bea.security.pdws.Distributor - unable to bind unbound arme
Communication Error:; nested exception is:
     javax.net.ssl.SSLHandshakeException: Error during SSL handshake; host: SGBLM010, port: 8,000.
2010-03-05 15:27:17,687 [Thread-31] ERROR com.bea.security.pdws.ARMEGroup - arme group '//bind/wls' error report, policyno = 52:
2010-03-05 15:27:17,687 [Thread-31] ERROR com.bea.security.pdws.ARMEGroup - arme 'asi.null.ARME.wls_ssm.asi.SGBLM010':
2010-03-05 15:27:33,015 [Thread-32] WARN com.bea.security.ssl.axis.AxisClientSocketFactory - Error during SSL handshake; host: SGBLM010, port: 8,000.
2010-03-05 15:27:33,015 [Thread-32] ERROR com.bea.security.pdws.Distributor - unable to bind unbound arme
Communication Error:; nested exception is:
     javax.net.ssl.SSLHandshakeException: Error during SSL handshake; host: SGBLM010, port: 8,000.
WLESWebLogic.wrapper.log:
INFO | jvm 1 | 2010/03/05 15:27:17 | Processing AxisFault, cause: javax.net.ssl.SSLHandshakeException: Error during SSL handshake; host: SGBLM010, port: 8,000.
INFO | jvm 1 | 2010/03/05 15:27:17 | Re-throwing the fault...
INFO | jvm 1 | 2010/03/05 15:27:18 | error.jsp: Client has closed the connection, error not reported to client.
INFO | jvm 1 | 2010/03/05 15:27:18 | error.jsp: The exception is: com.bea.wles.management.console.utils.NestedJspException: Connection reset by peer: socket write error
INFO | jvm 1 | 2010/03/05 15:27:33 | Processing AxisFault, cause: javax.net.ssl.SSLHandshakeException: Error during SSL handshake; host: SGBLM010, port: 8,000.
INFO | jvm 1 | 2010/03/05 15:27:33 | Re-throwing the fault...
although, it seems that the OES admin server is up since i am able to access the OES admin console.
i have tried playing around the policies to grant the "weblogic" the priviliges for an Admin but is still get the same issue. Although, when i try to distribute the changes in the policy, "ASI ( Policy for entire Oracle Entitlements Server system ) " still appears in the list of changes.
any thoughts on what the problem is? is there a way to force the distribution of the policy? maybe through the command prompt or other console?
Edited by: user9056644 on Mar 5, 2010 12:02 AM

Have you applied CP2 or CP3 to OES? There were enhancements that allows these policies to be scoped within an organization. I only ask to help guide you on distributing policies for the runtime WLS domain. The ASI domain is only for the admin. There should have been a set of resources and policies created as a result of running ConfigTool for your new instance (looks like you named it 'wls'). If no CP, it will be in DefaultApp next to ASI.
You have to distribute policies for 'wls' immediately following running ConfigTool before starting WebLogic or you will put it into a state where it can't be started. The corrective action is to remove the state.ck file under C:\BEA_HOME_10/ales32-ssm/wls-ssm/instance/wls_ssm/work/runtime, distribute policies, restart WebLogic.
If you need to re-run ConfigTool (after installing CP for instance), revert the following files:
<domain>/config/config.xml
<domain>/bin/startWebLogic.sh | .cmd
Revert from the no-ales backups created. Remove the instance folder under C:\BEA_HOME_10\ales32-ssm/wls-ssm/instance. You can then re-run ConfigTool if you have to.

Admin Server satrtup failing with the error User weblogic is not permitted to boot the server

Hi ,
The admin server is not coming up , its failing with the below error.
<May 25, 2014 10:28:35 PM PDT> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: User weblogic is not permitted to boot the server; The server policy may have changed in such a way that the user is no longer able to boot the server.Reboot the server with the administrative user account or contact the system administrator to update the server policy definitions.
weblogic.security.SecurityInitializationException: User weblogic is not permitted to boot the server; The server policy may have changed in such a way that the user is no longer able to boot the server.Reboot the server with the administrative user account or contact the system administrator to update the server policy definitions.
        at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:1010)
        at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1054)
        at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)
        at weblogic.security.SecurityService.start(SecurityService.java:141)
        at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
        Truncated. see log file for complete stacktrace.
I have tried resetting the password as per below link , it hasn't helped. Still facing issue. Please help
http://www.weblogic-tips.com/wls-security/
Thanks,
Pradeep

Creating New user did not help . Still same error.
<May 26, 2014 8:56:31 PM PDT> <Critical> <Security> <BEA-090404> <User weblogicNew is not permitted to boot the server; The server policy may have changed in such a way that the user is no longer able to boot the server.Reboot the server with the administrative user account or contact the system administrator to update the server policy definitions.>
<May 26, 2014 8:56:31 PM PDT> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: User weblogicNew is not permitted to boot the server; The server policy may have changed in such a way that the user is no longer able to boot the server.Reboot the server with the administrative user account or contact the system administrator to update the server policy definitions.
weblogic.security.SecurityInitializationException: User weblogicNew is not permitted to boot the server; The server policy may have changed in such a way that the user is no longer able to boot the server.Reboot the server with the administrative user account or contact the system administrator to update the server policy definitions.
        at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:1010)
        at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1054)
        at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)
        at weblogic.security.SecurityService.start(SecurityService.java:141)
        at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
        Truncated. see log file for complete stacktrace
>
<May 26, 2014 8:56:31 PM PDT> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>"

Cannot start weblogic server anymore after conf. jena for oracle database

Hi,
My weblogic server 10.3.4.0 installed in oracle developer days in oralce linux guest was able to start before using the oracle user account. Following the seman. tech. dev. guide, I set up jena adapter for oracle in my guest linux system. Since the oracle user doesn't have permission to copy folders into the autodeploy directory in weblogic server, so I login as root to copy the joseki.war folder into the autodeploy directory. However, after that, I am not able to start the weblogic server console anymore using the oracle user account. Any suggestions will be much appreciated. Thanks a lot in advance.
Hong

Pl do not post duplicates - cannot start weblogic server anymore in oracle user after config. in root

Starting WebLogic as different user ?

Hi Folks,
Does anyone know some way start WebLogic as different user ?
To be a bit more clear:
Let's say I'm logged in as unix user 'weblogic'. But, I want to start a server as user 'wls_domain1'. This is so that the various domains on my machine can run as separate users. I have an idea that I saw some command-line option to do this (something like -Dweblogic.SwitchUser=wls_domain1 ). But this may not be possible in unix anyway, without root privilege.
I do not see such an option at:
http://e-docs.bea.com/wls/docs81/admin_ref/weblogicServer.html
I use Node Manager, so need to set the user as a weblogic.Server option rather than using 'su' command in the unix start script.
thanks,
JM

Hi,
Go through the following link,In that you will get exact information on this issue.
http://e-docs.bea.com/wls/docs90/server_start/overview.html#1068948
Regards
Anilkumar kari

ERROR: Cannot start mail services, configuration directory does not exist

I'm running an Xserve G5 with one internal boot drive and one RAID using the other two internal drives. I used Apple's Disk Utility to set-up the RAID.
Back in early December, I moved my mail database and mail store to the RAID. Ever since, when I restart the server, the mailaccess.log generates the following error:
Jan 23 18:51:33 mail master[47]: ERROR: Cannot start mail services, configuration directory does not exist: /Volumes/RAID/mail.data/db
I'm speculating this is a timing error that gets created when Postfix initially can't find the RAID. Then, it must try again and find it because the error message does not repeat and mail starts running.
Is this something to worry about?

Hi Joel,
You're right, it's a timing issues. The mail system is ready for work before the file system is mounted. It's benign.
Jeff

Firefox crashes on start up for one user but not another

Crash ID: bp-df3a48d7-363c-4d2f-87d3-f73902140723
Version: 31
Crashes on start up for one user but not another. Both are administrators.
I have uninstalled and re-installed. No change with each user.
Crashes in safe mode as well (holding down shift)
No addons present in other user.
Have ran Malwarebytes and cleaned
Have ran CCCleaner and cleane all including registry entries with Firefox uninstalled.

Create a new profile as a test to check if your current profile is causing the problems. <br>
See '''Creating a profile''':
*https://support.mozilla.org/kb/profile-manager-create-and-remove-firefox-profiles
*http://kb.mozillazine.org/Standard_diagnostic_-_Firefox#Profile_issues
If the new profile works then you can transfer files from a previously used profile to the new profile, but be cautious not to copy corrupted files to avoid carrying over the problem <br>
'''Profile Backup and Restore'''
*http://kb.mozillazine.org/Profile_backup
*https://support.mozilla.org/en-US/kb/back-and-restore-information-firefox-profiles
*http://kb.mozillazine.org/Transferring_data_to_a_new_profile_-_Firefox

Java.lang.Exception: User : principals=[admin] is not allowed to shutdown the server

Hi,
When i shut down my managed and admin servers through the console i am getting
the following exception.Any one have an idea on this?
Exception :
java.lang.Exception: User : principals=[admin] is not allowed to shutdown the
server.
     at weblogic.server.ServerLifeCycleRuntime.shutdown(ServerLifeCycleRuntime.java:299)
     at java.lang.reflect.Method.invoke(Native Method)
     at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:750)
     at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:732)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
     at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:928)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:472)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:200)
     at $Proxy105.shutdown(Unknown Source)
     at java.lang.reflect.Method.invoke(Native Method)
     at weblogic.management.console.actions.mbean.DoMBeanOperationAction.performOnSingle(DoMBeanOperationAction.java:206)
     at weblogic.management.console.actions.mbean.DoMBeanOperationAction.perform(DoMBeanOperationAction.java:188)
     at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
     at weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1075)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:418)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:306)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:5517)
     at weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:685)
     at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3156)
     at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2506)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:234)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:210)

I have the exact same problem. It is for a WLI 7.0 SP-5 domain. I started admin and managed servers using the startWeblogic and startManagedWebLogic scripts, but trying to stop them from the console is throwing this exception:
java.lang.Exception: User : principals=[admin] is not allowed to shutdown the server.
     at weblogic.server.ServerLifeCycleRuntime.shutdown(ServerLifeCycleRuntime.java:299)
     at java.lang.reflect.Method.invoke(Native Method)
     at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:736)
     at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:718)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
     at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:1107)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:472)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:200)
     at $Proxy105.shutdown(Unknown Source)
     at java.lang.reflect.Method.invoke(Native Method)
     at weblogic.management.console.actions.mbean.DoMBeanOperationAction.performOnSingle(DoMBeanOperationAction.java:206)
     at weblogic.management.console.actions.mbean.DoMBeanOperationAction.perform(DoMBeanOperationAction.java:188)
     at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
     at weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1094)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:437)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:319)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:5626)
     at weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:685)
     at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3213)
     at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2555)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:251)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:219)
I upgraded from WLI7.0 SP-1 to SP-5, and since then I am getting this error.
Please help!

Java daemon on boot: "This user is not allowed access to the window system right now."

The daemon is located in /Library/LaunchDaemons/ and launches successfully on most occasions. However, it sometimes fails to start with this error:
Nov 17 20:36:24 server.local java[28972]: This user is not allowed access to the window system right now.
Nov 17 20:36:24 server com.apple.launchd[1] (net.java.server): Throttling respawn: Will start in 10 seconds
I have the server command running as a background daemon using its "nogui" option (the developers claim to have written it to not display a gui). However, it seems that somewhere along the line, Java is trying to display something. As the daemon is running before users log in, it gives this error. Once a user is logged in to the system, it runs fine; however, logging in a user to run the server is not an option. It needs to run on boot.
Any ideas for how to solve this? I'm going to contact the developers to see if it may be something they can fix, but I want to be able to force the issue in case the problem ever occurs in the future.

Irrespective of any claims by the developer, this certainly appears to be a test case that shows that the tool is not working as expected, and that the application has a bug. This test case would be better if there was some evidence around why only some of the startups fail, but in general this will involve what's been suggested earlier: "Contact the application developer."
As some general background on what's involved, see daemons and agents and related; processes that are not allowed to connect to the GUI for reasons of security.
I'd also suggest testing your DNS, as seeing "server.local" can imply local DNS configuration errors. Launch Terminal.app from Applications > Utilities and issue the following harmless diagnostic command and see if it reports no changes, or if it detects network or DNS errors:
sudo changeip -checkhostname
If this is OS X Server and a NAT'd network, you do not want to reference any DNS servers located off of your NAT'd network.
Why DNS? Because DNS errors can cause only some operations to fail, particularly if there's more than one DNS server selected (and where some subset of the DNS servers are malfunctioning or misconfigured).

After update to 11.3.1 users are not logged in to the ZAA

Hi,
we did a update from 11.2.3 to 11.3.1 a few weeks ago. All works fine but there is one problem. A lot of users are not logged in to the ZAA. If i try to start a remote session with the username i get the message the user is not logged in to any device.
If i connect me to the device and look at the ZAA the user is not logged in and i can not log in because i get the error message that the username or password is wrong.
The solution is to go to the registry -> HKEY_LOCAL_MACHINE\SOFTWARE\Novell\ZCM\ZenLgn\Hist ory\Cache\domain.local and i have to delete the user.
After that the login works fine
Sometimes i have to delete the user in this registry key too -> HKEY_LOCAL_MACHINE\SOFTWARE\Novell\ZCM\ZenLgn\Hist ory\CachedUserZenNames
Is that a known bug? What can i do to solve that problem?

I would recommend an SR.
You should not have to do that.
There were some similar bugs in the past, but were fixed in 11.2.x and
should not exist in 11.3.x at all.
On 10/15/2014 7:26 AM, SteffenMuch wrote:
>
> Hi,
>
> we did a update from 11.2.3 to 11.3.1 a few weeks ago. All works fine
> but there is one problem. A lot of users are not logged in to the ZAA.
> If i try to start a remote session with the username i get the message
> the user is not logged in to any device.
> If i connect me to the device and look at the ZAA the user is not logged
> in and i can not log in because i get the error message that the
> username or password is wrong.
>
> The solution is to go to the registry ->
> HKEY_LOCAL_MACHINE\SOFTWARE\Novell\ZCM\ZenLgn\Hist ory\Cache\domain.local
> and i have to delete the user.
> After that the login works fine
> Sometimes i have to delete the user in this registry key too ->
> HKEY_LOCAL_MACHINE\SOFTWARE\Novell\ZCM\ZenLgn\Hist ory\CachedUserZenNames
>
> Is that a known bug? What can i do to solve that problem?
>
>
Going to Brainshare 2014?
http://www.brainshare.com
Use Registration Code "nvlcwilson" for $300 off!
Craig Wilson - MCNE, MCSE, CCNA
Novell Technical Support Engineer
Novell does not officially monitor these forums.
Suggestions/Opinions/Statements made by me are solely my own.
These thoughts may not be shared by either Novell or any rational human.

I cannot email photos from within iPhoto (v. 9.5.1). When I hit send I get a message: "Your email did not go through because the server did not reply." This happens for both my iCloud account and my Shaw account. What to do???

I cannot email photos from within iPhoto (v. 9.5.1). When I hit send I get a message: "Your email did not go through because the server did not reply." This happens for both my iCloud account and my Shaw account. What to do???

Are you able to email from Mail with those two accounts? If so:
1 - go to iPhoto's Accounts preference pane and delete both accounts. Now add them back and try again.
2 - a better solution IMO is to set Mail as the email client for iPhoto is iPhoto's General preference pane. This gives you better access to your contacts, a sent copy of all emails and, if you want a layout similar to iPhoto's, photo layouts located in Mail's stationary.

TS1398 my problem is my iphone 4s is connected to the internet(wi-fi) with full signal strength but freezes when browsing and says "Cannot Open Page, Safari could not open page because the server stopped responding".

my problem is my iphone 4s is connected to wi-fi with full signal(3 bars) strength but freezes when browsing and says
"Cannot Open Page"
"Safari could not open page because the server stopped responding"
I already reset the iphone to its factory settings and erase all contents but still the browsing speed freezes or not searching at all. Sometimes it will work and fast but then the problem uccors every now and then. Iv'e been using iphone 4 for two years and I still have it and works fine compared to this IPHONE 4S.

Settings → scroll down to Safari → in Safari settings, I selected both Clear History and Clear Cookies and Data.
IF that does not work -
Restart or reset your iPhone, iPad, or iPod touch - Apple Support
Finally - if problem still present -
Go to Settings>General>Reset
Reset the network settings - you will need to add the password of your home WiFi in your phone once more
The device should turn itself off & back on then go into Settings>Wifi and join your network

Error:Cannot connect to WMI provider. You do not have permission or the server is unreachable

I'm getting the below message when i try and access SQL Config Manager on my Windows Server 2003 R2
"Cannot connect to WMI provider. You do not have permission or the server is unreachable. Note that you can only manage SQL Server 2005 and later servers with SQL Server Configuration Manager.
Generic failure [0x80041001]"
Also tries with the below solution but still the error persists
The solution is to go to a command prompt as administrator and then run mofcomp.
C:\Program Files\Microsoft SQL Server\90\Shared>mofcomp "C:\Program Files\Microsoft SQL Server\90\Shared\sqlmgmproviderxpsp2up.mof"
Below was the output of the command:
Microsoft (R) 32-bit MOF Compiler Version 5.2.3790.1830
Copyright (c) Microsoft Corp. 1997-2001. All rights reserved.
Parsing MOF file: C:\Program Files (x86)\Microsoft SQL Server\100\Shared\sqlmgmp
roviderxpsp2up.mof
(1): error SYNTAX 0X8004402f: Error creating temporary file
Compiler returned error 0x8004402f
C:\Program Files (x86)\Microsoft SQL Server\100\Shared>
Can anyone tell how this problem can be solved?

Sorry for the mistake.The command prompt is
C:\Program Files (x86)\Microsoft SQL Server\100\Shared>mofcomp "C:\Program Files (x86)\Microsoft SQL Server\100\Shared\sqlmgmproviderxpsp2up.mof"
And error i got is
Microsoft (R) 32-bit MOF Compiler Version 5.2.3790.1830
Copyright (c) Microsoft Corp. 1997-2001. All rights reserved.
Parsing MOF file: C:\Program Files (x86)\Microsoft SQL Server\100\Shared\sqlmgmp
roviderxpsp2up.mof
(1): error SYNTAX 0X8004402f: Error creating temporary file
Compiler returned error 0x8004402f
C:\Program Files (x86)\Microsoft SQL Server\100\Shared>
I hav checked that sqlmgmproviderxpsp2up.mof is in C:\Program Files (x86)\Microsoft SQL Server\100\Shared\ folder.

I cannot log into facebook. I get the following message: 404 Error - Not Found The resource you have requested could not be found on the server. There are many possible reasons for this. Either the file does not exist, there is an error in your request,

I am not able to go to the facebook site. www.facebook.com is not working. I get the following error message. 404 Error - Not Found
The resource you have requested could not be found on the server. There are many possible reasons for this. Either the file does not exist, there is an error in your request, or the file is not accessible in the requested directory. Please verify that:
* You have used the proper case; requests ARE case-sensitive!
* You have entered the URL correctly. (i.e. proper directory/filename)
* You used the FULL URL. (i.e. proper file type: .html, .gif , .jpg, etc.)
* You use a tilde (~) before user directories. (i.e. www.furcen.org/~jurann/ )
* The user/file still exists on this server.
I also get redirected to "Busca Google" when typing www.facebook.com in the address bar.
== URL of affected sites ==
http://facebook.com; buscagoogle.com

I have the same problem and it does not have to do with firefox. Do you have any idea how to fix it through?

How to start weblogic in debug mode ? and how to set the eclipse in the deb

how to start weblogic in debug mode ? and how to set the eclipse in the debug

Put this in JAVA_OPTIONS :
Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,address=3999,suspend=y,server=y
After restarted weblogic, in eclipse set your breakpoint , open debug perspective then choose Remote Java Appliction and configure Connection Properties (host=localhost and port=3999)

Cannot start weblogic 8.1 User is not permitted to boot the server

Similar Messages

Maybe you are looking for