Latch timeout stack dump

=====================================================================                                            
       BugCheck Dump                                                              
=====================================================================                                            
This file is generated by Microsoft SQL Server                                                            
version 9.00.5000.00                                                                    
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 AT/AT COMPATIBLE.                                                                
Bios Version is DELL   - 1                                                                  
Phoenix ROM BIOS PLUS Version 1.10 2.2.6                                                              
Current time is 06:28:49 08/28/14.                                                                
8 Intel x86 level 6, 2660 Mhz processor (s).                                                              
Windows NT 5.2 Build 3790 CSD Service Pack 2.                                                              
Memory                               
MemoryLoad = 82%                     
Total Physical = 32762 MB            
Available Physical = 5805 MB         
Total Page File = 82821 MB           
Available Page File = 56349 MB       
Total Virtual = 2047 MB              
Available Virtual = 282 MB           
**Dump thread - spid = 18, PSS = 0x7657A7D8, EC = 0x7657A7E0                                                     
***Stack Dump being sent to xxxxxx                                
* BEGIN STACK DUMP:                                                                  
*   08/28/14 06:28:49 spid 18                                                              
* Latch timeout                                                                    
* Short Stack Dump                   

Hello,
A fix was issued on CU 6 for SQL Server 2005 (Oct 2009) and your SQL Server instance has SP4 applied which was released November 2009.
Please apply CU1 for SP4 to make sure the hot fix has been applied to the SQL Server instance.
http://support.microsoft.com/kb/2464079
The following article may help you troubleshoot this issue:
http://mssqlwiki.com/tag/latch-timeout-stack-dump/
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Similar Messages

  • Stack Dump while creating Write Optimized DSO on BW 7.3, MS SQL - any SAP Notes?

    While attempting to create a Write Optimized DSO on BW 7.3, MS SQL, we had a stack dump - ABAP Program     CL_RSD_ODSO_VERS==============CP with short text " Access using NULL object reference is not possible. "
    Has anyone seen any SAP Notes on this subject?

    Hi John,
    Was any field deleted from the DSO, if yes, probably the system is not able to relate the pointer from the DSO table. Error like these come up very often when fields are deleted from DSO. Solution is to remove the field manually from the table also. However, the system is supposed to do but sometimes such ambiguity causes such issues.

  • Stack dump while trying to view the JNDI Tree on a managed server.

    Hi,
    We are running WLI 9.2.3.
    I have a problem when trying to view the managed servers JNDI Tree via the Admin console. The admin servers JNDI tree appears to be fine, but trying to view the 1st managed servers JNDI Tree via the admin console keeps producing a stack dump.
    Does anyone know why this would be? Is it a security issue, judging by the classes below:
    ####<Jul 14, 2010 1:31:29 PM BST> <Warning> <RMI> <sofatd2b> <tgri02_rsk_ms11> <[ACTIVE] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel
    <> <> <1279110689890> <BEA-080004> <An error was thrown by rmi server: weblogic.jndi.internal.RootNamingNode.listBindings(Ljava.lang.String;Ljava.util.Hashtable;)java.lang.StackOverflowError.
    java.lang.StackOverflowError
    at $Proxy5.isAccessAllowed(Unknown Source)
    at com.bea.common.security.internal.service.AccessDecisionServiceImpl.isAccessAllowed(AccessDecisionServiceImpl.java:105)
    at sun.reflect.GeneratedMethodAccessor202.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at com.bea.common.security.internal.utils.Delegator$ProxyInvocationHandler.invoke(Delegator.java:61)
    at $Proxy11.isAccessAllowed(Unknown Source)
    at com.bea.common.security.internal.service.AuthorizationServiceImpl.isAccessAllowed(AuthorizationServiceImpl.java:81)
    at sun.reflect.GeneratedMethodAccessor201.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at com.bea.common.security.internal.utils.Delegator$ProxyInvocationHandler.invoke(Delegator.java:61)
    at $Proxy13.isAccessAllowed(Unknown Source)
    at weblogic.security.service.AuthorizationManager.isAccessAllowed(AuthorizationManager.java:461)
    at weblogic.security.service.AuthorizationManager.isAccessAllowed(AuthorizationManager.java:524)
    at weblogic.jndi.internal.ServerNamingNode.checkPermission(ServerNamingNode.java:414)
    at weblogic.jndi.internal.ServerNamingNode.checkLookup(ServerNamingNode.java:394)
    at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:169)
    at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
    at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:269)
    at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:367)
    at javax.naming.InitialContext.lookup(InitialContext.java:351)
    at weblogic.deployment.jms.ForeignOpaqueReference.getReferent(ForeignOpaqueReference.java:196)
    at weblogic.jndi.internal.WLNamingManager.getObjectInstance(WLNamingManager.java:95)
    at weblogic.jndi.internal.ServerNamingNode.resolveObject(ServerNamingNode.java:348)
    at weblogic.jndi.internal.BasicNamingNode.resolveObject(BasicNamingNode.java:856)
    at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:209)
    at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:269)
    at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:367)
    at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:269)
    at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:367)
    at javax.naming.InitialContext.lookup(InitialContext.java:351)
    at weblogic.deployment.jms.ForeignOpaqueReference.getReferent(ForeignOpaqueReference.java:196)
    at weblogic.jndi.internal.WLNamingManager.getObjectInstance(WLNamingManager.java:95)
    at weblogic.jndi.internal.ServerNamingNode.resolveObject(ServerNamingNode.java:348)
    at weblogic.jndi.internal.BasicNamingNode.resolveObject(BasicNamingNode.java:856)
    at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:209)
    at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:269)
    at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:367)
    at javax.naming.InitialContext.lookup(InitialContext.java:351)
    at weblogic.deployment.jms.ForeignOpaqueReference.getReferent(ForeignOpaqueReference.java:196)
    at weblogic.jndi.internal.WLNamingManager.getObjectInstance(WLNamingManager.java:95)
    at weblogic.jndi.internal.ServerNamingNode.resolveObject(ServerNamingNode.java:348)
    at weblogic.jndi.internal.BasicNamingNode.resolveObject(BasicNamingNode.java:856)
    at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:209)
    at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:269)
    at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:367)
    at javax.naming.InitialContext.lookup(InitialContext.java:351)
    at weblogic.deployment.jms.ForeignOpaqueReference.getReferent(ForeignOpaqueReference.java:196)
    at weblogic.jndi.internal.WLNamingManager.getObjectInstance(WLNamingManager.java:95)
    at weblogic.jndi.internal.ServerNamingNode.resolveObject(ServerNamingNode.java:348)
    at weblogic.jndi.internal.BasicNamingNode.resolveObject(BasicNamingNode.java:856)
    at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:209)
    at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:269)
    at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:367)
    at javax.naming.InitialContext.lookup(InitialContext.java:351)
    at weblogic.deployment.jms.ForeignOpaqueReference.getReferent(ForeignOpaqueReference.java:196)
    at weblogic.jndi.internal.WLNamingManager.getObjectInstance(WLNamingManager.java:95)
    at weblogic.jndi.internal.ServerNamingNode.resolveObject(ServerNamingNode.java:348)
    at weblogic.jndi.internal.BasicNamingNode.resolveObject(BasicNamingNode.java:856)
    at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:209)
    at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:269)
    at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:367)
    at javax.naming.InitialContext.lookup(InitialContext.java:351)

    Hi,
    if it works in Chrome then this Problem is related to IE.
    Maybe the URL is to long? IE can "only" handle 2048 Characters.
    Regards
    -Seb.

  • Log Reader Agent error "could not execute sp_replcmds' and causes stack dump

    Publisher/Subscriber db:  SQL 2008 R2, 2000 compatability mode
    Distributor database is on separate server.
    (note:  There is another database on this instance that is running replication without error, it is not in compatibility mode)
    After snapshot agent finishes, the log reader agent starts and fails immediately with this error in the Agent Job.
    Then I get a SEV20 error and stack dump in the error logs.
    Date  6/12/2014 3:12:26 PM
    Log  Job History (SERVER\INSTANCE-DBNAME-43)
    Step ID  2
    Server  ######RT02
    Job Name  SERVER\INSTANCE-DBNAME-43
    Step Name  Run agent.
    Duration  00:00:01
    Sql Severity  0
    Sql Message ID  0
    Operator Emailed  
    Operator Net sent  
    Operator Paged  
    Retries Attempted  0
    Message
    2014-06-12 20:12:26.302 Copyright (c) 2008 Microsoft Corporation
    2014-06-12 20:12:26.302 Microsoft SQL Server Replication Agent: logread
    2014-06-12 20:12:26.302
    2014-06-12 20:12:26.302 The timestamps prepended to the output lines are expressed in terms of UTC time.
    2014-06-12 20:12:26.302 User-specified agent parameter values:
       -Publisher SERVER\INSTANCE
       -PublisherDB DBNAME
       -Distributor ######RT02
       -DistributorSecurityMode 1
       -Continuous
       -XJOBID 0x8958DF32810C6849B28A037A8FF8DD92
       -XJOBNAME SERVER\INSTANCE-DBNAME-43
       -XSTEPID 2
       -XSUBSYSTEM LogReader
       -XSERVER SERVER\INSTANCE
       -XCMDLINE 0
       -XCancelEventHandle 0000000000000F98
       -XParentProcessHandle 0000000000000F34
    2014-06-12 20:12:26.459 Parameter values obtained from agent profile:
       -pollinginterval 5000
       -historyverboselevel 1
       -logintimeout 15
       -querytimeout 1800
       -readbatchsize 500
       -readbatchsize 500000
    2014-06-12 20:12:26.493 Status: 4096, code: 20024, text: 'Initializing'.
    2014-06-12 20:12:26.493 The agent is running. Use Replication Monitor to view the details of this agent session.
    2014-06-12 20:12:27.885 Status: 0, code: 20011, text: 'The process could not execute 'sp_replcmds' on 'SERVER\INSTANCE'.'.
    2014-06-12 20:12:27.886 The process could not execute 'sp_replcmds' on 'SERVER\INSTANCE'.
    2014-06-12 20:12:27.886 Status: 0, code: 21, text: 'Warning: Fatal error 3624 occurred at Jun 12 2014  3:12PM. Note the error and time, and contact your system administrator.'.
    2014-06-12 20:12:27.886 Status: 0, code: 22037, text: 'The process could not execute 'sp_replcmds' on 'SERVER\INSTANCE'.'.
    I've tried removing replication and setting it back up again, restarting SQL, and restarting the server itself.
    Let me know if you need any more information to help troubleshoot.  Thanks.
    Please help, thanks. 

    Hi,
    Enable Verbose logging and check the results.
    Execute following commands: -Output C:\Temp\OUTPUTFILE.txt –Outputverboselevel 2.
    Please refer following KB article for your reference -
    http://support.microsoft.com/kb/q312292/
    Thanks.
    Tracy Cai
    TechNet Community Support

  • 10g - stack dump in JSP design tab - minor.

    I have a JSP which references a style sheet on a remote server. Don't ask. Normally when I look at it in the JSP editor Design tab I get an alert box saying 'Error opening style.css". This is fine.
    Today I got the following stack dump instead.
    The page displayed OK after I dismissed the error dialog.
    java.net.SocketTimeoutException: connect timed out
         at java.net.PlainSocketImpl.socketConnect(Native Method)
         at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
         at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171)
         at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)
         at java.net.Socket.connect(Socket.java:426)
         at sun.net.NetworkClient.doConnect(NetworkClient.java:137)
         at sun.net.www.http.HttpClient.openServer(HttpClient.java:386)
         at sun.net.www.http.HttpClient.openServer(HttpClient.java:602)
         at sun.net.www.http.HttpClient.<init>(HttpClient.java:303)
         at sun.net.www.http.HttpClient.<init>(HttpClient.java:265)
         at sun.net.www.http.HttpClient.New(HttpClient.java:336)
         at sun.net.www.http.HttpClient.New(HttpClient.java:317)
         at sun.net.www.http.HttpClient.New(HttpClient.java:312)
         at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:481)
         at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:472)
         at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:574)
         at java.net.URL.openStream(URL.java)
         at oracle.ide.net.URLFileSystemHelper.openInputStream(URLFileSystemHelper.java:962)
         at oracle.ide.net.URLFileSystem.openInputStream(URLFileSystem.java:1006)
         at oracle.ide.model.TextNode.loadURLContentIntoBuffer(TextNode.java:818)
         at oracle.ide.model.TextNode.reloadTextBuffer(TextNode.java:352)
         at oracle.ide.model.TextNode.reopen(TextNode.java:330)
         at oracle.ide.model.TextNode.open(TextNode.java:197)
         at oracle.ide.model.TextNode.acquireTextBuffer(TextNode.java:597)
         at oracle.ide.model.TextNode.getReader(TextNode.java)
         at oracle.jdevimpl.webapp.IdeHelper.getReader(IdeHelper.java:117)
         at oracle.jdevimpl.webapp.parser.css.Parser.characterStream(Parser.java:1559)
         at oracle.jdevimpl.webapp.parser.css.Parser.parseStyleSheet(Parser.java:228)
         at oracle.jdevimpl.webapp.model.css.SacDocumentBuilder.buildStyleSheet(SacDocumentBuilder.java:106)
         at oracle.jdevimpl.webapp.model.css.html.LinkedStyleSheet.load(LinkedStyleSheet.java:97)
         at oracle.jdevimpl.webapp.model.css.html.LinkedStyleSheet.getRules(LinkedStyleSheet.java:82)
         at oracle.jdevimpl.webapp.model.css.html.HtmlCSSValuesAssigner.insertStyleSheet(HtmlCSSManager.java:197)
         at oracle.jdevimpl.webapp.model.css.html.HtmlCSSValuesAssigner.<init>(HtmlCSSManager.java:182)
         at oracle.jdevimpl.webapp.model.css.html.HtmlCSSManager.getCSSValuesAssigner(HtmlCSSManager.java:65)
         at oracle.jdevimpl.webapp.view.DisplayManager._generateBoxes(DisplayManager.java:1415)
         at oracle.jdevimpl.webapp.view.DisplayManager.generateView(DisplayManager.java:910)
         at oracle.jdevimpl.webapp.view.DisplayManager.showContent(DisplayManager.java:476)
         at oracle.jdevimpl.webapp.editor.EditorImpl.showContent(EditorImpl.java:102)
         at oracle.jdevimpl.webapp.editor.html.HtmlEditor.updateDisplay(HtmlEditor.java:565)
         at oracle.jdevimpl.webapp.editor.WebAppEditor.syncIt(WebAppEditor.java:536)
         at oracle.jdevimpl.webapp.editor.WebAppEditor.access$4000271(WebAppEditor.java:54)
         at oracle.jdevimpl.webapp.editor.WebAppEditor$2.run(WebAppEditor.java:524)
         at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:178)
         at java.awt.EventQueue.dispatchEvent(EventQueue.java:449)
         at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:197)
         at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:151)
         at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:145)
         at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:136)
         at java.awt.EventDispatchThread.run(EventDispatchThread.java:99)

    Could you reduce your jsp and paste the contents here? We can examine it. Thanks, Steve Tom.

  • PMON failed to acquire latch, see PMON dump

    Hi,
    Database alert log show the following errors.
    PMON failed to acquire latch, see PMON dump
    PMON failed to acquire latch, see PMON dump
    PMON failed to acquire latch, see PMON dump
    PMON failed to acquire latch, see PMON dump
    PMON failed to acquire latch, see PMON dump
    PMON failed to acquire latch, see PMON dump
    PMON failed to acquire latch, see PMON dump
    PMON failed to acquire latch, see PMON dump
    PMON failed to acquire latch, see PMON dump
    PMON failed to acquire latch, see PMON dump
    PMON failed to acquire latch, see PMON dump
    PMON failed to acquire latch, see PMON dump
    PMON failed to acquire latch, see PMON dump
    PMON failed to acquire latch, see PMON dump
    PMON failed to acquire latch, see PMON dump
    PMON failed to acquire latch, see PMON dump
    PMON failed to acquire latch, see PMON dump
    PMON failed to acquire latch, see PMON dump
    PMON failed to acquire latch, see PMON dump
    PMON failed to acquire latch, see PMON dump
    PMON failed to acquire latch, see PMON dump
    PMON failed to acquire latch, see PMON dump
    PMON failed to acquire latch, see PMON dump
    During this time we excuting query,
    'exec sys.utl_recomp.recomp_parallel(8)' two session,
    One session hanged , another session running background,
    Kindly guide to us to find this issue
    Thanks and Regards
    Perumal Swamy.R

    Hi I have the same problem on a windows 2003 server, and in my alert log file there is that message :
    Wed Aug 10 11:20:40 2005
    kwqiclode: Error 1403 happened during loading of queue
    ORA-1403 encountered when generating server alert SMG-3503
    kwqiclode: Error 1403 happened during loading of queue
    Wed Aug 10 11:21:43 2005
    kwqiclode: Error 1403 happened during loading of queue
    kwqiclode: Error 1403 happened during loading of queue
    Wed Aug 10 11:22:46 2005
    kwqiclode: Error 1403 happened during loading of queue
    kwqiclode: Error 1403 happened during loading of queue
    Wed Aug 10 11:23:49 2005
    kwqiclode: Error 1403 happened during loading of queue
    kwqiclode: Error 1403 happened during loading of queue
    Wed Aug 10 11:24:49 2005
    kwqiclode: Error 1403 happened during loading of queue
    kwqiclode: Error 1403 happened during loading of queue
    Wed Aug 10 11:25:52 2005
    kwqiclode: Error 1403 happened during loading of queue
    kwqiclode: Error 1403 happened during loading of queue
    Wed Aug 10 11:26:55 2005
    kwqiclode: Error 1403 happened during loading of queue
    kwqiclode: Error 1403 happened during loading of queue
    kwqiclode: Error 1403 happened during loading of queue
    Wed Aug 10 11:27:55 2005
    kwqiclode: Error 1403 happened during loading of queue
    kwqiclode: Error 1403 happened during loading of queue
    Wed Aug 10 11:28:58 2005
    kwqiclode: Error 1403 happened during loading of queue
    kwqiclode: Error 1403 happened during loading of queue
    Wed Aug 10 11:29:40 2005
    kwqiclode: Error 1403 happened during loading of queue
    Wed Aug 10 11:30:01 2005
    kwqiclode: Error 1403 happened during loading of queue
    kwqiclode: Error 1403 happened during loading of queue
    Wed Aug 10 11:31:04 2005
    kwqiclode: Error 1403 happened during loading of queue
    ORA-1403 encountered when generating server alert SMG-3503
    kwqiclode: Error 1403 happened during loading of queue
    Wed Aug 10 11:32:07 2005
    kwqiclode: Error 1403 happened during loading of queue
    kwqiclode: Error 1403 happened during loading of queue
    Wed Aug 10 11:33:10 2005
    kwqiclode: Error 1403 happened during loading of queue
    kwqiclode: Error 1403 happened during loading of queue
    and in my pmon trace file d:\syges\bdump\syges_pmon_240.trc there is the above message :
    *** 2005-08-09 19:27:50.312
    PMON unable to acquire latch 2f0b508 process allocation
    possible holder pid = 17 ospid=2216
    *** 2005-08-09 19:27:50.343
    PMON unable to acquire latch 2f0b508 process allocation
    possible holder pid = 17 ospid=2216
    *** 2005-08-09 19:27:50.359
    PMON unable to acquire latch 2f0b508 process allocation
    possible holder pid = 17 ospid=2216
    *** 2005-08-09 19:27:50.375
    PMON unable to acquire latch 2f0b508 process allocation
    possible holder pid = 17 ospid=2216
    *** 2005-08-09 19:27:50.390
    PMON unable to acquire latch 2f0b508 process allocation
    possible holder pid = 17 ospid=2216
    *** 2005-08-09 19:27:50.406
    PMON unable to acquire latch 2f0b508 process allocation
    possible holder pid = 17 ospid=2216
    *** 2005-08-09 19:27:50.421
    PMON unable to acquire latch 2f0b508 process allocation
    possible holder pid = 17 ospid=2216
    *** 2005-08-09 19:27:50.437
    PMON unable to acquire latch 2f0b508 process allocation
    *** 2005-08-09 19:27:50.453
    version on my database :
    SQL> select * from v$version;
    BANNER
    Oracle Database 10g Enterprise Edition Release 10.1.0.4.0 - Prod
    PL/SQL Release 10.1.0.4.0 - Production
    CORE 10.1.0.4.0 Production
    TNS for 32-bit Windows: Version 10.1.0.4.0 - Production
    NLSRTL Version 10.1.0.4.0 - Production

  • Stack dump in 2005 server

    Hi All,
    Please help me in resolving this issue.
    ==================================================================== 
    BugCheck Dump 
    ===================================================================== 
    This file is generated by Microsoft SQL Server 
    version 9.00.5057.00 
    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 AT/AT COMPATIBLE. 
    Bios Version is INTEL - 6040000 
    PhoenixBIOS 4.0 Release 6.0 
    Current time is 06:04:58 09/21/14. 
    2 Intel x86 level 6, 2600 Mhz processor (s). 
    Windows NT 5.2 Build 3790 CSD Service Pack 2. 
    Memory 
    MemoryLoad = 95% 
    Total Physical = 4095 MB 
    Available Physical = 165 MB 
    Total Page File = 9029 MB 
    Available Page File = 4848 MB 
    Total Virtual = 2047 MB 
    Available Virtual = 256 MB 
    **Dump thread - spid = 0, PSS = 0x00000000, EC = 0x00000000 
    ***Stack Dump being sent to D:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\SQLDump0010.txt 
    * BEGIN STACK DUMP: 
    * 09/21/14 06:04:58 spid 0 
    * Non-yielding Resource Monitor 
    * Short Stack Dump
    select  @@ version:
    Microsoft SQL Server 2005 - 9.00.5057.00 (Intel X86)   Mar 25 2011 13:50:04   Copyright (c) 1988-2005 Microsoft Corporation  Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 2) 
    Thanks in advance.

    Hello,
    These types of errors are related to memory pressure or working set trimming on the SQL Server instance. Please try to set the max server
    memory option and leave 2 or 4 GB of RAM to the operating system.
    sp_configure
    'show advanced options', 1;
    GO
    RECONFIGURE;
    GO
    sp_configure
    'max server memory', 4096;
    GO
    RECONFIGURE;
    GO
    The above code limits SQL Server Memory Manager to 4 GB.
    Hope this helps.
    Regards,
    Alberto Morillo
    SQLCoffee.com

  • Stack dump with DBCC RESULTS

    Current time is 11:15:26 08/25/14.                                                              
    =====================================================================                                            
           BugCheck Dump                                                              
    =====================================================================                                            
    This file is generated by Microsoft SQL Server                                                            
    version 11.0.3000.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) Xeon(R) CPU E5-2640 v2 @ 2.00GHz.                                                      
    Bios Version is INTEL  - 6040000                                                                
    PhoenixBIOS 4.0 Release 6.0                                                                  
    12 X64 level 8664, 14 Mhz processor (s).                                                              
    Windows NT 6.2 Build 9200 CSD .                                                                  
    Memory                               
    MemoryLoad = 54%                     
    Total Physical = 129023 MB           
    Available Physical = 58720 MB        
    Total Page File = 147455 MB          
    Available Page File = 76622 MB       
    Total Virtual = 134217727 MB         
    Available Virtual = 134032858 MB     
    DBCC RESULTS
                <Dbcc ID="265" 
    <Dbcc ID="479" Error="2593" Severity="10" State="1">There are 445 rows in 111 pages for object "Temp_CalcFields_P
    laysDFD5C6F819E84D1EBA43D30C37AABB47".</Dbcc>                                                          
    <Dbcc ID="480" Error="2593" Severity="10" State="1">There are 154 rows in 4 pages for object "ReplicationInfo_tra
    cking".</Dbcc>                                                                  
    <Dbcc ID="481" Error="2593" Severity="10" State="1">There are 7022 rows in 177 pages for object "UserSettings_tra
    </DbccResults>                                                                    
    **Dump thread - spid = 0, EC = 0x00000010A909E730                                                            
    ***Stack Dump being sent to C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\LOG\SQLDump0003.txt  
    * BEGIN STACK DUMP:                                                                    
    *   08/25/14 11:15:26 spid 158                                                                
    * DBCC database corruption                                                                  
    * Input Buffer 90 bytes -                                                                  
    *             use [TC_Baylor_FB]  dbcc checkdb                                                  
    * Short Stack Dump                   
    CSession @0x0000001177F2C450
    m_sessionId = 158                    m_cRef = 14                          m_rgcRefType[0] = 1              
    m_rgcRefType[1] = 1                  m_rgcRefType[2] = 11                 m_rgcRefType[3] = 1                    
    m_rgcRefType[4] = 0                  m_rgcRefType[5] = 0                  m_pmo = 0x0000001177F2C040             
    m_pstackBhfPool = 0x0000000000000000 m_dwLoginFlags = 0x83e0              m_fBackground = 0                      
    m_eConnResetOption = 0               m_fUserProc = 1                      m_fConnReset = 0                       
    m_fIsConnReset = 0                   m_fInLogin = 0                       m_fAuditLoginSent = 1                  
    m_fAuditLoginFailedSent = 0          m_fReplRelease = 0                   m_fKill = 0                            
    m_ulLoginStamp = 6700445             m_eclClient = 7                      m_protType = 5                         
    m_hHttpToken = FFFFFFFFFFFFFFFF      
    m_pV7LoginRec
    0000000000000000:   5c010000 04000074 00100000 00000006 400d0000  \......t........@...                           
    0000000000000014:   00000000 e0830000 00000000 00000000 5e000e00  ....à?..........^...                           
    0000000000000028:   00000000 00000000 7a002e00 d6000e00 f2000400  ........z...Ö...ò...                           
    000000000000003C:   f6001c00 2e010000 2e010000 e3418e99 00e02e01  ö...........ãA?..à..                           
    0000000000000050:   28005601 00005601 00000000 0000               (.V...V.......                                 
    CPhysicalConnection @0x0000001177F2C230
    m_pPhyConn->m_pmo = 0x0000001177F2C040                                                              
    m_pPhyConn->m_pNetConn = 0x0000001177F2CBF0                                                            
    m_pPhyConn->m_pConnList = 0x0000001177F2C420                                                            
    m_pPhyConn->m_pSess = 0x0000001177F2C4A8                                  m_pPhyConn->m_fTracked = -1            
    m_pPhyConn->m_cbPacketsize = 4096    m_pPhyConn->m_fMars = 0              m_pPhyConn->m_fKill = 0                
    CBatch @0x0000001177F2D140
    m_pSess = 0x0000001177F2C450         m_pConn = 0x0000001177F2D020         m_cRef = 3                             
    m_rgcRefType[0] = 1                  m_rgcRefType[1] = 1                  m_rgcRefType[2] = 1                    
    m_rgcRefType[3] = 0                  m_rgcRefType[4] = 0                  m_pTask = 0x00000018199A2928           
    EXCEPT (null) @0x0000000064754EF0
    exc_number = 0                       exc_severity = 0                     exc_func = 0x00007FFF4730EE50          
    Task @0x00000018199A2928
    CPU Ticks used (ms) = 88442          Task State = 2                                                    
    WAITINFO_INTERNAL: WaitResource = 0x0000000000000000                      WAITINFO_INTERNAL: WaitType = 0x0      
    WAITINFO_INTERNAL: WaitSpinlock = 0x0000000000000000                      SchedulerId = 0x3                      
    ThreadId = 0x205c                    m_state = 0                          m_eAbortSev = 0                
    EC @0x00000010A909E730
    spid = 0                             ecid = 0                             ec_stat = 0x0          
    ec_stat2 = 0x0                       ec_atomic = 0x0                      ecType = 0                  
    __pSETLS = 0x0000001177F2D090        __pSEParams = 0x0000001177F2D520     
    SEInternalTLS @0x0000001177F2D090
    m_flags = 0                        
    m_TLSstatus = 3                    
    m_owningTask = 0x00000018199A2928     
    m_activeHeapDatasetList = 0x0000001177F2D090                                                  
    m_activeIndexDatasetList = 0x0000001177F2D0A0                            
    m_pDbccContext = 0x00000011DA40CED0   
    m_pAllocFileLimit = 0x0000000000000000                                  
    m_dekInstanceIndex = 0x-1             
    m_pImbiContext = 0x0000000000000000 
    SEParams @0x0000001177F2D520
    m_lockTimeout = -1                  
    m_isoLevel = 4096                  
    m_logDontReplicate = 0                
    m_neverReplicate = 0                
    m_XactWorkspace = 0x00000012508E3050                                       
    m_execStats = 0x00000015636D5CC8    

    Based on the dump contents, your SQL Server MDF database file is corrupt,  the possible solutions are based on the situation:
    1. If the corruption is not severe, then you can use the SQL Server build-in command DBCC CheckDB to correct the errors. See
    http://technet.microsoft.com/en-us/library/ms176064.aspx
    2. If the corruption is severe, then you may try some third party tools. The one I have tried successfully in the past is DataNumen SQL Recovery at
    http://www.datanumen.com/sql-recovery/ . You can use it to scan and recover the data from your corrupted MDF and NDF database files.
    Good luck!
    And what about restoring from backup ? That tool is of no use seriously have tried it.
    Restoring from valid backup is best option here dont go for tool its useless.
    Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
    My Technet Articles

  • Forms Runtime stack dump - MSVCRT.dll

    I'm having trouble with a Forms 5.0 app that I'm bringing up to Forms 6i. Whenever I try to run the form, I get a stack dump. I searched METALINK and found lots of people complaining of the same or similar problem, all in forum threads that have since been closed without anyone posting a solution. Has anyone experienced this? I'm desperate for a solution!
    I'm running Windows/NT Build 1381, SP6, but the problem also occurs on a Win2k workstation. I've tried uninstalling/reinstalling all the Oracle products on my workstation, and I've also tried loading various different versions of MSVCRT.dll into the WINNT/system32 folder. (This is a pain because Windows opens & locks the DLL.)
    Thanks in advance.
    -- Rob
    Here's the stack dump:
    ===========================================
    [05/28/02 15:42:47 Pacific Daylight Time]::Client Status [ConnId=0, PID=258]
         >> ERROR: Abnormal termination, Error Code: C0000005 ACCESS_VIOLATION
    ======================= STACK DUMP =======================
    Fault address: 78001C89 01:00000C89
    Module: C:\WINNT\system32\MSVCRT.dll
    System Information:
    Operating System: Windows NT Version 4.0 Build 1381 Service Pack 6
    Command line: "C:\Oracle\Developer6i\BIN\ifrun60.EXE" pcar1000.fmx
    FORM/BLOCK/FIELD: :.
    Last Trigger: - (No error number)
    Last Builtin: - (No error number)
    Registers:
    EAX:00357365
    EBX:0012EC4C
    ECX:00357365
    EDX:00000000
    ESI:00732C70
    EDI:FFFFFFFF
    CS:EIP:001B:78001C89
    SS:ESP:0023:0012EB18 EBP:0012EB30
    DS:0023 ES:0023 FS:0038 GS:0000
    Flags:00010202
    Call stack:
    Address Frame
    78001C89 0012EB30 strlen
    67241539 0012EBE0 uiwnzAdjustApiSize
    6723D1F8 0012ED6C uiwnc
    5DF5E2CE 038838E4 exiterr

    We are experiencing the same problem.
    O.S - Windows NT Ver 5.0 service pack 2
    Designer 6.5.88.4.0
    Repository 6.5.88.12.0
    Headstart 6.5
    Oracle 8.1.7.1.1
    The generated forms are running fine in web mode but crashes out when you run it in
    client-server mode. We have peformed all the recommendations in Headstart installation manual.
    Help us please..

  • Stack dump

    I'm running java in windows, using command prompt to execute programs. To get a stack dump, you can press ctrl-break in the dos box.
    Can someone tell me what exactly ctrl-break does apart from giving a stack dump. Does it change the stack or affect the current runtime of the program. In other words, does this command change the state of the currently executing program or is it a mere debugging tool that displays the current stack?
    thanx

    Just a debugging tool.
    - K

  • Stack dump: SQL Server keeps crushing

    My SQL Server keeps crushing with a stack dump error saying:
    (in the management studio error log):
    spid197    External dump process return code 0x20000001. External Dump process returned no errors.
    spid197   Stack signature for dump is 0x000000014A5D4200
    How can I investigate this further and what do these errors mean... also what does this return code mean and what does this signature dump code mean and where can I read more about them?
    Thanks in advance,
    Dror

    Support article on this and related errors:
    FIX: SQL Server 2012, SQL Server 2008 R2 or SQL Server 2008 stops responding and a "Non-yielding Scheduler" error is logged
    http://support.microsoft.com/kb/2699013
    Another support article:
    FIX: SQL Server 2005 or SQL Server 2008 may stop responding when you are performing a backup
    http://support.microsoft.com/kb/960543
    Also run DBCC CHECKDB to check for database corruption:
    http://social.msdn.microsoft.com/Forums/sqlserver/en-US/ea0099e9-3ad2-4713-8e4e-ca429041bf2d/sql-server-2008-r2-sp1-creates-dump-files-twice-a-minute-please-help?forum=sqldatabaseengine
    Kalman Toth Database & OLAP Architect
    SELECT Video Tutorials 4 Hours
    New Book / Kindle: Exam 70-461 Bootcamp: Querying Microsoft SQL Server 2012

  • Ifweb60.exe stack dump

    I turned on logging on my windows 2000 web server (log=...
    command). I'm now seeing a lot of stack dump errors in the log -
    several per day. Users have not been complaining (to me...).
    Any idea what to start looking at? They all reference
    ifweb60.exe;
    ======================= STACK DUMP =======================
    Fault address: 77E8F142 01:0000E142
    Module: C:\WINNT\system32\KERNEL32.dll
    System Information:
    Operating System: Windows NT Version 5.0 Build 2195 Service Pack
    2
    Command line: ifweb60.exe
    webfile=3708,440,163,PID9004,f60server.log
    FORM/BLOCK/FIELD: RPTTRAX:RPT_S_TRAX005.EQ_RELEASE_MILESTONE_TYPE
    Last Trigger: WHEN-WINDOW-ACTIVATED - (Successfully Completed)
    Msg: <NULL>
    Last Builtin: EXECUTE_TRIGGER - (Successfully Completed)

    ifweb60 is Oracle Forms60 Server, you can find it in the
    registery. If you don't need it, you can turn the server off
    from services( set it to manual), then it would not startup every
    time you reboot the box. If you need to keep it on, please refer
    to the forms documentations.
    Regards,
    --Tao                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               

  • /JVM/activeThreads.value shows 600+ active threads but stack dump shows 62

    In our production environment the dmstool reports 600+ active threads in our JVM but when I do a stack dump the number of threads adds up to 62. Is this normal? I would have thought that the stack dump would have shown the same number of threads (600) that the dmstool reported.
    In addition, the number of threads reported by the dmstool does not decrease much during non business hours. In fact, over multiple days it continues to grow. As it grows to this number, users report slower than normal response times throughout the application, although all functionality continues to work (no hanging). Could these 'missing' threads impact performance?
    Thank you

    jmap tool can print heap usage from core file.
    Ex:
    jmap -heap /your/jdk/java core.file
    For more info about jmap take a look at this.
    http://java.sun.com/j2se/1.5.0/docs/tooldocs/share/jmap.html

  • Resolve line numbers from a stack dump

    I have an application with a mutex dead lock. This program is compiled with CC and the flag �g.
    With pstack(pid) I get a proper stack dump with symbol names and hex addresses.
    Is there any way to resolve those hex addresses to line numbers from the source file?
    GNU got a tool named addr2line which solve this problem, is there any corresponding tools for Solaris 10?

    Don't know about addr2line analogue (maybe you can build it on Solaris, too), but there's always an option to use dbx:
    - attach to the process with 'dbx - pid'
    - issue 'where' in dbx console

  • Timeout Short Dump on a Data Query to a blank table.

    Hi,
    My program gives a short dump on quering a blank table. The dump says timeout.
    what could the possible problem be.
    regards,

    Runtime Error          TIME_OUT                                                       
           Occurred on     02/19/2009 at   10:35:35                                                                               
    Time limit exceeded.                                                                               
    What happened?                                                                               
    The program "SAPLE31C" has exceeded the maximum permitted runtime without             
    interruption, and has therefore been terminated.                                                                               
    What can you do?                                                                               
    Print out the error message (using the "Print" function)                              
    and make a note of the actions and input that caused the                              
    error.                                                                               
    To resolve the problem, contact your SAP system administrator.                        
    You can use transaction ST22 (ABAP Dump Analysis) to view and administer              
    termination messages, especially those beyond their normal deletion                  
    date.                                                                               
    Error analysis                                                                               
    After a certain length of time, the program is terminated. In the case                
    of a work area, this means that                                                       
    - endless loops (DO, WHILE, ...),                                                     
    - database accesses producing an excessively large result set,                        
    - database accesses without a suitable index (full table scan)                                                                               
    do not block the processing for too long.                                                                               
    The system profile "rdisp/max_wprun_time" contains the maximum runtime of a
    program. The                                                              
    current setting is 5400 seconds. Once this time limit has been exceeded,   
    the system tries to terminate any SQL statements that are currently        
    being executed and tells the ABAP processor to terminate the current       
    program. Then it waits for a maximum of 60 seconds. If the program is      
    still active, the work process is restarted.                                                                               
    successfully processed, the system gives it another 5400 seconds.          
    Hence the maximum runtime of a program is at least twice the value of      
    the system profile parameter "rdisp/max_wprun_time".                                                                               
    How to correct the error                                                                               
    You should usually execute long-running programs as batch jobs.            
    If this is not possible, increase the system profile parameter             
    "rdisp/max_wprun_time".                                                                               
    Depending on the cause of the error, you may have to take one of the       
    following measures:                                                        
    - Endless loop: Correct program;                                           
    - Dataset resulting from database access is too large:                     
      Instead of "SELECT * ... ENDSELECT", use "SELECT * INTO internal table   
      (for example);                                                           
    - Database has an unsuitable index: Check index generation.                                                                               
    You may able to find an interim solution to the problem                    
    ~~~~~~~
    The line to which it points is a select query on a table that has not records.

Maybe you are looking for

  • Update for Acrobat 9 Pro Extended and Catia V5 R22

    Hello ... We are using Adobe Acrobat 9 Pro Extended (now at version 9.5.4) at our company for converting CatPart-Files to 3dPDF ... Now we've got Catia V5 R22 (V5R62012) Files here and the converter can't read them ... Will there be an update and whe

  • How to unlock memory card

    Depending on the memory card you are using, there is a lock switch located at the side or the back that you can use to unlock the memory card. Please refer to the illustration below for more information. If my post answers your question, please mark

  • Outlook email date format

    Im running Outlook v 14.3.9. In the email I can only get date as month/day/year.  How do I change to get day/month/year? Many thanks JohnC

  • Convert PDF or other format to PDF/A

    Hello, I have some questions about converting to PDF/A using Adobe Acrobat 9 Pro I want to know if it is possible to convert PDF-documents or other 'image-documents' to PDF/A. Via advanced - Prefligt you can convert separate PDF-documents into PDF/A-

  • Error in ALPHA conversion

    Hi experts, I am loading a hierarchy for a infoobject. When I execute the infopackage, the monitor show me the next error:  Error in ALPHA conversion in NodeId00000009 for Infoobjetc 0CUSTOMER. Can anybody hepl me?