QUEUE_NAME is initial Frank Schmitt cau u give the solution?

Hi Frank,
My Scenario is Webservices-XI-BW...
While sending data from webservices the response i get is QUEUE_NAME is initial... this i am getting since i am using QOS--EOIO,
Can u tell me how u have solved this solution which u posted in sdn long back...
Result:
<SAP:Error>
<SAP:Category>XIServer</SAP:Category>
<SAP:Code>INTERNAL.ATTRIBUTE_INITIAL</SAP:Code>
<SAP:P1>QUEUE_NAME</SAP:P1>
<SAP:Stack>Attribute QUEUE_NAME is initial</SAP:Stack>
</SAP:Error>
I am also getting same error ...
please can u let me know how u have solved this
Regards,
Sridhar
Message was edited by: sridhar reddy kondam

Hi Michael,
Thanks for u r reply,
I am not using Soap Adapter, I am using XI adapter, and followed the Doc how to send XML data to BW using the doc
http://service.sap.com/~sapidb/011000358700011142902001E/HOWTOSENDXMLDATATOBW.DOC
My scenarion is XI-BW integration.
Here I am trying to send XML data as mentioned in the doc.. i can see the messeges if i give the QOS as EO but if i give EOIO then the said response i am getting...
Request u to give solution or suggestion...
Regards,
sridhar

Similar Messages

  • Please give the solutions ASAP.

    Hi Friends,
    Please give the solutions  if you know 100% correct...please don't go for slice and dice method.
    1. Which of the following is true of SID tables?
    a. SID tables are not part of the basic star schema
    b. The SID table links the dimension table to the fact table
    c. SID values in a SID table are only numeric
    d. Navigation attributes use the standard SID table
    e. The SID table links the master data and dimension tables.
    2. Which of the following parallel processes could have locking problem
       A. Hierarchy attr. change run    B.Loading Master data from Info object from various source systems. C  Roll up of Aggregates on Infocube D. Selective deletion Info cube / ODS E. Loading Info cube / ODS
    a. A & C
    b. A & B
    c. Â & D or E
    d. A&B, A &C, D &E.
    3. The transactional ODS will have the following tables.
    a. Active table
    b. Change log
    c. New table
    d. Active and New table
    e. no table.
    4. Which components of the BW star schema use SID?
    a. Dimensions
    b. Key Figures
    c. Characteristics
    d. Navigational Attributes
    e. Units
    5. Which of the following statements are true about aggregates?
    a. Once an aggregate is deactivated all data is deleted
    b. Time-dependent hierarchy structures with time dependent navigational attributes are allowed in aggregates
    c. More than one key characteristic is permitted in aggregates
    d. Time dependant characteristics are permitted in aggregates
    6. Where can you initially specify PSA or IDOCS?
    a. Transfer methods tab in the transfer rules
    b. In the scheduler
    c. In the communication structure
    d. In the assignment of the Infosource
    7. Why do you need a communication and transfer structure?
    a. for loading attributes
    b. for loading text
    c. for loading Transaction data
    d. for loading hierarchies
        8. What are the types of attributes?
    a. Navigational and text     
    b. Display and navigational     
    c. Display and calculated      
    d. Text and display     
    9. What is the role of the application components section?
    a. Organization of InfoSource
    b. Organization of Source System
    c. Organization of Infocubes
      10.  What is PSA the abbreviation for?
           a. Persistence Staging Area
            b. Permanent staging area
            c. Pre staging area
           d. None of the above
    11. If some data is missing, can you run full loads with selections in deltas?
            a. yes
             b. no
    12. Where can we decrease or increase the time limit for an IP to be in yellow state?
           a. IP settings.
           b. Technical status tab
           c. Update rules
    d. Data target.
    13. Multiproviders can include?
    a. All infocubes only
    b. ODSs only
    c. Infocubes, ODSs and infoobjects
    d. Infoobjects only.
    14. Which of the following reside on the BW system?
    a. Plug-In
    b. V1 Update queue
    c. InfoSource
    d. Extraction structure
    e. ODS.
    15. What are the two fact tables?
    a. E table, F table
    b. P table, E table
    c. F table, H table
    d. M table, A table.

    Hi,
    1. Which of the following is true of SID tables?
    c. SID values in a SID table are only numeric
    e. The SID table links the master data and dimension tables.
    2. Which of the following parallel processes could have locking problem
    a. A & C
    3. The transactional ODS will have the following tables.
    a. Active table
    4. Which components of the BW star schema use SID?
    a. Dimensions
    c. Characteristics
    d. Navigational Attributes
    5. Which of the following statements are true about aggregates?
    b. Time-dependent hierarchy structures with time dependent navigational attributes are allowed in aggregates
    c. More than one key characteristic is permitted in aggregates
    6. Where can you initially specify PSA or IDOCS?
    a. Transfer methods tab in the transfer rules
    7. Why do you need a communication and transfer structure?
    c. for loading Transaction data
    8. What are the types of attributes?
    b. Display and navigational
    9. What is the role of the application components section?
    a. Organization of InfoSource
    10. What is PSA the abbreviation for?
    a. Persistence Staging Area
    11. If some data is missing, can you run full loads with selections in deltas?
    b. no
    12. Where can we decrease or increase the time limit for an IP to be in yellow state?
    a. IP settings.
    13. Multiproviders can include?
    c. Infocubes, ODSs and infoobjects
    14. Which of the following reside on the BW system?
    c. InfoSource
    e. ODS.
    15. What are the two fact tables?
    a. E table, F table
    Regards
    Sunil

  • Can any body give the solution

    Hi,
    Can any body give the solution for my queries?
    A two level PO Release workflow is required to support the Import PO Release Approval business process.  Forecast and Replenishment will transfer orders to SAP ERP. Purchase orders will be blocked upon creation based on the document type. If the document type is ZIMP=Import Purchase order, the order will have to go through a release process described below:
    When a PO is created it will be automatically blocked based on the document type ZIMP and a workflow will be triggered to the stock planner responsible to work on the containerization of the order. The stock planner will receive an email notification and an SAP workitem to generate and send a report to the vendor to get the order containarized. Once the report has been sent the purchase order will be relased with code 01:In containerization.
    01/29/07: The containerization report needs to include: PO number (EKPO_EBELN), Article number (EKPO_MATNR), Vendor part number (EKPO_MFRPN), Description (MKAT_MAKTX), Quantity in Base unit of Measure (EKPO_MENGE) and Quantity in BuyPack unit of measure and Net price (EKPO_BPRME). This report should be generated out of SAP as part of the release code 01 of the workflow. The report will be downloaded to excel by the approver.
    After the order is released with code 01, a second workitem will be triggered to the stock planner who will use SAP to execute the workitem. The work item will allow the modification of the PO (if needed) with the containerized quantities and the release of it using release code 02:Release. The second work item for release code 02 does not need to trigger the report. 
    Substitutions:  If there is a substitute for the approver (i.e.an admin), that person will be included on the list of approvers.
    Emergency approvals:  A position not in the approver hierarchy (i.e., Finance Marketing Manager) can approve the request outside the loop of the approval workflow.
    these are the questions i have from the above requirement:
    Is the containerazation report which has to be include few fields has to develop as a report or has to be done in workflow?
    Can any body explain how the order is containerized and what is containerization?
    Where can i see the release codes in the me21n?
    If there is any queries regarding this requirement to shoot Functional Spec owner.Please Send to me.
    Give the Solutions ASAP.
    Regards,
    Naidu.

    See my response in Can any body give the solution.
    Rosaiah and others: please quit starting multiple threads for the same request. It is just annoying! In my opinion it is also disrespectful to everyone else in the forum, but that's my personal opinion.
    You could either have edited your original request, or posted a reply to it with the additional information.

  • REGARDING SCRIPTS.... CAN ANY ONE GIVE THE SOLUTION FOR THIS

    I have copied the standard script ML_SERVICE_ENTRY to ZFORM.... in tcode se71 but it has its original lang. - DE and lang - EN , if i get into this ZFORM ...
    in change mode,  the creation of windows, windows allignment and convert original lang. are in disabled mode , here i have to change the window size to add some text , is there any other method to change the language and to get these things in
    enable mode. plz give some solution for this one.

    Hi Mohan,
    While copying itself U have to give the Language in which U want to maintain, else U are supposed login in with the original Language only.
    Regards,
    Mohan
    *Reward if helpful*

  • Can any  one give the solution

    One standard program is copied to zprogram i want to change that report Header(in output screen)Report name:Vendor Age Analysis-Forecasted payment.it will show in output as a report header.

    Hi
    you can do the following steps:
    1) go to se38
    2) type your program name.
    3) select one of  the radio buttons available there " attributes".
    4) click on change.
    5) you will get a screen.
    6) there you can change the title of the program as your wish.
    7) save it and actiavte it.
    8) execute it.
    Hope it is useful if i understood what you need.
    reward points if useful.

  • Can any body give the solutions for frequently asked questions

    can any body help me in the following questions.
    1 .  what is a conversion routine .
    2.  how do you create fonts and colors in the sap scripts.
    3. how do u upload a logo in a smart form .
    4. can u  get both landscape and portrait in same layout , if yes how .
    5. what is the functional module used to upload excel file .
    6. what is the functional module used to get longtext in the report for purchase orders and sales orders
    7. what is the even alternative to initialization where authorizations are declared to run a report.
    8. how the exceptions with in function module rise when they are uncommented.
    9. how do u translate the report to other than system language.
    10. how to debug a sf without putting a stop point.
    11. what is the procedure to handle the data upload using table control in bdc.
    12. what is the procedure to access the standard text into scripts.
    13. what is the procedure to send the smart forms as a mail .
    14. in bdc how can u handle the table controls .
    15. there are 10000 records in a flat file and first record contains error , if I upload to the bdc program , and run in bdc session method what will happen.
    16. how can u attach the transport request for scripts .
    17. tools to transfer requests to quality control or production system.
    thanks in advance.

    Hi,
    Pls check service.sap.com/certification or your local education center at www.sap.com/education
    Eddy
    PS. Reward the useful answers and you will get <a href="http:///people/baris.buyuktanir2/blog/2007/04/04/point-for-points-reward-yourself">one point</a> yourself!

  • Any one can give the solution in terms of SQL

    I have a table like below
    Table Structure is
    1). Employee No - NUMBER(5)
    2). ATT_DATE_TIME - DATE
    3). INOUT - CHAR(1)
    the data are as below
    Employee DATE TIME IN/OUT ( I-IN, O-OUT)
    number
    2835     01/01/06     15.20     I
    2835     01/01/06     15.21     I
    2835     01/01/06     15.21     I
    2835     01/01/06     15.21     I
    2835     01/01/06     15.21     I
    2835     01/01/06     15.21     I
    2835     01/01/06     15.21     I
    2835     01/01/06     15.20     I
    2835     01/01/06     15.20     I
    2835     01/01/06     15.21     I
    2835     01/01/06     15.21     I
    2835     01/01/06     15.21     I
    2835     01/01/06     15.20     I
    2835     01/01/06     15.21     I
    2835     01/01/06     15.21     I
    2835     01/01/06     15.21     I
    Here an employee has logged so many times. i want to find out the nexted duplicate / invalid log data for single employee number and date

    the raw data are
    employe number Date Time In/Out
    A1 02-May-07 08:15:25 IN
    A1 02-May-07 08:15:26 IN
    A1 02-May-07 08:15:30 IN
    A2 02-May-07 08:15:32 IN
    A2 02-May-07 08:15:34 IN
    A1 02-May-07 14:15:10 OUT
    A1 02-May-07 15:00:10 IN
    A1 02-May-07 16:15:00 OUT
    A1 02-May-07 16:15:30 OUT
    A2 02-May-07 17:25:22 OUT
    employee number 1 data are extracted from above
    employe number Date Time In/Out
    A1 02-May-07 08:15:25 IN
    A1 02-May-07 08:15:26 IN
    A1 02-May-07 08:15:30 IN
    A1 02-May-07 14:15:10 OUT
    A1 02-May-07 15:00:10 IN
    A1 02-May-07 16:15:00 OUT
    A1 02-May-07 16:15:30 OUT
    employee number 2 data are extracted from above
    employe number Date Time In/Out
    A2 02-May-07 08:15:32 IN
    A2 02-May-07 08:15:34 IN
    A2 02-May-07 17:25:22 OUT
    I want output as below
    employe number Date Time In/Out
    A1 02-May-07 08:15:25 IN
    A2 02-May-07 08:15:32 IN
    A1 02-May-07 14:15:10 OUT
    A1 02-May-07 15:00:10 IN
    A1 02-May-07 16:15:30 OUT
    A2 02-May-07 17:25:22 OUT
    employee number 1 data are extracted from output as below
    A1 02-May-07 08:15:25 IN
    A1 02-May-07 14:15:10 OUT
    A1 02-May-07 15:00:10 IN
    A1 02-May-07 16:15:30 OUT
    employee number 2 data are extracted from output as below
    employe number Date Time In/Out
    A2 02-May-07 08:15:32 IN
    A2 02-May-07 17:25:22 OUT

  • Please give the solution...

    java.lang.NoSuchMethodError: com.sap.engine.services.webservices.jaxrpc.wsdl2java.BaseGeneratedStub._initParameter

    Hi Nizamudeen,
                             Please send the complete stack trace from server log as well as explain the complete scenario like what r u trying to do & where exactly u r getting this error.
    regards
    Sumit

  • Give the solution

    Hi,
    I want to write a program to get personal data and employee address of an employee between two dates.
    on selectionscreen i want to display personal number,from date,to date.
    Early reply is highly appreciable. <= the problem is still here and not searching, so I deleted your other thread as well.
    Thanks,
    ram.
    Edited by: Julius Bussche on Aug 18, 2008 7:11 PM

    Welcome to SCN Roshan.   I would encourage you to read the Rules of Engagement.   Please keep in mind this forum is for asking for help on problems you are unable to solve or have a question regarding ABAP.   The intent of this forum is not to have some one provide you code for a program that you have a spec for and need a program written.  The best part of learning ABAP is trying yourself and expanding your knowledge.  Please do come back if you have any questions or problems.  Good Luck and enjoy.
    Here is the link for the Rules of Engagement.
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/rulesofEngagement
    After scrolling further, I see you already posted this thread earlier and the thread was locked.
    select statement fails...
    Edited by: Mike Reich on Aug 18, 2008 8:22 PM

  • Can anybody give the solution of this code

    SELECT poh.org_id,pv.vendor_name,pol.creation_date,poh.segment1 "PO_NUM"
    rt.unit_price,jpt.tax_amount,NVL (pol.unit_price, 0) "PO_Amt",
    pda.quantity_ordered "QTY_Ordered",rsh.invoice_num,pol.item_description,
    msib.segment1,msib.segment2,msib.segment3,msib.segment4,mic.category_set_id
    FROM po_headers_all poh,
    po_lines_all pol,
    po_distributions_all pda,
    rcv_shipment_headers rsh,
    rcv_transactions rt,
    po_vendors pv,
    jai_po_taxes jpt,
    mtl_system_items_b msib,
    mtl_item_categories mic
    WHERE rsh.vendor_id = poh.vendor_id
    AND rt.po_header_id = pol.po_header_id
    AND poh.vendor_id = pv.vendor_id
    AND poh.po_header_id = pol.po_header_id
    AND jpt.vendor_id = poh.vendor_id
    AND msib.inventory_item_id = mic.inventory_item_id;

    Just to make things more evident
    SELECT poh.org_id,
           pv.vendor_name,
           pol.creation_date,
           poh.segment1 "PO_NUM"
           rt.unit_price,
           jpt.tax_amount,
           NVL (pol.unit_price, 0) "PO_Amt",
           pda.quantity_ordered "QTY_Ordered",
           rsh.invoice_num,
           pol.item_description,
           msib.segment1,
           msib.segment2,
           msib.segment3,
           msib.segment4,
           mic.category_set_id
      FROM po_headers_all poh,            /* (1)(3)(4)(5) */
           po_lines_all pol,              /* (2)(4) */
           po_distributions_all pda,      /* not joined */
           rcv_shipment_headers rsh,      /* (1) */
           rcv_transactions rt,           /* (2) */
           po_vendors pv,                 /* (3) */
           jai_po_taxes jpt,              /* (5) */
           mtl_system_items_b msib,       /* (6) */
           mtl_item_categories mic        /* (6) */
    WHERE rsh.vendor_id = poh.vendor_id                   /* (1) */
       AND rt.po_header_id = pol.po_header_id              /* (2) */
       AND poh.vendor_id = pv.vendor_id                    /* (3) */
       AND poh.po_header_id = pol.po_header_id             /* (4) */
       AND jpt.vendor_id = poh.vendor_id                   /* (5) */
       AND msib.inventory_item_id = mic.inventory_item_id  /* (6) */and another way
    poh  pol  pda  rsh  rt   pv   jpt  msib  mic
    1111111111111111
          2222222222222222
    33333333333333333333333333
    444444
    5555555555555555555555555555555
                                         666666
    /* msib|mic not joined with poh|pol|pda|rsh|rt|pv|jpt */
    /* no join begins/ends at pda */Regards
    Etbin

  • OLAP Query is Taking Time. Please give me the Solution.

    Hi Geof,
    I am new to this AW Cubes and all. I am facing with a problem. After reading u r responses and all I am asking u this question. I hope u will solve my problem.
    I trying to get the data out of cube using the below statement at SQL prompt.
    SELECT CONSTITUTION,ACTIVE_CODE,CLASSIFICATION,BR_CODE,CASTE,INTEREST_RATE,TOT_COUNT,OUTSTANDING_BAL FROM TABLE(OLAP_TABLE('MIS.KBL_REPORTS_AW DURATION SESSION',
    'DIMENSION CONSTITUTION AS varchar2(100) FROM AW_CUSTOMER_DIM1
    DIMENSION ACTIVE_CODE AS varchar2(50) FROM AW_ACTIVITY_DIM1
    DIMENSION CLASSIFICATION AS varchar2(50) FROM AW_PRODUCT_DIM1
    DIMENSION BR_CODE AS varchar2(50) FROM AW_BRANCH_DIM1
    DIMENSION CASTE AS varchar2(50) FROM AW_CASTE_DIM1
    DIMENSION INTEREST_RATE AS varchar2(50) FROM AW_INTEREST_DIM1
    MEASURE TOT_COUNT AS number(5) FROM KBL_REPORTS_CUBE1_COUNT_MEASURE
    MEASURE OUTSTANDING_BAL AS number(10) FROM KBL_REPORTS_CUBE1_BALANCE_MEASURE
    where CONSTITUTION like '%INDIVIDUAL%' and ACTIVE_CODE like '%010101';
    It is taking too much of time. Can u give the solution to me ???
    Regards,
    S.Vamsi Krishna

    Hi,
    What release are you using? You should use 10.2.0.2 if possible. The documentation references in this reply assume the 10.2.0.2 versions of the documentation.
    You may be able to add an empty MODEL clause to your query which has the paradoxical effect of speeding up most OLAP queries. See chapter 11 (OLAP_TABLE) in the Oracle OLAP Reference. But if performance is very poor, this is unlikely to improve matters enough.
    We need to figure out where the time is being spent. We can use Oracle trace files and the tkprof utility to do that. I'll describe the basics, but there is a lot more information in chapter 20 (Using Application Tracing Tools) of the Oracle Database Performance Tuning Guide.
    First, let's enable some configuration parameters that will cause the RDBMS to write some useful information to the trace file. Assuming that you have a SQL script that executes the query, you can add these commands to the beginning of the script:
    alter session set sql_trace=true
    alter session set timed_statistics=true
    alter session set "_olap_continuous_trace_file"=true
    alter session set "_olap_table_function_statistics"=true
    alter session set tracefile_identifier=perftest
    exec dbms_aw.execute('dotf tracefile');
    Now run the script with the query.
    Next we have to find the trace file. Trace files are written to the directory named by the configuration parameter user_dump_dest. As a privileged user, execute this command:
    SQL> show parameter user_dump_dest;
    Now look in that directory for a file whose name includes the string that we specified in the tracefile_identifier setting above (you can change this if you want):
    $ ls <user_dump_dest dir>/*perftest*.trc
    Having located the tracefile, run the tkprof utility:
    $ tkprof <trace file name> <tkprof output file name> aggregate=no
    Now edit the generated <tkprof output file name> and look for your query. It will be followed by a mini explain plan that includes a line for each subquery. You'll be able to see how much time is spent in each subquery and how many rows are returned to the enveloping query. The innermost subqueries will be the ones that query AW data. Your goal is to push as much of the work into the AW as possible, so that the AW engine return a minimal number of rows.
    You can get more detail from the trace file itself. If you are at all familiar with the OLAP DML, look for LIMIT commands and see that they roughly correspond to hierarchy selections and WHERE clause predicates in the SQL SELECT statement. OLAP DML comamnds have timestamps in the trace file, so you can get an idea of how long things are taking. You can find table function statistics by looking for XSTF and XSTABFUN in the trace file.
    Geof

  • Attribute QUEUE_NAME is Initial

    Hi All,
    My Scenario is Webservices-XI-BW...
    While sending data from webservices the response i get is QUEUE_NAME is initial... this i am getting since i am using QOS--EOIO,
    I have gone through weblog /people/sap.india5/blog/2006/01/03/xi-asynchronous-message-processing-understanding-xi-queues-part-i
    but i could not solve my problem....
    So can any one let me know how to make this solve...
    Regards,
    Sridhar Reddy

    Sridhar,
    Please go through the Note: 856597
    and the blog /people/siva.maranani/blog/2005/09/03/invoke-webservices-using-sapxi
    -Naveen.

  • Attribute QUEUE_NAME is initial Error

    Hallo,
    when I´m calling an BAPI over RFC and with QoS=EOIO then the following error occure:
    Result:
    <SAP:Error>
    <SAP:Category>XIServer</SAP:Category>
    <SAP:Code>INTERNAL.ATTRIBUTE_INITIAL</SAP:Code>
    <SAP:P1>QUEUE_NAME</SAP:P1>
    <SAP:Stack>Attribute QUEUE_NAME is initial</SAP:Stack>
    </SAP:Error>
    I made the RFC-Destination with the correct SAP-System; must i create a queue for this destination? And when yes how i can do this? I need an outbound-queue - yes?
    Thanks in advance,
    Frank

    Did you register your queues ? Go to <b>SXMB_ADM -> Manage Queues</b> and register your queues. If this does not work, delete the queues and register them again using the same transaction <b>SXMB_ADM -> Manage Queues</b>
    regards
    SKM

  • Cannot Install Sql Server 2008, Gives The Error "Database Engine Services Failed"

    I cannot install Sql Server 2008 R2 on Windows 8. Tried many times but failed because it gives the error "Database
    Engine Services Failed". Sql files cannot be corrupted because i can install the same setup on Windows 7 and i can connect to databases.
    I tried all the things below;
    * I'm uninstalling everything related with Sql Server from Control Panel/Programs And Features.
    * I'm deleting all the keys related with Sql Server from Regedit.
    * Later i'm restarting windows, and trying to install again. But during the install it gives the error "Database
    Engine Services Failed", install is finishing but when i opened the Management Studio i cannot connect to Database Engine with Sa naturally.
    * My firewall is already closed. And i have not any antivirus software.
    * I gave the permission for port 1433 on firewall.
    Please help me. Why i always take "Database Engine Services Failed" error? I will get crazy cause of that for many days.

    Here's the ERRORLOG file which i found under the folder;
    Microsoft SQL Server/MSSQL10_50.MSSQLSERVER/MSSQL/Log.
    2014-09-27 03:39:40.15 Server      Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (X64) 
    Apr  2 2010 15:48:46 
    Copyright (c) Microsoft Corporation
    Developer Edition (64-bit) on Windows NT 6.2 <X64> (Build 9200: )
    2014-09-27 03:39:40.15 Server      (c) Microsoft Corporation.
    2014-09-27 03:39:40.15 Server      All rights reserved.
    2014-09-27 03:39:40.15 Server      Server process ID is 5768.
    2014-09-27 03:39:40.15 Server      System Manufacturer: 'SAMSUNG ELECTRONICS CO., LTD.', System Model: '350V5C/350V5X/350V4C/350V4X/351V5C/351V5X/351V4C/351V4X/3540VC/3540VX/3440VC/3440VX'.
    2014-09-27 03:39:40.15 Server      Authentication mode is MIXED.
    2014-09-27 03:39:40.15 Server      Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
    2014-09-27 03:39:40.15 Server      Registry startup parameters: 
    -d C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\master.mdf
    -e C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG
    -l C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
    2014-09-27 03:39:40.15 Server      Command Line Startup Parameters:
    -m SqlSetup
    -f
    -Q
    -q Turkish_CI_AS
    -T 4022
    -T 4010
    -T 3659
    -T 3610
    2014-09-27 03:39:40.18 Server      Warning: The server instance was started using minimal configuration startup option (-f). Starting an instance of SQL Server with minimal configuration places the server in single-user mode automatically.  After
    the server has been started with minimal configuration, you should change the appropriate server option value or values, stop, and then restart the server.
    2014-09-27 03:39:40.18 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
    2014-09-27 03:39:40.18 Server      Detected 4 CPUs. This is an informational message; no user action is required.
    2014-09-27 03:39:40.31 Server      Perfmon counters for resource governor pools and groups failed to initialize and are disabled.
    2014-09-27 03:39:40.32 Server      Using dynamic lock allocation.  Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.  This is an informational message only.  No user action is required.
    2014-09-27 03:39:40.43 Server      Node configuration: node 0: CPU mask: 0x000000000000000f:0 Active CPU mask: 0x000000000000000f:0. This message provides a description of the NUMA configuration for this computer. This is an informational message
    only. No user action is required.
    2014-09-27 03:39:40.45 Server      Support for distributed transactions was not enabled for this instance of the Database Engine because it was started using the minimal configuration option. This is an informational message only. No user action
    is required.
    2014-09-27 03:39:40.45 spid7s      Warning ******************
    2014-09-27 03:39:40.45 spid7s      SQL Server started in single-user mode. This an informational message only. No user action is required.
    2014-09-27 03:39:40.46 spid7s      Starting up database 'master'.
    2014-09-27 03:39:40.52 spid7s      Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
    2014-09-27 03:39:40.58 spid7s      SQL Server was started using the -f flag. SQL Server Audit is disabled. This is an informational message. No user action is required.
    2014-09-27 03:39:40.59 spid7s      FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
    2014-09-27 03:39:40.59 spid7s      Server started with '-f' option. Auditing will not be started. This is an informational message only; no user action is required.
    2014-09-27 03:39:40.59 spid7s      Starting up database 'mssqlsystemresource'.
    2014-09-27 03:39:40.61 spid7s      The resource database build version is 10.50.1600. This is an informational message only. No user action is required.
    2014-09-27 03:39:40.94 spid7s      Password policy update was successful.
    2014-09-27 03:39:40.94 spid8s      Starting up database 'model'.
    2014-09-27 03:39:40.95 spid7s      Server name is 'CAGATAY'. This is an informational message only. No user action is required.
    2014-09-27 03:39:41.21 spid8s      Clearing tempdb database.
    2014-09-27 03:39:41.21 spid10s     A new instance of the full-text filter daemon host process has been successfully started.
    2014-09-27 03:39:41.24 Server      A self-generated certificate was successfully loaded for encryption.
    2014-09-27 03:39:41.24 Server      Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
    2014-09-27 03:39:41.24 Server      Dedicated administrator connection support was not started because it is disabled on this edition of SQL Server. If you want to use a dedicated administrator connection, restart SQL Server using the trace flag
    7806. This is an informational message only. No user action is required.
    2014-09-27 03:39:41.28 Server      The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x54b, state: 3. Failure to register an SPN may cause integrated authentication
    to fall back to NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies.
    2014-09-27 03:39:41.28 Server      SQL Server is now ready for client connections. This is an informational message; no user action is required.
    2014-09-27 03:39:41.70 spid8s      Starting up database 'tempdb'.
    2014-09-27 03:39:41.86 spid7s      Warning ******************
    2014-09-27 03:39:41.86 spid7s      Attempting to change default collation to Turkish_CI_AS.
    2014-09-27 03:39:41.92 spid7s       index restored for master.syspriorities.
    2014-09-27 03:39:41.95 spid7s       index restored for master.sysbrickfiles.
    2014-09-27 03:39:41.96 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:41.96 spid7s       index restored for master.sysowners.
    2014-09-27 03:39:42.13 spid7s       index restored for master.sysdbreg.
    2014-09-27 03:39:42.16 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.16 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.16 spid7s       index restored for master.sysschobjs.
    2014-09-27 03:39:42.17 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.17 spid7s       index restored for master.syscolpars.
    2014-09-27 03:39:42.17 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.18 spid7s       index restored for master.sysxlgns.
    2014-09-27 03:39:42.18 spid7s       index restored for master.sysxsrvs.
    2014-09-27 03:39:42.18 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.18 spid7s       index restored for master.sysnsobjs.
    2014-09-27 03:39:42.18 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.18 spid7s       index restored for master.syscerts.
    2014-09-27 03:39:42.19 spid7s       index restored for master.sysrmtlgns.
    2014-09-27 03:39:42.19 spid7s       index restored for master.sysxprops.
    2014-09-27 03:39:42.19 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.19 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.31 spid7s       index restored for master.sysscalartypes.
    2014-09-27 03:39:42.31 spid7s       index restored for master.sysidxstats.
    2014-09-27 03:39:42.31 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.32 spid7s       index restored for master.sysendpts.
    2014-09-27 03:39:42.32 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.32 spid7s       index restored for master.sysclsobjs.
    2014-09-27 03:39:42.32 spid7s       index restored for master.sysremsvcbinds.
    2014-09-27 03:39:42.32 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.32 spid7s       index restored for master.sysrts.
    2014-09-27 03:39:42.33 spid7s       index restored for master.sysasymkeys.
    2014-09-27 03:39:42.33 spid7s       index restored for master.syssqlguides.
    2014-09-27 03:39:42.44 spid7s       index restored for master.syssoftobjrefs.
    2014-09-27 03:39:42.47 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.48 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.49 spid7s       index restored for master.spt_values.
    2014-09-27 03:39:42.49 spid7s       index restored for master.MSreplication_options.
    2014-09-27 03:39:42.56 spid7s       index restored for tempdb.syspriorities.
    2014-09-27 03:39:42.56 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.57 spid7s       index restored for tempdb.sysowners.
    2014-09-27 03:39:42.57 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.57 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.57 spid7s       index restored for tempdb.sysschobjs.
    2014-09-27 03:39:42.57 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.59 spid7s       index restored for tempdb.syscolpars.
    2014-09-27 03:39:42.60 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.60 spid7s       index restored for tempdb.sysnsobjs.
    2014-09-27 03:39:42.60 spid7s       index restored for tempdb.syscerts.
    2014-09-27 03:39:42.60 spid7s       index restored for tempdb.sysxprops.
    2014-09-27 03:39:42.60 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.60 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.60 spid7s       index restored for tempdb.sysscalartypes.
    2014-09-27 03:39:42.61 spid7s       index restored for tempdb.sysidxstats.
    2014-09-27 03:39:42.61 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.61 spid7s       index restored for tempdb.sysclsobjs.
    2014-09-27 03:39:42.61 spid7s       index restored for tempdb.sysremsvcbinds.
    2014-09-27 03:39:42.61 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.61 spid7s       index restored for tempdb.sysrts.
    2014-09-27 03:39:42.62 spid7s       index restored for tempdb.sysasymkeys.
    2014-09-27 03:39:42.69 spid7s       index restored for tempdb.syssqlguides.
    2014-09-27 03:39:42.69 spid7s       index restored for tempdb.syssoftobjrefs.
    2014-09-27 03:39:42.75 spid7s       index restored for model.syspriorities.
    2014-09-27 03:39:42.75 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.75 spid7s       index restored for model.sysowners.
    2014-09-27 03:39:42.76 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.76 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.76 spid7s       index restored for model.sysschobjs.
    2014-09-27 03:39:42.76 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:43.00 spid7s       index restored for model.syscolpars.
    2014-09-27 03:39:43.00 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:43.00 spid7s       index restored for model.sysnsobjs.
    2014-09-27 03:39:43.00 spid7s       index restored for model.syscerts.
    2014-09-27 03:39:43.00 spid7s       index restored for model.sysxprops.
    2014-09-27 03:39:43.00 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:43.00 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:43.00 spid7s       index restored for model.sysscalartypes.
    2014-09-27 03:39:43.00 spid7s       index restored for model.sysidxstats.
    2014-09-27 03:39:43.01 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:43.01 spid7s       index restored for model.sysclsobjs.
    2014-09-27 03:39:43.01 spid7s       index restored for model.sysremsvcbinds.
    2014-09-27 03:39:43.01 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:43.01 spid7s       index restored for model.sysrts.
    2014-09-27 03:39:43.01 spid7s       index restored for model.sysasymkeys.
    2014-09-27 03:39:43.01 spid7s       index restored for model.syssqlguides.
    2014-09-27 03:39:43.01 spid7s       index restored for model.syssoftobjrefs.
    2014-09-27 03:39:43.02 spid7s      Starting up database 'msdb'.
    2014-09-27 03:39:43.82 spid7s       index restored for msdb.syspriorities.
    2014-09-27 03:39:43.85 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:43.93 spid7s       index restored for msdb.sysowners.
    2014-09-27 03:39:43.99 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.00 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.09 spid7s       index restored for msdb.sysschobjs.
    2014-09-27 03:39:44.12 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.20 spid7s       index restored for msdb.syscolpars.
    2014-09-27 03:39:44.20 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.20 spid7s       index restored for msdb.sysnsobjs.
    2014-09-27 03:39:44.20 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.25 spid7s       index restored for msdb.syscerts.
    2014-09-27 03:39:44.25 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.26 spid7s       index restored for msdb.sysxprops.
    2014-09-27 03:39:44.26 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.26 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.27 spid7s       index restored for msdb.sysscalartypes.
    2014-09-27 03:39:44.37 spid7s       index restored for msdb.sysidxstats.
    2014-09-27 03:39:44.41 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.42 spid7s       index restored for msdb.sysclsobjs.
    2014-09-27 03:39:44.42 spid7s       index restored for msdb.sysremsvcbinds.
    2014-09-27 03:39:44.42 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.42 spid7s       index restored for msdb.sysrts.
    2014-09-27 03:39:44.54 spid7s       index restored for msdb.sysasymkeys.
    2014-09-27 03:39:44.54 spid7s       index restored for msdb.syssqlguides.
    2014-09-27 03:39:44.59 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.74 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.85 spid7s       index restored for msdb.syssoftobjrefs.
    2014-09-27 03:39:44.89 spid7s       index restored for msdb.syspolicy_policies_internal.
    2014-09-27 03:39:44.90 spid7s       index restored for msdb.sysproxies.
    2014-09-27 03:39:44.90 spid7s       index restored for msdb.syscollector_execution_stats_internal.
    2014-09-27 03:39:44.90 spid7s       index restored for msdb.syssubsystems.
    2014-09-27 03:39:44.91 spid7s       index restored for msdb.log_shipping_primary_secondaries.
    2014-09-27 03:39:44.91 spid7s       index restored for msdb.sysdownloadlist.
    2014-09-27 03:39:44.91 spid7s       index restored for msdb.log_shipping_monitor_primary.
    2014-09-27 03:39:44.92 spid7s       index restored for msdb.sysoriginatingservers.
    2014-09-27 03:39:44.93 spid7s       index restored for msdb.log_shipping_monitor_history_detail.
    2014-09-27 03:39:44.95 spid7s       index restored for msdb.log_shipping_monitor_error_detail.
    2014-09-27 03:39:44.95 spid7s       index restored for msdb.log_shipping_secondary.
    2014-09-27 03:39:44.97 spid7s       index restored for msdb.log_shipping_secondary_databases.
    2014-09-27 03:39:45.10 spid7s       index restored for msdb.log_shipping_monitor_secondary.
    2014-09-27 03:39:45.10 spid7s       index restored for msdb.sysjobs.
    2014-09-27 03:39:45.10 spid7s       index restored for msdb.sysutility_ucp_mi_file_space_health_internal.
    2014-09-27 03:39:45.10 spid7s       index restored for msdb.sysutility_ucp_mi_database_health_internal.
    2014-09-27 03:39:45.10 spid7s       index restored for msdb.syscollector_blobs_internal.
    2014-09-27 03:39:45.11 spid7s       index restored for msdb.sysutility_mi_dac_execution_statistics_internal.
    2014-09-27 03:39:45.11 spid7s       index restored for msdb.sysjobsteps.
    2014-09-27 03:39:45.11 spid7s       index restored for msdb.sysutility_ucp_dac_file_space_health_internal.
    2014-09-27 03:39:45.11 spid7s       index restored for msdb.logmarkhistory.
    2014-09-27 03:39:45.11 spid7s       index restored for msdb.sysutility_mi_session_statistics_internal.
    2014-09-27 03:39:45.12 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.12 spid7s       index restored for msdb.sysdtscategories.
    2014-09-27 03:39:45.33 spid7s       index restored for msdb.syspolicy_target_sets_internal.
    2014-09-27 03:39:45.33 spid7s       index restored for msdb.sysutility_ucp_mi_volume_space_health_internal.
    2014-09-27 03:39:45.33 spid7s       index restored for msdb.sysschedules.
    2014-09-27 03:39:45.33 spid7s       index restored for msdb.sysdac_instances_internal.
    2014-09-27 03:39:45.33 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.50 spid7s       index restored for msdb.sysssispackages.
    2014-09-27 03:39:45.51 spid7s       index restored for msdb.sysutility_ucp_computer_cpu_health_internal.
    2014-09-27 03:39:45.51 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.52 spid7s       index restored for msdb.sysssispackagefolders.
    2014-09-27 03:39:45.52 spid7s       index restored for msdb.sysdac_history_internal.
    2014-09-27 03:39:45.53 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.62 spid7s       index restored for msdb.syscategories.
    2014-09-27 03:39:45.62 spid7s       index restored for msdb.systargetservers.
    2014-09-27 03:39:45.62 spid7s       index restored for msdb.systargetservergroups.
    2014-09-27 03:39:45.62 spid7s       index restored for msdb.syspolicy_policy_category_subscriptions_internal.
    2014-09-27 03:39:45.62 spid7s       index restored for msdb.sysalerts.
    2014-09-27 03:39:45.62 spid7s       index restored for msdb.sysoperators.
    2014-09-27 03:39:45.63 spid7s       index restored for msdb.syspolicy_system_health_state_internal.
    2014-09-27 03:39:45.63 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.63 spid7s       index restored for msdb.syscollector_config_store_internal.
    2014-09-27 03:39:45.65 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.65 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.65 spid7s       index restored for msdb.sysmanagement_shared_server_groups_internal.
    2014-09-27 03:39:45.66 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.66 spid7s       index restored for msdb.sysutility_mi_smo_properties_to_collect_internal.
    2014-09-27 03:39:45.66 spid7s       index restored for msdb.sysmanagement_shared_registered_servers_internal.
    2014-09-27 03:39:45.66 spid7s       index restored for msdb.syscachedcredentials.
    2014-09-27 03:39:45.79 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.79 spid7s       index restored for msdb.syscollector_collection_sets_internal.
    2014-09-27 03:39:45.79 spid7s       index restored for msdb.sysutility_ucp_dac_health_internal.
    2014-09-27 03:39:45.80 spid7s       index restored for msdb.MSdbms.
    2014-09-27 03:39:45.80 spid7s       index restored for msdb.MSdbms_datatype.
    2014-09-27 03:39:45.80 spid7s       index restored for msdb.sysmail_profile.
    2014-09-27 03:39:45.80 spid7s       index restored for msdb.sysutility_ucp_managed_instances_internal.
    2014-09-27 03:39:45.83 spid7s       index restored for msdb.syspolicy_management_facets.
    2014-09-27 03:39:45.84 spid7s       index restored for msdb.sysutility_ucp_mi_health_internal.
    2014-09-27 03:39:45.86 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.86 spid7s       index restored for msdb.syscollector_collector_types_internal.
    2014-09-27 03:39:45.86 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.86 spid7s       index restored for msdb.syspolicy_configuration_internal.
    2014-09-27 03:39:45.87 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.87 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.87 spid7s       index restored for msdb.syspolicy_facet_events.
    2014-09-27 03:39:45.87 spid7s       index restored for msdb.sysmail_account.
    2014-09-27 03:39:45.87 spid7s       index restored for msdb.syspolicy_conditions_internal.
    2014-09-27 03:39:45.88 spid7s       index restored for msdb.sysutility_ucp_health_policies_internal.
    2014-09-27 03:39:45.88 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.88 spid7s       index restored for msdb.syscollector_collection_items_internal.
    2014-09-27 03:39:45.90 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:46.00 spid7s       index restored for msdb.sysmail_servertype.
    2014-09-27 03:39:46.00 spid7s       index restored for msdb.sysutility_ucp_filegroups_with_policy_violations_internal.
    2014-09-27 03:39:46.02 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:46.03 spid7s       index restored for msdb.sysutility_ucp_policy_check_conditions_internal.
    2014-09-27 03:39:46.03 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:46.03 spid7s       index restored for msdb.sysutility_ucp_configuration_internal.
    2014-09-27 03:39:46.03 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:46.03 spid7s       index restored for msdb.sysutility_ucp_policy_target_conditions_internal.
    2014-09-27 03:39:46.04 spid7s       index restored for msdb.sysmail_server.
    2014-09-27 03:39:46.04 spid7s       index restored for msdb.syspolicy_policy_categories_internal.
    2014-09-27 03:39:46.04 spid7s       index restored for msdb.syspolicy_object_sets_internal.
    2014-09-27 03:39:46.04 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:46.05 spid7s       index restored for msdb.sysmail_configuration.
    2014-09-27 03:39:46.05 spid7s       index restored for msdb.sysdbmaintplan_databases.
    2014-09-27 03:39:46.05 spid7s       index restored for msdb.log_shipping_primary_databases.
    2014-09-27 03:39:46.39 spid7s      The default collation was successfully changed.
    2014-09-27 03:39:46.39 spid7s      Recovery is complete. This is an informational message only. No user action is required.
    2014-09-27 03:39:47.17 spid51      Changed database context to 'master'.
    2014-09-27 03:39:47.18 spid51      Changed language setting to us_english.
    2014-09-27 03:39:47.72 spid51      Setting database option RECOVERY to FULL for database model.
    2014-09-27 03:39:47.84 spid51      Configuration option 'show advanced options' changed from 0 to 1. Run the RECONFIGURE statement to install.
    2014-09-27 03:39:47.84 spid51      FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
    2014-09-27 03:39:47.98 spid51      Configuration option 'default language' changed from 0 to 0. Run the RECONFIGURE statement to install.
    2014-09-27 03:39:47.98 spid51      Configuration option 'default full-text language' changed from 1033 to 1033. Run the RECONFIGURE statement to install.
    2014-09-27 03:39:47.98 spid51      FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
    2014-09-27 03:39:47.98 spid51      Configuration option 'show advanced options' changed from 1 to 0. Run the RECONFIGURE statement to install.
    2014-09-27 03:39:47.98 spid51      FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
    2014-09-27 03:39:48.27 spid51      Error: 15007, Severity: 16, State: 1.
    2014-09-27 03:39:48.27 spid51      '' is not a valid login or you do not have permission.
    2014-09-27 03:51:25.13 Logon       Error: 18456, Severity: 14, State: 8.
    2014-09-27 03:51:25.13 Logon       Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]
    2014-09-27 03:51:32.67 Logon       Error: 18456, Severity: 14, State: 8.
    2014-09-27 03:51:32.67 Logon       Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]
    2014-09-27 03:51:42.11 Logon       Error: 18456, Severity: 14, State: 5.
    2014-09-27 03:51:42.11 Logon       Login failed for user 'CAGATAY\cagatay (cagatay)'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
    2014-09-27 03:52:42.07 Logon       Error: 18456, Severity: 14, State: 5.
    2014-09-27 03:52:42.07 Logon       Login failed for user 'CAGATAY\cagatay (cagatay)'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
    2014-09-27 03:53:01.23 Logon       Error: 18461, Severity: 14, State: 1.
    2014-09-27 03:53:01.23 Logon       Login failed for user 'CAGATAY\cagatay'. Reason: Server is in single user mode. Only one administrator can connect at this time. [CLIENT: <local machine>]
    2014-09-27 03:53:17.57 Logon       Error: 18456, Severity: 14, State: 8.
    2014-09-27 03:53:17.57 Logon       Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]
    2014-09-27 03:53:32.54 Logon       Error: 18456, Severity: 14, State: 5.
    2014-09-27 03:53:32.54 Logon       Login failed for user 'CAGATAY\cagatay (cagatay)'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
    2014-09-27 03:54:04.29 Logon       Error: 18456, Severity: 14, State: 5.
    2014-09-27 03:54:04.29 Logon       Login failed for user 'CAGATAY\cagatay (cagatay)'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
    2014-09-27 03:54:10.36 Logon       Error: 18456, Severity: 14, State: 5.
    2014-09-27 03:54:10.36 Logon       Login failed for user 'CAGATAY\cagatay'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
    2014-09-27 03:54:47.18 Logon       Error: 18456, Severity: 14, State: 8.
    2014-09-27 03:54:47.18 Logon       Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]
    Resolve the error, please refer to the following links.
    Enable DAC:http://www.mssqltips.com/sqlservertip/2538/enabling-dedicated-administrator-connection-in-sql-server-2008-express-edition/
    could not register the SPN Kerberos:
    http://saveadba.blogspot.com/2012/03/could-not-register-spn-kerberos.html  
    Make sure the password of sa is correct,and the login 'CAGATAY\cagatay' has been created in SQL Server

  • Be our December TechNet SSIS Guru. Give the gift of code!

    It's that time of the year again!
    It's Giving time!
    A time to think of those less awesome than you.
    A time to give something back to the community.
    Think of those happy faces you will make, as they open that article!
    Remember, "A TechNet Wiki article is not just for Christmas, it's for eternity"!!!
    A TechNet article is the gift that keeps on giving!
    If you have some spare over this upcoming festive month, please give the gift of code.
    So please wrap up some code with plenty of explanation and pop it under our TechNet tree!
    All you have to do is add an article to TechNet Wiki from your own specialist field. Something that fits into one of the categories listed on the submissions page. Copy in your own blog posts, a forum solution, a white
    paper, or just something you had to solve for your own day's work today.
    Drop us some nifty knowledge, or superb snippets, and become MICROSOFT TECHNOLOGY GURU OF THE MONTH!
    This is an official Microsoft TechNet recognition, where people such as yourselves can truly get noticed!
    HOW TO WIN
    1) Please copy over your Microsoft technical solutions and revelations to
    TechNet Wiki.
    2) Add a link to it on
    THIS WIKI COMPETITION PAGE (so we know you've contributed)
    3) Every month, we will highlight your contributions, and select a "Guru of the Month" in each technology.
    If you win, we will sing your praises in blogs and forums, similar to the
    weekly contributor awards. Once "on our radar" and making your mark, you will probably be
    interviewed for your greatness, and maybe eventually even invited into other inner TechNet/MSDN circles!
    Winning this award in your favoured technology will help us learn the active members in each community.
    Feel free to ask any questions below.
    More about TechNet Guru Awards
    Thanks in advance!
    Pete Laker
    #PEJL
    Got any nice code? If you invest time in coding an elegant, novel or impressive answer on MSDN forums, why not copy it over to the one and only
    TechNet Wiki, for future generations to benefit from! You'll never get archived again!
    If you are a member of any user groups, please make sure you list them in the
    Microsoft User Groups Portal. Microsoft are trying to help promote your groups, and collating them here is the first step.

    I have added an SSIS WIKI, but the code format is removed when saving the WIKI (IE11), which makes it unreadable.
    http://social.technet.microsoft.com/wiki/contents/articles/21978.execute-ssis-2012-package-with-parameters-via-net.aspx
    C# code
    // Connection to the database server where the packages are located
    SqlConnection ssisConnection = new SqlConnection(@"Data Source=.\SQL2012;Initial Catalog=master;Integrated Security=SSPI;");
    // SSIS server object with connection
    IntegrationServices ssisServer = new IntegrationServices(ssisConnection);
    // The reference to the package which you want to execute
    PackageInfo ssisPackage = ssisServer.Catalogs["SSISDB"].Folders["SSISJOOST"].Projects["MyProject"].Packages["MyPackage.dtsx"];
    // Add a parameter collection for 'system' paramers (ObjectType = 50), package parameters (ObjectType = 30) and project parameters (ObjectType = 20)
    Collection<PackageInfo.ExecutionValueParameterSet> executionParameter = new Collection<PackageInfo.ExecutionValueParameterSet>();
    // Add execution parameter (value) to override the default asynchronized execution. If you leave this out the package is executed asynchronized
    executionParameter.Add(new PackageInfo.ExecutionValueParameterSet { ObjectType = 50, ParameterName = "SYNCHRONIZED", ParameterValue = 1 });
    // Add execution parameter (value) to override the default logging level (0=None, 1=Basic, 2=Performance, 3=Verbose)
    executionParameter.Add(new PackageInfo.ExecutionValueParameterSet { ObjectType = 50, ParameterName = "LOGGING_LEVEL", ParameterValue = 3 });
    // Add a project parameter (value) to fill a project parameter
    executionParameter.Add(new PackageInfo.ExecutionValueParameterSet { ObjectType = 20, ParameterName = "MyProjectParameter", ParameterValue = "some value" });
    // Add a project package (value) to fill a package parameter
    executionParameter.Add(new PackageInfo.ExecutionValueParameterSet { ObjectType = 30, ParameterName = "MyPackageParameter", ParameterValue = "some value" });
    // Get the identifier of the execution to get the log
    long executionIdentifier = ssisPackage.Execute(false, null, executionParameter);
    // Loop through the log and do something with it like adding to a listbox
    foreach (OperationMessage message in ssisServer.Catalogs["SSISDB"].Executions[executionIdentifier].Messages)
    SSISMessagesListBox.Items.Add(message.MessageType.ToString() + ": " + message.Message);
    VB.Net code
    ' Connection to the database server where the packages are located
    Dim ssisConnection As New SqlConnection("Data Source=.\SQL2012;Initial Catalog=master;Integrated Security=SSPI;")
    ' SSIS server object with connection
    Dim ssisServer As New IntegrationServices(ssisConnection)
    ' The reference to the package which you want to execute
    Dim ssisPackage As PackageInfo = ssisServer.Catalogs("SSISDB").Folders("SSISJOOST").Projects("MyProject").Packages("MyPackage.dtsx")
    ' Add a parameter collection for 'system' paramers (ObjectType = 50), package parameters (ObjectType = 30) and project parameters (ObjectType = 20)
    Dim executionParameters As New Collection(Of PackageInfo.ExecutionValueParameterSet)
    ' Add execution parameter to override the default asynchronized execution. If you leave this out the package is executed asynchronized
    Dim executionParameter1 As New PackageInfo.ExecutionValueParameterSet
    executionParameter1.ObjectType = 50
    executionParameter1.ParameterName = "SYNCHRONIZED"
    executionParameter1.ParameterValue = 1
    executionParameters.Add(executionParameter1)
    ' Add execution parameter (value) to override the default logging level (0=None, 1=Basic, 2=Performance, 3=Verbose)
    Dim executionParameter2 As New PackageInfo.ExecutionValueParameterSet
    executionParameter2.ObjectType = 50
    executionParameter2.ParameterName = "LOGGING_LEVEL"
    executionParameter2.ParameterValue = 3
    executionParameters.Add(executionParameter2)
    ' Add a project parameter (value) to fill a project parameter
    Dim executionParameter3 As New PackageInfo.ExecutionValueParameterSet
    executionParameter3.ObjectType = 20
    executionParameter3.ParameterName = "MyProjectParameter"
    executionParameter3.ParameterValue = "some value1"
    executionParameters.Add(executionParameter3)
    ' Add a project package (value) to fill a package parameter
    Dim executionParameter4 As New PackageInfo.ExecutionValueParameterSet
    executionParameter4.ObjectType = 30
    executionParameter4.ParameterName = "MyPackageParameter"
    executionParameter4.ParameterValue = "some value2"
    executionParameters.Add(executionParameter4)
    ' Get the identifier of the execution to get the log
    Dim executionIdentifier As Long = ssisPackage.Execute(False, Nothing, executionParameters)
    ' Loop through the log and do something with it like adding to a listbox
    For Each message As OperationMessage In ssisServer.Catalogs("SSISDB").Executions(executionIdentifier).Messages
    SSISMessagesListBox.Items.Add(message.MessageType.ToString() + ": " + message.Message)
    Next
    Please mark the post as answered if it answers your question | My SSIS Blog:
    http://microsoft-ssis.blogspot.com |
    Twitter

Maybe you are looking for

  • Itunes wont load!!!

    when i click on itunes the license agreement thing pops up nd then go es away. i did the msconfig thing nd itunes started working but then internet explorer stopped working. i did system restore nd now everything is back to the way when itunes didnt

  • Drop shadow on img missing

    Hi! I want a drop shadow on my images. I have created this div to do that: .shadow{ box-shadow: 5px 5px 3px rgba(65, 65, 65, 0.5); Then I added the div class to my images. But it doesn't work on the images already inside a div tag. E.g. my two pictur

  • How to do reverse engineering to a sybase model?

    Hi, I´m new with sybase ase technology and i don´t now how to create a sybase model in ODI. I´m alredy created the data server and logical schema in topology manager but when i try to do the reverse engineering on designer module i can´t see the tabl

  • Can I use hotmail with the Mail app?

    I looked at the mail app, but didn't see hotmail in there. Can I use it on the touch after upgrading?

  • Regarding the SAP Business objects Server configuration

    Hi Experts , I was newly entered in to SAP Business Objects .Kindly i am requesting can you please let me know the follwing details . 1) Latest server configuration of the SAP Business Objects . 2) Latest version of the Crystal reporting / Desktop In