Error during unattended install of SQL 2012 (..setting 'CLTRESULTDIR' does not exist.)

Hi ALl,
I'm trying an automated install of SQL 2012 on WIndows 2012, but I keep running into this error (using a configuration.ini file generated by running through setup and grabbing it just before I clicked 'OK')
Contents of summary log:
Overall summary:
   Final result:                  Failed: see details below
   Exit code (Decimal):           -2068578304
   Exit facility code:            1204
   Exit error code:               0
   Exit message:                  The specified directory 'C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir' for setting 'CLTRESULTDIR' does not
exist.
   Start time:                    2015-01-09 10:19:12
   End time:                      2015-01-09 10:20:07
   Requested action:              Install
Setup completed with required actions for features.
 Troubleshooting information for those features:
   Next step for SQLEngine:       SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for Replication:     SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for FullText:        SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for DQ:              SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for AS:              SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for RS:              SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for RS_SHP:          SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for RS_SHPWFE:       SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for DQC:             SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for IS:              SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for Conn:            SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for Adv_SSMS:        SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for SDK:             SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for BC:              SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for DREPLAY_CTLR:    SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for DREPLAY_CLT:     SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for BIDS:            SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for SSMS:            SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for SNAC:            SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for SNAC_SDK:        SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for Writer:          SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for BOL:             SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for Browser:         SQL Server Setup was canceled before completing the operation. Try the setup process again.
 Machine Properties:
   Machine name:                  IDCSQLTST11
   Machine processor count:       2
   OS version:                    Future Windows Version
   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
Package properties:
   Description:                   Microsoft SQL Server 2012
   ProductName:                   SQL Server 2012
   Type:                          RTM
   Version:                       11
   SPLevel:                       0
   Installation location:         E:\SQL_Server_2012_StandardEdition\x64\setup\
   Installation edition:          Standard
Product Update Status:
   None discovered.
User Input Settings:
   ACTION:                        Install
   ADDCURRENTUSERASSQLADMIN:      false
   AGTSVCACCOUNT:                 NT Service\SQLSERVERAGENT
   AGTSVCPASSWORD:                <empty>
   AGTSVCSTARTUPTYPE:             Automatic
   ASBACKUPDIR:                   C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Backup
   ASCOLLATION:                   Latin1_General_CI_AS
   ASCONFIGDIR:                   C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Config
   ASDATADIR:                     C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Data
   ASLOGDIR:                      C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Log
   ASPROVIDERMSOLAP:              1
   ASSERVERMODE:                  MULTIDIMENSIONAL
   ASSVCACCOUNT:                  NT Service\MSSQLServerOLAPService
   ASSVCPASSWORD:                 <empty>
   ASSVCSTARTUPTYPE:              Manual
   ASSYSADMINACCOUNTS:            DOMAINAA\SQLADMINS
   ASTEMPDIR:                     C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Temp
   BROWSERSVCSTARTUPTYPE:         Disabled
   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:             E:\SQL_Server_2012_StandardEdition\ConfigurationFile.ini
   CTLRSTARTUPTYPE:               Manual
   CTLRSVCACCOUNT:                NT Service\SQL Server Distributed Replay Controller
   CTLRSVCPASSWORD:               <empty>
   CTLRUSERS:                     DOMAINAA\user12345
   ENABLERANU:                    false
   ENU:                           true
   ERRORREPORTING:                false
   FEATURES:                      SQLENGINE, REPLICATION, FULLTEXT, DQ, AS, RS, RS_SHP, RS_SHPWFE, DQC, BIDS, CONN, IS, BC, SDK, BOL, SSMS, ADV_SSMS,
DREPLAY_CTLR, DREPLAY_CLT, SNAC_SDK
   FILESTREAMLEVEL:               0
   FILESTREAMSHARENAME:           <empty>
   FTSVCACCOUNT:                  NT Service\MSSQLFDLauncher
   FTSVCPASSWORD:                 <empty>
   HELP:                          false
   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\MsDtsServer110
   ISSVCPASSWORD:                 <empty>
   ISSVCSTARTUPTYPE:              Automatic
   MATRIXCMBRICKCOMMPORT:         0
   MATRIXCMSERVERNAME:            <empty>
   MATRIXNAME:                    <empty>
   NPENABLED:                     0
   PID:                           *****
   QUIET:                         true
   QUIETSIMPLE:                   false
   ROLE:                         
   RSINSTALLMODE:                 DefaultNativeMode
   RSSHPINSTALLMODE:              SharePointFilesOnlyMode
   RSSVCACCOUNT:                  NT Service\ReportServer
   RSSVCPASSWORD:                 <empty>
   RSSVCSTARTUPTYPE:              Manual
   SAPWD:                         <empty>
   SECURITYMODE:                  SQL
   SQLBACKUPDIR:                  <empty>
   SQLCOLLATION:                  Latin1_General_CI_AS
   SQLSVCACCOUNT:                 NT Service\MSSQLSERVER
   SQLSVCPASSWORD:                <empty>
   SQLSVCSTARTUPTYPE:             Automatic
   SQLSYSADMINACCOUNTS:           DOMAINAA\SQLADMINS
   SQLTEMPDBDIR:                  F:\TempDB
   SQLTEMPDBLOGDIR:               <empty>
   SQLUSERDBDIR:                  E:\SQLData
   SQLUSERDBLOGDIR:               D:\SQLLog
   SQMREPORTING:                  false
   TCPENABLED:                    1
   UIMODE:                        Normal
   UpdateEnabled:                 true
   UpdateSource:                  MU
   X86:                           false
  Configuration file:            C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20150109_101753\ConfigurationFile.ini
Detailed results:
   Feature:                       Database Engine Services
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
  Feature:                       SQL Server Replication
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
  Feature:                       Full-Text and Semantic Extractions for Search
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
  Feature:                       Data Quality Services
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
  Feature:                       Analysis Services
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
  Feature:                       Reporting Services - Native
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
  Feature:                       Reporting Services - SharePoint
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
  Feature:                       Reporting Services Add-in for SharePoint Products
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
  Feature:                       Data Quality Client
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
  Feature:                       Integration Services
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
  Feature:                       Client Tools Connectivity
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
  Feature:                       Management Tools - Complete
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
  Feature:                       Client Tools SDK
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
  Feature:                       Client Tools Backwards Compatibility
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
  Feature:                       Distributed Replay Controller
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
  Feature:                       Distributed Replay Client
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
  Feature:                       SQL Server Data Tools
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
  Feature:                       Management Tools - Basic
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
  Feature:                       SQL Client Connectivity
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
  Feature:                       SQL Client Connectivity SDK
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
  Feature:                       SQL Writer
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
  Feature:                       Documentation Components
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
  Feature:                       SQL Browser
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file:               C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20150109_101753\SystemConfigurationCheck_Report.htm
Exception summary:
 The following is an exception stack listing the exceptions in outermost to innermost order
 Inner exceptions are being indented
Exception type: Microsoft.SqlServer.Chainer.Infrastructure.InputSettingValidationException
     Message:
         The specified directory 'C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir' for setting 'CLTRESULTDIR' does not exist.
     HResult : 0x84b40000
         FacilityCode : 1204 (4b4)
         ErrorCode : 0 (0000)
     Data:
       SQL.Setup.FailureCategory = InputSettingValidationFailure
       DisableWatson = true
     Stack:
         at Microsoft.SqlServer.Chainer.Infrastructure.InputSettingService.LogAllValidationErrorsAndThrowFirstOne(ValidationState vs)
         at Microsoft.SqlServer.Configuration.SetupExtension.ValidateFeatureSettingsAction.ExecuteAction(String actionId)
         at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
         at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun, ServiceContainer context)
     Inner exception type: Microsoft.SqlServer.Configuration.DistributedReplayExtension.DirectoryNotExistException
         Message:
                 The specified directory 'C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir' for setting 'CLTRESULTDIR' does not exist.
         HResult : 0x87d00006
                 FacilityCode : 2000 (7d0)
                 ErrorCode : 6 (0006)
         Data:
           DirectoryPath = C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir
           SettingName = CLTRESULTDIR
           WatsonData = 
Microsoft.SqlServer.Configuration.DistributedReplayExtension.DirectoryNotExistException@6

Hello,
Open the configuration file with notepad, then go to the “features” variable. On the following article you will find what
means each parameter:
http://msdn.microsoft.com/en-us/library/ms144259(v=sql.110).aspx#Feature
You will also find the list of features supported by each edition on the following article:
http://msdn.microsoft.com/en-us/library/Cc645993(v=sql.110).aspx
For example, it seems you have DQ and DQC on that configuration file, please remove them with their corresponding commas.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com
Thanks Albert that worked when I just selected the main features and excluded ones like DQ and DRC. Thing is why would the standard media allow you to install enterprise features, create a configuration file with these enterprise features and then fail?? Why
would Microsoft tease you like that? Frustrating since I spent hours on this ..

Similar Messages

  • UD - Selected set code does not exist

    Dear All,
    We have create material in 0001 plant. It is consumable material and QA is not required. But by mistake Inspection flag was activited in material master.
    Now material received is in QA Stock. We have created inspection plan and not inspection lot is in REL status.
    During UD system shows following message :
    "Selected set code does not exist, or data entered is incomplete"
    Is there any way to take stock in unrestricted without doing any QA activity ?
    Thanks and Regards,
    Nirav

    Hi,
    Why don't you simply complete the Stock posting using 'Inspection lot stock' tab in QA32?
    If you only need to take the stock out of QI and doesn't need Usage decision then why do bother about it.
    Besides, this error comes when the UD selected set defined in Configuration is not maintained for the Plant.
    To check this, Follow this path,
    QCC0> Quality inspection> Maintain inspection type. Select the Relative inspection type and see what is maintained.
    Once you maintain this Selected set for the plant 0001 using QS51, you won't get this error. Other way, define that selected set in the configuration which is already maintained for the plant.
    ntn

  • Error while deploy mapping ora-06550 table or view does not exist

    Hi everyone,
    i have a target source 'U_BCK' that cointains some Oracle table.
    I have also created a target schema 'BCK_OWNER' where i create some dimensions and cubes with mappings.
    My mappings connect some table from U_BCK with dimension or cube from BCK_OWNER.
    My repository owner is called 'rep_owner' and i used this user to create every metadata.
    Now i'm trying to deploy, and i don't have any problem until deploying mappings. When i try to deploy mappings i get some errors like ora-06550,ora-00942 table or view does not exist and statement ignored.
    Please help me and sorry for my english...
    Thanks,
    Alex.

    The mapping, that drives the data from one table to another is deployed to the database as a PL/SQL package. When deploying your mapping fails, it most often means that the resulting PL/SQL package doesn't compile in the database.
    Using Oracle SQL Developer (or Toad, SQL Navigator or any other tool) connect to the schema on the database where you have deployed the mapping. Open the pl/sql package and compile it. That should show you the place where the compilation fails, and give you an idea as to what table it can not find. Otherwise, in SQLPLUS, you can simply give the following command:
    ALTER PACKAGE THE_PACKAGE_NAME_GOES_HERE compile body;
    show errors;
    As the database user who owns the source tables, make sure to issue a GRANT command for each of the source tables, granting SELECT access to the database user who owns the mapping:
    grant select on TABLENAME to TARGETSCHEMA.
    hope this helps
    Borkur

  • Error trying to recreate OEM dbconsole in 11GR2 - aux_stats$ does not exist

    I created a blank 11GR2 database, then created tablespaces, users etc. and imported schema's from 9i export. So far so good.
    Now I can't connect to the OEM dbconsole, all arrows are green, instance up, listener up etc. but says it cant connect.
    Ok, recreate dbsonsole , first drop sysman, dbsmp cascade etc, then run emca -deconfig dbcontrol db -repos drop - seemed to go ok
    then run emca -config db -repos create - it asks for passwords etc, all ok so far, then craps out, I look in the logfile and see this:
    GRANT SELECT, INSERT, UPDATE, DELETE ON AUX_STATS$ TO SYSMAN
    ERROR at line 1:
    ORA-00942: table or view does not exist
    So now what? Why would it try to grant access to a table or view that does not exist? Did I miss something here?
    thanks

    This will give you the complete picture of Grid Certification.
    Oracle Enterprise Manager 10g Grid Control Certification Checker
    https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=412431.1
    Is there a workaround or a version that will install on 2008 x64?Well, no OMS has been certified with this version as of now. You can have 10.2.0.3/4 OMS on 2008(32 Bit)
    10.2.0.4 Agent is certified with 2008 64 bit.

  • Web-dynpro application -ERROR: ICF service node "/sap/bc/webdynpro/sap/zqm_cto_arr_general1" does not exist (see SAP Note 1109215) (termination: ERROR_MESSAGE_STATE)

    i have created my web-dynpro application in development. and sent to quality . whenever i will execute my dynpro in quality  i got one message
    ERROR: ICF service node "/sap/bc/webdynpro/sap/zqm_cto_arr_general1" does not exist (see SAP Note 1109215) (termination: ERROR_MESSAGE_STATE)
    whenever i saw  sicf  transaction my web-dynpro is not seen . my dynpro application name is more then 15 character. what i will do . please give me valuable suggestion.....

    Hi Ashok,
                   for your requirement the application is not exist in particular place. It means, the webdynpro application is saved at different package or different location.
                  Please change the webdynpro component name and save it in particular request in package, then transport it to quality ..(development server )
    then go to SICF  t.code .. sap->bc->webdynpro->sap->find  out your application and activate the service of your webdynpro application.
    Now test it ... this solution might helpful to you .
    Regards,
    Naveen M

  • ORA-02289 (10: 10): PL/SQL: ORA-02289: sequence does not exist

    Hi,
    I want to run a trigger on SCOTT account.But wheni try to run it.I am getting ' ORA-02289 (10: 10): PL/SQL: ORA-02289: sequence does not exist'.PLease help out

    Sequence FUNCTION_SEQ does not exist...
    Pease run
    Select * from user_objects
    where object_type='SEQUENCE'
    and object_name='FUNCTION_SEQ'In order to see that this object doesnt exist on your schema...
    Maybe you are trying to use sequence in different schema... Check it out too
    Select * from all_objects
    where object_type='SEQUENCE'
    and object_name='FUNCTION_SEQ'And if you has access to DBA_ views check this too...
    Select * from dba_objects
    where object_type='SEQUENCE'
    and object_name='FUNCTION_SEQ'If you need such sequence please give us an example of values you need and will provide a sequence creation script for you..

  • Error: For object RF_BELEG 9000, number range interval 92 does not exist FB

    Hi,
    When I am executing AFAB in test run mode for a particular company code I am getting below mentioned error:
    +For object RF_BELEG 9000, number range interval 92 does not exist FBN1+
        +Message no. NR751+
    +Diagnosis+
        +The database table NRIV has the delivery class 'C', i.e. the SAP default+
        +settings are only in client 000.+
    +Procedure+
        +Create the missing number range interval in customizing.+
        +Transaction code: FBN1+
    When I maintain number range 92 this error goes away. My question is we have no where assigned this number range 92 to any of the Document type then why system is asking to maintain the same?
    Sanjay

    Hi,
    You might be using the number range (say 92 which you've created in GL view & not in ENTRY view).
    Steps:
    Go to Define Document Number Ranges for Entry View OR use T-code FBN1.   Maintain & Assign two Number Ranges say 91 & 92 one for Document Type AF and another for AE for both the non-leading Ledgers say Y1 & Y2 ( Define Document Type for Entry VIew in a ledger). Also assign a number range to
    Document type SX (Closing Posting) apart from the above two Number Ranges (91 & 92)
    Hopefully it works for You............
    Dipti

  • Install SAP ERP 6.0 - Domain does not exist. Create user failed.

    Hi experts,
    I have encounter a problem while installing the the SAP ERP 6.0 by IDES Installation Master.
    I got no idea about whats wrong here. Please help me out.
    Thanks.
    Warning: Unable to get the name of the domain.
    INFO[E] 2009-08-07 14:28:46.439
    FSL-01027  Account user="PHOENIX\SAPServiceEC6" does not exist.
    WARNING 2009-08-07 14:28:46.439
    Unable to get the name of a domain controller for domain .
    WARNING[E] 2009-08-07 14:28:46.455
    FSL-01002  Unable to create account PHOENIX\SAPServiceEC6. HRESULT=0x80005009
    WARNING[E] 2009-08-07 14:28:46.455
    MUT-03025  Caught ESyException in Modulecall: ESAPinstException: error text undefined.
    ERROR 2009-08-07 14:28:46.455
    FCO-00011  The step createAccounts with step key |NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_Users_Create_Do|ind|ind|ind|ind|5|0|createAccounts was executed with status ERROR .
    Kind Regards,
    George.

    > I choosed typical setting, the system didnt prompt me to choose anything regarding about domain.
    Ok - then the system chooses a domain installation - which is the default.
    I suggest you stop the installation, run the uninstaller, boot the machine and start over using "Custom" if you want to do a local installation.
    Markus

  • How do i remove my old Apple Id from iPhone's iCloud setting which does not exist anymore

    Purchased new iphone 5s, installed with itunes restoring backup from iphone 4 (which was too old a backup). It restored an old apple id (which i do not use anymore) in the iCloud settings while having my new Apple Id in the Itunes & App Store. I cannot turn off the iCloud setting due to old AppleId popping up - which does not exist.. How do i remove the old Apple Id from icloud setting on the phone.
    I cannot erase the phone as it asks for the password for the old Apple Id. And i cannot do the restore again (after i made a recent back up my iphone 4) as itunes asks me to turn off Find my phone.

    The Apple ID exists. The email address you used to create it may not, but the Apple ID does. Call AppleCare and ask to speak to someone in account security.

  • Error while deploying map: ORA-00942 Table or view does not exist

    Hi OWB experts,
    I'm having yet another problem with OWB, this time when I try to deploy a mapping I get this error:
    ORA-06550: line 59, column 3:
    PL/SQL: ORA-00942: table or view does not exist
    DIM_01_ESTCON_MAP
    ORA-06550: line 93, column 3:
    PL/SQL: SQL Statement ignored
    If I open the package that OWB created I see the errors:
    CURSOR "DEDUP_SRC_0_IN2_c" IS
    SELECT
    "DEDUP_INPUT_SUBQUERY2$1"."ESTADOCONEXION_ID" "ESTADOCONEXION_ID",
    "DEDUP_INPUT_SUBQUERY2$1"."ESTADOCONEXION_COD_ESTCON" "ESTADOCONEXION_COD_ESTCON",
    "DEDUP_INPUT_SUBQUERY2$1"."ESTADOCONEXION_DESC_ESTCON" "ESTADOCONEXION_DESC_ESTCON",
    "DEDUP_INPUT_SUBQUERY2$1"."STANDARD_TOTAL_COD_TTL" "STANDARD_TOTAL_COD_TTL"
    FROM
    (SELECT
    DISTINCT
    "DIM_01_ESTCON_MAP"."GET_CONST_CA_0_ESTADOCO" "ESTADOCONEXION_ID",
    "ESTADOS"."ESTADO" "ESTADOCONEXION_COD_ESTCON",
    "ESTADOS"."DESC_EST" "ESTADOCONEXION_DESC_ESTCON",
    "DIM_01_ESTCON_MAP"."GET_TOTAL_C_0_TTLID" "STANDARD_TOTAL_COD_TTL"
    FROM
    "CONSULTA"."ESTADOS"@"PROD@AYADEV_LOCATION" "ESTADOS"
    WHERE
    ( estado LIKE 'EC%' )) "DEDUP_INPUT_SUBQUERY2$1";
    Where AYADEV_LOCATION points to the module/schema/location where my source data is.
    Now, I have defined three modules:
    SOURCE, where I defined the tables and other objects from the original database (source data)
    STAGE, where I am performing all the transformations; here I defined all the maps
    TARGET, this holds the dimensions and fact tables.
    Now all three modules point to different databases. The dblink for AYADEV_LOCATION has been created and shouldn't present any problems. The username that I'm using to log on to the source database is current and I can connect to it through SQL+ or any other program (TOAD, SQLDeveloper).
    What could be happening here? I'm using OWB 10g R2, with Oracle DB 10g R2.
    I'd really appreciate any help you could provide.
    Best Regards,
    --Osvaldo
    [osantos]

    Hi,
    I'm still having problems but I found out why these tables are returning errors. The username I've been given by the DBA to connect to the database is CONSULTA, but this user is only for querying purposes, the actual objects reside on a differente schema, of course, which is PROD. So the line:
    "CONSULTA"."ESTADOS"@"PROD@AYADEV_LOCATION" "ESTADOS"
    raises an exception because the table ESTADOS is not located on that schema, but on PROD. If I query the table from SQL Plus with:
    SELECT *
    FROM [email protected]@AYADEV_LOCATION
    then there's no problem at all.
    Why is this? How do I instruct OWB to point to the correct schema or to avoind fully qualifying the table name?
    Please help me, I'm kind of confused here.
    Best Regards,
    --oswaldo.
    [osantos]

  • Error While Generating Form-16 (HR_INF16_2012_B in language EN does not exist)

    Dear Experts
    My client is using SAP ECC6 EHP4 and We recently updated the HR Service Pack to SAPK-60464INSAPHRCIN in order to apply the SAP Note 1829618 - PY-IN: Union Budget Changes for Year 2013.
    After upgrading Service Pack we are getting the below error while generating Form-16.
    Layout set HR_INF16_2012_B in language EN does not exist
    How to resolve this issue
    Thanks

    This a Blunder from SAP. And this issue we are getting in almost all the client.
    For this we have to download respective Form from Golder client 000 and upload again in our working client.
    Better please raise an OSS message with SAP to provide you the steps.
    Thanks & Regards
    Rupesh Jain

  • Error in SE16n - PIR exsist only in EINE table & does not exist in EINA tab

    Hello All,
    This is regarding error in Pucrahsing Info Record in which PIR only exist in EINE table & not in EINA table. This is not normal behavior of SAP standard.
    In this issue we are able to see P. Info Record (5300083719) details in EINE table only.
    But the same PIR does not exist in EINA table .
    Also we can not see this in display mode(ME13) & system does not allow us to change PIR. System gives the error message that PIR does not exist.
    This is something strange. Can you pls. reply on this.
    Thanks in advance.
    Mahesh
    9869633910

    Hello,
    The PIR No is availabe in EINE (pur org data) and the same PIR is not availabe in EINA table( General data ).
    This is Program error. bcz some times system will not get the correct PIR no while creating the PO, in that time system will create new PIR , that no is from buffer table..
    And you cannot track that buffer table....... If you want to check the  on that day,, how many PO's were created for that same combination of material and vendor.
    Regards
    Mahesh Naik.

  • Error while creating folder: Path is invalid because folder does not exist

    Hi,
    I am having an issue while creating Folders in ID, when I create folder Structure like EDI -> VENDOR -> DELL I am getting the error as below:
    Path /EDI/VENDOR/DELL/ is invalid because folder VENDOR does not exist
    So first 2 levels of folder structure is fine and when I create third level (DELL) I get the above error. Any idea how to resolve this or is this the limitation?
    We have
    Service Pack:06
    Release:NW711_06_REL
    Thanks,
    Laxman

    Hi Laxman,
    Kindly try to refresh the SLD cache by going to Environment -> Clear SLD Data Cache. Make sure that the Cache Status are all in green.
    Hope this would help.
    Regards,
    Jenny

  • Error 'The application id or shortname (-1) you entered does not exist.'

    Hello,
    When I run the OA page it opens without any errors,but I delegate to Other page for insert record it showing following Error
    , Please help me to resolve this error.
    oracle.apps.fnd.framework.OAException: The application id or shortname (-1) you entered does not exist.
         at oracle.apps.fnd.framework.webui.OAPageErrorHandler.prepareException(Unknown Source)
         at oracle.apps.fnd.framework.webui.OAPageBean.renderDocument(Unknown Source)
         at oracle.apps.fnd.framework.webui.OAPageBean.renderDocument(Unknown Source)
         at OA.jspService(_OA.java:87)
         at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:59)
         at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:462)
         at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:594)
         at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:518)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
         at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:713)
         at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:370)
         at com.evermind.server.http.ServletRequestDispatcher.unprivileged_forward(ServletRequestDispatcher.java:259)
         at com.evermind.server.http.ServletRequestDispatcher.access$100(ServletRequestDispatcher.java:51)
         at com.evermind.server.http.ServletRequestDispatcher$2.oc4jRun(ServletRequestDispatcher.java:193)
         at oracle.oc4j.security.OC4JSecurity.doPrivileged(OC4JSecurity.java:283)
         at com.evermind.server.http.ServletRequestDispatcher.forward(ServletRequestDispatcher.java:198)
         at com.evermind.server.http.EvermindPageContext.forward(EvermindPageContext.java:392)
         at OA.jspService(_OA.java:80)
         at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:59)
         at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:462)
         at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:594)
         at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:518)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
         at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:713)
         at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:370)
         at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:871)
         at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:453)
         at com.evermind.server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:221)
         at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:122)
         at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:111)
         at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
         at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
         at java.lang.Thread.run(Thread.java:595)
    Regards,
    Kapil

    Helllo Friends,
    Issue get resolved. On page, there was one field with Item Style 'MessageLOVInput' and I had not given a source for 'External LOV' to that field.
    Thanks,
    Kapil

  • Error in EA13 (Single Reversal of Print Documents) : 'TE508 does not exists

    HI All,
    When reversing an individual invoice in EA13, an error comes up in the log. Though the invoice has been successfully reversed.
    The following error is displayed 'TE508 does not exist'
    Any reasons
    Regards,
    Rahul

    The following error is displayed 'TE508 does not exist'
    Check the settings in spro
    contract billing>Billing master data>activate display mode for Billing key date.
    try to do with reverse selection.
    Regds,
    Narendar Konakanchi

Maybe you are looking for

  • Black Friday TV Deals

    So I'm thinking of upgrading to a bigger size TV.  Wanted opinions on the deals for Black Friday.  I was looking at the SHARP 60" LED 1080P 120hz for $999.99.  But I'm kinda dissapointed that SEARS has same set right now for same price.  There are al

  • Folio showing in Content Viewer, but not when published in Custom Content Viewer... please help...!

    I shared a folio to review it in the Content Viewer and everything looks ok, but when published (public / free) custom viewer (v24) doesn't show it. What could be the problem? Thanks, and excuse my english...

  • Not able to capitalize asset

    Dear all, My user is not able to capitalize an asset and getting the error AW605. Through my understanding I got to understand that I need to clear the down payments first.  So I asked the user to use T code AB01 and clear the down payment. The user

  • HT1338 During the iPhoto slideshow of an event, photo appears blank/black. When I check the photos it is there.

    During an iPhoto slideshow of an event one or more photos appear as blank/black. When I check the photos they are there. Why is iPhoto not showing these photos?

  • Order Operation Table

    Hi, We are creating Function Module for one client requirement, where we need to make some changes in Order operation tab, on the basis of the existing operations. So please tell me, From where (Database Table) these operations in operation tab of or