Statistical Setup failure - Purchasing application

We upgraded our R/3 Plug-In from 2002.1 to PI 2004.1. To test the setup and init process,we ran the statistical setup run for 02 application. The setup program is successful but the documents are not posted into the MC02....SETUP tables. Checked the NPRT transaction to check the log entries, it displays that 252,000 documents are selected. Checked the extraction using RSA3 as well, it returns 0 records. Are there any specific entries that needs to be checked or entered for PI 2004.1 upgrade with reference to Purchasing application? or should I check any table lock stuff with reference to MC02...SETUP tables?

MS,
sorry for being so insistent, but for an analysis it is really important to check, if the statistical setup run actually created any data in the setup table.
If there are no records in the setup table, then the RSA3 can not show any records.
Best regards,
Bernd Sieger

Similar Messages

  • How to fill setup table for Application 18 Customer services

    Hi,
    How can I fill setup table for application 18.
    Regards,
    ST

    Hi,
    To fill LIS, first set your LIS to update. use the central Tcode OMO1(for SD), OMO2(for MM) or OMO3(for other logistics) or you can set it in MC24 also(activate button).
    SBIW -> settings for application specific datasources -> Logistics -> managing transfer information structures ->.... -> statistical setup Sales. (Application component 17 >transaction OLIIBW,Application component 18> OLISBW )-->select the relevent one whether sales/billings/deliveries etc in the pop-up. enter your LIS, give a name to job and execute.
    Also pls chk this;
    Re: query on setup table filling
    Regards
    CSM Reddy

  • Rmceneua - statistical setup of info structures from purchasing documents

    Hi all,
    I run the program rmceneua for a specific purchasing document number. The line on this PO has been selected for deletion. LOEKZ = 'L'. When S011 and S012 are populated, will this line be taken into consideration when calculating the effective order value, etc.
    I am new to SAP, so any help will be welcome.
    Thank you in advance,
    Rivaaj

    hi,
    the statistical setup will setup all PO-related extractors (2LIS_02_*) - so you only need one setup. =)
    at this point all you need to do is to replicate the datasource in your BW system, create and activate (or transport) transfer rules, assign update rules for this infosource in whichever infoproviders, create an infopackage, and load away. =)
    ryan.

  • Statistical setup info sturctures frm purchasing documents

    Hi all,
    Im stuck with a problem LO data extraction
    I customized Lo cockpit LBWE 2lis_02_scl and extract structure MC02M_0SCL
    while doing restructured the tables and to fill again setup tables Im getting an error "time of termination lies in past" what could be the reason can any one help me out pls..
    thanx ,
    aak

    hi,
    the statistical setup will setup all PO-related extractors (2LIS_02_*) - so you only need one setup. =)
    at this point all you need to do is to replicate the datasource in your BW system, create and activate (or transport) transfer rules, assign update rules for this infosource in whichever infoproviders, create an infopackage, and load away. =)
    ryan.

  • Statistical Setup (OLI3BW tcode)

    Hi all,
        Can anyone please explain me what the below fields mean and what should I select to do a Statistical setup ie to do a full update.
    Control of Recompilation run
    1.  Name of Run(New Run)
    2.  Termination date, Termination time
    3.  block all documents
    4.  Extraction structres BW
    Document data restriction
    1.  Archiving Session
    2.  Purchase Org
    3.  Purchase document
    4.  Document date
    I am trying to extract data from datasource 2lis_02_hdr using lo-cockpit and I have followed the below steps
    1.  LBWE transaction - inactivate update, deleted setup tables in application component 02(MM) and also deleted any delta queue in /nrso2
    2.  Maintain extract structure and datasource
    3.  Activated the update(Is this necessary to do before replicating the datasources ?)
    4.  Replicated the datasource in BW
    5.  Assigned infosource and created a infopackage to load the data to PSA.
    6.  Set up statistical update(tcode OLI3BW).  I am not sure if I have to do this before step 5.  I am struck here and unable to understand the fields to do a statistical update
    Please help me.
    Thanks,
    Sabrina.

    Hi Sabrina,
    1. Name of the run - You can put in any name here. It does not matter. You can call it 'RUN1' or 'TEST1' whatever. It is just for you to differentiate between different runs.
    2. Termination Date and Time - When it is filling up the setup tables, it might go on for a long time. So you can put in a time beyond which if the set up runs, the system must teminate it. Normally if you know that if it runs for more than 2 hours there is something wrong, you specify a time 2 hours from the current time as the 'safety upper limit'.
    3. Block all documents - If you set this, all the records are blocked in the database from changes during the setup run.
    4. Not sure...
    You can break up your setup run in parts broken down by date ranges or document numbers etc. For eg. set up for all records with dates from Jan to March, do full upload into BW, delete setup tables, run setup again for March to May etc. For this you have the rest of the selections.

  • Statistical Setup Tables

    What are the steps to delete and fill up the Statistical setup table for a 2LIS extractor? Thanks

    Hi Harpal.
    In R/3 you have to make the following steps.
    1) Transaction SBIW.
    2) "Business Information Warehouse" --> "Settings for Application-Specific DataSouerces" --> "Logistics" --> "Managing Extract Structure" --> "Inizialization".
    3) "Delete the Contents of the Setup Table" --> then select the Application related to the extrator 2LIS that you are interested in.
    4) "Filling in the Setup Tables" --> "Application-Specific Setup of Statistical Data" --> then select the Application related to the extrator 2LIS that you are interested in.
    You can check the right Application via transaction LBWE where you can see all the extractors with the related Application.
    PAY ATTENTION that the delete and fill of the SetUp Tables is for Application and not for extractor, as you can see in LBWE for Purchasing (02) where you can see that the three extractor 2LIS_02_HDR - 2LIS_02_ITM - 2LIS_02_SCL are all related to 02 Application.
    Ciao.
    Riccardo

  • Running Statistical Setup in producition

    Dear experts,,
    IS that mandatory when ever i run statistical setup need to lock the users or no need, can i go ahead deleted and and running setuptable in production
    Regards
    Radha

    Hi Radha,
      Consider the application '02' - It is for purchasing.
    If there is no delta pointer in rsa7 for all the purchasing datasources. There is no need to lock the user while filling set-up table.
    If delta pointer is there for datasources - data duplication will occur,
    Any modification in transactions -> R/3 Base table> LBWQ(Extraction Queue)--> RSA7 (Delta Queue).
    Set up table is a cluster table that is used to extract data from R/3 tables of same application.
    If I start filling set-up table, records from relevant R/3 tables will be updated to set-up table. During that time, If I made any change in any document - the same records will be updated in set-up table as well as in delta queue. Then there is data duplication.
    Edited by: Priya.D on Apr 13, 2010 1:39 PM

  • SQL Server Setup Failure 0x84B10001 (SQL 2012 SP2 and SQL 2014 Standard)

    I'm having a problem with SQL Server Setup. I had SQL Server 2012 R2 SP1 installed, and the SP2 installer would fail.
    I decided to just get SQL Server 2014. The setup (and system configuration checker) for that fails with the same error.
    SQL Server Setup failure
    SQL Server Setup has encountered the following error:
    '.', hexadecimal value 0x00, is an invalid character. Line 1, position 231747.
    Error code 0x84B10001
    I found this and other posts about similar problems that point at MSDE being the cause.
    http://social.msdn.microsoft.com/Forums/sqlserver/en-US/bc9f4949-1b45-427c-aa2b-d2222488a13e/problems-installing-sql-server-2012error-code-0x84b10001?forum=sqlexpress
    I definitely had MSDE installed, but I went through the steps to manually remove it and rebooted with no luck.
    /* Don Reynolds */

    (01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.SqlBrowserExtension.sqlBrowserStopServicePrivateConfig.xml'
    (01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.SqlBrowserExtension.sqlBrowserStopServicePrivateConfig.xml' validated with schema 'Microsoft.SqlServer.Configuration.SqlBrowserExtension.sqlBrowserStopServicePrivateConfig.xsd' loaded
    into datastore path '/Datastore/ProductSettings/SqlBrowserStopService/Private'
    (01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.SetupExtension.SkuPublicConfigObject.xsd'
    (01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.SetupExtension.SkuPublicConfigObjectDefault.xml'
    (01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.SetupExtension.SkuPublicConfigObjectDefault.xml' validated with schema 'Microsoft.SqlServer.Configuration.SetupExtension.SkuPublicConfigObject.xsd' loaded into datastore path '/Datastore/ProductSettings/Sku/Public'
    (01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.SetupExtension.SkuPrivateConfigObject.xsd'
    (01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.SetupExtension.SkuPrivateConfigObjectDefault.xml'
    (01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.SetupExtension.SkuPrivateConfigObjectDefault.xml' validated with schema 'Microsoft.SqlServer.Configuration.SetupExtension.SkuPrivateConfigObject.xsd' loaded into datastore path '/Datastore/ProductSettings/Sku/Private'
    (01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.Repl_ConfigExtension.ReplPrivateSettings.xsd'
    (01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.Repl_ConfigExtension.ReplPrivateDefaultSettings.xml'
    (01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.Repl_ConfigExtension.ReplPrivateDefaultSettings.xml' validated with schema 'Microsoft.SqlServer.Configuration.Repl_ConfigExtension.ReplPrivateSettings.xsd' loaded into datastore path
    '/Datastore/ProductSettings/Repl/Private'
    (01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.RSSHPExtension.SqlRSSHPConfigPublicDefaultSettings.xsd'
    (01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.RSSHPExtension.SqlRSSHPConfigPublicDefaultSettings.xml'
    (01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.RSSHPExtension.SqlRSSHPConfigPublicDefaultSettings.xml' validated with schema 'Microsoft.SqlServer.Configuration.RSSHPExtension.SqlRSSHPConfigPublicDefaultSettings.xsd' loaded into datastore
    path '/Datastore/ProductSettings/SqlRSSHP/Public'
    (01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.RSSHPExtension.SqlRSSHPConfigPrivateDefaultSettings.xsd'
    (01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.RSSHPExtension.SqlRSSHPConfigPrivateDefaultSettings.xml'
    (01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.RSSHPExtension.SqlRSSHPConfigPrivateDefaultSettings.xml' validated with schema 'Microsoft.SqlServer.Configuration.RSSHPExtension.SqlRSSHPConfigPrivateDefaultSettings.xsd' loaded into
    datastore path '/Datastore/ProductSettings/SqlRSSHP/Private'
    (01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.RSExtension.SqlRSConfigPublicDefaultSettings.xsd'
    (01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.RSExtension.SqlRSConfigPublicDefaultSettings.xml'
    (01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.RSExtension.SqlRSConfigPublicDefaultSettings.xml' validated with schema 'Microsoft.SqlServer.Configuration.RSExtension.SqlRSConfigPublicDefaultSettings.xsd' loaded into datastore path
    '/Datastore/ProductSettings/SqlRS/Public'
    (01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.RSExtension.SqlRSConfigPrivateDefaultSettings.xsd'
    (01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.RSExtension.SqlRSConfigPrivateDefaultSettings.xml'
    (01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.RSExtension.SqlRSConfigPrivateDefaultSettings.xml' validated with schema 'Microsoft.SqlServer.Configuration.RSExtension.SqlRSConfigPrivateDefaultSettings.xsd' loaded into datastore path
    '/Datastore/ProductSettings/SqlRS/Private'
    (01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.RSExtension.SqlRSDBConfigPrivateDefaultSettings.xsd'
    (01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.RSExtension.SqlRSDBConfigPrivateDefaultSettings.xml'
    (01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.RSExtension.SqlRSDBConfigPrivateDefaultSettings.xml' validated with schema 'Microsoft.SqlServer.Configuration.RSExtension.SqlRSDBConfigPrivateDefaultSettings.xsd' loaded into datastore
    path '/Datastore/ProductSettings/SqlRS/DBPrivate'
    (01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.ManagementToolsExtension.ManagementToolsPublicSettings.xsd'
    (01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.ManagementToolsExtension.ManagementToolsPublicDefaultSettings.xml'
    (01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.ManagementToolsExtension.ManagementToolsPublicDefaultSettings.xml' validated with schema 'Microsoft.SqlServer.Configuration.ManagementToolsExtension.ManagementToolsPublicSettings.xsd'
    loaded into datastore path '/Datastore/ProductSettings/ManagementTools/Public'
    (01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.ManagementToolsExtension.ManagementToolsPrivateSettings.xsd'
    (01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.ManagementToolsExtension.ManagementToolsPrivateDefaultSettings.xml'
    (01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.ManagementToolsExtension.ManagementToolsPrivateDefaultSettings.xml' validated with schema 'Microsoft.SqlServer.Configuration.ManagementToolsExtension.ManagementToolsPrivateSettings.xsd'
    loaded into datastore path '/Datastore/ProductSettings/ManagementTools/Private'
    (01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.ManagementToolsExtension.ManagementToolsAdvancedPublicSettings.xsd'
    (01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.ManagementToolsExtension.ManagementToolsAdvancedPublicDefaultSettings.xml'
    (01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.ManagementToolsExtension.ManagementToolsAdvancedPublicDefaultSettings.xml' validated with schema 'Microsoft.SqlServer.Configuration.ManagementToolsExtension.ManagementToolsAdvancedPublicSettings.xsd'
    loaded into datastore path '/Datastore/ProductSettings/ManagementToolsAdvanced/Public'
    (01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.ManagementToolsExtension.ManagementToolsAdvancedPrivateSettings.xsd'
    (01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.ManagementToolsExtension.ManagementToolsAdvancedPrivateDefaultSettings.xml'
    (01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.ManagementToolsExtension.ManagementToolsAdvancedPrivateDefaultSettings.xml' validated with schema 'Microsoft.SqlServer.Configuration.ManagementToolsExtension.ManagementToolsAdvancedPrivateSettings.xsd'
    loaded into datastore path '/Datastore/ProductSettings/ManagementToolsAdvanced/Private'
    (01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.DistributedReplayExtension.ControllerPrivateSettings.xsd'
    (01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.DistributedReplayExtension.ControllerPrivateDefaultSettings.xml'
    (01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.DistributedReplayExtension.ControllerPrivateDefaultSettings.xml' validated with schema 'Microsoft.SqlServer.Configuration.DistributedReplayExtension.ControllerPrivateSettings.xsd' loaded
    into datastore path '/Datastore/ProductSettings/DReplayController/Private'
    (01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.DistributedReplayExtension.ClientPrivateSettings.xsd'
    (01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.DistributedReplayExtension.ClientPrivateDefaultSettings.xml'
    (01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.DistributedReplayExtension.ClientPrivateDefaultSettings.xml' validated with schema 'Microsoft.SqlServer.Configuration.DistributedReplayExtension.ClientPrivateSettings.xsd' loaded into
    datastore path '/Datastore/ProductSettings/DReplayClient/Private'
    (01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.Cluster.ClusterDiskPrivateConfig.xsd'
    (01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.Cluster.ClusterDiskPrivateConfig.xml'
    (01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.Cluster.ClusterDiskPrivateConfig.xml' validated with schema 'Microsoft.SqlServer.Configuration.Cluster.ClusterDiskPrivateConfig.xsd' loaded into datastore path '/Datastore/ProductSettings/ClusterDisk/Private'
    (01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.Cluster.ClusterDiskPublicConfig.xsd'
    (01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.Cluster.ClusterDiskPublicConfig.xml'
    (01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.Cluster.ClusterDiskPublicConfig.xml' validated with schema 'Microsoft.SqlServer.Configuration.Cluster.ClusterDiskPublicConfig.xsd' loaded into datastore path '/Datastore/ProductSettings/ClusterDisk/Public'
    (01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.Cluster.ClusterGroupPrivateConfig.xsd'
    (01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.Cluster.ClusterGroupPrivateConfig.xml'
    (01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.Cluster.ClusterGroupPrivateConfig.xml' validated with schema 'Microsoft.SqlServer.Configuration.Cluster.ClusterGroupPrivateConfig.xsd' loaded into datastore path '/Datastore/ProductSettings/ClusterGroup/Private'
    (01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.Cluster.ClusterGroupPublicConfig.xsd'
    (01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.Cluster.ClusterGroupPublicConfig.xml'
    (01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.Cluster.ClusterGroupPublicConfig.xml' validated with schema 'Microsoft.SqlServer.Configuration.Cluster.ClusterGroupPublicConfig.xsd' loaded into datastore path '/Datastore/ProductSettings/ClusterGroup/Public'
    (01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.Cluster.ClusterIPAddressPrivateConfig.xsd'
    (01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.Cluster.ClusterIPAddressPrivateConfig.xml'
    (01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.Cluster.ClusterIPAddressPrivateConfig.xml' validated with schema 'Microsoft.SqlServer.Configuration.Cluster.ClusterIPAddressPrivateConfig.xsd' loaded into datastore path '/Datastore/ProductSettings/ClusterIPAddresses/Private'
    (01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.Cluster.ClusterIPAddressPublicConfig.xsd'
    (01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.Cluster.ClusterIPAddressPublicConfig.xml'
    (01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.Cluster.ClusterIPAddressPublicConfig.xml' validated with schema 'Microsoft.SqlServer.Configuration.Cluster.ClusterIPAddressPublicConfig.xsd' loaded into datastore path '/Datastore/ProductSettings/ClusterIPAddresses/Public'
    (01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.Cluster.FailoverInstanceNamePrivateConfig.xsd'
    (01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.Cluster.FailoverInstanceNamePrivateConfig.xml'
    (01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.Cluster.FailoverInstanceNamePrivateConfig.xml' validated with schema 'Microsoft.SqlServer.Configuration.Cluster.FailoverInstanceNamePrivateConfig.xsd' loaded into datastore path '/Datastore/ProductSettings/FailOverClusterName/Private'
    (01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.Cluster.FailoverInstanceNamePublicConfig.xsd'
    (01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.Cluster.FailoverInstanceNamePublicConfig.xml'
    (01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.Cluster.FailoverInstanceNamePublicConfig.xml' validated with schema 'Microsoft.SqlServer.Configuration.Cluster.FailoverInstanceNamePublicConfig.xsd' loaded into datastore path '/Datastore/ProductSettings/FailoverClusterName/Public'
    (01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.Cluster.ClusterNodePrivateConfig.xsd'
    (01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.Cluster.ClusterNodePrivateConfig.xml'
    (01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.Cluster.ClusterNodePrivateConfig.xml' validated with schema 'Microsoft.SqlServer.Configuration.Cluster.ClusterNodePrivateConfig.xsd' loaded into datastore path '/Datastore/ProductSettings/ClusterNode/Private'
    (01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.Cluster.ClusterNodePublicConfig.xsd'
    (01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.Cluster.ClusterNodePublicConfig.xml'
    (01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.Cluster.ClusterNodePublicConfig.xml' validated with schema 'Microsoft.SqlServer.Configuration.Cluster.ClusterNodePublicConfig.xsd' loaded into datastore path '/Datastore/ProductSettings/ClusterNode/Public'
    (01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.SlpExtension.SQLServerSCPPrivateSettings.xsd'
    (01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.SlpExtension.SQLServerSCPPrivateSettings.xml'
    (01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.SlpExtension.SQLServerSCPPrivateSettings.xml' validated with schema 'Microsoft.SqlServer.Configuration.SlpExtension.SQLServerSCPPrivateSettings.xsd' loaded into datastore path '/Datastore/ProductSettings/SQLServerSCP/Private'
    (01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.Cluster.ClusterNodesStatusPublicConfig.xml'
    (01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.Cluster.ClusterNodesStatusPublicConfig.xml' loaded into datastore path '/Datastore/ProductSettings/ClusterNodesStatus/Public'
    (01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.ASExtension.ASSPIInputSettings.xsd'
    (01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.ASExtension.ASSPIInputSettingsDefaults.xml'
    (01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.ASExtension.ASSPIInputSettingsDefaults.xml' validated with schema 'Microsoft.SqlServer.Configuration.ASExtension.ASSPIInputSettings.xsd' loaded into datastore path '/Datastore/ProductSettings/ASSIP/Public'
    (01) 2014-07-02 10:52:57 Slp: Completed Action: LoadPackageDatastoreObjects, returned True
    (01) 2014-07-02 10:52:57 Slp: ----------------------------------------------------------------------
    (01) 2014-07-02 10:52:57 Slp: Running Action: InitializeInputSettingStore
    (01) 2014-07-02 10:52:57 Slp: Completed Action: InitializeInputSettingStore, returned True
    (01) 2014-07-02 10:52:57 Slp: ----------------------------------------------------------------------
    (01) 2014-07-02 10:52:57 Slp: Running Action: InitializeRoleService
    (01) 2014-07-02 10:52:57 Slp: Loading role: SPI_AS_NewFarm
    (01) 2014-07-02 10:52:58 Slp: Loading role: SPI_AS_ExistingFarm
    (01) 2014-07-02 10:52:58 Slp: Loading role: AllFeatures_WithDefaults
    (01) 2014-07-02 10:52:58 Slp: Completed Action: InitializeRoleService, returned True
    (01) 2014-07-02 10:52:58 Slp: ----------------------------------------------------------------------
    (01) 2014-07-02 10:52:58 Slp: Running Action: ProcessChainerCommandLineArguments
    (01) 2014-07-02 10:52:58 Slp: ----------------------------------------
    (01) 2014-07-02 10:52:58 Slp: Setting: WORKFLOW
    (01) 2014-07-02 10:52:58 Slp: Value specified: RUNRULES
    (01) 2014-07-02 10:52:58 Slp: New setting source: CommandLine; previous setting source: NotSpecified
    (01) 2014-07-02 10:52:58 Slp: ----------------------------------------
    (01) 2014-07-02 10:52:58 Slp: Setting: TIMESTAMP
    (01) 2014-07-02 10:52:58 Slp: Value specified: 20140702_105236
    (01) 2014-07-02 10:52:58 Slp: New setting source: CommandLine; previous setting source: Default
    (01) 2014-07-02 10:52:58 Slp: ----------------------------------------
    (01) 2014-07-02 10:52:58 Slp: Setting: LOGMARKER
    (01) 2014-07-02 10:52:58 Slp: Value specified:
    (01) 2014-07-02 10:52:58 Slp: New setting source: CommandLine; previous setting source: Default
    (01) 2014-07-02 10:52:58 Slp: ----------------------------------------
    (01) 2014-07-02 10:52:58 Slp: Setting: MEDIASOURCE
    (01) 2014-07-02 10:52:58 Slp: Value specified: R:\
    (01) 2014-07-02 10:52:58 Slp: New setting source: CommandLine; previous setting source: NotSpecified
    (01) 2014-07-02 10:52:58 Slp: ----------------------------------------
    (01) 2014-07-02 10:52:58 Slp: Setting: INSTALLMEDIAPATH
    (01) 2014-07-02 10:52:58 Slp: Value specified: R:\x64\setup\
    (01) 2014-07-02 10:52:58 Slp: New setting source: CommandLine; previous setting source: NotSpecified
    (01) 2014-07-02 10:52:58 Slp: ----------------------------------------
    (01) 2014-07-02 10:52:58 Slp: Setting: ENU
    (01) 2014-07-02 10:52:58 Slp: Value specified: True
    (01) 2014-07-02 10:52:58 Slp: New setting source: CommandLine; previous setting source: Default
    (01) 2014-07-02 10:52:58 Slp: ----------------------------------------
    (01) 2014-07-02 10:52:58 Slp: Setting: MEDIALAYOUT
    (01) 2014-07-02 10:52:58 Slp: Value specified: Full
    (01) 2014-07-02 10:52:58 Slp: New setting source: CommandLine; previous setting source: Default
    (01) 2014-07-02 10:52:58 Slp: ----------------------------------------
    (01) 2014-07-02 10:52:58 Slp: Setting: ACTION
    (01) 2014-07-02 10:52:58 Slp: Value specified: RUNRULES
    (01) 2014-07-02 10:52:58 Slp: New setting source: CommandLine; previous setting source: NotSpecified
    (01) 2014-07-02 10:52:58 Slp: ----------------------------------------
    (01) 2014-07-02 10:52:58 Slp: Setting: RULES
    (01) 2014-07-02 10:52:58 Slp: Value specified: SCCCheckRules
    (01) 2014-07-02 10:52:58 Slp: New setting source: CommandLine; previous setting source: Default
    (01) 2014-07-02 10:52:58 Slp: ----------------------------------------
    (01) 2014-07-02 10:52:58 Slp: Completed Action: ProcessChainerCommandLineArguments, returned True
    (01) 2014-07-02 10:52:58 Slp: ----------------------------------------------------------------------
    (01) 2014-07-02 10:52:58 Slp: Running Action: ProcessMediaChainerConfigFileArguments
    (01) 2014-07-02 10:52:58 Slp: Procssing media configuration file R:\x64\setup\..\DefaultSetup.ini.
    (01) 2014-07-02 10:52:58 Slp: ----------------------------------------
    (01) 2014-07-02 10:52:58 Slp: Setting: PID
    (01) 2014-07-02 10:52:58 Slp: New setting source: ConfigFile; previous setting source: NotSpecified
    (01) 2014-07-02 10:52:58 Slp: ----------------------------------------
    (01) 2014-07-02 10:52:58 Slp: Completed Action: ProcessMediaChainerConfigFileArguments, returned True
    (01) 2014-07-02 10:52:58 Slp: ----------------------------------------------------------------------
    (01) 2014-07-02 10:52:58 Slp: Running Action: ProcessChainerConfigFileArguments
    (01) 2014-07-02 10:52:58 Slp: Completed Action: ProcessChainerConfigFileArguments, returned True
    (01) 2014-07-02 10:52:58 Slp: ----------------------------------------------------------------------
    (01) 2014-07-02 10:52:58 Slp: Running Action: ProcessSlipstreamParameters
    (01) 2014-07-02 10:52:58 Slp: Completed Action: ProcessSlipstreamParameters, returned True
    (01) 2014-07-02 10:52:58 Slp: ----------------------------------------------------------------------
    (01) 2014-07-02 10:52:58 Slp: Skipping Action: SetRoleAndUIModeForExpressMedia
    (01) 2014-07-02 10:52:58 Slp: Action is being skipped due to the following restrictions:
    (01) 2014-07-02 10:52:58 Slp: Condition "IsMediaExpress" did not pass as it returned false and true was expected.
    (01) 2014-07-02 10:52:58 Slp: ----------------------------------------------------------------------
    (01) 2014-07-02 10:52:58 Slp: Running Action: InitializeRetryHandler
    (01) 2014-07-02 10:52:58 Slp: Completed Action: InitializeRetryHandler, returned True
    (01) 2014-07-02 10:52:58 Slp: ----------------------------------------------------------------------
    (01) 2014-07-02 10:52:58 Slp: Running Action: ExecuteBootstrapProcessInputSettings
    (01) 2014-07-02 10:52:58 Slp: Workflow to execute: 'BOOTSTRAPPROCESSINPUTSETTINGS'
    (01) 2014-07-02 10:52:58 Slp: ----------------------------------------------------------------------
    (01) 2014-07-02 10:52:58 Slp: Running Action: StartSqmSession
    (01) 2014-07-02 10:52:58 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
    (01) 2014-07-02 10:52:58 Slp: Sco: Attempting to open registry subkey Software\Microsoft\Microsoft SQL Server\120
    (01) 2014-07-02 10:52:58 Slp: Sco: Attempting to get registry value CustomerFeedback
    (01) 2014-07-02 10:52:58 Slp: SQM Service: Sqm does not have active session.
    (01) 2014-07-02 10:52:58 Slp: SQM is opted-out by command line parameter /SQMREPORTING or registry key setting, SQM session is closed
    (01) 2014-07-02 10:52:58 Slp: Completed Action: StartSqmSession, returned True
    (01) 2014-07-02 10:52:58 Slp: ----------------------------------------------------------------------
    (01) 2014-07-02 10:52:58 Slp: Running Action: ValidateChainerSetting
    (01) 2014-07-02 10:52:58 Slp: -- PidInfoProvider : NormalizePid is normalizing input pid
    (01) 2014-07-02 10:52:58 Slp: -- PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid
    (01) 2014-07-02 10:52:58 Slp: -- PidInfoProvider : Compute new PID
    (01) 2014-07-02 10:52:58 Slp: -- PidInfoProvider : Read lcid 1033 from CultureInfo
    (01) 2014-07-02 10:52:58 Slp: -- PidInfoProvider : NormalizePid is normalizing input pid
    (01) 2014-07-02 10:52:58 Slp: -- PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid
    (01) 2014-07-02 10:52:58 Slp: -- PidInfoProvider : Use cached PID
    (01) 2014-07-02 10:52:58 Slp: -- PidInfoProvider : NormalizePid is normalizing input pid
    (01) 2014-07-02 10:52:58 Slp: -- PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid
    (01) 2014-07-02 10:52:58 Slp: -- PidInfoProvider : Use cached PID
    (01) 2014-07-02 10:52:58 Slp: -- PidInfoProvider : NormalizePid is normalizing input pid
    (01) 2014-07-02 10:52:58 Slp: -- PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid
    (01) 2014-07-02 10:52:58 Slp: -- PidInfoProvider : Use cached PID
    (01) 2014-07-02 10:52:58 Slp: -- PidInfoProvider : NormalizePid is normalizing input pid
    (01) 2014-07-02 10:52:58 Slp: -- PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid
    (01) 2014-07-02 10:52:58 Slp: -- PidInfoProvider : Use cached PID
    (01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : NormalizePid is normalizing input pid
    (01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid
    (01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : Use cached PID
    (01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : NormalizePid is normalizing input pid
    (01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid
    (01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : Use cached PID
    (01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : NormalizePid is normalizing input pid
    (01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid
    (01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : Use cached PID
    (01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : NormalizePid is normalizing input pid
    (01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid
    (01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : Use cached PID
    (01) 2014-07-02 10:52:59 Slp: Completed Action: ValidateChainerSetting, returned True
    (01) 2014-07-02 10:52:59 Slp: ----------------------------------------------------------------------
    (01) 2014-07-02 10:52:59 Slp: Running Action: ProcessFeatureCommandLineArguments
    (01) 2014-07-02 10:52:59 Slp: ----------------------------------------
    (01) 2014-07-02 10:52:59 Slp: Completed Action: ProcessFeatureCommandLineArguments, returned True
    (01) 2014-07-02 10:52:59 Slp: ----------------------------------------------------------------------
    (01) 2014-07-02 10:52:59 Slp: Running Action: ProcessMediaFeatureConfigFileArguments
    (01) 2014-07-02 10:52:59 Slp: Procssing media configuration file R:\x64\setup\..\DefaultSetup.ini.
    (01) 2014-07-02 10:52:59 Slp: ----------------------------------------
    (01) 2014-07-02 10:52:59 Slp: Completed Action: ProcessMediaFeatureConfigFileArguments, returned True
    (01) 2014-07-02 10:52:59 Slp: ----------------------------------------------------------------------
    (01) 2014-07-02 10:52:59 Slp: Running Action: ProcessFeatureConfigFileArguments
    (01) 2014-07-02 10:52:59 Slp: Completed Action: ProcessFeatureConfigFileArguments, returned True
    (01) 2014-07-02 10:52:59 Slp: ----------------------------------------------------------------------
    (01) 2014-07-02 10:52:59 Slp: Running Action: ValidateSettingsAgainstScenario
    (01) 2014-07-02 10:52:59 Slp: Scenario: RunRules
    (01) 2014-07-02 10:52:59 Slp: Completed Action: ValidateSettingsAgainstScenario, returned True
    (01) 2014-07-02 10:52:59 Slp: ----------------------------------------------------------------------
    (01) 2014-07-02 10:52:59 Slp: Running Action: FinalCalculateSettings
    (01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : NormalizePid is normalizing input pid
    (01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid
    (01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : Use cached PID
    (01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : NormalizePid is normalizing input pid
    (01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid
    (01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : Use cached PID
    (01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : NormalizePid is normalizing input pid
    (01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid
    (01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : Use cached PID
    (01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : NormalizePid is normalizing input pid
    (01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid
    (01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : Use cached PID
    (01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : NormalizePid is normalizing input pid
    (01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid
    (01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : Use cached PID
    (01) 2014-07-02 10:52:59 Slp: Completed Action: FinalCalculateSettings, returned True
    (01) 2014-07-02 10:52:59 Slp: Completed Action: ExecuteBootstrapProcessInputSettings, returned True
    (01) 2014-07-02 10:52:59 Slp: Completed Action: ExecuteBootstrapAfterExtensionsLoaded, returned True
    (01) 2014-07-02 10:52:59 Slp: ----------------------------------------------------------------------
    (01) 2014-07-02 10:52:59 Slp: Running Action: RunRemoteDiscoveryAction
    (01) 2014-07-02 10:52:59 Slp: Running discovery on local machine
    (01) 2014-07-02 10:53:03 Slp: Error: Action "Microsoft.SqlServer.Configuration.SetupExtension.RunDiscoveryAction" threw an exception during execution.
    (01) 2014-07-02 10:53:03 Slp: Microsoft.SqlServer.Setup.Chainer.Workflow.ActionExecutionException: '.', hexadecimal value 0x00, is an invalid character. Line 1, position 231747. ---> Microsoft.SqlServer.Chainer.Infrastructure.ChainerInfrastructureException:
    '.', hexadecimal value 0x00, is an invalid character. Line 1, position 231747. ---> System.Xml.XmlException: '.', hexadecimal value 0x00, is an invalid character. Line 1, position 231747.
    (01) 2014-07-02 10:53:03 Slp:    at System.Xml.XmlTextReaderImpl.Throw(Exception e)
    (01) 2014-07-02 10:53:03 Slp:    at System.Xml.XmlTextReaderImpl.ThrowInvalidChar(Int32 pos, Char invChar)
    (01) 2014-07-02 10:53:03 Slp:    at System.Xml.XmlTextReaderImpl.ParseNumericCharRefInline(Int32 startPos, Boolean expand, BufferBuilder internalSubsetBuilder, Int32& charCount, EntityType& entityType)
    (01) 2014-07-02 10:53:03 Slp:    at System.Xml.XmlTextReaderImpl.ParseNumericCharRef(Boolean expand, BufferBuilder internalSubsetBuilder, EntityType& entityType)
    (01) 2014-07-02 10:53:03 Slp:    at System.Xml.XmlTextReaderImpl.HandleEntityReference(Boolean isInAttributeValue, EntityExpandType expandType, Int32& charRefEndPos)
    (01) 2014-07-02 10:53:03 Slp:    at System.Xml.XmlTextReaderImpl.ParseAttributeValueSlow(Int32 curPos, Char quoteChar, NodeData attr)
    (01) 2014-07-02 10:53:03 Slp:    at System.Xml.XmlTextReaderImpl.ParseAttributes()
    (01) 2014-07-02 10:53:03 Slp:    at System.Xml.XmlTextReaderImpl.ParseElement()
    (01) 2014-07-02 10:53:03 Slp:    at System.Xml.XmlTextReaderImpl.ParseElementContent()
    (01) 2014-07-02 10:53:03 Slp:    at System.Xml.XmlLoader.LoadNode(Boolean skipOverWhitespace)
    (01) 2014-07-02 10:53:03 Slp:    at System.Xml.XmlLoader.LoadDocSequence(XmlDocument parentDoc)
    (01) 2014-07-02 10:53:03 Slp:    at System.Xml.XmlDocument.Load(XmlReader reader)
    (01) 2014-07-02 10:53:03 Slp:    at Microsoft.SqlServer.Chainer.Infrastructure.DataStoreService.LoadXmlDocument(String xml, XmlSchema schema, String namespacePrefix, String namespaceUri, String rootPath)
    (01) 2014-07-02 10:53:03 Slp:    --- End of inner exception stack trace ---
    (01) 2014-07-02 10:53:03 Slp:    at Microsoft.SqlServer.Chainer.Infrastructure.DataStoreService.LoadXmlDocument(String xml, XmlSchema schema, String namespacePrefix, String namespaceUri, String rootPath)
    (01) 2014-07-02 10:53:03 Slp:    at Microsoft.SqlServer.Chainer.Infrastructure.DataStoreService.LoadXmlDocument(XmlDocument doc, XmlSchema schema, String namespacePrefix, String namespaceUri, String rootPath)
    (01) 2014-07-02 10:53:03 Slp:    at Microsoft.SqlServer.Chainer.Infrastructure.SqlDiscoveryDatastoreInterface.LoadData(IEnumerable`1 machineNames, String discoveryDocRootPath, String clusterDiscoveryDocRootPath)
    (01) 2014-07-02 10:53:03 Slp:    at Microsoft.SqlServer.Configuration.SetupExtension.RunDiscoveryAction.ExecuteAction(String actionId)
    (01) 2014-07-02 10:53:03 Slp:    at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
    (01) 2014-07-02 10:53:03 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.<>c__DisplayClasse.<ExecuteActionWithRetryHelper>b__b()
    (01) 2014-07-02 10:53:03 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker workerDelegate)
    (01) 2014-07-02 10:53:03 Slp:    --- End of inner exception stack trace ---
    (01) 2014-07-02 10:53:03 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker workerDelegate)
    (01) 2014-07-02 10:53:03 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionWithRetryHelper(WorkflowObject metaDb, ActionKey action, ActionMetadata actionMetadata, TextWriter statusStream)
    (01) 2014-07-02 10:53:03 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
    (01) 2014-07-02 10:53:03 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
    (01) 2014-07-02 10:53:03 Slp: Received request to add the following file to Watson reporting: c:\temp\tmpFEEB.tmp
    (01) 2014-07-02 10:53:03 Slp: The following is an exception stack listing the exceptions in outermost to innermost order
    (01) 2014-07-02 10:53:03 Slp: Inner exceptions are being indented
    (01) 2014-07-02 10:53:03 Slp:
    (01) 2014-07-02 10:53:03 Slp: Exception type: Microsoft.SqlServer.Chainer.Infrastructure.ChainerInfrastructureException
    (01) 2014-07-02 10:53:03 Slp:     Message:
    (01) 2014-07-02 10:53:03 Slp:         '.', hexadecimal value 0x00, is an invalid character. Line 1, position 231747.
    (01) 2014-07-02 10:53:03 Slp:     HResult : 0x84b10001
    (01) 2014-07-02 10:53:03 Slp:         FacilityCode : 1201 (4b1)
    (01) 2014-07-02 10:53:03 Slp:         ErrorCode : 1 (0001)
    (01) 2014-07-02 10:53:03 Slp:     Stack:
    (01) 2014-07-02 10:53:03 Slp:         at Microsoft.SqlServer.Chainer.Infrastructure.DataStoreService.LoadXmlDocument(String xml, XmlSchema schema, String namespacePrefix, String namespaceUri, String rootPath)
    (01) 2014-07-02 10:53:03 Slp:         at Microsoft.SqlServer.Chainer.Infrastructure.DataStoreService.LoadXmlDocument(XmlDocument doc, XmlSchema schema, String namespacePrefix, String namespaceUri, String rootPath)
    (01) 2014-07-02 10:53:03 Slp:         at Microsoft.SqlServer.Chainer.Infrastructure.SqlDiscoveryDatastoreInterface.LoadData(IEnumerable`1 machineNames, String discoveryDocRootPath, String clusterDiscoveryDocRootPath)
    (01) 2014-07-02 10:53:03 Slp:         at Microsoft.SqlServer.Configuration.SetupExtension.RunDiscoveryAction.ExecuteAction(String actionId)
    (01) 2014-07-02 10:53:03 Slp:         at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
    (01) 2014-07-02 10:53:03 Slp:         at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.<>c__DisplayClasse.<ExecuteActionWithRetryHelper>b__b()
    (01) 2014-07-02 10:53:03 Slp:         at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker workerDelegate)
    (01) 2014-07-02 10:53:03 Slp:     Inner exception type: System.Xml.XmlException
    (01) 2014-07-02 10:53:03 Slp:         Message:
    (01) 2014-07-02 10:53:03 Slp:                 '.', hexadecimal value 0x00, is an invalid character. Line 1, position 231747.
    (01) 2014-07-02 10:53:03 Slp:         HResult : 0x80131940
    (01) 2014-07-02 10:53:03 Slp:         Stack:
    (01) 2014-07-02 10:53:03 Slp:                 at System.Xml.XmlTextReaderImpl.Throw(Exception e)
    (01) 2014-07-02 10:53:03 Slp:                 at System.Xml.XmlTextReaderImpl.ThrowInvalidChar(Int32 pos, Char invChar)
    (01) 2014-07-02 10:53:03 Slp:                 at System.Xml.XmlTextReaderImpl.ParseNumericCharRefInline(Int32 startPos, Boolean expand, BufferBuilder internalSubsetBuilder, Int32&
    charCount, EntityType& entityType)
    (01) 2014-07-02 10:53:03 Slp:                 at System.Xml.XmlTextReaderImpl.ParseNumericCharRef(Boolean expand, BufferBuilder internalSubsetBuilder, EntityType& entityType)
    (01) 2014-07-02 10:53:03 Slp:                 at System.Xml.XmlTextReaderImpl.HandleEntityReference(Boolean isInAttributeValue, EntityExpandType expandType, Int32& charRefEndPos)
    (01) 2014-07-02 10:53:03 Slp:                 at System.Xml.XmlTextReaderImpl.ParseAttributeValueSlow(Int32 curPos, Char quoteChar, NodeData attr)
    (01) 2014-07-02 10:53:03 Slp:                 at System.Xml.XmlTextReaderImpl.ParseAttributes()
    (01) 2014-07-02 10:53:03 Slp:                 at System.Xml.XmlTextReaderImpl.ParseElement()
    (01) 2014-07-02 10:53:03 Slp:                 at System.Xml.XmlTextReaderImpl.ParseElementContent()
    (01) 2014-07-02 10:53:03 Slp:                 at System.Xml.XmlLoader.LoadNode(Boolean skipOverWhitespace)
    (01) 2014-07-02 10:53:03 Slp:                 at System.Xml.XmlLoader.LoadDocSequence(XmlDocument parentDoc)
    (01) 2014-07-02 10:53:03 Slp:                 at System.Xml.XmlDocument.Load(XmlReader reader)
    (01) 2014-07-02 10:53:03 Slp:                 at Microsoft.SqlServer.Chainer.Infrastructure.DataStoreService.LoadXmlDocument(String xml, XmlSchema schema, String namespacePrefix,
    String namespaceUri, String rootPath)
    (01) 2014-07-02 10:53:08 Slp: Watson Bucket 2
     Original Parameter Values
    (01) 2014-07-02 10:53:08 Slp: Parameter 0 : SQL Server
    2014@RTM@
    (01) 2014-07-02 10:53:08 Slp: Parameter 1 : Microsoft.SqlServer.Chainer.Infrastructure.DataStoreService.LoadXmlDocument
    (01) 2014-07-02 10:53:08 Slp: Parameter 2 : System.Xml.XmlTextReaderImpl.Throw
    (01) 2014-07-02 10:53:08 Slp: Parameter 3 :
    Microsoft.SqlServer.Chainer.Infrastructure.ChainerInfrastructureException@1201@1
    (01) 2014-07-02 10:53:08 Slp: Parameter 4 :
    System.Xml.XmlException@-2146232000
    (01) 2014-07-02 10:53:08 Slp: Parameter 5 : RunRemoteDiscoveryAction
    (01) 2014-07-02 10:53:08 Slp:
     Final Parameter Values
    (01) 2014-07-02 10:53:08 Slp: Parameter 0 : SQL Server
    2014@RTM@
    (01) 2014-07-02 10:53:08 Slp: Parameter 1 : 0xDBE3EAAC
    (01) 2014-07-02 10:53:08 Slp: Parameter 2 : 0x066FCAFD
    (01) 2014-07-02 10:53:08 Slp: Parameter 3 :
    0xDF039760@1201@1
    (01) 2014-07-02 10:53:08 Slp: Parameter 4 : 0x5539C151
    (01) 2014-07-02 10:53:08 Slp: Parameter 5 : RunRemoteDiscoveryAction
    (01) 2014-07-02 10:53:09 Slp: Sco: Attempting to write hklm registry key Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Registry_SOFTWARE_Microsoft_Microsoft SQL Server.reg_
    (01) 2014-07-02 10:53:09 Slp: Sco: Attempting to write hklm registry key Uninstall to file C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Registry_SOFTWARE_Microsoft_Windows_CurrentVersion_Uninstall.reg_
    (01) 2014-07-02 10:53:09 Slp: Sco: Attempting to write hklm registry key MSSQLServer to file C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Registry_SOFTWARE_Microsoft_MSSQLServer.reg_
    (01) 2014-07-02 10:53:09 Slp: Sco: Attempting to write hklm registry key Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Registry_SOFTWARE_Wow6432Node_Microsoft_Microsoft SQL Server.reg_
    (01) 2014-07-02 10:53:09 Slp: Sco: Attempting to write hklm registry key Uninstall to file C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Registry_SOFTWARE_Wow6432Node_Microsoft_Windows_CurrentVersion_Uninstall.reg_
    (01) 2014-07-02 10:53:09 Slp: Sco: Attempting to write hklm registry key MSSQLServer to file C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Registry_SOFTWARE_Wow6432Node_Microsoft_MSSQLServer.reg_
    (01) 2014-07-02 10:53:10 Slp: '.', hexadecimal value 0x00, is an invalid character. Line 1, position 231747.
    (01) 2014-07-02 10:53:10 Slp: Watson bucket for exception based failure has been created
    (01) 2014-07-02 10:53:10 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
    (01) 2014-07-02 10:53:10 Slp: Sco: Attempting to open registry subkey Software\Microsoft\Microsoft SQL Server\120
    (01) 2014-07-02 10:53:10 Slp: Sco: Attempting to get registry value EnableErrorReporting
    (01) 2014-07-02 10:53:10 Slp: WER: Successfully read app consent from registry Software\Microsoft\Microsoft SQL Server\120\EnableErrorReporting=.
    (01) 2014-07-02 10:53:10 Slp: WER: Application level consent value '' was mapped to consent status 'WerConsentNotAsked'
    (01) 2014-07-02 10:53:12 Slp: WER: Result of the submission:: 'WerReportCancelled'
    (01) 2014-07-02 10:53:12 Slp: WER: Submitted 1 of 1 failures to the Watson data repository
    (01) 2014-07-02 10:53:12 Slp:
    (01) 2014-07-02 10:53:12 Slp: ----------------------------------------------------------------------
    (01) 2014-07-02 10:53:12 Slp:
    (01) 2014-07-02 10:53:12 Slp: Error result: -2068774911
    (01) 2014-07-02 10:53:12 Slp: Result facility code: 1201
    (01) 2014-07-02 10:53:12 Slp: Result error code: 1
    (01) 2014-07-02 10:53:12 Slp: SQM Service: Sqm does not have active session.
    /* Don Reynolds */

  • Integrate 'External non-SAP Purchasing Application' with SAP SD for third party purchasing/ drop shipping?

    What is the best way to integrate 'External non-SAP Purchasing Application' with SAP SD for third party purchasing/ drop shipping?
    Details about expected process Flow.
    Receive PO from customer into SAP > SAP SD creates Sales Order > ?? SAP Integrate with External non-SAP Purchasing Application to trigger purchasing > External non-SAP Purchasing Application creates PO, Ships Material to Customer Ship to address (drop ship), Sends Shipping confirmation (FCR) & Invoices to SAP> ??Receive FCR and Invoice in SAP > ?? Initiate SAP Accounts Payable (Vendor Payments) and Accounts Receivable (Customer Invoice) > ?? Update SAP SD Sales Order with shipping status>
    Questions we need to answer;
      - How to achieve '??' steps from above process.
      - What type of Master Data we will need to configure (Say Materials Item Category, Type etc.)
      - Any standards options to configure SAP SD (Type of Sales Order)
      - We certainly don’t want to trigger SAP MM Purchasing (i.e. PR, PO etc.). How can we bypass it.
      - How to make statistical receipts against sales order line items so that SO status will be updated.
      - How to receive Invoice and FCR from External non-SAP app to trigger AP and AR transactions.
      - Are there any SAP standard configurations/ BAPIs/ BADIs available to achieve this integration.
    Any inputs on above questions are appreciable.
    Anand.

    This question is resolved. We ended up activating purchasing module and used purchasing documents PR/ PO to integrate with third party purchasing system.
    Anand.

  • Regarding statistical setup running

    Hai
    iam loding data for purchasing data using 4 data sorses.(2lis_02_scn,2lis_02_cgr,2lis_02_sgr,2lis_02_itm) when i run the statistical setup by using OLI3BW i am geting data of ITM AND SGR data sorses into setup tables, but i am not getting data of remaining data sorses , data is present in the tables of that data sorses.what is the reason , pls provide solution its very very urgent. points will be assigned. and when i go to LBWE to see the structure the below error is coming, pls explain it.
    *Structure maintenance not provided for extraction structure MC02M0CGR ->*_
    Message no. MCEX152Diagnosis
    Structure MC02M_0CGR concerns a technical extraction structure. The inclusion of additional fields by using the structure maintenance is not part of the procedure for this.
    If an extraction structure is used for extracting transaction data from two different business events, then the generic filling of the extraction structure fields from the fundamental communication structure data does not normally occur. An enhancement of structure MC02M_0CGR could then cause the newly included fields from the different events to be filled differently or not at all.
    Procedure
    Use the fields delivered by SAP for the structure MC02M_0CGR. Check to see whether the additional information you want can be extracted using other structures.

    If the SCN structure is anything like the CGR structure, then neither will load.  To load into the setup tables, you need to have active structures. 
    It looks like someone was changing the CGR structure and somehow damaged it or deactivated it.  You need to fix this and then reactivate the structure.  Then you will get your data.
    Good Luck,
    Brian

  • Statistical Setup Error - Error Converting Quantity

    Dear SDN Mates,
    We are getting this below error while doing the statistical setup for SD extraction in 11 application,
    Error converting quantity: unit M numerator 0 / denominator 0.
    Regards
    Arun S

    Hi guys,
    I have the same error with below message :
    Error determining rate: foreign curr.  local curr.KRW date 17.06.2011 (doc. 14024)
    I checked data in table VBAK with sale document 14024, some information of this data record related above error :
    + ERDAT (Date on Which Record Was Created) : 17.06.2011
    + WAERK (SD Document Currency) : KRW
    + STWAE (Statistics currency) : <BLANK>
    I tried to create 2 new records in Currency Exchange Rates (OB08), like this :
    But there're still error.
    Please give some ideas to solve it.
    Regards
    Dennis Vu,

  • STATISTICAL SETUP- LO

    Hi Gurus,
    What is STATISTICAL SETUP in LO extraction.
    Regards,RAMU>

    Hello ram,
    Please go thru this.
    Setup of Statistical Data
    During a setup (statistical setup), the information structures are filled with consistent and complete data.
    The statistical setup of one or more information structures is necessary in the following cases:
    •     If an information structure was created using the Logistics Data Warehouse (statistical database)
    •     If the update for the information structures was activated after documents were already in the system that were meant to be included in the statistics
    •     If the statistical update in Customizing was changed
    •     If the statistical data is inconsistent
    Preparation
    To restart a statistical update after an termination, allocate a name to each background run of the setup.
    If a statistical setup is then terminated or if a setup is interrupted from the archive documents, the status of the setup will then be saved under the name of this run.
    When restarting under the same name, processing will continue from the intermediate status that was saved.
    After the run is successfully completed, the intermediate status that was saved is deleted.
    Recommendation
    •     The reports should run as a background job.
    •     You should not change the sequence of steps that describe the statistical setup of information structures (procedure).
    Procedure
    The following steps are necessary to perform a complete statistical set up:
    1. Initialize version for statistical setup
    For reasons of security, the statistical data determined during a setup is not directly written into an information structure, but are saved instead under a separate version name. This version must be activated for intermediate storage before the statistical setup is carried out.
    For this purpose, the report RMCSISCP is available.
    The actual data is saved under the version name "000".
    2. Save actual data
    The actual data in the system should be saved for safety reasons.
    Again, use report RMCSISCP for this purpose.
    3. Edit all archived documents
    To do this, you can use the various reports that are available in the individual applications.
    4. Edit all documents in the system
    This also takes place via the various reports that are available in the individual applications.
    5. Transfer the data which was obtained in the statistical setup from the statistical setup version to the actual version
    The data obtained is only imported to the actual version instead of the existing data after the successful completion of the statistical setup.
    The report RMCSISCP is again used for this purpose.
    Note
    You can see the versions of the standard information structures by using the standard analyses. Here are the following possibilities:
    a) You can allocate the version number of the version as a value to the user parameter "MCR" that you would like to see.
    On the selection screen of the standard analysis, the field Version under Parameters is automatically completed  with the given version number. The version number can be changed simply by overwriting it.
    This setting is user-dependent and applies to all standard analyses.
    b) If you assign the value "X" to the user paramter "MCR", the version "000" will generally appear on the selection screen of the standard analyses. Even in this case, the version number can be overwritten.
    This setting is also user-dependent and applies to all standard analyses.
    If you want to use either one of these functions, select System -> User profile -> User parameters. You can select this function from any menu.
    Recommendation
    You should change the user parameters in an alternative session, as it is not possible to return to the starting point from the user parameters maintenance screen.
    c) Via "User settings", you can also make specifications for the versions, which are also user-dependent, but also only refer to one particular standard analysis.
    To do this, in the selection screen of the standard analysis, select Goto -> User settings.
    You are now in the standard drill-down. Select Goto ->Parameters.
    If you set the indicator "Selectable version", the field "Version" with the version number "000" will also appear on the selection screen. This version number can be overwritten at any time and thus changed.
    6. Follow-up processing
    After successfully completing the statistical setup, you can then delete data that is no longer needed by deleting the version under which this data is saved.
    These include:
    o     Safety copy
    o     Version for statistical setup
    The report RMCSISCP can be used for this purpose.
    Activities
    To carry out a statistical setup, procede as follows:
    1. Enter your selection requirements.
    2. Save your entries.
    3. Select Program -> Execute.
    Description of the report RMCSISCP
    The report RMCSISCP is used in all information systems in Logistics. For this reason, the report is described below.
    You can use report RMCSISCP you can copy or delete versions from information structures under which statistical data has been saved.
    The data, that has been saved in an information structure, is different due to the version under which they have been saved.
    The version "000" includes the actual data, i.e., the data that was written into the information structure as a result of the statistical update.
    The intermediate results are stored in the versions that begin with "&(" and that are created when an information structure is setup.
    Planning data is stored under all other versions (that means version A000 and all numerical versions except version 000).
    The statistical setup of an information structure is carried out just like the online update, with the difference being that the data is not usually written into version "000" first, but rather into a version that you choose, that begins with "&(". The data is only copied from this version into the "000" version after the successful completion of the initial transfer.
    Note
    While copying into the "000" version, you must not carry out any postings that update the respective information structure.
    To keep the old version "000" (the existing actual data) from being lost, save it under another version. This "safety copy" is also generated with report RMCSISCP.
    You can use the indicator "Initialize target version" to delete data data stored until now under this version. If the indicator "Do not copy initial records" is set, data records are only set if at least one key figure is not initial.
    Attention
    The report RMCSISCP should only be used for copying, deleting and for copying + deleting. Copy Management should be used to meet more complex requirements (Tools -> Copy Management).
    Activities
    1. Enter the name of the information structure that is to be copied/deleted.
    2. Choose a processing type.
    The Copy Management screen is called up. The processing type that you have selected is already set.
    3. Here you make all the remaining entries required for selection.
    Additional functions
    You can also call up a log which contains detailed information about all of the completed setup runs.
    This function allows you to make restrictions by specifying the start date of a run, the run name, the user and the application.
    You can also either print the list of selected setup runs or the detail screen for a setup run.
    Thanks,Ramoji.

  • I bought my ipad in us, and has been using a purchasing applications. Now i already went back to bahrain, i am trying to purchase apllication using my bahrain credit card but it cannot get through as the default country is USA.   I tried

    I bought my ipad in us, and has been using a pre paid card in purchasing applications. Now i already went back to bahrain, i am trying to purchase apllication using my bahrain credit card but it cannot get through as the default country is USA.
    I tried to change my country but a message says i have a store credit balance and must spend it before changing store. But how i can spend it i only have 8 cents left?
    So how will i be able to purchase applications if i am in bahrain?

    You can try again after a few hours after waiting and you still get the same error, you'll need to contact support.
    https://expresslane.apple.com/GetproductgroupList.action

  • HT204266 Why is it that after upgrading to IOS 6, I could not retreive my full list of my purchased applications & ganes list in the app store now !!!!

    Why is it that after upgrading to IOS 6, I could not retreive my full list of my purchased applications &amp; ganes list in the app store now !!!!
    Whenever I try to tab my purchased in the update feature of app store; not only does the long list of my previous purchases do not showed up like in IOS 5 do but after a while it just prompt out to the main home page. I tried this for both my 3GS and 4GS too and both have the same problem. APPLE INC please rectify this serious problem as soon as possible.

    Did you read your other posted question, that has been answered.

  • After Effects can't continue: unexpected failure during application startup

    Im running 10.10, Mac OSX, it was running fine before a minor update came out, and now I can not open AE CS6. I have uninstalled, reinstalled it, installed the trial of CC 2014. No messages beside "After Effects can’t continue: unexpected failure during application startup" come up.
    System log:
    Jun 22 15:30:49 Users-iMac.local AdobeCrashDaemon[976]: WARNING: The Gestalt selector gestaltSystemVersion is returning 10.9.0 instead of 10.10.0. Use NSProcessInfo's operatingSystemVersion property to get correct system version number.
                Call location:
    Jun 22 15:30:49 Users-iMac.local AdobeCrashDaemon[976]: 0   CarbonCore                          0x00007fff82bb637d ___Gestalt_SystemVersion_block_invoke + 113
    Jun 22 15:30:49 Users-iMac.local AdobeCrashDaemon[976]: 1   libdispatch.dylib                   0x00007fff8bf70fa2 _dispatch_client_callout + 8
    Jun 22 15:30:49 Users-iMac.local AdobeCrashDaemon[976]: 2   libdispatch.dylib                   0x00007fff8bf70f00 dispatch_once_f + 79
    Jun 22 15:30:49 Users-iMac.local AdobeCrashDaemon[976]: 3   CarbonCore                          0x00007fff82b5e932 _Gestalt_SystemVersion + 987
    Jun 22 15:30:49 Users-iMac.local AdobeCrashDaemon[976]: 4   CarbonCore                          0x00007fff82b5e51f Gestalt + 144
    Jun 22 15:30:49 Users-iMac.local AdobeCrashDaemon[976]: 5   AdobeCrashDaemon                    0x0000000100002e69 -[MyDaemon GetOSVersionMajor] + 33
    Jun 22 15:30:49 Users-iMac.local AdobeCrashDaemon[976]: 6   AdobeCrashDaemon                    0x0000000100002d4a -[MyDaemon isRunningOnLeopard] + 25

    Well, looks like a bug in Yosemite. You might wanan read the pertinent announcements, anyway. At this point Adobe apps are not compatible with OSX 10.10.
    Mylenium

Maybe you are looking for

  • Re install itunes on my formated pc

    How i re install i tunes on my formated pc?

  • Empty DVD drive spins and hums while battery is charging

    This is odd and specific: When the battery runs down on my Powerbook and goes to sleep, I plug in the charger and the DVD drive starts spinning. It gives a continuous hum, despite being empty, which stops when I sleep the computer. When I reawaken it

  • No Matter What I Try, Keynote Continues To Crash

    Hello All, I am pleading for your help as I have exhausted what I think is every conceivable resource to solve this problem. I have ran Keynote '09 for many a year now and have not had any issues. Two weeks ago my business partner started a Keynote '

  • ON SAP CRM

    HI,     Can any one send me some information about sap crm.What is crm,How the data flows in crm,How to extract data from crm to bw.    please can any one send this information. Thanks, Indira.

  • DB Performance

    I need some help on the following query: Wanted to know about performance of Oracle DB on a 20 way IBM machine(in general or any specific doc)