Problem with SDM

Hi
i am having problems accessing the SDM of my 877 router. it asks for me for the username/apssword for the second time and when entered it stays there forever. i have installed java and turned popups as well... wht could be the problem. plzzzzzzzzz

Type the enable password into the password box.

Similar Messages

MDM Business Package : Deployment problem with SDM GUI

Dear Experts,
I want to deploy the MDM Business Package on to the j2ee engine.However, when i go to the SDM GUI and select the first SDA(com.sap.mdm.tech.mdm4j.sda) file for deployment, it just hangs and nothing happens after that.I feel something is wrong with the SDM GUI.
Please let me know any possible solutions/alternatives to this problem.
Thanks,
Karambir Singh

Hi Karambir,
1) Are you trying to deploy the sda from your local machine or from a network drive? If a network drive, try copying it to your local machine and then deploying it.
2) If the SDM is connecting to a remote application server, it can sometimes take a long time to get a response.
3) Can you deploy other deployable archives via the SDM, or is only mdm4j.sda causing a problem?
Walter

Problems with dependencies in SDM

Hi all,
I have some problems with the dependencies check in SDM.
Some time ago we have created several custom PAR files for our internal Portal. As it takes some time to upload all these PAR files manually we created EAR files out of these PAR files and bundled them into an SCA file.
As theses EAR files needs to be deployed in a certain order we managed to create specific dependencies between these EAR files.
Up to now everything worked fine.
But now we have a new challenge. Due to a structure change we needed to create new PAR files which change the dependency hierarchy. When we now create EAR files and bundle them to an SCA file we get an error message when trying to upload the files via SDM.
The SDM then throws following error:
For each of the listed SDAs (contained in the selected SCA) SDM has detected an SDA in its repository with identical development component attributes but with a different software type or with a different set of dependencies.
example:
in the past we had two PAR file "appA.par" and "appB.par". "appA.par" depends on "appB.par" and "appB.par" depends on the SAP Portal Runtime PAR file. (So "appB.par" needs to be deployed first).
Now we have three PAR files "appA.par", "appB.par" and "appC.par". "appA.par" does not depend any longer from "appB.par" but from "appC.par". Trying to deploy these files now via SDM throws an error telling that SDM can't upload the SCA file as "appA.par" should depend on "appB.par" and not on "appC.par"...
Is there any way to switch off this dependency check for custom components or to reset or avoid it somehow else.
What I want to avoid is to undeploy all the PAR files deployed so far as the list of PAR files is very big and the SDM undeployment tool is not very handy...
regards
René Jurmann

Hi,
I don't have a good answer to your question (other than undeploy them which you would like to avoid , but what I usually recommend for PAR transport is to have a dummy portal component for each of them (in the portal-app.xml) and create an iview of it in a special folder. Then just transfer all the iviews in a transport package, select include dependencies (<yournamespace_prefix>.*) and you have a standard portal transport package with all your pars.. Beats waiting for the SDM to start up
Dagfinn

Problem with deploying : SDM could not start the J2EE cluster on the host .

Hello, All
I have following problem with deploying the aplication I get this messenger:
16/09/2008 07:59:44 PM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
[001]Deployment aborted
Settings
SDM host : 192.168.0.14
SDM port : 50018
URL to deploy : file:/C:/DOCUME1/PENITU1/LOCALS~1/Temp/temp47114ZChangeRequestDatabase.ear
Result
=> deployment aborted : file:/C:/DOCUME1/PENITU1/LOCALS~1/Temp/temp47114ZChangeRequestDatabase.ear
Aborted: development component 'ZChangeRequestDatabase'/'local'/'LOKAL'/'0.2008.05.03.04.24.17'/'0':
SDM could not start the J2EE cluster on the host Jupiter! The online deployment is terminated. There is no cluster control instance running on host Jupiter which is described in SecureStorage . The instances, returned by MessageServer [MS host: Jupiter; MS port: 3901], are :|Name:JM_T1221612526745_0_penitus15 |Host:PENITUS15 |State:5|HostAddress:192.168.0.205||Name:JM_T1221612357814_0_Jupiter |Host:pfs |State:5|HostAddress:192.168.0.14||Name:JC_Jupiter_JTP_00 |Host:pfs |State:5|HostAddress:192.168.0.14|Please check if there is an appropriate running cluster instances.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).STARTUP_CLUSTER)
Deployment exception : The deployment of at least one item aborted
I dont'n know How do I solver this error?
- I reviewed the virtual memory and I increase the virtual memory
- I restarted the server and the system
- I reviwed the parameter in the config tool --> cluster --> security storage it is OK
Any suggestion for solver this problem
Thanks
Regards
DS

I found this messenger in Additional log information., Please si
17/09/2008 03:04:51 PM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] INFO:
[004]Additional log information about the deployment
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[1.5.3.7185 - 630]/>
<!NAME[C:\usr\sap\JTP\JC00\SDM\program\log\sdmcl20080917200328.log]/>
<!PATTERN[sdmcl20080917200328.log]/>
<!FORMATTER[com.sap.tc.logging.TraceFormatter(%24d %s: %m)]/>
<!ENCODING[Cp1252]/>
<!LOGHEADER[END]/>
Sep 17, 2008 1:04:40 PM Info: -
Starting deployment -
Sep 17, 2008 1:04:40 PM Info: Error handling strategy: OnErrorStop
Sep 17, 2008 1:04:40 PM Info: Prerequisite error handling strategy: OnPrerequisiteErrorStop
Sep 17, 2008 1:04:40 PM Info: Update strategy: UpdateAllVersions
Sep 17, 2008 1:04:40 PM Info: Starting deployment prerequisites:
Sep 17, 2008 1:04:40 PM Info: Loading selected archives...
Sep 17, 2008 1:04:40 PM Info: Loading archive 'C:\usr\sap\JTP\JC00\SDM\program\temp\temp62604ZIssueDatabase.ear'
Sep 17, 2008 1:04:41 PM Info: Selected archives successfully loaded.
Sep 17, 2008 1:04:41 PM Info: Actions per selected component:
Sep 17, 2008 1:04:41 PM Info: Initial deployment: Selected development component 'ZIssueDatabase'/'local'/'LOKAL'/'0.2008.04.17.10.53.03'/'0' will be deployed.
Sep 17, 2008 1:04:41 PM Info: Ending deployment prerequisites. All items are correct.
Sep 17, 2008 1:04:43 PM Error: Unable to compare host[Jupiter] and host[PENITUS15] Throwable: java.net.UnknownHostException Throwable message: PENITUS15: PENITUS15
Sep 17, 2008 1:04:45 PM Error: Unable to compare host[Jupiter] and host[pfs] Throwable: java.net.UnknownHostException Throwable message: pfs: pfs
Sep 17, 2008 1:04:45 PM Error: Unable to compare host[Jupiter] and host[pfs] Throwable: java.net.UnknownHostException Throwable message: pfs
Sep 17, 2008 1:04:45 PM Info: Saved current Engine state.
Sep 17, 2008 1:04:45 PM Info: Starting: Initial deployment: Selected development component 'ZIssueDatabase'/'local'/'LOKAL'/'0.2008.04.17.10.53.03'/'0' will be deployed.
Sep 17, 2008 1:04:45 PM Info: SDA to be deployed: C:\usr\sap\JTP\JC00\SDM\root\origin\local\ZIssueDatabase\LOKAL\0\0.2008.04.17.10.53.03\temp62604ZIssueDatabase.ear
Sep 17, 2008 1:04:45 PM Info: Software type of SDA: J2EE
Sep 17, 2008 1:04:45 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Sep 17, 2008 1:04:45 PM Error: Unable to compare host[Jupiter] and host[PENITUS15] Throwable: java.net.UnknownHostException Throwable message: PENITUS15
Sep 17, 2008 1:04:45 PM Error: Unable to compare host[Jupiter] and host[pfs] Throwable: java.net.UnknownHostException Throwable message: pfs
Sep 17, 2008 1:04:45 PM Error: Unable to compare host[Jupiter] and host[pfs] Throwable: java.net.UnknownHostException Throwable message: pfs
Sep 17, 2008 1:04:45 PM Info: Starting cluster instance processes.
Sep 17, 2008 1:04:45 PM Error: Unable to compare host[Jupiter] and host[PENITUS15] Throwable: java.net.UnknownHostException Throwable message: PENITUS15
Sep 17, 2008 1:04:45 PM Error: Unable to compare host[Jupiter] and host[pfs] Throwable: java.net.UnknownHostException Throwable message: pfs
Sep 17, 2008 1:04:45 PM Error: Unable to compare host[Jupiter] and host[pfs] Throwable: java.net.UnknownHostException Throwable message: pfs
Sep 17, 2008 1:04:45 PM Error: An error occured while starting a cluster instance.
Sep 17, 2008 1:04:45 PM Error: There is no clutser control instance running on host Jupiter which is described in SecureStorage .
The instances, returned by MessageServer [MS host: Jupiter; MS port: 3901], are :
Name:JM_T1221672404781_2_penitus15
Host:PENITUS15
State:5
HostAddress:192.168.0.215
Name:JM_T1221679486171_0_Jupiter
Host:pfs
State:5
HostAddress:192.168.0.14
Name:JC_Jupiter_JTP_00
Host:pfs
State:5
HostAddress:192.168.0.14
Please check if there is an appropriate running cluster instances.
Sep 17, 2008 1:04:45 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Sep 17, 2008 1:04:45 PM Error: Aborted: development component 'ZIssueDatabase'/'local'/'LOKAL'/'0.2008.04.17.10.53.03'/'0':
SDM could not start the J2EE cluster on the host Jupiter! The online deployment is terminated.
There is no clutser control instance running on host Jupiter which is described in SecureStorage .
The instances, returned by MessageServer [MS host: Jupiter; MS port: 3901], are :
Name:JM_T1221672404781_2_penitus15
Host:PENITUS15
State:5
HostAddress:192.168.0.215
Name:JM_T1221679486171_0_Jupiter
Host:pfs
State:5
HostAddress:192.168.0.14
Name:JC_Jupiter_JTP_00
Host:pfs
State:5
HostAddress:192.168.0.14
Please check if there is an appropriate running cluster instances.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).STARTUP_CLUSTER)
Sep 17, 2008 1:04:45 PM Info: Starting to save the repository
Sep 17, 2008 1:04:46 PM Info: Finished saving the repository
Sep 17, 2008 1:04:47 PM Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.
Sep 17, 2008 1:04:47 PM Error: -
At least one of the Deployments failed -
Any help will be well received about this problema
Thk
Regards
DS

Problems with the examples in NWDS

Hi All,
Running the Welcome example project in NWDS i have the included error.
I have problems with other examples too.
I did all the step by step tutorials.
I have NWDS 2.0.3
         J2EE 6.40 SP15
         EP 2004
I am new in NWDS and i have not still successed to run any application.
What is wrong with my systems?
I did all the configurations start J2EE /sdm etc.
Do i have to install other versions? I read that maybe i have to install the same SP 15.
Please if anybody can help me .
Thanks,
Ari
Error Summary
While processing the current request, an exception occured which could not be handled by the application or the framework.
If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
Root Cause
The initial exception that caused the request to fail, was:
com.sap.tc.webdynpro.services.sal.deployment.api.WDClassLoaderException: Classloader of 'local/Welcome' is null, even though application is started.
at com.sap.tc.webdynpro.serverimpl.wdc.deployment.DeployableObject.getClassLoader(DeployableObject.java:81)
at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:588)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:248)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154)
... 18 more
Ari

Thank you for your help,
I have NWDS 2.0.3 and Web AS 6.40 SP15 and EP 04.
How can i be sure if are compatible? Maybe i have to install NWDS SP15?
I did "Rebuild" and then "Deploy new archive and run" Deploying i was asking for the sdm password , then the application opened in a new browser and we can see this message below.
The Deploy Output View is empty. There is no eny successful deploy message.
I appreciate your help.
Thanks,
Ari
500   Internal Server Error
Web Dynpro Container/SAP J2EE Engine/6.40
Failed to process request. Please contact your system administrator.
[Details...]
Error Summary
While processing the current request, an exception occured which could not be handled by the application or the framework.
If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
Root Cause
The initial exception that caused the request to fail, was:
   java.lang.InstantiationError: com.sap.tc.webdynpro.progmodel.context.NodeInfo
    at com.sap.examples.welcome.wdp.InternalWelcomeComponent.<init>(InternalWelcomeComponent.java:41)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
    at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
    ... 27 more
See full exception chain for details.
Correction Hints
The currently executed application, or one of the components it depends on, has been compiled against class file versions that are different from the ones that are available at runtime.
If the exception message indicates, that the modified class is part of the Web Dynpro Runtime (package com.sap.tc.webdynpro.*) then the running Web Dynpro Runtime is of a version that is not compatible with the Web Dynpro Designtime (Developer Studio or Component Build Server) which has been used to build + compile the application.
Note: the above hints are only a guess. They are automatically derived from the exception that occurred and therefore can't be guaranteed to address the original problem in all cases.
System Environment
Client
Web Dynpro Client Type HTML Client
User agent Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322)
Version
DOM version
Client Type msie6
Client Type Profile ie6
ActiveX enabled
Cookies enabled
Frames enabled
Java Applets enabled
JavaScript enabled
Tables enabled
VB Script enabled
Server
Web Dynpro Runtime Vendor: SAP, Build ID: 6.4015.00.0000.20051123162612.0000 (release=630_VAL_REL, buildtime=2005-12-14:21:51:22[UTC], changelist=377533, host=PWDFM026)
J2EE Engine No information available
Java VM Java HotSpot(TM) Server VM, version:1.4.2_07-b05, vendor: Sun Microsystems Inc.
Operating system Windows 2003, version: 5.2, architecture: x86
Other
Session Locale en_US
Time of Failure Fri Jan 26 14:29:31 EET 2007 (Java Time: 1169814571353)
Web Dynpro Code Generation Infos
local/Welcome
No information available
sap.com/tcwddispwda
No information available
sap.com/tcwdcorecomp
No information available
Detailed Error Information
Detailed Exception Chain
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to create delegate for component com.sap.examples.welcome.WelcomeComponent. (Hint: Is the corresponding DC deployed correctly? Does the DC contain the component?)
     at com.sap.tc.webdynpro.progmodel.generation.ControllerHelper.createDelegate(ControllerHelper.java:110)
     at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.<init>(DelegatingComponent.java:38)
     at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doInit(ClientComponent.java:776)
     at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:330)
     at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:370)
     at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:608)
     at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
     at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:248)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:48)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: java.lang.reflect.InvocationTargetException
     at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
     at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
     at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
     at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
     at com.sap.tc.webdynpro.progmodel.generation.ControllerHelper.createDelegate(ControllerHelper.java:74)
     ... 26 more
Caused by: java.lang.InstantiationError: com.sap.tc.webdynpro.progmodel.context.NodeInfo
     at com.sap.examples.welcome.wdp.InternalWelcomeComponent.<init>(InternalWelcomeComponent.java:41)
     ... 31 more

EP + BW: Problems with user mapping in the portal

Hi,
I'm trying to connect the portal with the BW by using the report RSPOR_SETUP which is a step-by-step guide. The steps #1 - #11 seems to be ok but my problem is the 12th step, the user mapping/allocation maintenance in the portal.
There is an error emerging (in BW): System failure during call of function module RSWR_RFC_SERVICE_TEST (System failure indicates normally an authentication problem between ABAP and Java)
Another error is emerging by testing the connection in the portal. (System administration u2013 system configuration u2013 system landscape u2013 connection test: the first connection, the SAP Web-AS connection is ok but the second, connection test for connector, is not working.
Especially the connection to the backend system with the defined connector is not working. The output is: u201CConnection failure. Check that single sign on is correct configured.
On step 12 of the step-by-step guide I have to select a user in the portal, relate him to a system alias und maintain his technical username and password for the BW. I think here is the problem. Iu2019m able to select and save a system alias for the user, but Iu2019m not able to save his technical username and password. There is another error emerging (in the portal): u201CVerification of user mapping data for system SAP_BW failed, check credentials for errorsu201D, so Iu2019m not able to save the username and password.
I think thats the my problem. the log file confirms that: "Did not find any existing logon data for principal...." & "No user mapping data available for principal...."
I hope my problem description is understandable.
Any ideas how I can solve the credentials problem to save the username and the password?
Thanks in advance.
Tan
Edited by: Tan Yildiz on Jul 22, 2009 1:26 PM

I could deploy some of the usage types, but there is an error regarding the BI-REPPLAN package. I think it's one of the very last errors that stands between me and a working EP - BI connection. There is a problem with the version. Could you check the log details, to find out more?
Thank you.
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[1.5.3.7185 - 630]/>
<!NAME[D:\usr\sap\BIP\JC02\SDM\program\log\sdmcl20090806164716.log]/>
<!PATTERN[sdmcl20090806164716.log]/>
<!FORMATTER[com.sap.tc.logging.TraceFormatter(%24d %s: %m)]/>
<!ENCODING[UTF8]/>
<!LOGHEADER[END]/>
Aug 6, 2009 6:47:16 PM   Info: -
Starting validation -
Aug 6, 2009 6:47:16 PM   Info: Prerequisite error handling strategy: OnPrerequisiteErrorSkipDepending
Aug 6, 2009 6:47:16 PM   Info: Update strategy: UpdateLowerOrChangedVersions
Aug 6, 2009 6:47:16 PM   Info: Starting deployment prerequisites:
Aug 6, 2009 6:47:18 PM   Info: Loading selected archives...
Aug 6, 2009 6:47:18 PM   Info: Loading archive 'D:\usr\sap\BIP\JC02\SDM\program\temp\BIREPPLAN04_0-10005889.SCA'
Aug 6, 2009 6:47:21 PM   Info: Selected archives successfully loaded.
Aug 6, 2009 6:47:21 PM   Error: Unresolved dependencies found for the following SDAs:
1.: development component 'bi/plan/helpers/table2'/'sap.com'/'MAIN_NW701P03_C'/'2846642'/'0'
dependency:
       name:     'bi/alv/common'
     vendor:     'sap.com'
There is no component either in SDM repository or in Deployment batch that resolves the dependency.
dependency:
       name:     'bi/alv/ui'
     vendor:     'sap.com'
There is no component either in SDM repository or in Deployment batch that resolves the dependency.
Deployment will be aborted.
Aug 6, 2009 6:47:21 PM   Error: No Software Component Archive (SCA) or Software Delivery Archive (SDA) selected. Select at least one.
Deployment will be aborted.
Aug 6, 2009 6:47:21 PM   Error: Prerequisites were aborted.
Aug 6, 2009 6:47:22 PM   Error: Error while creating deployment actions. No Software Component Archive (SCA) or Software Delivery Archive (SDA) selected. Select at least one.
Deployment will be aborted.
Aug 6, 2009 6:47:23 PM   Info: -
Ending validation -

Problem with Adaptive Web Service model

Hi All,
I am trying to create a model using Adaptive Webservice.
While I am deploying the application I am getting the following warning message.
I cheked the web serivice throw WSNavigator, It is working properlty.Nov 27, 2008 3:34:56 PM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] WARNING:
[040]Deployment finished with warning
Settings
SDM host : infpu05445
SDM port : 50118
URL to deploy : file:/C:/DOCUME1/286355/LOCALS1/Temp/temp62998testw.ear
Result
=> deployed with warning : file:/C:/DOCUME1/286355/LOCALS1/Temp/temp62998testw.ear
Finished with warnings: development component 'testw'/'local'/'LOKAL'/'0.2008.11.27.15.34.48':
Caught exception during application startup from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Error occurred while starting application local/testw and wait. Reason: Clusterwide exception: server ID 12403050:com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to prepare application ''local/testw'' for startup. Reason=Clusterwide exception: Failed to start dependent library ''tc/wd/wslib'' of application ''local/testw''. Status of dependent component: STATUS_MISSING. Hint: Is the component deployed correctly on the engine?
     at com.sap.engine.services.webdynpro.WebDynproContainer.prepareStart(WebDynproContainer.java:1490)
     at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:231)
     at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:179)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:301)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:317)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:111)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:227)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4684)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4589)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4562)
     at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1163)
     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:304)
     at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:193)
     at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:122)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment exception : Got problems during deployment
Can you all please let me know is the problem with model creatuion or Web Service configuration.
Thanks,
Archana.

It seams that the component 'tc/wd/wslib' is not well deployed on your server. You should redeploy it on your server.
-Go to nwds, Development infrastructure perspective
-Expand the FRAMEWORK item, there is the 'tc/wd/wslib' normally
Deploy :
-Open the menu Window > Show view > Other and open the Undeploy View
-In the undeploy view expand the FRAMWORK item and locate the tcwdwslib (it ther is no such application, then go directly to deploy steps after)
-Add the to the undeploy list (+ button)
-Click undeploy (blue button near + button
When it is undeployed, you can redploy it:
-In the Componenet Browser, locate the 'tc/wd/wslib' in the FRAMWORK as befor
-Right-click and click Deploy and click OK
If it not working, try the same (undeploy/dredploy) with 'tc/wd/wslib/api'
Check also that the dependencies of your project should have 'tc/wd/wslib/api' and not tc/wd/wslib/
Hope it will help you
Quentin

Online deployment with SDM

Hallo,
I have folloving problem with deploying SAPXITOOL SP14 L9.
When I started deploying there is a message that SAP WEB AS JAVA is currently stopped, but J2EE (dispatcher, server0 and SDM) is started. If SDM deploying part com.sap.aii.security.ws.proxy the SDM using online deploying.
Now there is a bad message:
Feb 24, 2006 8:23:49 AM Info: Software type of SDA: J2EE
Feb 24, 2006 8:23:49 AM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Feb 24, 2006 8:23:49 AM Info: Starting cluster instance processes.
Feb 24, 2006 8:23:49 AM Error: An error occured while starting a cluster instance.
Feb 24, 2006 8:23:49 AM Error: There is no control instance running in the cluster:
Name:JM_T1140765829632_smbxi2db
Host:smbxi2db
State:5
Please check if there are running cluster instances.
Feb 24, 2006 8:23:49 AM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Feb 24, 2006 8:23:49 AM Error: Aborted: development component 'com.sap.aii.security.ws.proxy'/'sap.com'/'SAP AG'/'3.0.1420060214105340.0000':
SDM could not start the J2EE cluster on the host smbxi2db! The online deployment is terminated.
There is no control instance running in the cluster:
Name:JM_T1140765829632_smbxi2db
Host:smbxi2db
State:5
Please check if there are running cluster instances.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).STARTUP_CLUSTER)
Feb 24, 2006 8:23:52 AM Error: An error occured while restoring the cluster instances states
Feb 24, 2006 8:23:52 AM Error: There is no control instance running in the cluster:
Name:JM_T1140765832130_smbxi2db
Host:smbxi2db
State:5
Please check if there are running cluster instances.
Feb 24, 2006 8:23:52 AM Error: Received exception when restoring Engine state: There is no control instance running in the cluster:
Name:JM_T1140765832130_smbxi2db
Host:smbxi2db
State:5
Please check if there are running cluster instances.
Can you somebody help me to resolve this problem?
Thanks
Martin Capek

Please check if "smbxi2db" is the JAVA CI host . If not maintain correct host in secstore.
Configtool-> Secure Store -> admin/host/<SID> (JAVA CI host, Not DB host)

Can't undeploy with SDM?

I've got a very strange problem with the SDM tool. When I start it up and login, the 'SDM Repository' tab shows all the deployed modules. However, when I click on the undeployment tab, I don't see any modules - in fact, the screen is completely blank. If I try to click on the 'SDM Repository' tab again, it displays the various target systems and deployments, but I get the hourglass, with the message 'Loading flow file from server', and status 'Working' - at this point I can't click on any of the tabs, as it seems that the application has locked up.
I therefore can't undeploy any modules. This is not good!
I have used the Undeployment feature before, so it was
working at one point.
Anyone have any suggestions? I've perused all the SDM log files, but there are no errors in any of the files. I've also done the standard Windows problem resolution technique - I've rebooted my server. No effect.
Help!

My issue with undeploying via the SDM was related to multiple deployment descriptors in the SDM.
If the SDM is hanging when you attempt to undeploy, check the SDM log files, either at:
/usr/sap/<SID>/<instanceID>/work/jvm_sdm.out
or in the last SDM log in the directory
/usr/sap/<SID>/<instanceID>/SDM/program/log/
For an error like this:
"java.lang.IllegalStateException: More than one matching deployment for development component..."
or
"java.lang.IndexOutOfBoundsException: Index: X, Size: Y"
If you see errors like this, the SDM likely thinks there are multiple copies of a deployed component.
To determine the culprit, check the <DeploymentContainer> in the SDM repository at:
/usr/sap/<SID>/<INSTANCE>/SDM/program/config/sdmrepository.sdc
Search inside the <DeploymentID> tags for a component with value of 2 or greater. Remove all but the latest <DeploymentID> tag for the component, and restart the SDM. The component will now (hopefully) undeploy.
You can see SAP Note 824357 for more details on this solution too.
Thanks,
-- Alex

Printing problems with CS4.

Dear members:
After several attempts to print black-and-white photos in Photoshop CS4 I decided to give up and seek help.
I have followed the steps I believe are the right ones and the same I have used before with previous versions of Photoshop. First I applied the command Image > Adjustments > Black & White ... and my color photo became black-and-white on screen. I made an attempt to print but the print came out looking blueish (as if it had some kind of blue duotone applied to it). Second I tried the same settings and also set the printer (an Epson R 1800 photo printer) to black instead of color. Again the same result. In my last attempt I converted the image using the same command above (Image > Adjustments > Black & White ...), then I used the command Image > Adjustments > Desaturate and after that I applied the command Image > Mode > Grayscale. In addition to all these steps I also entered black in the printer dialog box instead of color. Still the print came out blueish just as it had before.
What must one do to "convince" Photoshop to print a color photo as a true black-and-white image ?
Thank you in advance for your help.
Joseph

Thanks Milenium. I appreciate your response. Yes I do work in RGB. The profile is sRGB IEC 61966-2.1( The same as for all the photos) The monitor profile (Sony SDM-HS95P-DVI-D) is set at the system as well as the HP printer profile. I would like to update what has happened since my last post:
I reinstalled CS3 and installed a Canon Pixima 9000. The Cannon was just as much a mess as the HP vibrant colors and dark muddy prints, but the Canon had another problem...It was shifting red-magenta to yellow -orange However what I learned is that CS3 and CS4 were sharing some functions and settings even though I had the syncronization function turned off I.E, color settings, and working space. I couldn't bother with the Canon and since it was a loaner I took it out of the equationfor the time being. Next I read a post from 2004 on some web site from folks who were having similar problems with CS3 and HP printers( I never had a problem with this combo and as previously mentioned I do a great deal of wide printing with pretty good gosh darn results) Howerer, a poster said that she went into the system printer profile and deleted any profile there, then set up CS3 with no color management, and set the print function on the HP at application managed color( which she believed to be HP's no color management at the printer if if no color management is selected in photoshop. KInd of makes sense,she attained a 90% improvement in her prints. Well I gave it a shot and set everything up just as she suggested including the deleting of all the system printer files and got the same results as she did in back in 2004. A step foward I hope. If you have any other suggestions please let me know. My next step would be to remove Design Premium and see if that has any effect on restoring CS3 to it's previous standard vanilla set up of let the printer manage the color with the sRGB IEC 61966-2 profile.
Message was edited by: lexabob rgb profile error correct is now in text sRGB IEC 61966-2

Error Deployment file CAF-UM with SDM

HI All
I have a problem in the SDM when I deployment the file CAF-UM I got this message:
Unresolved dependencies found for the following SDAs:
1.: development component 'caf/um/relgroups/admin'/'sap.com'/'MAIN_APL70VAL_C'/'963666'/'1'
dependency:
name: 'tc/wd/webdynpro'
vendor: 'sap.com'
There is no component either in SDM repository or in Deployment batch that resolves the dependency.
Deployment will be aborted.
What's the problem ?
Thanks
Regards
DS

Hi,
There might be some dependencies, Are you upgrading from 6 to 11 there are some problems with these
patches, Try to apply the stack.
Regards,
Vamshi.

SOLMAN 7.0 problem with Stack16-question on note#1231975

SOLMAN 7.0 problem with Stack16-question on note#1231975
I'm importing Stacks 16&17 into our Solution Manager 7.0 system
and getting errors when importing the Java part in JSPM after the ABAP
went in with no errors. The error matches OSS note 1231975 but we are
having problems understanding what this note is advising to fix the
issue. "SAPJTECHS SP16 component needs to be applied before proceeding
with the whole SP16 stack. It should fix the usages on the systems
fixing missing rows at BC_SL_PARTS table." Each time we start JSPM it
gives the errors mentioned in this note. How are we to import
SAPJTECHS before the rest of the Java Support Packs if we can't get
JSPM to come up due to this error? About half of the Java Support
Packs were imported before this error occured.

You can deploy that component manually using SDM (instead of JSPM).
Markus

A problem with threads

I am trying to implement some kind of a server listening for requests. The listener part of the app, is a daemon thread that listens for connections and instantiates a handling daemon thread once it gets some. However, my problem is that i must be able to kill the listening thread at the user's will (say via a sto button). I have done this via the Sun's proposed way, by testing a boolean flag in the loop, which is set to false when i wish to kill the thread. The problem with this thing is the following...
Once the thread starts excecuting, it will test the flag, find it true and enter the loop. At some point it will LOCK on the server socket waiting for connection. Unless some client actually connects, it will keep on listening indefinatelly whithought ever bothering to check for the flag again (no matter how many times you set the damn thing to false).
My question is this: Is there any real, non-theoretical, applied way to stop thread in java safely?
Thank you in advance,
Lefty

This was one solution from the socket programming forum, have you tried this??
public Thread MyThread extends Thread{
     boolean active = true;
     public void run(){
          ss.setSoTimeout(90);
          while (active){
               try{
                    serverSocket = ss.accept();
               catch (SocketTimeoutException ste){
               // do nothing
     // interrupt thread
     public void deactivate(){
          active = false;
          // you gotta sleep for a time longer than the
          // accept() timeout to make sure that timeout is finished.
          try{
               sleep(91);
          }catch (InterruptedException ie){
          interrupt();
}

Problem with Threads and a static variable

I have a problem with the code below. I am yet to make sure that I understand the problem. Correct me if I am wrong please.
Code functionality:
A timer calls SetState every second. It sets the state and sets boolean variable "changed" to true. Then notifies a main process thread to check if the state changed to send a message.
The problem as far I understand is:
Assume the timer Thread calls SetState twice before the main process Thread runs. As a result, "changed" is set to true twice. However, since the main process is blocked twice during the two calls to SetState, when it runs it would have the two SetState timer threads blocked on its synchronized body. It will pass the first one, send the message and set "changed" to false since it was true. Now, it will pass the second thread, but here is the problem, "changed" is already set to false. As a result, it won't send the message even though it is supposed to.
Would you please let me know if my understanding is correct? If so, what would you propose to resolve the problem? Should I call wait some other or should I notify in a different way?
Thanks,
B.D.
Code:
private static volatile boolean bChanged = false;
private static Thread objMainProcess;
   protected static void Init(){
        objMainProcess = new Thread() {
            public void run() {
                while( objMainProcess == Thread.currentThread() ) {
                   GetState();
        objMainProcess.setDaemon( true );
        objMainProcess.start();
    public static void initStatusTimer(){
        if(objTimer == null)
             objTimer = new javax.swing.Timer( 1000, new java.awt.event.ActionListener(){
                public void actionPerformed( java.awt.event.ActionEvent evt){
                          SetState();
    private static void SetState(){
        if( objMainProcess == null ) return;
        synchronized( objMainProcess ) {
            bChanged = true;
            try{
                objMainProcess.notify();
            }catch( IllegalMonitorStateException e ) {}
    private static boolean GetState() {
        if( objMainProcess == null ) return false;
        synchronized( objMainProcess ) {
            if( bChanged) {
                SendMessage();
                bChanged = false;
                return true;
            try {
                objMainProcess.wait();
            }catch( InterruptedException e ) {}
            return false;
    }

Thanks DrClap for your reply. Everything you said is right. It is not easy to make them alternate since SetState() could be called from different places where the state could be anything else but a status message. Like a GREETING message for example. It is a handshaking message but not a status message.
Again as you said, There is a reason I can't call sendMessage() inside setState().
The only way I was able to do it is by having a counter of the number of notifies that have been called. Every time notify() is called a counter is incremented. Now instead of just checking if "changed" flag is true, I also check if notify counter is greater than zero. If both true, I send the message. If "changed" flag is false, I check again if the notify counter is greater than zero, I send the message. This way it works, but it is kind of a patch than a good design fix. I am yet to find a good solution.
Thanks,
B.D.

Problem with threads running javaw

Hi,
Having a problem with multi thread programming using client server sockets. The program works find when starting the the application in a console using java muti.java , but when using javaw multi.java the program doesnt die and have to kill it in the task manager. The program doesnt display any of my gui error messages either when the server disconnect the client. all works find in a console. any advice on this as I havent been able to understand why this is happening? any comment would be appreciated.
troy.

troy,
Try and post a minimum code sample of your app which
does not work.
When using javaw, make sure you redirect the standard
error and standard output streams to file.
Graeme.Hi Graeme,
I dont understand what you mean by redirection to file? some of my code below.
The code works fine under a console, code is supposed to exit when the client (the other server )disconnects. the problem is that but the clientworker side of the code still works. which under console it doesnt.
public class Server{
ServerSocket aServerSocket;
Socket dianosticsSocket;
Socket nPortExpress;
ClientListener aClientListener;
LinkedList queue = new LinkedList();
int port = 0;
int clientPort = 0;
String clientName = null;
boolean serverAlive = true;
* Server constructor generates a server
* Socket and then starts a client threads.
* @param aPort      socket port of local machine.
public Server(int aPort, String aClientName, int aClientPort){
port = aPort;
clientName = aClientName;
clientPort = aClientPort;
try{
// create a new thread
aServerSocket = new ServerSocket(port) ;
// connect to the nPortExpress
aClientListener = new ClientListener(InetAddress.getByName(clientName), clientPort, queue,this);
// aClientListener.setDaemon(true);
aClientListener.start();
// start a dianostic port
DiagnosticsServer aDiagnosticsServer = new DiagnosticsServer(port,queue,aClientListener);
// System.out.println("Server is running on port " + port + "...");
// System.out.println("Connect to nPort");
catch(Exception e)
// System.out.println("ERROR: Server port " + port + " not available");
JOptionPane.showMessageDialog(null, (e.toString()),"ERROR: Server port " + port + " not available", JOptionPane.ERROR_MESSAGE);
serverAlive = false;
System.exit(1);
while(serverAlive&&aClientListener.hostSocket.isConnected()){
try{
// connect the client
Socket aClient = aServerSocket.accept();
//System.out.println("open client connection");
//System.out.println("client local: "+ aClient.getLocalAddress().toString());
// System.out.println("client localport: "+ aClient.getLocalPort());
// System.out.println("client : "+ aClient.getInetAddress().toString());
// System.out.println("client port: "+ aClient.getLocalPort());
// make a new client thread
ClientWorker clientThread = new ClientWorker(aClient, queue, aClientListener, false);
// start thread
clientThread.start();
catch(Exception e)
//System.out.println("ERROR: Client connection failure");
JOptionPane.showMessageDialog(null, (e.toString()),"ERROR: Client connection failure", JOptionPane.ERROR_MESSAGE);
}// end while
} // end constructor Server
void serverExit(){
     JOptionPane.showMessageDialog(null, "Server ","ERROR: nPort Failure", JOptionPane.ERROR_MESSAGE);
     System.exit(1);
}// end class Server
*** connect to another server
public class ClientListener extends Thread{
InetAddress hostName;
int hostPort;
Socket hostSocket;
BufferedReader in;
PrintWriter out;
boolean loggedIn;
LinkedList queue;      // reference to Server queue
Server serverRef; // reference to main server
* ClientListener connects to the host server.
* @param aHostName is the name of the host eg server name or IP address.
* @param aHostPort is a port number of the host.
* @param aLoginName is the users login name.
public ClientListener(InetAddress aHostName, int aHostPort,LinkedList aQueue,Server aServer)      // reference to Server queue)
hostName = aHostName;
hostPort = aHostPort;
queue = aQueue;
serverRef = aServer;
// connect to the server
try{
hostSocket = new Socket(hostName, hostPort);
catch(IOException e){
//System.out.println("ERROR: Connection Host Failed");
JOptionPane.showMessageDialog(null, (e.toString()),"ERROR: Connection to nPort Failed", JOptionPane.ERROR_MESSAGE);
System.exit(0);
} // end constructor ClientListener
** multi client connection server
ClientWorker(Socket aSocket,LinkedList aQueue, ClientListener aClientListener, boolean diagnostics){
queue = aQueue;
addToQueue(this);
client = aSocket;
clientRef = aClientListener;
aDiagnostic = diagnostics;
} // end constructor ClientWorker
* run method is the main loop of the server program
* in change of handle new client connection as well
* as handle all messages and errors.
public void run(){
boolean alive = true;
String aSubString = "";
in = null;
out = null;
loginName = "";
loggedIn = false;
while (alive && client.isConnected()&& clientRef.hostSocket.isConnected()){
try{
in = new BufferedReader(new InputStreamReader(client.getInputStream()));
out = new PrintWriter(new OutputStreamWriter(client.getOutputStream()));
if(aDiagnostic){
out.println("WELCOME to diagnostics");
broadCastDia("Connect : diagnostics "+client.getInetAddress().toString());
out.flush();
else {
out.println("WELCOME to Troy's Server");
broadCastDia("Connect : client "+client.getInetAddress().toString());
     out.flush();
String line;
while(((line = in.readLine())!= null)){
StringTokenizer aStringToken = new StringTokenizer(line, " ");
if(!aDiagnostic){
broadCastDia(line);
clientRef.sendMessage(line); // send mesage out to netExpress
out.println(line);
out.flush();
else{
if(line.equals("GETIPS"))
getIPs();
else{
clientRef.sendMessage(line); // send mesage out to netExpress
out.println(line);
out.flush();
} // end while
catch(Exception e){
// System.out.println("ERROR:Client Connection reset");
                         JOptionPane.showMessageDialog(null, (e.toString()),"ERROR:Client Connection reset", JOptionPane.ERROR_MESSAGE);
try{
if(aDiagnostic){
broadCastDia("Disconnect : diagnostics "+client.getInetAddress().toString());
out.flush();
else {
broadCastDia("Disconnect : client "+client.getInetAddress().toString());
     out.flush();
// close the buffers and connection;
in.close();
out.close();
client.close();
// System.out.println("out");
// remove from list
removeThreadQueue(this);
alive = false;
catch(Exception e){
// System.out.println("ERROR: Client Connection reset failure");
JOptionPane.showMessageDialog(null, (e.toString()),"ERROR: Client Connection reset failure", JOptionPane.ERROR_MESSAGE);
}// end while
} // end method run
* method run - Generates io stream for communicating with the server and
* starts the client gui. Run also parses the input commands from the server.
public void run(){
boolean alive = true;
try{
// begin to life the gui
// aGuiClient = new ClientGui(hostName.getHostName(), hostPort, loginName, this);
// aGuiClient.show();
in = new BufferedReader(new InputStreamReader(hostSocket.getInputStream()));
out = new PrintWriter(new OutputStreamWriter(hostSocket.getOutputStream()));
while (alive && hostSocket.isConnected()){
String line;
while(((line = in.readLine())!= null)){
System.out.println(line);
broadCast(line);
} // end while
} // end while
catch(Exception e){
//     System.out.println("ERRORa Connection to host reset");
JOptionPane.showMessageDialog(null, (e.toString()),"ERROR: Connection to nPort reset", JOptionPane.ERROR_MESSAGE);
try{
hostSocket.close();
     }catch(Exception a){
     JOptionPane.showMessageDialog(null, (a.toString()),"ERROR: Exception", JOptionPane.ERROR_MESSAGE);
alive = false;
System.exit(1);
} // end method run

Problem with SDM

Similar Messages

Maybe you are looking for