*** WARNING: Could not start service 80 for protocol HTTP on host MyFQDN

Hi,
I m configuring an external Sap webdispatcher to point to an ICF service
I need to install it on Windows Web server where others web sites are running.
I configured a specific ip for that on the Web servers and enter the DNS name in our domain.
On the the pfl file I define :
SAPLOCALHOSTFULL=<MyFQDN>
icm/host_name_full =<MyFQDN>
and specify icm/server_port_0 = PROT=HTTP,PORT=80
Each time I m starting it I received *** WARNING: Could not start service 80 for protocol HTTP on host <MyFQDN> .........
If I m using another port (Ex:86)no problem with my FQDN.But if I m doing servername:86 it s working also.
It s seems that the webdispatcher don t care about my FQDN.
How can I have the WEBDISPATCHER pointing to this specific FQDN and not all ?
Thanks,

Hi Damien,
You problem is perfectly logical : It's not possible to have 2 programs (IIS and web dispatcher) listening together on the same 80 HTTP port.
There is no configuration that I know on the web dispatcher to tell him to listen only on one IP address.
Summary : what you want to do is not possible.
I had a similar request and I did the following.
I use a Linux box with an Apache reverse proxy to select to distribute the HTTP requests on different web dispatchers. The rules depends from the called URLs.
Regards,
Olivier

Similar Messages

Could not start Service Broker for database id

I am getting this message in the SQL Server error log:
Could not start Service Broker for database id: 10. A problem is preventing SQL Server from starting Service Broker. Check the SQL Server error log for additional messages.
It appears even when the broker is disabled on the database. How can I eliminate this error?
Thanks!

In that case you're gonna have to contact Microsoft support, perhaps provide a copy of the database.
Typical reason why a broker cannot be started is that another database with the same service_broker_guid already exists in the instance (result of a file copy/attach or a double restore). However, in that case a message is given that states the reason.

Could not start Service Broker for database

Problem:
Could not start Service Broker for database id: 9. A problem is preventing SQL Server from starting Service Broker. Check the SQL Server error log for additional messages.
The windows and application logs do not give me any for information. I have checked the database instance and found that Database ID 9 does not exist in the sys.databases table. Could this be the reason?
How do I resolve it so that SQL Server does not try and start Service broker for a database ID that does not exist?
Any help will be greatly appreciated.
Thanks.

Hello Affy
Solution/Fix: To avoid this alert, I have set the "Enable Disaster Recovery File Updates" parameter to 0 in the regedit at the below location.
MY Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Backup Exec For Windows\Backup Exec\Engine\SQL Server
For furher details you can refer my blog.
Regards,
Naveen Kumar Thandra

Error: Could not start Service[keystone]: Execution of '/sbin/service openstack-keystone start' returned 1: Starting keystone: [FAILED]

I'm using Oracle Linux 6u6. While I'm installing openstack ( 2 node set up) using packstack, I'm getting this error:
Applying 10.245.33.37_cinder.pp
10.245.33.37_keystone.pp:                         [ ERROR ]
Applying Puppet manifests                         [ ERROR ]
ERROR : Error appeared during Puppet run: 10.245.33.37_keystone.pp
Error: Could not start Service[keystone]: Execution of '/sbin/service openstack-keystone start' returned 1: Starting keystone: [FAILED]
You will find full trace in log /var/tmp/packstack/20150327-100335-ltC8Ic/manifests/10.245.33.37_keystone.pp.log
Please check log file /var/tmp/packstack/20150327-100335-ltC8Ic/openstack-setup.log for more information
Additional information:
* A new answerfile was created in: /root/packstack-answers-20150327-100336.txt
* Time synchronization installation was skipped. Please note that unsynchronized time on server instances might be problem for some OpenStack components.
* Did not create a cinder volume group, one already existed
* File /root/keystonerc_admin has been created on OpenStack client host 10.245.33.37. To use the command line tools you need to source the file.
* To access the OpenStack Dashboard browse to http://10.245.33.37/dashboard .
Please, find your login credentials stored in the keystonerc_admin in your home directory.
Packages:
[root@slcai461 ~]# rpm -qa|grep keystone
python-keystoneclient-0.9.0-5.el6.noarch
python-keystone-2014.1.3-2.el6.noarch
openstack-keystone-2014.1.3-2.el6.noarch
[root@slcai461 ~]# rpm -qa|grep packstack
openstack-packstack-puppet-2014.1.1-0.12.dev1068.0.4.el6.noarch
openstack-packstack-2014.1.1-0.12.dev1068.0.4.el6.noarch
Log :
[root@slcai461 ~]# cat /var/tmp/packstack/20150327-100335-ltC8Ic/manifests/10.245.33.37_keystone.pp.log
Warning: Config file /etc/puppet/hiera.yaml not found, using Hiera defaults
Warning: Scope(Class[Keystone]): The sql_connection parameter is deprecated, use database_connection instead.
Warning: Scope(Class[Keystone]): token_format parameter is deprecated. Use token_provider instead.
Warning: Scope(Class[Keystone::Endpoint]): The public_address parameter is deprecated, use public_url instead.
Warning: Scope(Class[Keystone::Endpoint]): The internal_address parameter is deprecated, use internal_url instead.
Warning: Scope(Class[Keystone::Endpoint]): The admin_address parameter is deprecated, use admin_url instead.
Warning: Scope(Class[Nova::Keystone::Auth]): The cinder parameter is deprecated and has no effect.
Notice: Compiled catalog for slcai461.us.oracle.com in environment production in 1.60 seconds
Warning: The package type's allow_virtual parameter will be changing its default value from false to true in a future release. If you do not want to allow virtual packages, please explicitly set allow_virtual to false.
   (at /usr/lib/ruby/site_ruby/1.8/puppet/type.rb:816:in `set_default')
Notice: /Stage[main]/Keystone/Keystone_config[DEFAULT/admin_token]/value: value changed '[old secret redacted]' to '[new secret redacted]'
Notice: /Stage[main]/Keystone/Keystone_config[database/connection]/value: value changed '[old secret redacted]' to '[new secret redacted]'
Notice: /Stage[main]/Keystone::Db::Sync/Exec[keystone-manage db_sync]: Triggered 'refresh' from 3 events
Notice: /Stage[main]/Keystone/Exec[keystone-manage pki_setup]: Triggered 'refresh' from 2 events
Error: Could not start Service[keystone]: Execution of '/sbin/service openstack-keystone start' returned 1: Starting keystone: [FAILED]
Wrapped exception:
Execution of '/sbin/service openstack-keystone start' returned 1: Starting keystone: [FAILED]
Error: /Stage[main]/Keystone::Service/Service[keystone]/ensure: change from stopped to running failed: Could not start Service[keystone]: Execution of '/sbin/service openstack-keystone start' returned 1: Starting keystone: [FAILED]
Notice: /Stage[main]/Keystone::Service/Service[keystone]: Triggered 'refresh' from 5 events
Notice: /Stage[main]/Neutron::Keystone::Auth/Keystone_service[neutron]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Neutron::Keystone::Auth/Keystone_service[neutron]: Skipping because of failed dependencies
Notice: /Stage[main]/Keystone::Roles::Admin/Keystone_tenant[admin]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Keystone::Roles::Admin/Keystone_tenant[admin]: Skipping because of failed dependencies
Notice: /Stage[main]/Nova::Keystone::Auth/Keystone_service[nova_ec2]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Nova::Keystone::Auth/Keystone_service[nova_ec2]: Skipping because of failed dependencies
Notice: /Stage[main]/Cinder::Keystone::Auth/Keystone_service[cinderv2]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Cinder::Keystone::Auth/Keystone_service[cinderv2]: Skipping because of failed dependencies
Notice: /Stage[main]/Nova::Keystone::Auth/Keystone_service[novav3]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Nova::Keystone::Auth/Keystone_service[novav3]: Skipping because of failed dependencies
Notice: /Stage[main]/Keystone::Roles::Admin/Keystone_tenant[services]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Keystone::Roles::Admin/Keystone_tenant[services]: Skipping because of failed dependencies
Notice: /Stage[main]/Neutron::Keystone::Auth/Keystone_user[neutron]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Neutron::Keystone::Auth/Keystone_user[neutron]: Skipping because of failed dependencies
Notice: /Stage[main]/Nova::Keystone::Auth/Keystone_user[nova]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Nova::Keystone::Auth/Keystone_user[nova]: Skipping because of failed dependencies
Notice: /Stage[main]/Glance::Keystone::Auth/Keystone_user[glance]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Glance::Keystone::Auth/Keystone_user[glance]: Skipping because of failed dependencies
Notice: /Stage[main]/Keystone::Roles::Admin/Keystone_role[admin]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Keystone::Roles::Admin/Keystone_role[admin]: Skipping because of failed dependencies
Notice: /Stage[main]/Glance::Keystone::Auth/Keystone_user_role[glance@services]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Glance::Keystone::Auth/Keystone_user_role[glance@services]: Skipping because of failed dependencies
Notice: /Stage[main]/Keystone::Endpoint/Keystone_service[keystone]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Keystone::Endpoint/Keystone_service[keystone]: Skipping because of failed dependencies
Error: Could not prefetch keystone_endpoint provider 'keystone': Execution of '/usr/bin/keystone --os-endpoint http://127.0.0.1:35357/v2.0/ endpoint-list' returned 1: An unexpected error prevented the server from fulfilling your request. (HTTP 500)
Notice: /Stage[main]/Keystone::Endpoint/Keystone_endpoint[RegionOne/keystone]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Keystone::Endpoint/Keystone_endpoint[RegionOne/keystone]: Skipping because of failed dependencies
Notice: /Stage[main]/Main/Keystone_service[cinder_v2]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Main/Keystone_service[cinder_v2]: Skipping because of failed dependencies
Notice: /Stage[main]/Main/Keystone_endpoint[RegionOne/cinder_v2]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Main/Keystone_endpoint[RegionOne/cinder_v2]: Skipping because of failed dependencies
Notice: /Stage[main]/Nova::Keystone::Auth/Keystone_endpoint[RegionOne/novav3]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Nova::Keystone::Auth/Keystone_endpoint[RegionOne/novav3]: Skipping because of failed dependencies
Notice: /Stage[main]/Cinder::Keystone::Auth/Keystone_service[cinder]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Cinder::Keystone::Auth/Keystone_service[cinder]: Skipping because of failed dependencies
Notice: /Stage[main]/Cinder::Keystone::Auth/Keystone_endpoint[RegionOne/cinder]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Cinder::Keystone::Auth/Keystone_endpoint[RegionOne/cinder]: Skipping because of failed dependencies
Notice: /Stage[main]/Glance::Keystone::Auth/Keystone_service[glance]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Glance::Keystone::Auth/Keystone_service[glance]: Skipping because of failed dependencies
Notice: /Stage[main]/Glance::Keystone::Auth/Keystone_endpoint[RegionOne/glance]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Glance::Keystone::Auth/Keystone_endpoint[RegionOne/glance]: Skipping because of failed dependencies
Notice: /Stage[main]/Nova::Keystone::Auth/Keystone_user_role[nova@services]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Nova::Keystone::Auth/Keystone_user_role[nova@services]: Skipping because of failed dependencies
Notice: /Stage[main]/Keystone::Roles::Admin/Keystone_user[admin]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Keystone::Roles::Admin/Keystone_user[admin]: Skipping because of failed dependencies
Notice: /Stage[main]/Keystone::Roles::Admin/Keystone_user_role[admin@admin]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Keystone::Roles::Admin/Keystone_user_role[admin@admin]: Skipping because of failed dependencies
Notice: /Stage[main]/Cinder::Keystone::Auth/Keystone_user[cinder]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Cinder::Keystone::Auth/Keystone_user[cinder]: Skipping because of failed dependencies
Notice: /Stage[main]/Nova::Keystone::Auth/Keystone_endpoint[RegionOne/nova_ec2]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Nova::Keystone::Auth/Keystone_endpoint[RegionOne/nova_ec2]: Skipping because of failed dependencies
Notice: /Stage[main]/Cinder::Keystone::Auth/Keystone_endpoint[RegionOne/cinderv2]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Cinder::Keystone::Auth/Keystone_endpoint[RegionOne/cinderv2]: Skipping because of failed dependencies
Notice: /Stage[main]/Nova::Keystone::Auth/Keystone_service[nova]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Nova::Keystone::Auth/Keystone_service[nova]: Skipping because of failed dependencies
Notice: /Stage[main]/Nova::Keystone::Auth/Keystone_endpoint[RegionOne/nova]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Nova::Keystone::Auth/Keystone_endpoint[RegionOne/nova]: Skipping because of failed dependencies
Notice: /Stage[main]/Neutron::Keystone::Auth/Keystone_user_role[neutron@services]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Neutron::Keystone::Auth/Keystone_user_role[neutron@services]: Skipping because of failed dependencies
Notice: /Stage[main]/Neutron::Keystone::Auth/Keystone_endpoint[RegionOne/neutron]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Neutron::Keystone::Auth/Keystone_endpoint[RegionOne/neutron]: Skipping because of failed dependencies
Notice: /Stage[main]/Cinder::Keystone::Auth/Keystone_user_role[cinder@services]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Cinder::Keystone::Auth/Keystone_user_role[cinder@services]: Skipping because of failed dependencies
Notice: Finished catalog run in 3.10 seconds
Please let me know how to fix this.

This problem connected with proxy-setings.
As the first steps you should try:
       1. export system env variable:
http_proxy=http://www-proxy.ru.oracle.com:80
https_proxy=https://www-proxy.ru.oracle.com:80
no_proxy=127.0.0.1,localhost
and you can also export
    export OS_TENANT_NAME=admin
    export OS_USERNAME=admin
    export OS_PASSWORD=root
    export OS_AUTH_URL=http://<conntroller_IP>:5000/v2.0/
2. and than restart mysqld, if it is running, stop iptables and repeat installation process from beginning with the currently generated answer file
if we are exporting variable OS_PASSWORD, its value should be the same as value for CONFIG_KEYSTONE_ADMIN_PW in the currently generated answer file.
This OS_PASSWORD will be written by packstack in the /root/keystonerc_admin file and will be used as admin's password for login to Openstack dashboard.

ServiceLayer - Could not start service

Hello,
I've just bought Nokia N95 8GB and wanted to install Nokia PC Suite. When installing PC Connectivity Solution there was a window message with title ServiceLayer and text "Could not start service". Afterwards, installation continued and finished "succesfully". Unfortunately I have problem that was posted a few times. I can't connect phone to PC Suite. I tried to Repair PC Connectivity solution, uninstall this and Cable driver and repair Nokia PC Suite, uninstall everything and use later Nokia cleaner etc. Nothing worked. When I go to PC Connectivity Solution and run manually ServiceLayer.exe I get the same message, that "Could not start service". What should I do? Please help me. I do not want to format my HDD and install Windows from the beginning. I use WinXP SP2.

Hi,
I've found the cause of the problem. It was firewall - Agnitum Outpost Personal Firewall Pro. I had old version and after installing new version the message dissapeared. As You can see below - one of issues solved was the problem "Outpost Firewall could block installation of services".
"Outpost Firewall Pro 2008 (build 6.0.2172.214.422.270)
Release date: November 14, 2007
The following issues are resolved (only significant ones are listed):
* Outpost monitor and Outpost Feedback were not registered in startup entries
* Outpost Firewall could block installation of services
* Information about crashes could not be sent to Agnitum
* Rules autocreation did not work on 64-bit systems for applications from ProgramFiles (x86) and SysWOW64 folders
* Most commonly reported crashes (including crash on content filtering)
* Error 14001 during installation
* Rules were applied incorrectly in some cases
* Address macros could be incorrectly resolved in rules
* Leaktests SPT 15 and SPT 16 were failed on Vista64
* Error while importing LAN settings from Outpost Firewall 4.0
* Web pages content could be blocked/corrupted (GZIP decoding issue)
* Outpost Firewall now cannot be installed over Outpost Security Suite"
But now I have different problem - I can't download update of PC Suite. The download starts and it stops when the progress bar is in its way. Sometimes it goes to the end but the installation doesn't start. What could be the problem?

I got this error: following error: Warning: Can not start service RTCMEDIARELAY on computer

I am installing an edge server, when I start the services, enter the following error:
Warning: Can not start service RTCMEDIARELAY on computer. and only start two services,
Lync Rerver Replica Replicator agent and Lync Server Web Conferencing Edge.
my lync server is version 2010.
If you need more details, do it know.
Greetings.

Here are some similar threads you can refer to:
http://social.technet.microsoft.com/Forums/lync/en-US/2db2ef0b-7d4f-4908-a0c5-d5de5822d9cf/edge-server-services-not-starting
http://social.technet.microsoft.com/Forums/lync/en-US/1544fd15-5a60-47f0-9793-c68d6db030d6/warning-cannot-start-service-rtcmediarelay
Lisa Zheng
TechNet Community Support

Deployment SDM could not start the J2EE Cluster on the host nw4host

Hello,
I installed the WAS testdrive on Linux SUSE 9.3 and the SNDS on WinXP.
I am trying to deploy the welcome application from the SNDS and get the following error message:
SDM could not start the J2ee Cluster on the host nw4host! The online deployment is terminated. JStartup Framework ist not able to deliver an information about the cluster control instances! Please check the status of the J2EE Engine.
I can start the J2EE Start page on port 50000, the system info shows that dispatcher, server0 and SDM are running. I can start the visual admin with go, the SDM with RemoteGui and the DeployTool.
The comand startsap check nw4host shows, everythings running:
nw4host:nw4adm 54> startsap check nw4host
Checking ADA db Database
ABAP Database is running
Checking ADA db Database
J2EE Database is running
See logfile JdbcCon.log
Checking SAP NW4 Instance SCS01
Instance SCS01 is running
Checking SAP NW4 Instance DVEBMGS00
Instance DVEBMGS00 is running
Logging in to SAP with the Java Gui, the ICM says:
ABAP Server operational        = TRUE
J2EE Server configured         = FALSE
J2EE HTTP port                 = 50000
J2EE HTTPS port                = 50001
J2EE Server operational        = TRUE
Default root access handler    = ABAP
URL Prefix Table loaded        = TRUE
Any idea where the problem could be ?
Thanks, Manfred.

changed the ip address for nw4host in etc/hosts to the real ip address of the server where application runs

SDM could not start the J2EE cluster on the host Error on Deployments

Hi,
We are sudenly getting this Error when trying to make a Deployment in the NWDE:
Settings
SDM host : 10.26.26.198
SDM port : 50018
URL to deploy : file:/C:/DOCUME1/ALMA1.CAR/LOCALS~1/Temp/temp49346WDWFApp.ear
Result
=> deployment aborted : file:/C:/DOCUME1/ALMA1.CAR/LOCALS~1/Temp/temp49346WDWFApp.ear
Aborted: development component 'WDWFApp'/'local'/'LOKAL'/'0.2007.02.16.15.11.28'/'0':SDM could not start the J2EE cluster on the host vmxtbcsapep01! The online deployment is terminated. There is no clutser control instance running on host vmxtbcsapep01 which is described in SecureStorage . The instances, returned by MessageServer [MS host: vmxtbcsapep01; MS port: 3901], are :|Name:JM_T1171660289517_0_ALMACARVAJAL |Host:miriamdragustinovis |State:5|HostAddress:10.21.69.164||Name:JM_T1171656308064_0_vmxtbcsapep01 |Host:cvespinosa |State:5|HostAddress:10.26.26.198||Name:JC_vmxtbcsapep01_CPQ_00 |Host:cvespinosa |State:5|HostAddress:10.26.26.198|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
And in the sdm log file we got this kind of errors:
Feb 16, 2007 2:13:46 PM Error: Unable to compare host[vmxtbcsapep01] and host[miriamdragustinovis] Throwable: java.net.UnknownHostException Throwable message: miriamdragustinovis
Feb 16, 2007 2:13:46 PM Error: Unable to compare host[vmxtbcsapep01] and host[cvespinosa] Throwable: java.net.UnknownHostException Throwable message: cvespinosa
Feb 16, 2007 2:13:46 PM Error: Unable to compare host[vmxtbcsapep01] and host[cvespinosa] Throwable: java.net.UnknownHostException Throwable message: cvespinosa
Feb 16, 2007 2:13:46 PM Error: An error occured while starting a cluster instance.
Feb 16, 2007 2:13:46 PM Error: There is no clutser control instance running on host vmxtbcsapep01 which is described in SecureStorage .
The instances, returned by MessageServer [MS host: vmxtbcsapep01; MS port: 3901], are :
Name:JM_T1171656916610_0_ALMACARVAJAL
Host:miriamdragustinovis
State:5
HostAddress:10.21.69.164
Name:JM_T1171656308064_0_vmxtbcsapep01
Host:cvespinosa
State:5
HostAddress:10.26.26.198
Name:JC_vmxtbcsapep01_CPQ_00
Host:cvespinosa
State:5
HostAddress:10.26.26.198
Any Idea what can be wrong? we have even restarted de AIX Server and starting all the services and it is still not working.
Thanx in Advanced!
Gerardo J

Hi Gerardo,
I encountered exactly the same error, but had a different solution as I was expecting from the error-message.
In my case I was forced by the Visual Administrator to change the administration password, since the time was up on it. But as the password for the Visual Administrator is saved within the database, the password for the SDM is stored within the secure store (file-system) and changing the password just in VA will not automatically change it also in the secure store. But since both passwords for the internal usage need to be equalized, I encountered problems afterwards when trying to deploy something and I got the same error message. However the sense of restriction is meant here, the solution on it was rather simple as follows (Just note that you need to enter a dummy-password first, before setting the correct one similar to your visual administrator):
1. create a telnet session to your J2EE using a command line shell
2. enter "jump 0" to get on the correct node within your J2EE
3. enter "add user" to gain access to user-specific commands
4. enter "password <Administrator> <temporarily new password>"
5. exit
6. create another telnet session to your J2EE using a command line shell
7. after succeeded the login, you will now be forced to enter a new password - so enter "password <Administrator> <origin password of the Visual Administrator>"
8. exit
9. now start the config-tool of the engine
10. apply to the DB-default-question with "yes"
11. select the Secure Store on the left
12. select the entry "admin/password/..." that you can see it in the bottom lines.
13. click "Remove" to delete it from the list
14. set the password similar to the Visual Administrator password within the "Value" line (take care as you can not see the digits).
15. click "Add" to add it back to the list
16. click the disc symbol in the top of the UI to save the new password (if you don't get a dialog afterwards that the data has been stored, something may hasn't worked fine when removing/adding the password-entry, in this case repeat the action on it).
17. After exiting the config-tool, you need to restart the entire J2EE.
18. Your hopefully finished by success ;o))
Best regards
Jochen

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

NW4: SDM could not start the J2EE cluster on the host nw4host

Hello,
in NW4 i get this error when i try to deploy the welcome webdynpro:
SDM could not start the J2EE cluster on the host nw4host! The online deployment is terminated. JStartup Framework is not able to deliver an information about the cluster control instances! Please check the status of the J2EE Engine.
I am using NW4 (built 28.9.04) on Suse 9.0 and the corresponding IDE (2.04) on Windows 2000.
In the J2EE view of the IDE everything (SDM, Dispatcher and Server) is green. I can start the examples on port 50000. According to systeminfo everything is running.
I searched in OSS and found Note 738402. But there is no EOF in the SDM-logfile. And when i started the J2EE-Configtool the value for "admin/host/SID" is not localhost.
Any hints?
Regards,
Nico.

Hello,
> Developer Studio -> Preferences -> SAP J2EE Engine ?
of course. Every icon (SDM, Dispatcher and server) is green in the J22E-View of the IDE. I still get this error message.
Regards,
Nico.

Windows could not start DBConsole for new database instance

Hi,
I am getting this error "Windows could not start the OracleDBConsoleOracleInstance2 on Local Computer. For more information, review the System Event Log. If this is a non-Microsoft service, contact the system vendor, and refer to service-specific error code 1".
I installed Oracle 11g on Windows 7 and created my 1st database instance (oracleInstance1) successfully with a listener and service configured. I could access this database using DBconsole URL: https://hostname:1158/em.
I see the services started for:
OracleDBConsoleOracleInstance1
OracleOraDb11g_home1TNSListener
OracleServiceOracleInstance1
Next, I created a second database instance (oracleInstance2) and have configured a new service for this database. I am using the same listener as I intend to use one database instance at any point of time.
However, I got this warning message during configuration:
"Enterprise manager configuration succeeded with the following warning - Error starting Database Control. Please execute the following command(s).
1. Set the environment variable ORACLE_UNQNAME to Database unique name.
2. C:\Oracle\product\11.2.0\dbhome_1\bin\emctl.bat start dbconsole"
To start the new database console, I stopped the previously running DBConsole, OracleDBConsoleOracle1 and started the new DBConsole OracleDBConsoleOracle2 and get the above error.
When I try to start dbconsole manually using "emctl dbconsole start", it starts OracleDBConsoleOracle1 instead.
I changed environment variables ORACLE_SID=oracle2 and ORACLE_UNQNAME=oracle2
What am I missing here. Please help!
Thank you.

968952 wrote:
Hi,
I am getting this error "Windows could not start the OracleDBConsoleOracleInstance2 on Local Computer. For more information, review the System Event Log. If this is a non-Microsoft service, contact the system vendor, and refer to service-specific error code 1".
I installed Oracle 11g on Windows 7 and created my 1st database instance (oracleInstance1) successfully with a listener and service configured. I could access this database using DBconsole URL: https://hostname:1158/em.
I see the services started for:
OracleDBConsoleOracleInstance1
OracleOraDb11g_home1TNSListener
OracleServiceOracleInstance1
Next, I created a second database instance (oracleInstance2) and have configured a new service for this database. I am using the same listener as I intend to use one database instance at any point of time.
However, I got this warning message during configuration:
"Enterprise manager configuration succeeded with the following warning - Error starting Database Control. Please execute the following command(s).
1. Set the environment variable ORACLE_UNQNAME to Database unique name.
2. C:\Oracle\product\11.2.0\dbhome_1\bin\emctl.bat start dbconsole"
To start the new database console, I stopped the previously running DBConsole, OracleDBConsoleOracle1
Why?
and started the new DBConsole OracleDBConsoleOracle2 and get the above error.
When I try to start dbconsole manually using "emctl dbconsole start", it starts OracleDBConsoleOracle1 instead.
I changed environment variables ORACLE_SID=oracle2 and ORACLE_UNQNAME=oracle2
What am I missing here. Please help!First thing you are missing is showing us what you did. Instead you just described it, and that leaves a lot of room for questions. Copy and paste from a command prompt can work wonders here.
From a command prompt, enter the following:
set ORACLE_SID=oracle2
set ORACLE_UNQNAME=oracle2
set | sort
net start
emctl start dbconsolecopy the entire session, commands and full responses, and paste back here.
>
Thank you.Just to take a side road ...
"I am using the same listener as I intend to use one database instance at any point of time. "
Doesn't' matter if you use one instance or 100. The listener was DESIGNED to service multiple instances of multiple versions running from multiple homes. It is nothing but a connection broker. A telephone switchboard, if you will. All you need is a single listener, with the default name of LISTENER, running on the default port of 1521. It will handle all the database instances you care to throw at it. More instances than anyone in their right mind would ever put on a single server. Your server will run out of capacity to host additional instances before the listener runs out of capacity to service them. Especially since your 'server' is really just a toy in the Oracle world.

DQE Service could not started.

Hi All,
I installed WAS 6.40 SP7 and then EP6 SP6 on Windows Platform. Installation was successfull.
But when I tried to create Database iViews, its not opening the tables for the configured DB. Then i tried to open in Portal content page...
System Administratation ---> Distributed Query Engine
here when i open
* Configuration -> No content is displayed.
Session Manager -> DQE not installed(this messge is displayed)
MetaData Loader -> Portal Runtime Error
An exception occurred while processing a request for :
iView : pcd:portal_content/administrator/super_admin/super_admin_role/com.sap.portal.system_administration/com.sap.portal.distributed_query_engine/com.sap.portal.metadata_loader
Component Name : com.sap.portal.dqe.admintool.metadataloader.DQEMetadataLoader
The exception was logged. Inform your system administrator..
Exception id: 10:57_08/11/04_0002_9138850
See the details for the exception ID in the log file.
When i check the defalutTrace*.trc, the following message is printed...
#1.5#00508BE9307C00170000006000000DA40003E86216ECCFF0#1099932919156#com.sap.engine.core.service630.container.ServiceRunner##com.sap.engine.core.service630.container.ServiceRunner#######SAPEngine_System_Thread[impl:5]_49##0#0#Error#1#/System/Server#Plain###Service DQE error. Nested exception is: com.sap.engine.frame.ServiceException: <Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='Could not start DQE service, reason: Could not initialize RuntimeStateAdminAPIImpl.', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key Could not start DQE service, reason: Could not initialize RuntimeStateAdminAPIImpl.
at com.metamatrix.sap.service.MetaMatrixServiceFrame.start(MetaMatrixServiceFrame.java:144)
at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:201)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:142)
at com.sap.engine.frame.core.thread.Task.run(Task.java:60)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:134)
I fallowed the same instructions given in the installation guide, and insalled in two different machines,in both places I got same problem.
Can any body tell me solution for this problem.
When installing EP6SP3 I have choosen Portal Platform option(where we have DQE schema installation and Portal Platform option) and then updated to EP6SP6.Is it rigt?
From SDN site I got WAS with SP7 and EP with SP6 , if any new stable versions available please let me know from where I can get them.
Regards
Abhilash

Hello.
I have the same problem and when I go into Visual Admin and try to start DQE manually I receive the following error: Any help would be greatly appreciated.
Start service DQE
java.rmi.RemoteException: Could not start service DQE on cluster ID 6654350; nested exception is:
     com.sap.engine.frame.ServiceException: <Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='Service DQE error. Nested exception is: com.sap.engine.frame.ServiceException: <Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='Could not start DQE service, reason: Could not initialize RuntimeStateAdminAPIImpl.', Arguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key Could not start DQE service, reason: Could not initialize RuntimeStateAdminAPIImpl.
     at com.metamatrix.sap.service.MetaMatrixServiceFrame.start(MetaMatrixServiceFrame.java:144)
     at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:201)
     at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:142)
     at com.sap.engine.frame.core.thread.Task.run(Task.java:60)
     at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:73)
     at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:145)
', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key Service DQE error. Nested exception is: com.sap.engine.frame.ServiceException: <Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='Could not start DQE service, reason: Could not initialize RuntimeStateAdminAPIImpl.', Arguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key Could not start DQE service, reason: Could not initialize RuntimeStateAdminAPIImpl.
     at com.metamatrix.sap.service.MetaMatrixServiceFrame.start(MetaMatrixServiceFrame.java:144)
     at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:201)
     at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:142)
     at com.sap.engine.frame.core.thread.Task.run(Task.java:60)
     at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:73)
     at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:145)

Could not find MessageClient for clientId in pushMessageToClients

Hello everybody. I was stuck with unpleasent problem using LCDS 2.5.1 and theirs messaging service. My aim is sending real time messages to particular client which already subscribed to the defined destination within java code. I have following situation:
at first here is my messaging-config.xml:
<?xml version="1.0" encoding="UTF-8"?>
<service id="message-service" class="flex.messaging.services.MessageService">
    <adapters>
        <adapter-definition id="messagingAdapter"
            class="com.thomsonreuters.gip.messaging.impl.MessagingAdapterImpl" />
    </adapters>
    <destination id="realTimeMessaging">
        <adapter ref="messagingAdapter" />
        <channels>
            <channel ref="channel-rtmp" />
        </channels>
    </destination>
</service>
i am already know id of client consumer and pass it like input argument (Set clientIds)
actual sending performing in following method:
    protected void sendMessageToClients(Object msgBody, Set clientIds) {
        log.debug("send message to clients [ids = " + clientIds + ", message = " + msgBody + "]");
        // obtain message service by means of message broker
        MessageBroker messageBroker = MessageBroker.getMessageBroker(null);
        MessageService messageService = (MessageService) messageBroker.getService("message-service");
        // create async message with provided message body
        AsyncMessage message = createMessage(msgBody);
        // There I can sure that my client id (clientIds) present in message service subscribers id
        System.out.println(messageService.getSubscriberIds(message, true)); // this statement prints client id in wich i want to send message
        // Now push message to the clients (actualy one client)
        messageService.pushMessageToClients(clientIds, message, false);
and realy this code doese nothing, message is not recieved by expected user and in logs of lcds a can see following line:
[LCDS]02/19/2010 15:29:59.567 [DEBUG] [Service.Message] Warning: could not find MessageClient for clientId in pushMessageToClients: [F88813EC-AC0A-EF4D-136CAE2F50EC44EB]
But id F88813EC-AC0A-EF4D-136CAE2F50EC44EB was already printed by this statement System.out.println(messageService.getSubscriberIds(message, true));
What I have missed? Or where I should look to resolve this issue?
Please help me

Forgot to say. I am able to send message to all clients within following code:
public void sendMessageToAllClients(Object msgBody) {
        log.debug("send message to all clients: " + msgBody);
        AcknowledgeMessage acknowledgeMessage = MessageBroker.getMessageBroker(null).routeMessageToService(createMessage(msgBody),
                null);
        log.debug("result: " + acknowledgeMessage);
In this case all currently subscribed users receiving message.
here is method which creates AsyncMessage
private AsyncMessage createMessage(Object msgBody) {
        AsyncMessage msg = new AsyncMessage();
        msg.setClientId(getServerId());
        msg.setTimestamp(System.currentTimeMillis());
        msg.setMessageId(UUIDUtils.createUUID(true));
        msg.setDestination(destination);
        msg.setBody(msgBody);
        return msg;
And by the way I have my own custom adapter here is code:
public class MessagingAdapterImpl extends MessagingAdapter {
    private static final Log log = LogFactory.getLog(MessagingAdapterImpl.class);
    @Override
    public Object invoke(Message message) {
        log.debug("sending message " + ToStringBuilder.reflectionToString(message, ToStringStyle.SHORT_PREFIX_STYLE));
        MessageService msgService = (MessageService) getDestination().getService();
        msgService.pushMessageToClients(message, true);
        msgService.sendPushMessageFromPeer(message, true);
        return null;
    @Override
    public Object manage(CommandMessage commandMessage) {
        if (CommandMessage.SUBSCRIBE_OPERATION == commandMessage.getOperation()) {
            log.debug("subsriber is registered [" + commandMessage.getClientId() + "]");
        if (CommandMessage.UNSUBSCRIBE_OPERATION == commandMessage.getOperation()) {
            log.debug("subsriber is unregistered [" + commandMessage.getClientId() + "]");
        return null;
    @Override
    public boolean handlesSubscriptions() {
        return true;

Error: Error writing stream: Could not find prefix for namespace:

Hi all,
I am getting this error while doing topdownAssemble using WSA. The error seems as if the name space definitions do not have proper prefixs, but I have prefixes for all the name spaces.
Any idea what else might be causing the problem ?
Thanks,
--venkat
+ java -jar /opt/oc4j_extended_101310/webservices/lib/wsa.jar -topDownAssemble -wsdl parlayx_third_party_call_service.wsdl -unwrapParameters false -className oracle.sdp.parlayx.ThirdPartyCallImpl -input classes -output gen -ear dist/tpcall.ear -mappingFileName src/ThirdPartyCallService-java-wsdl-mapping.xml -packageName oracle.sdp.parlayx -fetchWsdlImports true -debug
FINE: OWS-11015 Trying to Access Resource at URL: file:/home/vayyagar/IdeaProjects/ParlayX/parlayx_third_party_call_service.wsdl
FINE: OWS-11015 Trying to Access Resource at URL: file:/home/vayyagar/IdeaProjects/ParlayX/parlayx_third_party_call_interface.wsdl
FINE: OWS-11015 Trying to Access Resource at URL: file:/home/vayyagar/IdeaProjects/ParlayX/parlayx_common_faults.wsdl
FINE: OWS-11015 Trying to Access Resource at URL: file:/home/vayyagar/IdeaProjects/ParlayX/parlayx_third_party_call_service.wsdl
FINE: OWS-11015 Trying to Access Resource at URL: file:/home/vayyagar/IdeaProjects/ParlayX/parlayx_third_party_call_interface.wsdl
FINE: OWS-11015 Trying to Access Resource at URL: file:/home/vayyagar/IdeaProjects/ParlayX/parlayx_common_faults.wsdl
FINE: OWS-11015 Trying to Access Resource at URL: file:/home/vayyagar/IdeaProjects/ParlayX/parlayx_third_party_call_interface.wsdl
FINE: OWS-11015 Trying to Access Resource at URL: file:/home/vayyagar/IdeaProjects/ParlayX/parlayx_common_faults.wsdl
FINE: OWS-11015 Trying to Access Resource at URL: file:/home/vayyagar/IdeaProjects/ParlayX/parlayx_common_faults.wsdl
Error: Error writing stream: Could not find prefix for namespace: http://www.csapi.org/wsdl/parlayx/common/v2_0/faults
Error writing stream: Could not find prefix for namespace: http://www.csapi.org/wsdl/parlayx/common/v2_0/faults: java.io.IOException: Could not find prefix for namespace: http://www.csapi.org/wsdl/parlayx/common/v2_0/faults
at oracle.j2ee.ws.wsdl.xml.WSDLWriterImpl.writeAttValFromQName(WSDLWriterImpl.java:660)
at oracle.j2ee.ws.wsdl.xml.WSDLWriterImpl.writeFault(WSDLWriterImpl.java:577)
at oracle.j2ee.ws.wsdl.xml.WSDLWriterImpl.writeOperation(WSDLWriterImpl.java:563)
at oracle.j2ee.ws.wsdl.xml.WSDLWriterImpl.writePortType(WSDLWriterImpl.java:422)
at oracle.j2ee.ws.wsdl.xml.WSDLWriterImpl.writeDefinition(WSDLWriterImpl.java:186)
at oracle.j2ee.ws.wsdl.xml.WSDLWriterImpl.writeWSDL(WSDLWriterImpl.java:93)
at oracle.j2ee.ws.wsdl.xml.WSDLWriterImpl.writeWSDL(WSDLWriterImpl.java:83)
at oracle.j2ee.ws.common.wsdl.WSDLImportLocalizer.writeOutWSDL(WSDLImportLocalizer.java:637)
at oracle.j2ee.ws.common.wsdl.WSDLImportLocalizer.writeOutTo(WSDLImportLocalizer.java:568)
at oracle.j2ee.ws.common.wsdl.WSDLImportLocalizer.localize(WSDLImportLocalizer.java:278)
at oracle.j2ee.ws.common.wsdl.WSDLImportLocalizer.localize(WSDLImportLocalizer.java:162)
at oracle.j2ee.ws.tools.wsa.Assembler.topDownAssemble(Assembler.java:828)
at oracle.j2ee.ws.tools.wsa.cli.Processor.execute(Processor.java:320)
at oracle.j2ee.ws.tools.wsa.cli.Processor.execute(Processor.java:169)
at oracle.j2ee.ws.tools.wsa.Main.mainNoSystemExit(Main.java:83)
at oracle.j2ee.ws.tools.wsa.Main.main(Main.java:48)
at oracle.j2ee.ws.wsdl.xml.WSDLWriterImpl.writeWSDL(WSDLWriterImpl.java:95)
at oracle.j2ee.ws.wsdl.xml.WSDLWriterImpl.writeWSDL(WSDLWriterImpl.java:83)
at oracle.j2ee.ws.common.wsdl.WSDLImportLocalizer.writeOutWSDL(WSDLImportLocalizer.java:637)
at oracle.j2ee.ws.common.wsdl.WSDLImportLocalizer.writeOutTo(WSDLImportLocalizer.java:568)
at oracle.j2ee.ws.common.wsdl.WSDLImportLocalizer.localize(WSDLImportLocalizer.java:278)
at oracle.j2ee.ws.common.wsdl.WSDLImportLocalizer.localize(WSDLImportLocalizer.java:162)
at oracle.j2ee.ws.tools.wsa.Assembler.topDownAssemble(Assembler.java:828)
at oracle.j2ee.ws.tools.wsa.cli.Processor.execute(Processor.java:320)
at oracle.j2ee.ws.tools.wsa.cli.Processor.execute(Processor.java:169)
at oracle.j2ee.ws.tools.wsa.Main.mainNoSystemExit(Main.java:83)
at oracle.j2ee.ws.tools.wsa.Main.main(Main.java:48)

HI,
Seems known issue. I would suggest to raise an Service Request with the test case.
GD,
Ashish

SDM Deployment Failed--SDM could not start the J2EE cluster on the DB Host

HI,
I am trying to deploy ESS packges in EP through SDM.But while deploying I am getting this error in SDM at the start itself:-
Error: An error occured while starting a cluster instance.
Oct 14, 2008 5:14:41 PM Error: There is no clutser control instance running on host SBPEPDB1 which is described in SecureStorage
Please check if there is an appropriate running cluster instances
SDM could not start the J2EE cluster on the host SBPEPDB1! The online deployment is terminated.
There is no clutser control instance running on host SBPEPDB1 which is described in SecureStorage
I am pasting the full LOG File details:-
Oct 14, 2008 6:32:00 PM Info: Starting cluster instance processes.
Oct 14, 2008 6:32:00 PM Error: An error occured while starting a cluster instance.
Oct 14, 2008 6:32:00 PM Error: There is no clutser control instance running on host SBPEPDB1 which is described in SecureStorage . The instances, returned by MessageServer [MS host: SBPEPCI1; MS port: 3900], are :
Name:JM_T1223989073901_0_CPCAPP109
Host:SBPEPCI1
State:5
HostAddress:172.17.131.38
Name:JC_CPCAPP109_EPP_01
Host:CPCAPP109
State:5
HostAddress:172.17.131.31
Please check if there is an appropriate running cluster instances.
Oct 14, 2008 6:32:00 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Oct 14, 2008 6:32:00 PM Error: Aborted: development component 'pcui_gp/isr/cfg'/'sap.com'/'MAIN_ERP05VAL_C'/'2515722'/'0', grouped by software component 'SAPPCUI_GP'/'sap.com'/'MAIN_ERP05VAL_C'/'1000.600.0.13.0.20080516101947''/'0':
SDM could not start the J2EE cluster on the host SBPEPDB1! The online deployment is terminated.
There is no clutser control instance running on host SBPEPDB1 which is described in SecureStorage .
The instances, returned by MessageServer [MS host: SBPEPCI1; MS port: 3900], are :
Name:JM_T1223989073901_0_CPCAPP109
Host:SBPEPCI1
State:5
HostAddress:172.17.131.38
Name:JC_CPCAPP109_EPP_01
Host:CPCAPP109
State:5
HostAddress:172.17.131.31
Please check if there is an appropriate running cluster instances.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).STARTUP_CLUSTER)
Oct 14, 2008 6:32:04 PM Info: Starting to save the repository
Oct 14, 2008 6:32:05 PM Info: Finished saving the repository
Oct 14, 2008 6:32:07 PM Info: Starting: Initial deployment: Selected software component 'SAPPCUI_GP'/'sap.com'/'MAIN_ERP05VAL_C'/'1000.600.0.13.0.20080516101947''/'0' will be deployed.
Oct 14, 2008 6:32:07 PM Error: Aborted: software component 'SAPPCUI_GP'/'sap.com'/'MAIN_ERP05VAL_C'/'1000.600.0.13.0.20080516101947''/'0':
Failed deployment of SDAs:
development component 'pcui_gp/isr/cfg'/'sap.com'/'MAIN_ERP05VAL_C'/'2515722'/'0' : aborted
Please, look at error logs above for more information!
I have checked the CONFIGTOOl and the properties seem to be OK.
I tried SHUTTING DOWN all APPLICATION servers & Restarting the DEPLOYMENT,but it still Failed
Pls suggest.
Regards,
Abhijeet
I

Hi George,
Thnx for your reply.
I have stopped all Application servers and kept only the CI-DB instances running.Retried deploying the ESS packages but still getting the same error.
Have checked the Visual admin,it is not in SAFE mode,it working normally.
Have alos checked the CLUSTER Manager Property Values in both Visual Admin & Config Tool,they are alright.
About the Cluster Resources,can you pls specify what exactly do you mean by "Cluster Resources are running or not".
I think if the application servers are stopped,then the Cluster resources shudnt come into play right?? Correct me if I am wrong.
Kindly suggest what other steps I shud take.
Regards,
Abhijeet

*** WARNING: Could not start service 80 for protocol HTTP on host MyFQDN

Similar Messages

Maybe you are looking for