Error: Could not start Layout Designer

When I click the LAYOUT tab in the form design, I get this error and exits.
When I read the help, it says that I need to install some form designer with gui. how do i do that and where can i get that?
Thanks
Kiran

Check =>https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/30a9630b-4f89-2a10-6fab-e311b3ffd9a6
Also /people/scott.jones/blog/2007/09/13/installing-and-configuring-sap-interactive-forms-by-adobe-for-the-sap-netweaver-composition-environment
Check OSS:965548,816065,1121176,1176858...Many More.

Similar Messages

Could not start Layout Designer (see long text)

Dear All,
Could not start Layout Designer (see long text)
Message no. FPUIFB086
Diagnosis
The forms design tool for developing the form layout could not be started; either it is not installed or there are errors in the installation.
Procedure
Make sure that you have the forms design tool installed on your desktop (the tool is part of the SAPGUI installation).
Refer also to SAP Note 1121176.
Note : I have already checked forums and also the long text file , i have installed SAP gui 720 with latest patch even though , we are getting the same error . or i have to installed ADOBE LIFE CYCLE DESIGNER to user PC ?
Note :
One of the forum is mentioned ,we can also download and install the newest SAP GUI (what is 7.2 i believe) which has LCD as a part of installation.
but still i am getting error .
SAP gui Details :
SAP PC VERSION INFORMATION: saplogon.exe
MAIN MODULE INFORMATION:
   saplogon.exe
   SAP Logon for Windows
   720 Final Release
   7200.3.9.1071
   1286983
SYSTEM INFORMATION:
   Operating system: Microsoft Windows XP 5.1 (2600)
                     Service Pack 3
Kindly advise.

Please let me know the path and it can be used permanent ? or it will ne expired ?
Thanks
Edited by: satheesh0812 on Nov 29, 2011 12:17 PM

Could not start Layout Designer

When i press layout button in adobe forms (SFP) i am getting the following error..
LONG TEXT:
Could not start Layout Designer (see long text)
Message no. FPUIFB086
Diagnosis
The forms design tool for developing the form layout could not be started; either it is not installed or there are errors in the installation.
Procedure
Make sure that you have the forms design tool installed on your desktop (the tool is part of the SAPGUI installation).

Hi Kodandarami Reddy.S ,
Which web site did you downlad the adobe lifecycle v8.0 ? I have to install this program to make a adobe forms.
Regards
recoba561161

Adobe Form: Could not start Layout Designer (see long text) - FPUIFB 086

Hello Gurus,
I have an issue when I working in SFP transaction, after create interface and form, When I switch to Layout Tab, I get and issue, please check my image blow:
Could anyone help me?
Thanks!

Please let me know the path and it can be used permanent ? or it will ne expired ?
Thanks
Edited by: satheesh0812 on Nov 29, 2011 12:17 PM

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.

Fiori leave request error "Could not start the app due to an internal error"

Hi,
I'm getting this error "Could not start the app due to an internal error" when accessing leave request application.
I don't get this error when I login and launch the app for the first time. when I go back to the home screen and select "My Leave Requests" app again, I get this error.
If I close the error message and do a browser refresh, everything is fine again for the first time, if I access the LR app again- same error .
Other apps are working fine.
I don't see any error in gateway or App logs.
below is the Request URI
/sap/opu/odata/UI2/INTEROP/ResolveLink?linkId=%27LeaveRequest-createLeaveRequest%27&shellType=%27FLP%27&formFactor=%27desktop%27
Service call info
Anyone with similar issue? any SAP notes?
we are on
UI2_731        100    0009    SAPK-10009INUI2731        SAP UI2 IMPL. FOR NW 7.31
UI2_FND        100    0009    SAPK-10009INUI2FND        SAP UI2 FOUNDATION
UI2_SRVC    100    0009    SAPK-10009INUI2SRVC        SAP UI INTEGRATION SERVICES
UI5_731        100    0009    SAPK-10009INUI5731        SAP UI5 TEAM PROVIDER ON 731
UISAPUI5    100    0009    SAPK-10009INUISAPUI5    SAP UI5
UI_INFRA    100    0009    SAPK-10009INUIINFRA        SAP UI INTEGRATION INFRASTRUCTURE
UIX01HCM    100    0003    SAPK-10003INUIX01HCM    UI for HCM Application
Tags edited by: Michael Appleby

Hi Masa,
We have required SAP notes now, we are on version 1.22.5.
It is still the same, working the first time I access the App, but subsequent access wont work until i refresh browser.
I've include the response and lpd/tile screens.
Thanks,
Phani

Error : Could not start the SSO service. Please check the configuration

Hi,
I am getting the above error when enabling the"Agent-Based Windows Single Sign-On with Active Directory (Kerberos0".
I already twice did the KTpass.Timing is perfect bet CAS and AD.Please look into this CAS LOG file and advice me the next step to solve this issue.
Thanks
swami

Until you perform the configuration on the AD server, the following message will appear:
Error: Could not start the SSO service. Please check the configuration.
So configure the AD server so that the error message will not appear again.

Error: could not start kstartupconfig4?

Fresh install of arch, just installed KDEMOD , when i start kde/kdm i get
"could not start kstartupconfig4, check your installation"
I have made sure I can RW to my home dir.. any help would be MUCH:D appreciated as i want to get up and runing here...

sorry, im just frustrated beyond belif, i hate kde WITH THE PASSION, but everyone is saying to give this kdemod a try..
this is a fresh install of arch, installed kdemod, did not work, so installed kdemod-complete, did not work
kdm fails on boot,
i installed GDM, it works fine, when i start a kde session from GDM it get the error.
"could not start kstartupconfig4, check your installation"
all daemons are loading fine, no errors anywhere else, xserver works fine.. just bloody kde that doesnt work.

Stms Error Could not start transport control program tp

Hi Experts,
We have installed new system and trying to configure STMS, but we are facing Issue like " Could not Start transport control program tp ". Can anyone please suggest us how to continue further...
Tasks we have done :
1. Upgraded kernel, tp , r3trans to latest.
2. Added Dbms_type = mss in Environmental variables
3. Reconfigured STMS by deleting old one..
Thanks in Advance...
Regards,
Krishna.M

Hi Benjamin,
We have checked for Authorizations to the dirve, we are having full authorizations also host file entries are correct, but we are unable to find the dev_tp trace file. Can you please tell me where can i find that file. For more information please find the image....
Please suggest me how to resolve the issue..
Regards,
Krishna.M

SRM Error : Could not start transaction.

The user want to approve the SC and is getting the error
"Cannot Start the Transaction"
"Return data for Work Item could not be read"
Please let me know how to fix this issue.

Hi,
Are there any dumps? What version of SRM are you using?
Regards,
Prasanna

Could not start the hyperion workspace-web application Error 1067

Hi,
I have installed hyperion from scratch in a distributed environment...everything was working fine.......i.e. shared services, workspace, essbase, sql server, and hfm. I was able to logon and navigate different options in the hyperion products...but essbase stopped working when I re-started all four servers ....?
(1) When I restarted all four servers and stopped and restarted all hyperion services as per giving sequence then everything works fine but essbase EAS console and workspace web console...i was getting error message " could not connect to administration server" whenever i try to connect EAS console to essbase then I went to services there I saw workspace agent and workspace web application service is down.
(2) as soon as I started those both services then my shared services automatically stopped but I was able to logon in Essbase console and workspace console but my shared services are down...
(3) as soon as I start shared service they started but my workspace agent and workspace web application automatically stopped...and when I try to start again workspace web application then I get this error "[ Could not start the hyperion workspace-web application services on local computer. Error 1067: the process terminated unexpectedly]"
I have been searching online and googling but have a hard luck to get some best solution for this...can some one help me or guide me to walk through with this issue...
Thank you very much in advance ...
Regards,
Safi

I solved this issue...It was with Hyperion Services those were stop responding some how.....but I stopped each service and restarted then those started working again...
Regards,
Safi

Saprouter could not start "Error:1053"

Hi!
I have installed the SAP-Router service and cannot start it from "SERVICES".
I get the error "Could not start the saprouter on the Local machine".
I also implemented the recommendation from microsoft ot apply the new package
from http://support.microsoft.com/kb/839174/en-us
. But If I try to apply it, the popup tells me "no new packages found that are newer than on my OS".
<b>How should I proceed?
Is it possible to deinstall the service from "services"?</b>
Thank you!
regards

Hello Peter,
We started a survey to change our SAProuter acrhitecture to SAProuter
7.0 version.
As we overviewed all prerequisites, we require from SAP support
confirmation on the 2 following points :
1. As saprouter program will be installed on host which already exists
and is located in DMZ, the existing Windows operating system version is
W2003 Server Standard Edition in french version.
Thus, we would like SAP support to confirm that SAProuter program can
be installed and will run correctly on Windows 2003 Standard Edition in
french version as SAP note 690432 'Windows 2003 Support' mentions that
SAP supports such an hardware configuration if Windows Multilanguage
User Interface (MUI) kit is installed and that W2003 Standard Edition
is supported for 'test or small systems only' (only saprouter program
will run on this host)
2. One of the requirements of saprouter installation is to provide
public @IP to SAP.
As we get such an IP adress, we require SAP support to confirm that
this IP adress will work properly as below :
Saprouter will be installed on host which is located in DMZ (SAP
requirement) what does mean 'between our 2 firewalls'
Thus, connection from sap will be translated by first firewall which
will redirect to public adress provided
Question : Must the host on which saprouter will run have one and only
one IP adress?
As mentionned previously, host already exists and has already an IP
adress : then, public @IP provided will have to be translated by
firewall.
Thanks for your response as my colleagues and I noted that you are 'reference guru' on several topics (you answered to us for customer message open ofr inquiry on ECC 6.0 upgrade with OS/DB migration)
Rgds,
Zulain

Error 1053 Could not start OracleServiceEMREP on local Computer

I have recently installed patch 3731593 for upgrading grid control from 10.2.0.4 to 10.2.0.5. Patch got installed successfully. But after applying patch, my windows service for repository is not getting started. I am getting following error "Could not start OracleServiceEMREP on local Computer. Error 1053. The service does not respond to the start or control request in a timely fashion.
Also when I gave command OMS_HOME>emctl start oms.I noticed following error.
Oracle Management Server is not functioning because of the following reason:
Connection to the repository failed. Verify that the repository connection infor
mation provided is correct.
As per my understanding, this error is due to Error 1053.
How can I solve this error.
Thanks & Regards,
Saurabh

Try to start the database wiith command line and check
.sqlplus "/as sysdba"
startup

Could not start the app due to a configuration problem - Launchpad issue

Hi,
When I try to launch a custom app from Fiori Launchpad I get an error could not start app due to configuration problem. Error 500- Internal Server Error.
App works correctly when I try to execute via URL http://XXX/sap/bc/ui5_ui5/sap/zmyfioriui5_v11.
Screenshot of Chrome debugging and lpd_cust attached.
It seems problem with ResolveLink but unable to conclude.
Any Suggestion how to proceed.
Thanks,
Mayank

Hi Mayank,
Few modifications :
For additional information field : ".component" at the end is not required.
Only keep : SAPUI5.Component=sap.ui.demo.myFiori
Check this screenshot :
Also, please don't keep Semantic object name and application alias as same name i.e. ymyfioriui5_v11. Its very confusing.
If above doesn't solve, please confirm below :
ZXXXLPD is your launchpad role in LPD_CUST tcode.
Please use TRANSACTIONAL instead of transactional (might be case sensitive)
Show your semantic object "ymyfioriui5_v11" created in /UI2/SEMOBJ
Regards,
Tejas

Could not start Sun Java Application Server

Hi ,
I have been using JSC for a while, now and then it reports an error " could not start sun java application server...". Does any one know why it s not able to start java application server..
Before you say anything, I have tried
1. use netstat to find any port conflicts.
2. Tried to start application server manually
3. shut down and start studio creator and then try running the project
4. shut down and start PC
unfortunately none of them helped
Only reinstalling resolved the problem. But I cant keep reinstalling very often.
Does any one know the permanent solution for this problem.
Cheers
kush

Sometimes it appears this is a timeout issue because it's taking too long to come up. As Jonathan says, undeploy can help with this (along with his other suggestions).
How many deployed projects do you see (in the server navigator you can open up the deployed server and see what's out there)?
I periodically undeploy "junk" projects that I'm not really using because they slow down the server startup (same thing happens I believe for tomcat... when the server starts it has to load them all and it takes awhile). You can undeploy from within the server navigator by drilling into the server nav and right clicking on the deployed app and choosing undeploy... or you can use the server admin tool.
hth,
v

Error: Could not start Layout Designer

Similar Messages

Maybe you are looking for