10.4.9 Server Starts in Verbose Mode

When I restart my G4 Server, it looks like it is starting like normal, shows the blue startup screen and says Mac Server is starting up, but when the bar reaches the end, it briefly goes to an all blue screen and then moves to a black screen with white text(verbose mode I think).
After searching the forums, I tried forcing the mac os x startup by holding command and x during startup, but nothing changes. I have also tried entering:
sudo nvram boot-args=""
to boot up normally, but still no change. I have tried repairing the disk in disk utility, booting from an external hard drive, but still boots in verbose mode.
Any help would be great.
1.6GHz G5 iMac   Mac OS X (10.4.10)  

Hi Dan-Cherokee:
What happens if you boot from the installer disk?
In the meantime try resetting the PRAM (ParameterRAM). Restart the server and hold down the command, alt, P and R keys at the same time. You should hear the start-up chime, keep them depressed until you hear the chime again, keep them depressed for a further start-up chime, now release the keys and immediately hold down the shift key. You will have to keep this depressed for some time as you are now booting in safe mode/boot. Eventually you will see the log in window with Safe Mode/Boot (in red) displayed, release the shift key and log in as normal, wait a few seconds and click on the trash icon, you should see a folder that has a long number for its name or possibly be called recovered items, delete this folder and reboot as normal. Safe Mode does a thorough check of your drive and directory as well as flushing system caches (this is what gets dumped into the trash).
Hope this helps – Tony

Similar Messages

  • Server started in RUNNING mode not showing in Startup Log File when MS Starts

    Dear all,
    When we start OSB Managed Server, server status is showing Running Status in Web logic console and it is also serving the requests. but in server Start up log file, it is not showing 'Server started in RUNNING mode' after it started.
    this behavior is only for 4 managed servers in cluster of 6 managed servers. other 2 managed servers are starting and showing the message correctly.
    please some body show some light on it as we need to fix this issue urgently.
    thanks in advance.
    pr

    Dear all,
    When we start OSB Managed Server, server status is showing Running Status in Web logic console and it is also serving the requests. but in server Start up log file, it is not showing 'Server started in RUNNING mode' after it started.
    this behavior is only for 4 managed servers in cluster of 6 managed servers. other 2 managed servers are starting and showing the message correctly.
    please some body show some light on it as we need to fix this issue urgently.
    thanks in advance.
    pr

  • WSM Managed server starts in ADMIN Mode after upgrade to 11.1.1.7

    We have just upgraded our 11g SOA Cluster environment from 11.1.1.4 to 11.1.1.7. The issue is after the upgrade, our WSM servers are starting to ADMIN state with following error.
    <Sep 25, 2013 7:14:35 AM PDT> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'DMS Application [Version=11.1.1.1.0]' due to error weblogic.application.ModuleException: Failed to load webapp: 'dms.war'.
    weblogic.application.ModuleException: Failed to load webapp: 'dms.war'
    Caused By: weblogic.management.DeploymentException: Error: Unresolved Webapp Library references for "ServletContext@381802823[app:DMS Application module:dms.war path:/dms spec-version:2.5 version:11.1.1.1.0]", defined in weblogic.xml [Extension-Name: jstl, Specification-Version: 1.2, Implementation-Version: 1.2, exact-match: false]
    at weblogic.servlet.internal.WebAppServletContext.processWebAppLibraries(WebAppServletContext.java:2750)
    Our cluster environment has one Admin Server, and two of each OSB, WSM and SOA managed servers. As our WSM servers are not coming up, we are not able to start our SOA servers too.
    Thank You

    Same issue here :-)), Just playing around with policies configuration, the server was running just fine, I wanted to check if the policies are applicable during runtime even the WSM managed server is down. After restart, it started in ADMIN mode, well the solution is straight. It is exactly telling that the dms application is missing the jstl library reference
    <Error> <Deployer> <iwpdcdevsoaa.iwater.ie> <WLS_WSM1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <bcfaf10ec8fbdfc2:-26d85d29:1429ffae24c:-8000-0000000000000003> <1385663491675> <BEA-149205> <Failed to initialize the application 'DMS Application [Version=11.1.1.1.0]' due to error weblogic.application.ModuleException: Failed to load webapp: 'dms.war'.
    weblogic.application.ModuleException: Failed to load webapp: 'dms.war'
            at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:395)
            at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:180)
            at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
            at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:518)
            at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
            at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159)
            at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:47)
            at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:649)
            at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
            at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
            at weblogic.application.internal.SingleModuleDeployment.prepare(SingleModuleDeployment.java:44)
            at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
            at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
            at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:144)
            at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:40)
            at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:191)
            at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:22)
            at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:261)
            at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:220)
            at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:166)
            at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
            at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:181)
            at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:97)
            at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
            at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
            at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
    Caused By: weblogic.management.DeploymentException: Error: Unresolved Webapp Library references for "ServletContext@384044243[app:DMS Application module:dms.war path:/dms spec-version:2.5 version:11.1.1.1.0]", defined in weblogic.xml [Extension-Name: jstl, Specification-Version: 1.2, Implementation-Version: 1.2, exact-match: false]
            at weblogic.servlet.internal.WebAppServletContext.processWebAppLibraries(WebAppServletContext.java:2750)
            at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:416)
            at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:494)
            at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:418)
            at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java:976)
            at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:384)
            at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:180)
            at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
            at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:518)
            at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
            at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159)
            at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:47)
            at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:649)
            at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
            at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
            at weblogic.application.internal.SingleModuleDeployment.prepare(SingleModuleDeployment.java:44)
            at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
            at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
            at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:144)
            at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:40)
            at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:191)
            at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:22)
            at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:261)
            at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:220)
            at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:166)
            at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
            at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:181)
            at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:97)
            at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
            at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
            at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
    >
    So search for "jstl" within the weblogic console in search bar, it is type of library, click on it and target it to the managed server where OWSM is running as weel. It was root cause in my case, somehow the library was not targeted to our WLS_WMS1 managed server. Now the server is back in RUNNING mode. Of course apply this in case of problem with SOA servers, target it to the cluster or exact nodes and it should work.
    Still I don't know how the issue has been crated, I don't think that somebody removed it from deployment. Rather I think that somebody was applying patch or some artifacts to OSB or SOA managed server and this library was required as well, but as soon as we have separated WSM cluster, it was maybe assuming that it is running within OSB or SOA clusters and therefore didn't target the WSM cluster automatically. But this is just the idea :-))
    Ladislav

  • OIM 11g server start up error

    Hi All,
    I am seeing below error when I start OIM server, any help ?
    <Jun 13, 2011 1:20:24 PM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
    <Jun 13, 2011 1:20:24 PM EDT> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
    <Jun 13, 2011 1:20:25 PM EDT> <Warning> <EJB> <BEA-010065> <MessageDrivenBean threw an Exception in onMessage(). The exception was:
    java.lang.NullPointerException.
    java.lang.NullPointerException
    at oracle.iam.platform.context.ContextManager.loadfromProxy(ContextManager.java:279)
    at oracle.iam.platform.context.ContextManager.loadContext(ContextManager.java:179)
    at oracle.iam.platform.async.impl.ContextUtil.reloadExecutionContext(ContextUtil.java:54)
    at oracle.iam.platform.async.impl.TaskExecutor.execute(TaskExecutor.java:53)
    at oracle.iam.platform.async.messaging.MessageReceiver.onMessage(MessageReceiver.java:68)
    Truncated. see log file for complete stacktrace
    >
    <Jun 13, 2011 1:20:25 PM EDT> <Warning> <EJB> <BEA-010065> <MessageDrivenBean threw an Exception in onMessage(). The exception was:
    java.lang.NullPointerException.
    java.lang.NullPointerException
    at oracle.iam.platform.context.ContextManager.loadfromProxy(ContextManager.java:279)
    at oracle.iam.platform.context.ContextManager.loadContext(ContextManager.java:179)
    at oracle.iam.platform.async.impl.ContextUtil.reloadExecutionContext(ContextUtil.java:54)
    at oracle.iam.platform.async.impl.TaskExecutor.execute(TaskExecutor.java:53)
    at oracle.iam.platform.async.messaging.MessageReceiver.onMessage(MessageReceiver.java:68)
    Truncated. see log file for complete stacktrace
    >
    <Jun 13, 2011 1:20:25 PM EDT> <Warning> <EJB> <BEA-010065> <MessageDrivenBean threw an Exception in onMessage(). The exception was:
    java.lang.NullPointerException.
    java.lang.NullPointerException
    at oracle.iam.platform.context.ContextManager.loadfromProxy(ContextManager.java:279)
    at oracle.iam.platform.context.ContextManager.loadContext(ContextManager.java:179)
    at oracle.iam.platform.async.impl.ContextUtil.reloadExecutionContext(ContextUtil.java:54)
    at oracle.iam.platform.async.impl.TaskExecutor.execute(TaskExecutor.java:53)
    at oracle.iam.platform.async.messaging.MessageReceiver.onMessage(MessageReceiver.java:68)
    Truncated. see log file for complete stacktrace
    >
    <Jun 13, 2011 1:20:25 PM EDT> <Warning> <EJB> <BEA-010216> <The Message-Driven EJB: oimKernelQueueMDB is throwing exception when processing the messages. Delivery failed after 11 attempts. The EJB container will suspend the message delivery for 5 seconds before retry.>
    <Jun 13, 2011 1:20:30 PM EDT> <Warning> <EJB> <BEA-010065> <MessageDrivenBean threw an Exception in onMessage(). The exception was:
    java.lang.NullPointerException.
    java.lang.NullPointerException
    at oracle.iam.platform.context.ContextManager.loadfromProxy(ContextManager.java:279)
    at oracle.iam.platform.context.ContextManager.loadContext(ContextManager.java:179)
    at oracle.iam.platform.async.impl.ContextUtil.reloadExecutionContext(ContextUtil.java:54)
    at oracle.iam.platform.async.impl.TaskExecutor.execute(TaskExecutor.java:53)
    at oracle.iam.platform.async.messaging.MessageReceiver.onMessage(MessageReceiver.java:68)
    Truncated. see log file for complete stacktrace
    >
    <Jun 13, 2011 1:20:30 PM EDT> <Warning> <EJB> <BEA-010216> <The Message-Driven EJB: oimKernelQueueMDB is throwing exception when processing the messages. Delivery failed after 21 attempts. The EJB container will suspend the message delivery for 10 seconds before retry.>
    <Jun 13, 2011 1:20:40 PM EDT> <Warning> <EJB> <BEA-010065> <MessageDrivenBean threw an Exception in onMessage(). The exception was:
    java.lang.NullPointerException.
    java.lang.NullPointerException
    at oracle.iam.platform.context.ContextManager.loadfromProxy(ContextManager.java:279)
    at oracle.iam.platform.context.ContextManager.loadContext(ContextManager.java:179)
    at oracle.iam.platform.async.impl.ContextUtil.reloadExecutionContext(ContextUtil.java:54)
    at oracle.iam.platform.async.impl.TaskExecutor.execute(TaskExecutor.java:53)
    at oracle.iam.platform.async.messaging.MessageReceiver.onMessage(MessageReceiver.java:68)
    Truncated. see log file for complete stacktrace
    >
    <Jun 13, 2011 1:20:40 PM EDT> <Warning> <EJB> <BEA-010216> <The Message-Driven EJB: oimKernelQueueMDB is throwing exception when processing the messages. Delivery failed after 31 attempts. The EJB container will suspend the message delivery for 20 seconds before retry.>

    Hi,
    For the first error and looking from WebLogic perspective "<EJB> <BEA-010065> <MessageDrivenBean threw an Exception in onMessage(). The exception was: java.lang.OutOfMemoryError." because MAXPERMSIZE in the start<servername>.cmd|SH is configured to small for the application. Normal solution should be increase MAXPERMSIZE . But you are also getting this "<BEA-010216> <The Message-Driven EJB: oimKernelQueueMDB is throwing exception when processing the messages." I recommend you to open an SR in Oracle Metalink to solve these errors.
    regards,
    Thiago L Guimaraes.

  • Booting in verbose mode after installing Mountain Lion

    I installed Mountain Lion on 3 machines. On my iMac I now boot after a cold start in verbose mode. What do I do to stop that? Thanks.

    Sorry, that I have no answer, but may be it helps psychologically to know that you are not alone. I have the same problem and maybe worse because the boot process holds at a certain point in single user mode and a root prompt. I have to enter "exit" to make it continue and startup properly. It looks like I have the same HW as you.

  • -debug  or -verbose mode for Oracle9is app server

    I am running Oracle9is Enterprise server. How do I set Debug or Verbose mode to see server stack. I tried DCMCTL utility with >dcmctl start -v -d
    but it didn't give me server stack. Any ideas?
    Thanks Denis

              Just looked in the server log file and found bridge debug messages :)
              (I was just watching the console)
              Hope I'm not filling this group with noise.
              Jeremy.
              

  • HELP! MacMini starting up in Verbose Mode

    Hi,
    My Mac Mini seems to be sarting up in Verbose Mode (black background with white type). Any ideas why this is happening? and how do I stop it?
    I've run Disk First Aid off the installion CD and its fixed all the problems that it found, but it still happening. Do I need to wipe the HD and start all over again, or try to just re-install the OS?
    Any words of wisdom?
    Thanks!
    Su
    Mac Mini   Mac OS X (10.4.9)  

    also download and install onyx
    http://www.titanium.free.fr/pgs2/english/download.html
    once installed, open onyx and go to the parameters tab, then go to the tab under that named login. find the one that says startup mode. select normal mode and it should reset it to normal.
    hope this helps
    -bjarec

  • Freezing at startup - weird message when starting up in verbose mode

    My macbook pro, only about 2 months old, freezes a lot while its starting up. i have to keep turning it off and on for it to work. It gets stuck at the grey screen with the apple and the loading icon.
    I decided to start up in verbose mode and maybe i can see what the problem is. So i did just that and i got this error message:
    SATA WARNING: completing a zero block transfer.
    it keeps repeating that message and scrolling down the screen forever.
    I have no idea what that could be.

    Most likely a problem with the disk and/or some corruption of the directory. Be sure to back up your own data if you haven't done so already. Then boot from your install disk and go to the menu bar and select Disk Utility and then Repair Disk. If it reports a problem and fixes it, run it again until everything comes up clean. If it reports a problem it can't fix you could invest in DiskWarrior, or, if you have AppleCare I believe you got a free copy of TechTool, you could try running that.
    Francine
    Francine
    Schwieder

  • How to start up MAC mini only in the verbose mode (command line) , no GUI

    Can anyone let me know how I can set up the mac mini to ALWAYS boot into a verbose mode only, no GUI interfaces at all?
    Mac Mini   Mac OS X (10.4.6)  
    Mac Mini   Mac OS X (10.4.6)  

    Hi, Andy your replies are really helpful. I did tried your method and also followed the link http://www.oreillynet.com/pub/h/348
    Now my mac mini - Tiger seems hanging forever at the boot up screen. A Apple log showed up with a message "Starting Mac OS X ..." and now almost 5 minutes passed, nothing happened ...

  • Managed server is not starting with MSI mode

    Managed server not starting with MSI mode even though we enabled the managed server independence mode
    Started the admin server and managed server first time enabled the MSI mode.
    Restarted all admin and Managed server.
    We have tested the following scenarios
    scenarios1: Stopped the Admin server and restarted the Managed server with MSI mode it comes up.
    scenarios2:Admin server is running but not able to connect to the managed server
    In this scenario
    we have removed the Network cable and restarted the managed server its throwing ldap error.
    <Aug 14, 2010 1:58:32 PM SGT> <Error> <Security> <BEA-090870> <The realm "myrealm" failed to be loaded: weblogic.security.service.SecurityServiceException: com.bea.common.engine.ServiceInitializationException: weblogic.security.spi.ProviderInitializationException: [Security:090730]Failed to verify credential mapper LDAP hierarchy
    netscape.ldap.LDAPException: failed to connect to server ldap://sgppsr00383:16827 (91)
    at netscape.ldap.LDAPConnSetupMgr.connectServer(LDAPConnSetupMgr.java:515)
    at netscape.ldap.LDAPConnSetupMgr.openSerial(LDAPConnSetupMgr.java:435) at netscape.ldap.LDAPConnSetupMgr.connect(LDAPConnSetupMgr.java:274)
    at netscape.ldap.LDAPConnSetupMgr.openConnection(LDAPConnSetupMgr.java:199)
    at netscape.ldap.LDAPConnThread.connect(LDAPConnThread.java:109)
    at netscape.ldap.LDAPConnection.connect(LDAPConnection.java:1083) at netscape.ldap.LDAPConnection.connect(LDAPConnection.java:954)
    at netscape.ldap.LDAPConnection.connect(LDAPConnection.java:781)
    at weblogic.ldap.EmbeddedLDAPConnection.getAndInitDelegate(EmbeddedLDAPConnection.java:2031)
    at weblogic.ldap.EmbeddedLDAPConnection.add(EmbeddedLDAPConnection.java:1065) at weblogic.security.providers.credentials.DefaultCredentialMapperLDAPHelper.addEntry(DefaultCredentialMapperLDAPHelper.java:537)
    at weblogic.security.providers.credentials.DefaultCredentialMapperLDAPHelper.createOrgUnit(DefaultCredentialMapperLDAPHelper.java:432)
    at weblogic.security.providers.credentials.DefaultCredentialMapperLDAPHelper.verifyHierarchy(DefaultCredentialMapperLDAPHelper.java:407)
    at weblogic.security.providers.credentials.DefaultCredentialMapperLDAPHelper.<init>(DefaultCredentialMapperLDAPHelper.java:146) at weblogic.security.providers.credentials.DefaultCredentialMapperLDAPHelper.getInstance(DefaultCredentialMapperLDAPHelper.java:112)
    at weblogic.security.providers.credentials.DefaultCredentialMapperProviderImpl.initialize(DefaultCredentialMapperProviderImpl.java:93)
    at com.bea.common.security.internal.legacy.service.SecurityProviderImpl.init(SecurityProviderImpl.java:53)
    at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:340) at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:292)
    at com.bea.common.engine.internal.ServiceEngineImpl.lookupService(ServiceEngineImpl.java:263)
    at com.bea.common.engine.internal.ServicesImpl.getService(ServicesImpl.java:71)
    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(CommonSecurityServiceManagerDelegateImpl.java:461) at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(CommonSecurityServiceManagerDelegateImpl.java:822)
    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealms(CommonSecurityServiceManagerDelegateImpl.java:851)
    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1007)
    at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:854) at weblogic.security.SecurityService.start(SecurityService.java:141)
    at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209) at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
    - with nested exception:
    Managed server looking for ldap configuration from admin server.
    I have checked the all configuration file same on both managed server and admin server.
    Please let me know How to recover the managed server in this scenario.
    Edited by: user10773210 on Aug 16, 2010 11:55 PM
    Edited by: user10773210 on Aug 17, 2010 2:38 AM

    thanks for the reply....
    the managed server is pointing to jrokit_160_22_D1.1.1-3 jdk....the server has enough ram also...while running the managed server showing status 'STARTING' for long period of time...and the admin server health goes 'Warning' because of threadpool....when we stop the managed server then adminserver health becomes ok...

  • How to start Weblogic 9.1 in verbose mode

    Hi all,
    I need to start Weblogic 9.1 in verbose mode.
    We have just recently migrated from weblogic 8 sp3 to weblogic 9.1. In weblogic 8 sp3, the option
    "-Dweblogic.ejb20.cmp.rdbms.codegen.verbose=true"
    would work but it doesn't work with Weblogic 9.1.
    Can anyone tell me how to do the same?
    Thanks and regards,
    Sachidanand

    If you close Firefox while in full screen mode then Firefox should reopen in full screen mode the next time.
    That choice is saved in the localstore.rdf file in the profile folder.
    *http://kb.mozillazine.org/localstore.rdf

  • Last week I've install Mac OS X Mountain Lion and then after the installation finish my IMAC start up in verbose mode. How can I turn off this mode and start my IMAC normally. I've try to key in the code "sudo nvram boot-args=" in terminal also.

    Last week I've install Mac OS X Mountain Lion and then after the installation finish my IMAC start up in verbose mode. How can I turn off this mode and start my IMAC normally. I've try to key in the code "sudo nvram boot-args=" in terminal also.
    Thank you for all of your answer.

    I've seen it mentioned on here that a PRAM reset may solve it:
    Reset PRAM
    Shut down the computer.
    Locate the following keys on the keyboard: Command, Option, P and R.
    You will need to hold these keys down simultaneously in step 4.
    Turn on the computer.
    Press and hold the Command-Option-P-R keys. You must press this key combination before the gray screen appears.
    Hold the keys down until the computer restarts and you hear the startup sound for the second time.
    Release the keys.

  • Start SQL Server in single user mode with parameter -m doesn't work well

    C:\Windows\system32>net start mssqlserver /m "Microsoft SQL Server Management St
    udio - Query"
    The SQL Server (MSSQLSERVER) service is starting.
    The SQL Server (MSSQLSERVER) service was started successfully.
    C:\Windows\system32>sqlcmd -S . -e
    1> go
    1> select @@servername;
    2> go
    select @@servername;
    myserver
    (1 rows affected)
    1>
    As you can see, I'm still able to connect with sqlcmd prompt to SQL Server. According production doc of SQL Server 2014, it should not be conncting by sqlcmd. it shall only be connected by SSMS.
    below the original doc on msdn:
    Start SQL Server in Single-User Mode
    Provide Feedback
    Under certain circumstances, you may have to start an instance of SQL Server
    in single-user mode by using the startup option -m. For
    example, you may want to change server configuration options or recover a
    damaged master database or other system database. Both actions require starting
    an instance of SQL Server in single-user mode.
    Starting SQL Server in single-user mode enables any member of the computer's
    local Administrators group to connect to the instance of SQL Server as a member
    of the sysadmin fixed server role. For more information, see Connect to
    SQL Server When System Administrators Are Locked
    Out.
    When you start an instance of SQL Server in single-user mode, note the
    following:
    Only one user can connect to the server.
    The CHECKPOINT process is not executed. By default, it is executed
    automatically at startup.
    Note
    Stop the SQL Server Agent service before connecting to an instance of SQL
    Server in single-user mode; otherwise, the SQL Server Agent service uses the
    connection, thereby blocking it.
    When you start an instance of SQL Server in single-user mode, SQL Server
    Management Studio can connect to SQL Server. Object Explorer in Management
    Studio might fail because it requires more than one connection for some
    operations. To manage SQL Server in single-user mode, execute Transact-SQL
    statements by connecting only through the Query Editor in Management Studio, or
    use the
    sqlcmd utility.
    When you use the -m option with sqlcmd or
    Management Studio, you can limit the connections to a specified client
    application. For example, -m"sqlcmd" limits connections to a
    single connection and that connection must identify itself as the
    sqlcmd client program. Use this option when you are starting
    SQL Server in single-user mode and an unknown client application is taking the
    only available connection. To connect through the Query Editor in Management
    Studio, use -m"Microsoft SQL Server Management Studio - Query".
    Shawn

    Hi Shawn Xiao,
    For starting SQL Server instance in single user mode, we can add –m; parameter in SQL Server Configuration Manager, also we can run CMD with ‘Run as administrator’ and input the following statement.
    NET START MSSQLSERVER /m
    I do a test in SQL Server 2014 Express version, after starting SQL with Single User Mode, SQL Server will only accept one connection. If you connect to SQL Server with a user account, the following error will occur.
    Login failed for user ‘domain\username’. Reason: Server is in single user mode. Only one administrator can connect at this time.
    However, in your situation, you can connect to SQL Server and run T-SQL statement successfully, it can be due to connection with the administrator account in your sqlcmd.
    For more information, you can review the following article.
    http://zarez.net/?p=117
    Regards,
    Sofiya Li
    Sofiya Li
    TechNet Community Support

  • 10.6 Verbose mode stops at ACPI_SMC_PlatformPlugin::start....

    Macbook not booting and stalls at spinning gear.
    Tried many things but ended up booting into verbose mode and it stops at
    ACPI_SMC_PlatformPlugin::start - watiForService(resourceMattching(AppleIntelCPUPowerManagement) timed out.
    Previously in the boot, it says it failed to load that kext because the link failed.
    - Tried repairing permissions
    - Netbooting into AST and running MRI. No errors. Reset SMC and NVRAM. No change.
    - Swapped RAM
    - Made image and restored to a new hard drive. Same problems.
    - Booted different computer from the harddrive. Still get spinning gear.
    - Swapped hard drive for a working one from another laptop and it booted fine.
    Any thoughts before I wipe the HD it and start from scratch?

    Dont wipe the hard drive!
    Just had this problem on a macbook pro 2011 at my work (computer repair business).  The problem occurred after switching out the hard drive and hard drive cable.  Tried booting an Apple Hardware Test, by install disk, or by bootable USB OSx.  Each time the verbose popped up before completing boot and ended at a failure of the load of the driver regarding cpu power management. 
    Ultimately, the problem was a corruption of the firmware, which is embedded in flash-based rom chips on the logic board.  The Apple website has the firmware for your model available and it should boot from the disk without trouble. 
    Incidentally, all attempts to boot failed except when booting to the OSx Lion full install from USB.  This alone seemed to bypass the corruption.  Regardless, the firmware restore should do it. 
    So don't wipe your drive.

  • SSRS error - verbose mode

    We have a SCCM and use SQL 2012 server for reporting. Recently we have started experiencing a problem where we can browse to the reports and once we do run the reports, it tries to run forever and eventually halts with the following error
    An error occurred within the report server database. This may be due to a connection failure, timeout or low disk condition within the database. (rsReportServerDatabaseError) 
    I have enabled verbose mode on the sql server and restarted the reporting service. Below is the log file where I am hoping someone will be able to tell me what the issue is:
    <Header>
      <Product>Microsoft SQL Server Reporting Services Version 2011.0110.5058.00 ((SQL11_PCU_Main).140514-1820 )</Product>
      <Locale>English (United Kingdom)</Locale>
      <TimeZone>GMT Standard Time</TimeZone>
      <Path>E:\Program Files\Microsoft SQL Server\MSRS11.INSTANCE2\Reporting Services\Logfiles\ReportServerService__12_18_2014_14_54_36.log</Path>
      <SystemName>SRVPRDAPPDB1</SystemName>
      <OSName>Microsoft Windows NT 6.2.9200</OSName>
      <OSVersion>6.2.9200</OSVersion>
      <ProcessID>27476</ProcessID>
      <Virtualization>None</Virtualization>
    </Header>
    <ProcessorArchitecture>AMD64</ProcessorArchitecture>
    <ApplicationArchitecture>AMD64</ApplicationArchitecture>
    rshost!rshost!4d58!12/18/2014-14:54:36:: i INFO: CLR runtime is initialized.
    rshost!rshost!4d58!12/18/2014-14:54:36:: v VERBOSE: Initializing Memory Monitoring
    rshost!rshost!4d58!12/18/2014-14:54:36:: i INFO: Derived memory configuration based on physical memory as 268369396 KB
    rshost!rshost!4d58!12/18/2014-14:54:36:: v VERBOSE: Supported winsock version is 2.2.
    appdomainmanager!DefaultDomain!4d58!12/18/2014-14:54:36:: i INFO: Entered managed ServiceMain in DefaultDomain.
    configmanager!DefaultDomain!6728!12/18/2014-14:54:37:: e ERROR: Configuration file element UrlReservation has a invalid VirtualRoot. It will be ignored.
    configmanager!DefaultDomain!6728!12/18/2014-14:54:37:: e ERROR: Configuration file element UrlReservation has a invalid VirtualRoot. It will be ignored.
    library!DefaultDomain!6728!12/18/2014-14:54:37:: i INFO: Initializing ConnectionType to '0'  as specified in Configuration file.
    library!DefaultDomain!6728!12/18/2014-14:54:37:: i INFO: Initializing SecureConnectionLevel to '0'  as specified in Configuration file.
    library!DefaultDomain!6728!12/18/2014-14:54:37:: i INFO: Initializing DisableSecureFormsAuthenticationCookie to 'False'  as specified in Configuration file.
    library!DefaultDomain!6728!12/18/2014-14:54:37:: i INFO: Initializing CleanupCycleMinutes to '10' minute(s) as specified in Configuration file.
    library!DefaultDomain!6728!12/18/2014-14:54:37:: i INFO: Initializing MaxActiveReqForOneUser to '20' requests(s) as specified in Configuration file.
    library!DefaultDomain!6728!12/18/2014-14:54:37:: i INFO: Initializing DatabaseQueryTimeout to '120' second(s) as specified in Configuration file.
    library!DefaultDomain!6728!12/18/2014-14:54:37:: i INFO: Initializing RunningRequestsScavengerCycle to '60' second(s) as specified in Configuration file.
    library!DefaultDomain!6728!12/18/2014-14:54:37:: i INFO: Initializing RunningRequestsDbCycle to '60' second(s) as specified in Configuration file.
    library!DefaultDomain!6728!12/18/2014-14:54:37:: i INFO: Initializing RunningRequestsAge to '30' second(s) as specified in Configuration file.
    library!DefaultDomain!6728!12/18/2014-14:54:37:: i INFO: Initializing MaxScheduleWait to '5' second(s) as specified in Configuration file.
    library!DefaultDomain!6728!12/18/2014-14:54:37:: i INFO: Initializing DisplayErrorLink to 'True'  as specified in Configuration file.
    library!DefaultDomain!6728!12/18/2014-14:54:37:: i INFO: Initializing WebServiceUseFileShareStorage to 'False'  as specified in Configuration file.
    library!DefaultDomain!6728!12/18/2014-14:54:37:: i INFO: Initializing WatsonFlags to '1064'  as specified in Configuration file.
    library!DefaultDomain!6728!12/18/2014-14:54:37:: i INFO: Initializing WatsonDumpOnExceptions to 'Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException,Microsoft.ReportingServices.Modeling.InternalModelingException,Microsoft.ReportingServices.ReportProcessing.UnhandledReportRenderingException'
     as specified in Configuration file.
    library!DefaultDomain!6728!12/18/2014-14:54:37:: i INFO: Initializing WatsonDumpExcludeIfContainsExceptions to 'System.Threading.ThreadAbortException,System.Web.UI.ViewStateException,System.OutOfMemoryException,System.Web.HttpException,System.IO.IOException,System.IO.FileLoadException,Microsoft.SharePoint.SPException,Microsoft.ReportingServices.WmiProvider.WMIProviderException'
     as specified in Configuration file.
    library!DefaultDomain!6728!12/18/2014-14:54:37:: i INFO: Initializing AuthenticationTypes to '4'  as specified in Configuration file.
    library!DefaultDomain!6728!12/18/2014-14:54:37:: i INFO: Initializing RSWindowsExtendedProtectionLevel to 'Off'  as specified in Configuration file.
    library!DefaultDomain!6728!12/18/2014-14:54:37:: i INFO: Initializing RSWindowsExtendedProtectionScenario to 'Proxy'  as specified in Configuration file.
    library!DefaultDomain!6728!12/18/2014-14:54:37:: i INFO: Initializing EnableAuthPersistence to 'True'  as specified in Configuration file.
    library!DefaultDomain!6728!12/18/2014-14:54:37:: i INFO: Initializing IsSchedulingService to 'True'  as specified in Configuration file.
    library!DefaultDomain!6728!12/18/2014-14:54:37:: i INFO: Initializing IsNotificationService to 'True'  as specified in Configuration file.
    library!DefaultDomain!6728!12/18/2014-14:54:37:: i INFO: Initializing IsEventService to 'True'  as specified in Configuration file.
    library!DefaultDomain!6728!12/18/2014-14:54:37:: i INFO: Initializing PollingInterval to '10' second(s) as specified in Configuration file.
    library!DefaultDomain!6728!12/18/2014-14:54:37:: i INFO: Initializing WindowsServiceUseFileShareStorage to 'False'  as specified in Configuration file.
    library!DefaultDomain!6728!12/18/2014-14:54:37:: i INFO: Initializing MemorySafetyMargin to '80' percent as specified in Configuration file.
    library!DefaultDomain!6728!12/18/2014-14:54:37:: i INFO: Initializing MemoryThreshold to '90' percent as specified in Configuration file.
    library!DefaultDomain!6728!12/18/2014-14:54:37:: i INFO: Initializing RecycleTime to '720' minute(s) as specified in Configuration file.
    library!DefaultDomain!6728!12/18/2014-14:54:37:: i INFO: Initializing MaxAppDomainUnloadTime to '30' minute(s) as specified in Configuration file.
    library!DefaultDomain!6728!12/18/2014-14:54:37:: i INFO: Initializing MaxQueueThreads to '0' thread(s) as specified in Configuration file.
    library!DefaultDomain!6728!12/18/2014-14:54:37:: w WARN: Initializing UrlRoot to default value of ''  because it was incorrectly specified in Configuration file as ''.
    library!DefaultDomain!6728!12/18/2014-14:54:37:: i INFO: Initializing IsWebServiceEnabled to 'True'  as specified in Configuration file.
    library!DefaultDomain!6728!12/18/2014-14:54:37:: i INFO: Initializing IsReportManagerEnabled to 'True'  as specified in Configuration file.
    library!DefaultDomain!6728!12/18/2014-14:54:37:: i INFO: Initializing MaxConnections to '2'  as specified in Configuration file.
    library!DefaultDomain!6728!12/18/2014-14:54:37:: i INFO: Initializing Timeout to '10' second(s) as specified in Configuration file.
    library!DefaultDomain!6728!12/18/2014-14:54:37:: i INFO: Initializing AppID to '(Default)'  as specified in Configuration file.
    library!DefaultDomain!6728!12/18/2014-14:54:37:: i INFO: Initializing CacheLevel to 'Default'  as specified in Configuration file.
    resourceutilities!DefaultDomain!6728!12/18/2014-14:54:37:: i INFO: Reporting Services starting SKU: Standard
    configmanager!DefaultDomain!6728!12/18/2014-14:54:37:: e ERROR: Failed to get url configuration section.
    configmanager!DefaultDomain!6728!12/18/2014-14:54:37:: e ERROR: Failed to get url configuration section.
    configmanager!DefaultDomain!6728!12/18/2014-14:54:37:: w WARN: IsApplicationUrlSubsetOfReportServer() -- Failed to get url configuration section.
    configmanager!DefaultDomain!6728!12/18/2014-14:54:37:: i INFO: Using report server internal url .
    configmanager!DefaultDomain!6728!12/18/2014-14:54:37:: i INFO: Using report server external url .
    configmanager!DefaultDomain!6728!12/18/2014-14:54:37:: i INFO: Using url root .
    rshost!rshost!6728!12/18/2014-14:54:37:: i INFO: Configuring maxPhysicalCpu=4, minLogicalCpu=0
    rshost!rshost!6728!12/18/2014-14:54:37:: i INFO: Logical processor per physical processor 16
    rshost!rshost!6728!12/18/2014-14:54:37:: i INFO: Logical processor per core 2
    rshost!rshost!6728!12/18/2014-14:54:37:: i INFO: Maximum logical CPU is 32
    library!DefaultDomain!6728!12/18/2014-14:54:37:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: No DSN present in configuration file, Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException:
    The report server has encountered a configuration error. ;
    servicecontroller!DefaultDomain!6728!12/18/2014-14:54:37:: e ERROR: Error initializing configuration from the database: Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: The report server has encountered a configuration error. 
    library!DefaultDomain!6728!12/18/2014-14:54:37:: i INFO: SQLDump flags: ReferencedMemory, AllThreads, SendToWatson
    library!DefaultDomain!6728!12/18/2014-14:54:37:: i INFO: MiniDump flags: DataSegs, UnloadedModules, ProcessThreadData
    library!DefaultDomain!6728!12/18/2014-14:54:37:: i INFO: Dump on: Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException,Microsoft.ReportingServices.Modeling.InternalModelingException,Microsoft.ReportingServices.ReportProcessing.UnhandledReportRenderingException
    library!DefaultDomain!6728!12/18/2014-14:54:37:: i INFO: Do not dump on: System.Threading.ThreadAbortException,System.Web.UI.ViewStateException,System.OutOfMemoryException,System.Web.HttpException,System.IO.IOException,System.IO.FileLoadException,Microsoft.SharePoint.SPException,Microsoft.ReportingServices.WmiProvider.WMIProviderException
    library!DefaultDomain!6728!12/18/2014-14:54:37:: i INFO: Minidump location: E:\Program Files\Microsoft SQL Server\MSRS11.INSTANCE2\Reporting Services\Logfiles
    library!DefaultDomain!6728!12/18/2014-14:54:37:: v VERBOSE: Setting unhandled exception handler
    appdomainmanager!DefaultDomain!6728!12/18/2014-14:54:37:: i INFO: Appdomain:2 WindowsService_0 started.
    library!WindowsService_0!6728!12/18/2014-14:54:37:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: No DSN present in configuration file, Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException:
    The report server has encountered a configuration error. ;
    servicecontroller!WindowsService_0!6728!12/18/2014-14:54:37:: e ERROR: Error initializing configuration from the database: Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: The report server has encountered a configuration
    error. 
    library!WindowsService_0!6728!12/18/2014-14:54:38:: i INFO: SQLDump flags: ReferencedMemory, AllThreads, SendToWatson
    library!WindowsService_0!6728!12/18/2014-14:54:38:: i INFO: MiniDump flags: DataSegs, UnloadedModules, ProcessThreadData
    library!WindowsService_0!6728!12/18/2014-14:54:38:: i INFO: Dump on: Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException,Microsoft.ReportingServices.Modeling.InternalModelingException,Microsoft.ReportingServices.ReportProcessing.UnhandledReportRenderingException
    library!WindowsService_0!6728!12/18/2014-14:54:38:: i INFO: Do not dump on: System.Threading.ThreadAbortException,System.Web.UI.ViewStateException,System.OutOfMemoryException,System.Web.HttpException,System.IO.IOException,System.IO.FileLoadException,Microsoft.SharePoint.SPException,Microsoft.ReportingServices.WmiProvider.WMIProviderException
    library!WindowsService_0!6728!12/18/2014-14:54:38:: i INFO: Minidump location: E:\Program Files\Microsoft SQL Server\MSRS11.INSTANCE2\Reporting Services\Logfiles
    library!WindowsService_0!6728!12/18/2014-14:54:38:: v VERBOSE: Setting unhandled exception handler
    resourceutilities!WindowsService_0!6728!12/18/2014-14:54:38:: i INFO: Reporting Services starting SKU: Standard
    library!WindowsService_0!5c98!12/18/2014-14:54:38:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: No DSN present in configuration file, Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException:
    The report server has encountered a configuration error. ;
    library!WindowsService_0!5c98!12/18/2014-14:54:38:: e ERROR: ServiceStartThread: Exception caught while starting service. Error: Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: The report server has encountered a configuration
    error. 
    library!WindowsService_0!5c98!12/18/2014-14:54:38:: e ERROR: ServiceStartThread: Attempting to start service again...
    rpcserver!DefaultDomain!5c98!12/18/2014-14:54:38:: i INFO: RPC Server started.
    servicecontroller!DefaultDomain!5c98!12/18/2014-14:54:38:: i INFO: RPC Server started. Endpoint name ='ReportingServices$MSRS11.INSTANCE2'
    rshost!rshost!370c!12/18/2014-14:54:38:: w WARN: Endpoint 2 is enabled but no url is registered for vdir=, pdir=E:\Program Files\Microsoft SQL Server\MSRS11.INSTANCE2\Reporting Services\ReportServer.
    rshost!rshost!4e68!12/18/2014-14:54:38:: w WARN: Endpoint 3 is enabled but no url is registered for vdir=, pdir=E:\Program Files\Microsoft SQL Server\MSRS11.INSTANCE2\Reporting Services\ReportManager.
    rshost!rshost!4e68!12/18/2014-14:54:38:: i INFO: Endpoint 4 is disabled and no url is registered vdir=, pdir=E:\Program Files\Microsoft SQL Server\MSRS11.INSTANCE2\Reporting Services\ReportServer\ReportBuilder.
    resourceutilities!DefaultDomain!6728!12/18/2014-14:54:38:: i INFO: Maximum memory limit is 65536Mb
    rshost!rshost!6728!12/18/2014-14:54:38:: i INFO: Derived memory configuration based on physical memory as 67108864 KB
    rpcserver!DefaultDomain!432c!12/18/2014-14:54:38:: i INFO: Process monitoring started.
    servicecontroller!DefaultDomain!3a4c!12/18/2014-14:54:38:: i INFO: Total Physical memory: 274810261504
    Thanks.

    This was to do with NIC settings on the SQL server. There was a mis-configuration where data was taking long time to copy. Once we have corrected this, all started to work just fine.

Maybe you are looking for

  • Lumia 925 black-update phone stuck

    I installed the black-update yesterday on my 925, in the beginnings no problems, but this morning when I tried to unlock my phone I typed my password but then the phone got stuck in the lock screen. After 3 minutes it automatically locked itself but

  • How do I ge tthe background color of a browser window.

    How do I get the default backgound color of a browser. I made my Applet with white as the background color. My supervisor's IE settings makes his IE background color tan. Is there any way I can read that "tan" from somewhere and use that as my Applet

  • Load large applet

    I have a large applet. I want to show a status bar that indicates the percentage of the loading status. How can I do that?

  • Move content to apple tv

    I have just put my apple tv back to my TV after a long time absence and I am unable to trasfer itunes content like music to my apple tv. I see that my computer is sync as I have the chain icon in the settings menu but cant figure out what to do next.

  • No Go! Why can't I find this in Help?

    Vista  Prem Elems 4.0:   Happily editing away when this icon appears   <ll> with a red slash / across (= No you can't!). Then  I can't  alter audio volume or move any clips.  What causes this and how prevent  it?  Exit and start again puts it right -