Multicast deployment with WDS 2012R2

Hi,
Testing WDS multicast deployment using Server 2012 R2. DHCP is also on the same box.
Unicast deployment work fine. Tested multicast scenarios but didn't helped.
Following the URL:
http://social.technet.microsoft.com/forums/windowsserver/en-US/bba1f5d1-41ff-4351-8d6c-3070b2052a59/wds-and-multicasting-session-is-starting-too-soon
But it didn't helped either, nothing found in logs we well, even there were no log generated for multicast transmission.
Note: I don't have configured anything on Switch right now.
Any suggestions?
N.A.Malik

Hi,
I think this article will be helpful, please refer to subtitle “Prerequisites
for creating a multicast transmission”
Performing Multicast Deployments
http://technet.microsoft.com/en-us/library/dd637994(v=ws.10).aspx
Hope this helps.

Similar Messages

  • 2012R2 Deployment with WDS yields Driver could not be installed error

    Hi
    I'm using WDS installed on a 2008R2 SP1 server.  My boot image is from Windows 2012.  When I deploy a Windows 2012
    R2 image I recive an error dialog during setup that states "Windows installation cannot continue because a required driver could not be installed."  In checking the setupact.log file it appears as though setup can't find pkgmgr.exe. 
    If I use the boot image from 2012 R2 then it works fine.  I want to continue using my existing boot image from 2012.  Any thoughts on why this is failing?
    Setupact.log excerpt:
    2014-02-12 06:55:33, Info       [0x0a0023] UI     progress task ProgressInfo\InstallingDrivers : StartProgress
    2014-02-12 06:55:33, Info                         Driver Install:=============================================
    2014-02-12 06:55:33, Info                         Driver Install:    Driver Path:   [\\167.68.251.22\REMINST\Stores\Drivers\vmxnet3ndis6.inf_x64_{E58F290F-F1A5-486A-BF8C-2A97B42FF9F8}\vmxnet3ndis6.inf]
    2014-02-12 06:55:33, Info                         Driver Install:    Attempting driver install.
    2014-02-12 06:55:33, Info                         Driver Install:    Driver Arch:   [9]
    2014-02-12 06:55:33, Info                         Driver Install:    Driver Root:   [D:\WINDOWS]
    2014-02-12 06:55:33, Info                         Driver Install:    Driver Drive:  [D:\]
    2014-02-12 06:55:33, Info                  CSI    00000001 Shim considered [l:256{128}]"\??\D:\WINDOWS\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.16384_none_fa1dc1539b4180d8\pkgmgr.exe"
    : got STATUS_OBJECT_PATH_NOT_FOUND
    2014-02-12 06:55:33, Info                  CSI    00000002 Shim considered [l:250{125}]"\??\D:\WINDOWS\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.16384_none_fa1dc1539b4180d8\pkgmgr.exe"
    : got STATUS_OBJECT_NAME_NOT_FOUND
    2014-02-12 06:55:33, Info                  CSI    00000003 Shim considered [l:236{118}]"\??\x:\sources\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.16384_none_fa1dc1539b4180d8\pkgmgr.exe"
    : got STATUS_OBJECT_PATH_NOT_FOUND
    2014-02-12 06:55:33, Info                  CSI    00000004 Shim considered [l:236{118}]"\??\x:\sources\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.16384_none_fa1dc1539b4180d8\pkgmgr.exe"
    : got STATUS_OBJECT_PATH_NOT_FOUND
    2014-02-12 06:55:33, Info                  CSI    00000005 Shim considered [l:112{56}]"\??\D:\WINDOWS\Servicing\6.3.9600.16384_amd64\pkgmgr.exe" :
    got STATUS_OBJECT_PATH_NOT_FOUND
    2014-02-12 06:55:33, Info                  CSI    00000006 Shim considered [l:106{53}]"\??\D:\WINDOWS\WinSxS\6.3.9600.16384_amd64\pkgmgr.exe" : got
    STATUS_OBJECT_PATH_NOT_FOUND
    2014-02-12 06:55:33, Info                  CSI    00000007 Shim considered [l:92{46}]"\??\x:\sources\6.3.9600.16384_amd64\pkgmgr.exe" : got STATUS_OBJECT_PATH_NOT_FOUND
    2014-02-12 06:55:33, Info                  CSI    00000008 Shim considered [l:92{46}]"\??\x:\sources\6.3.9600.16384_amd64\pkgmgr.exe" : got STATUS_OBJECT_PATH_NOT_FOUND
    2014-02-12 06:55:33, Error                 CSI    00000009 (F) HRESULT_FROM_WIN32(ERROR_PATH_NOT_FOUND) #1# from SssBindServicingStackParams={cb=00000040, flags=00000214,
    image={cb=00000010, flags=00000000, pcwszWindir=[10]"D:\WINDOWS"}} Cookie=(inner-null), Disp=1[gle=0x80070003]
    2014-02-12 06:55:33, Error                 CSI   
    0000000a@2014/2/12:14:55:33.601 (F) base\wcp\shim\binder.cpp(624): Error HRESULT_FROM_WIN32(ERROR_PATH_NOT_FOUND) originated in function SssBindServicingStack expression: (pInputParameters->dwFlags &
    (0x00000020))
    [gle=0x80004005]
    2014-02-12 06:55:33, Info                         Driver Install:    Driver Flags:  [1]
    2014-02-12 06:55:33, Info                         Driver Install:    Driver State:  [5]
    2014-02-12 06:55:33, Info                         Driver Install:    Driver Size:   [10823664]
    2014-02-12 06:55:33, Info                         Driver Install:    Driver Dest:   []
    2014-02-12 06:55:33, Info                         Driver Install:    Driver Result: [0x80070003]
    2014-02-12 06:55:33, Info       [0x0603b2] IBS    CallBack_InstallDriversOffline:Install Return [0x80070003]
    2014-02-12 06:55:33, Info       [0x0a0024] UI     progress task ProgressInfo\InstallingDrivers : EndProgress
    2014-02-12 06:55:33, Error      [0x0b00ae] WDS    CallBack_WdsClient_OfflineDriverInjectionEvents: Problem processing offline driver package injection event. Error code [0x80070057].
    2014-02-12 06:55:33, Info       [0x0640ae] IBSLIB PublishMessage: Publishing message [Windows installation cannot continue because a required driver could not be installed.]
    2014-02-12 06:55:33, Info       [0x0a013d] UI     Accepting Cancel. Exiting Page Progress.

    Hi,
    The WinPE version is 4.0 in using boot image on Windows Server 2012, which does not support deploy Windows 8.1/2012 R2.
    You should use WinPE 5.0 (from Windows Server 2012 R2) as you just tested. 
    If you have any feedback on our support, please send to [email protected]

  • Deployment failes (WDS+MDT2013)

    To make a long story short:
    Image procedure is: capture image from a Vmware client Windows 7 SP1 installation. Import into MDT2013, make a new Task Sequence for deploying that Image. Edit unattend xml in that TS to copyprofile.
    Update Deployment Share and import the wim into WDS. Booting client with network boot and choose the image to deploy.
    After making a new capture from a client and import into MDT. I thought this time i do not edit the TS because the name of the imported image is the same. Then updated the deployment share.
    When i tried to deploy this image a error on the client appears. First i get the menu which is in WDS on the client and choose deploy W7. The client is loading LiteTouchPE_x86.wim but when he is finished loading a Windows error problem occurs: 
    Windows failed to start. Recent hardware change might be the cause. This message appears also when
    somthing is wrong with Windows when he is not starting. 
    On the error screen beneath it says: Status: 0xc0000017    An unexpected error has occured. 
    So i think maybe this is due that i did not make a TS change. So i deleted the TS and meade
    a new one then do a edit unattend.xml. When i choose edit unattend xml a second problem arised: he tries to open the unattend but gives a error. So i start system image manually and want to open the unattend.xml which is in the control\imagename folder. Then
    he says that the unattend is not attached to an image?
    It looks like something is wrong with the LiteTouchPE_x86.wim but how can i see what it is?
    freddie

    Hi Freddie,
    I am not quite familiar with MDT and there have a specific forum to support the MDT question, more detail about the MDT question please post to the MDT support forum. At WDS
    side you can enable your WDS logging then post the error when this issue occur.
    More information:
    How to enable logging in Windows Deployment Services (WDS) in Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, and in Windows Server 2012
    http://support.microsoft.com/kb/936625/en-us
    MDT support 
    forum:
    https://social.technet.microsoft.com/Forums/en-US/home?forum=mdt
    Thanks for your understanding and support.
    I found many about this error occur with memory related issue, please try to increase your RAM then try again.
    More related information:
    Windows 7 Boot Failure due to Memory Diagnostics
    http://answers.microsoft.com/en-us/windows/forum/windows_7-system/windows-7-boot-failure-due-to-memory-diagnostics/92075cd6-a173-4a1c-976a-62e7facf1c79
    "c0000225" or "c0000017" error occurs when you try to start a Windows PE RAM disk image on a UEFI-enabled computer that is running Windows 7 or Windows Server
    2008 R2
    http://support.microsoft.com/kb/2209360/de
    I’m glad to be of help to you!
    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 Support, contact [email protected]

  • Java DC not deployed with WebDynPro DC

    Hi,
    I've been testing the DC functionality and I'm trying to create the following:
    1) WebDynPro DC (DCA)
    2) Java DC (DCB)
    DCB has code for reading data from a database table (three classes, one is set as a public part). This code is functioning ok in another WebDynpro project where I've used it as an external jar file located in the lib directory and added to classpath.
    DCA has a small table in the view that I'm filling (or trying to) with data from the database.
    DCB has one java class as a Public Part. DCA has this PP defined in the Used DC's (DC Metadata --> DC definition --> Used DC's). I can see the DCB code fine from the DCA's view (I can use the methods from the class).
    I see no code errors and everything compiles ok. I've built the DCA and DCB separately (Development Component --> Build) before doing the project build and deployment.
    When I deploy, I'm getting java.lang.NoClassDefFoundError for the DCB class (User.class) when the program starts. So it seems that the DCB is not deployed with the DCA. I've tried to look at the properties and java classpath but nothing I've done has helped.
    Purpose is set to compilation, and there is a
    <at-build-time/>
    tag in the .dcdef file.
    Deployment of normal (no DC) Webdynpro projects works fine and the jars in the lib directory are deployed to the server OK.
    Seems like I've tried everything but have found no solution yet. Refreshed every part, re-created everything, re-built, re-deployed etc...
    Shortly: how to get DCB to deploy ?
    Any help is appreciated here
    Kind Regards,
    Jari Pakarinen

    Hi,
    What is the Java DC for then ? If it cannot be used as a part of another DC (deployable unit) then how should it be used ? What is the use if it does not end up at the server with Webdynpro code ?
    The scenario I'm looking for is to include Java classes in a Webdynpro project as a part of the project (not jars done somewhere else, I can do that already) deployed to the server with the Webdynpro.
    Thank you for your help, I'm not blaming you or anything
    Regards,
    Jari

  • How to use MDS deploying with EAR file

    Hi everybody.
    I would to use MDS in my web application in order to use customization across the sessions. I've performed every step to do this on JDeveloper (11.1.1.3.1). I've tested my application deploying directly from JDeveloper using Application menu > Deploy > "myApp" to "myApplicationServer" (in this way I can choose the repository with a window like this: http://i.stack.imgur.com/Kci9c.png). The repository was prevoiusly registered on the server. In this way my application works fine and they all lived happily ever after.
    My problem occurs when I perform the deployment with "myApp to EAR" mode. When I try to install my EAR file in weblogic, it reply me with this error message:
    An error occurred during activation of changes, please see the log for details.
    +:oracle.mds.config.MDSConfigurationException:MDS-01335: namespace "/xliffBundles" mapped to metadata-store-usage "MAR_TargetRepos" but its definition was not found in MDS configuration.+
    I've looked for a solution around the web (included this forum) and I think that I should modify something in adf-config.xml file (below).
    Which steps I have to perform in order to install my application correctly with an EAR file?
    Thanks in advance.
    <?xml version="1.0" encoding="windows-1252" ?>
    <adf-config xmlns="http://xmlns.oracle.com/adf/config"
    xmlns:adf="http://xmlns.oracle.com/adf/config/properties"
    xmlns:sec="http://xmlns.oracle.com/adf/security/config"
    xmlns:ads="http://xmlns.oracle.com/adf/activedata/config">
    <adf:adf-properties-child xmlns="http://xmlns.oracle.com/adf/config/properties">
    <adf-property name="adfAppUID" value="BDO_GC_WEBAPP.bdogc"/>
    </adf:adf-properties-child>
    <!-- <ads:adf-activedata-config xmlns=
    "http://xmlns.oracle.com/adf/activedata/config">
    <latency-threshold>5000</latency-threshold>
    <keep-alive-interval>10000</keep-alive-interval>
    <max-reconnect-attempt-time>90000</max-reconnect-attempt-time>
    <reconnect-wait-time>8000</reconnect-wait-time>
    </ads:adf-activedata-config> -->
    <sec:adf-security-child xmlns="http://xmlns.oracle.com/adf/security/config">
    <CredentialStoreContext credentialStoreClass="oracle.adf.share.security.providers.jps.CSFCredentialStore"
    credentialStoreLocation="../../src/META-INF/jps-config.xml"/>
    <sec:JaasSecurityContext initialContextFactoryClass="oracle.adf.share.security.JAASInitialContextFactory"
    jaasProviderClass="oracle.adf.share.security.providers.jps.JpsSecurityContext"
    authorizationEnforce="true"
    authenticationRequire="true"/>
    </sec:adf-security-child>
    <adf-faces-config xmlns="http://xmlns.oracle.com/adf/faces/config">
    <persistent-change-manager>
    <persistent-change-manager-class>
    oracle.adf.view.rich.change.MDSDocumentChangeManager
    </persistent-change-manager-class>
    </persistent-change-manager>
    <taglib-config>
    <taglib uri="http://xmlns.oracle.com/adf/faces/rich">
    <tag name="column">
    <attribute name="displayIndex">
    <persist-changes>
    true
    </persist-changes>
    </attribute>
    <attribute name="frozen">
    <persist-changes>
    true
    </persist-changes>
    </attribute>
    <attribute name="noWrap">
    <persist-changes>
    true
    </persist-changes>
    </attribute>
    <attribute name="selected">
    <persist-changes>
    true
    </persist-changes>
    </attribute>
    <attribute name="visible">
    <persist-changes>
    true
    </persist-changes>
    </attribute>
    <attribute name="width">
    <persist-changes>
    true
    </persist-changes>
    </attribute>
    </tag>
    <tag name="table">
    <attribute name="filterVisible">
    <persist-changes>
    true
    </persist-changes>
    </attribute>
    </tag>
    </taglib>
    </taglib-config>
    </adf-faces-config>
    <adf-mds-config xmlns="http://xmlns.oracle.com/adf/mds/config">
    <mds-config xmlns="http://xmlns.oracle.com/mds/config" version="11.1.1.000">
    <cust-config>
    <match path="/">
    <customization-class name="oracle.adf.share.config.UserCC"/>
    </match>
    </cust-config>
    </mds-config>
    </adf-mds-config>
    </adf-config>

    Any suggestion?

  • EJB3.0 App deployed with warning:Object not found in lookup of JPA_DEFAULT

    Hi All ,
               I am working on NWCE7.1. I am deploying Enterprise Application DC wich is having
    1 . 3 EJB3.0 session DCs
    2.  1 JPA DC
    I am getting following warning in deployment. I have checked persistence.xml for jta-data-source , it is added. Still not working. I am getting this error after importing configuration(Track) for these DCs in my NWDS. Earlier build n deployment was working in other NWDS on other PC.
    --- Deploying file(s):
         D:\NWDS7.1\workspace.jdi\4\DCs\asianpaints.com\erecapp\_comp\gen\default\deploy\asianpaints.com~erecapp.ear
    --- Status:
         Deploy finished with warnings.
    --- Description:
                S U M M A R Y
    ~~~~~~~~~~~~~~~~~~~
    Successfully deployed:           0
    Deployed with warnings:           1
    Failed deployments:                0
    ~~~~~~~~~~~~~~~~~~~
    1. File:D:\NWDS7.1\workspace.jdi\4\DCs\asianpaints.com\erecapp\_comp\gen\default\deploy\asianpaints.com~erecapp.ear
         Name:erecapp
         Vendor:asianpaints.com
         Location:J2N_ERECTT_D
         Version:20090217100038
         Deploy status:Warning
         Version:HIGHER
         Description:
              1. Exception has been returned while the 'asianpaints.com/erecapp' was starting. Warning/Exception :
    [ERROR CODE DPL.DS.6193] Error while ; nested exception is:
         com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5030] Clusterwide exception: server ID 6358450:com.sap.engine.services.orpersistence.container.deploy.ActionException: [ERROR CODE DPL.DS.5030] Clusterwide exception: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of JPA_DEFAULT.
         at com.sap.engine.services.jndi.implserver.ServerContextImpl.lookup(ServerContextImpl.java:584)
         at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:343)
         at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:637)
         at javax.naming.InitialContext.lookup(InitialContext.java:351)
         at javax.naming.InitialContext.lookup(InitialContext.java:351)
         at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.initDataSources(ComplexModuleCreator.java:344)
         at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.initRuntimeModels(ComplexModuleCreator.java:230)
         at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.createModule(ComplexModuleCreator.java:154)
         at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.execute(ComplexModuleCreator.java:84)
         at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexActionAdapter.execute(ComplexActionAdapter.java:34)
         at com.sap.engine.services.orpersistence.container.deploy.impl.ApplicationCreator.execute(ApplicationCreator.java:74)
         at com.sap.engine.services.orpersistence.container.deploy.impl.PersistenceContainer.prepareStart(PersistenceContainer.java:187)
         at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:219)
         at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:179)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:420)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:445)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.super_MakeAllPhases(ParallelAdapter.java:337)
         at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:550)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:251)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:392)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3389)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3375)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3278)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3251)
         at com.sap.engine.services.dc.lcm.impl.J2EELCMProcessor.doStart(J2EELCMProcessor.java:99)
         at com.sap.engine.services.dc.lcm.impl.LifeCycleManagerImpl.start(LifeCycleManagerImpl.java:62)
         at com.sap.engine.services.dc.cm.deploy.impl.LifeCycleManagerStartVisitor.visit(LifeCycleManagerStartVisitor.java:34)
         at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
         at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcessLCMDeplItem(DefaultDeployPostProcessor.java:80)
         at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcess(DefaultDeployPostProcessor.java:56)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doPostProcessing(DeployerImpl.java:741)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.performDeploy(DeployerImpl.java:732)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doDeploy(DeployerImpl.java:576)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:270)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:192)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImplp4_Skel.dispatch(DeployerImplp4_Skel.java:875)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:351)
         at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:70)
         at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:62)
         at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:37)
         at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:877)
         at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:53)
         at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:58)
         at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108)
         at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:304)
         at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.initDataSources(ComplexModuleCreator.java:360)
         at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.initRuntimeModels(ComplexModuleCreator.java:230)
         at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.createModule(ComplexModuleCreator.java:154)
         at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.execute(ComplexModuleCreator.java:84)
         at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexActionAdapter.execute(ComplexActionAdapter.java:34)
         at com.sap.engine.services.orpersistence.container.deploy.impl.ApplicationCreator.execute(ApplicationCreator.java:74)
         at com.sap.engine.services.orpersistence.container.deploy.impl.PersistenceContainer.prepareStart(PersistenceContainer.java:187)
         at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:219)
         at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:179)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:420)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:445)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.super_MakeAllPhases(ParallelAdapter.java:337)
         at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:550)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:251)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:392)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3389)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3375)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3278)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3251)
         at com.sap.engine.services.dc.lcm.impl.J2EELCMProcessor.doStart(J2EELCMProcessor.java:99)
         at com.sap.engine.services.dc.lcm.impl.LifeCycleManagerImpl.start(LifeCycleManagerImpl.java:62)
         at com.sap.engine.services.dc.cm.deploy.impl.LifeCycleManagerStartVisitor.visit(LifeCycleManagerStartVisitor.java:34)
         at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
         at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcessLCMDeplItem(DefaultDeployPostProcessor.java:80)
         at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcess(DefaultDeployPostProcessor.java:56)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doPostProcessing(DeployerImpl.java:741)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.performDeploy(DeployerImpl.java:732)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doDeploy(DeployerImpl.java:576)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:270)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:192)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImplp4_Skel.dispatch(DeployerImplp4_Skel.java:875)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:351)
         at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:70)
         at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:62)
         at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:37)
         at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:877)
         at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:53)
         at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:58)
         at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108)
         at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:304)
    Result
    Status:Warning

    You have to give an explicit data source in your persistence.xml to solve this error normaly.
    <persistence version="1.0" xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd">
         <persistence-unit name="YOUR_UNIT">
        <jta-data-source>DSNAME</jta-data-source>
    Frank

  • Replace a 2003 (not R2) File Server with a 2012R2 files server and preferably keep the same machine name and IP when finished

    I am wanting to replace a 2003 (not R2) File Server with a 2012R2 file server and preferably keep the same machine name and IP when finished.  For the moment I just need some "high level" guidance, little details can be worked out once I know
    which direction I will go.  I was considering that DFS might be a way to help get through the process although when finished the 2012R2 Files server will be by itself with no other file server planned at this time.  DFS can stay installed for maybe
    future purposes but clearly I wouldn't need the DFS Replication with only one machine.
    Here's a few details of the environment....
    1.  DC's are 2012R2 but it is still 2003 DFL because the old 2003 DCs are still present.  But likely they will be gone and the DFL elevated before I start on the File Server project
    2. Nearly all machines in the facility have a shortcut on the "All Users" Desktop that points to the existing old File Server.  Editing or replacing that shortcut would be a major pain,...hence why I want to keep the same machine name at least,
    and maybe the same IP if not too much trouble.  This way the existing shortcut would continue to work with the new 2012R2 File Server.  The UNC path represented in that shortcut is also configured into one or more of our major business applications,
    futher emphasizing the need to keep the UNC path the same throughout the process.
    3. The facility runs 24/7/365 but is "light" on weekends.  The political environment is such that there is little to no tolerance for any down time at all.
    4. Would DFS (based from the 2012R2 machine) be a good tool to get where I need to go?
    Thanks for any suggestions.
    Phillip Windell

    Hi Sharon,
    I've done some more reading and have a few new ideas to run past you....
    Yes regular DFS wouldn't help and the Namespace would still be different than how it was with just the old server. However I was thinking DFS Replication could replace the purpose of RoboCopy and it would keep the two locations "in sync" until I was ready
    to flip over to the new server.  DFS Rep can exist independently of a DFS Namespace, so a Namespace is not even needed. It needs a minimum of 2003R2 for the "later & better" DFS Rep but I believe 2003 can do an "in place" upgrade to 2003R2, so I would upgrade
    the old server to 2003R2 first.  As long as the DFS Rep on 2012R2 and 2003R2 will properly interact I think that will work.
    Thanks for the reg info on the Shares.  I'm debating if editing that would reg file would really be much better than manually creating the Shares on the new server while the DFS Replication was doing its job.  I'll probably export that Key as a
    safety move whether I use it or not.
    Once the DFS Rep is fully in sync and the Shares are in place on the new server, I figure I would then:
    1. Remove the DFS Replication Object (optionally remove DFS Services completely)
    2. Rename the old File Server to something else and set it to DHCP
    3. Rename the new File Server to the name I want to use and give it the IP the old server had.
    How does that sound?
    Phillip Windell

  • Multicast issue with Win XP

              I am wondering if anyone else has encountered Multicast problems with Windows XP.
              I think I am, and believe these issues are preventing the servers in my clusters
              from syncing their JNDI tree bindings.
              I noticed this while configuring a JMS Server and Queues in a clustered development
              environment. It is a simple cluster of 2 servers both on a single Win XP machine,
              see post 14712 in weblogic.developer.interest.jms (http://newsgroups2.bea.com/cgi-bin/dnewsweb?cmd=article&group=weblogic.developer.interest.jms&item=14712&utag=).
              I tried the MultiCast test utility (http://e-docs.bea.com/wls/docs81/admin_ref/utils.html#1199798)
              and found what I think means I have a multicast problem. Output follows:
              ------ Begin MultiCast test utility output: ------
              C:\bea\weblogic81\server\lib>java -cp weblogic.jar utils.MulticastTest -N server200
              -A 237.155.155.1 -t 15
              ***** WARNING ***** WARNING ***** WARNING *****
              Do NOT use the same multicast address as a running WLS cluster.
              Starting test. Hit any key to abort
              Using multicast address 237.155.155.1:7001
              Will send messages under the name server200 every 2 seconds
              Will print warning every 15 seconds if no messages are received
              I (server200) sent message num 1
              I (server200) sent message num 2
              I (server200) sent message num 3
              I (server200) sent message num 4
              I (server200) sent message num 5
              I (server200) sent message num 6
              I (server200) sent message num 7
              java.net.SocketTimeoutException: Receive timed out
              at java.net.PlainDatagramSocketImpl.receive(Native Method)
              at java.net.DatagramSocket.receive(Unknown Source)
              at utils.MulticastTest$Receiver.run(MulticastTest.java:304)
              I (server200) sent message num 8
              I (server200) sent message num 9
              I (server200) sent message num 10
              I (server200) sent message num 11
              ------ End MultiCast test utility output: ------
              I expected to see "Received message X from server200" messages, like I saw from
              the Win2K machines I tried.
              There is a Microsoft Knowledge Base Article - 827536, "An IP multicast may not
              be sent correctly from Windows XP or from Windows Server 2003" (http://support.microsoft.com/default.aspx?scid=kb;en-us;827536).
              The issue appears to be limited to computers with more than one network adapter
              (like I have). I am pursuing the hotfix from Microsoft, but these things take
              time.
              Anyone else having similar issues?
              Any and all help is appreciated.
              

              I am facing a problem and believe that its because of multicast too. The problem
              is seen on XP but not on W2000.
              The MulticastTest when executed does not show any message exchange at all. When
              a server is started I get following exception
              <BEA-000364> <Server failed during initialization. Exception:weblogic.server.ServerLifecycleException:
              Failed to listen on multicast address
              weblogic.server.ServerLifecycleException: Failed to listen on multicast address
                   at weblogic.cluster.ClusterCommunicationService.initialize(ClusterCommunicationService.java:57)
                   at weblogic.t3.srvr.T3Srvr.initializeHere(T3Srvr.java:922)
                   at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:664)
                   at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:342)
                   at weblogic.Server.main(Server.java:32)
              Caused by: java.net.SocketException: error setting options
                   at java.net.PlainDatagramSocketImpl.join(Native Method)
                   at java.net.PlainDatagramSocketImpl.join(PlainDatagramSocketImpl.java:134)
                   at java.net.MulticastSocket.joinGroup(MulticastSocket.java:274)
                   at weblogic.cluster.FragmentSocket.initializeMulticastSocket(FragmentSocket.java:92)
                   at weblogic.cluster.FragmentSocket.start(FragmentSocket.java:109)
                   at weblogic.cluster.MulticastManager.startListening(MulticastManager.java:164)
                   at weblogic.cluster.ClusterCommunicationService.initialize(ClusterCommunicationService.java:52)
                   ... 4 more
              >
              Are you experiencing similar problem ?
              Parag
              "Andy Frank" <[email protected]> wrote:
              >
              >I am wondering if anyone else has encountered Multicast problems with
              >Windows XP.
              > I think I am, and believe these issues are preventing the servers in
              >my clusters
              >from syncing their JNDI tree bindings.
              >
              >
              >I noticed this while configuring a JMS Server and Queues in a clustered
              >development
              >environment. It is a simple cluster of 2 servers both on a single Win
              >XP machine,
              >see post 14712 in weblogic.developer.interest.jms (http://newsgroups2.bea.com/cgi-bin/dnewsweb?cmd=article&group=weblogic.developer.interest.jms&item=14712&utag=).
              >
              >
              >I tried the MultiCast test utility (http://e-docs.bea.com/wls/docs81/admin_ref/utils.html#1199798)
              >and found what I think means I have a multicast problem. Output follows:
              >
              >
              >------ Begin MultiCast test utility output: ------
              >C:\bea\weblogic81\server\lib>java -cp weblogic.jar utils.MulticastTest
              >-N server200
              >-A 237.155.155.1 -t 15
              >***** WARNING ***** WARNING ***** WARNING *****
              >Do NOT use the same multicast address as a running WLS cluster.
              >
              >
              >Starting test. Hit any key to abort
              >
              >
              >Using multicast address 237.155.155.1:7001
              >Will send messages under the name server200 every 2 seconds
              >Will print warning every 15 seconds if no messages are received
              >
              > I (server200) sent message num 1
              > I (server200) sent message num 2
              > I (server200) sent message num 3
              > I (server200) sent message num 4
              > I (server200) sent message num 5
              > I (server200) sent message num 6
              > I (server200) sent message num 7
              >java.net.SocketTimeoutException: Receive timed out
              > at java.net.PlainDatagramSocketImpl.receive(Native Method)
              > at java.net.DatagramSocket.receive(Unknown Source)
              > at utils.MulticastTest$Receiver.run(MulticastTest.java:304)
              > I (server200) sent message num 8
              > I (server200) sent message num 9
              > I (server200) sent message num 10
              > I (server200) sent message num 11
              >------ End MultiCast test utility output: ------
              >
              >I expected to see "Received message X from server200" messages, like
              >I saw from
              >the Win2K machines I tried.
              >
              >
              >There is a Microsoft Knowledge Base Article - 827536, "An IP multicast
              >may not
              >be sent correctly from Windows XP or from Windows Server 2003" (http://support.microsoft.com/default.aspx?scid=kb;en-us;827536).
              > The issue appears to be limited to computers with more than one network
              >adapter
              >(like I have). I am pursuing the hotfix from Microsoft, but these things
              >take
              >time.
              >
              >
              >Anyone else having similar issues?
              >
              >Any and all help is appreciated.
              

  • SCCM: Application deployment vs Package deployment with requirements and prerequisits.

    Hey,
    My organization is in the process of implementing a new remote networking solution for all employees, however some employees require additional software vs others. What I am trying to find out is if there is a way to have one package with supersedes and
    requirements that we can use to do a massive deployement. 
    Here are the different scenarios with order of installation:
    Financial group Desktop:
    1.Install New solution
    2.Install Configuration
    3.Install Token Authentication 
    (nothing crazy)
    Financial Group Laptops
    1.Install Token Authentication
    2.Install New Solution
    3.Install COnfiguration
    4.Un-uninstall Old Solution
    5.Un-install Tunnel Guard application (requires a reboot, that's why it's last). (this is the application that would be deployed with requirements to go back up the chain of supersedes (meaning, deploy 5, but do 4, when 4 is triggered, it does 3 first, etc...)
    All other laptops
    1.Install New Solution
    2.Install COnfiguration
    3.Un-uninstall Old Solution
    4.Un-install Tunnel Guard application (requires a reboot, that's why it's last).(this is the application that would be deployed with requirements to go back up the chain of supersedes (meaning, deploy 4, but do 3, when 3 is triggered, it does 2 first, etc...)
    Because of the different requirements, is there a way to have one deployment with multiple deployment types to say based off:
    1. Computer types (we have a naming convention that identifies laptops and desktops.
    2. Only install certain pieces of software (Token validator in this case if financial application is detected on the machine).
    Or should I create different applications for each case with different collections or go with 3 different packages and collections with install this package first set in the package deployment
    Thanks for your help.

    The problem is the last uninstall, because it's not applicable to all machines. That means that if you would deploy that with all it's dependencies, it wouldn't do anything on the desktops as it's not applicable to them.
    In this case, if you want to use one deployment, the easiest solution is a task sequence. That way you can target everything in one time and still build some logic to prevent some (un-)installs.
    My Blog: http://www.petervanderwoude.nl/
    Follow me on twitter: pvanderwoude

  • Patch deployment with status "Enforcement state unknown"

    Hi All
    I am pretty new to the patch deployment.
    I generated a report and see there is Last State column with "Enforcement state unknown", not sure if it means failed for those hostnames or will be retried for the installation.
    Kindly clarify.
    Regards
    Ramesh
    Regards Ram

    They will only start to install updates automatically when there is an active update deployment with a scheduled deadline that has past. See for a lot more information:
    http://technet.microsoft.com/en-us/library/gg682168.aspx#BKMK_SUMCompliance
    Also, when Days since last communication is more than 0, that's usually an indication that the client is not communicating any more. That can be caused by a lot of things including something simple as that the device is turned of, or not
    connected with the network.
    My Blog: http://www.petervanderwoude.nl/
    Follow me on twitter: pvanderwoude

  • Multiple SSIDs with WDS, custom DHCP addresses, & Web interface

    I just bought an Aiport Extreme Base station along with an Aiport Express. So far, everything is great, but I had a few of things I would like configure a certain way, and I am having a little problem.
    Just to let you know, I am using the base station as the main router/firewall (with my cable modem). I am using the express basically as a wireless bridge (via WDS).
    The way Apple takes care of things with WDS, is by assiging the same SSID to both the base station and express for seamless roaming. However, I would like them both to have their own SSID. I cannot seem to get this working, and I know that some other vendors allow this (Buffalo, Linksys).
    The other issue is regarding DHCP on the LAN side. I want to for example hand out IP addresses 192.168.2.50-60 to my internal clients, and I want the base station to have an address of 192.168.2.1 and the express to have 192.168.2.5. It seems this also I am having problems with. It seems like the base station is very rigid on what options I have in this regard.
    Lastly, I wondered if there is any other way to administer these guys (like a web browser). Sometimes I need to remotely make changes to the router, and don’t really want to install another app just for this purpose (especially at work, or some other remote location).
    Thanks
    Mac Mini 1.25 GHz   Mac OS X (10.4.3)   1 Gig of RAM

    The way Apple takes care of things with WDS, is by
    assiging the same SSID to both the base station
    and
    express for seamless roaming. However, I would
    like
    them both to have their own SSID.
    I don't know why you'd want that but if you are
    extending the range of your wireless network with WDS
    it isn't possible with Airports.
    The other issue is regarding DHCP on the LAN side.
    I
    want to for example hand out IP addresses
    192.168.2.50-60 to my internal clients, and I want
    the base station to have an address of 192.168.2.1
    and the express to have 192.168.2.5. It seems this
    also I am having problems with.
    You can set the DHCP range and then assign static
    IP's to anything that conforms to that network as
    long as it won't conflict with something
    automatically assigned by DHCP. As a router NAT must
    be enabled so if you want a unique range of numbers
    only DHCP is used which won't work in your case.
    In other words set the range at 192.168.1.1 and that
    is the address of the base station. That can be used
    for the statically IP'd device's router and DNS
    entries as well like this:
    Device 1 IP 192.168.1.101
    Device 1 subnet 255.255.255.0
    Device 1 router 192.168.1.1
    Device 1 DNS 192.168.1.1
    Device 2 IP 192.168.1.102
    Device 2 subnet 255.255.255.0
    Device 2 router 192.168.1.1
    Device 2 DNS 192.168.1.1
    etc...
    Lastly, I wondered if there is any other way to
    administer these guys (like a web browser).
    Not that I'm aware of. Airport Admin Utility is all
    there is. I have seen a java utility but it wasn't
    very friendly.
    Thanks for the answers. Despite these minor limitations, so far the Apple hardware is some of the best 802.11 stuff I have used (except for maybe a Cisco 1200).

  • ESS/MSS business packages "Deployed with Warning"

    Hello All,
       We are on NW04s SP10 on MS SQL server and Windows server. The Database and portal installations or on different machines. I installed the business packages ESS 1.0, MSS 1.0 and the XSS components - 600 using the JSPM.
    After I deploy, I get the message<b> "Deployed with Warning"</b>
    When I opened the log files and checked for errors, I found errors in deployment on these SDAs
    sap.com/essfiaddr  - WEBDYNPRO
    sap.com/essinaddr  - WEBDYNPRO
    sap.com/essinpdata  - WEBDYNPRO
    sap.com/mssexpdyn  - WEBDYNPRO
    sap.com/mssexpssa  - WEBDYNPRO
    sap.com/mssoprogeneraldescription  - WEBDYNPRO
    And I get the following exceptions for all the SDAs above.
    <b>07/01/11 09:54:10 -    sap.com/essfiaddr  - WEBDYNPRO
    07/01/11 09:54:10 -  ***********************************************************
    Jan 11, 2007 9:54:11 AM  Info: End of log messages of the target system.
    Jan 11, 2007 9:54:11 AM  Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
    Jan 11, 2007 9:54:11 AM  Warning: Finished with warnings: development component 'ess/fi/addr'/'sap.com'/'MAIN_ERP05PAT_C'/'795293':
    Caught exception during application startup from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: Error occurred while starting application sap.com/ess/fi/addr and wait.
    Reason: Clusterwide exception: server ID 11376250:com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to prepare application ''sap.com/essfiaddr'' for startup. Reason=
    Clusterwide exception: Failed to start application ''sap.com/essfiaddr'': The referenced application ''sap.com/ess~per'' can''t be started. Check the causing exception for details. Hint: Is the referenced application deployed correctly on the server?
         at com.sap.engine.services.webdynpro.WebDynproContainer.prepareStart(WebDynproContainer.java:1490)
         at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:231)
         at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:179)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:301)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:317)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:111)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:227)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4684)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4589)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4562)
         at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1163)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:304)
         at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:193)
         at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:122)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)</b>
    Now, after this, when I log into the portal and see the MSS role, the links are all missing. I see only Overview and its worksets and pages and Reports and its worksets. Everything else is missing. The warning that I see is<b> "Linked object is unavailable"</b>
    Could anyone please suggest me what could be wrong?
    Thanks,
    Sunitha<b></b>

    Hi Sunitha,
    First of all I was not able to find if your backend is ERP 2004 or ERP 2005. It should be ERP 2005 if you want to user ESS 1.0 and MSS 1.0 BP
    Please check in Content Administrator if you can locate these applications and test the same. If yes then you can ignore this warning. If No, in that case you have to redeploy XSS, ESS and MSS using SDM again.
    The links in portal comes from your backend Area Page Customizing. To verify if the problem is with your Portal Business Package or with your backend customizing run your ESS applications using
    http://<portal>:<port>/webdynpro/dispatcher/sap.com/pcui_gp~xssutils/XssMenuArea?sap.xss.menuhdr=SAPDEFAULT&sap.xss.menuargrp=SAPDEFAULTESS
    and MSS using
    http://<portal>:<port>/webdynpro/dispatcher/sap.com/pcui_gp~xssutils/XssMenuArea?sap.xss.menuhdr=SAPDEFAULT&sap.xss.menuargrp=SAPDEFAULTMSS
    If you can see all the links correctly here, your backend customization is fine and there is a problem with your BP of ESS and MSS. So you will have to import the same again in the portal. However if you are not able to view the links in the page, then there is a problem with you Area Page Customization. You will need to check your config with the Client 000 configuration to find out the missing config.
    Hope this helps.
    Regards,
    Shubham

  • SAP Netweaver 04 SP16 deployed with Xalan 2.60 or Xalan 2.70

    SAP Netweaver 04 SP16 deployed with Xalan 2.60 or Xalan 2.70
    Have you tried to port and run (Sneak Preview)  SAPNetWeaver java 04 SP16 or 04S SP7 with a later version on Xalan version 2.60 or Xalan version 2.70 along with jdk 1.4.2_(8 or greater)?
    What specifically is failing? What patches or work around have you used to overcome compatibility issues with Xalan?
    When we run Sneak Preview SAPNetWeaver java 04 SP16 SP7 with a version on Xalan version 2.60 or Xalan version 2.70 along with jdk 1.4.2_11, We get error 503 Service Unavailable, Application cannot be started
    Details: com.sap.engine.services.deploy.container.ExceptionInfo: Error while parsing file “data-source-aliases.xml”.

    Hi
    SAP does not allow usage of any other XML parsers with SAP web AS.
    please have a look at this link
    http://help.sap.com/saphelp_nw04/helpdata/en/36/ef353e39011a38e10000000a114084/frameset.htm
    "Setting system properties in a system that supports more than one parser is prohibited".
    The Error which you are getting is because one of the
    java.system properties for parsing is
    getting changed by xalan. These system properties are explictly set by the SAP XML implementation which it does not allow you to change.
    Also can you please let me know where are you placing the xalan jar file ? is it deployed as a j2ee library or part of war ?
    Hope this helps. please mark points for helpful answers
    regards
    rajesh kr

  • Deploy with warning

    Hi.All.
    when i deployed  WD application , it end with warning ,could someone tell me how to do.
    --- Deploying file(s):
         E:\Documents and Settings\MrBryant\workspace_rt.jdi\LocalDevelopment\DCs\demo.sap.com\tutorial_pagenavigation\_comp\gen\default\deploy\demo.sap.com~tutorial_pagenavigation.ear
    --- Status:
         Deploy finished with warnings.
    --- Description:
                S U M M A R Y
    ~~~~~~~~~~~~~~~~~~~
    Successfully deployed:           0
    Deployed with warnings:           1
    Failed deployments:                0
    ~~~~~~~~~~~~~~~~~~~
    1. File:E:\Documents and Settings\MrBryant\workspace_rt.jdi\LocalDevelopment\DCs\demo.sap.com\tutorial_pagenavigation\_comp\gen\default\deploy\demo.sap.com~tutorial_pagenavigation.ear
         Name:tutorial_pagenavigation
         Vendor:demo.sap.com
         Location:localDevelopment
         Version:20090421170011
         Deploy status:Warning
         Version:HIGHER
         Description:
              1. Exception has been returned while the [demo.sap.com/tutorial_pagenavigation] was starting. Warning/Exception :[
    ][[ERROR CODE DPL.DS.6193] Error while ; nested exception is:
         com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5030] Clusterwide exception: [server ID 48033250:can't instantiate default ORB implementation com.sun.enterprise.iiop.POAEJBORB
               -> com.sun.enterprise.iiop.POAEJBORB
    ------------------------- Loader Info -------------------------
    ClassLoader name: [service:deploy]
    Living status: alive
    Direct parent loaders:
       [system:Frame]
       [library:core_lib]
       [library:tc~bl~txmanager~plb]
       [service:iiop]
       [service:file]
       [library:tc~je~jlinee~lib]
    Resources:
       /usr/sap/C04/J04/j2ee/cluster/bin/services/deploy/lib/private/sap.com~tc~je~deploy~impl.jar
    server ID 48033250:com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5035] Application [demo.sap.com/tutorial_pagenavigation] cannot be started. Reason: it has hard reference to resource [tc~wd~api] with type [application], which is not active on the server.
    Hint: 1) Is referred resource deployed? 2) Is referred resource able to start?
         at com.sap.engine.services.deploy.server.ReferenceResolver.checkApplicationStatus(ReferenceResolver.java:871)
         at com.sap.engine.services.deploy.server.ReferenceResolver.processReferenceToApplication(ReferenceResolver.java:848)
         at com.sap.engine.services.deploy.server.ReferenceResolver.processMakeReference(ReferenceResolver.java:575)
         at com.sap.engine.services.deploy.server.ReferenceResolver.beforeStartingApplication(ReferenceResolver.java:489)
         at com.sap.engine.services.deploy.server.application.StartTransaction.beginCommon(StartTransaction.java:169)
         at com.sap.engine.services.deploy.server.application.StartTransaction.begin(StartTransaction.java:134)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:493)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:467)
         at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:560)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:197)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:358)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3432)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3418)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3308)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3280)
         at com.sap.engine.services.dc.lcm.impl.J2EELCMProcessor.doStart(J2EELCMProcessor.java:105)
         at com.sap.engine.services.dc.lcm.impl.LifeCycleManagerImpl.start(LifeCycleManagerImpl.java:78)
         at com.sap.engine.services.dc.cm.deploy.impl.LifeCycleManagerStartVisitor.visit(LifeCycleManagerStartVisitor.java:34)
         at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
         at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcessLCMDeplItem(DefaultDeployPostProcessor.java:91)
         at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcess(DefaultDeployPostProcessor.java:61)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doPostProcessing(DeployerImpl.java:862)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.performDeploy(DeployerImpl.java:810)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doDeploy(DeployerImpl.java:640)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:359)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:248)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImplp4_Skel.dispatch(DeployerImplp4_Skel.java:897)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:355)
         at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:69)
         at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:67)
         at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:41)
         at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:977)
         at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:57)
         at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:55)
         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.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5035] Application [sap.com/tc~wd~api] cannot be started. Reason: it has hard reference to resource [tc~wd~dispwda] with type [application], which is not active on the server.
    Hint: 1) Is referred resource deployed? 2) Is referred resource able to start?
         at com.sap.engine.services.deploy.server.ReferenceResolver.checkApplicationStatus(ReferenceResolver.java:871)
         at com.sap.engine.services.deploy.server.ReferenceResolver.processReferenceToApplication(ReferenceResolver.java:848)
         at com.sap.engine.services.deploy.server.ReferenceResolver.processMakeReference(ReferenceResolver.java:575)
         at com.sap.engine.services.deploy.server.ReferenceResolver.beforeStartingApplication(ReferenceResolver.java:489)
         at com.sap.engine.services.deploy.server.application.StartTransaction.beginCommon(StartTransaction.java:169)
         at com.sap.engine.services.deploy.server.application.StartTransaction.beginLocal(StartTransaction.java:142)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:582)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:202)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:367)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.regularStartApplicationLocalAndWait(DeployServiceImpl.java:3229)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:3221)
         at com.sap.engine.services.deploy.server.ReferenceResolver.checkApplicationStatus(ReferenceResolver.java:863)
         ... 35 more
    Caused by: com.sap.engine.services.servlets_jsp.server.exceptions.WebDeploymentException: Error in starting application [sap.com/tc~wd~dispwda].
         at com.sap.engine.services.servlets_jsp.server.deploy.StartAction.prepareStart(StartAction.java:246)
         at com.sap.engine.services.servlets_jsp.server.deploy.WebContainer.prepareStart(WebContainer.java:420)
         at com.sap.engine.services.deploy.server.utils.container.ContainerWrapper.prepareStart(ContainerWrapper.java:363)
         at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:228)
         at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:194)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:591)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:202)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:367)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.regularStartApplicationLocalAndWait(DeployServiceImpl.java:3229)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:3221)
         at com.sap.engine.services.deploy.server.ReferenceResolver.checkApplicationStatus(ReferenceResolver.java:863)
         ... 46 more
    Caused by: org.omg.CORBA.INITIALIZE: can't instantiate default ORB implementation com.sun.enterprise.iiop.POAEJBORB  vmcid: 0x0  minor code: 0  completed: No
         at org.omg.CORBA.ORB.create_impl(ORB.java:297)
         at org.omg.CORBA.ORB.init(ORB.java:336)
         at com.sap.engine.services.servlets_jsp.server.application.NamingResources.bindNamingResources(NamingResources.java:147)
         at com.sap.engine.services.servlets_jsp.server.application.ApplicationContext.init(ApplicationContext.java:937)
         at com.sap.engine.services.servlets_jsp.server.deploy.StartAction.createContext(StartAction.java:305)
         at com.sap.engine.services.servlets_jsp.server.deploy.StartAction.prepareStart(StartAction.java:141)
         ... 56 more
    Caused by: java.lang.ClassNotFoundException: com.sun.enterprise.iiop.POAEJBORB
    ------------------------- Loader Info -------------------------
    ClassLoader name: [service:deploy]
    Living status: alive
    Direct parent loaders:
       [system:Frame]
       [library:core_lib]
       [library:tc~bl~txmanager~plb]
       [service:iiop]
       [service:file]
       [library:tc~je~jlinee~lib]
    Resources:
       /usr/sap/C04/J04/j2ee/cluster/bin/services/deploy/lib/private/sap.com~tc~je~deploy~impl.jar
         at com.sap.engine.boot.loader.MultiParentClassLoader.loadClass(MultiParentClassLoader.java:274)
         at com.sap.engine.boot.loader.MultiParentClassLoader.loadClass(MultiParentClassLoader.java:243)
         at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:363)
         at java.lang.Class.forName0(Native Method)
         at java.lang.Class.forName(Class.java:242)
         at org.omg.CORBA.ORB.create_impl(ORB.java:295)
         ... 61 more
    Result
    Status:Warning
    Edited by: zhenhua peng on Apr 21, 2009 11:24 AM

    Hi,
    From the logs it is clear that your application is dependent on [tcwdapi] which is either not deployed on the target server or failed to start. This is called as class loader exception. To overcome this issue, you have to either deploy the reference application or see to that it is in "Started" status in the target server. If you have trouble in starting the application, then it might be necessary to restart the java server and then do the deployment.
    Regards,
    Pranav

  • The application was previously deployed with version 'V2.0'

    hi am having this error where running my appication am in jdeveloper 11.1.1.6.0,the application was running correct the previous day
    IntegratedWebLogicServer startup time: 34045 ms.[Running application  on Server Instance IntegratedWebLogicServer...]
    IntegratedWebLogicServer started.
    [09:32:46 AM] ----  Deployment started.  ----
    [09:32:46 AM] Target platform is  (Weblogic 10.3).
    [09:32:46 AM] Retrieving existing application information
    [09:32:46 AM] Running dependency analysis...
    [09:32:46 AM] Deploying 3 profiles...
    [09:32:46 AM] Wrote MAR file to C:\Users\10017134\AppData\Roaming\JDeveloper\system11.1.1.6.38.61.92\o.j2ee\drs\AutoGeneratedMar
    [09:32:49 AM] Wrote Web Application Module to C:\Users\10017134\AppData\Roaming\JDeveloper\system11.1.1.6.38.61.92\o.j2ee\drs\ViewControllerWebApp.war
    [09:32:49 AM] Info: Namespace '/persdef' is mapped to deploy-target metadata-store-usage 'WebCenterFileMetadataStore' in adf-config.xml but no metadata from the namespace is included in the MAR.
    [09:32:49 AM] Info: Any customizations created while running the application will be written to 'C:\Users\10017134\AppData\Roaming\JDeveloper\system11.1.1.6.38.61.92\o.mds.dt\adrs\\AutoGeneratedMar\mds_adrs_writedir'.
    [09:32:49 AM] Wrote Enterprise Application Module to C:\Users\10017134\AppData\Roaming\JDeveloper\system11.1.1.6.38.61.92\o.j2ee\drs
    [09:32:49 AM] Deploying Application...
    <16 Apr 2013 9:32:49 AM> <Error> <Deployer> <BEA-149082> <You cannot deploy application 'j2ee-app' without version. The application was previously deployed with version 'V2.0'.>
    <16 Apr 2013 9:32:49 AM> <Warning> <Deployer> <BEA-149124> <Failures were detected while initiating deploy task for application 'j2ee-app'. Error is: '[Deployer:149082]You cannot deploy application 'j2ee-app' without version. The application was previously deployed with version 'V2.0'.'>
    [09:32:49 AM] ####  Deployment incomplete.  ####
    [09:32:49 AM] Remote deployment failed (oracle.jdevimpl.deploy.common.Jsr88RemoteDeployer)
    #### Cannot run application  due to error deploying to IntegratedWebLogicServer.
    [Application  stopped and undeployed from Server Instance IntegratedWebLogicServer]
    i don't what to delete C:\Users\10017134\AppData\Roaming\JDeveloper\system11.1.1.6.38.61.92\DefaultDomain\servers\DefaultServer\logs\Edited by: adf009 on 2013/04/16 10:45 AM

    Hi,
    Check below link,
    Integrated Weblogic is not running Jdeveloper application
    Nilum.

Maybe you are looking for

  • IPod Mini and iTunes 7

    I have an iPod Mini and I recently downloaded iTunes 7.0.1. For some reason, my podcasts won't import to the podcasts folder on my iPod. Is there any way to work around this, or will I just have to listen to them under songs instead? Dean

  • Does anyone know when Siri location services will work in the UK?

    I really like the iP4S, and perhaps moving to it from a Blackberry. However, one of the key features of the 4S is Siri and the last time I checked, it didn't have the "there is a pizza place within 5 miles from you" type service. I know it's in beta,

  • Problems or Issues in Go Live & Support Phase

    Hello, Can anyone help me with more description in Support Phase................ i have couple of questions. What are the responsibilities in a Support Phase of a Implementation project faced by Support team? What are the common issues / problems to

  • Printer go off when we give command for print

    when ever we give command for print of adobe file it shows printer not attach to computer

  • ComboBox set width problem

    Hey all, Has anyone experienced this, when i give a preferred width to my comboBox, and i use it for the first time, the drop down is still the same size. When the comboBox is again pressed, the dropdown comes with the given size. Please see the link