I had SQL Server Personal edition on my Windows XP
Professional client computer and something happened
yesterday when the network people push down Antivirus
update. Now when I try to connect other SQL Servers on the
network, it takes too long and I keep hearing raddling
disk noise.
I have the following error messages on my Event viewer:
Hanging application mmc.exe, version 5.1.2600.0, hang
module hungapp, version 0.0.0.0, hang address 0x00000000.
also
Hanging application isqlw.exe, version 2000.80.194.0, hang
module hungapp, version 0.0.0.0, hang address 0x00000000.
Is there anyone else has experienced this.
Thanks for any feedback.I'd run a ScanDisk ... peculiar noises from any disks are usually not good.
Showing posts with label edition. Show all posts
Showing posts with label edition. Show all posts
Friday, March 23, 2012
MMC.EXE -Application Error
--Using SQL Server 2000 standard edition with SP3 on Windows 2000 Server
I am getting an error when I try to copy the data from a table to a text fil
e using a DTS Package. I am simply creating a connection to the database (s
ource) where the table exists and then creating another connection to the te
xt file (destination). The
properties of the text file are comma for the column delimiter, double quote
s for the text qualifers and first row contains column names. So after crea
ting the two connections I then create the 'Transform Data Task' (black arro
w going from the source to
the destination). I then go to the properties of the 'Transform Data Task'.
On the 'Source' tab I select the table I want to copy. I can preview the
data with no problems. I then click on the 'Destination' tab to define the
colmns. I click 'populate
from source' (it populates from the source) and then click 'execute'. This
is where the problem happens. It doesn't define the columns in the 'Destina
tion' tab. It is blank in the white space below. When I click the 'Define
Columns' button to try def
ine the columns again, I receive the following error in a pop up window:
In the Title Bar of the pop up window it says: MMC.EXE - Application Error
In the main part of the window it says: The instruction at 0x4173d23a" refe
renced memory at "0x01521e90". The memory could not be "written". Click on
OK to terminate the program
I click OK, and then it boots me out of Enterprise Manager.
In the 'disconnected edit' properties for the text file destination connecti
on, I have set the OLE DB Properties 'max characters per delimited column' f
rom 255 to 8000 to set if that is the problem since I have some columns that
are varchar 255. Still ge
t the same error.
I appreciate any help in advance to try resolving this problem.This error occurs when you apply SP3 or SP3a to your server. Article 814113
addresses this problem and then tells you to go to article 821277 for the p
atch downloads. You have to apply a cumulative security patch which creates
a problem with passwords o
n sql logins so you have to apply a small patch to fix that. I applied both
hotfixes in a test environment and it fixed the error. Hopefully it doesn'
t break anything else. Also, you have to apply these hotfixes to sql server
2000 with SP3 or SP3a and
also to workstations who are just running the client.
"IKE" wrote:
> --Using SQL Server 2000 standard edition with SP3 on Windows 2000 Server
> I am getting an error when I try to copy the data from a table to a text file usin
g a DTS Package. I am simply creating a connection to the database (source) where t
he table exists and then creating another connection to the text file (destination).
T
he properties of the text file are comma for the column delimiter, double qu
otes for the text qualifers and first row contains column names. So after c
reating the two connections I then create the 'Transform Data Task' (black a
rrow going from the source
to the destination). I then go to the properties of the 'Transform Data Tas
k'. On the 'Source' tab I select the table I want to copy. I can preview t
he data with no problems. I then click on the 'Destination' tab to define t
he colmns. I click 'popula
te from source' (it populates from the source) and then click 'execute'. Th
is is where the problem happens. It doesn't define the columns in the 'Dest
ination' tab. It is blank in the white space below. When I click the 'Defi
ne Columns' button to try d
efine the columns again, I receive the following error in a pop up window:
> In the Title Bar of the pop up window it says: MMC.EXE - Application Erro
r
> In the main part of the window it says: The instruction at 0x4173d23a" re
ferenced memory at "0x01521e90". The memory could not be "written". Click
on OK to terminate the program
> I click OK, and then it boots me out of Enterprise Manager.
> In the 'disconnected edit' properties for the text file destination connection, I
have set the OLE DB Properties 'max characters per delimited column' from 255 to 800
0 to set if that is the problem since I have some columns that are varchar 255. Sti
ll
get the same error.
> I appreciate any help in advance to try resolving this problem.
>
>
I am getting an error when I try to copy the data from a table to a text fil
e using a DTS Package. I am simply creating a connection to the database (s
ource) where the table exists and then creating another connection to the te
xt file (destination). The
properties of the text file are comma for the column delimiter, double quote
s for the text qualifers and first row contains column names. So after crea
ting the two connections I then create the 'Transform Data Task' (black arro
w going from the source to
the destination). I then go to the properties of the 'Transform Data Task'.
On the 'Source' tab I select the table I want to copy. I can preview the
data with no problems. I then click on the 'Destination' tab to define the
colmns. I click 'populate
from source' (it populates from the source) and then click 'execute'. This
is where the problem happens. It doesn't define the columns in the 'Destina
tion' tab. It is blank in the white space below. When I click the 'Define
Columns' button to try def
ine the columns again, I receive the following error in a pop up window:
In the Title Bar of the pop up window it says: MMC.EXE - Application Error
In the main part of the window it says: The instruction at 0x4173d23a" refe
renced memory at "0x01521e90". The memory could not be "written". Click on
OK to terminate the program
I click OK, and then it boots me out of Enterprise Manager.
In the 'disconnected edit' properties for the text file destination connecti
on, I have set the OLE DB Properties 'max characters per delimited column' f
rom 255 to 8000 to set if that is the problem since I have some columns that
are varchar 255. Still ge
t the same error.
I appreciate any help in advance to try resolving this problem.This error occurs when you apply SP3 or SP3a to your server. Article 814113
addresses this problem and then tells you to go to article 821277 for the p
atch downloads. You have to apply a cumulative security patch which creates
a problem with passwords o
n sql logins so you have to apply a small patch to fix that. I applied both
hotfixes in a test environment and it fixed the error. Hopefully it doesn'
t break anything else. Also, you have to apply these hotfixes to sql server
2000 with SP3 or SP3a and
also to workstations who are just running the client.
"IKE" wrote:
> --Using SQL Server 2000 standard edition with SP3 on Windows 2000 Server
> I am getting an error when I try to copy the data from a table to a text file usin
g a DTS Package. I am simply creating a connection to the database (source) where t
he table exists and then creating another connection to the text file (destination).
T
he properties of the text file are comma for the column delimiter, double qu
otes for the text qualifers and first row contains column names. So after c
reating the two connections I then create the 'Transform Data Task' (black a
rrow going from the source
to the destination). I then go to the properties of the 'Transform Data Tas
k'. On the 'Source' tab I select the table I want to copy. I can preview t
he data with no problems. I then click on the 'Destination' tab to define t
he colmns. I click 'popula
te from source' (it populates from the source) and then click 'execute'. Th
is is where the problem happens. It doesn't define the columns in the 'Dest
ination' tab. It is blank in the white space below. When I click the 'Defi
ne Columns' button to try d
efine the columns again, I receive the following error in a pop up window:
> In the Title Bar of the pop up window it says: MMC.EXE - Application Erro
r
> In the main part of the window it says: The instruction at 0x4173d23a" re
ferenced memory at "0x01521e90". The memory could not be "written". Click
on OK to terminate the program
> I click OK, and then it boots me out of Enterprise Manager.
> In the 'disconnected edit' properties for the text file destination connection, I
have set the OLE DB Properties 'max characters per delimited column' from 255 to 800
0 to set if that is the problem since I have some columns that are varchar 255. Sti
ll
get the same error.
> I appreciate any help in advance to try resolving this problem.
>
>
MMC.EXE -Application Error
--Using SQL Server 2000 standard edition with SP3 on Windows 2000 Server
I am getting an error when I try to copy the data from a table to a text file using a DTS Package. I am simply creating a connection to the database (source) where the table exists and then creating another connection to the text file (destination). The
properties of the text file are comma for the column delimiter, double quotes for the text qualifers and first row contains column names. So after creating the two connections I then create the 'Transform Data Task' (black arrow going from the source to
the destination). I then go to the properties of the 'Transform Data Task'. On the 'Source' tab I select the table I want to copy. I can preview the data with no problems. I then click on the 'Destination' tab to define the colmns. I click 'populate
from source' (it populates from the source) and then click 'execute'. This is where the problem happens. It doesn't define the columns in the 'Destination' tab. It is blank in the white space below. When I click the 'Define Columns' button to try def
ine the columns again, I receive the following error in a pop up window:
In the Title Bar of the pop up window it says: MMC.EXE - Application Error
In the main part of the window it says: The instruction at 0x4173d23a" referenced memory at "0x01521e90". The memory could not be "written". Click on OK to terminate the program
I click OK, and then it boots me out of Enterprise Manager.
In the 'disconnected edit' properties for the text file destination connection, I have set the OLE DB Properties 'max characters per delimited column' from 255 to 8000 to set if that is the problem since I have some columns that are varchar 255. Still ge
t the same error.
I appreciate any help in advance to try resolving this problem.
This error occurs when you apply SP3 or SP3a to your server. Article 814113 addresses this problem and then tells you to go to article 821277 for the patch downloads. You have to apply a cumulative security patch which creates a problem with passwords o
n sql logins so you have to apply a small patch to fix that. I applied both hotfixes in a test environment and it fixed the error. Hopefully it doesn't break anything else. Also, you have to apply these hotfixes to sql server 2000 with SP3 or SP3a and
also to workstations who are just running the client.
"IKE" wrote:
> --Using SQL Server 2000 standard edition with SP3 on Windows 2000 Server
> I am getting an error when I try to copy the data from a table to a text file using a DTS Package. I am simply creating a connection to the database (source) where the table exists and then creating another connection to the text file (destination). T
he properties of the text file are comma for the column delimiter, double quotes for the text qualifers and first row contains column names. So after creating the two connections I then create the 'Transform Data Task' (black arrow going from the source
to the destination). I then go to the properties of the 'Transform Data Task'. On the 'Source' tab I select the table I want to copy. I can preview the data with no problems. I then click on the 'Destination' tab to define the colmns. I click 'popula
te from source' (it populates from the source) and then click 'execute'. This is where the problem happens. It doesn't define the columns in the 'Destination' tab. It is blank in the white space below. When I click the 'Define Columns' button to try d
efine the columns again, I receive the following error in a pop up window:
> In the Title Bar of the pop up window it says: MMC.EXE - Application Error
> In the main part of the window it says: The instruction at 0x4173d23a" referenced memory at "0x01521e90". The memory could not be "written". Click on OK to terminate the program
> I click OK, and then it boots me out of Enterprise Manager.
> In the 'disconnected edit' properties for the text file destination connection, I have set the OLE DB Properties 'max characters per delimited column' from 255 to 8000 to set if that is the problem since I have some columns that are varchar 255. Still
get the same error.
> I appreciate any help in advance to try resolving this problem.
>
>
I am getting an error when I try to copy the data from a table to a text file using a DTS Package. I am simply creating a connection to the database (source) where the table exists and then creating another connection to the text file (destination). The
properties of the text file are comma for the column delimiter, double quotes for the text qualifers and first row contains column names. So after creating the two connections I then create the 'Transform Data Task' (black arrow going from the source to
the destination). I then go to the properties of the 'Transform Data Task'. On the 'Source' tab I select the table I want to copy. I can preview the data with no problems. I then click on the 'Destination' tab to define the colmns. I click 'populate
from source' (it populates from the source) and then click 'execute'. This is where the problem happens. It doesn't define the columns in the 'Destination' tab. It is blank in the white space below. When I click the 'Define Columns' button to try def
ine the columns again, I receive the following error in a pop up window:
In the Title Bar of the pop up window it says: MMC.EXE - Application Error
In the main part of the window it says: The instruction at 0x4173d23a" referenced memory at "0x01521e90". The memory could not be "written". Click on OK to terminate the program
I click OK, and then it boots me out of Enterprise Manager.
In the 'disconnected edit' properties for the text file destination connection, I have set the OLE DB Properties 'max characters per delimited column' from 255 to 8000 to set if that is the problem since I have some columns that are varchar 255. Still ge
t the same error.
I appreciate any help in advance to try resolving this problem.
This error occurs when you apply SP3 or SP3a to your server. Article 814113 addresses this problem and then tells you to go to article 821277 for the patch downloads. You have to apply a cumulative security patch which creates a problem with passwords o
n sql logins so you have to apply a small patch to fix that. I applied both hotfixes in a test environment and it fixed the error. Hopefully it doesn't break anything else. Also, you have to apply these hotfixes to sql server 2000 with SP3 or SP3a and
also to workstations who are just running the client.
"IKE" wrote:
> --Using SQL Server 2000 standard edition with SP3 on Windows 2000 Server
> I am getting an error when I try to copy the data from a table to a text file using a DTS Package. I am simply creating a connection to the database (source) where the table exists and then creating another connection to the text file (destination). T
he properties of the text file are comma for the column delimiter, double quotes for the text qualifers and first row contains column names. So after creating the two connections I then create the 'Transform Data Task' (black arrow going from the source
to the destination). I then go to the properties of the 'Transform Data Task'. On the 'Source' tab I select the table I want to copy. I can preview the data with no problems. I then click on the 'Destination' tab to define the colmns. I click 'popula
te from source' (it populates from the source) and then click 'execute'. This is where the problem happens. It doesn't define the columns in the 'Destination' tab. It is blank in the white space below. When I click the 'Define Columns' button to try d
efine the columns again, I receive the following error in a pop up window:
> In the Title Bar of the pop up window it says: MMC.EXE - Application Error
> In the main part of the window it says: The instruction at 0x4173d23a" referenced memory at "0x01521e90". The memory could not be "written". Click on OK to terminate the program
> I click OK, and then it boots me out of Enterprise Manager.
> In the 'disconnected edit' properties for the text file destination connection, I have set the OLE DB Properties 'max characters per delimited column' from 255 to 8000 to set if that is the problem since I have some columns that are varchar 255. Still
get the same error.
> I appreciate any help in advance to try resolving this problem.
>
>
Wednesday, March 21, 2012
MMC 3.0 and SQL 2000
I am to install MMC 3.0 to a server (Server 2003 Standard Edition SP1) with
SQL 2000 Sp4. I would like to know if Server Enterprise Manager works under
MMC 3.0.
--
Regards
Rasmus SöderlundHi Rasmus
EM seems to work fine with MMC 3.0
John
"Rasmus" wrote:
> I am to install MMC 3.0 to a server (Server 2003 Standard Edition SP1) with
> SQL 2000 Sp4. I would like to know if Server Enterprise Manager works under
> MMC 3.0.
> --
> Regards
>
> Rasmus Söderlund
SQL 2000 Sp4. I would like to know if Server Enterprise Manager works under
MMC 3.0.
--
Regards
Rasmus SöderlundHi Rasmus
EM seems to work fine with MMC 3.0
John
"Rasmus" wrote:
> I am to install MMC 3.0 to a server (Server 2003 Standard Edition SP1) with
> SQL 2000 Sp4. I would like to know if Server Enterprise Manager works under
> MMC 3.0.
> --
> Regards
>
> Rasmus Söderlund
Monday, March 19, 2012
Mixed environments - SQL 2000 Standard & Enterprise?
We are upgrading a production database server to new hardware. The server is currently running SQL Server 2000 Standard Edition. We are thinking about installing SQL Server 2000 Enterprise Edition, however that would mean the test server (2000 Standard) and production server (2000 Enterprise) have different edtions of SQL Server. How much of a risk does this present? Later in the year we would upgrade test to SQL Server 2000 EE, but for a couple of months the environments would be different.
Thanks, DaveThere would be no side-effect for going from std to ent at all.|||The only problem I can forsee would be if you use a feature that only exists in Enterprise Edition. Most of the ones I can think of off the top of my head do not affect code, though (clustering, log shipping).|||I would use the SQL Server Dev Edition for the test environment since it has the full functionality as SQL Server Ent like log shipping.
Thanks, DaveThere would be no side-effect for going from std to ent at all.|||The only problem I can forsee would be if you use a feature that only exists in Enterprise Edition. Most of the ones I can think of off the top of my head do not affect code, though (clustering, log shipping).|||I would use the SQL Server Dev Edition for the test environment since it has the full functionality as SQL Server Ent like log shipping.
Monday, March 12, 2012
Missing table log_shipping_monitor table
We upgraded SQL Server from standard to enterprise edition. When attempting to setup a maintenance plan we got an error 208: Invalid object name: msdb.dbo.log_shipping_monitor.
The table log_shipping_monitor doesn't exist in the msdb database.
Any ideas?
what happens if you appy/re-apply the latest sp.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"John M. Snarski" <John M. Snarski@.discussions.microsoft.com> wrote in
message news:8C1CFC6B-49B9-44A9-8FDC-E5A463C6E1D7@.microsoft.com...
> We upgraded SQL Server from standard to enterprise edition. When
attempting to setup a maintenance plan we got an error 208: Invalid object
name: msdb.dbo.log_shipping_monitor.
> The table log_shipping_monitor doesn't exist in the msdb database.
> Any ideas?
|||no change
"Hilary Cotter" wrote:
> what happens if you appy/re-apply the latest sp.
> --
> Hilary Cotter
> Looking for a book on SQL Server replication?
> http://www.nwsu.com/0974973602.html
>
> "John M. Snarski" <John M. Snarski@.discussions.microsoft.com> wrote in
> message news:8C1CFC6B-49B9-44A9-8FDC-E5A463C6E1D7@.microsoft.com...
> attempting to setup a maintenance plan we got an error 208: Invalid object
> name: msdb.dbo.log_shipping_monitor.
>
>
The table log_shipping_monitor doesn't exist in the msdb database.
Any ideas?
what happens if you appy/re-apply the latest sp.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"John M. Snarski" <John M. Snarski@.discussions.microsoft.com> wrote in
message news:8C1CFC6B-49B9-44A9-8FDC-E5A463C6E1D7@.microsoft.com...
> We upgraded SQL Server from standard to enterprise edition. When
attempting to setup a maintenance plan we got an error 208: Invalid object
name: msdb.dbo.log_shipping_monitor.
> The table log_shipping_monitor doesn't exist in the msdb database.
> Any ideas?
|||no change
"Hilary Cotter" wrote:
> what happens if you appy/re-apply the latest sp.
> --
> Hilary Cotter
> Looking for a book on SQL Server replication?
> http://www.nwsu.com/0974973602.html
>
> "John M. Snarski" <John M. Snarski@.discussions.microsoft.com> wrote in
> message news:8C1CFC6B-49B9-44A9-8FDC-E5A463C6E1D7@.microsoft.com...
> attempting to setup a maintenance plan we got an error 208: Invalid object
> name: msdb.dbo.log_shipping_monitor.
>
>
Friday, March 9, 2012
Missing SQL Server Project template
I have VS2005 Beta 2 (build 8.0.50215.44) and the June CTP of SQL Server 2005 Developer Edition installed.
Many thanks.
|||Nevermind. I have VS.Net 2005 Beta2 and didn't notice that if I expanded the Visual C# under the project types tree, there was a database node which contained the "SQL Server" project template.
Take care.
Within VS2005, when I go to File -> New Project, I don't have the "Database" project type under either VB or C#. Which also means that the "SQL Server Project" template is not being offered.
Is there a manual way of adding the template, or some other workaround/solution?
Which SKU of Visual Studio are you using? Visual Studio Express does not have SQL Server project support.
Thanks,
-Vineet.
Many thanks.
|||Nevermind. I have VS.Net 2005 Beta2 and didn't notice that if I expanded the Visual C# under the project types tree, there was a database node which contained the "SQL Server" project template.
Take care.
missing SQL Server Agent
Hi,
I'm learning SQL 2005 and installed the express ADV edition to my pc. But I miss the Agent service.
Is this included in express? Has it another name after SQL server 2000?
thanks
majid
Looking at the edition comparison page (http://www.microsoft.com/sql/prodinfo/features/compare-features.mspx), it looks like SQL Agent Job Scheduling Service only comes with Workgroup, Standard, and Enterprise.Thanks,
Sam Lester (MSFT)|||
oh, I see, Thanx
majid
Wednesday, March 7, 2012
Missing ODBC Driver
I have a Windows 2000 development server with multiple instance of SQL Server 2000 Dev Edition installed. Recently, i encounter an error on Enterpise Manager.
"A connection could not be established to SERVERNAME\INSTANCENAME.
Reason : Data source name not found and no default driver specified.
Please verify SQL Server is running and check your SQL Server registration properties(by right-clicking on the SERVERNAME\INSTANCENAME node) and try again."
I tried to use Query Analyser on the server to connect to instance. And receive this error
"Unable to connect to server SERVERNAME\INSTANCENAME:
ODBC: Msg 0, Level 16, State 1
[Microsoft][ODBC Driver Manager]Data source name not found and no default driver specified"
I tried connecting using IPAddr\InstanceName and it return the same error.
But if I use another machine (not the Development Server), I can connect to the instance sucessfully using Query Analyser.
Opening up the ODBC Data Source Adminsitrator, under the Drivers tab page, it is empty. So I tried re-installing MDAC 2.8 and also SP1, the installation completed sucessfully but the drivers is still missing. Tried searching on the MSDN site, shows, ODBC Driver cannot be un-installed.
Anybody can help on this ?
Have you changed anyhting on your PC recently? Any updates to the Windows or server? Have you tried to run Component Checker that comes with MDAC to see what could be corrupted in MDAC installation?|||Component Checker reported that I have MDAC 2.8 SP1 ON WINDOWS XP SP2.
But my OS is Windows 2000 SP4|||Does it show any error for the installed drivers/providers?|||I ran the check against the SP and it shows 3 files with mismatch
File : odbcjt32.dll
Mixmatch Fields : Expected : version = 4.0.6304.0
Path : C:\WINNT\system32\
Version : 4.0.6200.0
FileVersion : 4.06200.0
FileDescription : Microsoft ODBC Desktop Driver Pack 3.5
CodePage : 1252
Size : 270608
Date : 06/19/2003
File : msxml3.dll
Mixmatch Fields : Expected : version = 8.50.2162.0
Path : C:\WINNT\system32\
Version : 8.70.1104.0
FileVersion : 8.70.1104.0
FileDescription : MSXML 3.0 SP7
CodePage : 1200
Size : 1049088
Date : 02/18/2005
File : odbcji32.dll
Mixmatch Fields : Expected : version = 4.0.6304.0
Path : C:\WINNT\system32\
Version : 4.0.6200.0
FileVersion : 4.06200.0
FileDescription : Microsoft ODBC Desktop Driver Pack 3.5
CodePage : 1252
Size : 53520
Date : 07/22/2002|||I ran the check against "MDAC 2.8 SP1 ON WINDOWS XP SP2."|||Is the problem i am facing related to SQL Server Data Access or should i post this in Windows 2000 forum instead ?|||It is more related to the Windows installation rather than Data Access to SQL Server. In my opinion MDAC is corrupted somehow|||Thanks for replying.
Saturday, February 25, 2012
Missing Join Predicate error
All,
We did an inplace upgrade of our "SQLServer 2000 SP3a" production server to
"SQLServer 2005 SP2 Enterprise Edition" on saturday. The system has 8 CPUs
and 4GB of RAM. This evening, the server crashed and I had to reboot the box.
I checked the eventvwr and this is what I get. I also found a stack dump in
the log. I checked the blackbox trace for any signs and I found "MIssing Join
Predicate" in the EventClass for one of the databases. This leads me to
believe that this is the reason why SQLServer crashed though we never
encountered this problem in the SQLServer 2000 installation before we
upgraded -- the application has been working fine without any problem over
the past several years. I could have trouble shooted this issue more but
unfortunately the text of the code that resulted in the "MIssing Join
Predicate" is empty in the Text column.
Event Type:Error
Event Source:MSSQLSERVER
Event Category:(2)
Event ID:17311
Date:1/14/2008
Time:5:59:11 PM
User:N/A
Computer:ENSQLP2
Description:
SQL Server is terminating because of fatal exception c0000005. This error
may be caused by an unhandled Win32 or C++ exception, or by an access
violation encountered during exception handling. Check the SQL error log for
any related stack dumps or messages. This exception forces SQL Server to
shutdown. To recover from this error, restart the server (unless SQLAgent is
configured to auto restart).
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 9f 43 00 00 10 00 00 00 ?C.....
0008: 08 00 00 00 45 00 4e 00 ...E.N.
0010: 53 00 51 00 4c 00 50 00 S.Q.L.P.
0018: 32 00 00 00 00 00 00 00 2......
Has anyone encountered this problem before? I will start a user defined
trace and get to the core tomorrow. Neverthless, I was wondering if anyone
has encountered this issue before
Here is the stack dump. Note that at this point I also dont know which
query/SP caused the crash.
================================================== ===================
BugCheck Dump
================================================== ===================
This file is generated by Microsoft SQL Server
version 9.00.3042.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 HP - 2
Current time is 17:59:12 01/14/08.
8 Intel x86 level 15, 2833 Mhz processor (s).
Windows NT 5.2 Build 3790 CSD Service Pack 1.
Memory
MemoryLoad = 51%
Total Physical = 4094 MB
Available Physical = 1986 MB
Total Page File = 10069 MB
Available Page File = 7980 MB
Total Virtual = 2047 MB
Available Virtual = 217 MB
**Dump thread - spid = 0, PSS = 0x00000000, EC = 0x00000000
***Stack Dump being sent to e:\MSSQL\MSSQL\LOG\SQLDump0005.txt
*
************************************************** *****************************
*
* BEGIN STACK DUMP:
* 01/14/08 17:59:12 spid 0
*
* ex_handle_except encountered exception C0000005 - Server terminating
*
*
* MODULE BASE END SIZE
* sqlservr 01000000 02C09FFF 01c0a000
* ntdll 7C800000 7C8BFFFF 000c0000
* kernel32 77E40000 77F41FFF 00102000
* MSVCR80 78130000 781CAFFF 0009b000
* msvcrt 77BA0000 77BF9FFF 0005a000
* MSVCP80 7C420000 7C4A6FFF 00087000
* ADVAPI32 77F50000 77FEBFFF 0009c000
* RPCRT4 77C50000 77CEEFFF 0009f000
* USER32 77380000 77411FFF 00092000
* GDI32 77C00000 77C48FFF 00049000
* CRYPT32 761B0000 76242FFF 00093000
* MSASN1 76190000 761A1FFF 00012000
* Secur32 76F50000 76F62FFF 00013000
* MSWSOCK 71B20000 71B60FFF 00041000
* WS2_32 71C00000 71C16FFF 00017000
* WS2HELP 71BF0000 71BF7FFF 00008000
* USERENV 76920000 769E3FFF 000c4000
* opends60 333E0000 333E6FFF 00007000
* NETAPI32 71C40000 71C97FFF 00058000
* SHELL32 7C8D0000 7D0D3FFF 00804000
* SHLWAPI 77DA0000 77DF1FFF 00052000
* comctl32 77420000 77522FFF 00103000
* psapi 76B70000 76B7AFFF 0000b000
* instapi 48060000 48069FFF 0000a000
* sqlevn70 4F610000 4F7B8FFF 001a9000
* SQLOS 344D0000 344D4FFF 00005000
* rsaenh 68000000 6802EFFF 0002f000
* AUTHZ 76C40000 76C53FFF 00014000
* MSCOREE 79000000 79044FFF 00045000
* ole32 77670000 777A3FFF 00134000
* msv1_0 76C90000 76CB6FFF 00027000
* iphlpapi 76CF0000 76D09FFF 0001a000
* kerberos 62810000 62867FFF 00058000
* cryptdll 766E0000 766EBFFF 0000c000
* schannel 76750000 76776FFF 00027000
* COMRES 77010000 770D5FFF 000c6000
* XOLEHLP 628D0000 628D5FFF 00006000
* MSDTCPRX 628E0000 62957FFF 00078000
* msvcp60 780C0000 78120FFF 00061000
* MTXCLU 62960000 62978FFF 00019000
* VERSION 77B90000 77B97FFF 00008000
* WSOCK32 71BB0000 71BB8FFF 00009000
* OLEAUT32 77D00000 77D8BFFF 0008c000
* CLUSAPI 62980000 62991FFF 00012000
* RESUTILS 629A0000 629B2FFF 00013000
* DNSAPI 76ED0000 76EFEFFF 0002f000
* winrnr 76F70000 76F76FFF 00007000
* WLDAP32 76F10000 76F3DFFF 0002e000
* rasadhlp 76F80000 76F87FFF 00008000
* security 62DF0000 62DF3FFF 00004000
* msfte 63750000 639A8FFF 00259000
* dbghelp 639B0000 63AC4FFF 00115000
* WINTRUST 76BB0000 76BDAFFF 0002b000
* imagehlp 76C10000 76C38FFF 00029000
* dssenh 68100000 68123FFF 00024000
* hnetcfg 63D20000 63D78FFF 00059000
* wshtcpip 71AE0000 71AE7FFF 00008000
* NTMARTA 77E00000 77E21FFF 00022000
* SAMLIB 63DC0000 63DCEFFF 0000f000
* ntdsapi 766F0000 76704FFF 00015000
* xpsp2res 63E50000 64114FFF 002c5000
* CLBCatQ 777B0000 77832FFF 00083000
* sqlncli 64120000 64343FFF 00224000
* COMCTL32 77530000 775C6FFF 00097000
* comdlg32 762B0000 762F9FFF 0004a000
* SQLNCLIR 007A0000 007D2FFF 00033000
* msftepxy 645D0000 645E4FFF 00015000
* EntApi 65E90000 65EA2FFF 00013000
* WININET 77210000 772B7FFF 000a8000
* xpsqlbot 66100000 66105FFF 00006000
* xpstar90 66120000 66168FFF 00049000
* SQLSCM90 66180000 66188FFF 00009000
* ODBC32 661A0000 661DCFFF 0003d000
* BatchParser90 661E0000 661FEFFF 0001f000
* ATL80 7C630000 7C64AFFF 0001b000
* odbcint 664D0000 664E6FFF 00017000
* xpstar90 664F0000 66515FFF 00026000
* xplog70 66520000 6652BFFF 0000c000
* xplog70 66540000 66542FFF 00003000
* odsole70 66550000 6655EFFF 0000f000
* SXS 66BD0000 66C8BFFF 000bc000
* oledb32 668E0000 66958FFF 00079000
* MSDART 64510000 64529FFF 0001a000
* OLEDB32R 64530000 64540FFF 00011000
* msdaora 66FF0000 67030FFF 00041000
* MSDATL3 66BA0000 66BB4FFF 00015000
* MSDAORAR 644F0000 644F3FFF 00004000
* oci 67040000 67096FFF 00057000
* MSVCR71 7C340000 7C395FFF 00056000
* OCIW32 670A0000 670F5FFF 00056000
* ORACLIENT10 67100000 67351FFF 00252000
* oracore10 67360000 67442FFF 000e3000
* oranls10 67450000 67513FFF 000c4000
* oraunls10 67520000 67537FFF 00018000
* orauts 66BC0000 66BC6FFF 00007000
* WINMM 76AA0000 76ACCFFF 0002d000
* oravsn10 67540000 67545FFF 00006000
* oracommon10 67550000 67641FFF 000f2000
* orageneric10 67650000 67BA6FFF 00557000
* orasnls10 67BB0000 67BD6FFF 00027000
* oraxml10 67BE0000 67D3FFFF 00160000
* MSVCIRT 67D40000 67D4FFFF 00010000
* oran10 67D50000 67E5CFFF 0010d000
* oranl10 67E60000 67E9CFFF 0003d000
* oranldap10 67EA0000 67EB6FFF 00017000
* orannzsbb10 67EC0000 67FC8FFF 00109000
* oraldapclnt10 68030000 68082FFF 00053000
* orancrypt10 67FD0000 67FEAFFF 0001b000
* oranro10 68090000 680DBFFF 0004c000
* oranhost10 67FF0000 67FF6FFF 00007000
* orancds10 680E0000 680E5FFF 00006000
* orantns10 680F0000 680F7FFF 00008000
* orapls10 68130000 68487FFF 00358000
* oraslax10 68490000 68498FFF 00009000
* oraplp10 684A0000 686A3FFF 00204000
* orahasgen10 686B0000 6873AFFF 0008b000
* oraocr10 68740000 687A9FFF 0006a000
* oraocrb10 687B0000 687EFFFF 00040000
* orantcp10 687F0000 687FFFFF 00010000
* orasql10 68800000 68899FFF 0009a000
* comsvcs 68B10000 68C48FFF 00139000
* activeds 76DF0000 76E22FFF 00033000
* adsldpc 76DC0000 76DE6FFF 00027000
* credui 76B80000 76BADFFF 0002e000
* ATL 76A80000 76A97FFF 00018000
* msadce 68DD0000 68E27FFF 00058000
* msadcer 68D70000 68D74FFF 00005000
* sqlmap90 6A090000 6A0ADFFF 0001e000
* MAPI32 6A0C0000 6A0DEFFF 0001f000
* sqlmap90 6A0E0000 6A0E5FFF 00006000
* MSMAPI32 6A0F0000 6A24BFFF 0015c000
* MAPIR 6A570000 6A62FFFF 000c0000
* mso 6AAC0000 6B67CFFF 00bbd000
* EMSABP32 6B690000 6B6D2FFF 00043000
* MPRAPI 76CD0000 76CE8FFF 00019000
* rtutils 76E30000 76E3BFFF 0000c000
* SETUPAPI 770E0000 771E9FFF 0010a000
* netman 77840000 77882FFF 00043000
* netshell 76300000 764C0FFF 001c1000
* RASAPI32 76E90000 76ECEFFF 0003f000
* rasman 76E40000 76E51FFF 00012000
* TAPI32 76E60000 76E8EFFF 0002f000
* WZCSAPI 6B820000 6B82CFFF 0000d000
* WZCSvc 77890000 77900FFF 00071000
* WMI 76CC0000 76CC4FFF 00005000
* DHCPCSVC 76D10000 76D2EFFF 0001f000
* WTSAPI32 76F00000 76F07FFF 00008000
* WINSTA 771F0000 77200FFF 00011000
* ESENT 6B830000 6B934FFF 00105000
* contab32 6C4E0000 6C4FEFFF 0001f000
* EMSMDB32 6C510000 6C5BEFFF 000af000
* encryption 6C930000 6C936FFF 00007000
* MSVBVM60 6C940000 6CA91FFF 00152000
* Dciph32 02C40000 02C4DFFF 0000e000
* dbghelp 69530000 69644FFF 00115000
*
* Edi: 6995E178: 6533D2F8 77F5E95E 00000000 6995E2C8 00000000
77FC2190
* Esi: 00000000:
* Eax: 6995E05C: 000042AC 00000000 00000000 77E55E02 00000000
0000000C
* Ebx: 0000003F:
* Ecx: 6995E6CC: 00000000 00010007 00000000 00460044 6533D2FC
6995E08C
* Edx: 0000003D:
* Eip: 77E55E02: 10C2C95E 90909000 A1649090 00000018 C334408B
891C428B
* Ebp: 6995E0AC: 6995E0F0 021A29C4 000042AC 00000000 00000000
00000000
* SegCs: 0000001B:
* EFlags: 00000246:
* Esp: 6995E058: 00000000 000042AC 00000000 00000000 77E55E02
00000000
* SegSs: 78130023: 00000000 00000000 00000000 00000000 00000000
00000000
*
************************************************** *****************************
*
* Short Stack Dump
77E55E02 Module(kernel32+00015E02)
021A29C4 Module(sqlservr+011A29C4)
021A6880 Module(sqlservr+011A6880)
021A642D Module(sqlservr+011A642D)
02414429 Module(sqlservr+01414429)
77E99F7A Module(kernel32+00059F7A)
78138B5E Module(MSVCR80+00008B5E)
781329C1 Module(MSVCR80+000029C1)
78132A36 Module(MSVCR80+00002A36)
We did an inplace upgrade of our "SQLServer 2000 SP3a" production server to
"SQLServer 2005 SP2 Enterprise Edition" on saturday. The system has 8 CPUs
and 4GB of RAM. This evening, the server crashed and I had to reboot the box.
I checked the eventvwr and this is what I get. I also found a stack dump in
the log. I checked the blackbox trace for any signs and I found "MIssing Join
Predicate" in the EventClass for one of the databases. This leads me to
believe that this is the reason why SQLServer crashed though we never
encountered this problem in the SQLServer 2000 installation before we
upgraded -- the application has been working fine without any problem over
the past several years. I could have trouble shooted this issue more but
unfortunately the text of the code that resulted in the "MIssing Join
Predicate" is empty in the Text column.
Event Type:Error
Event Source:MSSQLSERVER
Event Category:(2)
Event ID:17311
Date:1/14/2008
Time:5:59:11 PM
User:N/A
Computer:ENSQLP2
Description:
SQL Server is terminating because of fatal exception c0000005. This error
may be caused by an unhandled Win32 or C++ exception, or by an access
violation encountered during exception handling. Check the SQL error log for
any related stack dumps or messages. This exception forces SQL Server to
shutdown. To recover from this error, restart the server (unless SQLAgent is
configured to auto restart).
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 9f 43 00 00 10 00 00 00 ?C.....
0008: 08 00 00 00 45 00 4e 00 ...E.N.
0010: 53 00 51 00 4c 00 50 00 S.Q.L.P.
0018: 32 00 00 00 00 00 00 00 2......
Has anyone encountered this problem before? I will start a user defined
trace and get to the core tomorrow. Neverthless, I was wondering if anyone
has encountered this issue before
Here is the stack dump. Note that at this point I also dont know which
query/SP caused the crash.
================================================== ===================
BugCheck Dump
================================================== ===================
This file is generated by Microsoft SQL Server
version 9.00.3042.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 HP - 2
Current time is 17:59:12 01/14/08.
8 Intel x86 level 15, 2833 Mhz processor (s).
Windows NT 5.2 Build 3790 CSD Service Pack 1.
Memory
MemoryLoad = 51%
Total Physical = 4094 MB
Available Physical = 1986 MB
Total Page File = 10069 MB
Available Page File = 7980 MB
Total Virtual = 2047 MB
Available Virtual = 217 MB
**Dump thread - spid = 0, PSS = 0x00000000, EC = 0x00000000
***Stack Dump being sent to e:\MSSQL\MSSQL\LOG\SQLDump0005.txt
*
************************************************** *****************************
*
* BEGIN STACK DUMP:
* 01/14/08 17:59:12 spid 0
*
* ex_handle_except encountered exception C0000005 - Server terminating
*
*
* MODULE BASE END SIZE
* sqlservr 01000000 02C09FFF 01c0a000
* ntdll 7C800000 7C8BFFFF 000c0000
* kernel32 77E40000 77F41FFF 00102000
* MSVCR80 78130000 781CAFFF 0009b000
* msvcrt 77BA0000 77BF9FFF 0005a000
* MSVCP80 7C420000 7C4A6FFF 00087000
* ADVAPI32 77F50000 77FEBFFF 0009c000
* RPCRT4 77C50000 77CEEFFF 0009f000
* USER32 77380000 77411FFF 00092000
* GDI32 77C00000 77C48FFF 00049000
* CRYPT32 761B0000 76242FFF 00093000
* MSASN1 76190000 761A1FFF 00012000
* Secur32 76F50000 76F62FFF 00013000
* MSWSOCK 71B20000 71B60FFF 00041000
* WS2_32 71C00000 71C16FFF 00017000
* WS2HELP 71BF0000 71BF7FFF 00008000
* USERENV 76920000 769E3FFF 000c4000
* opends60 333E0000 333E6FFF 00007000
* NETAPI32 71C40000 71C97FFF 00058000
* SHELL32 7C8D0000 7D0D3FFF 00804000
* SHLWAPI 77DA0000 77DF1FFF 00052000
* comctl32 77420000 77522FFF 00103000
* psapi 76B70000 76B7AFFF 0000b000
* instapi 48060000 48069FFF 0000a000
* sqlevn70 4F610000 4F7B8FFF 001a9000
* SQLOS 344D0000 344D4FFF 00005000
* rsaenh 68000000 6802EFFF 0002f000
* AUTHZ 76C40000 76C53FFF 00014000
* MSCOREE 79000000 79044FFF 00045000
* ole32 77670000 777A3FFF 00134000
* msv1_0 76C90000 76CB6FFF 00027000
* iphlpapi 76CF0000 76D09FFF 0001a000
* kerberos 62810000 62867FFF 00058000
* cryptdll 766E0000 766EBFFF 0000c000
* schannel 76750000 76776FFF 00027000
* COMRES 77010000 770D5FFF 000c6000
* XOLEHLP 628D0000 628D5FFF 00006000
* MSDTCPRX 628E0000 62957FFF 00078000
* msvcp60 780C0000 78120FFF 00061000
* MTXCLU 62960000 62978FFF 00019000
* VERSION 77B90000 77B97FFF 00008000
* WSOCK32 71BB0000 71BB8FFF 00009000
* OLEAUT32 77D00000 77D8BFFF 0008c000
* CLUSAPI 62980000 62991FFF 00012000
* RESUTILS 629A0000 629B2FFF 00013000
* DNSAPI 76ED0000 76EFEFFF 0002f000
* winrnr 76F70000 76F76FFF 00007000
* WLDAP32 76F10000 76F3DFFF 0002e000
* rasadhlp 76F80000 76F87FFF 00008000
* security 62DF0000 62DF3FFF 00004000
* msfte 63750000 639A8FFF 00259000
* dbghelp 639B0000 63AC4FFF 00115000
* WINTRUST 76BB0000 76BDAFFF 0002b000
* imagehlp 76C10000 76C38FFF 00029000
* dssenh 68100000 68123FFF 00024000
* hnetcfg 63D20000 63D78FFF 00059000
* wshtcpip 71AE0000 71AE7FFF 00008000
* NTMARTA 77E00000 77E21FFF 00022000
* SAMLIB 63DC0000 63DCEFFF 0000f000
* ntdsapi 766F0000 76704FFF 00015000
* xpsp2res 63E50000 64114FFF 002c5000
* CLBCatQ 777B0000 77832FFF 00083000
* sqlncli 64120000 64343FFF 00224000
* COMCTL32 77530000 775C6FFF 00097000
* comdlg32 762B0000 762F9FFF 0004a000
* SQLNCLIR 007A0000 007D2FFF 00033000
* msftepxy 645D0000 645E4FFF 00015000
* EntApi 65E90000 65EA2FFF 00013000
* WININET 77210000 772B7FFF 000a8000
* xpsqlbot 66100000 66105FFF 00006000
* xpstar90 66120000 66168FFF 00049000
* SQLSCM90 66180000 66188FFF 00009000
* ODBC32 661A0000 661DCFFF 0003d000
* BatchParser90 661E0000 661FEFFF 0001f000
* ATL80 7C630000 7C64AFFF 0001b000
* odbcint 664D0000 664E6FFF 00017000
* xpstar90 664F0000 66515FFF 00026000
* xplog70 66520000 6652BFFF 0000c000
* xplog70 66540000 66542FFF 00003000
* odsole70 66550000 6655EFFF 0000f000
* SXS 66BD0000 66C8BFFF 000bc000
* oledb32 668E0000 66958FFF 00079000
* MSDART 64510000 64529FFF 0001a000
* OLEDB32R 64530000 64540FFF 00011000
* msdaora 66FF0000 67030FFF 00041000
* MSDATL3 66BA0000 66BB4FFF 00015000
* MSDAORAR 644F0000 644F3FFF 00004000
* oci 67040000 67096FFF 00057000
* MSVCR71 7C340000 7C395FFF 00056000
* OCIW32 670A0000 670F5FFF 00056000
* ORACLIENT10 67100000 67351FFF 00252000
* oracore10 67360000 67442FFF 000e3000
* oranls10 67450000 67513FFF 000c4000
* oraunls10 67520000 67537FFF 00018000
* orauts 66BC0000 66BC6FFF 00007000
* WINMM 76AA0000 76ACCFFF 0002d000
* oravsn10 67540000 67545FFF 00006000
* oracommon10 67550000 67641FFF 000f2000
* orageneric10 67650000 67BA6FFF 00557000
* orasnls10 67BB0000 67BD6FFF 00027000
* oraxml10 67BE0000 67D3FFFF 00160000
* MSVCIRT 67D40000 67D4FFFF 00010000
* oran10 67D50000 67E5CFFF 0010d000
* oranl10 67E60000 67E9CFFF 0003d000
* oranldap10 67EA0000 67EB6FFF 00017000
* orannzsbb10 67EC0000 67FC8FFF 00109000
* oraldapclnt10 68030000 68082FFF 00053000
* orancrypt10 67FD0000 67FEAFFF 0001b000
* oranro10 68090000 680DBFFF 0004c000
* oranhost10 67FF0000 67FF6FFF 00007000
* orancds10 680E0000 680E5FFF 00006000
* orantns10 680F0000 680F7FFF 00008000
* orapls10 68130000 68487FFF 00358000
* oraslax10 68490000 68498FFF 00009000
* oraplp10 684A0000 686A3FFF 00204000
* orahasgen10 686B0000 6873AFFF 0008b000
* oraocr10 68740000 687A9FFF 0006a000
* oraocrb10 687B0000 687EFFFF 00040000
* orantcp10 687F0000 687FFFFF 00010000
* orasql10 68800000 68899FFF 0009a000
* comsvcs 68B10000 68C48FFF 00139000
* activeds 76DF0000 76E22FFF 00033000
* adsldpc 76DC0000 76DE6FFF 00027000
* credui 76B80000 76BADFFF 0002e000
* ATL 76A80000 76A97FFF 00018000
* msadce 68DD0000 68E27FFF 00058000
* msadcer 68D70000 68D74FFF 00005000
* sqlmap90 6A090000 6A0ADFFF 0001e000
* MAPI32 6A0C0000 6A0DEFFF 0001f000
* sqlmap90 6A0E0000 6A0E5FFF 00006000
* MSMAPI32 6A0F0000 6A24BFFF 0015c000
* MAPIR 6A570000 6A62FFFF 000c0000
* mso 6AAC0000 6B67CFFF 00bbd000
* EMSABP32 6B690000 6B6D2FFF 00043000
* MPRAPI 76CD0000 76CE8FFF 00019000
* rtutils 76E30000 76E3BFFF 0000c000
* SETUPAPI 770E0000 771E9FFF 0010a000
* netman 77840000 77882FFF 00043000
* netshell 76300000 764C0FFF 001c1000
* RASAPI32 76E90000 76ECEFFF 0003f000
* rasman 76E40000 76E51FFF 00012000
* TAPI32 76E60000 76E8EFFF 0002f000
* WZCSAPI 6B820000 6B82CFFF 0000d000
* WZCSvc 77890000 77900FFF 00071000
* WMI 76CC0000 76CC4FFF 00005000
* DHCPCSVC 76D10000 76D2EFFF 0001f000
* WTSAPI32 76F00000 76F07FFF 00008000
* WINSTA 771F0000 77200FFF 00011000
* ESENT 6B830000 6B934FFF 00105000
* contab32 6C4E0000 6C4FEFFF 0001f000
* EMSMDB32 6C510000 6C5BEFFF 000af000
* encryption 6C930000 6C936FFF 00007000
* MSVBVM60 6C940000 6CA91FFF 00152000
* Dciph32 02C40000 02C4DFFF 0000e000
* dbghelp 69530000 69644FFF 00115000
*
* Edi: 6995E178: 6533D2F8 77F5E95E 00000000 6995E2C8 00000000
77FC2190
* Esi: 00000000:
* Eax: 6995E05C: 000042AC 00000000 00000000 77E55E02 00000000
0000000C
* Ebx: 0000003F:
* Ecx: 6995E6CC: 00000000 00010007 00000000 00460044 6533D2FC
6995E08C
* Edx: 0000003D:
* Eip: 77E55E02: 10C2C95E 90909000 A1649090 00000018 C334408B
891C428B
* Ebp: 6995E0AC: 6995E0F0 021A29C4 000042AC 00000000 00000000
00000000
* SegCs: 0000001B:
* EFlags: 00000246:
* Esp: 6995E058: 00000000 000042AC 00000000 00000000 77E55E02
00000000
* SegSs: 78130023: 00000000 00000000 00000000 00000000 00000000
00000000
*
************************************************** *****************************
*
* Short Stack Dump
77E55E02 Module(kernel32+00015E02)
021A29C4 Module(sqlservr+011A29C4)
021A6880 Module(sqlservr+011A6880)
021A642D Module(sqlservr+011A642D)
02414429 Module(sqlservr+01414429)
77E99F7A Module(kernel32+00059F7A)
78138B5E Module(MSVCR80+00008B5E)
781329C1 Module(MSVCR80+000029C1)
78132A36 Module(MSVCR80+00002A36)
Missing Join Predicate error
All,
We did an inplace upgrade of our "SQLServer 2000 SP3a" production server to
"SQLServer 2005 SP2 Enterprise Edition" on saturday. The system has 8 CPUs
and 4GB of RAM. This evening, the server crashed and I had to reboot the box.
I checked the eventvwr and this is what I get. I also found a stack dump in
the log. I checked the blackbox trace for any signs and I found "MIssing Join
Predicate" in the EventClass for one of the databases. This leads me to
believe that this is the reason why SQLServer crashed though we never
encountered this problem in the SQLServer 2000 installation before we
upgraded -- the application has been working fine without any problem over
the past several years. I could have trouble shooted this issue more but
unfortunately the text of the code that resulted in the "MIssing Join
Predicate" is empty in the Text column.
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17311
Date: 1/14/2008
Time: 5:59:11 PM
User: N/A
Computer: ENSQLP2
Description:
SQL Server is terminating because of fatal exception c0000005. This error
may be caused by an unhandled Win32 or C++ exception, or by an access
violation encountered during exception handling. Check the SQL error log for
any related stack dumps or messages. This exception forces SQL Server to
shutdown. To recover from this error, restart the server (unless SQLAgent is
configured to auto restart).
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 9f 43 00 00 10 00 00 00 Â?C.....
0008: 08 00 00 00 45 00 4e 00 ...E.N.
0010: 53 00 51 00 4c 00 50 00 S.Q.L.P.
0018: 32 00 00 00 00 00 00 00 2......
Has anyone encountered this problem before? I will start a user defined
trace and get to the core tomorrow. Neverthless, I was wondering if anyone
has encountered this issue beforeHere is the stack dump. Note that at this point I also dont know which
query/SP caused the crash.
=====================================================================
BugCheck Dump
=====================================================================
This file is generated by Microsoft SQL Server
version 9.00.3042.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 HP - 2
Current time is 17:59:12 01/14/08.
8 Intel x86 level 15, 2833 Mhz processor (s).
Windows NT 5.2 Build 3790 CSD Service Pack 1.
Memory
MemoryLoad = 51%
Total Physical = 4094 MB
Available Physical = 1986 MB
Total Page File = 10069 MB
Available Page File = 7980 MB
Total Virtual = 2047 MB
Available Virtual = 217 MB
**Dump thread - spid = 0, PSS = 0x00000000, EC = 0x00000000
***Stack Dump being sent to e:\MSSQL\MSSQL\LOG\SQLDump0005.txt
*
*******************************************************************************
*
* BEGIN STACK DUMP:
* 01/14/08 17:59:12 spid 0
*
* ex_handle_except encountered exception C0000005 - Server terminating
*
*
* MODULE BASE END SIZE
* sqlservr 01000000 02C09FFF 01c0a000
* ntdll 7C800000 7C8BFFFF 000c0000
* kernel32 77E40000 77F41FFF 00102000
* MSVCR80 78130000 781CAFFF 0009b000
* msvcrt 77BA0000 77BF9FFF 0005a000
* MSVCP80 7C420000 7C4A6FFF 00087000
* ADVAPI32 77F50000 77FEBFFF 0009c000
* RPCRT4 77C50000 77CEEFFF 0009f000
* USER32 77380000 77411FFF 00092000
* GDI32 77C00000 77C48FFF 00049000
* CRYPT32 761B0000 76242FFF 00093000
* MSASN1 76190000 761A1FFF 00012000
* Secur32 76F50000 76F62FFF 00013000
* MSWSOCK 71B20000 71B60FFF 00041000
* WS2_32 71C00000 71C16FFF 00017000
* WS2HELP 71BF0000 71BF7FFF 00008000
* USERENV 76920000 769E3FFF 000c4000
* opends60 333E0000 333E6FFF 00007000
* NETAPI32 71C40000 71C97FFF 00058000
* SHELL32 7C8D0000 7D0D3FFF 00804000
* SHLWAPI 77DA0000 77DF1FFF 00052000
* comctl32 77420000 77522FFF 00103000
* psapi 76B70000 76B7AFFF 0000b000
* instapi 48060000 48069FFF 0000a000
* sqlevn70 4F610000 4F7B8FFF 001a9000
* SQLOS 344D0000 344D4FFF 00005000
* rsaenh 68000000 6802EFFF 0002f000
* AUTHZ 76C40000 76C53FFF 00014000
* MSCOREE 79000000 79044FFF 00045000
* ole32 77670000 777A3FFF 00134000
* msv1_0 76C90000 76CB6FFF 00027000
* iphlpapi 76CF0000 76D09FFF 0001a000
* kerberos 62810000 62867FFF 00058000
* cryptdll 766E0000 766EBFFF 0000c000
* schannel 76750000 76776FFF 00027000
* COMRES 77010000 770D5FFF 000c6000
* XOLEHLP 628D0000 628D5FFF 00006000
* MSDTCPRX 628E0000 62957FFF 00078000
* msvcp60 780C0000 78120FFF 00061000
* MTXCLU 62960000 62978FFF 00019000
* VERSION 77B90000 77B97FFF 00008000
* WSOCK32 71BB0000 71BB8FFF 00009000
* OLEAUT32 77D00000 77D8BFFF 0008c000
* CLUSAPI 62980000 62991FFF 00012000
* RESUTILS 629A0000 629B2FFF 00013000
* DNSAPI 76ED0000 76EFEFFF 0002f000
* winrnr 76F70000 76F76FFF 00007000
* WLDAP32 76F10000 76F3DFFF 0002e000
* rasadhlp 76F80000 76F87FFF 00008000
* security 62DF0000 62DF3FFF 00004000
* msfte 63750000 639A8FFF 00259000
* dbghelp 639B0000 63AC4FFF 00115000
* WINTRUST 76BB0000 76BDAFFF 0002b000
* imagehlp 76C10000 76C38FFF 00029000
* dssenh 68100000 68123FFF 00024000
* hnetcfg 63D20000 63D78FFF 00059000
* wshtcpip 71AE0000 71AE7FFF 00008000
* NTMARTA 77E00000 77E21FFF 00022000
* SAMLIB 63DC0000 63DCEFFF 0000f000
* ntdsapi 766F0000 76704FFF 00015000
* xpsp2res 63E50000 64114FFF 002c5000
* CLBCatQ 777B0000 77832FFF 00083000
* sqlncli 64120000 64343FFF 00224000
* COMCTL32 77530000 775C6FFF 00097000
* comdlg32 762B0000 762F9FFF 0004a000
* SQLNCLIR 007A0000 007D2FFF 00033000
* msftepxy 645D0000 645E4FFF 00015000
* EntApi 65E90000 65EA2FFF 00013000
* WININET 77210000 772B7FFF 000a8000
* xpsqlbot 66100000 66105FFF 00006000
* xpstar90 66120000 66168FFF 00049000
* SQLSCM90 66180000 66188FFF 00009000
* ODBC32 661A0000 661DCFFF 0003d000
* BatchParser90 661E0000 661FEFFF 0001f000
* ATL80 7C630000 7C64AFFF 0001b000
* odbcint 664D0000 664E6FFF 00017000
* xpstar90 664F0000 66515FFF 00026000
* xplog70 66520000 6652BFFF 0000c000
* xplog70 66540000 66542FFF 00003000
* odsole70 66550000 6655EFFF 0000f000
* SXS 66BD0000 66C8BFFF 000bc000
* oledb32 668E0000 66958FFF 00079000
* MSDART 64510000 64529FFF 0001a000
* OLEDB32R 64530000 64540FFF 00011000
* msdaora 66FF0000 67030FFF 00041000
* MSDATL3 66BA0000 66BB4FFF 00015000
* MSDAORAR 644F0000 644F3FFF 00004000
* oci 67040000 67096FFF 00057000
* MSVCR71 7C340000 7C395FFF 00056000
* OCIW32 670A0000 670F5FFF 00056000
* ORACLIENT10 67100000 67351FFF 00252000
* oracore10 67360000 67442FFF 000e3000
* oranls10 67450000 67513FFF 000c4000
* oraunls10 67520000 67537FFF 00018000
* orauts 66BC0000 66BC6FFF 00007000
* WINMM 76AA0000 76ACCFFF 0002d000
* oravsn10 67540000 67545FFF 00006000
* oracommon10 67550000 67641FFF 000f2000
* orageneric10 67650000 67BA6FFF 00557000
* orasnls10 67BB0000 67BD6FFF 00027000
* oraxml10 67BE0000 67D3FFFF 00160000
* MSVCIRT 67D40000 67D4FFFF 00010000
* oran10 67D50000 67E5CFFF 0010d000
* oranl10 67E60000 67E9CFFF 0003d000
* oranldap10 67EA0000 67EB6FFF 00017000
* orannzsbb10 67EC0000 67FC8FFF 00109000
* oraldapclnt10 68030000 68082FFF 00053000
* orancrypt10 67FD0000 67FEAFFF 0001b000
* oranro10 68090000 680DBFFF 0004c000
* oranhost10 67FF0000 67FF6FFF 00007000
* orancds10 680E0000 680E5FFF 00006000
* orantns10 680F0000 680F7FFF 00008000
* orapls10 68130000 68487FFF 00358000
* oraslax10 68490000 68498FFF 00009000
* oraplp10 684A0000 686A3FFF 00204000
* orahasgen10 686B0000 6873AFFF 0008b000
* oraocr10 68740000 687A9FFF 0006a000
* oraocrb10 687B0000 687EFFFF 00040000
* orantcp10 687F0000 687FFFFF 00010000
* orasql10 68800000 68899FFF 0009a000
* comsvcs 68B10000 68C48FFF 00139000
* activeds 76DF0000 76E22FFF 00033000
* adsldpc 76DC0000 76DE6FFF 00027000
* credui 76B80000 76BADFFF 0002e000
* ATL 76A80000 76A97FFF 00018000
* msadce 68DD0000 68E27FFF 00058000
* msadcer 68D70000 68D74FFF 00005000
* sqlmap90 6A090000 6A0ADFFF 0001e000
* MAPI32 6A0C0000 6A0DEFFF 0001f000
* sqlmap90 6A0E0000 6A0E5FFF 00006000
* MSMAPI32 6A0F0000 6A24BFFF 0015c000
* MAPIR 6A570000 6A62FFFF 000c0000
* mso 6AAC0000 6B67CFFF 00bbd000
* EMSABP32 6B690000 6B6D2FFF 00043000
* MPRAPI 76CD0000 76CE8FFF 00019000
* rtutils 76E30000 76E3BFFF 0000c000
* SETUPAPI 770E0000 771E9FFF 0010a000
* netman 77840000 77882FFF 00043000
* netshell 76300000 764C0FFF 001c1000
* RASAPI32 76E90000 76ECEFFF 0003f000
* rasman 76E40000 76E51FFF 00012000
* TAPI32 76E60000 76E8EFFF 0002f000
* WZCSAPI 6B820000 6B82CFFF 0000d000
* WZCSvc 77890000 77900FFF 00071000
* WMI 76CC0000 76CC4FFF 00005000
* DHCPCSVC 76D10000 76D2EFFF 0001f000
* WTSAPI32 76F00000 76F07FFF 00008000
* WINSTA 771F0000 77200FFF 00011000
* ESENT 6B830000 6B934FFF 00105000
* contab32 6C4E0000 6C4FEFFF 0001f000
* EMSMDB32 6C510000 6C5BEFFF 000af000
* encryption 6C930000 6C936FFF 00007000
* MSVBVM60 6C940000 6CA91FFF 00152000
* Dciph32 02C40000 02C4DFFF 0000e000
* dbghelp 69530000 69644FFF 00115000
*
* Edi: 6995E178: 6533D2F8 77F5E95E 00000000 6995E2C8 00000000
77FC2190
* Esi: 00000000:
* Eax: 6995E05C: 000042AC 00000000 00000000 77E55E02 00000000
0000000C
* Ebx: 0000003F:
* Ecx: 6995E6CC: 00000000 00010007 00000000 00460044 6533D2FC
6995E08C
* Edx: 0000003D:
* Eip: 77E55E02: 10C2C95E 90909000 A1649090 00000018 C334408B
891C428B
* Ebp: 6995E0AC: 6995E0F0 021A29C4 000042AC 00000000 00000000
00000000
* SegCs: 0000001B:
* EFlags: 00000246:
* Esp: 6995E058: 00000000 000042AC 00000000 00000000 77E55E02
00000000
* SegSs: 78130023: 00000000 00000000 00000000 00000000 00000000
00000000
*
*******************************************************************************
*
----
* Short Stack Dump
77E55E02 Module(kernel32+00015E02)
021A29C4 Module(sqlservr+011A29C4)
021A6880 Module(sqlservr+011A6880)
021A642D Module(sqlservr+011A642D)
02414429 Module(sqlservr+01414429)
77E99F7A Module(kernel32+00059F7A)
78138B5E Module(MSVCR80+00008B5E)
781329C1 Module(MSVCR80+000029C1)
78132A36 Module(MSVCR80+00002A36)
We did an inplace upgrade of our "SQLServer 2000 SP3a" production server to
"SQLServer 2005 SP2 Enterprise Edition" on saturday. The system has 8 CPUs
and 4GB of RAM. This evening, the server crashed and I had to reboot the box.
I checked the eventvwr and this is what I get. I also found a stack dump in
the log. I checked the blackbox trace for any signs and I found "MIssing Join
Predicate" in the EventClass for one of the databases. This leads me to
believe that this is the reason why SQLServer crashed though we never
encountered this problem in the SQLServer 2000 installation before we
upgraded -- the application has been working fine without any problem over
the past several years. I could have trouble shooted this issue more but
unfortunately the text of the code that resulted in the "MIssing Join
Predicate" is empty in the Text column.
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17311
Date: 1/14/2008
Time: 5:59:11 PM
User: N/A
Computer: ENSQLP2
Description:
SQL Server is terminating because of fatal exception c0000005. This error
may be caused by an unhandled Win32 or C++ exception, or by an access
violation encountered during exception handling. Check the SQL error log for
any related stack dumps or messages. This exception forces SQL Server to
shutdown. To recover from this error, restart the server (unless SQLAgent is
configured to auto restart).
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 9f 43 00 00 10 00 00 00 Â?C.....
0008: 08 00 00 00 45 00 4e 00 ...E.N.
0010: 53 00 51 00 4c 00 50 00 S.Q.L.P.
0018: 32 00 00 00 00 00 00 00 2......
Has anyone encountered this problem before? I will start a user defined
trace and get to the core tomorrow. Neverthless, I was wondering if anyone
has encountered this issue beforeHere is the stack dump. Note that at this point I also dont know which
query/SP caused the crash.
=====================================================================
BugCheck Dump
=====================================================================
This file is generated by Microsoft SQL Server
version 9.00.3042.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 HP - 2
Current time is 17:59:12 01/14/08.
8 Intel x86 level 15, 2833 Mhz processor (s).
Windows NT 5.2 Build 3790 CSD Service Pack 1.
Memory
MemoryLoad = 51%
Total Physical = 4094 MB
Available Physical = 1986 MB
Total Page File = 10069 MB
Available Page File = 7980 MB
Total Virtual = 2047 MB
Available Virtual = 217 MB
**Dump thread - spid = 0, PSS = 0x00000000, EC = 0x00000000
***Stack Dump being sent to e:\MSSQL\MSSQL\LOG\SQLDump0005.txt
*
*******************************************************************************
*
* BEGIN STACK DUMP:
* 01/14/08 17:59:12 spid 0
*
* ex_handle_except encountered exception C0000005 - Server terminating
*
*
* MODULE BASE END SIZE
* sqlservr 01000000 02C09FFF 01c0a000
* ntdll 7C800000 7C8BFFFF 000c0000
* kernel32 77E40000 77F41FFF 00102000
* MSVCR80 78130000 781CAFFF 0009b000
* msvcrt 77BA0000 77BF9FFF 0005a000
* MSVCP80 7C420000 7C4A6FFF 00087000
* ADVAPI32 77F50000 77FEBFFF 0009c000
* RPCRT4 77C50000 77CEEFFF 0009f000
* USER32 77380000 77411FFF 00092000
* GDI32 77C00000 77C48FFF 00049000
* CRYPT32 761B0000 76242FFF 00093000
* MSASN1 76190000 761A1FFF 00012000
* Secur32 76F50000 76F62FFF 00013000
* MSWSOCK 71B20000 71B60FFF 00041000
* WS2_32 71C00000 71C16FFF 00017000
* WS2HELP 71BF0000 71BF7FFF 00008000
* USERENV 76920000 769E3FFF 000c4000
* opends60 333E0000 333E6FFF 00007000
* NETAPI32 71C40000 71C97FFF 00058000
* SHELL32 7C8D0000 7D0D3FFF 00804000
* SHLWAPI 77DA0000 77DF1FFF 00052000
* comctl32 77420000 77522FFF 00103000
* psapi 76B70000 76B7AFFF 0000b000
* instapi 48060000 48069FFF 0000a000
* sqlevn70 4F610000 4F7B8FFF 001a9000
* SQLOS 344D0000 344D4FFF 00005000
* rsaenh 68000000 6802EFFF 0002f000
* AUTHZ 76C40000 76C53FFF 00014000
* MSCOREE 79000000 79044FFF 00045000
* ole32 77670000 777A3FFF 00134000
* msv1_0 76C90000 76CB6FFF 00027000
* iphlpapi 76CF0000 76D09FFF 0001a000
* kerberos 62810000 62867FFF 00058000
* cryptdll 766E0000 766EBFFF 0000c000
* schannel 76750000 76776FFF 00027000
* COMRES 77010000 770D5FFF 000c6000
* XOLEHLP 628D0000 628D5FFF 00006000
* MSDTCPRX 628E0000 62957FFF 00078000
* msvcp60 780C0000 78120FFF 00061000
* MTXCLU 62960000 62978FFF 00019000
* VERSION 77B90000 77B97FFF 00008000
* WSOCK32 71BB0000 71BB8FFF 00009000
* OLEAUT32 77D00000 77D8BFFF 0008c000
* CLUSAPI 62980000 62991FFF 00012000
* RESUTILS 629A0000 629B2FFF 00013000
* DNSAPI 76ED0000 76EFEFFF 0002f000
* winrnr 76F70000 76F76FFF 00007000
* WLDAP32 76F10000 76F3DFFF 0002e000
* rasadhlp 76F80000 76F87FFF 00008000
* security 62DF0000 62DF3FFF 00004000
* msfte 63750000 639A8FFF 00259000
* dbghelp 639B0000 63AC4FFF 00115000
* WINTRUST 76BB0000 76BDAFFF 0002b000
* imagehlp 76C10000 76C38FFF 00029000
* dssenh 68100000 68123FFF 00024000
* hnetcfg 63D20000 63D78FFF 00059000
* wshtcpip 71AE0000 71AE7FFF 00008000
* NTMARTA 77E00000 77E21FFF 00022000
* SAMLIB 63DC0000 63DCEFFF 0000f000
* ntdsapi 766F0000 76704FFF 00015000
* xpsp2res 63E50000 64114FFF 002c5000
* CLBCatQ 777B0000 77832FFF 00083000
* sqlncli 64120000 64343FFF 00224000
* COMCTL32 77530000 775C6FFF 00097000
* comdlg32 762B0000 762F9FFF 0004a000
* SQLNCLIR 007A0000 007D2FFF 00033000
* msftepxy 645D0000 645E4FFF 00015000
* EntApi 65E90000 65EA2FFF 00013000
* WININET 77210000 772B7FFF 000a8000
* xpsqlbot 66100000 66105FFF 00006000
* xpstar90 66120000 66168FFF 00049000
* SQLSCM90 66180000 66188FFF 00009000
* ODBC32 661A0000 661DCFFF 0003d000
* BatchParser90 661E0000 661FEFFF 0001f000
* ATL80 7C630000 7C64AFFF 0001b000
* odbcint 664D0000 664E6FFF 00017000
* xpstar90 664F0000 66515FFF 00026000
* xplog70 66520000 6652BFFF 0000c000
* xplog70 66540000 66542FFF 00003000
* odsole70 66550000 6655EFFF 0000f000
* SXS 66BD0000 66C8BFFF 000bc000
* oledb32 668E0000 66958FFF 00079000
* MSDART 64510000 64529FFF 0001a000
* OLEDB32R 64530000 64540FFF 00011000
* msdaora 66FF0000 67030FFF 00041000
* MSDATL3 66BA0000 66BB4FFF 00015000
* MSDAORAR 644F0000 644F3FFF 00004000
* oci 67040000 67096FFF 00057000
* MSVCR71 7C340000 7C395FFF 00056000
* OCIW32 670A0000 670F5FFF 00056000
* ORACLIENT10 67100000 67351FFF 00252000
* oracore10 67360000 67442FFF 000e3000
* oranls10 67450000 67513FFF 000c4000
* oraunls10 67520000 67537FFF 00018000
* orauts 66BC0000 66BC6FFF 00007000
* WINMM 76AA0000 76ACCFFF 0002d000
* oravsn10 67540000 67545FFF 00006000
* oracommon10 67550000 67641FFF 000f2000
* orageneric10 67650000 67BA6FFF 00557000
* orasnls10 67BB0000 67BD6FFF 00027000
* oraxml10 67BE0000 67D3FFFF 00160000
* MSVCIRT 67D40000 67D4FFFF 00010000
* oran10 67D50000 67E5CFFF 0010d000
* oranl10 67E60000 67E9CFFF 0003d000
* oranldap10 67EA0000 67EB6FFF 00017000
* orannzsbb10 67EC0000 67FC8FFF 00109000
* oraldapclnt10 68030000 68082FFF 00053000
* orancrypt10 67FD0000 67FEAFFF 0001b000
* oranro10 68090000 680DBFFF 0004c000
* oranhost10 67FF0000 67FF6FFF 00007000
* orancds10 680E0000 680E5FFF 00006000
* orantns10 680F0000 680F7FFF 00008000
* orapls10 68130000 68487FFF 00358000
* oraslax10 68490000 68498FFF 00009000
* oraplp10 684A0000 686A3FFF 00204000
* orahasgen10 686B0000 6873AFFF 0008b000
* oraocr10 68740000 687A9FFF 0006a000
* oraocrb10 687B0000 687EFFFF 00040000
* orantcp10 687F0000 687FFFFF 00010000
* orasql10 68800000 68899FFF 0009a000
* comsvcs 68B10000 68C48FFF 00139000
* activeds 76DF0000 76E22FFF 00033000
* adsldpc 76DC0000 76DE6FFF 00027000
* credui 76B80000 76BADFFF 0002e000
* ATL 76A80000 76A97FFF 00018000
* msadce 68DD0000 68E27FFF 00058000
* msadcer 68D70000 68D74FFF 00005000
* sqlmap90 6A090000 6A0ADFFF 0001e000
* MAPI32 6A0C0000 6A0DEFFF 0001f000
* sqlmap90 6A0E0000 6A0E5FFF 00006000
* MSMAPI32 6A0F0000 6A24BFFF 0015c000
* MAPIR 6A570000 6A62FFFF 000c0000
* mso 6AAC0000 6B67CFFF 00bbd000
* EMSABP32 6B690000 6B6D2FFF 00043000
* MPRAPI 76CD0000 76CE8FFF 00019000
* rtutils 76E30000 76E3BFFF 0000c000
* SETUPAPI 770E0000 771E9FFF 0010a000
* netman 77840000 77882FFF 00043000
* netshell 76300000 764C0FFF 001c1000
* RASAPI32 76E90000 76ECEFFF 0003f000
* rasman 76E40000 76E51FFF 00012000
* TAPI32 76E60000 76E8EFFF 0002f000
* WZCSAPI 6B820000 6B82CFFF 0000d000
* WZCSvc 77890000 77900FFF 00071000
* WMI 76CC0000 76CC4FFF 00005000
* DHCPCSVC 76D10000 76D2EFFF 0001f000
* WTSAPI32 76F00000 76F07FFF 00008000
* WINSTA 771F0000 77200FFF 00011000
* ESENT 6B830000 6B934FFF 00105000
* contab32 6C4E0000 6C4FEFFF 0001f000
* EMSMDB32 6C510000 6C5BEFFF 000af000
* encryption 6C930000 6C936FFF 00007000
* MSVBVM60 6C940000 6CA91FFF 00152000
* Dciph32 02C40000 02C4DFFF 0000e000
* dbghelp 69530000 69644FFF 00115000
*
* Edi: 6995E178: 6533D2F8 77F5E95E 00000000 6995E2C8 00000000
77FC2190
* Esi: 00000000:
* Eax: 6995E05C: 000042AC 00000000 00000000 77E55E02 00000000
0000000C
* Ebx: 0000003F:
* Ecx: 6995E6CC: 00000000 00010007 00000000 00460044 6533D2FC
6995E08C
* Edx: 0000003D:
* Eip: 77E55E02: 10C2C95E 90909000 A1649090 00000018 C334408B
891C428B
* Ebp: 6995E0AC: 6995E0F0 021A29C4 000042AC 00000000 00000000
00000000
* SegCs: 0000001B:
* EFlags: 00000246:
* Esp: 6995E058: 00000000 000042AC 00000000 00000000 77E55E02
00000000
* SegSs: 78130023: 00000000 00000000 00000000 00000000 00000000
00000000
*
*******************************************************************************
*
----
* Short Stack Dump
77E55E02 Module(kernel32+00015E02)
021A29C4 Module(sqlservr+011A29C4)
021A6880 Module(sqlservr+011A6880)
021A642D Module(sqlservr+011A642D)
02414429 Module(sqlservr+01414429)
77E99F7A Module(kernel32+00059F7A)
78138B5E Module(MSVCR80+00008B5E)
781329C1 Module(MSVCR80+000029C1)
78132A36 Module(MSVCR80+00002A36)
Monday, February 20, 2012
Missing Features In Standard Edition X64?
Hi all
In BOL in the features per version section it states that certain features available in the 32-bit version of Std Edition is not available in the 64-bit version. Eg. Database Mail, Query Editor, Query Designer etc.
I have downloaded the latest BOL (May 2007) and installed it and it still says certain features are not available in X64.
However I configured Database Mail on Std Edition X64 and it works 100%. Had some issues with SQLAgent using it but Service Pack 2 solved the problem.
Query Editor and Designer works even though Microsoft says it isn't available.
Is there any difference in the tools or features available in Std Edition 32-bit or 64-bit?
My other concern is what has Microsoft said is available and isn't?
From my tests I can't see anything missing. We are about to go purchase software and licenses and don't want to make the wrong choice.
Thanks
John
Currently, there are not 64 bit client tools pubically available to use with 64 bit SQL Server.
The 32 bit tools work just fine.
You most likely have installed and are using the 32 bit client tools.
|||The following page in Books on Line is in error.
http://msdn2.microsoft.com/en-us/library/ms143761.aspx
I have submitted two requests for changes:
1. Remove the standard edition 64 bit column from the management tools section, and update the header of the SE 32 column to include SE 64. This says that tools features are the same in 32 and 64 bit.
2. SQL Mail is available only in 32 bit installations. DB Mail is available in 32 and 64 bit installs, whether they are standard or enterprise.
Thanks for pointing this out. I hope we can spare you further confusion.
jkh
|||Thanks for getting back to me and clearing up the confusion.
Regards
John
Subscribe to:
Posts (Atom)