Startup the Mobile Engine via Eclipse

Dear all,
In our company, we are using the MAM for a couple of years. I am doing all the developments via Eclipse.
For debugging the MAM or starting up the MAM from my development environment, I've made a small startup class which starts up the Mobile Engine and launches a browser. All works fine, except that I have to login every time again, and I want to login automatically (by providing the username and password in my startup class, so I can bypass the login screen).
Is there anyone who knows how to login (via JAVA) in the Mobile Engine?
This is the code I use to startup the Mobile Engine:
public static void main(String[] args)
     String [] arg = {"-home:C:\\Program Files\\SAP Mobile Infrastructure", "-trace", "-url:MAM25/start", "-app:jsp"};
     FrameworkInitializer.main(arg);
     openWebBrowser("iexplore", "http://localhost:4444");
I have tried already to add something like
"-logonuser:POLMKT", "-logonpwd:init123"
as an extra argument, but it doesn't seem to work...
Thanks in advance!
Best regards,
Diederik Van Wassenhove

Hello Sivakumar,
Thanks for your reply!
In the meanwhile, I have found another method to do it via the following JAVA code. Maybe it is helpful for someone else as well:
import com.sap.ip.me.api.user.LogonException;
import com.sap.ip.me.api.user.UserManager;
UserManager userManager = UserManager.getInstance();
try
     userManager.logOnUser(user, password);
     System.out.println("User " + user + " logged in");
catch (LogonException e)
     System.out.println("Not able to login user" + user + "!");
     e.printStackTrace();

Similar Messages

  • Adobe Drive not connecting to hello world sample launched via Eclipse

    I'm trying to get the hello world sample running with Drive SDK 5. I got:
    Adobe Drive 5.0.1
    AdobeDriveSDK-5.0.0.398770.zip
    latest Java JRE 1.6
    Eclipes 4.3.1 (Kepler SR 1)
    Windows 7 64bit
    I configured the hello world project as described in the getting started guide. I double checked that AD4ServiceManager.exe is not running. After starting the project in Eclipse and waiting about 15 seconds, all bundles are active:
    osgi> ss
    Framework is launched.
    id     State       Bundle
    0     ACTIVE      org.eclipse.osgi_3.5.0.v20090520
    1     ACTIVE      com.adobe.csi.ncomm_2.0.0.28
    2     ACTIVE      com.adobe.drive.core_2.0.0.28
    3     ACTIVE      org.eclipse.equinox.cm_1.0.100.v20090520-1800
    4     ACTIVE      org.eclipse.equinox.preferences_3.2.300.v20090520-1800
    5     ACTIVE      org.eclipse.equinox.app_1.2.0.v20090520-1800
    6     ACTIVE      com.adobe.drive.biz.filesystem_2.0.0.28
    7     ACTIVE      javax.servlet_2.5.0.v200806031605
    8     ACTIVE      org.eclipse.equinox.launcher_1.0.200.v20090520
    9     ACTIVE      com.adobe.drive.manager.executor_1.0.0.28
    10     ACTIVE      com.adobe.drive.connector.cmis_2.0.0.28
    11     ACTIVE      com.adobe.drive.ui_2.0.0.28
                     Fragments=27
    12     ACTIVE      org.hsqldb_2.2.9
    13     ACTIVE      com.adobe.drive.model.synchronization_2.0.0.28
    14     ACTIVE      com.adobe.drive.data.persistence.api_2.0.0.28
    15     ACTIVE      org.eclipse.equinox.ds_1.1.0.v20090601
    16     ACTIVE      org.eclipse.update.configurator_3.3.0.v20090312
    17     ACTIVE      org.hibernate_3.2.5
    18     ACTIVE      com.adobe.csi.core_2.0.0.28
    19     ACTIVE      com.adobe.drive.connector.service_2.0.0.28
    20     ACTIVE      com.adobe.drive.model_2.0.0.28
    21     ACTIVE      com.adobe.drive.data.provider_2.0.0.28
    22     ACTIVE      com.adobe.csi.auth.keystore_2.0.0.28
    23     ACTIVE      com.adobe.drive.connector.api_2.0.0.28
    24     ACTIVE      com.adobe.drive.data.persistence.hsqldb_2.0.0.28
    25     ACTIVE      com.adobe.drive.data.cache_2.0.0.28
    26     ACTIVE      org.apache.commons.codec_1.0.0.28
    27     RESOLVED    com.adobe.drive.ui.scripting_2.0.0.28
                     Master=11
    28     ACTIVE      org.apache.commons.net_1.4.1
    29     ACTIVE      sample.helloworld_2.0.0
    30     ACTIVE      com.adobe.csi.bootstrap_2.0.0.28
    31     ACTIVE      com.adobe.drive.data.manager_2.0.0.28
    32     ACTIVE      org.apache.commons.logging_1.0.4
    33     ACTIVE      com.adobe.versioncue.nativecomm_4.0.1.28
    34     ACTIVE      com.adobe.drive.biz.versioncue.api_2.0.0.28
    35     ACTIVE      org.eclipse.equinox.common_3.5.0.v20090520-1800
    36     ACTIVE      com.adobe.csi.pipes_2.0.0
    37     ACTIVE      com.adobe.drive.data.model_2.0.0.28
    38     ACTIVE      com.adobe.drive.data.persistence_2.0.0.28
    39     ACTIVE      com.adobe.drive.processinfo_2.0.0.28
    40     ACTIVE      com.adobe.drive.connector.cmis.client_2.0.0.28
    41     ACTIVE      com.adobe.drive.ncomm.filesystem_2.0.0.28
    42     ACTIVE      org.eclipse.equinox.registry_3.4.100.v20090520-1800
    43     ACTIVE      org.apache.commons.httpclient_3.1.0
    44     ACTIVE      com.adobe.drive.vcdetector_2.0.0
    45     ACTIVE      com.adobe.drive.ncomm.versioncue_2.0.0.28
    46     ACTIVE      com.adobe.drive.connector.cqdam_4.0.0.28
    47     ACTIVE      com.adobe.csi.core.preferences_2.0.0.28
    48     ACTIVE      org.eclipse.equinox.util_1.0.100.v20090520-1800
    49     ACTIVE      com.adobe.csi.utils_2.0.0.28
    50     ACTIVE      com.adobe.drive.biz.automount_2.0.0.28
    51     ACTIVE      com.adobe.csi.core.logging_2.0.0.28
    52     ACTIVE      com.adobe.drive.manager.interests_2.0.0.28
    53     ACTIVE      org.apache.log4j_1.2.15
    54     ACTIVE      com.adobe.drive.ifs_2.0.0.28
    55     ACTIVE      com.adobe.drive.core.jobs_2.0.0.28
    56     ACTIVE      org.eclipse.osgi.services_3.2.0.v20090520-1800
    57     ACTIVE      com.adobe.drive.biz.versioncue_2.0.0.28
    58     ACTIVE      com.adobe.csi.auth_2.0.0.28
    Also, the output of csstat looks fine:
    osgi> csstat
    Registered connector factories (schema : reference):
    cmis : {org.osgi.service.component.ComponentFactory}={component.factory=com.adobe.drive.connector.handlerfactory, component.name=com.adobe.drive.connector.cmis#cmis, service.id=48}
    cq : {org.osgi.service.component.ComponentFactory}={component.factory=com.adobe.drive.connector.handlerfactory, component.name=cq#cq, service.id=75}
    helloworld : {org.osgi.service.component.ComponentFactory}={component.factory=com.adobe.drive.connector.handlerfactory, component.name=sample.helloworld#helloworld, service.id=70}
    Instantiated connector factories (uuid : factory):
    Afterwards, I start Adobe Drive (32bit version). The UI hangs with the message "Adobe Drive is starting. Please wait.". From task manager I can see that not just Adobe Drive was started, but also AD4ServiceManager.exe. I guess, this should not happen, because Adobe Drive should discover the one launched via Eclipse.
    So what's going wrong here? How does Adobe Drive discover the one launched via Eclipse? What could block discovery?
    Here more details in case that helps debugging the problem. MANIFEST.MF:
    Manifest-Version: 1.0
    Bundle-ManifestVersion: 2
    Bundle-Name: HelloWorld Plug-in
    Bundle-SymbolicName: sample.helloworld
    Bundle-Version: 2.0.0
    Bundle-Vendor: Adobe Systems
    Adobe-AutoStart: true
    Require-Bundle: com.adobe.drive.connector.api,
    com.adobe.drive.core,
    com.adobe.drive.model,
    com.adobe.csi.utils
    Service-Component: OSGI-INF/HelloWorldHandlerFactory.xml
    build.properties
    source.. = src/
    output.. = bin/
    bin.includes = META-INF/,\
                   OSGI-INF/
    HelloWorldHandlerFactory.xml:
    <?xml version="1.0"?>
         <component name="sample.helloworld#helloworld"
         factory="com.adobe.drive.connector.handlerfactory">
         <implementation class="sample.helloworld.HelloWorldHandlerFactory"/>
    </component>
    Here the Eclipse run configuration settings:

    Wow, this seems to help even though it is still a bit shaky. Here the steps I have to do to get it working:
    manually launch 64bit version of AD4ServiceManager.exe with parameter -launchedbydrive
    launch Eclipse project and wait till ss shows everything as registered (much faster now)
    start 64bit version of Drive -> my adapter doesn't show up
    shutdown drive
    start 64bit version of Drive again -> my adapter now shows up and works as expected
    I find a few things confusing here:
    In Eclipse, should I configure the 32bit or 64bit version of AD4ServiceManager as plugin execution environment? Currently, I'm using the 32bit version.
    Why isn't the step of manually launching AD4ServiceManager.exe not mentioned in the getting started guide?
    I will reboot my machine to see if it is still working or just some special sun radiation making it work currently :-)

  • I don't have a DSL or cable modem to access the Internet ... just a mobile WiFi (there is no cable available at our house). How do I connect my Time Capsule to the Internet via the mobile WiFi?

    I don't have a DSL or cable modem to access the Internet ... just a mobile WiFi (there is no cable available at our house and the mobile WiFi is our only option). How do I connect my Time Capsule to the Internet via the mobile WiFi?

    LOL!!
    I am in Australia and the ISP... I think both the main ones would fit your description to a T.. big T in particular.
    Your router is really unsuitable.. if it is only wireless and no ethernet.. just buy an ethernet one.
    Do a search on ebay.. 3g router.
    But you can get the TC to join a wireless network.
    It is a non-standard setup that Apple will not support.. the option is hidden.
    If you are on Lion download the 5.6 utility. Go to the wireless set up page and hold down the option key whilst selecting wireless mode.. a new option, join will appear. You can then put in the ssid and passkey of the 3g router.
    But please note the end result of this setup..
    very slow speed. The TC is now a second wireless hop from your clients.. this will halve the speed.
    In this mode the ethernet are deactived.. for reasons only Apple know, they decided you should not use ethernet when doing this.

  • Could not find the Database Engine startup handle.

    Why can't Microsoft make software that "Just Works" any more.
    This is Sooooo frustrating!  I'm a developer.  I want to write database software and I'd like to use SQL Server.  But I can't even get the damn thing to install on a fresh Windows 8.1 installation. 
    MySQL - installs no problem - it just works.
    Oracle - Installs no problem - It just works. 
    I downloaded SQL Server 2012 Express with SP1, ran the Install, took most of the defaults, and I get:
    Install Failed:
    The following error has occurred:
    Could not find the Database Engine startup handle.
    For help, click:
    http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft%20SQL%20Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%25400x4BDAF9BA%25401306%254025
    Of course, clicking on the link takes me to a non existing web page - what else?  Just incompetence everywhere.  This is Microsoft's own operating system yet they can't even get their own database to install while their competitors can.
    How can they let this happen!
    Then I googled the above error message.  - Hundreds of hits and a lot of them are threads in forums and lots of civilians saying "try this try that"  none of which works. Not a single Microsoft Employee to be found in any of the
    discussions or answers.  And this same problem has been happening since 2008! Yet Microsoft can't be bothered to fix it.
    This kind of buggy software shouldn't have made it past Alpha testing.
    Come on Microsoft, you just have to try harder.  I can understand bugs that happen in unusual circumstances, after all I'm a developer too.  But this won't even install on a clean Windows 8.  It's tantamount to releasing a "Hello
    World"  program that crashes on startup!

    Hi Bob,
    If you make sure all your hardware and software requirements are met for installation of SQL Server 2012 on window 8.1 Its highly unlikely you will face issue.I can understand your situation so let me help you.As Kalman pointed can you paste output
    of setup log file which was generated due to failed installation using Kalman's link.
    Did you went thorugh below link
    How to install SQL server on Win 8.1
    Hardware and software requirements for SQL Server 2012
    Please first read above links understand how it works and then proceed
    Regarding startup handle error .AFAIK its because of Account with which you are trying to install SQL server somehow is not able to start it up after installation.Basically a righst issue.Can be different in some cases.Now whenever you install SQL server
    alsway RK on Setup file and select run as administrator.When you reach page window where you need to select startup account for SQL Server please select NT Authority\System( or local system account) .
    Details with steps
    http://social.technet.microsoft.com/wiki/contents/articles/24364.sql-server-troubleshooting-could-not-find-database-engine-startup-handle-error-during-installation.aspx
    Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

  • Setup problem - sql server 2014 - "could not find the database engine startup handle" - 0x851a0019

    I tried to install ,deleted and re-installed several times and no help at all.
    visual studio 2013 with update 2 rc and adk installed in my computer.
    error code: 0x851a0019
    error messege in setup: could not find the database engine startup handle
    edition: Microsoft SQL Server 2014 Enterprise (Evaluation)
    logs:
    Overall summary:
      Final result:                  Failed: see details below
      Exit code (Decimal):           -2061893607
      Start time:                    2014-04-03 13:53:29
      End time:                      2014-04-03 14:47:48
      Requested action:              Install
    Setup completed with required actions for features.
    Troubleshooting information for those features:
      Next step for RS:              Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Next step for SQLEngine:       Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Next step for DQ:              Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Next step for FullText:        Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Next step for Replication:     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
    Machine Properties:
      Machine name:                  ARIELUBA-PC
      Machine processor count:       8
      OS version:                    Windows 8
      OS service pack:               
      OS region:                     United States
      OS language:                   English (United States)
      OS architecture:               x64
      Process architecture:          64 Bit
      OS clustered:                  No
    Product features discovered:
      Product              Instance             Instance ID                    Feature                
                     Language             Edition              Version         Clustered  Configured
      SQL Server 2012      SQLEXPRESS           MSSQL11.SQLEXPRESS             Database Engine Services                 1033      
              Express Edition      11.1.3128.0     No         Yes       
      SQL Server 2012      SQLEXPRESS           MSSQL11.SQLEXPRESS             SQL Server Replication                   1033      
              Express Edition      11.1.3128.0     No         Yes       
      SQL Server 2012      ADK                  MSSQL11.ADK                    Database Engine Services            
        1033                 Express Edition      11.0.2100.60    No         Yes       
      SQL Server 2012      ADK                  MSSQL11.ADK                    SQL Server Replication              
        1033                 Express Edition      11.0.2100.60    No         Yes       
      SQL Server 2012                                                          LocalDB        
                             1033                 Express Edition      11.1.3412.0     No         Yes    
    Package properties:
      Description:                   Microsoft SQL Server 2014 
      ProductName:                   SQL Server 2014
      Type:                          RTM
      Version:                       12
      SPLevel:                       0
      Installation location:         C:\Users\Arie Luba\Downloads\WS2012R2DC\SQLServer2014-x64-ENU\x64\setup\
      Installation edition:          Evaluation
    Product Update Status:
      None discovered.
    User Input Settings:
      ACTION:                        Install
      ADDCURRENTUSERASSQLADMIN:      true
      AGTSVCACCOUNT:                 NT Service\SQLSERVERAGENT
      AGTSVCPASSWORD:                *****
      AGTSVCSTARTUPTYPE:             Manual
      ASBACKUPDIR:                   C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Backup
      ASCOLLATION:                   Hebrew_CI_AS
      ASCONFIGDIR:                   C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Config
      ASDATADIR:                     C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Data
      ASLOGDIR:                      C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Log
      ASPROVIDERMSOLAP:              1
      ASSERVERMODE:                  MULTIDIMENSIONAL
      ASSVCACCOUNT:                  NT Service\MSSQLServerOLAPService
      ASSVCPASSWORD:                 <empty>
      ASSVCSTARTUPTYPE:              Automatic
      ASSYSADMINACCOUNTS:            ARIELUBA-PC\Arie Luba
      ASTEMPDIR:                     C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Temp
      BROWSERSVCSTARTUPTYPE:         Automatic
      CLTCTLRNAME:                   
      CLTRESULTDIR:                  C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir\
      CLTSTARTUPTYPE:                Manual
      CLTSVCACCOUNT:                 NT Service\SQL Server Distributed Replay Client
      CLTSVCPASSWORD:                <empty>
      CLTWORKINGDIR:                 C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\WorkingDir\
      COMMFABRICENCRYPTION:          0
      COMMFABRICNETWORKLEVEL:        0
      COMMFABRICPORT:                0
      CONFIGURATIONFILE:             C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140403_135327\ConfigurationFile.ini
      CTLRSTARTUPTYPE:               Manual
      CTLRSVCACCOUNT:                NT Service\SQL Server Distributed Replay Controller
      CTLRSVCPASSWORD:               <empty>
      CTLRUSERS:                     ARIELUBA-PC\Arie Luba
      ENABLERANU:                    false
      ENU:                           true
      ERRORREPORTING:                false
      FEATURES:                      SQLENGINE, REPLICATION, FULLTEXT, DQ, AS, RS, RS_SHP, RS_SHPWFE, DQC, CONN, IS, BC, SDK, BOL, SSMS, ADV_SSMS, DREPLAY_CTLR, DREPLAY_CLT, MDS
      FILESTREAMLEVEL:               0
      FILESTREAMSHARENAME:           <empty>
      FTSVCACCOUNT:                  NT Service\MSSQLFDLauncher
      FTSVCPASSWORD:                 <empty>
      HELP:                          false
      IACCEPTSQLSERVERLICENSETERMS:  true
      INDICATEPROGRESS:              false
      INSTALLSHAREDDIR:              C:\Program Files\Microsoft SQL Server\
      INSTALLSHAREDWOWDIR:           C:\Program Files (x86)\Microsoft SQL Server\
      INSTALLSQLDATADIR:             <empty>
      INSTANCEDIR:                   C:\Program Files\Microsoft SQL Server\
      INSTANCEID:                    MSSQLSERVER
      INSTANCENAME:                  MSSQLSERVER
      ISSVCACCOUNT:                  NT Service\MsDtsServer120
      ISSVCPASSWORD:                 <empty>
      ISSVCSTARTUPTYPE:              Automatic
      MATRIXCMBRICKCOMMPORT:         0
      MATRIXCMSERVERNAME:            <empty>
      MATRIXNAME:                    <empty>
      NPENABLED:                     0
      PID:                           *****
      QUIET:                         false
      QUIETSIMPLE:                   false
      ROLE:                          AllFeatures_WithDefaults
      RSINSTALLMODE:                 DefaultNativeMode
      RSSHPINSTALLMODE:              SharePointFilesOnlyMode
      RSSVCACCOUNT:                  NT Service\ReportServer
      RSSVCPASSWORD:                 <empty>
      RSSVCSTARTUPTYPE:              Automatic
      SAPWD:                         <empty>
      SECURITYMODE:                  <empty>
      SQLBACKUPDIR:                  <empty>
      SQLCOLLATION:                  Hebrew_CI_AS
      SQLSVCACCOUNT:                 NT Service\MSSQLSERVER
      SQLSVCPASSWORD:                <empty>
      SQLSVCSTARTUPTYPE:             Automatic
      SQLSYSADMINACCOUNTS:           ARIELUBA-PC\Arie Luba
      SQLTEMPDBDIR:                  <empty>
      SQLTEMPDBLOGDIR:               <empty>
      SQLUSERDBDIR:                  <empty>
      SQLUSERDBLOGDIR:               <empty>
      SQMREPORTING:                  false
      TCPENABLED:                    1
      UIMODE:                        Normal
      UpdateEnabled:                 true
      UpdateSource:                  MU
      USEMICROSOFTUPDATE:            false
      X86:                           false
      Configuration file:            C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140403_135327\ConfigurationFile.ini
    Detailed results:
      Feature:                       Management Tools - Complete
      Status:                        Passed
      Feature:                       Client Tools Connectivity
      Status:                        Passed
      Feature:                       Client Tools SDK
      Status:                        Passed
      Feature:                       Client Tools Backwards Compatibility
      Status:                        Passed
      Feature:                       Management Tools - Basic
      Status:                        Passed
      Feature:                       Reporting Services - Native
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Component name:                SQL Server Database Engine Services Instance Features
      Component error code:          0x851A0019
      Error description:             Could not find the Database Engine startup handle.
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025
      Feature:                       Database Engine Services
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred during the setup process of the feature.
      Next Step:                     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Component name:                SQL Server Database Engine Services Instance Features
      Component error code:          0x851A0019
      Error description:             Could not find the Database Engine startup handle.
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025
      Feature:                       Data Quality Services
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Component name:                SQL Server Database Engine Services Instance Features
      Component error code:          0x851A0019
      Error description:             Could not find the Database Engine startup handle.
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025
      Feature:                       Full-Text and Semantic Extractions for Search
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Component name:                SQL Server Database Engine Services Instance Features
      Component error code:          0x851A0019
      Error description:             Could not find the Database Engine startup handle.
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025
      Feature:                       SQL Server Replication
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Component name:                SQL Server Database Engine Services Instance Features
      Component error code:          0x851A0019
      Error description:             Could not find the Database Engine startup handle.
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025
      Feature:                       Master Data Services
      Status:                        Passed
      Feature:                       Distributed Replay Client
      Status:                        Passed
      Feature:                       Distributed Replay Controller
      Status:                        Passed
      Feature:                       Integration Services
      Status:                        Passed
      Feature:                       Data Quality Client
      Status:                        Passed
      Feature:                       Analysis Services
      Status:                        Passed
      Feature:                       Reporting Services - SharePoint
      Status:                        Passed
      Feature:                       Reporting Services Add-in for SharePoint Products
      Status:                        Passed
      Feature:                       SQL Browser
      Status:                        Passed
      Feature:                       Documentation Components
      Status:                        Passed
      Feature:                       SQL Writer
      Status:                        Passed
      Feature:                       Setup Support Files
      Status:                        Passed
    Rules with failures:
    Global rules:
    Scenario specific rules:
    Rules report file:               C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140403_135327\SystemConfigurationCheck_Report.htm
    2014-04-03 14:14:28.01 Server      Microsoft SQL Server 2014 - 12.0.2000.8 (X64) 
    Feb 20 2014 20:04:26 
    Copyright (c) Microsoft Corporation
    Enterprise Evaluation Edition (64-bit) on Windows NT 6.3 <X64> (Build 9600: ) (Hypervisor)
    2014-04-03 14:14:28.01 Server      UTC adjustment: 3:00
    2014-04-03 14:14:28.01 Server      (c) Microsoft Corporation.
    2014-04-03 14:14:28.01 Server      All rights reserved.
    2014-04-03 14:14:28.01 Server      Server process ID is 7148.
    2014-04-03 14:14:28.01 Server      System Manufacturer: 'Dell Inc.', System Model: 'Inspiron N5110'.
    2014-04-03 14:14:28.01 Server      Authentication mode is WINDOWS-ONLY.
    2014-04-03 14:14:28.01 Server      Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
    2014-04-03 14:14:28.01 Server      The service account is 'NT Service\MSSQLSERVER'. This is an informational message; no user action is required.
    2014-04-03 14:14:28.01 Server      Registry startup parameters: 
    -d C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\DATA\master.mdf
    -e C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Log\ERRORLOG
    -l C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
    2014-04-03 14:14:28.01 Server      Command Line Startup Parameters:
    -s "MSSQLSERVER"
    -m "SqlSetup"
    -Q
    -q "Hebrew_CI_AS"
    -T 4022
    -T 4010
    -T 3659
    -T 3610
    -T 8015
    2014-04-03 14:14:28.28 Server      SQL Server detected 1 sockets with 4 cores per socket and 8 logical processors per socket, 8 total logical processors; using 8 logical processors based on SQL Server licensing. This is an informational message;
    no user action is required.
    2014-04-03 14:14:28.28 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
    2014-04-03 14:14:28.28 Server      Detected 8099 MB of RAM. This is an informational message; no user action is required.
    2014-04-03 14:14:28.28 Server      Using conventional memory in the memory manager.
    2014-04-03 14:14:28.31 Server      Default collation: SQL_Latin1_General_CP1_CI_AS (us_english 1033)
    2014-04-03 14:14:28.34 Server      Perfmon counters for resource governor pools and groups failed to initialize and are disabled.
    2014-04-03 14:14:28.36 Server      Query Store settings initialized with enabled = 1, 
    2014-04-03 14:14:28.36 Server      The maximum number of dedicated administrator connections for this instance is '1'
    2014-04-03 14:14:28.36 Server      Node configuration: node 0: CPU mask: 0x00000000000000ff:0 Active CPU mask: 0x00000000000000ff:0. This message provides a description of the NUMA configuration for this computer. This is an informational message
    only. No user action is required.
    2014-04-03 14:14:28.38 Server      Using dynamic lock allocation.  Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.  This is an informational message only.  No user action is required.
    2014-04-03 14:14:28.39 Server      Database Mirroring Transport is disabled in the endpoint configuration.
    2014-04-03 14:14:28.39 spid8s      Warning ******************
    2014-04-03 14:14:28.39 spid8s      SQL Server started in single-user mode. This an informational message only. No user action is required.
    2014-04-03 14:14:28.40 spid8s      Starting up database 'master'.
    2014-04-03 14:14:28.42 Server      Software Usage Metrics is disabled.
    2014-04-03 14:14:28.48 Server      CLR version v4.0.30319 loaded.
    2014-04-03 14:14:28.56 Server      Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
    2014-04-03 14:14:28.62 spid8s      SQL Server Audit is starting the audits. This is an informational message. No user action is required.
    2014-04-03 14:14:28.63 spid8s      SQL Server Audit has started the audits. This is an informational message. No user action is required.
    2014-04-03 14:14:28.64 spid8s      SQL Trace ID 1 was started by login "sa".
    2014-04-03 14:14:28.64 spid8s      Server name is 'ARIELUBA-PC'. This is an informational message only. No user action is required.
    2014-04-03 14:14:28.65 spid16s     Password policy update was successful.
    2014-04-03 14:14:28.66 spid16s     Error: 17190, Severity: 16, State: 1.
    2014-04-03 14:14:28.66 spid16s     Initializing the FallBack certificate failed with error code: 1, state: 20, error number: 0.
    2014-04-03 14:14:28.66 spid16s     Unable to initialize SSL encryption because a valid certificate could not be found, and it is not possible to create a self-signed certificate.
    2014-04-03 14:14:28.66 spid16s     Error: 17182, Severity: 16, State: 1.
    2014-04-03 14:14:28.66 spid16s     TDSSNIClient initialization failed with error 0x80092004, status code 0x80. Reason: Unable to initialize SSL support. Cannot find object or property. 
    2014-04-03 14:14:28.66 spid16s     Error: 17182, Severity: 16, State: 1.
    2014-04-03 14:14:28.66 spid16s     TDSSNIClient initialization failed with error 0x80092004, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. Cannot find object or property. 
    2014-04-03 14:14:28.66 spid16s     Error: 17826, Severity: 18, State: 3.
    2014-04-03 14:14:28.66 spid16s     Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
    2014-04-03 14:14:28.67 spid16s     Error: 17120, Severity: 16, State: 1.
    2014-04-03 14:14:28.67 spid16s     SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
    ________________________________________________________________________________________________

    Is it okay? (see below)
    ;SQL Server 2014 Configuration File
    [OPTIONS]
    ; Specifies a Setup work flow, like INSTALL, UNINSTALL, or UPGRADE. This is a required parameter. 
    ACTION="Install"
    ; Detailed help for command line argument ROLE has not been defined yet. 
    ROLE="AllFeatures_WithDefaults"
    ; Use the /ENU parameter to install the English version of SQL Server on your localized Windows operating system. 
    ENU="True"
    ; Parameter that controls the user interface behavior. Valid values are Normal for the full UI,AutoAdvance for a simplied UI, and EnableUIOnServerCore for bypassing Server Core setup GUI block. 
    UIMODE="Normal"
    ; Setup will not display any user interface. 
    QUIET="False"
    ; Setup will display progress only, without any user interaction. 
    QUIETSIMPLE="False"
    ; Specify whether SQL Server Setup should discover and include product updates. The valid values are True and False or 1 and 0. By default SQL Server Setup will include updates that are found. 
    UpdateEnabled="True"
    ; Specify if errors can be reported to Microsoft to improve future SQL Server releases. Specify 1 or True to enable and 0 or False to disable this feature. 
    ERRORREPORTING="False"
    ; If this parameter is provided, then this computer will use Microsoft Update to check for updates. 
    USEMICROSOFTUPDATE="False"
    ; Specifies features to install, uninstall, or upgrade. The list of top-level features include SQL, AS, RS, IS, MDS, and Tools. The SQL feature will install the Database Engine, Replication, Full-Text, and Data Quality Services (DQS) server. The Tools feature
    will install Management Tools, Books online components, SQL Server Data Tools, and other shared components. 
    FEATURES=SQLENGINE,REPLICATION,FULLTEXT,DQ,AS,RS,RS_SHP,RS_SHPWFE,DQC,CONN,IS,BC,SDK,BOL,SSMS,ADV_SSMS,DREPLAY_CTLR,DREPLAY_CLT,MDS
    ; Specify the location where SQL Server Setup will obtain product updates. The valid values are "MU" to search Microsoft Update, a valid folder path, a relative path such as .\MyUpdates or a UNC share. By default SQL Server Setup will search Microsoft Update
    or a Windows Update service through the Window Server Update Services. 
    UpdateSource="MU"
    ; Displays the command line parameters usage 
    HELP="False"
    ; Specifies that the detailed Setup log should be piped to the console. 
    INDICATEPROGRESS="False"
    ; Specifies that Setup should install into WOW64. This command line argument is not supported on an IA64 or a 32-bit system. 
    X86="False"
    ; Specify the root installation directory for shared components.  This directory remains unchanged after shared components are already installed. 
    INSTALLSHAREDDIR="C:\Program Files\Microsoft SQL Server"
    ; Specify the root installation directory for the WOW64 shared components.  This directory remains unchanged after WOW64 shared components are already installed. 
    INSTALLSHAREDWOWDIR="C:\Program Files (x86)\Microsoft SQL Server"
    ; Specify a default or named instance. MSSQLSERVER is the default instance for non-Express editions and SQLExpress for Express editions. This parameter is required when installing the SQL Server Database Engine (SQL), Analysis Services (AS), or Reporting Services
    (RS). 
    INSTANCENAME="MSSQLSERVER"
    ; Specify that SQL Server feature usage data can be collected and sent to Microsoft. Specify 1 or True to enable and 0 or False to disable this feature. 
    SQMREPORTING="False"
    ; Specify the Instance ID for the SQL Server features you have specified. SQL Server directory structure, registry structure, and service names will incorporate the instance ID of the SQL Server instance. 
    INSTANCEID="MSSQLSERVER"
    ; The computer name that the client communicates with for the Distributed Replay Controller service. 
    CLTCTLRNAME="SQLDRC"
    ; The Windows account(s) used to grant permission to the Distributed Replay Controller service. 
    CTLRUSERS="ARIELUBA-PC\Arie Luba"
    ; The account used by the Distributed Replay Controller service. 
    CTLRSVCACCOUNT="NT Service\SQL Server Distributed Replay Controller"
    ; The startup type for the Distributed Replay Controller service. 
    CTLRSTARTUPTYPE="Manual"
    ; The account used by the Distributed Replay Client service. 
    CLTSVCACCOUNT="NT Service\SQL Server Distributed Replay Client"
    ; The startup type for the Distributed Replay Client service. 
    CLTSTARTUPTYPE="Manual"
    ; The result directory for the Distributed Replay Client service. 
    CLTRESULTDIR="C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir"
    ; The working directory for the Distributed Replay Client service. 
    CLTWORKINGDIR="C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\WorkingDir"
    ; RSInputSettings_RSInstallMode_Description 
    RSINSTALLMODE="DefaultNativeMode"
    ; RSInputSettings_RSInstallMode_Description 
    RSSHPINSTALLMODE="SharePointFilesOnlyMode"
    ; Specify the installation directory. 
    INSTANCEDIR="C:\Program Files\Microsoft SQL Server"
    ; Agent account name 
    AGTSVCACCOUNT="NT Service\SQLSERVERAGENT"
    ; Auto-start service after installation.  
    AGTSVCSTARTUPTYPE="Manual"
    ; Startup type for Integration Services. 
    ISSVCSTARTUPTYPE="Automatic"
    ; Account for Integration Services: Domain\User or system account. 
    ISSVCACCOUNT="NT Service\MsDtsServer120"
    ; The name of the account that the Analysis Services service runs under. 
    ASSVCACCOUNT="NT Service\MSSQLServerOLAPService"
    ; Controls the service startup type setting after the service has been created. 
    ASSVCSTARTUPTYPE="Automatic"
    ; The collation to be used by Analysis Services. 
    ASCOLLATION="Hebrew_CI_AS"
    ; The location for the Analysis Services data files. 
    ASDATADIR="C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Data"
    ; The location for the Analysis Services log files. 
    ASLOGDIR="C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Log"
    ; The location for the Analysis Services backup files. 
    ASBACKUPDIR="C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Backup"
    ; The location for the Analysis Services temporary files. 
    ASTEMPDIR="C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Temp"
    ; The location for the Analysis Services configuration files. 
    ASCONFIGDIR="C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Config"
    ; Specifies whether or not the MSOLAP provider is allowed to run in process. 
    ASPROVIDERMSOLAP="1"
    ; Specifies the list of administrator accounts that need to be provisioned. 
    ASSYSADMINACCOUNTS="ARIELUBA-PC\Arie Luba"
    ; Specifies the server mode of the Analysis Services instance. Valid values are MULTIDIMENSIONAL and TABULAR. The default value is MULTIDIMENSIONAL. 
    ASSERVERMODE="MULTIDIMENSIONAL"
    ; CM brick TCP communication port 
    COMMFABRICPORT="0"
    ; How matrix will use private networks 
    COMMFABRICNETWORKLEVEL="0"
    ; How inter brick communication will be protected 
    COMMFABRICENCRYPTION="0"
    ; TCP port used by the CM brick 
    MATRIXCMBRICKCOMMPORT="0"
    ; Startup type for the SQL Server service. 
    SQLSVCSTARTUPTYPE="Automatic"
    ; Level to enable FILESTREAM feature at (0, 1, 2 or 3). 
    FILESTREAMLEVEL="0"
    ; Set to "1" to enable RANU for SQL Server Express. 
    ENABLERANU="False"
    ; Specifies a Windows collation or an SQL collation to use for the Database Engine. 
    SQLCOLLATION="Hebrew_CI_AS"
    ; Account for SQL Server service: Domain\User or system account. 
    SQLSVCACCOUNT="NT Service\MSSQLSERVER"
    ; Windows account(s) to provision as SQL Server system administrators. 
    SQLSYSADMINACCOUNTS="ARIELUBA-PC\Arie Luba"
    ; Provision current user as a Database Engine system administrator for %SQL_PRODUCT_SHORT_NAME% Express. 
    ADDCURRENTUSERASSQLADMIN="True"
    ; Specify 0 to disable or 1 to enable the TCP/IP protocol. 
    TCPENABLED="1"
    ; Specify 0 to disable or 1 to enable the Named Pipes protocol. 
    NPENABLED="0"
    ; Startup type for Browser Service. 
    BROWSERSVCSTARTUPTYPE="Automatic"
    ; Specifies which account the report server NT service should execute under.  When omitted or when the value is empty string, the default built-in account for the current operating system.
    ; The username part of RSSVCACCOUNT is a maximum of 20 characters long and
    ; The domain part of RSSVCACCOUNT is a maximum of 254 characters long. 
    RSSVCACCOUNT="NT Service\ReportServer"
    ; Specifies how the startup mode of the report server NT service.  When 
    ; Manual - Service startup is manual mode (default).
    ; Automatic - Service startup is automatic mode.
    ; Disabled - Service is disabled 
    RSSVCSTARTUPTYPE="Automatic"
    ; Add description of input argument FTSVCACCOUNT 
    FTSVCACCOUNT="NT Service\MSSQLFDLauncher"

  • SQL Server Express 2014 on Win8.1: Could not find the Database Engine startup handle

    Hello,
    I tried to follow all the similarly titled posts in this forum, yet no solution seems to work, so I hope I can find some up-to-date suggestion here (most of the older posts refer to versions from 2008 to 2012...).
    I have installed Visual Studio 2013 (with the latest Update 2 RC) on a freshly installed development workstation with Win 8.1 with all its updates. Now I'd want to install SQL Server 2014 Express, but the setup keeps failing with the dreaded "Could
    not find the Database Engine startup handle" error (the log follows below).
    What I tried:
    1) download again and repair. Same error.
    2) completely uninstall by launching setup.exe /Action=uninstall (success), then rebooting the OS, then installing again. Same error. I did this twice, the second time I also manually removed any directory left out in C:\Program Files etc.
    When I launch the setup, I select all the components for installation in the package SQLEXPRADV_x64_ENU.exe (1.12 GB, last downloaded today -Apr 3, 2014-), and accept all the defaults including the proposed services accounts. There is no preexisting
    SQL Server instance, as expected.
    The setup takes its time, and finally fails with the error quoted above. I really do not want to reformat my HD and fully reconfigure my workstation, which took about 3 days... Could anyone suggest a solution to have SQL Server 2014 setup so I can start
    developing instead of wasting time in administering the system?
    Thanks to all! The log follows.
    Overall summary:
      Final result:                  Failed: see details below
      Exit code (Decimal):           -2061893607
      Start time:                    2014-04-03 18:30:58
      End time:                      2014-04-03 19:04:41
      Requested action:              Install
    Setup completed with required actions for features.
    Troubleshooting information for those features:
      Next step for RS:              Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Next step for SQLEngine:       Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Next step for FullText:        Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Next step for Replication:     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
    Machine Properties:
      Machine name:                  DIOMEDES
      Machine processor count:       4
      OS version:                    Windows 8
      OS service pack:               
      OS region:                     United States
      OS language:                   English (United States)
      OS architecture:               x64
      Process architecture:          64 Bit
      OS clustered:                  No
    Product features discovered:
      Product              Instance             Instance ID                    Feature                
                     Language             Edition              Version         Clustered  Configured
    Package properties:
      Description:                   Microsoft SQL Server 2014 
      ProductName:                   SQL Server 2014
      Type:                          RTM
      Version:                       12
      SPLevel:                       0
      Installation location:         C:\Users\Daniele\Downloads\SQLEXPRADV_x64_ENU\x64\setup\
      Installation edition:          Express
    Product Update Status:
      None discovered.
    User Input Settings:
      ACTION:                        Install
      ADDCURRENTUSERASSQLADMIN:      true
      AGTSVCACCOUNT:                 NT AUTHORITY\NETWORK SERVICE
      AGTSVCPASSWORD:                *****
      AGTSVCSTARTUPTYPE:             Disabled
      ASBACKUPDIR:                   Backup
      ASCOLLATION:                   Latin1_General_CI_AS
      ASCONFIGDIR:                   Config
      ASDATADIR:                     Data
      ASLOGDIR:                      Log
      ASPROVIDERMSOLAP:              1
      ASSERVERMODE:                  MULTIDIMENSIONAL
      ASSVCACCOUNT:                  <empty>
      ASSVCPASSWORD:                 <empty>
      ASSVCSTARTUPTYPE:              Automatic
      ASSYSADMINACCOUNTS:            <empty>
      ASTEMPDIR:                     Temp
      BROWSERSVCSTARTUPTYPE:         Disabled
      CLTCTLRNAME:                   <empty>
      CLTRESULTDIR:                  <empty>
      CLTSTARTUPTYPE:                0
      CLTSVCACCOUNT:                 <empty>
      CLTSVCPASSWORD:                <empty>
      CLTWORKINGDIR:                 <empty>
      COMMFABRICENCRYPTION:          0
      COMMFABRICNETWORKLEVEL:        0
      COMMFABRICPORT:                0
      CONFIGURATIONFILE:             
      CTLRSTARTUPTYPE:               0
      CTLRSVCACCOUNT:                <empty>
      CTLRSVCPASSWORD:               <empty>
      CTLRUSERS:                     <empty>
      ENABLERANU:                    true
      ENU:                           true
      ERRORREPORTING:                false
      FEATURES:                      SQLENGINE, REPLICATION, FULLTEXT, RS, CONN, BC, SDK, BOL, SSMS, ADV_SSMS, LOCALDB
      FILESTREAMLEVEL:               0
      FILESTREAMSHARENAME:           <empty>
      FTSVCACCOUNT:                  NT Service\MSSQLFDLauncher$SQLEXPRESS
      FTSVCPASSWORD:                 <empty>
      HELP:                          false
      IACCEPTSQLSERVERLICENSETERMS:  true
      INDICATEPROGRESS:              false
      INSTALLSHAREDDIR:              C:\Program Files\Microsoft SQL Server\
      INSTALLSHAREDWOWDIR:           C:\Program Files (x86)\Microsoft SQL Server\
      INSTALLSQLDATADIR:             <empty>
      INSTANCEDIR:                   C:\Program Files\Microsoft SQL Server\
      INSTANCEID:                    SQLEXPRESS
      INSTANCENAME:                  SQLEXPRESS
      ISSVCACCOUNT:                  NT AUTHORITY\Network Service
      ISSVCPASSWORD:                 <empty>
      ISSVCSTARTUPTYPE:              Automatic
      MATRIXCMBRICKCOMMPORT:         0
      MATRIXCMSERVERNAME:            <empty>
      MATRIXNAME:                    <empty>
      NPENABLED:                     0
      PID:                           *****
      QUIET:                         false
      QUIETSIMPLE:                   false
      ROLE:                          AllFeatures_WithDefaults
      RSINSTALLMODE:                 DefaultNativeMode
      RSSHPINSTALLMODE:              DefaultSharePointMode
      RSSVCACCOUNT:                  NT Service\ReportServer$SQLEXPRESS
      RSSVCPASSWORD:                 <empty>
      RSSVCSTARTUPTYPE:              Automatic
      SAPWD:                         <empty>
      SECURITYMODE:                  <empty>
      SQLBACKUPDIR:                  <empty>
      SQLCOLLATION:                  Latin1_General_CI_AS
      SQLSVCACCOUNT:                 NT Service\MSSQL$SQLEXPRESS
      SQLSVCPASSWORD:                *****
      SQLSVCSTARTUPTYPE:             Automatic
      SQLSYSADMINACCOUNTS:           DIOMEDES\Daniele
      SQLTEMPDBDIR:                  <empty>
      SQLTEMPDBLOGDIR:               <empty>
      SQLUSERDBDIR:                  <empty>
      SQLUSERDBLOGDIR:               <empty>
      SQMREPORTING:                  false
      TCPENABLED:                    0
      UIMODE:                        AutoAdvance
      UpdateEnabled:                 true
      UpdateSource:                  MU
      USEMICROSOFTUPDATE:            false
      X86:                           false
      Configuration file:            C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140403_183057\ConfigurationFile.ini
    Detailed results:
      Feature:                       Management Tools - Complete
      Status:                        Passed
      Feature:                       Client Tools Connectivity
      Status:                        Passed
      Feature:                       Client Tools SDK
      Status:                        Passed
      Feature:                       Client Tools Backwards Compatibility
      Status:                        Passed
      Feature:                       Management Tools - Basic
      Status:                        Passed
      Feature:                       Reporting Services - Native
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Component name:                SQL Server Database Engine Services Instance Features
      Component error code:          0x851A0019
      Error description:             Could not find the Database Engine startup handle.
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025
      Feature:                       Database Engine Services
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred during the setup process of the feature.
      Next Step:                     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Component name:                SQL Server Database Engine Services Instance Features
      Component error code:          0x851A0019
      Error description:             Could not find the Database Engine startup handle.
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025
      Feature:                       Full-Text and Semantic Extractions for Search
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Component name:                SQL Server Database Engine Services Instance Features
      Component error code:          0x851A0019
      Error description:             Could not find the Database Engine startup handle.
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025
      Feature:                       SQL Server Replication
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Component name:                SQL Server Database Engine Services Instance Features
      Component error code:          0x851A0019
      Error description:             Could not find the Database Engine startup handle.
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025
      Feature:                       SQL Browser
      Status:                        Passed
      Feature:                       Documentation Components
      Status:                        Passed
      Feature:                       SQL Writer
      Status:                        Passed
      Feature:                       LocalDB
      Status:                        Passed
      Feature:                       Setup Support Files
      Status:                        Passed
    Rules with failures:
    Global rules:
    Scenario specific rules:
    Rules report file:               C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140403_183057\SystemConfigurationCheck_Report.htm

    Thank you, it worked! I suppose that it was really your nr.3 which made the difference. I changed NT Service\MSSQL$SQLEXPRESS to NT AUTHORITY\System for the Data service. I'll then change it again as suggested (any suggestion about a "standard"
    account to be used here?), even if this is a development workstation using SQL Server Express only as a local database for debugging, so security is not really a big concern.
    Thanks for the feedback.Ya I know No3 was real step but just added more info so as to rule out any other possibility.
    No not as such, you wont believe,quite few pf my clients I have worked for keep it with local system and they have not complained yet ,they are afraid to change account as few of them faced issue SQL Server not coming online due to logon failure( after changing
    startup account to some domain a and that was happening due to some AD policy.But if you have nay plans to move Critical database in production which would be act as Database to some Internet facing application please follow my suggestion
    of running SQL Server with Least privileged domain account.
    Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

  • Issue when installing SQL Server Express 2012 - "The requested control is not valid for this service" + "Could not find the database engine startup handle"

    Good morning,
    I'm experiencing the following issue when installing Microsoft SQL Server Express 2012 (with tools, SQLEXPRWT_x86_ENU.exe) on the laptop of my company;
    Installation goes plain until around the end of the progress bar, it stops on the setup of
    SqlEngineDBStartConfigAction_install_configrc_Cpu32
    giving 7-8 times, even pressing "Cancel", the message "The requested control is not valid for this service";
    After this, I receive one last message ""Could not find the database engine startup handle", then installation ends with failures, in particular the Database Engine and the Server Replication failed to be installed.
    I've put in my SkyDrive the error log I received after the install;
    I'm at full disposal if you need further information,
    thank you in advance
    Best regards
    Francesco

    Well, i just ran into this issue and the problem was lack of admin rights. It was my company's laptop so got the setup initiated by my company's IT team with admin rights. However, the upon completion of setup, i go the same error messages as stated above: 
    SqlEngineDBStartConfigAction_install_configrc_Cpu32
    giving 7-8 times, even pressing "Cancel", the message "The requested control is not valid for this service";
    After this, I receive one last message ""Could not find the database engine startup handle", then installation ends with failures, in particular the Database Engine and the Server Replication failed to be installed.
    Also, if you open SQL Server Configuration, the status of the service is "Change Pending" and you would not be able to set the startup login type to Local Service/System/Network.
    Then, I just got my account added as Local Admin and then tried to start the service and was able to.
    However, I am not sure whether same was the case for you.
    Please mark the answer as helpful if i have answered your query. Thanks and Regards, Kartar Rana

  • Problem = always shut down when connect to the internet (both via wifi & mobile data)

    problem = always shut down when connect to the internet (both via wifi & mobile data) my problem is my phone (sony z1) regularly shut down automatically when connect to the internet (both via wifi & mobile data). it just happens after i downloaded and installed the latest available software (as following): Android version: Google Android 4.3 (Jelly Bean) Latest available software: 14.2.A.1.136 Release started: 2014-01-30 please suggest how to fix this problem.

    I suggest you disable any battery savers or task killers if you have.Boot your phone in safe mode and see how it is:
    http://talk.sonymobile.com/t5/FAQ/How-to-boot-your-phone-into-safe-mode/m-p/348008#U348008
    All we have to decide is what to do with the time that is given to us - J.R.R. Tolkien

  • TS3988 I have set up all the iCloud on my iPad and iPhone both are the latest version but they don't seem to sinc with each other does this take some time? I am connected to the Internet via wifi do I need to turn the mobile data to on on both maybe??

    I have set up all the iCloud on my iPad and iPhone both are the latest version but they don't seem to sinc with each other does this take some time? I am connected to the Internet via wifi do I need to turn the mobile data to on on both maybe??

    Welcome to the Apple Community.
    You need to turn the services you want to sync (calendars, contacts etc) on on both devices from settings > iCloud.

  • IPhone contacts: file transfer to Windows 7 via USB-cable  My iPhone can communicate with the computer only via USB-cable (no mobile data, no bluetooth, no internet, no outlook). As I want to get the phone to the "doctor" I want to save specifically

    iPhone contacts: file transfer to Windows 7 via USB-cable
    My iPhone can communicate with the computer only via USB-cable (no mobile data, no bluetooth, no internet, no outlook). As I want to get the phone to the "doctor" I want to save specifically my contact data and calendar details on the computer (OS: Windows 7). How can I solve this task? I will appreciate your valuable information, thanks.

    Using the iPhone, the USB cable, iTunes and Windows Contacts, sync the iPhone contacts to Windows Contacts. That will save them there. They are also included in the iPhone backup made in iTunes, and if you use iCloud.
    I'm sorry, I missed the calendar part the first time I looked. For calendar, you need a supported application on the computer (Outlook) or if you use iCloud, you can use the iCloud contacts and calendar app to sync.

  • What is the difference between Mobile Engine and MI?

    hi all,
    i want to know the difference between Mobile Engine and MI and also what are the main advantages included in MI instead of ME.

    Hi Anusha,
    ME had MicroITS as UI.
    MI has JSP and AWT as UI programming.
    From the above discussion its clear that JSP is the best option for programming.
    PS: AWT was depricated by SUNMicro.
    I just thought of sharing the history of MI.
    just to share to you a "history" of mobile projects in SAP.
    the current MI was actually a merged project from two mobile
    projects - the old Mobile Engine and the unheard Mobile
    Development Framework (MDF). when these projects were
    restructured, the ME was extended with some functionalities
    such as the SmartSync which was actually the replication
    technology used in MDF. MDF client was based on C++ and
    uses the CEDB as the database. it was not chosen to be
    the client due to its platform-dependency. MDF was already
    a working product when the restructuring happened. and there
    were some client functionalities like xml based GUI and
    metadata/logic definition that the current MI client doesn't
    have.
    Hope this is helpful.
    Close the thread if your done with your clarification.
    Cheers,
    Karthick

  • Establishing the Polling Function on Mobile Engine Server

    Dear all,
    we are setting up MDSD 4.0 as per the Direct Store Delivery "Configuration Guide" of 2009.
    At page 48, it describes the Connection of NetWeaver Mobile Server Component to the DSD Connector.
    Process Flow
    The following steps need to be performed to enable communication between the DSD
    Backend and the DSD Connector.
    1. Defining an RFC Destination on the NetWeaver Mobile Server [Seite 49].
    2. Establishing the Polling Function on Mobile Engine Server [Seite 50].
    While the first point is perfectly detailed at the page 49, the second point is omitted and at the page 50 it changes subject to Connection of DSD Administration Console to SAP WebAS and DSD Connector.
    Does anyone have the page that we are missing?
    Any ideas on how to setup the polling from MI to the DSD Connector?
    All the best,
    Andreu

    Dear all,
    just in casde someone is ever stuck there, we resolved this issue applying the SAP Note 1508174.
    All the best,
    Andreu

  • HT204053 I have changed my Apple ID in iTunes, which I access through my current ISP! I have another - old ISP on my mobile which I originally setup to access the App Store. I cannot access the App Store via old Apple ID. How do I change to new Apple ID?

    I had two (2) different ISP's, one for the mobile phone and one for the computer. I have changed my Apple ID in iTunes, and also changed my ISP provider for my mobile phone. NOW I cannot acces the App Store (through the iPhone icon. How can I change the Apple ID for access to the App Store which keeps requesting the 'old' Apple ID (lost the password and cannot get help as ISP is no longer available for help) Have tried syn, no rsult, I have the new Apple ID as Apple ID on my mobile phone. Help required here???

    To change the iCloud ID on your devices you have to go to Settings>iCloud, tap Delete Account, provide the password for the old ID when prompted (if using iOS 7), then sign back in with your current ID.
    If you don't know the password for your old ID, or if it isn't accepted, you will have to temporarily recreate it in order to delete the existing account.  To do this, go to https://appleid.apple.com, click Manage my Apple ID and sign in with your current iCloud ID.  Click edit next to the primary email account, change it back to your old email address and save the change.  Then edit the name of the account to change it back to your old email address.  You can now use your current password to turn off Find My iPhone on your device, even though it prompts you for the password for your old account ID. Then save any photo stream photos that you wish to keep to your camera roll.  When finished go to Settings>iCloud, tap Delete Account and choose Delete from My iDevice when prompted (your iCloud data will still be in iCloud).  Next, go back to https://appleid.apple.com and change your primary email address and iCloud ID name back to the way it was.  Now you can go to Settings>iCloud and sign in with your current iCloud ID and password.

  • Error While Running the Mobile Application.

    Hi friends,
    In SAP MI 7.1 I have Successfully done the following steps:-
    1. Created and build the service.
    2. Created and build the UI.
    3. Created and Build the application.
    as per the tutorial available in the link
    http://help.sap.com/saphelp_nwmobile71/helpdata/en/45/e5f99c6f472e98e10000000a155369/frameset.htm
    After deploying , When I am trying to run the mobile application . I am getting the below shown error.
    java.lang.IllegalStateException: com/sap/sdb/minDB/DriverEmbeddedMinDB (Unsupported major.minor version 48.0)
         at com.sap.tc.mobile.cfs.compat.Context.getPersistenceManager(Context.java:41)
         at com.sap.tc.mobile.cfs.compat.Context.getPersistenceManager(Context.java:28)
         at com.sap.tc.mobile.cfs.init.FrameworkInitializer.init(FrameworkInitializer.java:76)
         at java.lang.reflect.Method.invoke(Native Method)
         at com.sap.tc.mobile.cfs.startup.pda.Startup.main(Unknown Source)
    Error starting the framework
    java.lang.reflect.InvocationTargetException: java.lang.IllegalStateException: Cannot initialize framework
         at com.sap.tc.mobile.cfs.init.FrameworkInitializer.init(FrameworkInitializer.java:146)
         at java.lang.reflect.Method.invoke(Native Method)
         at com.sap.tc.mobile.cfs.startup.pda.Startup.main(Unknown Source)
    Also in the Netweaver prefrences /Mobile/handhelds/runtime settings/ when I click on launch simulator . It gives the same error.
    Please Suggest.
    Regards
    Nitesh.

    <br>Thanks a lot Alen . The reply was usefull. <br><br>
    Now after deploying when I am running the application in mobile handheld Simulator . It gives the below shown exception<br><br>
    2009-11-04 13:39:40 ...  (com.sap.tc.mobile.wdlite.renderer.exception.OCAExceptionLocalizeHelper:) Thread: main Error: <br>Resourcebundle sap.comtcmobilewdlitecontainer could not be found. Trying to use the default bundle.<br>
    2009-11-04 13:39:40 ...  (com.sap.tc.mobile.cfs.pers.PersistenceManager:release resultset) Thread: Finalizer Error: <br>java.sql.SQLException: Result set is closed<br>
    2009-11-04 13:39:40 ...  Thread: main Error: Internal Error. Please check the log file. --> <br>
    2009-11-04 13:39:40 ...  (com.sap.tc.mobile.wdlite.renderer.exception.OCAExceptionHandler:) Thread: main Error: Internal <br>Error. Please check the log file.<br>
    2009-11-04 13:39:40 ...  (com.sap.tc.mobile.wdlite.renderer.exception.OCAExceptionLocalizeHelper:) Thread: main Error: <br>Resourcebundle sap.comtcmobilewdlitecontainer could not be found. Trying to use the default bundle.<br>
    2009-11-04 13:39:40 ...  Thread: main Error: Internal Error. Please check the log file. --> <br>
    2009-11-04 13:39:40 ...  (com.sap.tc.mobile.wdlite.renderer.exception.OCAExceptionHandler:) Thread: main Error: Internal <br>Error. Please check the log file.<br>
    2009-11-04 13:39:40 ...  (com.sap.tc.mobile.wdlite.renderer.exception.OCAExceptionLocalizeHelper:) Thread: main Error: <br>Resourcebundle sap.comtcmobilewdlitecontainer could not be found. Trying to use the default bundle.
    java.lang.NullPointerException<br>
         at com.sap.tc.mobile.wdlite.progmodel.core.WDLite.launchApplication(WDLite.java:77)<br>
         at com.sap.tc.mobile.wdlite.progmodel.core.WDLite.launchApplication(WDLite.java:85)<br>
         at com.sap.tc.mobile.wdlite.container.AppMenuView.startApp(AppMenuView.java:561)<br>
         at com.sap.tc.mobile.wdlite.container.AppMenuView.onActionLaunchApp(AppMenuView.java:325)<br>
         at com.sap.tc.mobile.wdlite.container.AppMenuView.invokeEventHandler(AppMenuView.java:368)<br>
         at com.sap.tc.mobile.wdlite.progmodel.core.AbstractViewElement.doHandleEvent(AbstractViewElement.java:199)<br>
         at com.sap.tc.mobile.wdlite.renderer.api.UIElement.doHandleEvent(UIElement.java:353)<br>
         at com.sap.tc.mobile.wdlite.renderer.api.UIImageButton.mouseReleased(UIImageButton.java:152)<br>
         at com.sap.tc.mobile.wdlite.renderer.api.UIElement.dispatchMouseReleasedWidgetEvent(UIElement.java:396)<br>
         at com.sap.tc.mobile.wdlite.renderer.api.UIElement$1.mouseReleased(UIElement.java:439)<br>
         at com.sap.tc.mobile.wdlite.renderer.swt.MouseEventDispatcher.mouseUp(SWTControl.java:372)<br>
         at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:137)<br>
         at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)<br>
         at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928)<br>
         at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3348)<br>
         at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2968)<br>
         at com.sap.tc.mobile.wdlite.renderer.swt.container.WorkingArea.refresh(WorkingArea.java:129)<br>
         at com.sap.tc.mobile.wdlite.renderer.api.RenderingManager.refresh(RenderingManager.java:231)<br>
         at com.sap.tc.mobile.wdlite.progmodel.core.Application.refresh(Application.java:24)<br>
         at com.sap.tc.mobile.wdlite.progmodel.core.Application.navigate(Application.java:176)<br>
         at com.sap.tc.mobile.wdlite.progmodel.core.Application.enter(Application.java:19)<br>
         at com.sap.tc.mobile.wdlite.progmodel.core.WDLite.setCurrentApplication(WDLite.java:148)<br>
         at com.sap.tc.mobile.wdlite.progmodel.core.WDLite.launchApplication(WDLite.java:80)<br>
         at com.sap.tc.mobile.wdlite.framework.ApplicationLauncher.start(ApplicationLauncher.java:101)<br>
         at com.sap.tc.mobile.wdlite.framework.Start.runOnContext(Start.java:576)<br>
         at com.sap.tc.mobile.wdlite.framework.Start.startApplication(Start.java:600)<br>
         at com.sap.tc.mobile.wdlite.framework.Start.startContainer(Start.java:637)<br>
         at com.sap.tc.mobile.cfs.framework.spi.FrameworkManager.startContainer(FrameworkManager.java:261)<br>
         at com.sap.tc.mobile.cfs.init.FrameworkInitializer.init(FrameworkInitializer.java:139)<br>
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)<br>
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)<br>
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)<br>
         at java.lang.reflect.Method.invoke(Method.java:324)<br>
         at com.sap.tc.mobile.cfs.startup.pda.Startup.main(Unknown Source)<br>
    2009-11-04 13:39:40 ...  (com.sap.tc.mobile.wdlite.renderer.exception.OCAExceptionLocalizeHelper:) Thread: main Error: <br>Resourcebundle sap.comtcmobilewdlitecontainer could not be found. Trying to use the default bundle.<br>
    2009-11-04 13:39:40 ...  Thread: main Error: Application launch failed. --> <br>
    2009-11-04 13:39:40 ...  (com.sap.tc.mobile.wdlite.renderer.exception.OCAExceptionHandler:) Thread: main Error: Application <br>launch failed.<br>
    2009-11-04 13:39:40 ...  (com.sap.tc.mobile.wdlite.renderer.exception.OCAExceptionLocalizeHelper:) Thread: main Error: <br>Resourcebundle sap.comtcmobilewdlitecontainer could not be found. Trying to use the default bundle.<br>
    java.lang.ClassCastException<br>
         at com.sap.demo.order_sv.service.impl.OrderService.generateTestData(OrderService.java:52)<br>
         at com.sap.orderapp.comp.OrderComp.generateTestData(OrderComp.java:175)<br>
         at com.sap.orderapp.comp.OrderComp.wdDoInit(OrderComp.java:73)<br>
         at com.sap.tc.mobile.wdlite.progmodel.core.Controller.enter(Controller.java:21)<br>
         at com.sap.tc.mobile.wdlite.progmodel.core.Component.enter(Component.java:24)<br>
         at com.sap.tc.mobile.wdlite.progmodel.core.Application.setCurrentComponent(Application.java:125)<br>
         at com.sap.tc.mobile.wdlite.progmodel.core.Application.navigate(Application.java:155)<br>
         at com.sap.tc.mobile.wdlite.progmodel.core.Application.enter(Application.java:19)<br>
         at com.sap.tc.mobile.wdlite.progmodel.core.WDLite.setCurrentApplication(WDLite.java:148)<br>
         at com.sap.tc.mobile.wdlite.progmodel.core.WDLite.launchApplication(WDLite.java:80)<br>
         at com.sap.tc.mobile.wdlite.container.AppMenuView.startApp(AppMenuView.java:561)<br>
         at com.sap.tc.mobile.wdlite.container.AppMenuView.onActionLaunchApp(AppMenuView.java:325)<br>
         at com.sap.tc.mobile.wdlite.container.AppMenuView.invokeEventHandler(AppMenuView.java:368)<br>
         at com.sap.tc.mobile.wdlite.progmodel.core.AbstractViewElement.doHandleEvent(AbstractViewElement.java:199)<br>
         at com.sap.tc.mobile.wdlite.renderer.api.UIElement.doHandleEvent(UIElement.java:353)<br>
         at com.sap.tc.mobile.wdlite.renderer.api.UIImageButton.mouseReleased(UIImageButton.java:152)<br>
         at com.sap.tc.mobile.wdlite.renderer.api.UIElement.dispatchMouseReleasedWidgetEvent(UIElement.java:396)<br>
         at com.sap.tc.mobile.wdlite.renderer.api.UIElement$1.mouseReleased(UIElement.java:439)<br>
         at com.sap.tc.mobile.wdlite.renderer.swt.MouseEventDispatcher.mouseUp(SWTControl.java:372)<br>
         at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:137)<br>
         at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)<br>
         at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928)<br>
         at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3348)<br>
         at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2968)<br>
         at com.sap.tc.mobile.wdlite.renderer.swt.container.WorkingArea.refresh(WorkingArea.java:129)<br>
         at com.sap.tc.mobile.wdlite.renderer.api.RenderingManager.refresh(RenderingManager.java:231)<br>
         at com.sap.tc.mobile.wdlite.progmodel.core.Application.refresh(Application.java:24)<br>
         at com.sap.tc.mobile.wdlite.progmodel.core.Application.navigate(Application.java:176)<br>
         at com.sap.tc.mobile.wdlite.progmodel.core.Application.enter(Application.java:19)<br>
         at com.sap.tc.mobile.wdlite.progmodel.core.WDLite.setCurrentApplication(WDLite.java:148)<br>
         at com.sap.tc.mobile.wdlite.progmodel.core.WDLite.launchApplication(WDLite.java:80)<br>
         at com.sap.tc.mobile.wdlite.framework.ApplicationLauncher.start(ApplicationLauncher.java:101)<br>
         at com.sap.tc.mobile.wdlite.framework.Start.runOnContext(Start.java:576)<br>
         at com.sap.tc.mobile.wdlite.framework.Start.startApplication(Start.java:600)<br>
         at com.sap.tc.mobile.wdlite.framework.Start.startContainer(Start.java:637)<br>
         at com.sap.tc.mobile.cfs.framework.spi.FrameworkManager.startContainer(FrameworkManager.java:261)<br>
         at com.sap.tc.mobile.cfs.init.FrameworkInitializer.init(FrameworkInitializer.java:139)<br>
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)<br>
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)<br>
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)<br>
         at java.lang.reflect.Method.invoke(Method.java:324)<br>
         at com.sap.tc.mobile.cfs.startup.pda.Startup.main(Unknown Source)<br>
    Please Suggest<br>
    <br>
    <br>
    It will be a great help.<br>
    Regards
    Nitesh.
    Edited by: Nitesh Harit on Nov 4, 2009 2:22 PM

  • Connecting to the mobile device

    Hi ,
    We have installed the MAM 2.5 Application successfully on the system.
    The Application is working fine now.
    We have to use the mobile device now we are planning to connect it to the
    system and then perform the sync.
    Are we supposed to install mobile Engine again on the device and install the
    application or in the first sync we get the application the device.
    Can you let me the procedure how to get the application on the device.
    Thanks,
    Aswini

    Hi Aswini,
    You will need the following three CAB files to Install SAP MI Client on your PDA.
    1.Creme cab file
    ->CrEme327a_AX_CE50_PPC_minimal.CAB file if u are using the Mobile 5 Device.
    ->CrEme327a_AX_CE42_PPC_minimal.CAB if u are using the Mobile 2003 device.
    You can download the creme from NSICOM site.
    http://www.nsicom.com/Default.aspx?tabid=159
    2.Jsse file.
    3.MI Client cab file.
    ->MI25Tom_en.CAB..file.(You can download the same from service.sap.com)
    First you should connect your PDA with PC via USB/Active sync.
    Then Copy these files in temp folder of your device.Then Click on cab files in following sequence creme->jsse->MI Client cab file.to install the SAP MI Client on to your device.Once the SAP MI Client is installed on your PDA.You can download the MAM Application in the sameway as on desktop PC.
    Hope this helps.
    Thanks
    Regards
    Devendra

Maybe you are looking for

  • I cant make a bootable (usb/dvd) for windows 8.1 pro 64 bit

    right now i am using windows 8.1 pro 32 bit ,, want to change to 64 bit   , my CPU is 64 bit  and i have 4 GB ram (i know i should have more ram ,, but i dont do this upgrade for the ram  , but because some emulators , and some application ask 64 bit

  • BPM Composer auditing

    Hi all, Does anyone know if its possible to track/audit the BPM Composer, administrative actions of a "Project Administrator" ? For example... I added one user (Bob) to BPMComposerAdmin application role using FMW control. The user=Bob launches BPM co

  • G5 having trouble booting, don't always get a 'chime' noise

    Trouble getting my G5 1.6ghz w/10.4.x to boot/start. Seems to be intermittent as far as hearing startup chime. Any suggestion? The first few tries to start the G5 it would make no chime, nothing on the screen. Just some quiet whirring inside I was un

  • PWM signal from Accelerometer by using DIO of PIC-MIO-16E-4

    I am a new beginner to use digital signal acqusition. The accelrometer send the pulse width modualated signal and I need to use DIO line instead of counter. I wonder how I can measure the pulse width, + duty, and -duty.

  • Setting up one IMAC in a windows environment

    I am a systems administrator in a small company that operates in a 100% windows environment. We have no one on staff with any support knowledge when it comes to apple. I have one individual ( a graphic designer) that has requested a Imac. The reason;