Home > Default > SQL 2005 x64 exception

SQL 2005 x64 exception

November 30Hits:1
Recently We've migrated SQL 2005 x86 Enterprise running on Windows 2003 Enterprise to new hardware where is running Windows 2008 SP2 and SQL 2005 x64 SP4 with CU3. We migrate users (with standard approach by Microsoft) and application databases
to new server. Everything is looking ok, applications working. But we've got some SQL exceptions like below.
Is there any known bug related to that? Could someone help us.
MemoryLoad = 15%                    
Total Physical = 32733 MB           
Available Physical = 27752 MB       
Total Page File = 64782 MB          
Available Page File = 60344 MB      
Total Virtual = 8388607 MB          
Available Virtual = 8355366 MB      
**Dump thread - spid = 84, PSS = 0x00000000D1A43ED0, EC = 0x00000000D1A43EE0                                    
***Stack Dump being sent to D:\MSSQL.1\MSSQL\LOG\SQLDump0005.txt                                                
* BEGIN STACK DUMP:                                                                                             
*   04/25/14 12:54:30 spid 84                                                                                   
* ex_handle_except encountered exception C0000264 - Server terminating                                          
* Input Buffer 255 bytes - 
There is also some output from debugger:
0:000> .ecxr
rax=0000000077207080 rbx=0000000000000000 rcx=0000000016a37d50
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000440
rip=00000000772070bd rsp=0000000016a38240 rbp=000000000000003f
 r8=0000000000000000  r9=0000000000000000 r10=0000000000000000
r11=0000000000000287 r12=00000000032fdab0 r13=0000000000000000
r14=00000000000019e4 r15=0000000049b8d00c
iopl=0         nv up ei pl nz na po nc
cs=0033  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00000206
00000000`772070bd 4881c4c8000000  add     rsp,0C8h
0:000> kC 1000
Call Site


In last days we "close" our SQL to some scanning security applications which could also do some things on our SQL. But it's only a guess. About sqlshield we do the unregister and register DLL's again. Now at last two exception is not the same situation.
Can you see something from there with "Non-yielding Scheduler". Is it also possible that it something wrong with the hardware. We're using new Cisco rack 1U server for that SQL server. I've also read someting about upgrading the BIOS, related to errors
"Non-yielding Scheduler". At the end i can also tell, that the server is alive for a couple of days, if there is no a lot activity on the server, i mean on national holidays, through weekend, etc.
Any new idea?
       BugCheck Dump                                                                                            
This file is generated by Microsoft SQL Server                                                                  
version 9.00.5266.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 Cisco0 - 0                                                                                      
BIOS Date: 08/20/13 06:01:31 Ver: 04.06.05                                                                      
Current time is 11:17:16 04/30/14.                                                                              
12 Unknown CPU 9., 14 Mhz processor (s).                                                                        
Windows NT 6.0 Build 6002 CSD Service Pack 2.                                                                   
MemoryLoad = 17%                    
Total Physical = 32733 MB           
Available Physical = 26900 MB       
Total Page File = 64782 MB          
Available Page File = 59543 MB      
Total Virtual = 8388607 MB          
Available Virtual = 8355342 MB      
***Unable to get thread context - no pss                                                                        
* BEGIN STACK DUMP:                                                                                             
*   04/30/14 11:17:16 spid 0                                                                                    
* Non-yielding Scheduler                                                                                        
Stack Signature for the dump is 0x00000000000003AD          

Read other 14 answers


Related Articles

  • SQL 2005 x64 exceptionNovember 30

    Recently We've migrated SQL 2005 x86 Enterprise running on Windows 2003 Enterprise to new hardware where is running Windows 2008 SP2 and SQL 2005 x64 SP4 with CU3. We migrate users (with standard approach by Microsoft) and application databases to ne

  • SQL 2005 x64 poor performance after migration from SQL 2005 x86November 30

    Recently We've migrated SQL 2005 x86 SP1 Enterprise running on Windows 2003 Enterprise to new hardware where is running Windows 2008 SP2 and SQL 2005 x64 SP4 with CU3. In the work day, there are sometime SQL excpetions like this below. On other hand

  • MS SQL 2005 x64 Linked Server to Oracle 10g 32bitNovember 30

    I need to connect to a Oracle DB from a SQL Server 2005 x64 on W2003. The Instant Client installed is with ODP, which is used to connect to another Oracle DB. I get de error ORA-12154 while doing the linked server query. Do

  • OraOLEDB.Oracle on x64 Win 2003 connect to Oracle 9.2 from SQL 2005 x64November 30

    I know this is an Oracle board but some of you may also support SQL Server like I do and I am hoping someone has had the pleasure of using OraOLEDB.Oracle on 64 bit. I have a 64 bit SQL Server 2005 SP2 on a Windows 2003 x64. The developer said that h

  • SQL Server Error when tryingt to install the CMS DB on SQL Server 2005 x64October 11

    I am trying to install BOEXI R3 on w2k3 64-bit OS in a SQL Server 2005 x64 database, I am currently at the installation step where i Specify an exisiting CMS database. I created a System DSN and tested it, and it was successful. So when I got to the

  • Netweaver 7.0 SR3 install - x64 - Windows 2003(64-bit)/MS SQL 2005November 30

    I want to install Netweaver 7.0 SR3 on 64-Bit Windows 2003 Enterprise server with a SQL 2005 backend. I downloaded packages 51033323_1, 51033323_2 & 51033323_3 and started the sapinst.exe utility in the 51033323_1\IM_WINDOWS_I386 directory. I get the

  • Upgrade R/3 4.7 110 from SQL 2000 to ECC 6.0 /SQL 2005October 11

    Dear Experts, We are currently running R/3 4.7 110 with kernel 640 32 Bit Non Unicode on Windows Server 2000/ MS SQL 2000 Platform. We are planning to Upgrade the same to ECC 6.0 on Windows 2003/ SQL 2005 on New x64 Bit Hardware. I was earlier planni

  • Can SQL 2000 and SQL 2005 drivers co-exist in PI?November 30

    Hi, Currently in our PI environment, we have JDBC Adapter connections to SQL 2000 database servers for which the Driver has already been installed. For connecting to new SQL 2005 database servers, I understand that we have to install the SQL 2005 dri

  • SQL 2005 fixed memoryNovember 30

    Hi , I have SAP 47X200 on SQL2005 64-bit installed on Windows enterprise edition X64. I have installed database software using SQL4SAP.vbs as decrived in the installation guide : all OK , all work fine. But , I want to use SQL 2005 with fixed memory

  • The acount information could not be verified - SQL 2005 SP3 installation on Windows 2008 R2 Failover ClusterNovember 30

    Hi, We have a problem when we are trying to install SQL SP3 on SQL 2005 cluster. The problem is described bellow: We installed a new Windows 2008 R2 x64 failover cluster with two nodes. As a next step we installed SQL 2005 Enterprise edition x64 on t

Copyright (C) 2019 wisumpire.com, All Rights Reserved. webmaster#wisumpire.com 14 q. 0.694 s.