DMZ Client Deployment failing. Unable to find Management Point

I'm trying to install SCCM 2012 R2 client to a server in our DMZ.  This server is in a workgroup.  I have been following this article
http://nikifoster.wordpress.com/2011/01/31/installing-configmgr-clients-on-servers-in-a-dmz/ however the SCCM agent doesn't seem to be able to find the Management Point, which is on the internal LAN.
Step so far
1) Port 80 and Port 8530 opened on the firewall between the DMZ server and the Primary site server (bi-directionally).
2) Host and LMHost file on the DMZ server updated with the IP address of the Primary site server (where the MP is located).
3)Boundary created on the Primary site server to include the IP address of the DMZ server.
4)Client install files copied locally to the DMZ server.
5)Installed with the following command ccmsetup.exe /MP:servername SMSSITECODE=ABC DNSSUffix=contoso.com
The client installs but does not pick up the correct site code.  On the site tab the settings are blank and I can't manually update them.  In the locationservices.log it looks like it assigns the server to the correct site and then the following
error appears Failed to retrieve DNS service record.... Unable to to find Lookup MP in Registry,AD, DNS and WINS.
I'm not using Certificates.  The DMZ server IP address can be resolved from the Management Point (which is the site server) and the DMZ server will resolve the Management Point address.
Does anyone have any ideas what I've missed?
Thanks in advance

Also note the difference between /mp and SMSMP:
http://blog.configmgrftw.com/ccmsetup-mp-and-smsmp/
Both are required in this case.
Jason | http://blog.configmgrftw.com | @jasonsandys

Similar Messages

  • Error deploy SOA application "Deployment Failed: Unable to register service

    Hi All
    I have build a SOA application and tried to build and deploy to my SOA server but stuck with below error msg.
    Step-1: Created the application, with BPEL components etc.
    Step-2: Right click on the application, then Deploy -> To -> My Server..
    Step-3: SOA build msg
    Buildfile: F:\PF\Oracle\Middleware\jdeveloper\bin\ant-sca-compile.xml
    BUILD SUCCESSFUL
    Total time: 5 seconds
    Step-4: Deployment msg
    +[03:09:24 PM] ---- Deployment started. ----+
    +[03:09:24 PM] Target platform is (Weblogic 10.3).+
    +[03:09:24 PM] Running dependency analysis...+
    +[03:09:24 PM] Building...+
    +[03:09:32 PM] Deploying profile...+
    +[03:09:32 PM] Wrote SAR file to F:\SSID\Oracle_WS\Clawback\CustomerSubscriptionStatusMonitor\deploy\sca_CustomerSubscriptionStatusMonitor_rev1.0.jar+
    +[03:09:32 PM] Deploying sca_CustomerSubscriptionStatusMonitor_rev1.0.jar to soa_server1 [9.184.173.34:8001]+
    +[03:09:32 PM] Processing sar=/F:/SSID/Oracle_WS/Clawback/CustomerSubscriptionStatusMonitor/deploy/sca_CustomerSubscriptionStatusMonitor_rev1.0.jar+
    +[03:09:32 PM] Adding sar file - F:\SSID\Oracle_WS\Clawback\CustomerSubscriptionStatusMonitor\deploy\sca_CustomerSubscriptionStatusMonitor_rev1.0.jar+
    +[03:09:32 PM] Preparing to send HTTP request for deployment+
    +[03:09:33 PM] Creating HTTP connection to host:9.184.173.34, port:8001+
    +[03:09:33 PM] Sending internal deployment descriptor+
    +[03:09:33 PM] Sending archive - sca_CustomerSubscriptionStatusMonitor_rev1.0.jar+
    +[03:09:53 PM] Received HTTP response from the server, response code=500+
    +[03:09:53 PM] Error deploying archive sca_CustomerSubscriptionStatusMonitor_rev1.0.jar to soa_server1 [9.184.173.34:8001]+
    +[03:09:53 PM] HTTP error code returned [500]+
    +[03:09:53 PM] Error message from server:+
    Error during composite deployment: oracle.fabric.common.FabricDeploymentException: oracle.fabric.common.FabricException: Deployment Failed: Unable to register service.: Deployment Failed: Unable to register service..
    +[03:09:53 PM] Check server log for more details.+
    +[03:09:53 PM] #### Deployment incomplete. ####+
    +[03:09:53 PM] Error deploying archive file:/F:/SSID/Oracle_WS/Clawback/CustomerSubscriptionStatusMonitor/deploy/sca_CustomerSubscriptionStatusMonitor_rev1.0.jar+
    +(oracle.tip.tools.ide.fabric.deploy.common.SOARemoteDeployer)+
    Also I have check the http://localhost:8001/soa-infra/ and it says*
    Welcome to the Oracle SOA Platform on WebLogic
    SOA Version: v11.1.1.0.0 - 11.1.1.1.0_090609.1407.5182 built on Tue Jun 09 15:06:41 PDT 2009
    WebLogic Server 10.3.1.0 Wed Jun 10 22:24:41 MDT 2009 1227385 (10.3.1.0)
    There are no composites deployed to the platform
    Edited by: user11263460 on Dec 13, 2009 2:39 AM

    If this still needed. Take a look in Your WSDL file - any references to schemas etc. Are they accessible on server? For example - XSD file have absolute file system link - change it to project level import (copy xsd file to project) or publish to MDS.

  • Deployment Failed: Unable to register service. 11g

    Hi ,
    i am using JDev version 11.1.1.3.0. While deploying a composite i got th efollowing error. can someone please let me know :
    Error during deployment
    oracle.fabric.common.FabricException: Deployment Failed: Unable to register service.
    at oracle.integration.platform.blocks.deploy.StandaloneCompositeDeploymentCoordinatorImpl.coordinateCompositeDeployment(StandaloneCompositeDeploymentCoordinatorImpl.java:37)
    at oracle.integration.platform.blocks.deploy.servlet.BaseDeployProcessor.deployNewComposite(BaseDeployProcessor.java:359)
    at oracle.integration.platform.blocks.deploy.servlet.BaseDeployProcessor.deploySARs(BaseDeployProcessor.java:219)
    at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeployWork(DeployProcessor.java:161)
    at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeployWork(DeployProcessor.java:110)
    at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeploy(DeployProcessor.java:98)
    at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.process(DeployProcessor.java:79)
    at oracle.integration.platform.blocks.deploy.servlet.CompositeDeployerServlet.doPost(CompositeDeployerServlet.java:153)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:821)
    at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
    at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
    at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:27)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
    at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:94)
    at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313)
    at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:414)
    at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:138)
    at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
    at oracle.dms.wls.DMSServletFilter.doFilter(DMSServletFilter.java:330)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.doIt(WebAppServletContext.java:3684)
    at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2268)
    at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2174)
    at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1446)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Caused By: oracle.fabric.common.FabricDeploymentException: Unable to register service. {rootCauses=[]}

    If this still needed. Take a look in Your WSDL file - any references to schemas etc. Are they accessible on server? For example - XSD file have absolute file system link - change it to project level import (copy xsd file to project) or publish to MDS.

  • Unable to deploy EJB: unable to find EndPointFinder

    Hello.
    We are in a process of migrating applications from WL7 SP7 to WL 10.3
    JDK 1.4 to JDK 1.6
    EJB 2.1 remains same.
    When we try to connect to a third-party (SONIC) secured JMS infrastructure Topic. I have configured the credential mapper for that.
    When I deployed application in WL 10.3 I got following error
    Unable to deploy EJB: TLDBanMoveMDB from tbstotld.jar:
    unable to find EndPointFinder for ldap://emldev01.sbc.com:4299/t=jms,ou=2_0,ou=dst01,ou=telegence,ou=ld,o=billing'
    weblogic.application.ModuleException: Exception activating module: EJBModule(tbstotld.jar)
    Unable to deploy EJB: TLDBanMoveMDB from tbstotld.jar:
    unable to find EndPointFinder for ldap://emldev01.sbc.com:4299/t=jms,ou=2_0,ou=dst01,ou=telegence,ou=ld,o=billing
    at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:493)
    at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:107)
    at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:411)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
    at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:74)
    at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:66)
    at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
    at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
    at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:16)
    at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:162)
    at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:140)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:106)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
    Following is my deployment descriptor.
    <weblogic-enterprise-bean>
    <ejb-name>TLDBanMoveMDB</ejb-name>
    <message-driven-descriptor>
    <pool>
    <max-beans-in-free-pool>30</max-beans-in-free-pool>
    <initial-beans-in-free-pool>1</initial-beans-in-free-pool>
    </pool>
    <destination-jndi-name>cn=tldNotify</destination-jndi-name>
    <initial-context-factory>com.sun.jndi.ldap.LdapCtxFactory</initial-context-factory>
    <provider-url>ldap://emldev01.sbc.com:4299/t=jms,ou=2_0,ou=dst01,ou=telegence,ou=ld,o=billing</provider-url>
    <connection-factory-jndi-name>cn=embdev01TCF</connection-factory-jndi-name>
    <jms-client-id>M20413</jms-client-id>
    </message-driven-descriptor>
    </weblogic-enterprise-bean>
    I did some research and learned that Weblogic seems to confuse as to which initial context factory to use. See the posts as linked in here. Is this a bug in Weblogic?
    http://forums.oracle.com/forums/thread.jspa?threadID=873769
    http://objectmix.com/weblogic/537901-unable-find-endpointfinder.html
    Some folks are recommending using weblogic.ejbcgen, but all I have is deployment descriptors and not sure how do I handle this.
    If I create a foreign jndi provider, how do I replace the details in my weblogic-ejb-jar.xml?
    Please help.
    Thanks
    Hari.
    Edited by: rihem09 on Nov 10, 2009 6:55 PM

    Check out this page.
    http://objectmix.com/weblogic/537901-unable-find-endpointfinder.html
    글 수정: user6407983

  • Time Machine restore fail: "Unable to find Driver for platform ACPI"

    After restoring a recent Time Machine backup of a 2010 MacBook Pro Snow Leopard system, I'm getting boot errors like
    panic(cpu 0 caller 0x5591cb: "Unable to find driver for this platform: \"ACPI\".\n"@/SourceCache/xnu/xnu-1504.7.4/iokit/Kernal/IOPlatformExpert.cpp:1389
    Dbugger called <panic>
    Backtrace (CPU 0), Freame : Return Address (4 potential args on stack)
    I'm re-installing using the Utilities menu on they grey (Snow Leopard) system DVD that came with the MacBook Pro I'm trying to restore. I'm definitely not using a Leopard DVD, which is something I know can cause problems.
    I've managed to restore from a non-Time Machine clone of my drive, but I now no longer trust my Time Machine backups. They are fine for restoring the odd user file, but seem to be broken or missing something crucial that means that my Time Machine backup is useless for restoring an entire system, which is something it should be capable of.
    Am I missing something obvious? Any suggestions?

    Hi Linc, thanks for your reply!
    In case I wasn't clear, I'm not reinstalling after restoring, or reinstalling the OS.
    Restoring my system from TM leaves me with an unusable system that kernel panics immediately on boot. My workaround is just to ignore TM and restore from a different kind of backup (a clone made with SuperDuper, as it happens).
    I think it would be a bit generous to Time Machine to call this a "workaround"! Time Machine doesn't work for me.
    Has anyone ever solved the problem of full restores of their TM backup leaving them with a system that has this problem?

  • Client check failed - how to find the details

    system: sccm 2012 r2.
    Noticed there are quite a number of clients in the status/result as: client check failed
    where and how can I find the details as why/what causes the failure?
    Thanks in advance

    Hi,
    On the clients you can review the CCMEVAL.log file, you can also check out the two reports "Client remediation summary" and "Client remediation details"
    Regards,
    Jörgen
    -- My System Center blog ccmexec.com -- Twitter
    @ccmexec

  • Client Install Fails - Unable to get Win32_OperatingSystem object

    I have a PC that won't install the SCCM client via Client Push.  In the CCM.Log file on the site server, it connects to the IPC$ and admin$ shares using my client installation account, but then it comes back with this error:
    ---> Unable to get Win32_OperatingSystem object from WMI on remote machine "PCNAME", error = 0x80080005.
    I know that error means that access was denied to WMI, and I verified that when I run wbemtest manually (using the same client installation account), I can connect to the root\cimv2 object on that PC but when I try to enumerate the instances of the Win32_OperatingSystem object, I get the same error.
    I also tried using Computer Management applet (remotely - I have no local access to this PC) to look at the WMI Control properties.  Again, I get the same access denied error so I can't check/change the security permissions that way.
    I have verified that my client installation account is in the local Administrators group of the PC.  I've already tried rebuilding the WMI repository - that worked but it didn't fix the access issue.  I know I can install the client manually but I'm guessing I'd still have a problem with inventories, etc. that are dependent on access to that WMI object.  Any suggestions about how to go about fixing the WMI access issue?
    Thanks so much, --Jo

    Finally getting back to this issue after vacaton... sigh.
    I got a little further.  I took client push out of the mix and ran ccmsetup.exe locally on the PC.  This time the client installation ran.  However, I'm still getting a similar error from the client itself and the client is not talking to the site.  After the client was installed, only about 10 of the log files showed up in system32\ccm\logs. 
    ccmexec.log shows this error: 
    Endpoint'PolicyAgent_PolicyEvaluator' return 0x80070057 from event notification
    PolicyAgentProvider.log has these lines repeating:
    Failed to create actual config class for 'CCM_RootCACertificates' 
    Failed to update namespace 'Machine' (80041002) 
    Successfully updated namespace 'DefaultMachine' 
    Successfully updated namespace 'DefaultUser' 
    Failed to create actual config class for 'CCM_MulticastConfig' 
    Failed to update namespace 'Machine' (80041002) 
    PolicyEvaluator.log has this error:
    Received notification that Local policy has changed. 
    Failed to trigger Machine settings update (80070057)
    SrcUpdateManager has these errors:
    Instance of CCM_SourceUpdateClientConfig doesn't exist in WMI
    Failed to get instance of CCM_SourceUpdateHistory, error 80041002
    ClientIDManagerStartup.log has these errors:
    GetSystemEnclosureInfo failed (0x80080005)
    ComputeHardwareID failed (0x80080005).
    RegTask: Failed to create registration request body. Error: 0x80080005
    The rest of the logs that exist (LocationServices, StatusAgent, ClientLocation, RemCtrl, and setuppolicyevaluator) appear to be OK. 
    These seem to all be WMI-related errors/issues, but I can't find any specific information on any SCCM/SMS websites/forums that address these particular errors in these particular log files.  I've tried rebuilding the repository (several times), I've done the regsvr stuff as discussed above, etc. 
    I ran WMIDIAG next.  It ran for a little less than two hours - not sure if that's normal or not, but the log file continued to update the entire time.  Now I have this log file and I'm not sure what to do with the issues I found.  I'm looking at the WMI REPORT: BEGIN section...  I see instructions that make sense for most of the errors.  However, the section of log file below shows the area that is most likely causing issues for SCCM because it is the same error I get on the client install.  I have no idea how to fix this stuff - any help would be appreciated:
    31997 14:20:05 (1) !! ERROR: WMI ENUMERATION operation errors reported: .......................................... 33 ERROR(S)!
    31998 14:20:05 (0) ** - ROOT/CIMV2, InstancesOfAsync, CIM_USBDevice, 0x80080005 - .
    31999 14:20:05 (0) ** - ROOT/CIMV2, InstancesOfAsync, CIM_USBHub, 0x80080005 - .
    32000 14:20:05 (0) ** - ROOT/CIMV2/SMS, InstancesOfAsync, SMS_Class_Template, 0x80041011 - (WBEM_E_PROVIDER_NOT_FOUND) Provider referenced in the schema does not have a corresponding registration.
    32001 14:20:05 (0) ** - Root/Default, InstancesOf, SystemRestore, 0x80080005 - Server execution failed.
    32002 14:20:05 (0) ** - Root/CIMv2, InstancesOf, Win32_Process, 0x80080005 - Server execution failed.
    32003 14:20:05 (0) ** - Root/CIMv2, InstancesOf, Win32_OperatingSystem, 0x80080005 - Server execution failed.
    32004 14:20:05 (0) ** - Root/CIMv2, InstancesOf, Win32_ComputerSystem, 0x80080005 - Server execution failed.
    32005 14:20:05 (0) ** - Root/CIMv2, InstancesOf, Win32_Service, 0x80041013 - (WBEM_E_PROVIDER_LOAD_FAILURE) COM cannot locate a provider referenced in the schema.
    32006 14:20:05 (0) ** - Root/CIMv2, InstancesOf, Win32_Bios, 0x80080005 - Server execution failed.
    32007 14:20:05 (0) ** - Root/CIMv2, InstancesOf, Win32_PerfRawData_Tcpip_IP, 0x80080005 - Server execution failed.
    32008 14:20:05 (0) ** - Root/CIMv2, InstancesOf, Win32_PerfRawData_Tcpip_TCP, 0x80080005 - Server execution failed.
    32009 14:20:05 (0) ** - Root/CIMv2, InstancesOf, Win32_PerfRawData_Tcpip_UDP, 0x80080005 - Server execution failed.
    32010 14:20:05 (0) ** - Root/CIMv2, InstancesOf, Win32_PerfRawData_Tcpip_ICMP, 0x80080005 - Server execution failed.
    32011 14:20:05 (0) ** - Root/CIMv2, InstancesOf, Win32_PerfRawData_PerfOS_Cache, 0x80080005 - Server execution failed.
    32012 14:20:05 (0) ** - Root/CIMv2, InstancesOf, Win32_PerfRawData_PerfOS_Memory, 0x80041013 - (WBEM_E_PROVIDER_LOAD_FAILURE) COM cannot locate a provider referenced in the schema.
    32013 14:20:05 (0) ** - Root/CIMv2, InstancesOf, Win32_PerfRawData_PerfOS_Objects, 0x80080005 - Server execution failed.
    32014 14:20:05 (0) ** - Root/CIMv2, InstancesOf, Win32_PerfRawData_PerfOS_PagingFile, 0x80080005 - Server execution failed.
    32015 14:20:05 (0) ** - Root/CIMv2, InstancesOf, Win32_PerfRawData_PerfOS_Processor, 0x80080005 - Server execution failed.
    32016 14:20:05 (0) ** - Root/CIMv2, InstancesOf, Win32_PerfRawData_PerfOS_System, 0x80080005 - Server execution failed.
    32017 14:20:05 (0) ** - Root/CIMv2, InstancesOf, Win32_PerfRawData_PerfProc_Process, 0x80080005 - Server execution failed.
    32018 14:20:05 (0) ** - Root/CIMv2, InstancesOf, Win32_PerfRawData_PerfProc_Thread, 0x80080005 - Server execution failed.
    32019 14:20:05 (0) ** - Root/CIMv2, InstancesOf, Win32_PerfFormattedData_Tcpip_IP, 0x80080005 - Server execution failed.
    32020 14:20:05 (0) ** - Root/CIMv2, InstancesOf, Win32_PerfFormattedData_Tcpip_TCP, 0x80080005 - Server execution failed.
    32021 14:20:05 (0) ** - Root/CIMv2, InstancesOf, Win32_PerfFormattedData_Tcpip_UDP, 0x80080005 - Server execution failed.
    32022 14:20:05 (0) ** - Root/CIMv2, InstancesOf, Win32_PerfFormattedData_Tcpip_ICMP, 0x80041013 - (WBEM_E_PROVIDER_LOAD_FAILURE) COM cannot locate a provider referenced in the schema.
    32023 14:20:05 (0) ** - Root/CIMv2, InstancesOf, Win32_PerfFormattedData_PerfOS_Cache, 0x80080005 - Server execution failed.
    32024 14:20:05 (0) ** - Root/CIMv2, InstancesOf, Win32_PerfFormattedData_PerfOS_Memory, 0x80080005 - Server execution failed.
    32025 14:20:05 (0) ** - Root/CIMv2, InstancesOf, Win32_PerfFormattedData_PerfOS_Objects, 0x80080005 - Server execution failed.
    32026 14:20:05 (0) ** - Root/CIMv2, InstancesOf, Win32_PerfFormattedData_PerfOS_PagingFile, 0x80080005 - Server execution failed.
    32027 14:20:05 (0) ** - Root/CIMv2, InstancesOf, Win32_PerfFormattedData_PerfOS_Processor, 0x80080005 - Server execution failed.
    32028 14:20:05 (0) ** - Root/CIMv2, InstancesOf, Win32_PerfFormattedData_PerfOS_System, 0x80080005 - Server execution failed.
    32029 14:20:05 (0) ** - Root/CIMv2, InstancesOf, Win32_PerfFormattedData_PerfProc_Process, 0x80080005 - Server execution failed.
    32030 14:20:05 (0) ** - Root/CIMv2, InstancesOf, Win32_PerfFormattedData_PerfProc_Thread, 0x80080005 - Server execution failed.
    32031 14:20:05 (0) **
    32032 14:20:05 (1) !! ERROR: WMI EXECQUERY operation errors reported: ............................................ 17 ERROR(S)!
    32033 14:20:05 (0) ** - Root/Default, SELECT * FROM SystemRestore, 0x80080005 - Server execution failed.
    32034 14:20:05 (0) ** - Root/CIMv2, SELECT * FROM Win32_LogicalDisk WHERE FreeSpace > 10000000 AND DriveType = 3, 0x80080005 - Server execution failed.
    32035 14:20:05 (0) ** - Root/CIMv2, SELECT * FROM Win32_PageFileUsage, 0x80041013 - (WBEM_E_PROVIDER_LOAD_FAILURE) COM cannot locate a provider referenced in the schema.
    32036 14:20:05 (0) ** - Root/CIMv2, SELECT * FROM Win32_BIOS WHERE Version IS NOT NULL, 0x80080005 - Server execution failed.
    32037 14:20:05 (0) ** - Root/CIMv2, SELECT * FROM Win32_NetworkAdapter WHERE AdapterType IS NOT NULL AND AdapterType != "Wide Area Network (WAN)" AND Description != "Packet Scheduler Miniport", 0x80041013 - (WBEM_E_PROVIDER_LOAD_FAILURE) COM cannot locate a provider referenced in the schema.
    32038 14:20:05 (0) ** - Root/CIMv2, SELECT * FROM Win32_Processor WHERE Name IS NOT NULL, 0x80080005 - Server execution failed.
    32039 14:20:05 (0) ** - Root/CIMv2, SELECT * FROM Win32_DiskDrive, 0x80041013 - (WBEM_E_PROVIDER_LOAD_FAILURE) COM cannot locate a provider referenced in the schema.
    32040 14:20:05 (0) ** - Root/CIMv2, SELECT * FROM Win32_ComputerSystem, 0x80080005 - Server execution failed.
    32041 14:20:05 (0) ** - Root/CIMv2, SELECT * FROM Win32_DiskPartition, 0x80041013 - (WBEM_E_PROVIDER_LOAD_FAILURE) COM cannot locate a provider referenced in the schema.
    32042 14:20:05 (0) ** - Root/CIMv2, SELECT * FROM Win32_LogicalDisk WHERE Description != "Network Connection", 0x80080005 - Server execution failed.
    32043 14:20:05 (0) ** - Root/CIMv2, SELECT * FROM Win32_SoundDevice, 0x80041013 - (WBEM_E_PROVIDER_LOAD_FAILURE) COM cannot locate a provider referenced in the schema.
    32044 14:20:05 (0) ** - Root/CIMv2, SELECT * FROM Win32_VideoController, 0x80080005 - Server execution failed.
    32045 14:20:05 (0) ** - Root/CIMv2, SELECT * FROM Win32_USBController, 0x80041013 - (WBEM_E_PROVIDER_LOAD_FAILURE) COM cannot locate a provider referenced in the schema.
    32046 14:20:05 (0) ** - Root/CIMv2, SELECT * FROM Win32_DesktopMonitor, 0x80080005 - Server execution failed.
    32047 14:20:05 (0) ** - Root/CIMv2, SELECT * FROM Win32_PointingDevice WHERE Status = "OK", 0x80041013 - (WBEM_E_PROVIDER_LOAD_FAILURE) COM cannot locate a provider referenced in the schema.
    32048 14:20:05 (0) ** - Root/CIMv2, SELECT * FROM Win32_Keyboard, 0x80080005 - Server execution failed.
    32049 14:20:05 (0) ** - Root/CIMv2, SELECT * FROM Win32_SystemDriver WHERE StartMode != "Disabled", 0x80041013 - (WBEM_E_PROVIDER_LOAD_FAILURE) COM cannot locate a provider referenced in the schema.
    32050 14:20:05 (0) **
    32051 14:20:05 (0) ** WMI PUT operations: ........................................................................ OK.
    32052 14:20:05 (0) ** WMI DELETE operations: ..................................................................... OK.
    32053 14:20:05 (0) ** WMI GET VALUE operations: .................................................................. OK.
    32054 14:20:05 (0) ** WMI static instances retrieved: ............................................................ 1541.
    32055 14:20:05 (0) ** WMI dynamic instances retrieved: ........................................................... 0.
    32056 14:20:05 (0) ** WMI instances request cancellations (to limit performance impact): ......................... 0.
    32057 14:20:05 (0) **
    32058 14:20:05 (0) ** 38 error(s) 0x80080005 - (WBEM_UNKNOWN) This error code is external to WMI.
    32059 14:20:05 (0) **
    32060 14:20:05 (0) ** 1 error(s) 0x80041011 - (WBEM_E_PROVIDER_NOT_FOUND) Provider referenced in the schema does not have a corresponding registration
    32061 14:20:05 (0) ** => This error is typically due to the following major reasons:
    32062 14:20:05 (0) **    - The application queried by the WMI provider is not installed, not available or not running
    32063 14:20:05 (0) **      at the time of the request was made. This error can also be generated because
    32064 14:20:05 (0) **      the application supporting the providers has been uninstalled.
    32065 14:20:05 (0) **    - The WMI provider binary files are not accessible (e.g. access denied ACL).
    32066 14:20:05 (0) **    - A WMI provider registration problem at the CIM level (MOFCOMP.EXE) or at the COM level (REGSVR32.EXE).
    32067 14:20:05 (0) **      You must re-register the WMI provider by recompiling its associated MOF file with MOFCOMP.EXE
    32068 14:20:05 (0) **    Note: - If the WMI provider DLL CIM and COM registrations are correct, this error can
    32069 14:20:05 (0) **            be returned because the provider has a dependency on another DLL that cannot be
    32070 14:20:05 (0) **            loaded (missing or bad DLL)
    32071 14:20:05 (0) **          - Dependencies can be found with the DEPENDS.EXE tool coming with the
    32072 14:20:05 (0) **            Windows XP and Windows 2003 Support Tools. The command line is as follows:
    32073 14:20:05 (0) **            e.g. DEPENDS.EXE <PATH><Provider.DLL>
    32074 14:20:05 (0) ** => If the software has been de-installed intentionally, then this information must be
    32075 14:20:05 (0) **    removed from the WMI repository. You can use the 'WMIC.EXE' command to remove the provider
    32076 14:20:05 (0) **    registration data and its set of associated classes.
    32077 14:20:05 (0) ** => To correct this situation, you can:
    32078 14:20:05 (0) **    - Install or start the application supporting these providers.
    32079 14:20:05 (0) **    - Register the providers in CIM (MOFCOMP) or DCOM (REGSVR32).
    32080 14:20:05 (0) **    Note: In this case the provider should also be listed in the 'missing WMI
    32081 14:20:05 (0) **          provider DCOM registrations' or in the 'missing WMI provider files' section.
    32082 14:20:05 (2) !! WARNING: Re-registering with REGSVR32.EXE all DLL from 'C:\WINDOWS\SYSTEM32\WBEM\'
    32083 14:20:05 (0) **          may not solve the problem as the DLL supporting the WMI class(es)
    32084 14:20:05 (0) **          can be located in a different folder.
    32085 14:20:05 (0) **          You must refer to the class name to determine the software delivering the related DLL.
    32086 14:20:05 (0) **
    Thanks, --Jo

  • Trying to export security, ExportSecurity.cmd fails , unable to find class

    Our Version is hyperion planning 9.3.1
    When I run ExportSecurity.cmd it fails complaining it cannot find class HspExportSecurityCmd
    When i look in HspJS.jar i dont see that HspExportSecurityCmd class. does anyone know what jar file that class is in so I can get this working?

    Hi,
    com.hyperion.planning.utils.HspExportSecurityCmd class is indeed part of the HspJS.jar file. Ensure your cmd file used to call the utility explicitly puts the HspJS.jar on the classpath, and that it is actually pointing to a place where the jar file exists.
    regards,
    Robb Salzmann

  • Unable to find managed files in Aperture 3

    Hi there,
    I have consildated the master files by copy them into the aperture library. The problem is that now aperture is now able to locate any of the master files. I tried to use the option of relocating the master file but it was impossible since the files are stored into the aperture library.
    Any suggestions/ideas/ tricks will be really appreciated.
    Cheers

    We need clearer information in order to help out.
    FEGD wrote:
    Hi there,
    I have consildated the master files by copy them into the aperture library.
    This was done from within Aperture via "File→Consolidate Master ... "?
    The problem is that now aperture is now able to locate any of the master files.
    This seems to be a typo. Should it be " ... is that now aperture is not able to ... "?
    What are the symptoms?
    I tried to use the option of relocating the master file but it was impossible since the files are stored into the aperture library.
    "File→Relocate Master" should work with both Managed Masters and Referenced Masters.
    Any suggestions/ideas/ tricks will be really appreciated.
    The usual trouble-shooting steps are recommended: reboot, repair Library, re-build Library.

  • WRT54GS "Upgrade are failed" - unable to find solution

    I noticed other people are having this problem, but I still haven't found a solution for it.
    The label on my router says "WRT54GS" and the current firmware is 4.71.4. Can anybody point me to the proper file?
    Thanks!

    What is the version number of your router?
    http://homesupport.cisco.com/en-us/support/routers/WRT54GS

  • Unable to find a WSDL that has a definition for service

    Dear all
    I have a very simple composite applicationexposing a web service. When I deploy the application I get:
    There was an error deploying the composite on soa_server1: Deployment Failed: Unable to find a WSDL that has a definition for service {http://soa/sf/login}bpelprocess1_client_ep and port loginPort_pt. Please make sure that the port attribute for the binding defined in the composite file is correct by checking the namespace, service name, and port name. In addition, check that the WSDL associated with the binding namespace is imported and currently reachable (check the import nodes at the top of the composite file). Finally, validate the HTTP proxy settings for the server.
    However the build process shows no errors. The entire application was built using Jdeveloper 11.1.1.5 using a pre-constructed WSDL. The SOA suite is 11.1.1.5
    Any pointers will be really appreciated.
    Thanks
    The composite is this:
    <?xml version="1.0" encoding="UTF-8" ?>
    <!-- Generated by Oracle SOA Modeler version 1.0 at [2/28/13 2:25 PM]. -->
    <composite name="SOA2" revision="1.0" label="2013-02-28_14-25-14_553"
    mode="active" state="on" xmlns="http://xmlns.oracle.com/sca/1.0"
    xmlns:xs="http://www.w3.org/2001/XMLSchema"
    xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy"
    xmlns:orawsp="http://schemas.oracle.com/ws/2006/01/policy"
    xmlns:ui="http://xmlns.oracle.com/soa/designer/">
    <import namespace="http://soa/sf/login" location="loginToSFDC.wsdl"
    importType="wsdl"/>
    <service name="bpelprocess1_client_ep" ui:wsdlLocation="loginToSFDC.wsdl">
    <interface.wsdl interface="http://soa/sf/login#wsdl.interface(loginPort)"/>
    <binding.ws port="http://soa/sf/login#wsdl.endpoint(bpelprocess1_client_ep/loginPort_pt)"/>
    </service>
    <component name="BPELProcess1" version="2.0">
    <implementation.bpel src="BPELProcess1.bpel"/>
    <property name="bpel.config.transaction" type="xs:string" many="false">required</property>
    </component>
    <wire>
    <source.uri>bpelprocess1_client_ep</source.uri>
    <target.uri>BPELProcess1/bpelprocess1_client</target.uri>
    </wire>
    </composite>
    The WSDL used to generate the BPEL is:
    <?xml version= '1.0' encoding= 'UTF-8' ?>
    <definitions
    targetNamespace="http://soa/sf/login"
    xmlns="http://schemas.xmlsoap.org/wsdl/"
    xmlns:tns1="http://soa/sf/login"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:flt="urn:fault.partner.soap.sforce.com"
    xmlns:obj="urn:sobject.partner.soap.sforce.com"
    xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
    xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
    xmlns:typ="urn:partner.soap.sforce.com"
    xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
    >
    <types>
    <xsd:schema targetNamespace="http://uk.gov.fca.sf/login" elementFormDefault="qualified" xmlns:tns1="http://uk.gov.fca.sf/login"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:flt="urn:fault.partner.soap.sforce.com"
    xmlns:obj="urn:sobject.partner.soap.sforce.com" xmlns:typ="urn:partner.soap.sforce.com"
    xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
    xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/">
    <xsd:import namespace="urn:partner.soap.sforce.com" schemaLocation="xsd/partner_types.xsd"/>
    <xsd:import namespace="urn:fault.partner.soap.sforce.com" schemaLocation="xsd/partner_faults.xsd"/>
    <xsd:import namespace="urn:sobject.partner.soap.sforce.com" schemaLocation="xsd/partner_objects.xsd"/>
    </xsd:schema>
    </types>
    <message name="loginInMessage">
    <part name="loginIn" element="typ:login"/>
    <part name="LoginScopeHeaderIn" element="typ:LoginScopeHeader"/>
    <part name="CallOptionsIn" element="typ:CallOptions"/>
    </message>
    <message name="loginOutMessage">
    <part name="return" element="typ:loginResponse"/>
    </message>
    <portType name="loginPort">
    <operation name="loginOp">
    <input message="tns1:loginInMessage"/>
    <output message="tns1:loginOutMessage"/>
    </operation>
    </portType>
    <binding name="loginPortSOAP11Binding" type="tns1:loginPort">
    <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
    <operation name="loginOp">
    <soap:operation style="document" soapAction="http://soa:8101/login/loginOp"/>
    <input>
    <soap:body use="literal" parts="in"/>
    </input>
    <output>
    <soap:body use="literal" parts="return"/>
    </output>
    </operation>
    </binding>
    <binding name="loginPortSOAP12Binding" type="tns1:loginPort">
    <soap12:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
    <operation name="loginOp">
    <soap12:operation style="document" soapAction="http://uk.gov.fca.sf:7101/login/loginOp" soapActionRequired="false"/>
    <input>
    <soap12:body use="literal" parts="in"/>
    </input>
    <output>
    <soap12:body use="literal" parts="return"/>
    </output>
    </operation>
    </binding>
    <service name="loginSrvc">
    <port name="login_port_11" binding="tns1:loginPortSOAP11Binding">
    </port>
    <port name="login_port_12" binding="tns1:loginPortSOAP12Binding">
    </port>
    </service>
    <partnerLinkType name="ProviderRole"
    xmlns="http://schemas.xmlsoap.org/ws/2003/05/partner-link/">
    <role name="Role1">
    <portType name="tns1:loginPort"/>
    </role>
    </partnerLinkType>
    </definitions>

    Hi,
    I don't see a loginPort_pt port in the wsdl, but it is referenced by the composite...
    There's only ports login_port_11 and login_port_12 defined...
    Cheers,
    Vlad

  • Deployment Failed of Fusion Order11g Composite

    hi all ,
    I am getting this error while deploying the composites individually ..can someone help?
    Error during deployment: Deployment Failed: Unable to find a WSDL that has a definition for service {www.globalcompany.example.com}StoreFrontService and port StoreFrontServiceSoapHttpPort. Please make sure that the port attribute for the binding defined in the composite file is correct by checking the namespace, service name, and port name. In addition, check that the WSDL associated with the binding namespace is imported and currently reachable (check the import nodes at the top of the composite file). Finally, validate the HTTP proxy settings for the server..
    Edited by: AndyC1 on Apr 18, 2010 11:28 PM

    Its Unable to find your WSDL file, is this on the same machine??
    also, check the configuration of your machine,
    Intel Core 2 duo processor+4GB RAM is best for 11G
    I had issues when I was having machine with AMD processor
    Yatan

  • Manage SCCM 2012 clients in DMZ (OS Deploy, Windows updates) via DP/MP

    Hi,
    We ’d like to manage (=OS Deploy, Packages,Windows updates) Windows clients (Windows 2008/2012 R2 servers for now, about 20 of them) in a DMZ (= different domain).
    There is this article
    https://nikifoster.wordpress.com/2011/01/31/installing-configmgr-clients-on-servers-in-a-dmz/ which explains what to do … in 2011. Since then lots of things are changed I guess
    Before I dive in, I’d need to have an overview + do some administrative tasks (like asking for firewall accesses).
    Current setup DMZ:
    Our SCCM 2012 R2 server is on a Windows 2008 R2 OS
    Client communication is done via HTTP (not HTTPS)
    An extra physical Distribution point is setup (only DP, nothing more) in our current domain
    A new Windows 2012 server is setup in the DMZ which should host the DP and probably management point (since it should manage the clients over there)
    There are clients in DMZ that are currenlty managed by SCCM 2007 but 
    this server will be phased out, these client have:
    Correct sccm functionality
    Correct DNS resolution
    My steps/questions, please comment:
    Add the DMZ ip range to SCCM 2012 boundary as “DMZ”
    Add the network access account to be able to deploy as well clients as distribution point in DMZ
    In the DMZ accesses on firewall for server VLAN have to be asked
    When we have a distribution point and communication is “HTTP only” then http (port 80) from DMZ to sccm server should suffice, correct? Or are
     extra firewall openings needed for management point access/packages and windows updates sync?
    Now the sccm clients will be deployed to the servers in DMZ: deploy SCCM clients to hosts in DMZ, how this should be done: we connect a console to the SCCM-server in the DMZ then deploy the discovered clients?
    OS Deploy should be made available, but no dhcp is available in DMZ and it is not an option either, therefore we would boot from an ISO then enter an ip (or pre-enter it so there is already filled in an ip?). So tasksequences/deployments
    for servers in DMZ, where are they configured/deployed then? Via console access on DMZ management point or can we deploy on our domain SCCM management point (not in DMZ) and it will be synced to the DMZ management point? Not clear
    Selective sync of software to this distribution point (howto? not sure), we don’t need any Windows 8 software/drivers to be synced.
    Thanks for your input!
    J.
    Jan Hoedt

    No comment;
    I think you mean the client push installation account and the site system installation account;
    More ports are required, see site server > distribution point and distribution point > management point from the provided link;
    The console will always be connected to your primary site server. The client will be pushed from the primary site server and it will provide the initial files. The other files will be downloaded from the local distribution point;
    The task sequence deployment will be just like a normal taks sequence deployment. The only difference is the location of the server;
    Only the content that's distributed to the distribution point in the DMZ will be available on that distribution point.
    My Blog: http://www.petervanderwoude.nl/
    Follow me on twitter: pvanderwoude

  • Management point location for workgroup clients in DMZ

    Hi All,
    I am trying to install the SCCM 2012 client to some servers that are located in a workgroup and in a DMZ at our organization.
    I have read up about the config for this and I think that we have everything in place but the clients themselves are not locating a management point which I think is due to the setup of the IIS on the management points.
    Firstly, I ammended the local hosts file on the system to ensure that the server could resolve the SCCM site server and 2 management points by using NetBIOS and FQDN. I also checked that the ports are opened from the client to the
    management point.
    I then ran ccmsetup using the following switches /noservice /mp=smsmp SMSSITECODE=XXX SMSSLP=SMSMP FSP=SMSSITESERVER CCMHTTPPORT=24555 CCMHTTPSPORT=24556 RESETKEYINFORMATION=TRUE which appers to have sucessfully installed the client
    but is now failing to communicate with the MP specified. I am seeing on the client the following repeated in the locationservices.log
    <![LOG[Raising event:
    instance of CCM_CcmHttp_Status
                DateTime = "20141127153834.775000+000";
                HostName = "SMSMP";
                HRESULT = "0x87d0027e";
                ProcessID = 4004;
                StatusCode = 401;
                ThreadID = 5184;
    ]LOG]!><time="15:38:34.775+00" date="11-27-2014" component="LocationServices" context="" type="1" thread="5184" file="event.cpp:715">
    <![LOG[Successfully sent location services HTTP failure message.]LOG]!><time="15:38:34.962+00" date="11-27-2014" component="LocationServices" context="" type="1" thread="5184"
    file="ccmhttperror.cpp:396">
    <![LOG[Error sending HEAD request. HTTP code 401, status 'Unauthorized']LOG]!><time="15:38:34.962+00" date="11-27-2014" component="LocationServices" context="" type="3"
    thread="5184" file="util.cpp:2568">
    <![LOG[Workgroup client is in Unknown location]LOG]!><time="15:38:34.962+00" date="11-27-2014" component="LocationServices" context="" type="1" thread="5184"
    file="lsad.cpp:1078">
    <![LOG[[CCMHTTP] ERROR: URL=http://SMSMP, Port=24555, Options=224, Code=0, Text=CCM_E_BAD_HTTP_STATUS_CODE]LOG]!><time="15:38:34.993+00" date="11-27-2014"
    component="LocationServices" context="" type="1" thread="5184" file="ccmhttperror.cpp:297">
    And on the management point I am seeing the following repeated in the IIS logs
    x.x.x.x HEAD / - 24555 - x.x.x.x SMS+CCM+5.0 - 401 2 5 216 0
    I understand that this points to the IIS authentication issue so I have tried browsing to http://smsmp.domainname.com/sms_mp/.sms_aut?mplist and
    I do get a list of management points returned so I'm a little confused now. The other thing that confuses me is that we also have another domain we manage clients
    in and these systems have all registered with the MP fine even though there is no trust relationship in place between the 2 domains.
    I have checked anonymous authentication has been enabled on the SMS_MP virtual directory but I can see that it is set to use a user account of IUSR, but this is not a local user on the MP nor an AD user from what I can see.
    Is anybody able to point me in the correct direction of either what I am doing wrong or which settings I should be checking?
    Thanks in advance for any help
    Andrew

    You mention in your ccmsetup install properties: CCMHTTPPORT=24555 CCMHTTPSPORT=24556
    While the MPList test you provided shows:
    http://smsmp.domainname.com/sms_mp/.sms_aut?mplist
    This is on port 80
    Where is your MP? Port 80 or 24555 ?

  • NW 7.2 CE EAR deploy error: Unable to extract ws clients deployment data

    Hi,
        I am attempting to deploy an extremely simple Enterprise application from Developer Studio. I creates a new enterprise app then created a new dynamic web project as associated it with the EAR. I then placed a single JSP containing only static content within the web app. When I attempt to deploy (either through the server view, as a workspace deployable archive in deploy view or after exporting the EAR and deploying as an eternal archive in deploy view) I receive the following error and the deployment fails. I am not trying to do anything with web services or web service clients. After a fresh reinstall deployment works for a short while then the error begins occurring again. Creating a new workspace and recreating the project caused no change.
       Any help, tips or things to try would be greatly appreciated.

    --- Deploying file(s):
         C:\SAP_Workspace_72_b\TestEarB\TestEarB.ear
    --- Status:
         Deploy Exception.
    --- Description:
                S U M M A R Y
    ~~~~~~~~~~~~~~~~~~~
    Successfully deployed:           0
    Deployed with warnings:           0
    Failed deployments:                1
    ~~~~~~~~~~~~~~~~~~~
    ASJ.dpl_dc.001085 An error occurred while deploying the deployment item [sap.com_TestEarB].
    ; nested exception is:
         com.sap.engine.services.dc.gd.DeliveryException: [ERROR CODE DPL.DC.3298] An error occurred during deployment of [sap.com_TestEarB]. Cannot deploy it.
    1. File:C:\SAP_Workspace_72_b\TestEarB\TestEarB.ear
         Name:TestEarB
         Vendor:sap.com
         Location:localhost
         Version:2010.08.12.09.23.12
         Deploy status:Aborted
         Version:NEW
         Description:
              1. Exception occurred during ws clients deployment. Unable to extract ws clients deployment data for archive TestWeb.war, application sap.com/TestEarB.
               -> Unsupported Source object.
              2. [ASJ.dpl_dc.006005] The reason for nested issue could be concurrency one in components involved in exception stack trace.
    Hint: 1) Search in [std_server.out] file in work dir for message [Possible concurrency issue related to item [sap.com_TestEarB].] or thread dumps.
    --- Exception:
    com.sap.engine.services.dc.api.deploy.DeployException: [ERROR CODE DPL.DCAPI.1027] DeploymentException.
    Reason: ASJ.dpl_dc.001085 An error occurred while deploying the deployment item [sap.com_TestEarB].
    ; nested exception is:
         com.sap.engine.services.dc.gd.DeliveryException: [ERROR CODE DPL.DC.3298] An error occurred during deployment of [sap.com_TestEarB]. Cannot deploy it.
         at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:891)
         at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:259)
         at com.sap.ide.eclipse.deployer.dc.deploy.DeployProcessor70.deploy(DeployProcessor70.java:104)
         at com.sap.ide.eclipse.sdm.threading.DCDeployThread.run(DCDeployThread.java:80)
    Caused by: com.sap.engine.services.dc.cm.deploy.DeploymentException: ASJ.dpl_dc.001085 An error occurred while deploying the deployment item [sap.com_TestEarB].
    ; nested exception is:
         com.sap.engine.services.dc.gd.DeliveryException: [ERROR CODE DPL.DC.3298] An error occurred during deployment of [sap.com_TestEarB]. Cannot deploy it.
         at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:244)
         at com.sap.engine.services.dc.cm.deploy.impl.BulkOnlineDeployProcessor.deploy(BulkOnlineDeployProcessor.java:62)
         at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor$DeployProcessorHelper.visit(AbstractDeployProcessor.java:273)
         at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:84)
         at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor.deploy(AbstractDeployProcessor.java:95)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployThread.run(DeployThread.java:39)
         at com.sap.engine.core.thread.execution.Executable.run(Executable.java:115)
         at com.sap.engine.core.thread.execution.Executable.run(Executable.java:96)
         at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:315)
    Caused by: com.sap.engine.services.dc.gd.DeliveryException: [ERROR CODE DPL.DC.3298] An error occurred during deployment of [sap.com_TestEarB]. Cannot deploy it.
         at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.deploy(ApplicationDeployer.java:134)
         at com.sap.engine.services.dc.gd.impl.InitialApplicationDeployer.performDeployment(InitialApplicationDeployer.java:130)
         at com.sap.engine.services.dc.gd.impl.InitialGenericDeliveryImpl.deploy(InitialGenericDeliveryImpl.java:57)
         at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:210)
         ... 8 more
    Caused by: com.sap.engine.services.deploy.server.utils.DSRemoteException: ASJ.dpl_ds.006193 Error while deploying ear file C:\SAP_Workspace_72_b\TestEarB\TestEarB.ear; nested exception is:
         java.lang.Exception: com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException: Exception occurred during ws clients deployment. Unable to extract ws clients deployment data for archive TestWeb.war, application sap.com/TestEarB.
         at com.sap.engine.services.webservices.server.deploy.wsclients.WSClientsDeployProcess.extractWSClientsJ2EEEngineDescriptors(WSClientsDeployProcess.java:249)
         at com.sap.engine.services.webservices.server.deploy.wsclients.WSClientsDeployProcess.extractWSClientsJ2EEEngineDescriptors(WSClientsDeployProcess.java:204)
         at com.sap.engine.services.webservices.server.deploy.wsclients.WSClientsDeployProcess.init(WSClientsDeployProcess.java:122)
         at com.sap.engine.services.webservices.server.deploy.WSBaseAbstractDProcess.makeProcess(WSBaseAbstractDProcess.java:320)
         at com.sap.engine.services.webservices.server.deploy.WebServicesDeployManager.deployWSClients(WebServicesDeployManager.java:1079)
         at com.sap.engine.services.webservices.server.deploy.WebServicesDeployManager.deploy(WebServicesDeployManager.java:274)
         at com.sap.engine.services.deploy.server.utils.container.ContainerWrapper.deploy(ContainerWrapper.java:273)
         at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:577)
         at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:296)
         at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:211)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:697)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:755)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:2198)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:394)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:347)
         at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.deploy(ApplicationDeployer.java:116)
         at com.sap.engine.services.dc.gd.impl.InitialApplicationDeployer.performDeployment(InitialApplicationDeployer.java:130)
         at com.sap.engine.services.dc.gd.impl.InitialGenericDeliveryImpl.deploy(InitialGenericDeliveryImpl.java:57)
         at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:210)
         at com.sap.engine.services.dc.cm.deploy.impl.BulkOnlineDeployProcessor.deploy(BulkOnlineDeployProcessor.java:62)
         at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor$DeployProcessorHelper.visit(AbstractDeployProcessor.java:273)
         at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:84)
         at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor.deploy(AbstractDeployProcessor.java:95)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployThread.run(DeployThread.java:39)
         at com.sap.engine.core.thread.execution.Executable.run(Executable.java:115)
         at com.sap.engine.core.thread.execution.Executable.run(Executable.java:96)
         at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:315)
    Caused by: javax.xml.transform.TransformerException: Unsupported Source object.
         at com.sap.engine.lib.jaxp.TransformerImpl.invokeDocHandlerMethodsFor(TransformerImpl.java:651)
         at com.sap.engine.lib.jaxp.TransformerImpl.transformSimple(TransformerImpl.java:267)
         at com.sap.engine.lib.jaxp.TransformerImpl.transform(TransformerImpl.java:237)
         at com.sap.engine.lib.xml.util.legacy.StaxDOMLoader.load(StaxDOMLoader.java:53)
         at com.sap.engine.services.webservices.server.deploy.j2ee.ws.J2EE14WSClientConvertor.convert(J2EE14WSClientConvertor.java:278)
         at com.sap.engine.services.webservices.server.deploy.j2ee.ws.J2EE14WSClientConvertor.convert(J2EE14WSClientConvertor.java:231)
         at com.sap.engine.services.webservices.server.deploy.j2ee.ws.J2EE14WSClientConvertor.convert(J2EE14WSClientConvertor.java:204)
         at com.sap.engine.services.webservices.server.deploy.wsclients.WSClientsDeployProcess.extractWSClientsJ2EEEngineDescriptors(WSClientsDeployProcess.java:217)
         ... 26 more
         at com.sap.engine.services.deploy.server.DeployServiceImpl.catchDeploymentExceptionWithDSRem(DeployServiceImpl.java:4398)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:349)
         at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.deploy(ApplicationDeployer.java:116)
         ... 11 more
    Caused by: java.lang.Exception: com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException: Exception occurred during ws clients deployment. Unable to extract ws clients deployment data for archive TestWeb.war, application sap.com/TestEarB.
         at com.sap.engine.services.webservices.server.deploy.wsclients.WSClientsDeployProcess.extractWSClientsJ2EEEngineDescriptors(WSClientsDeployProcess.java:249)
         at com.sap.engine.services.webservices.server.deploy.wsclients.WSClientsDeployProcess.extractWSClientsJ2EEEngineDescriptors(WSClientsDeployProcess.java:204)
         at com.sap.engine.services.webservices.server.deploy.wsclients.WSClientsDeployProcess.init(WSClientsDeployProcess.java:122)
         at com.sap.engine.services.webservices.server.deploy.WSBaseAbstractDProcess.makeProcess(WSBaseAbstractDProcess.java:320)
         at com.sap.engine.services.webservices.server.deploy.WebServicesDeployManager.deployWSClients(WebServicesDeployManager.java:1079)
         at com.sap.engine.services.webservices.server.deploy.WebServicesDeployManager.deploy(WebServicesDeployManager.java:274)
         at com.sap.engine.services.deploy.server.utils.container.ContainerWrapper.deploy(ContainerWrapper.java:273)
         at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:577)
         at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:296)
         at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:211)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:697)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:755)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:2198)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:394)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:347)
         at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.deploy(ApplicationDeployer.java:116)
         at com.sap.engine.services.dc.gd.impl.InitialApplicationDeployer.performDeployment(InitialApplicationDeployer.java:130)
         at com.sap.engine.services.dc.gd.impl.InitialGenericDeliveryImpl.deploy(InitialGenericDeliveryImpl.java:57)
         at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:210)
         at com.sap.engine.services.dc.cm.deploy.impl.BulkOnlineDeployProcessor.deploy(BulkOnlineDeployProcessor.java:62)
         at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor$DeployProcessorHelper.visit(AbstractDeployProcessor.java:273)
         at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:84)
         at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor.deploy(AbstractDeployProcessor.java:95)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployThread.run(DeployThread.java:39)
         at com.sap.engine.core.thread.execution.Executable.run(Executable.java:115)
         at com.sap.engine.core.thread.execution.Executable.run(Executable.java:96)
         at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:315)
    Caused by: javax.xml.transform.TransformerException: Unsupported Source object.
         at com.sap.engine.lib.jaxp.TransformerImpl.invokeDocHandlerMethodsFor(TransformerImpl.java:651)
         at com.sap.engine.lib.jaxp.TransformerImpl.transformSimple(TransformerImpl.java:267)
         at com.sap.engine.lib.jaxp.TransformerImpl.transform(TransformerImpl.java:237)
         at com.sap.engine.lib.xml.util.legacy.StaxDOMLoader.load(StaxDOMLoader.java:53)
         at com.sap.engine.services.webservices.server.deploy.j2ee.ws.J2EE14WSClientConvertor.convert(J2EE14WSClientConvertor.java:278)
         at com.sap.engine.services.webservices.server.deploy.j2ee.ws.J2EE14WSClientConvertor.convert(J2EE14WSClientConvertor.java:231)
         at com.sap.engine.services.webservices.server.deploy.j2ee.ws.J2EE14WSClientConvertor.convert(J2EE14WSClientConvertor.java:204)
         at com.sap.engine.services.webservices.server.deploy.wsclients.WSClientsDeployProcess.extractWSClientsJ2EEEngineDescriptors(WSClientsDeployProcess.java:217)
         ... 26 more
         at com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException.writeReplace(WSDeploymentException.java:60)

Maybe you are looking for

  • JavaScript and CSS info in WPC

    Hi all, Is it possible to keep CSS (Stylesheet) and Javascript information from older html web pages and bring them into Web Page Composer? We have some older intranet web pages which we now want to display in the portal without ofcourse using URL iV

  • Need table available in General Ledger

    Dear All, Can any one explain me the list of tables availble in General Ledger Module in oracle-applications, including join-conditions.... Regards Subash Edited by: user12070109 on Oct 19, 2009 5:03 AM

  • Actions

    Moderator message: you've posted the same question in ECC HCM (HR) Forum.  That is the correct forum for these questions.  In future use a more meaningful subject for your posts. Hi Experts,     I have a requirement where there are 4 actions for a pa

  • JOB not ran on sepcified time.

    HI, I've used the following code to run the job everyday at 3 AM. Now, I did execute this code and found the job did not run on specifed time. when I queried the user_jobs to check the next time , then it showed me the entirley different time. I real

  • Trouble with Airport Extreme and Time Capsule

    Just got a new 2TB time capsule and added it to my network (existing Airport Express and Airport Extreme).  All devices are hard-wire back-hauled to Linksys router.  Set up was straight forward with no issues and initiated a time capsule back up with