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

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

  • 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.

  • 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

  • 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.

  • 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.

  • 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

  • Could not start transport control program tp while releasing the TR

    Hello experts,
    i have a problem if any one phase this kind of problem & if u know the solution please share to me its urgent
    problem in Development system ,for this  i had updated kernel , TP patch level , R3trans patch level in  development and quality system , but still the problem is occurring in development system . while  releasing the Transport Request this error is coming  that too not in frequently some times it is happening some times it not happening  ( some times its working fine ) 
    Could not start transport control program tp
    Message no. TP608 Diagnosis
    There was an attempt to start the transport control program tp using the local RFC interface. An
    error occurred here.
      Error code: 4
      RFC error text: timeout during allocate / CPIC-CALL: 'ThSAPCMRCV'
    Meaning of the error codes:
      03  RFC system failure
      04  RFC communication failure
    System Response
    The function terminates. Details about the error can be found in the trace file of the Gateway
    Monitor (SMGW).
    Procedure
    Contact your system administrator or use report RSTPTEST to localize the error. You can then
    execute the command again.
    please suggest me what can i do for better , how can i resolve this issue
    Thanks &  Regards,
    Narasimha

    Hello experts ,
    Last one and half month on-words we are phasing some problems on STMS
    while releasing the Transport Request getting this error messages on
    status-bar
    1. "could not start transport control program tp"
    2. while importing the TR into quality system getting this error message" RFC Error :timeout during allocate/CPIC-CALL "
    3.while forwarding the TR from QAS to PRD : " RFC Error :timeout during
    allocate/CPIC-CALL "
    after continues refreshing,we are able to release the request and importthe request into quality system. But after some time again same problem
    coming
    for this we did the kernel upgrade , tp , & R3trans update and STMS RE-
    Configuration etc...But no use with this we got the same problem after
    finishing all these workaround , but don't know what happened after 2-3
    days STMS starts working fine DEV-QAS-PRD ,
    Now we are in the same problem after continues refreshing,we are able torelease the request and import the request into quality system. But after
    some time again same problem coming
    please suggest us what could be the reason behind this & what we can do
    for better

  • Could not find layout General Audio 10 in Garageband... Yosemite problem?

    iMac (21.5-inch, Late 2012)
    2.7 GHz Intel Core i5
    8 GB 1600 MHz DDR3
    Hi there
    Has anyone encountered a garageband problem since installing Yosemite?
    Whichever song file I bring up i keep getting this error message "Could not find layout General Audio 10"
    I'm assuming this refers to the visuals for the tones, compressors, reverbs etc as they're not showing for any tracks
    Is this likely to be fixed and, maybe, is it because i've just bought and installed Logic X?
    Hope someone can help

    General Audio 10 improbably part of the additional content.
    Try this fix posted by Robinson Collins:
    Re: I downloaded Garage Band 2x and the same note appears: there is no General Audio 10. Please advise. Thank you.
    Try this: Go to your menu bar, select "Garageband" and then "Restore Sound Library..."
    It can take awhile to download as it's a pretty big library. You might need to also select "Update Sound Library..." after the restore is done.

  • Windows could not start the FLEXnet Licensing Service service on Local Computer Error 1068: The dependency service or group failed to start.

    Today I installed Adobe Director 11.5. I received a couple of errors in the FLEXnet Licensing Service. It looks It could not start. I tried to download the Licence fix what I found on Google but that doesn't work, so I checked the 'Service' at service (windows).
    It's status is empty. When I double click on the FLEXnet Licensing Service, clicked on start at the opened window and an error is coming: 
    Windows could not start the FLEXnet Licensing Service service on Local Computer
    Error 1068: The dependency service or group failed to start.
    I don't understand what it says with this message, only that it is impossible to start. However, that is not what I am trying of course, I want to start the FLEXnet Licensing Service, service. 
    Re-installing of the software, doesn't make any change. How can I start it so Director is also working?

    Hi Don1233,
    Please consider seek help at the software vendor side.
    For the services didn't start, follow the suggestions posted by Elton in the thread below:
    https://social.technet.microsoft.com/Forums/en-US/e35da253-f0df-41d1-8df2-b73fa54742a0/windows-could-not-start-the-flexnet-licensing-service-service-on-local-computer-error-1068-the?forum=w7itproinstall
    Best regards
    Michael Shao
    TechNet Community Support

  • 1)Could not start up os x 2)Only could start bootcamp 3)Tried resetting nvram 4)Could not start even in bootcamp 5)Verify disk says -. Verifying volume "Macintosh HD" Error: Live file system repair is not supported 6)Installed maverick on USB d

    1) Could not start up os x
    2) Only could start bootcamp
    3) Tried resetting nvram
    4) Could not start even in bootcamp
    5) Verify disk says …. Verifying volume “Macintosh HD”
    Error: Live file system repair is not supported
    6) Installed maverick on USB drive
    7) Boot from USB drive. Tried verifying HD: Volume header needs minor repair. The volume Recovery HD was found corrupt and needs to be repaired. Verifying volume “Macintosh HD”: Error: live file system repair is not supported.
    8) The terminal code says
    9) Last login: Wed Feb 11 14:09:47 on console
    10)  xxxx-MacBook:~ xxxx$ diskutil list
    11)  /dev/disk0
    12)  #: TYPE NAME SIZE       IDENTIFIER
    13)  0:      GUID_partition_scheme *160.0 GB   disk0
    14)  1: EFI EFI 209.7 MB   disk0s1
    15)  2:                  Apple_HFS Macintosh HD            80.1 GB disk0s2
    16)  3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3
    17)  4:       Microsoft Basic Data 50.0 GB    disk0s4
    18)  /dev/disk1
    19)  #: TYPE NAME SIZE       IDENTIFIER
    20)  0:      GUID_partition_scheme *15.6 GB    disk1
    21)  1: EFI EFI 209.7 MB   disk1s1
    22)  2:                  Apple_HFS BOOT                    14.8 GB    disk1s2
    23)  3:                 Apple_Boot Recovery HD             650.0 MB   disk1s3
    24)  Saeedehs-MacBook:~ saeedehmirbagheri$ diskutil cs list
    25)  No CoreStorage logical volume groups found
    26)  Saeedehs-MacBook:~ saeedehmirbagheri$ sudo gpt -vv -r show /dev/disk0
    27)  Password:
    28)  gpt show: /dev/disk0: mediasize=160041885696; sectorsize=512; blocks=312581808
    29)  gpt show: /dev/disk0: PMBR at sector 0
    30)  gpt show: /dev/disk0: Pri GPT at sector 1
    31)  gpt show: /dev/disk0: Sec GPT at sector 312581807
    32)  start       size  index  contents
    33)  0          1 PMBR
    34)  1          1 Pri GPT header
    35)  2         32 Pri GPT table
    36)  34          6
    37)  40     409600      1  GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
    38)  409640  156394528      2  GPT part - 48465300-0000-11AA-AA11-00306543ECAC
    39)  156804168    1269544      3  GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC
    40)  158073712   56853648        
    41)  214927360   97652736      4  GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
    42)  312580096       1679        
    43)  312581775         32         Sec GPT table
    44)  312581807          1         Sec GPT header
    45)  xxxx-MacBook:~ xxxx$ sudo fdisk /dev/disk0
    46)  Disk: /dev/disk0 geometry: 19457/255/63 [312581808 sectors]
    47)  Signature: 0xAA55
    48)  Starting       Ending
    49)  #: id  cyl  hd sec -  cyl  hd sec [     start - size]
    50)  ------------------------------------------------------------------------

    Thank you -
    I booted from external USB. The diskutil list output is from OS x booting from the USB, which shows the following:
    Saeedehs-MacBook:~ saeedehmirbagheri$ diskutil list
    /dev/disk0
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:      GUID_partition_scheme                        *160.0 GB   disk0
       1:                        EFI EFI                     209.7 MB   disk0s1
       2:                  Apple_HFS Macintosh HD            80.1 GB    disk0s2
       3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3
       4:       Microsoft Basic Data                         50.0 GB    disk0s4
    /dev/disk1
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:      GUID_partition_scheme                        *15.6 GB    disk1
       1:                        EFI EFI                     209.7 MB   disk1s1
       2:                  Apple_HFS BOOT                    14.8 GB    disk1s2
       3:                 Apple_Boot Recovery HD             650.0 MB   disk1s3
    Saeedehs-MacBook:~ saeedehmirbagheri$ diskutil cs list
    No CoreStorage logical volume groups found
    I am not able to use target disk mode because I don't have firewire/thunderbolt ports.

  • WLS 9.2: MigrationException: Could not start JTAMT on local server

    I have configured a two machine WLS 9.2 Cluster with two Managed Servers.
              When I try to start the Managed Server through the Node Manager from Admin
              Server's WLS Console, it fails with the following error (
              actually both Managed Servers fail with the same error):
              weblogic.cluster.migration.MigrationException: Could not start JTAMT on
              local server because it could not be deactivated on the current host.
              at
              weblogic.transaction.internal.TransactionRecoveryService.deployAllTransactionRecoveryServices(TransactionRecoveryService.java:400)
              at
              weblogic.transaction.internal.TransactionRecoveryService.resume(TransactionRecoveryService.java:170)
              at
              weblogic.transaction.internal.TransactionRecoveryService.start(TransactionRecoveryService.java:181)
              at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
              at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
              at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
              This message resides in file:
              bea920\weblogic92\common\nodemanager\servers\MANAGED-SERVER1\logs\MANAGED-SERVER1.log
              The WLS installation was done including the Node Manager Service.
              Is this error message familiar at all and what could be done to fix it?
              These Managed Servers run on Win2000 and Win2003 respectively. Should I do
              something to the OS (Enable XA Txs in Control Panel/MSDTC)?

    Did you start AdminServer before try to start MANAGED-SERVER1?
              Did you ever migrate Transaction Recovery Service of MANAGED-SERVER1 to other servers?
              If the problem still exist, you can enable the debug option "DebugJTAMigration" and post the stack trace.

  • The Sun Java Application Server 8.1 could not start anymore

    Very incredible I was working fine from may days with Stydio Creator 2
    but yesterday I run the project and it does not work anymore, please can you suggest something:
    The Sun Java Application Server 8.1 could not start.
    from the Output console:
    C:\Sun\Creator2\SunAppServer8\bin\asadmin.bat start-domain --domaindir C:\Sun\Creator2\SunAppServer8\domains\ creator
    Failed to start server localhost:4848
    Deployment error: Failed to start server localhost:4848. See the server log file for details.
    Exception=Deployment error: Failed to start server localhost:4848. See the server log file for details.
    Deployment error: Failed to start server localhost:4848. See the server log file for details.
    at org.netbeans.modules.j2ee.deployment.devmodules.api.Deployment.deploy(Deployment.java:198)
    at org.netbeans.modules.j2ee.ant.Deploy.execute(Deploy.java:75)
    at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
    at org.apache.tools.ant.Task.perform(Task.java:364)
    at org.apache.tools.ant.Target.execute(Target.java:341)
    at org.apache.tools.ant.Target.performTasks(Target.java:369)
    at org.apache.tools.ant.Project.executeTarget(Project.java:1214)
    at org.apache.tools.ant.Project.executeTargets(Project.java:1062)
    at org.apache.tools.ant.module.bridge.impl.BridgeImpl.run(BridgeImpl.java:234)
    at org.apache.tools.ant.module.run.TargetExecutor.run(TargetExecutor.java:242)
    at org.netbeans.core.execution.RunClassThread.run(RunClassThread.java:125)
    Caused by: Failed to start server localhost:4848
    at org.netbeans.modules.j2ee.deployment.devmodules.api.Deployment.deploy(Deployment.java:152)
    ... 10 more
    and in the log file:
    [#|2006-02-24T11:49:51.296+0100|WARNING|sun-appserver-pe8.1_02|
    javax.enterprise.system.core|_ThreadID=25;|CORE5061: Exception :
    com.sun.appserv.server.ServerLifecycleException: [C4073]: A JMS destination limit was reached.
    Too many Subscribers/Receivers for Queue :
    temporary_destination://queue/192.168.0.159/3376/2 user=admin, broker=127.0.0.1:27676(2403)
         at com.sun.enterprise.jms.JmsProviderLifecycle.onTermination(JmsProviderLifecycle.java:476)
         at com.sun.enterprise.server.ApplicationServer.onTermination(ApplicationServer.java:454)
         at com.sun.enterprise.server.Shutdown.startShutdown(Shutdown.java:42)
         at com.sun.enterprise.admin.event.AdminEventMulticaster.invokeShutdownEventListener(AdminEventMulticaster.java:1445)
         at com.sun.enterprise.admin.event.AdminEventMulticaster.handleShutdownEvent(AdminEventMulticaster.java:1434)
         at com.sun.enterprise.admin.event.AdminEventMulticaster.processEvent(AdminEventMulticaster.java:443)
         at com.sun.enterprise.admin.event.AdminEventMulticaster.multicastEvent(AdminEventMulticaster.java:139)
         at com.sun.enterprise.admin.server.core.channel.AdminChannelServer.sendNotification(AdminChannelServer.java:90)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:585)
         at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294)
         at sun.rmi.transport.Transport$1.run(Transport.java:153)
         at java.security.AccessController.doPrivileged(Native Method)
         at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
         at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460)
         at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701)
         at java.lang.Thread.run(Thread.java:595)
    thanks

    I just had the same problem this morning. I believe the app server starts and if you browser directly to your app you'd get it, but the connection between the appserver and the IDE is somehow lost. An easier solution than completely reinstalling for me was to delete the .Creator folder in my home directory (C;|Documents and Setting\<username>\.Creator) and restart Creator

  • Workflow could not start in HCM process and Forms

    Hi All
    It would be really helpful if you can suggest possible solution regarding case management case in HCM forms and process.
    I have set up a simple custom HCM process and Form regarding Infotype 2 updation. I have checked the process and form consistency and it seems fine. Now when I run the process from HRASR_DT it generates a process number but it also gives an error workflow could not start.I get following error (SWIA log - Step history)
    Executing flow work item - Transaction brackets of the workflow has been damaged
    Exception occurred - Error when starting work item 000000007031
    PROCESS_NODE - Error when processing node '0000000014' (ParForEach index 000000)
    CREATE - Error when creating a component of type 'Step'
    CREATE_WIM_HANDLE - Error when creating a work item
    CREATE_VIA_WFM - Exit CL_HRASR00_POBJ_WF_EXIT triggered exeception for event CREATED and (target) status
    EVENT_RAISED - Error updating the process object
    Executing flow work item - Exit CL_HRASR00_POBJ_WF_EXIT triggered exeception for event STATE_CHG and (target) status READY->ERROR
    EVENT_RAISED - Error updating the process object
    Executing flow work item - Transaction brackets of the workflow has been damaged
    Executing flow work item - Work item 000000007031: Object FLOWITEM method EXECUTE cannot be executed
    Executing flow work item - Error when processing node '0000000014' (ParForEach index 000000)
    I have searched few SAP notes such as 1384961 which talks about same error but it is implemented in our system (EA-HR 604 , Patch 27, )
    Appreciate any help.
    Thanks
    Umang

    Hi Swati
    One of the similar (not exact) issues were resolved by correcting the event linkage....please refer thread:
    http://scn.sap.com/message/14848795#14848795
    Not sure of the details of the the resolution, maybe Ragavendran Kanagaraj can throw more light.
    Just some high level checks (if not done already):
    Check event linkage errors in SWEQADM if anything is related to your WF
    Check in SWEL if it's showing any more details (not sure if it will)
    Any warnings in syntax check of WF template (PFTC) or WF definition (SWDD)
    Any error sin binding
    regards,
    Modak

  • 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

Maybe you are looking for