ZENworks Agent Service stops after deploying 10.3.3 agent.

Hi,
Yesterday i patched our three ZCM-servers (Sles 11) with 10.3.3. I then deployed the 10.3.3 agent to some computers in the IT-department. ZCC shows that the deployment were successful. The problem is that you can not log on to the ZONE from many of these computers. The Novell ZENworks Agent Service stops. I get the following in the Application Windows Log on a Windows 7 64-bit client:
Faulting application name: ZenworksWindowsService.exe, version: 10.3.3.3582, time stamp: 0x4d654308
Faulting module name: ntdll.dll, version: 6.1.7600.16695, time stamp: 0x4cc7b325
Exception code: 0xc0000374
Fault offset: 0x00000000000c6ab2
Faulting process id: 0x3f8
Faulting application start time: 0x01cbe3a9dd16f0fc
Faulting application path: C:\Program Files (x86)\Novell\ZENworks\bin\ZenworksWindowsService.e xe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 019eaf5e-4f9e-11e0-986f-005056b925a1
Can anyone help me with this problem?
John Hallberg
Jonkoping University

I would try removing all versions of .NET and then reinstalling the
latest 3.5 SP1 version to see if that helps, since the Agent relies on .NET
If that does not help, I would recommend getting an SR created so the
dump could be analyzed.
On 3/16/2011 5:06 AM, hajo68 wrote:
>
> Hi,
>
> Yesterday i patched our three ZCM-servers (Sles 11) with 10.3.3. I then
> deployed the 10.3.3 agent to some computers in the IT-department. ZCC
> shows that the deployment were successful. The problem is that you can
> not log on to the ZONE from many of these computers. The Novell ZENworks
> Agent Service stops. I get the following in the Application Windows Log
> on a Windows 7 64-bit client:
>
>
> Faulting application name: ZenworksWindowsService.exe, version:
> 10.3.3.3582, time stamp: 0x4d654308
> Faulting module name: ntdll.dll, version: 6.1.7600.16695, time stamp:
> 0x4cc7b325
> Exception code: 0xc0000374
> Fault offset: 0x00000000000c6ab2
> Faulting process id: 0x3f8
> Faulting application start time: 0x01cbe3a9dd16f0fc
> Faulting application path: C:\Program Files
> (x86)\Novell\ZENworks\bin\ZenworksWindowsService.e xe
> Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
> Report Id: 019eaf5e-4f9e-11e0-986f-005056b925a1
>
> Can anyone help me with this problem?
>
> John Hallberg
> Jonkoping University
>
>
Craig Wilson - MCNE, MCSE, CCNA
Novell Knowledge Partner
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.

Similar Messages

  • SAPCCM4X.03 Windows Service stops after 3 sec.

    Hi!
    I would like to set up the SAPCCM4X agent on the satellite system.
    The installation with the commando >sapccm4x -R pf=... endes without any errors.
    The problem is that the appropriate SAPCCM4X.03 Windows Service stops after 3 sec.
    The output on the CMD console is:
    INFO: trying to register service SAPCCM4X.03 at Windows Service Control Manager
    starttype of service:             manual/[auto] :
    DomainName\UserName  or [<LocalSystem account>] :
    INFO: Agent is running (no actual pid, but actual shared memory!)
    WARNING: Service SAPCCM4X.03 already stopped. But agent is running!
    WARNING: The following service is registered but could not be started
    SAPCCM4X.03  
    (command ["E:\usr\sap\SC3\SYS\exe\run\sapccm4x.exe" -Service
    pf=E:\usr\sap\SC3\SYS\profile\SC3_DVEBMGS03_VMSAP01]   user <LocalSystem account>)
    INFO: Updated config file E:\usr\sap\SC3\DVEBMGS03\log\sapccm4x\csmconf.
    EXITING with code 0
    How can I solve this problem?
    Thank you
    Ju00FCrgen

    Hello Jürgen,
    WARNING: Service SAPCCM4X.03 already stopped. But agent is running!
    you could try to clean up the part of the shared memory used by the agent:
    sapccm4x pf=<instance profile> -initshm
    Maybe the agent starts afterwards.
    Regards, Michael

  • IMAP + POP service stops after startup. Cannot configure params in shell

    Hello,
    Just bought a MacMini, with 10.6.4 server. However, I cannot make POP nor IMAP services to work. They stop after startup. SMTP works fine though.
    How do I troubleshoot? The graphical 'Mail Configure Service...' does not make the IMAP service start.
    I cannot change the mail parameters via command line.
    For example:
    $ sudo serveradmin set mail:imap:enable_imap = no /yes is ignored.

    By manually reseting the variables in the file, mail started with IMAP and POP running,
    I trust this is a bug in the serveradmin .app
    Here is the garbled file:
    ----sslcertfile variable could not be reset by serveradmin, it apparently appended data instead of overwriting:
    # Note: This key is managed by Server Admin. See above before making changes
    sslcertfile = /etc/certificates/MacMini.sip.com.gr.8017D0CBEBF8CC56CF776F2E03D8E3849C9F743A.c ert.pem (Email).D8106694C6517EA5D450AC90C2D2B86624A82000.cert.pem SSL Server.EBBA9E02804AECB53A9C44F983024BEDE1397CA8.cert.pem Ltd (SSL client).7BA20201B838A758AA227335E7FD87EB80F53DEC.cert.pem (Email).D8106694C6517EA5D450AC90C2D2B86624A82000.cert.pem (Email).D8106694C6517EA5D450AC90C2D2B86624A82000.cert.pem (Email).D8106694C6517EA5D450AC90C2D2B86624A82000.cert.pem (Email).D8106694C6517EA5D450AC90C2D2B86624A82000.cert.pem Ltd (SSL client).7BA20201B838A758AA227335E7FD87EB80F53DEC.cert.pem Ltd (SSL client).7BA20201B838A758AA227335E7FD87EB80F53DEC.cert.pem (Email).D8106694C6517EA5D450AC90C2D2B86624A82000.cert.pem (Email).D8106694C6517EA5D450AC90C2D2B86624A82000.cert.pem Ltd (SSL client).7BA20201B838A758AA227335E7FD87EB80F53DEC.cert.pem (Email).D8106694C6517EA5D450AC90C2D2B86624A82000.cert.pem (Email).D8106694C6517EA5D450AC90C2D2B86624A82000.cert.pem (Email).D8106694C6517EA5D450AC90C2D2B86624A82000.cert.pem SSL Server.EBBA9E02804AECB53A9C44F983024BEDE1397CA8.cert.pem Ltd (SSL client).7BA20201B838A758AA227335E7FD87EB80F53DEC.cert.pem (Email).D8106694C6517EA5D450AC90C2D2B86624A82000.cert.pem (Email).D8106694C6517EA5D450AC90C2D2B86624A82000.cert.pem (Email).D8106694C6517EA5D450AC90C2D2B86624A82000.cert.pem (Email).D8106694C6517EA5D450AC90C2D2B86624A82000.cert.pem (Email).D8106694C6517EA5D450AC90C2D2B86624A82000.cert.pem SSL Server.EBBA9E02804AECB53A9C44F983024BEDE1397CA8.cert.pem (Email).D8106694C6517EA5D450AC90C2D2B86624A82000.cert.pem Ltd.1949E49930EF79AE0C0B92EFDA9699918DDC5AA8.cert.pem Ltd.1949E49930EF79AE0C0B92EFDA9699918DDC5AA8.cert.pem Ltd.1949E49930EF79AE0C0B92EFDA9699918DDC5AA8.cert.pem SIP Ltd.68A893BB34CC5B16AEBA36DFFE4A8B5397F9FB56.cert.pem Ltd.1949E49930EF79AE0C0B92EFDA9699918DDC5AA8.cert.pem Ltd.1949E49930EF79AE0C0B92EFDA9699918DDC5AA8.cert.pem SIP Ltd.68A893BB34CC5B16AEBA36DFFE4A8B5397F9FB56.cert.pem Ltd.1949E49930EF79AE0C0B92EFDA9699918DDC5AA8.cert.pem Ltd.1949E49930EF79AE0C0B92EFDA9699918DDC5AA8.cert.pem SIP Ltd.68A893BB34CC5B16AEBA36DFFE4A8B5397F9FB56.cert.pem SIP Ltd.68A893BB34CC5B16AEBA36DFFE4A8B5397F9FB56.cert.pem SIP Ltd.68A893BB34CC5B16AEBA36DFFE4A8B5397F9FB56.cert.pem Ltd.1949E49930EF79AE0C0B92EFDA9699918DDC5AA8.cert.pem Ltd.1949E49930EF79AE0C0B92EFDA9699918DDC5AA8.cert.pem Ltd.1949E49930EF79AE0C0B92EFDA9699918DDC5AA8.cert.pem Ltd.1949E49930EF79AE0C0B92EFDA9699918DDC5AA8.cert.pem Ltd.1949E49930EF79AE0C0B92EFDA9699918DDC5AA8.cert.pem Ltd.1949E49930EF79AE0C0B92EFDA9699918DDC5AA8.cert.pem SIP Ltd.68A893BB34CC5B16AEBA36DFFE4A8B5397F9FB56.cert.pem Ltd.1949E49930EF79AE0C0B92EFDA9699918DDC5AA8.cert.pem Ltd.1949E49930EF79AE0C0B92EFDA9699918DDC5AA8.cert.pem Ltd.1949E49930EF79AE0C0B92EFDA9699918DDC5AA8.cert.pem SIP Ltd.68A893BB34CC5B16AEBA36DFFE4A8B5397F9FB56.cert.pem SIP Ltd.68A893BB34CC5B16AEBA36DFFE4A8B5397F9FB56.cert.pem SIP Ltd.68A893BB34CC5B16AEBA36DFFE4A8B5397F9FB56.cert.pem SIP Ltd.68A893BB34CC5B16AEBA36DFFE4A8B5397F9FB56.cert.pem Ltd.1949E49930EF79AE0C0B92EFDA9699918DDC5AA8.cert.pem Ltd.1949E49930EF79AE0C0B92EFDA9699918DDC5AA8.cert.pem
    # Note: This key is managed by Server Admin. See above before making changes
    sslkeyfile = /etc/certificates/MacMini.sip.com.gr.8017D0CBEBF8CC56CF776F2E03D8E3849C9F743A.k ey.pem (Email).D8106694C6517EA5D450AC90C2D2B86624A82000.key.pem SSL Server.EBBA9E02804AECB53A9C44F983024BEDE1397CA8.key.pem Ltd (SSL client).7BA20201B838A758AA227335E7FD87EB80F53DEC.key.pem (Email).D8106694C6517EA5D450AC90C2D2B86624A82000.key.pem (Email).D8106694C6517EA5D450AC90C2D2B86624A82000.key.pem (Email).D8106694C6517EA5D450AC90C2D2B86624A82000.key.pem (Email).D8106694C6517EA5D450AC90C2D2B86624A82000.key.pem Ltd (SSL client).7BA20201B838A758AA227335E7FD87EB80F53DEC.key.pem (Email).D8106694C6517EA5D450AC90C2D2B86624A82000.key.pem (Email).D8106694C6517EA5D450AC90C2D2B86624A82000.key.pem (Email).D8106694C6517EA5D450AC90C2D2B86624A82000.key.pem SSL Server.EBBA9E02804AECB53A9C44F983024BEDE1397CA8.key.pem Ltd (SSL client).7BA20201B838A758AA227335E7FD87EB80F53DEC.key.pem (Email).D8106694C6517EA5D450AC90C2D2B86624A82000.key.pem (Email).D8106694C6517EA5D450AC90C2D2B86624A82000.key.pem (Email).D8106694C6517EA5D450AC90C2D2B86624A82000.key.pem (Email).D8106694C6517EA5D450AC90C2D2B86624A82000.key.pem (Email).D8106694C6517EA5D450AC90C2D2B86624A82000.key.pem SSL Server.EBBA9E02804AECB53A9C44F983024BEDE1397CA8.key.pem (Email).D8106694C6517EA5D450AC90C2D2B86624A82000.key.pem Ltd.1949E49930EF79AE0C0B92EFDA9699918DDC5AA8.key.pem Ltd.1949E49930EF79AE0C0B92EFDA9699918DDC5AA8.key.pem Ltd.1949E49930EF79AE0C0B92EFDA9699918DDC5AA8.key.pem SIP Ltd.68A893BB34CC5B16AEBA36DFFE4A8B5397F9FB56.key.pem Ltd.1949E49930EF79AE0C0B92EFDA9699918DDC5AA8.key.pem Ltd.1949E49930EF79AE0C0B92EFDA9699918DDC5AA8.key.pem SIP Ltd.68A893BB34CC5B16AEBA36DFFE4A8B5397F9FB56.key.pem Ltd.1949E49930EF79AE0C0B92EFDA9699918DDC5AA8.key.pem Ltd.1949E49930EF79AE0C0B92EFDA9699918DDC5AA8.key.pem SIP Ltd.68A893BB34CC5B16AEBA36DFFE4A8B5397F9FB56.key.pem SIP Ltd.68A893BB34CC5B16AEBA36DFFE4A8B5397F9FB56.key.pem SIP Ltd.68A893BB34CC5B16AEBA36DFFE4A8B5397F9FB56.key.pem Ltd.1949E49930EF79AE0C0B92EFDA9699918DDC5AA8.key.pem Ltd.1949E49930EF79AE0C0B92EFDA9699918DDC5AA8.key.pem Ltd.1949E49930EF79AE0C0B92EFDA9699918DDC5AA8.key.pem Ltd.1949E49930EF79AE0C0B92EFDA9699918DDC5AA8.key.pem Ltd.1949E49930EF79AE0C0B92EFDA9699918DDC5AA8.key.pem Ltd.1949E49930EF79AE0C0B92EFDA9699918DDC5AA8.key.pem SIP Ltd.68A893BB34CC5B16AEBA36DFFE4A8B5397F9FB56.key.pem Ltd.1949E49930EF79AE0C0B92EFDA9699918DDC5AA8.key.pem Ltd.1949E49930EF79AE0C0B92EFDA9699918DDC5AA8.key.pem Ltd.1949E49930EF79AE0C0B92EFDA9699918DDC5AA8.key.pem SIP Ltd.68A893BB34CC5B16AEBA36DFFE4A8B5397F9FB56.key.pem SIP Ltd.68A893BB34CC5B16AEBA36DFFE4A8B5397F9FB56.key.pem SIP Ltd.68A893BB34CC5B16AEBA36DFFE4A8B5397F9FB56.key.pem SIP Ltd.68A893BB34CC5B16AEBA36DFFE4A8B5397F9FB56.key.pem Ltd.1949E49930EF79AE0C0B92EFDA9699918DDC5AA8.key.pem Ltd.1949E49930EF79AE0C0B92EFDA9699918DDC5AA8.key.pem
    # Note: This key is managed by Server Admin. See above before making changes
    sslcafile = /etc/certificates/MacMini.sip.com.gr.8017D0CBEBF8CC56CF776F2E03D8E3849C9F743A.c hain.pem (Email).D8106694C6517EA5D450AC90C2D2B86624A82000.chain.pem SSL Server.EBBA9E02804AECB53A9C44F983024BE.....

  • Active directory domain services stopped after removing routing and remote access role

    Hello everyone;;
    I am in deep trouble.. I did install routing and remote access and then  lost connection to the server remotely. Then I connected a monitor to the server and removed the role... then it asked me to restart the server . After logging back in I found
    all my active directory service has gone... I can see red cross on active directory domain services.. Also I am able to ping other pcs but other pcs cannot ping my server..
    However when I go into the active directory services, it shows all services are running except file replication service. I have tried to start that service but it give error 1053 error..
    My server in  between loses LAN connection... I dont know what is going on.. Please help!!!
    My  server is win 2008 R2 ser pack 1
    Only one DC....
    Has fixed ip, 
    no DNS server running..

    Hi,
    The File Replication Service Start Error 1053 error can be caused by damaged Windows system files. Corrupted system files entries can threaten the well-being of your computer. Many events can result in creating system file errors.
    Please refer to the articles below to troubleshoot the issue:
    File Replication Service Start Error 1053
    http://repairerrors.net/file-replication-service-start-error-1053.html
    Please Note: Since the website is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.
    Regards,
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Error after Deploying a new Entity Service

    After deploying an entity service and testing it via the testtool the following error occured. Do you have an idea about the reason for this strange behaviour?
    Thanks in advance.
    ERROR. Exception thrown in method create. The transaction is marked for rollback.: javax/jdo/InstanceCallbacks -
    Loader Info -
    ClassLoader name: [siemens.com/sm3kshtlog] Parent loader name: [Frame ClassLoader] References:   common:service:http;service:servlet_jsp   service:ejb   common:service:iiop;service:naming;service:p4;service:ts   service:jmsconnector   library:jsse   library:servlet   common:library:IAIKSecurity;library:activation;library:mail;library:tcsecssl   library:ejb20   library:j2eeca   library:jms   library:opensql   common:library:com.sap.security.api.sda;library:com.sap.security.core.sda;library:security.class;library:webservices_lib;service:adminadapter;service:basicadmin;service:com.sap.security.core.ume.service;service:configuration;service:connector;service:dbpool;service:deploy;service:jmx;service:jmx_notification;service:keystore;service:security;service:userstore   interface:resourcecontext_api   interface:webservices   interface:cross   interface:ejbserialization   sap.com/cafcore   library:cafmetamodellib   library:cafruntimeapilib   sap.com/cafruntimeear Resources:   C:\usr\sap\P7D\JC00\j2ee\cluster\server0\apps\siemens.com\sm3kshtlog\EJBContainer\clientjars\clientsiemens.comsm3kshtlogejbmodule.jar   C:\usr\sap\P7D\JC00\j2ee\cluster\server0\apps\siemens.com\sm3kshtlog\EJBContainer\applicationjars\siemens.comsm3kshtlogejbmodule.jar   C:\usr\sap\P7D\JC00\j2ee\cluster\server0\apps\siemens.com\sm3kshtlog\src.zip Loading model: {parent,references,local} -
    The error occurred while trying to load "com.siemens.sm3k.shtlog.besrv.sigdatsource.SigDatSourceJDO".:

    Hi Samir,
    you could be right...
    it could be, that our metadata are inconsistent, because we had before problems with the automatic code generation.
    What should we do, if we have such a inconsistency of our ejbmodule, dictionary and metadata model?
    is there a way to repair the project?
    Undeploy and Redeploy doesn't have an effect on this.
    We cannot start again, because we put in 10days of development?
    Thanks for any help.
    Greetings Jens

  • Data services stop working after updating to new OS version for Q10

    I am from Qatar, after i updated my device ( Q10 SNQ100-3 ) to new OS ( 10.2.1.537 ), the mobile data services stopped working, but it works everytime I connect to wifi. This is the same with Z10. Please need help.

    Hi and Welcome to the Community!
    With a strong carrier network signal (e.g., not merely WiFi), I suggest the following steps, in order, even if they seem redundant to what you have already tried (step 1 should result in a message coming to your BB...please wait for that before proceeding to the next step):
    1) Register HRT
    KB00510 How to register a BlackBerry smartphone with the wireless network
    Please wait for one "registration" message to arrive
    2) Reboot
    Pre-BB10 Devices ONLY. With power ON, remove the back cover and pull out the battery. Wait about a minute then replace the battery and cover. Power up and wait patiently through the long reboot -- ~5 minutes.
    BB10 Devices. Hold the top button down until the counter reaches zero. Wait for the device to be fully shut down (e.g., nothing at all displayed on the screen, no LED lights, etc.). Hold the top button until the red LED is lit. Wait through the full boot-up process. IF this fails, you can attempt the battery-pull method above, but it is normally NOT recommended unless nothing else works.
    See if things have returned to good operation. Like all computing devices, BB's suffer from memory leaks and such...with a hard reboot being the best cure.
    Hopefully that will get things going again for you! If not, then you should contact your mobile service provider for formal support.
    Good luck!
    Occam's Razor nearly always applies when troubleshooting technology issues!
    If anyone has been helpful to you, please show your appreciation by clicking the button inside of their post. Please click here and read, along with the threads to which it links, for helpful information to guide you as you proceed. I always recommend that you treat your BlackBerry like any other computing device, including using a regular backup schedule...click here for an article with instructions.
    Join our BBM Channels
    BSCF General Channel
    PIN: C0001B7B4   Display/Scan Bar Code
    Knowledge Base Updates
    PIN: C0005A9AA   Display/Scan Bar Code

  • Search Service stopped crawling content after previously working

    The search service stopped crawling contennt. This was working previously.  I tried to stop full crawl and restart.  The ULS logs reveals this error repeatedly. when filter on search errors.
    Microsoft.Ceres.ContentEngine.SubmitterComponent.ContentSubmissionDecorator : CreateSession() failed with unexpected exception System.ServiceModel.FaultException`1[System.String]: The creator of this fault did not specify a Reason. (Fault Detail is equal
    to Specified flow: Microsoft.CrawlerFlow could not be started. Unable to start a flow instance on any of the available nodes.).
    Before we dropped the index and or rebuilding the Search Service application has anyone else worked on a similar issue?
    Thank you.

    Hi PSCoan,
    From the error message, it seems that the service account running the SharePoint Search Host Controller and the SharePoint search server 15 is missing the following four local policies:
    SeAssignPrimaryTokenPrivilege (Replace a process-level token )
    SeImpersonatePrivilege (Impersonate a client after authentication)
    SeServiceLogonRight (Log on as a service)
    SeIncreaseQuotaPrivilege (Adjust memory quotas for a process)
    Please go to the Local Group Policy Editor to assign the policies to the service account.
    Click Start , type gpedit.msc in the
    Start Search box, and then press ENTER .
    Expand Local Computer Policy -> Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> User Rights Assignment.
    Right click “Replace a process-level token” -> Properties -> Add User or Group.
    Right click “Impersonate a client after authentication” -> Properties -> Add User or Group.
    Right click “Log on as a service” -> Properties -> Add User or Group.
    Right click “Adjust memory quotas for a process” -> Properties -> Add User or Group.
    Thanks,
    Victoria
    Forum Support
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Victoria Xia
    TechNet Community Support

  • Stop VM after deployment - SkipInstallVirtualizationGuestServices

    Hi Experts,
    I am deploying a Custom Linux VM using template.
    I have written a powershell script that will get the template and create a new VM from the template using "New-SCVirtualMachine".
    But, the VM is started after deployment. I already have the Linux Integration Services installed in my VM. So, I removed "-StartVM" and added "-SkipInstallVirtualizationGuestServices" to avoid guest services
    installation.
    But it is still started in the "Customize Virtual Machine" Process and Guestagent.iso is added to CD of my VM.
    Please help in avoiding the VM to start after deployment.
    Thanks in advance,
    Saleem

    Had you discovered this:
    http://www.ms4u.info/2012/06/create-linux-vm-template-in-vmm-2012.html
    and this as well:
    http://operatingquadrant.com/2013/01/15/creating-linux-vm-templates-with-system-center-2012-sp1-virtual-machine-manager/
    Note the version differences on SCVMM and thus the support for different actions.
    Brian Ehlert http://ITProctology.blogspot.com Learn. Apply. Repeat.

  • Deployment stops after reboot

    Hello,
    I have a task sequence deploying Windows 7 and some applications. Everything has worked fine, but now, the deployment stops after the reboot after the os install. My applications don't get installed. I have already created a completely new image and task
    sequence but it still doesn't work.
    Here is the end of the smsts.log file:
    <![LOG[!--------------------------------------------------------------------------------------------!]LOG]!><time="12:20:55.218+000" date="02-19-2015" component="TSManager" context="" type="1"
    thread="1532" file="instruction.cxx:2957">
    <![LOG[Expand a string: WinPEandFullOS]LOG]!><time="12:20:55.218+000" date="02-19-2015" component="TSManager" context="" type="0" thread="1532" file="executionenv.cxx:782">
    <![LOG[Executing command line: smsboot.exe /target:WinPE]LOG]!><time="12:20:55.234+000" date="02-19-2015" component="TSManager" context="" type="1" thread="1532" file="commandline.cpp:805">
    <![LOG[========================= [ smsboot.exe ] =========================]LOG]!><time="12:20:55.249+000" date="02-19-2015" component="Reboot" context="" type="1" thread="1156" file="rebootcomputer.cpp:184">
    <![LOG[Command line: '"smsboot.exe" /target:WinPE']LOG]!><time="12:20:55.249+000" date="02-19-2015" component="Reboot" context="" type="0" thread="1156" file="rebootcomputer.cpp:186">
    <![LOG[SMSTSRebootDelay=30]LOG]!><time="12:20:55.249+000" date="02-19-2015" component="Reboot" context="" type="1" thread="1156" file="rebootcomputer.cpp:122">
    <![LOG[SMSTSRebootMessage=Initiating system reboot]LOG]!><time="12:20:55.249+000" date="02-19-2015" component="Reboot" context="" type="1" thread="1156" file="rebootcomputer.cpp:122">
    <![LOG[SMSTSRebootRequested=WinPE]LOG]!><time="12:20:55.249+000" date="02-19-2015" component="Reboot" context="" type="1" thread="1156" file="rebootcomputer.cpp:122">
    <![LOG[Process completed with exit code 0]LOG]!><time="12:20:55.249+000" date="02-19-2015" component="TSManager" context="" type="1" thread="1532" file="commandline.cpp:1102">
    <![LOG[!--------------------------------------------------------------------------------------------!]LOG]!><time="12:20:55.249+000" date="02-19-2015" component="TSManager" context="" type="1" thread="1532"
    file="instruction.cxx:3010">
    <![LOG[Successfully complete the action (Restart computer) with the exit win32 code 0]LOG]!><time="12:20:55.249+000" date="02-19-2015" component="TSManager" context="" type="1" thread="1532"
    file="instruction.cxx:3036">
    <![LOG[Sending status message . . .]LOG]!><time="12:20:55.249+000" date="02-19-2015" component="TSManager" context="" type="1" thread="1532" file="utility.cxx:292">
    <![LOG[Executing in non SMS standalone mode. Ignoring send a task execution status message request]LOG]!><time="12:20:55.249+000" date="02-19-2015" component="TSManager" context="" type="1" thread="1532"
    file="utility.cxx:302">
    <![LOG[Set a global environment variable _SMSTSLastActionRetCode=0]LOG]!><time="12:20:55.249+000" date="02-19-2015" component="TSManager" context="" type="0" thread="1532" file="executionenv.cxx:668">
    <![LOG[Set a global environment variable _SMSTSLastActionSucceeded=true]LOG]!><time="12:20:55.249+000" date="02-19-2015" component="TSManager" context="" type="0" thread="1532" file="executionenv.cxx:668">
    <![LOG[Expand a string: %_SMSTSMDataPath%\Logs]LOG]!><time="12:20:55.249+000" date="02-19-2015" component="TSManager" context="" type="0" thread="1532" file="executionenv.cxx:782">
    <![LOG[Deleting file without retry]LOG]!><time="12:20:55.249+000" date="02-19-2015" component="TSManager" context="" type="1" thread="1532" file="ccmfile.cpp:1015">
    Thank you.

    Most likely cause is that the image you are deploying was not syspreped correctly.
    GO back to your image and check the c:\windows\system32\sysprep\panther logs and *VERIFY* that sysprep completed successfully.
    Then try deploying the image again to a real machine and verify that the Specialize and OOBE phases are executed correctly in the c:\windows\panther logs.
    IF you are still having problems, please upload your panther logs and BDD.log to a public site like OneDrive and share the link.
    How to find the right MDT log files (bdd.log/smsts.log) to debug
    problems.
    How to debug problems in Windows Setup (Panther)
    Keith Garner - Principal Consultant [owner] -
    http://DeploymentLive.com

  • Error after deploying the application in PI java system

    Hi all,
    I have created a test web dynpro java application and deployed in PI7.1 java engine. Using the JCO's maintained i hav connected to ECC7.1 system and created a model to call a bapi. After deploying and running the application, I got the following error. Please let me know the solution
    Regards
    Sagar
        500   Internal Server Error  SAP NetWeaver Application Server/Java AS 
    The initial exception that caused the request to fail, was:
    java.lang.NullPointerException
        at com.sap.conn.jco.rt.DefaultDestinationManager.checkProperties(DefaultDestinationManager.java:405)
        at com.sap.conn.jco.rt.DefaultDestinationManager.update(DefaultDestinationManager.java:142)
        at com.sap.conn.jco.rt.DefaultDestinationManager.searchDestination(DefaultDestinationManager.java:292)
        at com.sap.conn.jco.rt.DefaultDestinationManager.getDestinationInstance(DefaultDestinationManager.java:90)
        at com.sap.conn.jco.JCoDestinationManager.getDestination(JCoDestinationManager.java:61)
        ... 82 more
    See full exception chain for details.
    Failed to process request. Please contact your system administrator.
    While processing the current request, an exception occured which could not be handled by the application or the framework.
    If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
    For further information about the Web Dynpro error page, error analysis and a description of well-known error situations, see SAP note 1113811.
    System Environment
    Client
    Web Dynpro Client Type HTML Client
    User agent Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; GTB6.3)
    Client Type msie6
    Client Type Profile ie6
    ActiveX enabled
    Java Applets enabled
    Accessibility mode disabled
    Rendering engine: Lightspeed
    Inline CSS:  enabled
    Validate by rendering:  enabled
    Server
    Web Dynpro Runtime vendor: 'sap.com', name: 'tc/wd/webdynpro', location: 'SAP AG', counter: '7.1100.20081021173332.0000', change number: '28470', codeline: NW711_00_REL
    J2EE Engine 7.11.3710.27866.20080910102732
    System ID (SID) PID
    Server Node ID |1698650|16986|Server 00 00_16986|sappidev01.xtium.com/10.255.30.89|SERVER|RUNNING
    Java VM SAP Java 64-Bit Server VM, version:5.1.027, vendor: SAP AG
    Operating system Windows 2003, version: 5.2, architecture: amd64
    Application
    Java EE Application (deployable object) demo.sap.com/pegatest
    Web Dynpro Application Pegatestappli
    Request URI /webdynpro/dispatcher/demo.sap.com/pegatest/Pegatestappli
    Version vendor: 'demo.sap.com', name: 'pegatest', location: 'localDevelopment', counter: '20100112141118', change number: 'null'
    Session & Other
    Session Locale en_US
    Session Timezone Pacific Standard Time
    Time of Failure Tue Jan 12 00:39:45 PST 2010 (Java Time: 1263285585307)
    Session User ClientUser(id=USER.R3_DATASOURCE.J2EE_ADMIN, name=J2EE_ADMIN)
    Client Session Id bxuvisJvMVwF2Jn5_M0-ODXALydDRLAhJgFa6xkA_SAP
    Client Window Id 09190ac2ff5611dea2480050568315be
    Application Session Id 09190ac3ff5611dea70e0050568315be
    Web Dynpro Code Generation Infos
    demo.sap.com/pegatest
    Error Information
    Detailed Exception Chain
    com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Exception was thrown in preprocessing phase of application session ApplicationSession(id=09190ac3ff5611dea70e0050568315be, name=com.sap.demo.pegatest.pegatestappli.Pegatestappli). The causing exception is nested. RID=09190ac0ff5611deb9b80050568315be
      at com.sap.tc.webdynpro.clientserver.session.ClientSession.doPreprocessing(ClientSession.java:680)
      at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:239)
      at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:258)
      at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.delegateToRequestManager(AbstractExecutionContextDispatcher.java:202)
      at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.DispatchHandlerForRequestManager.doService(DispatchHandlerForRequestManager.java:38)
      at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.AbstractDispatchHandler.service(AbstractDispatchHandler.java:116)
      at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:95)
      at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.ExecutionContextDispatcher.dispatchToRequestManager(ExecutionContextDispatcher.java:140)
      at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:92)
      at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:104)
      at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doContent(AbstractDispatcherServlet.java:87)
      at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doGet(AbstractDispatcherServlet.java:54)
      at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
      at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
      at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:140)
      at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:37)
      at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:466)
      at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:291)
      at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:396)
      at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:385)
      at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:48)
      at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
      at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:76)
      at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
      at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:240)
      at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
      at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:78)
      at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
      at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
      at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
      at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
      at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
      at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
      at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
      at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
      at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
      at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
      at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
      at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:43)
      at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
      at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
      at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:42)
      at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
      at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
      at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:457)
      at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:250)
      at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:45)
      at com.sap.engine.core.thread.execution.Executable.run(Executable.java:109)
      at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)
    Caused by: com.sap.tc.webdynpro.progmodel.context.DictionaryException: InvocationTargetException
      at com.sap.tc.webdynpro.progmodel.context.DictionaryHandler.getDataType(DictionaryHandler.java:192)
      at com.sap.tc.webdynpro.progmodel.context.DataAttributeInfo.init(DataAttributeInfo.java:434)
      at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initUnmappedAttributes(NodeInfo.java:978)
      at com.sap.tc.webdynpro.progmodel.context.DataNodeInfo.doInit(DataNodeInfo.java:294)
      at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:950)
      at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:954)
      at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:69)
      at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:205)
      at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:552)
      at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doPreprocessing(ClientApplication.java:1296)
      at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.delegateToApplicationDoPreprocessing(AbstractExecutionContextDispatcher.java:146)
      at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.DispatchHandlerForAppPreprocessing.doService(DispatchHandlerForAppPreprocessing.java:35)
      at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.AbstractDispatchHandler.service(AbstractDispatchHandler.java:116)
      at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:95)
      at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.ExecutionContextDispatcher.dispatchToApplicationDoPreprocessing(ExecutionContextDispatcher.java:100)
      at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:74)
      at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.dispatch(ApplicationSession.java:571)
      at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.dispatch(ApplicationSession.java:602)
      at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doPreprocessing(ApplicationSession.java:252)
      at com.sap.tc.webdynpro.clientserver.session.ClientSession.doPreprocessing(ClientSession.java:677)
      ... 48 more
    Caused by: com.sap.dictionary.runtime.DdException: InvocationTargetException
      at com.sap.dictionary.runtime.ProviderFactory4J7.getProvider(ProviderFactory4J7.java:36)
      at com.sap.dictionary.runtime.DdDictionaryPool.getProvider(DdDictionaryPool.java:96)
      at com.sap.dictionary.runtime.DdDictionaryPool.makeDictionary(DdDictionaryPool.java:75)
      at com.sap.dictionary.runtime.DdDictionaryPool.makeDictionary(DdDictionaryPool.java:63)
      at com.sap.dictionary.runtime.DdBroker.getDataType(DdBroker.java:224)
      at com.sap.tc.webdynpro.progmodel.context.DictionaryHandler._getScalarType(DictionaryHandler.java:462)
      at com.sap.tc.webdynpro.progmodel.context.DictionaryHandler.getDataType(DictionaryHandler.java:171)
      ... 67 more
    Caused by: java.lang.reflect.InvocationTargetException
      at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
      at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
      at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
      at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
      at com.sap.dictionary.runtime.ProviderFactory4J7.getProvider(ProviderFactory4J7.java:21)
      ... 73 more
    Caused by: com.sap.conn.jco.JCoException: (106) JCO_ERROR_RESOURCE: Destination DEV_ECC6_220_METADATA does not exist
      at com.sap.mdi.jco7.Factory.makeException(Factory.java:41)
      at com.sap.mdi.jco7.Destination.<init>(Destination.java:35)
      at com.sap.mdi.jco7.Destination.make(Destination.java:21)
      at com.sap.mdi.jco7.Factory.getDestination(Factory.java:28)
      at com.sap.dictionary.runtime.mdi.DataProvider.<init>(DataProvider.java:115)
      ... 78 more
    Caused by: com.sap.conn.jco.JCoException: (106) JCO_ERROR_RESOURCE: Destination DEV_ECC6_220_METADATA does not exist
      at com.sap.conn.jco.rt.DefaultDestinationManager.update(DefaultDestinationManager.java:163)
      at com.sap.conn.jco.rt.DefaultDestinationManager.searchDestination(DefaultDestinationManager.java:292)
      at com.sap.conn.jco.rt.DefaultDestinationManager.getDestinationInstance(DefaultDestinationManager.java:90)
      at com.sap.conn.jco.JCoDestinationManager.getDestination(JCoDestinationManager.java:61)
      at com.sap.mdi.jco7.Destination.<init>(Destination.java:32)
      ... 81 more
    Caused by: java.lang.NullPointerException
      at com.sap.conn.jco.rt.DefaultDestinationManager.checkProperties(DefaultDestinationManager.java:405)
      at com.sap.conn.jco.rt.DefaultDestinationManager.update(DefaultDestinationManager.java:142)
      ... 85 more

    yes, you are getting Cross Origin Problem .So, you need to disable the web security for chrome.
    Go to properties of chrome , and add this after path of chrome.
    --disable-web-security
    After this restart the chrome.
    Please follow the below link for reference.
    windows - Is it possible to run Chrome with and without web security at the same time? - Super User
    Regards
    Sridevi

  • SQL 2012 SP1 Enterprise (SSRS in SharePoint mode): Reporting Services scale-out deployment is not supported in this edition of Reporting Services

    Hello,
    SSRS in SharePoint mode is driving me insane.
    We are recreating a SharePoint 2013 (SP1) farm in a test environment with the following set-up:
    2 SP Web FrontEnds
    2 SP Application Servers
    1 SQL Server
    At both SP APP Servers, we installed SSRS (SQL 2012 Enterprise w/ SP1) in SP integrated mode.
    We managed to start the SSRS SP service at the first SP APP Server. However when we try to start it on the second APP Server, we get the following error:
    "Reporting Services scale-out deployment is not supported in this edition of Reporting Services. This edition only supports one instance of the SQL Server Reporting Services Service in the farm.  The SQL Server Reporting Services service cannot
    be started on this server unless it is stopped on all other servers in the farm. "
    Now I can't stress this enough: This is a SQL Server 2012 SP1 Enterprise. This is the image we got from our MSDN subscription. There is no mistake here.
    Could someone please advise why SP might think this version of SSRS is not the correct one?
    Thanks in advance for your help.
    Regards,
    P.

    Hello,
    I'm afraid that is not it.
    After a long, frustrating and strenuous investigation and troubleshooting, we found the problem.
    The problem is the current ISO for SQL Server 2012 Enterprise SP1 (x64) found at MSDN. Bear in mind that we downloaded this ISO from MSDN about a month ago.
    As soon as we recreated the environment using the ISO for SQL Server 2012 Enterprise SP2 (x64) found at MSDN, everything worked as expected -- and that includes running more than one SSRS in SharePoint mode.
    Also bear in mind that we tried updating the SQL SP1 install with SP2 and subsequent cumulative updates but that never fixed the problem.
    There is something fundamentally wrong with that ISO with SP1 slipstreamed in it that no matter the subsequent updates installed, SSRS in SharePoint mode fails to work properly on a multi-server environment. We went as far as SP2 with CU3 and nothing seemed
    to fix the problem. And yes, we also performed manual updates to the SSRS and PowerPivot SharePoint MSI add-ins.
    I am shocked and distraught to find out that I lost hours of work due to a dodgy ISO image.
    Regards,
    P.

  • Best practice for customizing EJB property after deployment

    Hi Gurus,
      What is the best practice for customizing EJB property after deployment in NW7.1? I have a stateless session bean and it needs to get some environment information before acting. While the information can only be known at runtime. What should I do to achieve it? I thought I can bind the property with a JNDI context but I did not find out where to declare and change the context value. Please advise. Thanks.
    B.R.

    Hi.
    I have a similar problem. But I still can not edit the properties of the ejb-jar.xml.
    I tried to stop the web service, but the properties still remain unmodifiable.
    Could you advise me how to change them?
    We have installed SAP Server 7.0.2

  • After deployment of war/exploded war modified files are not reflected

    Dear All,
    I have done the application deployment(war/exploded war) successfully in weblogic 10.3.5.0 version But After deployment js/jsp files to get updated through the scheduler in the following path Weblogic/user_projects/domains/domain/servers/my_server/tmp/_WL_user/myapp/7i4bde/war/
    The files are getting updated successfully with updated values in above specified path.
    But it is not getting reflected, when we are accessing the application.
    Kindly help for the same..
    Thanks in Advance
    Vijay Jetti

    Hi Vijay,
    When your doing a deployment,
    Stop the Managed server,
    Rename the folders "tmp" and "cache" to tmp_04012013 and cache_04012013 inside Weblogic/user_projects/domains/domain/servers/my_server/
    (This is for clearing the Cache)
    After Deployment-->Start the managed server.
    On starting the services,new directory tmp and cache will be created and All the changes will be automatically be reflected.
    As you have said,
    After deployment js/jsp files to get updated through the scheduler in the following path
    Weblogic/user_projects/domains/domain/servers/my_server/tmp/_WL_user/myapp/7i4bde/war/Make a point to restart the managed server once the scheduled job is complete(No need to clear the cache).
    Assume your scheduler is set at 6.00,then restart the services around 6.30
    Hope this helps.
    Regards
    Fabian

  • After deployment MQ 6.0 drivers, JMS channels are Inactive

    Hi
    I have deployed MQ 6.0 drivers on PI 7.1. And after my JMS communication channels are Inactive.
    The status is showing in rwb is ..
                "Channel Has Internal Error"
                "Adapter has not provided any status information about this channel"
                "Exception: Channel with Status Unknown or Not Registered"
    I am unable to understand whether it is development issue or basis issue. Please provide solution on this.
    I have cross checked below things and everthing fine
    1. I have modified the CC configuration w.r.t PI 7.1also.
    2. Cache full refresh is working fine
    3. Vendor 7 MQ jar files are placed correctly after deployment in below folder
    /usr/sap/SID/Instance/j2ee/cluster/bin/ext/com.sap.aii.adapter.lib/lib
    CL3Export.jar
    CL3Nonexport.jar
    com.ibm.mq.jar
    com.ibm.mqjms.jar
    connector.jar
    dhbcore.jar
    rmm.jar
    4. SICF services are activie.
    Thanks & Regards
    Sudhakar Meriyala

    confirm if the deployment was done as specified in Note 1138877 - PI 7.1 : How to Deploy External Drivers JDBC/JMS Adapters
    Also try to stop and start the adapter if the configuration details given are correct in the adapter

  • Resource not release when starting/stopping the deployed application

    I am testing to deploy an standard web application on Weblogic 11gR1 at Windows XP. It is running and everything is working fine. But I noticed below situation which concersns about the release of resouce during stop and start deployed application by using Admin Server Console:
    After the deployed application starting running in Weblogic, I go to Admin Server Console to select the deployed application at deployment section and click "stop\When work complete". It looks like that the deployed application was stopped and its state went to "Prepared". Then I start it again by click "Start\Servicing all requests". It started correctly. If I tried multiple times of "Start \ Stop" operations on this deployed application, then eventurally, I got "output memory" exception and Weblogic died. I wached the memory usage of Weblogic, when applying multiple times of 'start / stop' operation on an deployed application, the memory usage of weblogic continuese to grow and until "output memory" exception occurs.
    Is it normal? What might be wrong when configuring weblogc? or somethng wrong for deployed application?
    Anybody can provide any help would be great appreciated.
    Thanks in advance.
    Jim

    Hi Mithun,
    Thanks for your reply! If stopping the deployment need some time to finish, So, admin console of weblogic should disable ( grey out ) its starting button while the related deployed application is still shutting down. After the deployed application were stopped completely, then enable the starting button again to avoid the issue.
    I just feel a little bit strange for the admin console of Weblogic to behavior on start / stop deployed application.
    Thanks,
    Zhiping

Maybe you are looking for