Server start sequence

We have a clustered environment with 2 boxes running 2 instances of WLS clustered across the boxes.During the start-up,after server started message, after 'adding server to cluster view, the last item is:<ListenThread> Adding address: ip/ip to licensed client list.ip address here does not look consistent. on one app box, the ip address is that of other app box. (.28/.28 and .28/.28) for both the instancesOn the other box, the ip address is the backend address of our web boxes (.21/.21) for one instance and (.22/.22) for the other instance.I would like to understand the message.Thanks much.
          

gday Sunil --
I'd try reposting this Portal question to either the Portal forum on OTN or the General Application Server forum. You're likely to get access to more Portal specific folks there.
cheers
-steve-

Similar Messages

  • Import Server & Port Sequence

    Hi All ,
    We are using import server for importing records into MDM.
    In our scenarios ,we are using mulitiple ports &  depending on condition, files/records are dropped into particular port.
    For Eg. There 3 ports say .. Port1 , Port 2 , Port3 . Files are dropped into ready folders of these port thro' XI.
    Now when import server starts , files are imported from Port1 , then from Port2 , & lastly from Port3.
    But Business scenario requires , file to be imported from Port3 first , after that Port1 & Port 2 resp.
    Does anybody know how to do it using import server?
    We dont want to use import batch .
    Thanks ,
    Nilesh

    Hi Nilesh,
    Could you please change the sequence of the Ports in the Port table, the way you
    want to Import the informations...and do run the scenario...
    please feel free to revert to me if things doesn't workk...
    thanks
    Alexander
    P.S. Kindly reward the points, if found problem solved..
    Hey sorry guys my solution pretty similar since I have posted almost on the same time....
    Message was edited by: Alexander Raja
            Alexander Raja

  • How to load a java class at server start-up

    Hi,
    I have one custome java class that is being referenced by all the applications deployed in OC4J container. How can I load that class automatically and be evailable in the path at server start-up time. Is there an option available to give the class name that also gets loaded automatically.
    Thanks

    To me, you have two mixed issues.
    1. OC4J supports a startup/shutdown model where a named class will be invoked when the container is started (or stopped).
    This is described in the doc here:
    http://download-west.oracle.com/docs/cd/B32110_01/web.1013/b28952/startclas.htm#CIHECEIB
    Note that this specifically calls the methods that are implemented from the respective OC4JShutdown and OC4JStartup interfaces -- the class that is instantiated and called here is not available to all other applications by default. This is more to suit the need where something needs to be done when the container is started/stopped.
    2 The next option is where you just want to make a class available to all applications deployed to the container. For this we provide the shared-library mechanism. Using this you can either make use of the implicit global.libraries shared-lib in which you simply drop JAR files into the j2ee/home/applib directory whereupon the classes will become available by default to all applications. Or you can choose to install a shared-library that contains your specific classes (in a JAR file) and then import that into the default application whereupon the configuration will be inherited by all deployed applications.
    cheers
    -steve-

  • Server start or server stop sometimes hands

    If I try to delete the server because its not responding to a stop then that does not work too.
    I deleted the server entry in the server.xml, and this removed the server however I may have screwed something up by doing that!
    Why do I do when the server start sort of hands at around 23%, this is on a new server with nothing published as yet...
    Also it is picking up jrockit to start and stop, even after I set eclipse up with 1.5 vm.... Anyway around other than modifying setDomainEnv.cmd ?
    Thankyou, (I WILL get this thing to work for me. The productivity boost is so very tantalizing!)

    The VM used to start weblogic is irrelevant to the VM used with Eclipse.
    Set JAVA_VENDOR=Sun in setDomainEnv.cmd to use Sun JDK.
    To troubleshotting the server stop problem,
    try manually run [domian]/bin/stopWebLogic.cmd
    see any difference.

  • Is there any way to get an application to load automatically on server start?

    We're trying to implement a load-balancing mechanism between FMS hosts in a virtual "farm".  The mechanism we're using is to have the FMSs periodically send "load" data (along with a timestamp) to an application server.  That server will then use that load information and timestamp to detect when an FMS server has gone down and to make stream assignments to FMSs.
    Right now, I've implemented this code via a setInterval() in live/main.asc.  I've added a "return false" to Application.onAppStop() to (according to the docs, I haven't tested this yet) keep the server from shutting down an idle instance.  So I've left with a "chicken and egg" issue: how do I get the interval running before the first request hits the application (and forces the load of the application)?  I've tried putting the setInterval in onAppStart() and as a global.  In both cases, it only gets executed after application is loaded.
    So, is there any way to force an application to load (via a config file parameter or local command-line)?

    Hi,
    I am sorry i have not read the full details what you wrote, but if you are looking for loading of application on start of the server, there is a configuration tag in application.xml called loadonstartup and by default it is set to false. Set it to true to enable it and all the apps will be loaded on server start.
    alternatively , you can make an application.xml inside the application folder and set this tag to true, to have this applied only to a particular application,
    Also, the fms admin console can launch a new instance of an app without any connection being made initially.
    Thank you !

  • Using environment variable / double quotes in "Arguments" in "Server Start"

    I have an admin server, NodeManager, and 1 managed server, all on the same machine (windows). I am trying to enter something similar to this to the arguments field in the Server Start tab:
    -Dmy.property=%USERPROFILE%\someDir\someJar.jar
    But when the managed server is started it throws this exception:
    Error opening zip file or JAR manifest missing : %USERPROFILE%\someDir\someJar.jar
    It appears that the environment variable is not being translated into it's value. It is just passed on to the managed server as plain-text. I tried surrounding the path with double quotes (") but the console validates the input and does not allow this: *"Arguments may not contain '"'"*
    Even editing the config.xml file manually cannot work, as the admin server fails to startup after this:
    <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason: [Management:141266]Parsing failure in config.xml: java.lang
    .IllegalArgumentException: Arguments may not contain '"'.>
    I also tried using %20 to no avail, it is just passed as %20.
    I thought that perhaps this had something to do with the spaces in the value of %USERPROFILE% (which is "C:\documents and settings.."), but the same thing happens with other env. variables which point to other directories with no spaces.
    _My question:_
    Is there any supported way of :
    using double quotes? what if i have to reference a folder with spaces in it's name?
    reference an environment variable? What if i have to rely on it's value for distributed servers where i do not know in advance the variable's value?
    Edited by: 937622 on Sep 28, 2012 1:02 AM

    There is workaround : http://stackoverflow.com/questions/12629395/weblogic-using-environment-variable-double-quotes-in-arguments-in-server
    Just posting here for reference. Let's see if we get a different answer from anyone else.

  • Server start up error

    I have configured two applications on two different domains belonging to two different instances of my weblogic server.Now I am getting the following error:
    While starting the second instance of my weblogic server ,I am getting the error-' Server cannot be launched within timeout '.The first instance is starting properly.
    My weblogic server version is 10.
    Please help!!

    I have weblogic10 server installed on my workstation.In that I have created two domains base_domain and dest_domain,in each domain I have created one server instance and both are named AdminServer.In each server instance I have deployed one seperate Application.
    The server instance that is starting is having a cmd window opened with the script responsible for server start up running in it successfully.
    But when I start the second server instance it does not open any such window.
    And yes I see the server log for the server instance getting started and do not see any such server log for the instance that fails to start.

  • Weblogic Admin server - Configuration/Server Start/Arguments ignored?

    Hi,
    I'm trying to specify a http proxy for a WebLogic Admin Server in order for an application to access external resources. I've placed the settings into the "Server Configuration / Server Start / Arguments", and verified that they have been saved into the config/config.xml file for that domain:
    <server-start>
    <arguments>-Dhttp.proxyHost=[XXXX] -Dhttp.proxyPort=8080</arguments>
    <password-encrypted>[XXXX]</password-encrypted>
    </server-start>
    However, no matter how I start the server, these settings are ignored despite that the documentation states these should be added to the java command line.
    starting weblogic with Java version:
    java version "1.6.0_19"
    Java(TM) SE Runtime Environment (build 1.6.0_19-b04)
    Java HotSpot(TM) 64-Bit Server VM (build 16.2-b04, mixed mode)
    Starting WLS with line:
    C:\PROGRA~1\Java\JDK16~1.0_1\bin\java -client -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=128m -XX:MaxPermSize=256m -Dweblogic.Name=AdminServer -Djava.security.policy=C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.policy -Xverify:none -da -Dplatform.home=C:\Oracle\MIDDLE~1\WLSERV~1.3 -Dwls.home=C:\Oracle\MIDDLE~1\WLSERV~1.3\server -Dweblogic.home=C:\Oracle\MIDDLE~1\WLSERV~1.3\server -Dweblogic.management.discover=true -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=C:\Oracle\MIDDLE~1\patch_wls1032\profiles\default\sysext_manifest_classpath weblogic.Server
    As a test I created a new managed server in the same domain, specifying the same startup properties, and they were picked up during startup.
    If I manually place the settings into the bin/setDomainEnv.cmd batch file for the domain they are also picked up and work.
    Is there an undocumented restriction on Admin Servers that they ignore the "Server Start / Arguments" setting, or is there something else I can check as to why this is not working?
    Many thanks,
    - Micha.

    Umm... I already pasted the relevant snippet out of the config.xml, but following is the entire file. The startup arguments, as specified in the admin console, are:
    -Dhttp.proxyHost=[XXXXXXXX] -Dhttp.proxyPort=8080
    which matches what is saved in the config.xml.
    <?xml version='1.0' encoding='UTF-8'?>
    <domain xmlns="http://xmlns.oracle.com/weblogic/domain" xmlns:sec="http://xmlns.oracle.com/weblogic/security" xmlns:wls="http://xmlns.oracle.com/weblogic/security/wls" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.oracle.com/weblogic/security/xacml http://xmlns.oracle.com/weblogic/security/xacml/1.0/xacml.xsd http://xmlns.oracle.com/weblogic/security/providers/passwordvalidator http://xmlns.oracle.com/weblogic/security/providers/passwordvalidator/1.0/passwordvalidator.xsd http://xmlns.oracle.com/weblogic/domain http://xmlns.oracle.com/weblogic/1.0/domain.xsd http://xmlns.oracle.com/weblogic/security http://xmlns.oracle.com/weblogic/1.0/security.xsd http://xmlns.oracle.com/weblogic/security/wls http://xmlns.oracle.com/weblogic/security/wls/1.0/wls.xsd">
    <name>wls_starter</name>
    <domain-version>10.3.2.0</domain-version>
    <security-configuration>
    <name>wls_starter</name>
    <realm>
    <sec:authentication-provider xsi:type="wls:default-authenticatorType"></sec:authentication-provider>
    <sec:authentication-provider xsi:type="wls:default-identity-asserterType">
    <sec:active-type>AuthenticatedUser</sec:active-type>
    </sec:authentication-provider>
    <sec:role-mapper xmlns:xac="http://xmlns.oracle.com/weblogic/security/xacml" xsi:type="xac:xacml-role-mapperType"></sec:role-mapper>
    <sec:authorizer xmlns:xac="http://xmlns.oracle.com/weblogic/security/xacml" xsi:type="xac:xacml-authorizerType"></sec:authorizer>
    <sec:adjudicator xsi:type="wls:default-adjudicatorType"></sec:adjudicator>
    <sec:credential-mapper xsi:type="wls:default-credential-mapperType"></sec:credential-mapper>
    <sec:cert-path-provider xsi:type="wls:web-logic-cert-path-providerType"></sec:cert-path-provider>
    <sec:cert-path-builder>WebLogicCertPathProvider</sec:cert-path-builder>
    <sec:name>myrealm</sec:name>
    <sec:password-validator xmlns:pas="http://xmlns.oracle.com/weblogic/security/providers/passwordvalidator" xsi:type="pas:system-password-validatorType">
    <sec:name>SystemPasswordValidator</sec:name>
    <pas:min-password-length>8</pas:min-password-length>
    <pas:min-numeric-or-special-characters>1</pas:min-numeric-or-special-characters>
    </sec:password-validator>
    </realm>
    <default-realm>myrealm</default-realm>
    <credential-encrypted>[XXXXXXXXXX]</credential-encrypted>
    <node-manager-username>weblogic</node-manager-username>
    <node-manager-password-encrypted>[XXXXXXXX]</node-manager-password-encrypted>
    </security-configuration>
    <server>
    <name>AdminServer</name>
    <max-http-message-size>-1</max-http-message-size>
    <ssl>
    <enabled>false</enabled>
    </ssl>
    <log>
    <file-name>logs/AdminServer.log</file-name>
    <rotation-type>bySize</rotation-type>
    <number-of-files-limited>true</number-of-files-limited>
    <file-count>7</file-count>
    <file-min-size>500</file-min-size>
    <rotate-log-on-startup>true</rotate-log-on-startup>
    <logger-severity>Trace</logger-severity>
    <logger-severity-properties></logger-severity-properties>
    <log-file-severity>Info</log-file-severity>
    <stdout-severity>Info</stdout-severity>
    <domain-log-broadcast-severity>Notice</domain-log-broadcast-severity>
    <memory-buffer-severity>Debug</memory-buffer-severity>
    <log4j-logging-enabled>false</log4j-logging-enabled>
    <redirect-stdout-to-server-log-enabled>false</redirect-stdout-to-server-log-enabled>
    <domain-log-broadcaster-buffer-size>1</domain-log-broadcaster-buffer-size>
    </log>
    <machine>[XXXXXXXXXX]</machine>
    <listen-port>8080</listen-port>
    <listen-port-enabled>true</listen-port-enabled>
    <web-server>
    <frontend-http-port>0</frontend-http-port>
    <frontend-https-port>0</frontend-https-port>
    <keep-alive-enabled>true</keep-alive-enabled>
    <keep-alive-secs>30</keep-alive-secs>
    <https-keep-alive-secs>60</https-keep-alive-secs>
    <post-timeout-secs>30</post-timeout-secs>
    <max-post-size>-1</max-post-size>
    <send-server-header-enabled>false</send-server-header-enabled>
    <wap-enabled>false</wap-enabled>
    <accept-context-path-in-get-real-path>false</accept-context-path-in-get-real-path>
    </web-server>
    <listen-address></listen-address>
    <java-compiler>javac</java-compiler>
    <tunneling-enabled>false</tunneling-enabled>
    <tunneling-client-ping-secs>45</tunneling-client-ping-secs>
    <tunneling-client-timeout-secs>40</tunneling-client-timeout-secs>
    <server-start>
    <arguments>-Dhttp.proxyHost=[XXXXXXXX] -Dhttp.proxyPort=8080</arguments>
    <password-encrypted>[XXXXXXX]</password-encrypted>
    </server-start>
    <server-life-cycle-timeout-val>30</server-life-cycle-timeout-val>
    <startup-timeout>0</startup-timeout>
    <graceful-shutdown-timeout>30</graceful-shutdown-timeout>
    <ignore-sessions-during-shutdown>false</ignore-sessions-during-shutdown>
    <client-cert-proxy-enabled>false</client-cert-proxy-enabled>
    </server>
    <embedded-ldap>
    <name>wls_starter</name>
    <credential-encrypted>[XXXXXXXXXX]</credential-encrypted>
    </embedded-ldap>
    <configuration-version>10.3.2.0</configuration-version>
    <app-deployment>
    <name>[XXXXXXXXXX]</name>
    <target>AdminServer</target>
    <module-type>ear</module-type>
    <source-path>[XXXXXXXXXX]</source-path>
    <security-dd-model>DDOnly</security-dd-model>
    </app-deployment>
    <app-deployment>
    <name>[XXXXXXXXXX]</name>
    <target>AdminServer</target>
    <module-type>ear</module-type>
    <source-path>[XXXXXXXXXX]</source-path>
    <security-dd-model>DDOnly</security-dd-model>
    </app-deployment>
    <app-deployment>
    <name>[XXXXXXXXXX]</name>
    <target>AdminServer</target>
    <module-type>ear</module-type>
    <source-path>[XXXXXXXXXX]</source-path>
    <security-dd-model>DDOnly</security-dd-model>
    </app-deployment>
    <app-deployment>
    <name>[XXXXXXXXXX]</name>
    <target>AdminServer</target>
    <module-type>ear</module-type>
    <source-path>[XXXXXXXXXX]</source-path>
    <security-dd-model>DDOnly</security-dd-model>
    </app-deployment>
    <machine>
    <name>[XXXXXXXXXX]</name>
    </machine>
    <jms-server>
    <name>WseeJmsServer</name>
    <target>AdminServer</target>
    <persistent-store>WseeFileStore</persistent-store>
    </jms-server>
    <jms-server>
    <name>[XXXXXXXXXX]</name>
    <target>AdminServer</target>
    <persistent-store>WseeFileStore</persistent-store>
    </jms-server>
    <self-tuning>
    <work-manager>
    <name>weblogic.wsee.mdb.DispatchPolicy</name>
    <target>AdminServer</target>
    </work-manager>
    </self-tuning>
    <file-store>
    <name>WseeFileStore</name>
    <directory>WseeFileStore</directory>
    <target>AdminServer</target>
    </file-store>
    <jms-system-resource>
    <name>WseeJmsModule</name>
    <target>AdminServer</target>
    <sub-deployment>
    <name>BEA_JMS_MODULE_SUBDEPLOYMENT_WSEEJMSServer</name>
    <target>WseeJmsServer</target>
    </sub-deployment>
    <descriptor-file-name>jms/wseejmsmodule-jms.xml</descriptor-file-name>
    </jms-system-resource>
    <jms-system-resource>
    <name>[XXXXXXXXXX]</name>
    <target>AdminServer</target>
    <sub-deployment>
    <name>[XXXXXXXXXX]</name>
    <target>[XXXXXXXXXX]</target>
    </sub-deployment>
    <descriptor-file-name>[XXXXXXXXXX]</descriptor-file-name>
    </jms-system-resource>
    <admin-server-name>AdminServer</admin-server-name>
    <jdbc-system-resource>
    <name>[XXXXXXXXXX]</name>
    <target>AdminServer</target>
    <descriptor-file-name>[XXXXXXXXXX]</descriptor-file-name>
    </jdbc-system-resource>
    <saf-agent>
    <name>ReliableWseeSAFAgent</name>
    <target>AdminServer</target>
    <store>WseeFileStore</store>
    </saf-agent>
    </domain>

  • Setting the Administrator password on a MDT Server Task Sequence

    I've created a SCCM 2012 R2 CU3 MDT 2013 task sequence using the Server Task Sequence template to deploy Windows Server 2012 R2. I'm not doing a capture but just using the .wim file from the source DVD. The problem I'm having is setting the local admin
    password in Apply Windows Settings. It's not taking the password that I've assigned it. I'm not sure how many others have created a Server Task Sequence or not but I'd be interested to know how to get around this problem.

    Sorry, in Apply Windows Settings I've selected "Enable the account and specify the local administrator password" and entered the local password there. When the system is imaged and I try to log in locally it gives the the error "The user name
    or password is incorrect. Try again." error.
    I have checked that the local administrator account is enabled so I know it's not that and I've tried multiple times. I even took one of our client task sequences that I know works, made a copy of it, and added the Server 2012 R2 install to it and get the
    same result.

  • How to add an object in JNDI when a server starts?

    I have an integration app. The app contains EJB project. The project contains EJB which reads data from LDAP.
    My first version of EJB contains the following code:
    Hashtable env = new Hashtable();
    env.put(Context.INITIAL_CONTEXT_FACTORY,"com.sun.jndi.ldap.LdapCtxFactory");
    env.put(Context.PROVIDER_URL, strProvider);
    env.put(Context.SECURITY_AUTHENTICATION, strAuth); env.put(Context.SECURITY_PRINCIPAL,strPrincipal); env.put(Context.SECURITY_CREDENTIALS,strCredentials);
    DirContext dirCtx = new InitialDirContext(env); // exception
    All connection properties are hardcoded and it is not a good practice.
    Also I can put those properties into deployment descriptor. But I am going to have some EJBs and each EJB has to have those properties into descriptors. It is not useful.
    My idea: I would like to have whatever object which is called automatically when a server starts; this object creates InitialDirContext and put the context into JNDI. All EJBs lookup the context by a name. But I don't know how to do that.
    And another question: how to change connection properties dynamically? My idea is putting the properties in XML Cache. And my object (which creates InitialDirContext) reads the properties from XML Cache. Can I handle a message that my properties in XML Cache have been changed and in this cases my object reads new properties and calls rebind() to update InitialDirContext?
    Thanks,
    Ivan

    To bind an object into the JNDI tree check the documentation here:
    http://e-docs.bea.com/wls/docs81/jndi/jndi.html#475702
    If this is to be used by all your applications that you deploy on the server check out the startup/shutdown class documentation here:
    http://edocs.bea.com/wls/docs81/ConsoleHelp/startup_shutdown.html
    Cheers
    IV

  • Weird issue with 10.0.1.0 on Linux - 5 mins delay in server start-up!!

    Hi ...
    I am having some weird (and unique??) issue with WLS 10.0.1.0 on RHEL servers.
    WLS installation on our DEV env works perfectly fine and the server starts up in 15-20 secs. for each of the two domains created on it.
    But the QA server is another story all together ! ... It has the same OS and version, WSL installation and version, hardware configs, processes running at the time of start-up etc. But the problem is that when I try to start the server on the only domain on that server, it always gets delayed by 5-6 mins in between the startup at this point -
    +&lt;Feb 17, 2009 *7:04:50 *PM UTC&gt; &lt;Info&gt; &lt;Management&gt; &lt;BEA-141107&gt; &lt;Version: WebLogic Server 10.0 MP1 Thu Oct 18 20:17:44 EDT 2007 1005184 &gt;+
    +&lt;Feb 17, 2009 *7:10:56 *PM UTC&gt; &lt;Info&gt; &lt;WebLogicServer&gt; &lt;BEA-000215&gt; &lt;Loaded License : /opt/bea/license.bea&gt;+
    (Notice the 6 mins delay in the timestamps)
    There are no logs getting generated within this time and it seems like the WLS 10.0.1.0 just spaces out
    After the delay it starts up pretty fast .. within 10-15 secs!!
    Anybody here seen such behavior with WLS
    thanks,
    --Shailesh Welankar                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   

    I recommend taking some thread dumps during this delay and contacting support to get some advice.
    You can take the thread dumps by kill -3, JRockit Mission Control, etc.

  • Help-Cubes are not getting started when Analytical server started in 11.1.1

    Installed Oracle Essbase Analytical server along with Shared Services, Provider Services and Integration Services thru EPM v11.1.1.3. Shared services and provider services on Windows 2003 and Essbase Analytical Services and Integration Services on UNIX/AIX. All the components got configured successfully. Copied the essbase.sec from the server which has previous version (v11.1.1.1.0) of Essbase. We have been encountering couple of problems. The first one is the applications(cubes) didn't start when the analytical server started. The second one is when trying to start using MAXL script, the applications took long time (more than 30 minutes) to start.
    Any suggestions that you may have in resolving this are appreciated. Thanks,

    In the application properties, is the box 'Start application when Essbase server starts' checked? If not, that's why they didn't automatically start. Also, once you started them manually, does it still take 30 minutes to start? Or is shutdown and startup faster now?
    Sabrina

  • SSRS Log shows Reporting web server started, was it closed before?

    Hi there:
        During the weekend, one of our sql jobs that calls  a RSS script to create a SSRS PDF report failed
        The job error says
        " Could not connect to server: http://XXXXXXXXX/ReportServer/ReportService2005.asmx "
        The command inside the job is below
        RS.EXE -i "\\XXXXXXXXX\Secure\Business Intelligence\SSRS\Scripts\publishReportSnapshot(366).rss" -s http://XXXXXXXXX/ReportServer -l 300
     (XXXXXXX refers to the server name which is withheld here)
     I've checked the SSRS log file and below is what I've found
    Please see the entries below:
    library!WindowsService_4!26e8!09/24/2011-12:18:07:: i INFO: Call to CleanBatch() ends
    library!WindowsService_4!15b8!09/24/2011-12:28:07:: i INFO: Call to CleanBatch()
    library!WindowsService_4!15b8!09/24/2011-12:28:07:: i INFO: Cleaned 0 batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0 chunks, 0 running jobs, 0 persisted streams, 0 segments, 0 segment mappings.
    library!WindowsService_4!15b8!09/24/2011-12:28:07:: i INFO: Call to CleanBatch() ends 
    appdomainmanager!DefaultDomain!2430!09/24/2011-12:36:20:: i INFO: Appdomain:15 ReportServer_MSSQLSERVER_0-9-129613665780462239 started.
    appdomainmanager!ReportServer_0-9!2430!09/24/2011-12:36:21:: i INFO: RS authentication mode is 4; effective ASP.NET authentication mode is Windows. vdir=/ReportServer.
    appdomainmanager!DefaultDomain!2430!09/24/2011-12:36:21:: i INFO: Appdomain:15 ReportServer_MSSQLSERVER_0-9-129613665780462239 initialized (#5).
    webserver!ReportServer_0-9!2430!09/24/2011-12:37:31:: i INFO: Reporting Web Server started
    resourceutilities!ReportServer_0-9!2430!09/24/2011-12:37:31:: i INFO: Reporting Services starting SKU: Enterprise
    resourceutilities!ReportServer_0-9!2430!09/24/2011-12:37:31:: i INFO: Evaluation copy: 0 days left
    resourceutilities!ReportServer_0-9!2430!09/24/2011-12:37:31:: i INFO: Running on 8 physical processors, 8 logical processors
    runningjobs!ReportServer_0-9!2430!09/24/2011-12:37:31:: i INFO: Running Requests Scavenger timer enabled: Next Event: 60 seconds.  Cycle: 60 seconds
    runningjobs!ReportServer_0-9!2430!09/24/2011-12:37:31:: i INFO: Running Requests DB timer enabled: Next Event: 60 seconds.  Cycle: 60 seconds
    My question is as follows:
    1. Why does it have the entry saying Reporting web server started? Does it mean it was closed before?
    2.Why does it have the entry saying Evaluation copy: 0 days left
    thanks
     Hui--Currently using Reporting Service 2000; Visual Studio .NET 2003; Visual Source Safe SSIS 2008 SSAS 2008, SVN --

    Hi cat_a,
    Please check the “SecureConnectionLevel” property value in the rsreportserver.config file. (By default, the rsreportserver.config file store in the following path:
    <drive:> Program Files\Microsoft SQL Server\ MSRS10.MSSQLSERVER\Reporting Services\ReportServer\rsreportserver.config)
    When the value is set, the SecureConnectionLevel element in the report server configuration file is changed, and the URLRoot element in the configuration file is set to use "https://" if the specified Level is greater than or equal to 1, or "http://" if
    the specified Level is 0.
    For more information, please refer to the article below:
    http://msdn.microsoft.com/en-us/library/ms152810.aspx
    For the Report Server is Evaluation, there is a thread about this topic, please see:
    http://social.msdn.microsoft.com/Forums/en/sqlreportingservices/thread/02aa072e-905e-4e5a-b612-98df146fe3b1
    Thanks,
    Bin Long
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

  • Application Server Starting and then Stopping

    For some reason my NSP server is starting with MMC, but then after about a minute it stops again. Please see the log files below. It seems to be a database problem but I don't know how to fix it...
    dev_w0
    trc file: "dev_w0", trc level: 1, release: "700"
    *  ACTIVE TRACE LEVEL           1
    *  ACTIVE TRACE COMPONENTS      all, MJ

    B Fri Jun 20 23:50:24 2008
    B  create_con (con_name=R/3)
    B  Loading DB library 'C:\usr\sap\NSP\DVEBMGS00\exe\dbsdbslib.dll' ...
    B  Library 'C:\usr\sap\NSP\DVEBMGS00\exe\dbsdbslib.dll' loaded
    B  Version of 'C:\usr\sap\NSP\DVEBMGS00\exe\dbsdbslib.dll' is "700.08", patchlevel (0.19)
    B  New connection 0 created
    M sysno      00
    M sid        NSP
    M systemid   560 (PC with Windows NT)
    M relno      7000
    M patchlevel 0
    M patchno    23
    M intno      20050900
    M make:      multithreaded, ASCII
    M pid        4928
    M
    M  kernel runs with dp version 202(ext=109) (@(#) DPLIB-INT-VERSION-202)
    M  length of sys_adm_ext is 360 bytes
    M  ***LOG Q0Q=> tskh_init, WPStart (Workproc 0 4928) [dpxxdisp.c   1288]
    I  MtxInit: 30000 0 0
    M  DpSysAdmExtCreate: ABAP is active
    M  DpSysAdmExtCreate: VMC (JAVA VM in WP) is not active
    M  DpShMCreate: sizeof(wp_adm)          5280     (880)
    M  DpShMCreate: sizeof(tm_adm)          3351072     (16672)
    M  DpShMCreate: sizeof(wp_ca_adm)          1200     (60)
    M  DpShMCreate: sizeof(appc_ca_adm)     1200     (60)
    M  DpCommTableSize: max/headSize/ftSize/tableSize=500/8/528040/528048
    M  DpShMCreate: sizeof(comm_adm)          528048     (1048)
    M  DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0
    M  DpShMCreate: sizeof(file_adm)          0     (72)
    M  DpShMCreate: sizeof(vmc_adm)          0     (1076)
    M  DpShMCreate: sizeof(wall_adm)          (22440/34344/56/100)
    M  DpShMCreate: sizeof(gw_adm)     48
    M  DpShMCreate: SHM_DP_ADM_KEY          (addr: 04C80040, size: 3950264)
    M  DpShMCreate: allocated sys_adm at 04C80040
    M  DpShMCreate: allocated wp_adm at 04C81978
    M  DpShMCreate: allocated tm_adm_list at 04C82E18
    M  DpShMCreate: allocated tm_adm at 04C82E48
    M  DpShMCreate: allocated wp_ca_adm at 04FB5068
    M  DpShMCreate: allocated appc_ca_adm at 04FB5518
    M  DpShMCreate: allocated comm_adm at 04FB59C8
    M  DpShMCreate: system runs without file table
    M  DpShMCreate: allocated vmc_adm_list at 05036878
    M  DpShMCreate: allocated gw_adm at 050368B8
    M  DpShMCreate: system runs without vmc_adm
    M  DpShMCreate: allocated ca_info at 050368E8
    M  DpShMCreate: allocated wall_adm at 050368F0
    Y  *** ERROR => ztta/diag_area is 64000. [sapinit.c    325]
    Y  *** ERROR => ztta/diag_area adjusted to 128000 (minimum value). [sapinit.c    327]
    Y  *** ERROR => ztta/cua_area is 90000. [sapinit.c    963]
    Y  *** ERROR => ztta/cua_area adjusted to 250000. [sapinit.c    967]
    X  EmInit: MmSetImplementation( 2 ).
    X  MM diagnostic options set: 0
    X  <ES> client 0 initializing ....
    X  Using implementation flat
    M  <EsNT> Memory Reset disabled as NT default
    X  ES initialized.

    M Fri Jun 20 23:50:25 2008
    M  ThInit: running on host PackardBell
    M  calling db_connect ...

    C  DBSDBSLIB : version 700.08, patch 0.019 (Make PL 0.23)
    C  MAXDB shared library (dbsdbslib) patchlevels (last 10)
    C    (0.019) UPDSTAT optimized (note 870327)
    C    (0.010) MaxDB DBSL patch collection 1 2005 (note 850830)
    C    (0.009) New stream compression available with LVC 7.6.0 b12 (note 835809)
    C    (0.008) Support of SDBUPDEXCL (note 847616)
    C    (0.005) Switch stream compression on/off (note 835809)
    C    (0.005) ITAB stream handling optimized (note 835809)


    C  Loading SQLDBC client runtime ...
    C  SQLDBC SDK Version : SQLDBC.H  7.6.0    BUILD 002-121-083-965
    C  SQLDBC Library Version : libSQLDBC 7.6.0    BUILD 018-123-113-357
    C  SQLDBC client runtime is MaxDB 7.6.0.018 CL 113357
    C  INFO : SQLOPT= -I 0 -t 0
    C  Try to connect (DEFAULT) on connection 0 ...
    C  *** ERROR => Connect to database failed, rc = -10757 (XUSER error (the USERKEY is unknown))
    [dbsdbsql.cpp 98]
    C  Try to connect (SQLOPT) on connection 0 ...
    C  *** ERROR => Connect to database failed, rc = -10709 (Connection failed (RTE:Database name is missing))
    [dbsdbsql.cpp 118]
    B  ***LOG BV3=> severe db error -10709    ; work process is stopped [dbsh#1 @ 1195] [dbsh    1195 ]
    B  ***LOG BY2=> sql error -10709 performing CON [dblink#3 @ 431] [dblink  0431 ]
    B  ***LOG BY0=> Connection failed (RTE:Database name is missing) [dblink#3 @ 431] [dblink  0431 ]
    M  ***LOG R19=> ThInit, db_connect ( DB-Connect 000256) [thxxhead.c   1391]
    M  in_ThErrHandle: 1
    M  *** ERROR => ThInit: db_connect (step 1, th_errno 13, action 3, level 1) [thxxhead.c   9995]

    M  Info for wp 0

    M    stat = 4
    M    reqtype = 1
    M    act_reqtype = -1
    M    rq_info = 0
    M    tid = -1
    M    mode = 255
    M    len = -1
    M    rq_id = 65535
    M    rq_source = 255
    M    last_tid = 0
    M    last_mode = 0
    M    semaphore = 0
    M    act_cs_count = 0
    M    control_flag = 0
    M    int_checked_resource(RFC) = 0
    M    ext_checked_resource(RFC) = 0
    M    int_checked_resource(HTTP) = 0
    M    ext_checked_resource(HTTP) = 0
    M    report = >                                        <
    M    action = 0
    M    tab_name = >                              <
    M    vm = V-1

    M  *****************************************************************************
    M  *
    M  *  LOCATION    SAP-Server PackardBell_NSP_00 on host PackardBell (wp 0)
    M  *  ERROR       ThInit: db_connect
    M  *
    M  *  TIME        Fri Jun 20 23:50:25 2008
    M  *  RELEASE     700
    M  *  COMPONENT   Taskhandler
    M  *  VERSION     1
    M  *  RC          13
    M  *  MODULE      thxxhead.c
    M  *  LINE        10180
    M  *  COUNTER     1
    M  *
    M  *****************************************************************************

    M  PfStatDisconnect: disconnect statistics
    M  Entering TH_CALLHOOKS
    M  ThCallHooks: call hook >ThrSaveSPAFields< for event BEFORE_DUMP
    M  *** ERROR => ThrSaveSPAFields: no valid thr_wpadm [thxxrun1.c   720]
    M  *** ERROR => ThCallHooks: event handler ThrSaveSPAFields for event BEFORE_DUMP failed [thxxtool3.c  260]
    M  Entering ThSetStatError
    M  ThIErrHandle: do not call ThrCoreInfo (no_core_info=0, in_dynp_env=0)
    M  Entering ThReadDetachMode
    M  call ThrShutDown (1)...
    M  ***LOG Q02=> wp_halt, WPStop (Workproc 0 4928) [dpnttool.c   327]

    Ok I eventually figured it out... The SAP Application Server starts the database using the XUSER authentication - For some reason my system lost all settings for this.
    In order to recreate, I had to use the command prompt and use the XUSER command.
    Firstly "XUSER LIST" lists all user keys - I had none.
    I then needed to set the default XUSER:
    XUSER -d NSP -u SAPNSP,<password>
    <password> is the password for the user specified
    Then I created the "c" key:
    XUSER -d NSP -U c -u SAPNSP,<password>
    The reason I set up the "c" XUSER is because I noticed that in "\usr\sap\NSP\DVEBMGS00\exe\" there is a batch file used to start the DB - "strdbs.cmd". Inside this file it uses "c" as the user key in order to set the state of the DB.
    After all of that it worked again...

  • 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

Maybe you are looking for