Configuration of CTS Deploy Service

Dear Support,
In transaction WSADMIN in client 000 of the CTS system (AS ABAP part)and choose Go to u2192 Administration Settingsand enter the add the URL (http://<host of deploy web service>:<5$$00> in ABAP Stack.
Then open a java browser and navigate to the Web Service Navigator. When i check the webservice Deployeproxy is not available in the list of deployed Web Services on that server.
Could you please help on this.
Thanks & Regards,
Venkat.

Please answer

Similar Messages

Error "web service destination is not configured" in CTS+

Hi experts,
during deployment with CTS+ I get the error "web service destination is not configured" (see below). In fact there is a web service to be deployed and a WebDynpro-DC using this web service as adaptive web service model. The model uses the destination DACC_PI_WS_METADATA_DEST and DACC_PI_WS_EXECUTION_DEST. I configured both destinations in the server with type "WSDL".
Any idea what goes wrong?
Regards,
Christoph
1 ETP199 ######################################
1 ETP199X######################################
1 ETP189 DEPLOYMENT
1 ETP101 transport order     : "JADK900006"
1 ETP102 system              : "JAQ"
1 ETP199X######################################
1 ETP189 DEPLOYMENT
1 ETP101 transport order     : "JADK900006"
1 ETP102 system              : "JAQ"
1 ETP108 tp path             : "tp"
1 ETP109 version and release : "372.04.29" "700"
1 ETP198
2 EPU601X"CTS Deploy Service - Version 0.92" "06.03.2007" " " " "
2 EPU602 "==================================================""======================"" "" "
===="" "" "
2 EPU601 "Deploy web service destination =" " " " " " "
2 EPU601 "Directory =" "/usr/sap/trans/data" " " " "
2 EPU601 "SDM Deploy URL =" " " " " " "
2 EPU601 "SLD Deploy URL =" " " " " " "
2 EPU601 "XI Deploy URL =" " " " " " "
4 EPU607 Non-ABAP system "JAQ" (communication system "KSM")
4 EPU601X"Deploy for" "SDM" " " " "
4 EPU601 "Deploy File =" "karmann.comSC_DACCDIP_DACCD_C~20081001122205.sca" " " " "
4WEPU601 "Web service destination is not configured" " " ", deployment skipped" " "
4WEPU601 "Return Code =" "4" " " " "
4WEPU601 "Highest Return Code =" "4" " " " "

Hello,
I am getting an identical error per below. I have checked Web deploy service, CTSDEPLOY setup in SM59 etc and looks OK, yet the issue still occurs:
   Deployment
   Transport request   : BWDK903389
   System              : BWQ
   tp path             : tp
   Version and release: 372.04.36 700
   CTS Deploy Service - Version 0.92 06.03.2007
   ========================================================================
   Deploy web service destination =
   Directory =
   SDM Deploy URL =
   SLD Deploy URL =
   XI Deploy URL =
   Double-stack system BWQ
   Deploy for SDM
   Deploy File = CTSTEST_20081008_123719.epa
   Web service destination is not configured   , deployment skipped
   Return Code = 4
   Highest Return Code = 4
   Deployment
   End date and time : 20081015162015
   Ended with return code: ===> 4 <===
Anyone have any ideas on this one?
Thanks & Regards,
Michael

Transports not visible after CTS+ Deploy

Hi,
We have configured CTS+ in our XI landscape. The XI objects are succesfully getting transported to QA from Dev and when transporting from QA to PRD the deployment is happening without errors but we are not able see those transports in the PRD.
Transport log is has no errors and it is calling the right system.
Here with attaching the transport log
Log File:
devsappi.abbgrain.local\sapmnt\trans\log\DPXT900068.PTX
     3T             ######################################
        Deployment
        Transport request   : DPXK900068
             System              : PTX
        tp path             : tp
        Version and release: 372.04.10 700
     3T             CTS Deploy Service - Version 0.92 06.03.2007
        ========================================================================
        Deploy web service destination = CTSDEPLOY
        Directory =
devsappi.abbgrain.local\sapmnt\trans\data
        SDM Deploy URL =
        SLD Deploy URL =
        XI Deploy URL = http://prodsappi.abbgrain.local:53000
        Double-stack system PTX
        Deploy for XID
        Deploy File = 5df706c0307511dd9b0e005056b9061c
        Start of Web Service Log
        Deploy Service called with following parameters:
        CommunicationData-Type:1
        CommunicationData-Address:http://prodsappi.abbgrain.local:53000/dir
        CommunicationData-Host:prodsappi.abbgrain.local
        CommunicationData-Port:53000
        CommunicationData-User:'filled'
        CommunicationData-Password:'filled'
        Deployable(0)
        Deployable-Type:1
        Deployable-Id:
devsappi.abbgrain.local\sapmnt\trans\data/DPXK900068/5df706c0307511dd9b0e005056b9061
        >>>c
        Importing archive:
devsappi.abbgrain.local\sapmnt\trans\data/DPXK900068/5df706c0307511dd9b0e005056b
        >>>9061c
        Import finished sucessfully
        End of Web Service Log
        Return Code = 0
        Highest Return Code = 0
        Deployment
        End date and time : 20080714174834
             Ended with return code: ===> 0 <===
Please suggest what could be the problem and where I can cross verify.
Thanks & regards
Mrutyunjay

Hi Mrutyunjay,
directory transports are not activated automatically. With the CTS+ import to the directory a changelist containg the objects is created under the service user used for the target system in the XI TMS configuration.
You have to takeover the changelist from the service user, adjust the "non-transportable" fields of the objects in the changelist, and finally activate the changelist,
Afterwards the objects should exist in the target directory.
Best regards,
Silvia

CTS+ Deploy in XI

Hi,
We have configured CTS+ in our XI landscape. The XI objects are succesfully getting transported to QA from Dev and when transporting from QA to PRD the deployment is happening without errors but we are not able see those transports in the PRD.
Transport log is has no errors and it is calling the right system.
Here with attaching the transport log
Log File:
devsappi.abbgrain.local\sapmnt\trans\log\DPXT900068.PTX
3T ######################################
Deployment
Transport request : DPXK900068
 System : PTX
tp path : tp
Version and release: 372.04.10 700
3T CTS Deploy Service - Version 0.92 06.03.2007
========================================================================
Deploy web service destination = CTSDEPLOY
Directory =
devsappi.abbgrain.local\sapmnt\trans\data
SDM Deploy URL =
SLD Deploy URL =
XI Deploy URL = http://prodsappi.abbgrain.local:53000
Double-stack system PTX
Deploy for XID
Deploy File = 5df706c0307511dd9b0e005056b9061c
Start of Web Service Log
Deploy Service called with following parameters:
CommunicationData-Type:1
CommunicationData-Address:http://prodsappi.abbgrain.local:53000/dir
CommunicationData-Host:prodsappi.abbgrain.local
CommunicationData-Port:53000
CommunicationData-User:'filled'
CommunicationData-Password:'filled'
Deployable(0)
Deployable-Type:1
Deployable-Id:
devsappi.abbgrain.local\sapmnt\trans\data/DPXK900068/5df706c0307511dd9b0e005056b9061
'>>>c'
Importing archive:
devsappi.abbgrain.local\sapmnt\trans\data/DPXK900068/5df706c0307511dd9b0e005056b
'>>>9061c'
Import finished sucessfully
End of Web Service Log
Return Code = 0
Highest Return Code = 0
Deployment
End date and time : 20080714174834
 Ended with return code: ===> 0 <===
Please suggest what could be the problem and where I can cross verify.
[I have placed this post in XI Forum but felt this is more appropriate place for this question]
Thanks & regards
Mrutyunjay

If you are trying to transport the integration directory objects, you would need to activate those with Integration builder.
Please check the "change list" tab with user nwdi_ctsadm.
You may find those objects there.
Regards,
Makoto

Windows deployment services configuration

Hi,
Can any one tell me how to deploy .EXE file in windows deployment services. It`s accepting .MSI file types only.
Regards
Sakthi

Hi Sakthi,
>>Can any one tell me how to deploy .EXE file in windows deployment services. It`s accepting .MSI file types only
By default, in Active Directory, group policy can be used to deploy .msi software package. If we want to deploy a .exe file with group policy, we can convert the .exe file into .msi package or we can use a script to install the file and use
group policy to deploy the script to clients.
Windows Deployment Services is used to deploy Windows operating systems over the network. To push .exe to the operating systems, SCCM is a great option.
Regarding SCCM, the following article can be referred to for more information.
Configuration Manager
https://technet.microsoft.com/en-us/library/gg682129.aspx
Regarding deploying .exe files, the following thread can be referred to for more information.
What is the best way to push deployment of a exe file
https://social.technet.microsoft.com/Forums/en-US/a79b3406-6bc1-4af1-b826-522b1d4fa827/what-is-the-best-way-to-push-deployment-of-a-exe-file?forum=winserverDS
In addition, if we have questions regarding SCCM, we can ask for suggestions in the following forum.
Configure Manager 2012
https://social.technet.microsoft.com/Forums/en-us/home?category=systemcenter2012configurationmanager
Best regards,
Frank Shen
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

Issue in deploying Service Bus projects using maven

Hi,
I am following the following documentation for deploying service bus projects to my OSB server.
http://docs.oracle.com/middleware/1213/core/MAVEN/osb_maven_project.htm#MAVEN8973
I was able to issue mvn package as described in documentation and also able to see sbar files in .data/Maven directory of each project.
But i am seeing following error when i issue mvn pre-integration-test. Am i missing any steps.
[INFO] --- oracle-servicebus-plugin:12.1.3-0-0:deploy (default-deploy) @ System ---
[INFO] Service Bus Archive deployed using session Service_Bus_Maven-System-1424718369010.
java.io.IOException: Unable to resolve 'weblogic.management.mbeanservers.domainruntime'. Resolved 'w
eblogic.management.mbeanservers'
        at weblogic.management.remote.common.ClientProviderBase.makeConnection(ClientProviderBase.ja
va:237)
        at weblogic.management.remote.common.ClientProviderBase.newJMXConnector(ClientProviderBase.j
ava:120)
        at javax.management.remote.JMXConnectorFactory.newJMXConnector(JMXConnectorFactory.java:369)
        at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:267)
        at oracle.sb.maven.plugin.deploy.MBeanHelper$MBeanInvocationHandler.getJMXConnector(MBeanHel
per.java:228)
        at oracle.sb.maven.plugin.deploy.MBeanHelper$MBeanInvocationHandler.invoke(MBeanHelper.java:
131)
        at com.sun.proxy.$Proxy16.createSession(Unknown Source)
        at oracle.sb.maven.plugin.DeployMojo.createSession(DeployMojo.java:141)
        at oracle.sb.maven.plugin.DeployMojo.execute(DeployMojo.java:89)
        at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.j
ava:101)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
        at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBu
ilder.java:84)
        at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBu
ilder.java:59)
        at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter
.java:183)
        at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
        at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
        at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
        at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:606)
        at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
        at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
        at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
        at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.management.mbeanservers.d
omainruntime'. Resolved 'weblogic.management.mbeanservers' [Root exception is javax.naming.NameNotFo
undException: Unable to resolve 'weblogic.management.mbeanservers.domainruntime'. Resolved 'weblogic
.management.mbeanservers']; remaining name 'domainruntime'
        at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1180
        at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:270)
        at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:187)
        at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:210)
        at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:224)
        at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:224)
        at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:224)
        at weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(Unknown Source)
        at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:701)
        at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:231)
        at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:527)
        at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
        at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
        at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:523)

Hi Siva,
I am facing same issue I am bale to create package but while deployment goal I am facing problem.I am following same document as you do.
I can see my mvn-pre-integration ..show me sucees in result
[DEBUG]   Excluded: org.apache.maven:maven-artifact:jar:3.0.3
[DEBUG] Configuring mojo com.oracle.servicebus.plugin:oracle-servicebus-plugin:12.1.3-0-0:package from plugin realm ClassRealm[plugin>com.oracle.servicebus.plugin:oracl
-servicebus-plugin:12.1.3-0-0, parent: sun.misc.Launcher$AppClassLoader@65450f1f]
[DEBUG] Configuring mojo 'com.oracle.servicebus.plugin:oracle-servicebus-plugin:12.1.3-0-0:package' with basic configurator -->
[DEBUG]   (f) oracleHome = C:\Oracle\Middleware\Oracle_Home
[DEBUG]   (f) project = MavenProject: LinuxMachine:TestOSBLinux:1.0-SNAPSHOT @ C:\JDeveloper\mywork\OSB-DEPLOY\LinuxMachine\TestOSBLinux\pom.xml
[DEBUG]   (f) system = false
[DEBUG] -- end configuration --
[INFO]
[INFO] --- oracle-servicebus-plugin:12.1.3-0-0:deploy (default-deploy) @ TestOSBLinux ---
[DEBUG] Configuring mojo com.oracle.servicebus.plugin:oracle-servicebus-plugin:12.1.3-0-0:deploy from plugin realm ClassRealm[plugin>com.oracle.servicebus.plugin:oracle
servicebus-plugin:12.1.3-0-0, parent: sun.misc.Launcher$AppClassLoader@65450f1f]
[DEBUG] Configuring mojo 'com.oracle.servicebus.plugin:oracle-servicebus-plugin:12.1.3-0-0:deploy' with basic configurator -->
[DEBUG]   (f) oraclePassword = Oracle123
[DEBUG]   (f) oracleServerUrl = http://192.168.137.150:7001
[DEBUG]   (f) oracleUsername = weblogic
[DEBUG]   (f) project = MavenProject: LinuxMachine:TestOSBLinux:1.0-SNAPSHOT @ C:\JDeveloper\mywork\OSB-DEPLOY\LinuxMachine\TestOSBLinux\pom.xml
[DEBUG] -- end configuration --
[INFO] Service Bus Archive deployed using session Service_Bus_Maven-TestOSBLinux-1429888616161.
[INFO]
[INFO] --- oracle-servicebus-plugin:12.1.3-0-0:deploy (deploy) @ TestOSBLinux ---
[DEBUG] Configuring mojo com.oracle.servicebus.plugin:oracle-servicebus-plugin:12.1.3-0-0:deploy from plugin realm ClassRealm[plugin>com.oracle.servicebus.plugin:oracle
servicebus-plugin:12.1.3-0-0, parent: sun.misc.Launcher$AppClassLoader@65450f1f]
[DEBUG] Configuring mojo 'com.oracle.servicebus.plugin:oracle-servicebus-plugin:12.1.3-0-0:deploy' with basic configurator -->
[DEBUG]   (f) oraclePassword = Oracle123
[DEBUG]   (f) oracleServerUrl = http://192.168.137.150:7001
[DEBUG]   (f) oracleUsername = weblogic
[DEBUG]   (f) project = MavenProject: LinuxMachine:TestOSBLinux:1.0-SNAPSHOT @ C:\JDeveloper\mywork\OSB-DEPLOY\LinuxMachine\TestOSBLinux\pom.xml
[DEBUG] -- end configuration --
[INFO] Service Bus Archive deployed using session Service_Bus_Maven-TestOSBLinux-1429888623126.
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building LinuxMachine 1.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[DEBUG] Lifecycle default -> [validate, initialize, generate-sources, process-sources, generate-resources, process-resources, compile, process-classes, generate-test-so
rces, process-test-sources, generate-test-resources, process-test-resources, test-compile, process-test-classes, test, prepare-package, package, pre-integration-test, i
tegration-test, post-integration-test, verify, install, deploy]
[DEBUG] Lifecycle clean -> [pre-clean, clean, post-clean]
[DEBUG] Lifecycle site -> [pre-site, site, post-site, site-deploy]
[DEBUG] === PROJECT BUILD PLAN ================================================
[DEBUG] Project:       LinuxMachine:LinuxMachine:1.0-SNAPSHOT
[DEBUG] Dependencies (collect): []
[DEBUG] Dependencies (resolve): []
[DEBUG] Repositories (dependencies): [central (https://repo.maven.apache.org/maven2, default, releases)]
[DEBUG] Repositories (plugins)     : [central (https://repo.maven.apache.org/maven2, default, releases)]
[DEBUG] =======================================================================
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] TestOSBLinux ....................................... SUCCESS [ 20.752 s]
[INFO] LinuxMachine ....................................... SUCCESS [ 0.009 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
But not get deployed .....
When i run mvn com.oracle.servicebus.plugin:oracle-servicebus-plugin:deploy** to invoke deployment goal it fails which below logs
org.apache.maven.plugin.MojoNotFoundException: Could not find goal 'deploy*.*' in plugin com.oracle.servicebus.plugin:oracle-servicebus-plugin:12.1.3-0-0 amon
goals deploy, package
        at org.apache.maven.plugin.internal.DefaultMavenPluginManager.getMojoDescriptor(DefaultMavenPluginManager.java:275)
        at org.apache.maven.plugin.DefaultBuildPluginManager.getMojoDescriptor(DefaultBuildPluginManager.java:239)
        at org.apache.maven.lifecycle.internal.MojoDescriptorCreator.getMojoDescriptor(MojoDescriptorCreator.java:233)
        at org.apache.maven.lifecycle.internal.DefaultLifecycleTaskSegmentCalculator.calculateTaskSegments(DefaultLifecycleTaskSegmentCalculator.java:103)
        at org.apache.maven.lifecycle.internal.DefaultLifecycleTaskSegmentCalculator.calculateTaskSegments(DefaultLifecycleTaskSegmentCalculator.java:83)
        at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:85)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:355)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
        at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
        at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:216)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:160)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:606)
        at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
        at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
        at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
        at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
[ERROR]
[ERROR]
Thanks&Regards
Prabhat

Configuration wizard Weblogic deployment error [Admin Center]

I'm getting an error during the "Executing WLST Script" phase of the configuration wizard.
My environment:
BEA Weblogic Server 10.0 (installed with Workspace Studio 1.1)
Oracle BPM 10g3 (10.3.0.0)
Oracle Database 10g Express
This is what the AdmCenterConsole.log file has:
Deploying application from C:\OraBPMwlHome\j2ee\weblogic\deployer\wlj2eedeployer.ear to targets BPMServer (upload=true) ...
<Jan 28, 2009 11:15:59 AM PST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, wlj2eedeployer archive: C:\OraBPMwlHome\j2ee\weblogic\deployer\wlj2eedeployer.ear, to BPMServer .>
.Completed the deployment of Application with status completed
Current Status of your Deployment:
Deployment command type: deploy
Deployment State : completed
Deployment Message : no message
Deploying application from C:\OraBPMwlHome\ears\engine\01-eng-bpmengine.ear to targets BPMServer (upload=true) ...
<Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, 01-eng-bpmengine -archive: C:\OraBPMwlHome\ears\engine\01-eng-bpmengine.ear-, to BPMServer .>
WLST-WLS-1233170095995: <Warning> <DeploymentService> <BEA-290003> <Deployment service servlet encountered an exception while handling request of type "app_upload". Exception is: "*Connection reset*".>
Failed to deploy the application with status failed
Current Status of your Deployment:
Deployment command type: deploy
Deployment State : failed
Deployment Message : weblogic.deploy.api.spi.exceptions.ServerConnectionException: [J2EE Deployment SPI:260041 Unable to upload 'C:\OraBPMwlHome\ears\engine\01-eng-bpmengine.ear' to 't3://dmcad00064252:7001'
No stack trace available.
weblogic.management.scripting.ScriptException: Error occured while performing deploy : Deployment Failed.
    at weblogic.management.scripting.ExceptionHandler.handleException(ExceptionHandler.java:49)
    at weblogic.management.scripting.WLSTUtils.throwWLSTException(WLSTUtils.java:185)
    at weblogic.management.scripting.JSR88DeployHandler.deploy(JSR88DeployHandler.java:535)
    at weblogic.management.scripting.WLScriptContext.deploy(WLScriptContext.java:427)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at org.python.core.PyReflectedFunction.__call__(PyReflectedFunction.java:160)
    at org.python.core.PyMethod.__call__(PyMethod.java:96)
    at org.python.core.PyObject.__call__(PyObject.java:248)
    at org.python.core.PyObject.invoke(PyObject.java:2016)
    at org.python.pycode._pyx19.deploy$8(<iostream>:223)
    at org.python.pycode._pyx19.call_function(<iostream>)
    at org.python.core.PyTableCode.call(PyTableCode.java:208)
    at org.python.core.PyTableCode.call(PyTableCode.java:404)
    at org.python.core.PyFunction.__call__(PyFunction.java:184)
    at org.python.pycode._pyx18.deploy_Applications$61(C:\Documents and Settings\c742323\.configWizard\tmp\config.py:623)
    at org.python.pycode._pyx18.call_function(C:\Documents and Settings\c742323\.configWizard\tmp\config.py)
    at org.python.core.PyTableCode.call(PyTableCode.java:208)
    at org.python.core.PyTableCode.call(PyTableCode.java:256)
    at org.python.core.PyFunction.__call__(PyFunction.java:169)
    at org.python.pycode._pyx18.f$0(C:\Documents and Settings\c742323\.configWizard\tmp\config.py:738)
    at org.python.pycode._pyx18.call_function(C:\Documents and Settings\c742323\.configWizard\tmp\config.py)
    at org.python.core.PyTableCode.call(PyTableCode.java:208)
    at org.python.core.PyCode.call(PyCode.java:14)
    at org.python.core.Py.runCode(Py.java:1135)
    at org.python.util.PythonInterpreter.execfile(PythonInterpreter.java:167)
    at weblogic.management.scripting.WLST.main(WLST.java:106)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at weblogic.WLST.main(WLST.java:29)

Hi. I'm having this same exact issue. My AdmCenterConsole.log contains the same error. Additionally, the log file for my BPMDomain log contains this information:
Current Status of your Deployment:
Deployment command type: deploy
Deployment State : failed
Deployment Message : weblogic.management.ManagementException: [Deployer:149003]Unable to access application source information in '[DeploymentService:290003]Deployment service servlet encountered an exception while handling request of type "app_upload". Exception is: "Read timed out".\app\01-eng-albpmengine.ear' for application '01-eng-albpmengine'. The specific error is: No application files exist.
No stack trace available.
This Exception occurred at Sun Apr 19 14:29:13 CDT 2009.
weblogic.management.scripting.ScriptException: Error occured while performing deploy : Deployment Failed.
     at weblogic.management.scripting.ExceptionHandler.handleException(ExceptionHandler.java:48)
     at weblogic.management.scripting.WLSTUtils.throwWLSTException(WLSTUtils.java:185)
     at weblogic.management.scripting.JSR88DeployHandler.deploy(JSR88DeployHandler.java:536)
     at weblogic.management.scripting.WLScriptContext.deploy(WLScriptContext.java:429)
mick3y -- Did you happen to ever get this issue resolved?
Thanks, Alan

Windows Deployment Services Unable to PXE boot clients PXE-E53: No Boot Filename Received

Hi
I'm trying to configure WDS/MDT to deploy Windows 8.1. I've captured an image and I'm ready to deploy the image to a workstation, as per the above title when I attempt to PXE boot a test workstation it just times out with the following error message PXE-E52:No
Boot Filename Recieved. I've tried a few tweaks to get it working however no such luck.
The setup is as follows it's a virtual Windows 2012 R2 machine, just a fresh member server with microsoft deployment toolkit installed and WDS role installed with the nesscary framework features installed.
I've tried tweaking the properties of most of the settings within the server settings in WDS with no such luck.
I'm a novice at WDS but from what I've read I shouldn't need configure that much in the first place to get it working.
I'm willing to bet it will be something I've overlooked so I need a 2nd opinon, could anyone provide any troubleshooting tips. If you require anymore information please let me know.
Cheers

Hi Joel,
This error may caused by the WDS server is not pushing the images because PXE Clients are not able to download or communicate with the TFTP server.
The image can’t be download generally caused by the the Vlan is not enabled IP helper/DHCP relay agent configured on it, all DHCP broadcasts on UDP port 67 by client computers
should be forwarded directly to both the DHCP server and the Windows Deployment Services PXE server.
The related KB:
PXE clients computers do not start when you configure the Dynamic Host Configuration Protocol server to use options 60, 66, 67
http://support.microsoft.com/kb/259670
The similar thread:
PXE-E53: No boot filename received
http://social.technet.microsoft.com/Forums/systemcenter/en-US/8de3bd6a-f8ec-41d9-ae0f-5b2fdb9e5831/pxee53-no-boot-filename-recieved?forum=configmgrosd
WDSServer (Windows Deployment Server) Fails to Start
http://social.microsoft.com/Forums/en-US/d96b0b86-f2b0-49a5-8946-19ab515f23e6/wdsserver-windows-deployment-server-fails-to-start?forum=windowshpcitpros
I’m glad to be of help to you!
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Windows Deployment Services Issues

i have a Windows deployment Services server running , and at the same server i am running dhcp as well as dns server. the network series is 10.241.0.1 to 10.241.0.105 , questions:
Q: if i want the dhcp server to offer ip address in the network of 10.241.1.1 is it possible or i need to take the dhcp server in the network series of 1.
Q: sometimes there is a problem in wds , the client pc says no dhcp proxies were offered, how do i resolve that ?
Q:While entering the scope in the dhcp server, the dhcp server says the IP is overlapped or invalid ip address, any solutions ?
Q: i have multiple operating systems to deploys via network, so how is that possible , should i create a new image group or can i add the images in the same images and will it ask during the startup ? i tried by adding the other os to the group , the first
os gets booted and installed but when i select the second operating system says, wdsclient error, no dhcp offered , , , , and so.

Hi,
According to your description, I list your questions and the suggestions for each question as bellow:
Q: if i want the dhcp server to offer ip address in the network of 10.241.1.1 is it possible or i need to take the dhcp server in the network series of 1.
If there are 2 network, 10.241.0.1/24 and 10.241.1.1/24, and you want the DHCP server (which is belong to network 10.241.0.1/24 ) to provide DHCP service to clients on network 10.241.1.1/24. You may configure a DHCP relay agent on network 10.241.1.1/24, in
order to forwarder DHCP messages between clients (which are on network 10.241.1.1/24) and DHCP server. Detailed information about how to configure DHCP relay agent you may reference the link:
http://technet.microsoft.com/en-us/library/dd469685.aspx
Q: sometimes there is a problem in wds , the client pc says no dhcp proxies were offered, how do i resolve that ?
On the client which says no DHCP proxies were offered, open CMD, type “ipconfig /all” and hit Enter, check to see if it obtains the correct parameters. If not, type “ipconfig /release“ and “ipconfig /renew” to renew IP address.
Q:While entering the scope in the dhcp server, the dhcp server says the IP is overlapped or invalid ip address, any solutions ?
On a DHCP server, you can create only on scope for a subnet. If you have created a scope from 10.241.0.1 to 10.241.0.105, with subnet mask 255.255.255.0, then a scope with network ID 10.241.0.0 can’t be created. You may use
Exclusions to resolve this problem. If the problem still exit, please provide the scope and relate parameters you want to add, and the exiting scope you have already added on the DHCP server.
Q: i have multiple operating systems to deploys via network, so how is that possible , should i create a new image group or can i add the images in the same images and will it ask during the startup ? i tried by adding the other os to the group ,
the first os gets booted and installed but when i select the second operating system says, wdsclient error, no dhcp offered , , , , and so.
You must have a working DHCP server with an active scope on the network because Windows Deployment Services uses PXE, which relies on DHCP for IP addressing. Make sure that your DHCP implement is working and let us resolve the above 3 problems first. Besides,
you may reference the link for detailed information about Windows Deployment Services Getting Started Guide:
http://technet.microsoft.com/en-us/library/cc771670(v=WS.10).aspx
Best Regards,
Eve Wang

Windows Deployment Services - Windows 8.1 Deployment Failure (Required Driver could not be Installed)

Hello everyone,
Give you a little background on the hardware/software which we are running to do a Windows 8.1 Deployment, we have an VM of Windows Server 2008 R2 with Windows Deployment Services installed and configured correctly. For the boot image it's a Windows 8.1
WIM and as for the Install Image we have a base image of Win 8.1 with all drivers installed for an HP EliteBook 8540w , we Syspreped and then capture the image using the W2K capture on PXE to capture and upload the image to the server. This is where we first
ran into the problem of connecting to the server and had to inject the lan drivers to have network connectivity. After the image was uploaded to the server, we thought to try and run a deployment of that image on an identical laptop. PXE boot into that Image,
it asks for domain credentials which are accepted it begins the installation process and fails at "Windows installation cannot continue because a required driver could not be installed"?
We just set up client logging on the server and it is useless it just says that the driver is missing, but what driver is missing? There are thousands, which one?
Another forum has this issue: http://social.technet.microsoft.com/Forums/windows/en-US/4cf0b378-09d0-4e0b-bc6e-3d898b668f98/during-deployment-windows-installation-cannot-continue-because-a-required-driver-could-not-be?forum=w8itproinstall

Hi,
Please first check the solution here:
Error: Windows installation cannot continue because a required driver could not be installed
http://support.brainwaregroup.com/kb/article/AA-00702/0/Error%3A-Windows-installation-cannot-continue-because-a-required-driver-could-not-be-installed.html
Also, please try to find out Setup logs from the client computer, and we can see the details in the Setup log:
If the failure occurs in Windows PE before the disk configuration page of the WDS client is completed, you can find the logs at the
X:\Windows\Panther folder. Use Shift+F10 to open a command prompt, and then change the directory to the location.
If the failure occurs in Windows PE after the disk configuration page of the WDS client is completed, you can find the logs on the local disk volume at the
$Windows.~BT\Sources\Panther folder. The local disk volume is usually the drive
C. Use Shift+F10 to open a command prompt, and then change the directory to the location.
Kate Li
TechNet Community Support

Windows Deployment Service. Network Profile Radio Buttons greyed out with R2

Hi All
I have downloaded and setup Server 2008 R2 (not yet activated). I have added the following roles "DHCP Server", "DNS Server", "Active Directory Domain Services" and "Windows Deployment Services". I can PXE boot a test client machine and (using the boot.win from windows 7 dvd) multicast a XP Image to it. This setup is connected via a 100 Mb switch and is an isolated network.
Under windows deployment services - if I right click my server - select properties - network tab "Network Profile is greyed out". I have tried running wdsutil /Set-TransportServer /Server:big /Profile:100Mbps but get the following error message: "Windows Deployment Services Management Utility Version 6.1.7600.16385. Error code 0xC110011F This WDS transport server does not support network profiles.
I have tried this on two hardware setups:
An Intel D915GUX 3GHz 2GB RAM and Marvel Yukon 88E8050 ethernet controller.
An Intel D965 Core2Duo 1.86GHz 2GB RAM and Intel 82566DM Network controller.
Incidently I have done the same setup with Server 2008 (not R2) on the D965 and the Network Profile radio buttons are not greyed out. If I upgrade the same test machine to server 2008 R2 the Network Profile radio buttons are greyed out. Is this a design change, does Server 2008 R2 no longer support network profiles as I am now unable to select 10 100 or 1000 Mbs ?
If more information is required or if anything needs further detail please let me know.
Thanks for any help.
Liam.D

Is there any way at all to manually set or control the network profile? In my environment, a SCCM\WDS multicast stream is bottoming out on speed and network utilization when the stream crosses a Nexus 7009 router. Speeds go from 200 Mbps to 20 mbps. I have
a theory that this "new" automatic configuration is placing the clients in a slow network profile that are on the opposite side of the router and I have been unable to find a way to speed of the transmission. I have also ruled out the "master
client" slowing down the stream buy using different clients only connecting to a stream 1 at a time. I have also ruled out the router as the source of the problem by having a VLC client listen to the multicast stream on the same side of the router as
the slow clients. The VLC client (unknown to SCCM\WDS) was able to receive the transmissions at 20 % utilization / 200 Mbps.
-Tony

Windows Deployment Services "the specified image file is either invalid or corrupted"

I'm trying to add images to a virtual server running WS08 R2 but the only type of images that get accepted are the vista x86, nothing else works,
I tried the following image files:
windows server 2008 R2
windows server 2008 x64
windows 7 x64
windows 7 x86
windows vista x64
and always the same error: "the specified image file is either invalid or corrupted"
the machine configuration is as follows:
Virtual machine on Hyper-V 2 (host is WS08 R2 Enterprise)
2048 MB RAM
25 GB free diskspace
running these roles:
AD
DNS
DHCP
WDS
hope someone can help

Was a solution for this ever found? I am experiencing the same issue with the following setup:
I am having an issue with a virtualized Windows Server 2008 R2 Enterprise blue-screening any time I try and add an install image through the Windows Deployment Services mode.
Server:
Lenovo TD200x – 3822-43U
Dual Intel Xeon E5530 CPU’s
Installed Memory: 28.0 GB
Two raid arrays.
                Array 1 – 500 GB Mirror – hosting Windows 2008
R2 Enterprise running Hyper-V
                Array 2 – 1 TB RAID 10 – hosting Virtual Machines
and Virtual Hard Disks
We have the latest firmware update installed on this physical machine
Our physical server is the Lenovo TD200x machine. On it, we are running Windows Server 2008 R2 Enterprise
Within Hyper-V, I am running a Windows Server 2008 R2 Enterprise domain.
Virtual Server 1 is a domain controller running Windows Server 2008 R2. It is configured with roles of: Active Directory Domain Services, DNS,
and DHCP.
Virtual Server 2 is a member server running Windows Server 2008 R2. It is configured with the role of: Windows Deployment Services.
The error is occurring on Virtual Server 2. After everything is installed on this server, and it is setup as a domain member and has the Windows
Deployment services role added, I go through and ad a Windows 7 boot image within Windows Deployment Services with no problem. When I go through and try to add a Windows 7 install image, however, during the creation of that install image, the Virtual
Server 2 pops up an error that reads:
Error occurred while trying to execute command.
Error Code: 0x80070002
After this, the system will immediately blue-screen and reboot with a STOP 0x000000F4 Error
I have tried using various Windows 7 DVD’s and even using the Windows 7 ISO file, mounting it as a drive. All with the same results.
I have erased the virtual server and recreated it with the same results. I have removed the entire domain and recreated both servers with the same results.
I have setup the physical box as a Windows Server 2008 R2 domain controller and added the Windows Deployment Services role and did NOT have any problems
going about it in that manner. Therefore, the issue lies within running this in a Virtualized server within Hyper-V.

Can't start "Windows Deployment Services" Service

I have a Windows 2003 Server that has WDS SP1 installed. The Windows
Deployment Services Server Service isn't started and when I try to
start it I get a message that says:
Windows could not start the Widows Deployment Services Server on Local
Computer. For more information, review the System Event Log. If this
is a non-Microsoft service, contact the service vendor, and refer to
server-specific error code 2310.
Event viewer lists Event ID 257 and this:
An error occurred while trying to start the Windows Deployment Services
server.
Error Information: 0x906
When I go to the actual WDS application, my server isn't listed. If
I try and add it, I get a message that says "The Windows Deployment
Services configuration is corrupt. Would you like to add it anyway?"
If I say yes, the server is added, but it has a red x through it.
I thought about removing WDS and then re-installing it, but it listed a
number of programs that might fail if I did that.
What should I do?

Thanks, my problem was exactly that:
..................The error you are receiving generally indicates that you have a networking configuration problem on your server that
is causing the domain to be unreachable...............
They exchanged the Firewall and forgot to unlock the doors. After review and release back to work.
Thank you.________________
Moura

Make WDS Service account approve pending devices in WINDOWS DEPLOYMENT SERVICES

Hi Technet and all other people reading this.
I am at the moment trying to get a Service account(WDSService) to approve pending devices in Windoes Deployment Services on a WDS server.
I have created a domain called LALALA.dk on a server(DNS is included in the domain), and installed windows deployment services on another server. The Deployment service is setup to prestage devices, and therefore devices needs to be approved before it can
be deployed.
My problem is that at the moment, we are using Domain Admin accounts to do the approving and i wish to change that to a service account, made specially for this job which ofc. should have minimum right. Because i have a very hard time understanding
why i NEED to grant domain admin rights or local admin rights to a person just so that he can approve pending devices. There has to be a way to use a service account to do the job.
I have done some research and found out that local admin, domain admins and enterprise admins are the only onces that have the permission to approve pending devices, and that a problem for me, when i want a service account to do it for me(Not automatically)
but a service account that can name and approve devices manually.
Here is what i have allready tried.
1. making WDSService run the Windows Deployment Services (service), but this didnt work because it lacks the permissions needed.
2. I have given the read+write permissions on the remoteinstall folder, even tried with full control.
3. Delegate control on the OU in active directory, to create computer object, with full write permissions. I also tried with full control. I added both WDSServer$ and the service account(WDSService) on the OU. Still nothing.
4. I then downloaded subinacl tool, and granted WDSService account permission to start, stop the service, even tried with full control on the Windows Deployment Service(WDSServer as server_name). I get error 1297 something with priviledge missing from the
service account to perform the actions. So still nothing. Which is really weird when i ran a command i cant remember now, where i could see that the service account had full permission granted to the service, and still was'nt able to start the service.
5. I then tried to create a script using WDSUTIL, but was not able to grant the service account permissions to perform the action of approving pending devices. And i dont want to use a script everytime i need to approve a device.
6. Since the local system account is running the Windows Deployment Service , my thought was to join the WDSService account to the built-in NT AUTHORITY/local system or NT AUTHORITY/local service, this seems impossible from what i experienced, unless you
are super powershell geek i quess you can, so this option didnt get me anywhere as well.
6. I then created a gpo granting wdsservice account the "log on as a service" policy on the Windows deployment service Server, still nothing works as attended. I still get error 1297.
7.I tried copying the registry keys (WDSSERVER) from the HKEY_LOCAL_MACHINE hive on the WDS Server, and imported it into my Domain's registry, but could'nt find the service i wanted to grant permissions to in the group policy settings (computer configuration/policies/windows
settings/security settings/System Services) I then created a registry entry with group policy (computer configuration/policies/windows settings/security settings/registry) to point to (local machine/system/controlset001/services/WDSServer) and granting
WDSService account full control and deployed the policy to the Deployment server. Nothing happend and i still cant approve pending devices with my service account.
from my understanding service account where created to maintain small certain tasks or actions with limited permissions, so if comprimised they could only do very little damage, and so that this account can be setup to perform the tasks without any administation
of the account. So my question is, is it even possible to achieve what i want = granting a service account the permission to perform the action of approving pending devices on a Windows Deployment Server, and if so how ?
I am so confused over this and I am really reaching the limits of my understanding of this.
Help is very much appreciated.
Henrik Larsen

Hi ZeR1X,
The Require Administrator approval is for unknown computers.
The similar thread:
WDS - Request administrator approval not working
https://social.technet.microsoft.com/Forums/windowsserver/en-US/b9088be7-7afe-4e2b-b5fb-4554a92c4a2a/wds-request-administrator-approval-not-working
More information:
Windows Deployment Service fails to start with error information of 0x5
http://support.microsoft.com/kb/2009647
WDS 3.01 Troubleshooting Guide
http://technet.microsoft.com/en-us/library/cc754828(v=ws.10).aspx
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]

PXE-E61 Meadia test failure error occurred during installing OS form windows deployment service?

Hi,
I have installed WDS service in my dell server windows 2008 server R2. I am using WDS server and Dhcp server in different machine.I have received error "PXE:E-61 Media test failure check cable ", when I trying to install
OS from my WDS server. But I have created a one partition in VMware and successfully installed windows 2008 R2 server from Windows deployment service. But when I am trying to install the OS in another dell server from WDS, I have received this error.
Any help?

Hi,
For PXE boot, we need the client boot from network. Check your boot option in BIOS settings. Meanwhile, we need WDS server and
DHCP server accessible. If the client locate in a different subnet, IP helper should be configured to point to WDS server and DHCP server.
If everything is configured correctly, I recommend you contact with the manufacture.
Hope this helps.

Configuration of CTS Deploy Service

Similar Messages

Maybe you are looking for