"A severe error occurred on the current command. The results, if any, should be discarded." + Full-text-index Sql Server 2008 R2 SP1

Hello.
I have a problem with SQL Server 2008 R2 SP1:
I have a table with the full-text index-activated on 3 fields of type nvarchar.
When I try to open a transaction (ex: BEGIN TRAN {inserts} COMMIT) to insert multiple rows, I get the following error: "A severe error occurred on the current command ...".
I checked the Sql Server Logs and the Event Viewer on the machine, but nothing was logged.
I found a workaround: disable full-text-index => Do stuff => enable  full-text-index, but this is very annoying (especially when i use the Data Compare to update that table on the Development Environment).
Help!!!

I concur with Tom. Upgrade to SP3. This may resolve the issue.
Since you say that there is nothing in the SQL Server errorlog, this may be an API issue. Try running the same commands through the command-line tools SQLCMD or OSQL to see how this turns out.
Erland Sommarskog, SQL Server MVP, [email protected]

Similar Messages

  • MS SQL server is going down frequently(10 days of gap) with exception message: "A severe error occurred on the current command. The results, if any, should be discarded".

    MS SQL server is going down frequently(10 days of gap) with exception message: "A severe error occurred
    on the current command. The results, if any, should be discarded". We are facing this issue for past two month.But funny thing is server will be up automatically with out any service restart manually.  Also if we try to restart the SQL
    server service manually then SQL server will be in a dead lock situation and it will not come up even if we wait for long time. Then we should do a windows server machine restart to
    make the SQL sever up. As a suggestion from Microsoft to fix this kind of similar issue,
    we have installed service pack 3 for SQL Server. But even after we are facing same issue.
    Server Details:
    Server OS: Windows Server 2008 R2
    Two type of database servers are installed on server:
    1. MS SQL Server 2008 R2
    2. My SQL
    Also Reporting server is configured for the purpose of generating SSRS report from a dot net website.
     NOTE:Immediately after the data retrieval/save, we are closing the connection explicitly by the
    application.
    we have checked the windows event log and below are the details:
    Log Name:      Application
    Source:        ASP.NET 4.0.30319.0
    Application information:
        Application domain: /LM/W3SVC/5/ROOT-1-130718142067856406
        Trust level: Full
        Application Virtual Path: /
        Application Path: E:\WebSpaceFolder\ACSQuiK\Production\
        Machine name: DBSERVER 
     Process information:
        Process ID: 148
        Process name: w3wp.exe
        Account name: NT AUTHORITY\NETWORK SERVICE 
     Exception information:
        Exception type: SqlException
        Exception message: A severe error occurred on the current command.  The results, if any, should be discarded.
       at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
       at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
       at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
    Log Name:      Application
    Source:        Report Server Windows Service (MSSQLSERVER)
    Description:
    Report Server Windows Service (MSSQLSERVER) cannot connect to the report server database.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Report Server Windows Service (MSSQLSERVER)" />
        <EventID Qualifiers="0">107</EventID>
    Could anybody can suggest any kind of fix for this issue? Thanks in advance.

    Hi YesYemPee,
    I have tried but still not clear about your issue, I would like you provide more details information about your issue based on below points to better analysis about the issue:
    What action did you do and caused the error "A severe error occurred on the current command. The results, if any, should be discarded", did you run report on the web application or something else then the error happen?
    If you rendering the report and got the error, please try to provide us more error information in the log files which path like:
    C:\Program Files\Microsoft SQL Server\MSRS10_50.MSSQLSERVER\Reporting Services\LogFiles
    If it is not the case in step1, Please try to provide SQL Server Error log(SQL Server Logs) and more details information.
    If you still have any problem, please feel free to ask.
    Regards,
    Vicky Liu
    Vicky Liu
    TechNet Community Support

  • A severe error occurred on the current command. The results, if any, should be discarded(Not Always)

    We have a DotNet website which is deployed on a physical server(windows server 2008 r2). The application is started to using for live. Most of the time application is  working fine. But some times we have noticed the application is failed to communicate
    with MS SQL 2008 R2 database and as result the below error is displaying:
    "A severe error occurred on the current command. The results, if any, should be discarded. at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject
    stateObj, Boolean callerHasConnectionLock, Boolean asyncClose) at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean&
    dataReady) at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) at System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean
    enlistOK) "
    If we tried to connect the database server the same issue is showing:"A severe error occurred on the current command. The results, if any, should be discarded"
    The issue will be resolved automatically after 30-45 minutes .   Please let us know if any fixes can be done to resolve this issue.
    NOTE: We have installed SQL Server 2008 service pack 3 as per the suggestion from experts .But still the issue pwersist.

    Hello,
    When this issue occurs have you check the existing connections? If an app was unclean developed it can happen that the app opens connection by connection, but never closed them correctly and when all available connections are in use, such an error can occur.
    Olaf Helper
    [ Blog] [ Xing] [ MVP]

  • A severe error occurred on the current command. The results, if any, should be discarded.

    I have a strange situation on a database, which are on SQL Server 2008 R2 Express SP2. The database size is something around 90 MB.
    When a user try to insert a record inside one table, he receive an error message,  and the program is disconnected from the database. I tried to investigate this issue, and I discovered that when user try to insert one row  the trigger for
    insert invoke also the trigger for update and sql server crushes with "A severe error occurred on the current command.  The results, if any, should be discarded."
    I have checked from SQL Server Management Studio to run a direct Update on the specific table. The same error occurred.
    I have run DBCC CheckTable and no errors have been found. I also have run DBCC CHECKDB and no errors.
    Because I also have 3 other different databases, with the same functionality, on the same server which are going well with more than 100 000 records in that specific table, and the triggers are going well for more than 5 years, I have assumed that some
    problems occurs inside the database. That is why I have copied all the records from the "damage" database to a new one. This means that inside the new databases the indexes are regenerated and a new space will be allocated.
    The same strange things are happening. The same table can not be updated with a very basic Update statement.
    I am looking for a patch or KB to solve this issues.
    Any ideas are will be appreciated.
    Thank you

    there is a file as response to one of my tests to investigate which command is responsible for this error. 
    Current time is 21:18:39 08/18/13.                                                                              
    =====================================================================                                           
           BugCheck Dump                                                                                            
    =====================================================================                                           
    This file is generated by Microsoft SQL Server                                                                  
    version 10.50.4000.0                                                                                            
    upon detection of fatal unexpected error. Please return this file,                                              
    the query or program that produced the bugcheck, the database and                                               
    the error log, and any other pertinent information with a Service Request.                                      
    Computer type is Intel(R) Core(TM) i7 CPU         860  @ 2.80GHz.                                               
    Bios Version is INTEL  - 1072009                                                                                
    BIOS Date: 09/23/09 11:58:43 Ver: 08.00.10                                                                      
    8 X64 level 8664, 2 Mhz processor (s).                                                                          
    Windows NT 6.1 Build 7601 CSD Service Pack 1.                                                                   
    Memory                              
    MemoryLoad = 16%                    
    Total Physical = 8125 MB            
    Available Physical = 6755 MB        
    Total Page File = 16248 MB          
    Available Page File = 14719 MB      
    Total Virtual = 8388607 MB          
    Available Virtual = 8380163 MB      
    ***Stack Dump being sent to d:\MSSQL10_50.MSSQLSERVER\MSSQL\LOG\SQLDump0084.txt                                 
    SqlDumpExceptionHandler: Process 52 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is
    terminating this process.                                                                                       
    * BEGIN STACK DUMP:                                                                                             
    *   08/18/13 21:18:39 spid 52                                                                                   
    *   Exception Address = 0000000000886B00 Module(sqlservr+00000000001F6B00)                                      
    *   Exception Code    = c0000005 EXCEPTION_ACCESS_VIOLATION                                                     
    *   Access Violation occurred writing address 0000000000000000                                                  
    * Input Buffer 214 bytes -                                                                                      
    *               begin transaction    insert into DocContabile   select *  f                                     
    *  rom gunoiDocContabile      rollback                                                                          
    *  MODULE                          BASE      END       SIZE                                                     
    * sqlservr                       0000000000690000  00000000042A1FFF  03c12000                                   
    * ntdll                          0000000077730000  00000000778D8FFF  001a9000                                   
    * kernel32                       0000000077510000  000000007762EFFF  0011f000                                   
    * KERNELBASE                     000007FEFD6E0000  000007FEFD74AFFF  0006b000                                   
    * ADVAPI32                       000007FEFE090000  000007FEFE16AFFF  000db000                                   
    * msvcrt                         000007FEFE300000  000007FEFE39EFFF  0009f000                                   
    * sechost                        000007FEFF590000  000007FEFF5AEFFF  0001f000                                   
    * RPCRT4                         000007FEFF5B0000  000007FEFF6DCFFF  0012d000                                   
    * MSVCR80                        0000000071710000  00000000717D8FFF  000c9000                                   
    * MSVCP80                        0000000071600000  0000000071708FFF  00109000                                   
    * sqlos                          00000000715F0000  00000000715F6FFF  00007000                                   
    * Secur32                        000007FEFD1E0000  000007FEFD1EAFFF  0000b000                                   
    * SSPICLI                        000007FEFD3B0000  000007FEFD3D4FFF  00025000                                   
    * pdh                            000007FEF90C0000  000007FEF910DFFF  0004e000                                   
    * SHLWAPI                        000007FEFDE50000  000007FEFDEC0FFF  00071000                                   
    * GDI32                          000007FEFE3A0000  000007FEFE406FFF  00067000                                   
    * USER32                         0000000077630000  0000000077729FFF  000fa000                                   
    * LPK                            000007FEFDE40000  000007FEFDE4DFFF  0000e000                                   
    * USP10                          000007FEFF970000  000007FEFFA38FFF  000c9000                                   
    * USERENV                        000007FEFC850000  000007FEFC86DFFF  0001e000                                   
    * profapi                        000007FEFD510000  000007FEFD51EFFF  0000f000                                   
    * WINMM                          000007FEFB320000  000007FEFB35AFFF  0003b000                                   
    * IPHLPAPI                       000007FEFAD70000  000007FEFAD96FFF  00027000                                   
    * NSI                            000007FEFDFB0000  000007FEFDFB7FFF  00008000                                   
    * WINNSI                         000007FEFAD60000  000007FEFAD6AFFF  0000b000                                   
    * opends60                       0000000071590000  0000000071597FFF  00008000                                   
    * NETAPI32                       000007FEFAEB0000  000007FEFAEC5FFF  00016000                                   
    * netutils                       000007FEFAEA0000  000007FEFAEABFFF  0000c000                                   
    * srvcli                         000007FEFD060000  000007FEFD082FFF  00023000                                   
    * wkscli                         000007FEFAE80000  000007FEFAE94FFF  00015000                                   
    * LOGONCLI                       000007FEFCB90000  000007FEFCBBFFFF  00030000                                   
    * SAMCLI                         000007FEFAE60000  000007FEFAE73FFF  00014000                                   
    * BatchParser                    0000000071560000  000000007158CFFF  0002d000                                   
    * IMM32                          000007FEFE060000  000007FEFE08DFFF  0002e000                                   
    * MSCTF                          000007FEFE1F0000  000007FEFE2F8FFF  00109000                                   
    * psapi                          00000000778F0000  00000000778F6FFF  00007000                                   
    * instapi10                      0000000071320000  000000007132CFFF  0000d000                                   
    * cscapi                         000007FEF7FA0000  000007FEF7FAEFFF  0000f000                                   
    * sqlevn70                       0000000071100000  0000000071303FFF  00204000                                   
    * CRYPTSP                        000007FEFCE50000  000007FEFCE66FFF  00017000                                   
    * rsaenh                         000007FEFCA70000  000007FEFCAB6FFF  00047000                                   
    * CRYPTBASE                      000007FEFD440000  000007FEFD44EFFF  0000f000                                   
    * BROWCLI                        000007FEF8B80000  000007FEF8B91FFF  00012000                                   
    * AUTHZ                          000007FEFCF70000  000007FEFCF9EFFF  0002f000                                   
    * MSCOREE                        000007FEF8980000  000007FEF89EEFFF  0006f000                                   
    * ole32                          000007FEFDC30000  000007FEFDE32FFF  00203000                                   
    * credssp                        000007FEFC960000  000007FEFC969FFF  0000a000                                   
    * msv1_0                         000007FEFCD90000  000007FEFCDE0FFF  00051000                                   
    * cryptdll                       000007FEFD090000  000007FEFD0A3FFF  00014000                                   
    * kerberos                       000007FEFCCD0000  000007FEFCD83FFF  000b4000                                   
    * MSASN1                         000007FEFD5B0000  000007FEFD5BEFFF  0000f000                                   
    * schannel                       000007FEFCB00000  000007FEFCB55FFF  00056000                                   
    * CRYPT32                        000007FEFD7D0000  000007FEFD939FFF  0016a000                                   
    * security                       0000000071390000  0000000071392FFF  00003000                                   
    * WS2_32                         000007FEFF360000  000007FEFF3ACFFF  0004d000                                   
    * SHELL32                        000007FEFE5D0000  000007FEFF357FFF  00d88000                                   
    * OLEAUT32                       000007FEFDED0000  000007FEFDFA6FFF  000d7000                                   
    * ncrypt                         000007FEFCF20000  000007FEFCF6CFFF  0004d000                                   
    * bcrypt                         000007FEFCEF0000  000007FEFCF11FFF  00022000                                   
    * mswsock                        000007FEFCDF0000  000007FEFCE44FFF  00055000                                   
    * wship6                         000007FEFCFB0000  000007FEFCFB6FFF  00007000                                   
    * wshtcpip                       000007FEFC720000  000007FEFC726FFF  00007000                                   
    * ntmarta                        000007FEFC620000  000007FEFC64CFFF  0002d000                                   
    * WLDAP32                        000007FEFE410000  000007FEFE461FFF  00052000                                   
    * ntdsapi                        000007FEF7AF0000  000007FEF7B16FFF  00027000                                   
    * bcryptprimitives               000007FEFC9D0000  000007FEFCA1BFFF  0004c000                                   
    * SAMLIB                         000007FEFBE10000  000007FEFBE2CFFF  0001d000                                   
    * CLBCatQ                        000007FEFD960000  000007FEFD9F8FFF  00099000                                   
    * sqlncli10                      0000000063720000  00000000639DCFFF  002bd000                                   
    * VERSION                        000007FEFC650000  000007FEFC65BFFF  0000c000                                   
    * COMCTL32                       000007FEFA110000  000007FEFA1AFFFF  000a0000                                   
    * COMDLG32                       000007FEFDFC0000  000007FEFE056FFF  00097000                                   
    * SQLNCLIR10                     00000000636E0000  0000000063716FFF  00037000                                   
    * netbios                        000007FEF4340000  000007FEF4349FFF  0000a000                                   
    * xpstar                         0000000063650000  00000000636D7FFF  00088000                                   
    * SQLSCM                         0000000063640000  000000006364DFFF  0000e000                                   
    * ODBC32                         000007FEF0AC0000  000007FEF0B70FFF  000b1000                                   
    * ATL80                          0000000063620000  000000006363FFFF  00020000                                   
    * odbcint                        00000000635E0000  0000000063617FFF  00038000                                   
    * clusapi                        000007FEF91B0000  000007FEF91FFFFF  00050000                                   
    * resutils                       000007FEF9190000  000007FEF91A8FFF  00019000                                   
    * xpstar                         00000000635B0000  00000000635D4FFF  00025000                                   
    * dbghelp                        0000000063330000  000000006348DFFF  0015e000                                   
    *     P1Home: 000000000BB6A950:  00000000C0000005  0000000000000000  0000000000886B00  0000000000000002  00000000
    What else should I have to do?
    Thank you,
    Horia

  • A server error occurred on the current command. the results if any should be discarded in SQL 2008 R2

    Hi,
    I am using SQL server 2008 R2 and also MultipleActiveResultSet = true and Pooling = true (default value) in connection string.
    While executing query 'IF ORIGINAL_LOGIN() = SUSER_SNAME() EXECUTE AS USER = 'MyUser'', I received error stating  'A server error occurred on the current command. the results if any should be discarded'. At the same time I could check that SqlConnection
    state is also closed.
    I have also fired 'REVERT' query If I find such exception and again try to execute same query again. but no luck. I received the same exception while executing query (Execute As) again.
    What can be the solution to avoid such exception and make my code working?
    Thanks,
    Ashish

    Login failed for user 'sa'. The user is not associated with a trusted SQL Server connection.
    Above issue occurs genrally when authentication mode is set to Windows Authentication insted Mixed Mode.
    You can change the authentication mode of the SQL server from “Windows Authentication Mode (Windows Authentication)” to “Mixed Mode (Windows Authentication and SQL Server Authentication)”.
    Run following script in SQL Analyzer to change the authentication
    LOGIN sa ENABLE
    GO
    ALTER LOGIN sa WITH PASSWORD = '<password>'
    GO
    http://blog.sqlauthority.com/2007/04/14/sql-server-fix-error-18452-login-failed-for-user-null-the-user-is-not-associated-with-a-trusted-sql-server-connection/
    But as per the first post it seems issue is different have you observerd Error log?
    Check out at C:\Program Files\Microsoft SQL Server\MSSQL.n\MSSQL\LOG\ERRORLOG
    Location might differ as per the Server configration
    Please click the Mark as answer button and vote as helpful if this reply solves your problem

  • A Servere Error Occured on the Current Command, The Result, If Any, should be discarded Message (10:17:1)

    Hello
    I am getting Following error when I predd add button. On this add button I do Bulk Copy insertion in some of tables.
    I am using Linq to sql classes. At my side error is not comming. But at client side error is comming. They have more than 1 lac data. I am not getting why this kind of error occured?
    So can anybody please tell me possible causes of this error?
    If possible then can anybody sugest me any solution for it?
    Thanking you in advance..
    Regards
    Vipul

    So can you please analyse it & tell me the possible reasons for this kind of error..
    Did you check the SQL Server error log?  That might provide details as to the underlying cause of the error.
    & also if possible then can you please send me basic solution that you can sugest me..
    One method that might avoid the problem to insert in smaller batches line 10,000 rows.  Use a separate data table for the SqlBulkCopy and perform the WriteToServer in a loop.  Copy up to 10K rows from the source to target data table and
    execute WriteToServer in each iteration.
    A more robust method is to create your own DataReader that batches the rows.  The original data table could be used as the source. 
    Dan Guzman, SQL Server MVP, http://www.dbdelta.com

  • A severe error occurred on the current command - select into

    Hi
    I am making a backup of a table before working on the original, but when I try a simple select into statement I receive 'Msg 0, Level 11, State 0, Line 0 - A Severe error occurred on the current command.  The results, if any, should be discarded.'
    I am able to run a select query on the original table with the same where clause I am using in the select into statement and it runs without error.  
    Does anyone know why this is happening?
    Server 2008 64bit, SQL Server 2008r2
    Thank you for any help

    This is a generic message that informs you that something went very wrong, either in SQL Server itself or in the client API.
    If open a command promptt and try the same command running from SQLCMD or OSQL, what happens? If things seems to work well, run a simple second command like "SELECT 1" to make sure that this works. (The use a different API from SSMS, why it is
    worth testing.)
    Also look in the SQL Server error log. If you see a stack dump which appeared at the same time as you ran the SELECT INTO statement, then it's clear that the accident was in SQL Server.
    I would recommend that you run DBCC CHECKDB on the database, as the root cause could be corruption.
    Erland Sommarskog, SQL Server MVP, [email protected]

  • ERROR at line 1: ORA-29855: error occurred in the execution of ODCIINDEXCREATE routine ORA-20000: Oracle Text error: DRG-10700: preference does not exist: global_lexer ORA-06512: at "CTXSYS.DRUE", line 160 ORA-06512: at "CTXSYS.TEXTINDEXMETHODS", line 366

    database version 11.2.0.4
    rac two node
    CREATE INDEX MAXIMO.ACTCI_NDX3 ON MAXIMO.ACTCI
    (DESCRIPTION)
    INDEXTYPE IS CTXSYS.CONTEXT
    PARAMETERS('lexer global_lexer language column LANGCODE')
    ERROR at line 1:
    ORA-29855: error occurred in the execution of ODCIINDEXCREATE routine
    ORA-20000: Oracle Text error:
    DRG-10700: preference does not exist: global_lexer
    ORA-06512: at "CTXSYS.DRUE", line 160
    ORA-06512: at "CTXSYS.TEXTINDEXMETHODS", line 366

    Like the error message says, you don't have a global_lexer.  So, you need to create a global_lexer and that lexer must have at least a default sub_lexer, then you can use that global_lexer in your index parameters.  Please see the demonstration below, including reproduction of the error and solution.
    SCOTT@orcl12c> -- reproduction of problem:
    SCOTT@orcl12c> CREATE TABLE actci
      2    (description  VARCHAR2(60),
      3      langcode     VARCHAR2(30))
      4  /
    Table created.
    SCOTT@orcl12c> CREATE INDEX ACTCI_NDX3 ON ACTCI (DESCRIPTION)
      2  INDEXTYPE IS CTXSYS.CONTEXT
      3  PARAMETERS('lexer global_lexer language column LANGCODE')
      4  /
    CREATE INDEX ACTCI_NDX3 ON ACTCI (DESCRIPTION)
    ERROR at line 1:
    ORA-29855: error occurred in the execution of ODCIINDEXCREATE routine
    ORA-20000: Oracle Text error:
    DRG-10700: preference does not exist: global_lexer
    ORA-06512: at "CTXSYS.DRUE", line 160
    ORA-06512: at "CTXSYS.TEXTINDEXMETHODS", line 366
    SCOTT@orcl12c> -- solution:
    SCOTT@orcl12c> DROP INDEX actci_ndx3
      2  /
    Index dropped.
    SCOTT@orcl12c> BEGIN
      2    CTX_DDL.CREATE_PREFERENCE ('global_lexer', 'multi_lexer');
      3    CTX_DDL.CREATE_PREFERENCE ('english_lexer', 'basic_lexer');
      4    CTX_DDL.ADD_SUB_LEXER ('global_lexer', 'default', 'english_lexer');
      5  END;
      6  /
    PL/SQL procedure successfully completed.
    SCOTT@orcl12c> CREATE INDEX ACTCI_NDX3 ON ACTCI (DESCRIPTION)
      2  INDEXTYPE IS CTXSYS.CONTEXT
      3  PARAMETERS('lexer global_lexer language column LANGCODE')
      4  /
    Index created.

  • This feature can only be installed on a server running SQL Server 2008 R2 SP1 or later ERROR

    Attempting to install MBAM 2.5, and the SQL Server I have available for the install is SQL Server 2008 R2 SP2; the databases installed correctly, but when I run the Reports install it suddenly doesn't like my SQL anymore. The error says I need to install
    SQL Server 2008 R2 SP1, SQL Server 2012 SP1, or later - and the server is already at that level.
    Any idea of how to progress without needing to wipe out SQL and upgrading everything to 2012 R2? I really need to get this running ASAP, so I'm hoping there's a tip that will allow me to get the install to complete.

    Added note: When I check the mbam setup logs in event viewer, I get the following error:
    IsSupportedSqlVersion: The SQL version is not supported - 10.50.1600.1.
    Checking the version in SQL Management Studio shows:
    select @@VERSION
    Microsoft SQL Server 2008 R2 (SP2) - 10.50.4000.0 (X64)

  • What is the best way to deal with memory leak issue in sql server 2008 R2

    What is the best way to deal with memory leak issue in sql server 2008 R2.

    What is the best way to deal with memory leak issue in sql server 2008 R2.
    I have heard of memory leak in OS that too because of some external application or rouge drivers SQL server 2008 R2 if patched to latest SP and CU ( may be if required) does not leaks memory.
    Are you in opinion that since SQL is taking lot of memory and then not releasing it is a memory leak.If so this is not a memory leak but default behavior .You need to set proper value for max server memory in sp_configure to limit buffer pool usage.However
    sql can take more memory from outside buffer pool if linked server ,CLR,extended stored procs XML are heavily utilized
    Any specific issue you are facing
    Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

  • Severe Error Ocurred on the Current Command REPORT BUILDER SSRS 2008

    Hi,
         I have a report with 6 tabs, I am using totally 8 Stored Procedures for it.I am using SQL SERVER 2008 R2 and the same in production also.
    Everything works fine when I run the report in my local machine's BIDS, however, when I deploy it into the Production, it occasionally gives an error which reads "An error has occurred during local report processing. (rsProcessingAborted). Query execution
    failed  for dataset 'DS_xxxx'. (rsErrorExecutingCommand)
    A Severe error occurred on the current command. The results, if any, should be discarded. Operation cancelled by user.
    When I ran the SPs individually in the SSMS they are executing fine and the report itself works fine always in my local BIDS.
    Also, This issue happend several weeks after the report was deployed to the production, i.e. it was working fine but suddenly it started giving this error, so I changed the global temp table I was using to a permanent table and then it worked fine for a
    few more weeks, now, again, I am getting the same error occasionally, is there any way to avoid this error completely and can you list all the possible causes for this error, because it happens 2 times out of 5 runs so it is difficult to debug it also.
    As for the Report it self, It is a simple report with a few spark line Charts and a mostly data charts. I am not using any CTEs or Global Temp Tables anywhere in the report.
    Thanks You.

    Hi,
    I would suggest you increase the time out on the reports to 3600 and how it works.
    You can set a default value for all reports in the Site Settings page.
    The default timeout in SSRS for reports is 1800 seconds.
    If still no progress, please check the RS log.
    For more information, see
    Set Report Processing Properties.
    Thanks.
    Tracy Cai
    TechNet Community Support

  • Error occurs during the rendering of jsp component

    Hi everyone,
       I have writting a webdynpro java program and it run well in j2ee engine. I wanted to display it in my portal, so I use sap webdynpro iview to integrate it.But when I preview it ,the following error occured.
    [code]
    Portal Runtime Error
    An exception occurred while processing a request for :
    iView : pcd:portal_content/APPChina/HQ/mbos/iviews/com.app.hq.mbos.doctree
    Component Name : com.sap.portal.appintegrator.sap.WebDynpro
    Error occurs during the rendering of jsp component.
    Exception id: 02:52_28/09/07_2636_803509951
    See the details for the exception ID in the log file
    [/code]
    The detail error information in defaulttrace is below:
    [code]
    Exception ID:02:52_28/09/07_2636_803509951
    [EXCEPTION]
    com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Resource
    Component : pcd:portal_content/APPChina/HQ/mbos/iviews/com.app.hq.mbos.doctree
    Component class : com.sapportals.portal.sapapplication.SAPApplicationIntegratorComponent
    User : Administrator
         at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:969)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:444)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:527)
         at com.sapportals.portal.prt.component.AbstractComponentResponse.include(AbstractComponentResponse.java:89)
         at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:232)
         at com.sapportals.portal.appintegrator.Utils.includeJSP(Utils.java:199)
         at com.sapportals.portal.appintegrator.layer.PSIDLayer.render(PSIDLayer.java:58)
         at com.sapportals.portal.appintegrator.LayerProcessor.processContentPass(LayerProcessor.java:226)
         at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContent(AbstractIntegratorComponent.java:100)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
         at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
         at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:646)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
         at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
         at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:545)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Caused by: com.sapportals.portal.prt.component.PortalComponentException: Error occurs during the compilation of java generated from the jsp
         at com.sapportals.portal.prt.core.broker.JSPComponentItem.getComponentInstance(JSPComponentItem.java:116)
         at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.service(PortalComponentItemFacade.java:355)
         at com.sapportals.portal.prt.core.broker.PortalComponentItem.service(PortalComponentItem.java:934)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:435)
         ... 39 more
    Caused by: com.sapportals.portal.prt.servlets_jsp.server.compiler.CompilingException: Error occurs during the rendering of jsp component
         at com.sapportals.portal.prt.servlets_jsp.server.jsp.JSPParser.parse(JSPParser.java:2189)
         at com.sapportals.portal.prt.servlets_jsp.server.jsp.JSPCompiler.compile(JSPCompiler.java:81)
         at com.sapportals.portal.prt.servlets_jsp.server.jsp.JSPCompiler.run(JSPCompiler.java:140)
         at com.sapportals.portal.prt.core.broker.JSPComponentItem.compileJSP(JSPComponentItem.java:291)
         at com.sapportals.portal.prt.core.broker.JSPComponentItem.getComponentInstance(JSPComponentItem.java:141)
         ... 42 more
    [/code]

    Hi,
    Please look at the file
    C:\usr\sap\<sid>\JC<instance>\j2ee\cluster\server0\log\default.x.trc
    for more details of the exception.
    There will be a stack trace here which is essential in order to resolve the problem. Please post the stack trace here.
    Dagfinn

  • 0CFM_INIT_POSITIONS: Errors occurred during the extraction

    Hi,
    I am working in treasury management. I have activated the data source 0CFM_INIT_POSITIONS in rsa5 and while loading data I am getting error: Errors in source system
    If I checked same data source in rsa3 in ECC, I got the following error
    Errors occurred during the extraction.
    could any one solve this problem?

    sry, forgot to mention the error that i am getting for this init request in infocube mange->monitor
    Delta upload is only possible after successful initialization
    Message no. RSBM103
    Diagnosis
    You tried to extract records using a delta request in the target BI. However, it is not possible to transfer a consistent delta for this DataSource.
    System Response
    One of the following takes place:
    1. You have not yet triggered the delta update with an init request.
    2. The delta update was initialized but a request was deleted that was already transferred into the target BI.
    3. The delta update was initialized but a request was deleted that was not yet transferred into the target BI.
    In each case the consistency of the data transferred into the target BI is not guaranteed.
    Procedure
    Restructure the delta update by deleting the delta request that already exists in the target BI and then submitting an init request to InfoCube 0CFM_O01 of the source BI.

  • Errors occurred during the extraction - 0FI_AR_30

    Hi guys,
    I have just activated some datasources  0FI_AR_30, 0FI_AR_20 and 0FI_AR_50 and when I tried to check the extractors in RSA3 am getting a (Errors occurred during the extraction).  Any clues? 
    Thanks,
    Recca

    Hi Gaurav,
    I have no any other error message other than this in an SAP message window.  This of course is a full extraction to check if the datasource fields are pulling data from the tables.  Also, can you please expanciate on the init that need to be done.......do you mean Infopackage need to be created before I can check an extractor or what do you mean by target system?.  This is RSA3 in ECC and not RSA1 IN BI.  Please explain.
    Thanks,
    Recca

  • SQL Server 2008 KB2977321 Failed with Error code 1642

    As part of application of security patches via windows update, sql server KB2977321 was applied along with a number of OS security patches. 
    Prior to applying the patches, I stopped the agent, engine, reporting, analysis and full text services.
    The Sql server build prior to windows update was (for both instances):
    ProductVersion           
    ProductLevel               
    Edition
    10.0.5500.0                 
    SP3            
    Standard Edition (64-bit)
    After the update process, my main instance is showing (the second instance is not in use yet and I have left it in its stopped state)
    Microsoft SQL Server 2008 (SP3) - 10.0.5520.0 (X64)
    Jul 11 2014 16:11:50
    Copyright (c) 1988-2008 Microsoft Corporation
    Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (VM)
    In the Administrative Logs after the OS patches were applied (and all were reported as successful by windows update), I found the following errors listed:
    Log Name:     
    Application
    Source:       
    MsiInstaller
    Date:         
    11/18/2014 7:16:45 PM
    Event ID:     
    1024
    Task Category: None
    Level:        
    Error
    Keywords:     
    Classic
    User:         
    SYSTEM
    Computer:     
    SJCDB3.intranet.co.st-johns.fl.us
    Description:
    Product: Microsoft SQL Server 2008 Database Engine Services - Update '{9145CF54-462E-4A28-8FB5-A44C93AD3716}' could not be installed. Error code 1642. Windows Installer can create logs to help troubleshoot
    issues with installing software packages. Use the following link for instructions on turning on logging support: http://go.microsoft.com/fwlink/?LinkId=23127
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
    <Provider Name="MsiInstaller" />
    <EventID Qualifiers="0">1024</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-11-19T00:16:45.000000000Z" />
    <EventRecordID>1764186</EventRecordID>
    <Channel>Application</Channel>
    <Computer>SJCDB3.intranet.co.st-johns.fl.us</Computer>
    <Security UserID="S-1-5-18" />
      </System>
      <EventData>
    <Data>Microsoft SQL Server 2008 Database Engine Services</Data>
    <Data>{9145CF54-462E-4A28-8FB5-A44C93AD3716}</Data>
    <Data>1642</Data>
    <Data>(NULL)</Data>
    <Data>(NULL)</Data>
    <Data>(NULL)</Data>
    <Data>
    </Data>
    <Binary>7B38373544383436332D313135422D343444322D414432352D3731454337453833423843437D207B39313435434635342D343632452D344132382D384642352D4134344339334144333731367D2031363432</Binary>
      </EventData>
    </Event>
    In the C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20141118_191448\Detail.txt file I found the following around the time the error was reported
    2014-11-18 19:16:30 Slp: Baseline Package Id sql_engine_core_inst_Cpu64 - The highest patch version is 10.3.5500.0
    2014-11-18 19:16:30 Slp: Patch Id KB2977321_sql_engine_core_inst_Cpu64 - NotInstalled on the baseline msi package sql_engine_core_inst_Cpu64. 
    Detail description of this patch package is: PatchId=KB2977321_sql_engine_core_inst_Cpu64 PatchVersion=10.3.5520.0 BaselinePackageId=sql_engine_core_inst_Cpu64 BaselineVersion=10.3.5500.0; PatchFileName=sql_engine_core_inst.msp PatchCode={9145CF54-462E-4A28-8FB5-A44C93AD3716}
    2014-11-18 19:16:30 Slp: Patch Id: KB2977321_sql_engine_core_inst_Cpu32 - The baseline msi is not installed. 
    The patch package is ignored.
    2014-11-18 19:16:30 Slp: Patch Id: KB2977321_sql_engine_core_inst_Cpu32 - Detail description of this patch package is: PatchId=KB2977321_sql_engine_core_inst_Cpu32 PatchVersion=10.3.5520.0 BaselinePackageId=sql_engine_core_inst_Cpu32
    BaselineVersion=10.3.5500.0; PatchFileName=sql_engine_core_inst.msp PatchCode={9145CF54-462E-4A28-8FB5-A44C93AD3716}
    2014-11-18 19:16:30 Slp: Baseline Package Id sql_rs_Cpu64 - The highest patch version is 10.3.5500.0
    2014-11-18 19:16:30 Slp: Patch Id KB2977321_sql_rs_Cpu64 - NotInstalled on the baseline msi package sql_rs_Cpu64. 
    Detail description of this patch package is: PatchId=KB2977321_sql_rs_Cpu64 PatchVersion=10.3.5520.0 BaselinePackageId=sql_rs_Cpu64 BaselineVersion=10.3.5500.0; PatchFileName=sql_rs.msp PatchCode={2296F7DD-2D3D-4802-B61A-AE7460EFB767}
    2014-11-18 19:16:30 Slp: Patch Id: KB2977321_sql_rs_Cpu32 - The baseline msi is not installed. 
    The patch package is ignored.
    2014-11-18 19:16:30 Slp: Patch Id: KB2977321_sql_rs_Cpu32 - Detail description of this patch package is: PatchId=KB2977321_sql_rs_Cpu32 PatchVersion=10.3.5520.0 BaselinePackageId=sql_rs_Cpu32 BaselineVersion=10.3.5500.0;
    PatchFileName=sql_rs.msp PatchCode={2296F7DD-2D3D-4802-B61A-AE7460EFB767}
    2014-11-18 19:16:30 Slp: Baseline Package Id sql_is_Cpu64 - The highest patch version is 10.3.5500.0
    2014-11-18 19:16:30 Slp: Patch Id KB2977321_sql_is_Cpu64 - NotInstalled on the baseline msi package sql_is_Cpu64. 
    Detail description of this patch package is: PatchId=KB2977321_sql_is_Cpu64 PatchVersion=10.3.5520.0 BaselinePackageId=sql_is_Cpu64 BaselineVersion=10.3.5500.0; PatchFileName=sql_is.msp PatchCode={E870296C-24CC-4D82-BB59-CD136692E2BD}
    2014-11-18 19:16:30 Slp: Baseline Package Id sql_bids_Cpu64 - The highest patch version is 10.3.5500.0
    2014-11-18 19:16:30 Slp: Patch Id KB2977321_sql_bids_Cpu64 - NotInstalled on the baseline msi package sql_bids_Cpu64. 
    Detail description of this patch package is: PatchId=KB2977321_sql_bids_Cpu64 PatchVersion=10.3.5520.0 BaselinePackageId=sql_bids_Cpu64 BaselineVersion=10.3.5500.0; PatchFileName=sql_bids.msp PatchCode={EA407FA6-C2D1-4D3D-9227-B9E06DDDEFD0}
    2014-11-18 19:16:30 Slp: Baseline Package Id sql_ssms_Cpu64 - The highest patch version is 10.3.5500.0
    2014-11-18 19:16:30 Slp: Patch Id KB2977321_sql_ssms_Cpu64 - NotInstalled on the baseline msi package sql_ssms_Cpu64. 
    Detail description of this patch package is: PatchId=KB2977321_sql_ssms_Cpu64 PatchVersion=10.3.5520.0 BaselinePackageId=sql_ssms_Cpu64 BaselineVersion=10.3.5500.0; PatchFileName=sql_ssms.msp PatchCode={8A81B870-E8F0-415D-AC80-13BEAA3EC8C8}
    2014-11-18 19:16:30 Slp: Baseline Package Id: sql_common_core_Cpu64 - No patches are found by SQL Discovery on the installed package whose ProductCode is {5340A3B5-3853-4745-BED2-DD9FF5371331}
    2014-11-18 19:16:30 Slp: Patch Id KB2977321_sql_common_core_Cpu64 - NotInstalled on the baseline msi package sql_common_core_Cpu64. 
    Detail description of this patch package is: PatchId=KB2977321_sql_common_core_Cpu64 PatchVersion=10.3.5520.0 BaselinePackageId=sql_common_core_Cpu64 BaselineVersion=10.3.5500.0; PatchFileName=sql_common_core.msp PatchCode={CF023E0F-3A19-4DBF-BCA3-0F664B447EDB}
    The instance came up successfully and seems to be operating normally. Was there an error or was the KB installed correctly as the result of the windows update process indicated? 
    Is there a way I can verify this? 

    I did some research on this particular KB article and it seems to be related to Master Data Services which I am not using.  The KB was pushed automatically and I am not sure that it was a required update in our situation. I'd like to understand exactly
    what caused the error message before initiating a repair as this is a production and not a test environment.  Everything appears to be functioning properly and I have received direction from Microsoft in the past that information in some logs identified
    as level 'error' are in fact to be ignored.  I checked the windows update and this KB shows 'Successful' rather than failed or cancelled.
    I would also like more information on why sql server services should not be stopped prior to allowing the OS patches to be applied.   I have received messages in the past that stopping the services before service packs are applied
    prevent the necessity for a reboot of the machine.  I've never heard before that it is a best practice not to stop Sql service prior to applying patches.  Once the services are stopped, I have our infrastructure admin start a VM snapshot on
    the machine then kick off the windows update process. When done, I reboot the machine, test out Sql Server processes and then if all goes well give the ok to release the VM snapshot.  I've supported various databases for 12 years, Sql Server for 5
    years and this is the first time I've heard stopping the service manually can cause problems.  If that is the case, I will certainly change how I do things....
    I did run the discovery report and the results follow:
    Microsoft SQL Server 2008 Setup Discovery Report
    Product
    Instance
    Instance ID
    Feature
    Language
    Edition
    Version
    Clustered
    Sql Server 2008
    MSSQLSERVER
    MSSQL10.MSSQLSERVER
    Database Engine Services
    1033
    Standard Edition
    10.3.5520.0
    No
    Sql Server 2008
    MSSQLSERVER
    MSSQL10.MSSQLSERVER
    SQL Server Replication
    1033
    Standard Edition
    10.3.5520.0
    No
    Sql Server 2008
    MSSQLSERVER
    MSSQL10.MSSQLSERVER
    Full-Text Search
    1033
    Standard Edition
    10.3.5500.0
    No
    Sql Server 2008
    MSSQLSERVER
    MSAS10.MSSQLSERVER
    Analysis Services
    1033
    Standard Edition
    10.3.5500.0
    No
    Sql Server 2008
    MSSQLSERVER
    MSRS10.MSSQLSERVER
    Reporting Services
    1033
    Standard Edition
    10.3.5520.0
    No
    Sql Server 2008
    EVAULT
    MSSQL10.EVAULT
    Database Engine Services
    1033
    Standard Edition
    10.3.5520.0
    No
    Sql Server 2008
    Management Tools - Basic
    1033
    Standard Edition
    10.3.5520.0
    No
    Sql Server 2008
    Management Tools - Complete
    1033
    Standard Edition
    10.3.5500.0
    No
    Sql Server 2008
    Client Tools Connectivity
    1033
    Standard Edition
    10.3.5500.0
    No
    Sql Server 2008
    Client Tools Backwards Compatibility
    1033
    Standard Edition
    10.3.5500.0
    No
    Sql Server 2008
    Client Tools SDK
    1033
    Standard Edition
    10.3.5500.0
    No
    Sql Server 2008
    Integration Services
    1033
    Standard Edition
    10.3.5520.0
    No

Maybe you are looking for