On one box Enterprise Manager is indicating a second instance â' . (Windows
NT)â' , in addition to the default instance, â' (local) (Windows NT)â'. This
second instance was not installed, It just appeared. The MSSQL directory
indicates the presence of only one instance. Databases, and security
configurations are identical in structure and information between the two
instances. Has any one seen this happen? Would you recommend deleting the
â'Ghostâ' instance. Any ideas welcome. Thanks to everyone for being there to
help. SQL 2000 SP4.coenzyme wrote:
> On one box Enterprise Manager is indicating a second instance â' . (Windows
> NT)â' , in addition to the default instance, â' (local) (Windows NT)â'. This
> second instance was not installed, It just appeared. The MSSQL directory
> indicates the presence of only one instance. Databases, and security
> configurations are identical in structure and information between the two
> instances. Has any one seen this happen? Would you recommend deleting the
> â'Ghostâ' instance. Any ideas welcome. Thanks to everyone for being there to
> help. SQL 2000 SP4.
>
You can safely delete either one - registrations in EM have no effect on
the actual instances that are running.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Thanks Tracy. It's a real comfort to know there's experienced people like you
who are willing to help.
"Tracy McKibben" wrote:
> coenzyme wrote:
> > On one box Enterprise Manager is indicating a second instance â' . (Windows
> > NT)â' , in addition to the default instance, â' (local) (Windows NT)â'. This
> > second instance was not installed, It just appeared. The MSSQL directory
> > indicates the presence of only one instance. Databases, and security
> > configurations are identical in structure and information between the two
> > instances. Has any one seen this happen? Would you recommend deleting the
> > â'Ghostâ' instance. Any ideas welcome. Thanks to everyone for being there to
> > help. SQL 2000 SP4.
> >
> >
> You can safely delete either one - registrations in EM have no effect on
> the actual instances that are running.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>
Showing posts with label windows. Show all posts
Showing posts with label windows. Show all posts
Monday, March 26, 2012
Duplicate instances
On one box Enterprise Manager is indicating a second instance “ . (Window
s
NT)” , in addition to the default instance, “ (local) (Windows NT)”.
This
second instance was not installed, It just appeared. The MSSQL directory
indicates the presence of only one instance. Databases, and security
configurations are identical in structure and information between the two
instances. Has any one seen this happen? Would you recommend deleting the
“Ghost” instance. Any ideas welcome. Thanks to everyone for being there
to
help. SQL 2000 SP4.coenzyme wrote:
> On one box Enterprise Manager is indicating a second instance “ . (Wind
ows
> NT)” , in addition to the default instance, “ (local) (Windows NT)”
. This
> second instance was not installed, It just appeared. The MSSQL directory
> indicates the presence of only one instance. Databases, and security
> configurations are identical in structure and information between the two
> instances. Has any one seen this happen? Would you recommend deleting the
> “Ghost” instance. Any ideas welcome. Thanks to everyone for being ther
e to
> help. SQL 2000 SP4.
>
You can safely delete either one - registrations in EM have no effect on
the actual instances that are running.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Thanks Tracy. It's a real comfort to know there's experienced people like yo
u
who are willing to help.
"Tracy McKibben" wrote:
> coenzyme wrote:
> You can safely delete either one - registrations in EM have no effect on
> the actual instances that are running.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>
s
NT)” , in addition to the default instance, “ (local) (Windows NT)”.
This
second instance was not installed, It just appeared. The MSSQL directory
indicates the presence of only one instance. Databases, and security
configurations are identical in structure and information between the two
instances. Has any one seen this happen? Would you recommend deleting the
“Ghost” instance. Any ideas welcome. Thanks to everyone for being there
to
help. SQL 2000 SP4.coenzyme wrote:
> On one box Enterprise Manager is indicating a second instance “ . (Wind
ows
> NT)” , in addition to the default instance, “ (local) (Windows NT)”
. This
> second instance was not installed, It just appeared. The MSSQL directory
> indicates the presence of only one instance. Databases, and security
> configurations are identical in structure and information between the two
> instances. Has any one seen this happen? Would you recommend deleting the
> “Ghost” instance. Any ideas welcome. Thanks to everyone for being ther
e to
> help. SQL 2000 SP4.
>
You can safely delete either one - registrations in EM have no effect on
the actual instances that are running.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Thanks Tracy. It's a real comfort to know there's experienced people like yo
u
who are willing to help.
"Tracy McKibben" wrote:
> coenzyme wrote:
> You can safely delete either one - registrations in EM have no effect on
> the actual instances that are running.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>
Thursday, March 22, 2012
Duplicate Domains Listed - Unable to Add Logins
I have a Windows 2003 server with SQL Server 2000 running on it. The server
is performing dual roles as both a database server and a Primary Domain
Controller. When attempting to add logins for the server, I see the domain
listed twice. This causes any attempt to add a user to fail. I get the
following error:
Error 15401: Windows NT user or group 'DOMAIN\Administrators' not found.
Check the name again.
Does anyone know why this might be happening and how to fix it?
Thank You,
Jason Williard
You can take a look at this kb:
http://support.microsoft.com/kb/258025
-oj
"Jason Williard" <jason@.pcsafe.net> wrote in message
news:GZudnS-WBtrKZr7fRVn-uA@.comcast.com...
>I have a Windows 2003 server with SQL Server 2000 running on it. The
>server is performing dual roles as both a database server and a Primary
>Domain Controller. When attempting to add logins for the server, I see the
>domain listed twice. This causes any attempt to add a user to fail. I get
>the following error:
> Error 15401: Windows NT user or group 'DOMAIN\Administrators' not found.
> Check the name again.
>
> Does anyone know why this might be happening and how to fix it?
> Thank You,
> Jason Williard
>
is performing dual roles as both a database server and a Primary Domain
Controller. When attempting to add logins for the server, I see the domain
listed twice. This causes any attempt to add a user to fail. I get the
following error:
Error 15401: Windows NT user or group 'DOMAIN\Administrators' not found.
Check the name again.
Does anyone know why this might be happening and how to fix it?
Thank You,
Jason Williard
You can take a look at this kb:
http://support.microsoft.com/kb/258025
-oj
"Jason Williard" <jason@.pcsafe.net> wrote in message
news:GZudnS-WBtrKZr7fRVn-uA@.comcast.com...
>I have a Windows 2003 server with SQL Server 2000 running on it. The
>server is performing dual roles as both a database server and a Primary
>Domain Controller. When attempting to add logins for the server, I see the
>domain listed twice. This causes any attempt to add a user to fail. I get
>the following error:
> Error 15401: Windows NT user or group 'DOMAIN\Administrators' not found.
> Check the name again.
>
> Does anyone know why this might be happening and how to fix it?
> Thank You,
> Jason Williard
>
Duplicate Domains Listed - Unable to Add Logins
I have a Windows 2003 server with SQL Server 2000 running on it. The server
is performing dual roles as both a database server and a Primary Domain
Controller. When attempting to add logins for the server, I see the domain
listed twice. This causes any attempt to add a user to fail. I get the
following error:
Error 15401: Windows NT user or group 'DOMAIN\Administrators' not found.
Check the name again.
Does anyone know why this might be happening and how to fix it?
Thank You,
Jason WilliardYou can take a look at this kb:
http://support.microsoft.com/kb/258025
-oj
"Jason Williard" <jason@.pcsafe.net> wrote in message
news:GZudnS-WBtrKZr7fRVn-uA@.comcast.com...
>I have a Windows 2003 server with SQL Server 2000 running on it. The
>server is performing dual roles as both a database server and a Primary
>Domain Controller. When attempting to add logins for the server, I see the
>domain listed twice. This causes any attempt to add a user to fail. I get
>the following error:
> Error 15401: Windows NT user or group 'DOMAIN\Administrators' not found.
> Check the name again.
>
> Does anyone know why this might be happening and how to fix it?
> Thank You,
> Jason Williard
>
is performing dual roles as both a database server and a Primary Domain
Controller. When attempting to add logins for the server, I see the domain
listed twice. This causes any attempt to add a user to fail. I get the
following error:
Error 15401: Windows NT user or group 'DOMAIN\Administrators' not found.
Check the name again.
Does anyone know why this might be happening and how to fix it?
Thank You,
Jason WilliardYou can take a look at this kb:
http://support.microsoft.com/kb/258025
-oj
"Jason Williard" <jason@.pcsafe.net> wrote in message
news:GZudnS-WBtrKZr7fRVn-uA@.comcast.com...
>I have a Windows 2003 server with SQL Server 2000 running on it. The
>server is performing dual roles as both a database server and a Primary
>Domain Controller. When attempting to add logins for the server, I see the
>domain listed twice. This causes any attempt to add a user to fail. I get
>the following error:
> Error 15401: Windows NT user or group 'DOMAIN\Administrators' not found.
> Check the name again.
>
> Does anyone know why this might be happening and how to fix it?
> Thank You,
> Jason Williard
>
Duplicate Domains Listed - Unable to Add Logins
I have a Windows 2003 server with SQL Server 2000 running on it. The server
is performing dual roles as both a database server and a Primary Domain
Controller. When attempting to add logins for the server, I see the domain
listed twice. This causes any attempt to add a user to fail. I get the
following error:
Error 15401: Windows NT user or group 'DOMAIN\Administrators' not found.
Check the name again.
Does anyone know why this might be happening and how to fix it?
Thank You,
Jason WilliardYou can take a look at this kb:
http://support.microsoft.com/kb/258025
-oj
"Jason Williard" <jason@.pcsafe.net> wrote in message
news:GZudnS-WBtrKZr7fRVn-uA@.comcast.com...
>I have a Windows 2003 server with SQL Server 2000 running on it. The
>server is performing dual roles as both a database server and a Primary
>Domain Controller. When attempting to add logins for the server, I see the
>domain listed twice. This causes any attempt to add a user to fail. I get
>the following error:
> Error 15401: Windows NT user or group 'DOMAIN\Administrators' not found.
> Check the name again.
>
> Does anyone know why this might be happening and how to fix it?
> Thank You,
> Jason Williard
>
is performing dual roles as both a database server and a Primary Domain
Controller. When attempting to add logins for the server, I see the domain
listed twice. This causes any attempt to add a user to fail. I get the
following error:
Error 15401: Windows NT user or group 'DOMAIN\Administrators' not found.
Check the name again.
Does anyone know why this might be happening and how to fix it?
Thank You,
Jason WilliardYou can take a look at this kb:
http://support.microsoft.com/kb/258025
-oj
"Jason Williard" <jason@.pcsafe.net> wrote in message
news:GZudnS-WBtrKZr7fRVn-uA@.comcast.com...
>I have a Windows 2003 server with SQL Server 2000 running on it. The
>server is performing dual roles as both a database server and a Primary
>Domain Controller. When attempting to add logins for the server, I see the
>domain listed twice. This causes any attempt to add a user to fail. I get
>the following error:
> Error 15401: Windows NT user or group 'DOMAIN\Administrators' not found.
> Check the name again.
>
> Does anyone know why this might be happening and how to fix it?
> Thank You,
> Jason Williard
>
Monday, March 19, 2012
Dump file
Hi Everyone,
We have a SQL Server creates a dump file & stops the
service. Any help is highly appeciated.
SQL 2000 (SP3A) on a Windows 2000 Box (SP4)
Thanks,
================================================== =========
==========
BugCheck
Dump
================================================== =========
==========
This file is generated by Microsoft SQL Server
8.00.760
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 PhoenixBIOS 4.0 Release
6.0
Current time is 13:27:01
06/18/04.
4 Intel x86 level 15, 3066 Mhz processor
(s).
Windows NT 5.0 Build 2195 CSD Service Pack
4.
Memory
MemoryLoad = 77%
Total Physical = 2046 MB
Available Physical = 465 MB
Total Page File = 3940 MB
Available Page File = 2463 MB
Total Virtual = 2047 MB
Available Virtual = 288 MB
*Dump thread - spid = 68, PSS = 0x52f031c8, EC =
0x52f034f0
*Stack Dump being sent to d:\Microsoft SQL
Server\MSSQL\log\SQLDump0001.txt
*
************************************************** *********
******************
**
*
* BEGIN STACK
DUMP:
* 06/18/04 13:27:01 spid
68
*
*
*
* Input Buffer 224 bytes -
* CREATE UNIQUE CLUSTERED INDEX [PK_promo] ON [dbo].
[promo] ([promo_id]
* ) WITH DROP_EXISTING ON
[PRIMARY]
*
*
* MODULE BASE END
SIZE
* sqlservr 00400000 00B2CFFF
0072d000
* ntdll 77F80000 77FFAFFF
0007b000
* KERNEL32 7C570000 7C622FFF
000b3000
* ADVAPI32 7C2D0000 7C331FFF
00062000
* RPCRT4 77D30000 77D9DFFF
0006e000
* USER32 77E10000 77E6EFFF
0005f000
* GDI32 77F40000 77F78FFF
00039000
* OPENDS60 41060000 41065FFF
00006000
* MSVCRT 78000000 78044FFF
00045000
* UMS 41070000 4107CFFF
0000d000
* SQLSORT 42AE0000 42B6FFFF
00090000
* MSVCIRT 780A0000 780B1FFF
00012000
* sqlevn70 41080000 41086FFF
00007000
* NETAPI32 027A0000 027EEFFF
0004f000
* SECUR32 027F0000 027FEFFF
0000f000
* NETRAP 02800000 02805FFF
00006000
* SAMLIB 02810000 0281EFFF
0000f000
* WS2_32 02820000 02833FFF
00014000
* WS2HELP 02840000 02847FFF
00008000
* WLDAP32 02850000 02879FFF
0002a000
* DNSAPI 02880000 028A3FFF
00024000
* WSOCK32 028B0000 028B7FFF
00008000
* ole32 02CA0000 02D8BFFF
000ec000
* XOLEHLP 02E10000 02E17FFF
00008000
* MSDTCPRX 02E20000 02ED3FFF
000b4000
* MTXCLU 02EE0000 02EEFFFF
00010000
* VERSION 02EF0000 02EF6FFF
00007000
* LZ32 02F00000 02F05FFF
00006000
* CLUSAPI 02F10000 02F1FFFF
00010000
* RESUTILS 02F20000 02F2CFFF
0000d000
* USERENV 02F30000 02F90FFF
00061000
* rnr20 02FA0000 02FABFFF
0000c000
* iphlpapi 02FF0000 03002FFF
00013000
* ICMP 03010000 03014FFF
00005000
* MPRAPI 03020000 03036FFF
00017000
* OLEAUT32 03040000 030DAFFF
0009b000
* ACTIVEDS 030E0000 0310EFFF
0002f000
* ADSLDPC 03110000 03132FFF
00023000
* RTUTILS 03140000 0314DFFF
0000e000
* SETUPAPI 03150000 031DDFFF
0008e000
* RASAPI32 031E0000 03212FFF
00033000
* RASMAN 03220000 03230FFF
00011000
* TAPI32 03240000 03261FFF
00022000
* COMCTL32 03270000 032F3FFF
00084000
* SHLWAPI 03300000 03364FFF
00065000
* DHCPCSVC 03370000 03388FFF
00019000
* winrnr 03830000 03837FFF
00008000
* rasadhlp 03840000 03844FFF
00005000
* SSNMPN70 03F40000 03F45FFF
00006000
* SSNETLIB 03F50000 03F64FFF
00015000
* security 042A0000 042A3FFF
00004000
* msafd 04B90000 04BADFFF
0001e000
* wshtcpip 04C00000 04C06FFF
00007000
* SSmsLPCn 04CA0000 04CA6FFF
00007000
* ntdsapi 04D80000 04D90FFF
00011000
* SQLFTQRY 063E0000 06411FFF
00032000
* CLBCATQ 06420000 064A5FFF
00086000
* sqloledb 064C0000 06532FFF
00073000
* MSDART 06540000 0655EFFF
0001f000
* comdlg32 06560000 0659DFFF
0003e000
* SHELL32 06630000 06877FFF
00248000
* MSDATL3 06880000 06894FFF
00015000
* oledb32 06D30000 06D95FFF
00066000
* OLEDB32R 06DA0000 06DAFFFF
00010000
* msv1_0 06DB0000 06DCEFFF
0001f000
* CRYPT32 06DD0000 06E47FFF
00078000
* MSASN1 06E50000 06E5FFFF
00010000
* xpsqlbot 06E60000 06E65FFF
00006000
* rsabase 07010000 07032FFF
00023000
* xpstar 08830000 08876FFF
00047000
* SQLRESLD 08880000 08886FFF
00007000
* SQLSVC 08890000 088A6FFF
00017000
* ODBC32 088B0000 088E1FFF
00032000
* odbcbcp 088F0000 088F5FFF
00006000
* W95SCM 08900000 0890BFFF
0000c000
* SQLUNIRL 10000000 1002CFFF
0002d000
* WINSPOOL 08910000 0892DFFF
0001e000
* MPR 08930000 08940FFF
00011000
* SHFOLDER 08950000 08957FFF
00008000
* odbcint 08B20000 08B35FFF
00016000
* NDDEAPI 08B40000 08B46FFF
00007000
* SQLSVC 08B50000 08B55FFF
00006000
* xpstar 08B60000 08B68FFF
00009000
* mswsock 08EF0000 08F01FFF
00012000
* xplog70 09960000 09971FFF
00012000
* xplog70 09980000 09983FFF
00004000
* dbghelp 06E90000 06F44FFF
000b5000
*
ec_buftrace.Entry [62]
bpage = 0x1A010000 bhash = 0x00000000
bpageno = (1:744605)
bdbid = 59 breferences = 8336 bstat
= 0xb
bspin = 0 bnext = 0x00000000
ec_buftrace.Entry [63]
bpage = 0x42F52000 bhash = 0x00000000
bpageno = (1:849240)
bdbid = 59 breferences = 1406 bstat
= 0xb
bspin = 0 bnext = 0x00000000
EXCEPT (null) @.0x0DCEC148
exc_number = 0 exc_severity =
0
exc_func = MSQLErrorHandler+0 Line 0+0x0
Under what circumstances do you see this? Also could you please paste the
"short stack dump" that is present in the error logs.
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.
We have a SQL Server creates a dump file & stops the
service. Any help is highly appeciated.
SQL 2000 (SP3A) on a Windows 2000 Box (SP4)
Thanks,
================================================== =========
==========
BugCheck
Dump
================================================== =========
==========
This file is generated by Microsoft SQL Server
8.00.760
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 PhoenixBIOS 4.0 Release
6.0
Current time is 13:27:01
06/18/04.
4 Intel x86 level 15, 3066 Mhz processor
(s).
Windows NT 5.0 Build 2195 CSD Service Pack
4.
Memory
MemoryLoad = 77%
Total Physical = 2046 MB
Available Physical = 465 MB
Total Page File = 3940 MB
Available Page File = 2463 MB
Total Virtual = 2047 MB
Available Virtual = 288 MB
*Dump thread - spid = 68, PSS = 0x52f031c8, EC =
0x52f034f0
*Stack Dump being sent to d:\Microsoft SQL
Server\MSSQL\log\SQLDump0001.txt
*
************************************************** *********
******************
**
*
* BEGIN STACK
DUMP:
* 06/18/04 13:27:01 spid
68
*
*
*
* Input Buffer 224 bytes -
* CREATE UNIQUE CLUSTERED INDEX [PK_promo] ON [dbo].
[promo] ([promo_id]
* ) WITH DROP_EXISTING ON
[PRIMARY]
*
*
* MODULE BASE END
SIZE
* sqlservr 00400000 00B2CFFF
0072d000
* ntdll 77F80000 77FFAFFF
0007b000
* KERNEL32 7C570000 7C622FFF
000b3000
* ADVAPI32 7C2D0000 7C331FFF
00062000
* RPCRT4 77D30000 77D9DFFF
0006e000
* USER32 77E10000 77E6EFFF
0005f000
* GDI32 77F40000 77F78FFF
00039000
* OPENDS60 41060000 41065FFF
00006000
* MSVCRT 78000000 78044FFF
00045000
* UMS 41070000 4107CFFF
0000d000
* SQLSORT 42AE0000 42B6FFFF
00090000
* MSVCIRT 780A0000 780B1FFF
00012000
* sqlevn70 41080000 41086FFF
00007000
* NETAPI32 027A0000 027EEFFF
0004f000
* SECUR32 027F0000 027FEFFF
0000f000
* NETRAP 02800000 02805FFF
00006000
* SAMLIB 02810000 0281EFFF
0000f000
* WS2_32 02820000 02833FFF
00014000
* WS2HELP 02840000 02847FFF
00008000
* WLDAP32 02850000 02879FFF
0002a000
* DNSAPI 02880000 028A3FFF
00024000
* WSOCK32 028B0000 028B7FFF
00008000
* ole32 02CA0000 02D8BFFF
000ec000
* XOLEHLP 02E10000 02E17FFF
00008000
* MSDTCPRX 02E20000 02ED3FFF
000b4000
* MTXCLU 02EE0000 02EEFFFF
00010000
* VERSION 02EF0000 02EF6FFF
00007000
* LZ32 02F00000 02F05FFF
00006000
* CLUSAPI 02F10000 02F1FFFF
00010000
* RESUTILS 02F20000 02F2CFFF
0000d000
* USERENV 02F30000 02F90FFF
00061000
* rnr20 02FA0000 02FABFFF
0000c000
* iphlpapi 02FF0000 03002FFF
00013000
* ICMP 03010000 03014FFF
00005000
* MPRAPI 03020000 03036FFF
00017000
* OLEAUT32 03040000 030DAFFF
0009b000
* ACTIVEDS 030E0000 0310EFFF
0002f000
* ADSLDPC 03110000 03132FFF
00023000
* RTUTILS 03140000 0314DFFF
0000e000
* SETUPAPI 03150000 031DDFFF
0008e000
* RASAPI32 031E0000 03212FFF
00033000
* RASMAN 03220000 03230FFF
00011000
* TAPI32 03240000 03261FFF
00022000
* COMCTL32 03270000 032F3FFF
00084000
* SHLWAPI 03300000 03364FFF
00065000
* DHCPCSVC 03370000 03388FFF
00019000
* winrnr 03830000 03837FFF
00008000
* rasadhlp 03840000 03844FFF
00005000
* SSNMPN70 03F40000 03F45FFF
00006000
* SSNETLIB 03F50000 03F64FFF
00015000
* security 042A0000 042A3FFF
00004000
* msafd 04B90000 04BADFFF
0001e000
* wshtcpip 04C00000 04C06FFF
00007000
* SSmsLPCn 04CA0000 04CA6FFF
00007000
* ntdsapi 04D80000 04D90FFF
00011000
* SQLFTQRY 063E0000 06411FFF
00032000
* CLBCATQ 06420000 064A5FFF
00086000
* sqloledb 064C0000 06532FFF
00073000
* MSDART 06540000 0655EFFF
0001f000
* comdlg32 06560000 0659DFFF
0003e000
* SHELL32 06630000 06877FFF
00248000
* MSDATL3 06880000 06894FFF
00015000
* oledb32 06D30000 06D95FFF
00066000
* OLEDB32R 06DA0000 06DAFFFF
00010000
* msv1_0 06DB0000 06DCEFFF
0001f000
* CRYPT32 06DD0000 06E47FFF
00078000
* MSASN1 06E50000 06E5FFFF
00010000
* xpsqlbot 06E60000 06E65FFF
00006000
* rsabase 07010000 07032FFF
00023000
* xpstar 08830000 08876FFF
00047000
* SQLRESLD 08880000 08886FFF
00007000
* SQLSVC 08890000 088A6FFF
00017000
* ODBC32 088B0000 088E1FFF
00032000
* odbcbcp 088F0000 088F5FFF
00006000
* W95SCM 08900000 0890BFFF
0000c000
* SQLUNIRL 10000000 1002CFFF
0002d000
* WINSPOOL 08910000 0892DFFF
0001e000
* MPR 08930000 08940FFF
00011000
* SHFOLDER 08950000 08957FFF
00008000
* odbcint 08B20000 08B35FFF
00016000
* NDDEAPI 08B40000 08B46FFF
00007000
* SQLSVC 08B50000 08B55FFF
00006000
* xpstar 08B60000 08B68FFF
00009000
* mswsock 08EF0000 08F01FFF
00012000
* xplog70 09960000 09971FFF
00012000
* xplog70 09980000 09983FFF
00004000
* dbghelp 06E90000 06F44FFF
000b5000
*
ec_buftrace.Entry [62]
bpage = 0x1A010000 bhash = 0x00000000
bpageno = (1:744605)
bdbid = 59 breferences = 8336 bstat
= 0xb
bspin = 0 bnext = 0x00000000
ec_buftrace.Entry [63]
bpage = 0x42F52000 bhash = 0x00000000
bpageno = (1:849240)
bdbid = 59 breferences = 1406 bstat
= 0xb
bspin = 0 bnext = 0x00000000
EXCEPT (null) @.0x0DCEC148
exc_number = 0 exc_severity =
0
exc_func = MSQLErrorHandler+0 Line 0+0x0
Under what circumstances do you see this? Also could you please paste the
"short stack dump" that is present in the error logs.
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.
Dump file
Hi Everyone,
We have a SQL Server creates a dump file & stops the
service. Any help is highly appeciated.
SQL 2000 (SP3A) on a Windows 2000 Box (SP4)
Thanks,
=========================================================== ========== BugCheck
Dump
=========================================================== ==========
This file is generated by Microsoft SQL Server
8.00.760
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 PhoenixBIOS 4.0 Release
6.0
Current time is 13:27:01
06/18/04.
4 Intel x86 level 15, 3066 Mhz processor
(s).
Windows NT 5.0 Build 2195 CSD Service Pack
4.
Memory
MemoryLoad = 77%
Total Physical = 2046 MB
Available Physical = 465 MB
Total Page File = 3940 MB
Available Page File = 2463 MB
Total Virtual = 2047 MB
Available Virtual = 288 MB
*Dump thread - spid = 68, PSS = 0x52f031c8, EC = 0x52f034f0
*Stack Dump being sent to d:\Microsoft SQL
Server\MSSQL\log\SQLDump0001.txt
*
***********************************************************
******************
**
*
* BEGIN STACK
DUMP:
* 06/18/04 13:27:01 spid
68
*
*
*
* Input Buffer 224 bytes -
* CREATE UNIQUE CLUSTERED INDEX [PK_promo] ON [dbo].
[promo] ([promo_id]
* ) WITH DROP_EXISTING ON
[PRIMARY]
*
*
* MODULE BASE END
SIZE
* sqlservr 00400000 00B2CFFF
0072d000
* ntdll 77F80000 77FFAFFF
0007b000
* KERNEL32 7C570000 7C622FFF
000b3000
* ADVAPI32 7C2D0000 7C331FFF
00062000
* RPCRT4 77D30000 77D9DFFF
0006e000
* USER32 77E10000 77E6EFFF
0005f000
* GDI32 77F40000 77F78FFF
00039000
* OPENDS60 41060000 41065FFF
00006000
* MSVCRT 78000000 78044FFF
00045000
* UMS 41070000 4107CFFF
0000d000
* SQLSORT 42AE0000 42B6FFFF
00090000
* MSVCIRT 780A0000 780B1FFF
00012000
* sqlevn70 41080000 41086FFF
00007000
* NETAPI32 027A0000 027EEFFF
0004f000
* SECUR32 027F0000 027FEFFF
0000f000
* NETRAP 02800000 02805FFF
00006000
* SAMLIB 02810000 0281EFFF
0000f000
* WS2_32 02820000 02833FFF
00014000
* WS2HELP 02840000 02847FFF
00008000
* WLDAP32 02850000 02879FFF
0002a000
* DNSAPI 02880000 028A3FFF
00024000
* WSOCK32 028B0000 028B7FFF
00008000
* ole32 02CA0000 02D8BFFF
000ec000
* XOLEHLP 02E10000 02E17FFF
00008000
* MSDTCPRX 02E20000 02ED3FFF
000b4000
* MTXCLU 02EE0000 02EEFFFF
00010000
* VERSION 02EF0000 02EF6FFF
00007000
* LZ32 02F00000 02F05FFF
00006000
* CLUSAPI 02F10000 02F1FFFF
00010000
* RESUTILS 02F20000 02F2CFFF
0000d000
* USERENV 02F30000 02F90FFF
00061000
* rnr20 02FA0000 02FABFFF
0000c000
* iphlpapi 02FF0000 03002FFF
00013000
* ICMP 03010000 03014FFF
00005000
* MPRAPI 03020000 03036FFF
00017000
* OLEAUT32 03040000 030DAFFF
0009b000
* ACTIVEDS 030E0000 0310EFFF
0002f000
* ADSLDPC 03110000 03132FFF
00023000
* RTUTILS 03140000 0314DFFF
0000e000
* SETUPAPI 03150000 031DDFFF
0008e000
* RASAPI32 031E0000 03212FFF
00033000
* RASMAN 03220000 03230FFF
00011000
* TAPI32 03240000 03261FFF
00022000
* COMCTL32 03270000 032F3FFF
00084000
* SHLWAPI 03300000 03364FFF
00065000
* DHCPCSVC 03370000 03388FFF
00019000
* winrnr 03830000 03837FFF
00008000
* rasadhlp 03840000 03844FFF
00005000
* SSNMPN70 03F40000 03F45FFF
00006000
* SSNETLIB 03F50000 03F64FFF
00015000
* security 042A0000 042A3FFF
00004000
* msafd 04B90000 04BADFFF
0001e000
* wshtcpip 04C00000 04C06FFF
00007000
* SSmsLPCn 04CA0000 04CA6FFF
00007000
* ntdsapi 04D80000 04D90FFF
00011000
* SQLFTQRY 063E0000 06411FFF
00032000
* CLBCATQ 06420000 064A5FFF
00086000
* sqloledb 064C0000 06532FFF
00073000
* MSDART 06540000 0655EFFF
0001f000
* comdlg32 06560000 0659DFFF
0003e000
* SHELL32 06630000 06877FFF
00248000
* MSDATL3 06880000 06894FFF
00015000
* oledb32 06D30000 06D95FFF
00066000
* OLEDB32R 06DA0000 06DAFFFF
00010000
* msv1_0 06DB0000 06DCEFFF
0001f000
* CRYPT32 06DD0000 06E47FFF
00078000
* MSASN1 06E50000 06E5FFFF
00010000
* xpsqlbot 06E60000 06E65FFF
00006000
* rsabase 07010000 07032FFF
00023000
* xpstar 08830000 08876FFF
00047000
* SQLRESLD 08880000 08886FFF
00007000
* SQLSVC 08890000 088A6FFF
00017000
* ODBC32 088B0000 088E1FFF
00032000
* odbcbcp 088F0000 088F5FFF
00006000
* W95SCM 08900000 0890BFFF
0000c000
* SQLUNIRL 10000000 1002CFFF
0002d000
* WINSPOOL 08910000 0892DFFF
0001e000
* MPR 08930000 08940FFF
00011000
* SHFOLDER 08950000 08957FFF
00008000
* odbcint 08B20000 08B35FFF
00016000
* NDDEAPI 08B40000 08B46FFF
00007000
* SQLSVC 08B50000 08B55FFF
00006000
* xpstar 08B60000 08B68FFF
00009000
* mswsock 08EF0000 08F01FFF
00012000
* xplog70 09960000 09971FFF
00012000
* xplog70 09980000 09983FFF
00004000
* dbghelp 06E90000 06F44FFF
000b5000
*
ec_buftrace.Entry [62]
--
bpage = 0x1A010000 bhash = 0x00000000
bpageno = (1:744605)
bdbid = 59 breferences = 8336 bstat
= 0xb
bspin = 0 bnext = 0x00000000
ec_buftrace.Entry [63]
--
bpage = 0x42F52000 bhash = 0x00000000
bpageno = (1:849240)
bdbid = 59 breferences = 1406 bstat
= 0xb
bspin = 0 bnext = 0x00000000
EXCEPT (null) @.0x0DCEC148
--
exc_number = 0 exc_severity = 0
exc_func = MSQLErrorHandler+0 Line 0+0x0Under what circumstances do you see this? Also could you please paste the
"short stack dump" that is present in the error logs.
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.
We have a SQL Server creates a dump file & stops the
service. Any help is highly appeciated.
SQL 2000 (SP3A) on a Windows 2000 Box (SP4)
Thanks,
=========================================================== ========== BugCheck
Dump
=========================================================== ==========
This file is generated by Microsoft SQL Server
8.00.760
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 PhoenixBIOS 4.0 Release
6.0
Current time is 13:27:01
06/18/04.
4 Intel x86 level 15, 3066 Mhz processor
(s).
Windows NT 5.0 Build 2195 CSD Service Pack
4.
Memory
MemoryLoad = 77%
Total Physical = 2046 MB
Available Physical = 465 MB
Total Page File = 3940 MB
Available Page File = 2463 MB
Total Virtual = 2047 MB
Available Virtual = 288 MB
*Dump thread - spid = 68, PSS = 0x52f031c8, EC = 0x52f034f0
*Stack Dump being sent to d:\Microsoft SQL
Server\MSSQL\log\SQLDump0001.txt
*
***********************************************************
******************
**
*
* BEGIN STACK
DUMP:
* 06/18/04 13:27:01 spid
68
*
*
*
* Input Buffer 224 bytes -
* CREATE UNIQUE CLUSTERED INDEX [PK_promo] ON [dbo].
[promo] ([promo_id]
* ) WITH DROP_EXISTING ON
[PRIMARY]
*
*
* MODULE BASE END
SIZE
* sqlservr 00400000 00B2CFFF
0072d000
* ntdll 77F80000 77FFAFFF
0007b000
* KERNEL32 7C570000 7C622FFF
000b3000
* ADVAPI32 7C2D0000 7C331FFF
00062000
* RPCRT4 77D30000 77D9DFFF
0006e000
* USER32 77E10000 77E6EFFF
0005f000
* GDI32 77F40000 77F78FFF
00039000
* OPENDS60 41060000 41065FFF
00006000
* MSVCRT 78000000 78044FFF
00045000
* UMS 41070000 4107CFFF
0000d000
* SQLSORT 42AE0000 42B6FFFF
00090000
* MSVCIRT 780A0000 780B1FFF
00012000
* sqlevn70 41080000 41086FFF
00007000
* NETAPI32 027A0000 027EEFFF
0004f000
* SECUR32 027F0000 027FEFFF
0000f000
* NETRAP 02800000 02805FFF
00006000
* SAMLIB 02810000 0281EFFF
0000f000
* WS2_32 02820000 02833FFF
00014000
* WS2HELP 02840000 02847FFF
00008000
* WLDAP32 02850000 02879FFF
0002a000
* DNSAPI 02880000 028A3FFF
00024000
* WSOCK32 028B0000 028B7FFF
00008000
* ole32 02CA0000 02D8BFFF
000ec000
* XOLEHLP 02E10000 02E17FFF
00008000
* MSDTCPRX 02E20000 02ED3FFF
000b4000
* MTXCLU 02EE0000 02EEFFFF
00010000
* VERSION 02EF0000 02EF6FFF
00007000
* LZ32 02F00000 02F05FFF
00006000
* CLUSAPI 02F10000 02F1FFFF
00010000
* RESUTILS 02F20000 02F2CFFF
0000d000
* USERENV 02F30000 02F90FFF
00061000
* rnr20 02FA0000 02FABFFF
0000c000
* iphlpapi 02FF0000 03002FFF
00013000
* ICMP 03010000 03014FFF
00005000
* MPRAPI 03020000 03036FFF
00017000
* OLEAUT32 03040000 030DAFFF
0009b000
* ACTIVEDS 030E0000 0310EFFF
0002f000
* ADSLDPC 03110000 03132FFF
00023000
* RTUTILS 03140000 0314DFFF
0000e000
* SETUPAPI 03150000 031DDFFF
0008e000
* RASAPI32 031E0000 03212FFF
00033000
* RASMAN 03220000 03230FFF
00011000
* TAPI32 03240000 03261FFF
00022000
* COMCTL32 03270000 032F3FFF
00084000
* SHLWAPI 03300000 03364FFF
00065000
* DHCPCSVC 03370000 03388FFF
00019000
* winrnr 03830000 03837FFF
00008000
* rasadhlp 03840000 03844FFF
00005000
* SSNMPN70 03F40000 03F45FFF
00006000
* SSNETLIB 03F50000 03F64FFF
00015000
* security 042A0000 042A3FFF
00004000
* msafd 04B90000 04BADFFF
0001e000
* wshtcpip 04C00000 04C06FFF
00007000
* SSmsLPCn 04CA0000 04CA6FFF
00007000
* ntdsapi 04D80000 04D90FFF
00011000
* SQLFTQRY 063E0000 06411FFF
00032000
* CLBCATQ 06420000 064A5FFF
00086000
* sqloledb 064C0000 06532FFF
00073000
* MSDART 06540000 0655EFFF
0001f000
* comdlg32 06560000 0659DFFF
0003e000
* SHELL32 06630000 06877FFF
00248000
* MSDATL3 06880000 06894FFF
00015000
* oledb32 06D30000 06D95FFF
00066000
* OLEDB32R 06DA0000 06DAFFFF
00010000
* msv1_0 06DB0000 06DCEFFF
0001f000
* CRYPT32 06DD0000 06E47FFF
00078000
* MSASN1 06E50000 06E5FFFF
00010000
* xpsqlbot 06E60000 06E65FFF
00006000
* rsabase 07010000 07032FFF
00023000
* xpstar 08830000 08876FFF
00047000
* SQLRESLD 08880000 08886FFF
00007000
* SQLSVC 08890000 088A6FFF
00017000
* ODBC32 088B0000 088E1FFF
00032000
* odbcbcp 088F0000 088F5FFF
00006000
* W95SCM 08900000 0890BFFF
0000c000
* SQLUNIRL 10000000 1002CFFF
0002d000
* WINSPOOL 08910000 0892DFFF
0001e000
* MPR 08930000 08940FFF
00011000
* SHFOLDER 08950000 08957FFF
00008000
* odbcint 08B20000 08B35FFF
00016000
* NDDEAPI 08B40000 08B46FFF
00007000
* SQLSVC 08B50000 08B55FFF
00006000
* xpstar 08B60000 08B68FFF
00009000
* mswsock 08EF0000 08F01FFF
00012000
* xplog70 09960000 09971FFF
00012000
* xplog70 09980000 09983FFF
00004000
* dbghelp 06E90000 06F44FFF
000b5000
*
ec_buftrace.Entry [62]
--
bpage = 0x1A010000 bhash = 0x00000000
bpageno = (1:744605)
bdbid = 59 breferences = 8336 bstat
= 0xb
bspin = 0 bnext = 0x00000000
ec_buftrace.Entry [63]
--
bpage = 0x42F52000 bhash = 0x00000000
bpageno = (1:849240)
bdbid = 59 breferences = 1406 bstat
= 0xb
bspin = 0 bnext = 0x00000000
EXCEPT (null) @.0x0DCEC148
--
exc_number = 0 exc_severity = 0
exc_func = MSQLErrorHandler+0 Line 0+0x0Under what circumstances do you see this? Also could you please paste the
"short stack dump" that is present in the error logs.
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.
Dump file
Hi Everyone,
We have a SQL Server creates a dump file & stops the
service. Any help is highly appeciated.
SQL 2000 (SP3A) on a Windows 2000 Box (SP4)
Thanks,
========================================
===================
==========
BugCheck
Dump
========================================
===================
==========
This file is generated by Microsoft SQL Server
8.00.760
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 PhoenixBIOS 4.0 Release
6.0
Current time is 13:27:01
06/18/04.
4 Intel x86 level 15, 3066 Mhz processor
(s).
Windows NT 5.0 Build 2195 CSD Service Pack
4.
Memory
MemoryLoad = 77%
Total Physical = 2046 MB
Available Physical = 465 MB
Total Page File = 3940 MB
Available Page File = 2463 MB
Total Virtual = 2047 MB
Available Virtual = 288 MB
*Dump thread - spid = 68, PSS = 0x52f031c8, EC =
0x52f034f0
*Stack Dump being sent to d:\Microsoft SQL
Server\MSSQL\log\SQLDump0001.txt
*
****************************************
*******************
******************
**
*
* BEGIN STACK
DUMP:
* 06/18/04 13:27:01 spid
68
*
*
*
* Input Buffer 224 bytes -
* CREATE UNIQUE CLUSTERED INDEX [PK_promo] ON [dbo].
[promo] ([promo_id]
* ) WITH DROP_EXISTING ON
[PRIMARY]
*
*
* MODULE BASE END
SIZE
* sqlservr 00400000 00B2CFFF
0072d000
* ntdll 77F80000 77FFAFFF
0007b000
* KERNEL32 7C570000 7C622FFF
000b3000
* ADVAPI32 7C2D0000 7C331FFF
00062000
* RPCRT4 77D30000 77D9DFFF
0006e000
* USER32 77E10000 77E6EFFF
0005f000
* GDI32 77F40000 77F78FFF
00039000
* OPENDS60 41060000 41065FFF
00006000
* MSVCRT 78000000 78044FFF
00045000
* UMS 41070000 4107CFFF
0000d000
* SQLSORT 42AE0000 42B6FFFF
00090000
* MSVCIRT 780A0000 780B1FFF
00012000
* sqlevn70 41080000 41086FFF
00007000
* NETAPI32 027A0000 027EEFFF
0004f000
* SECUR32 027F0000 027FEFFF
0000f000
* NETRAP 02800000 02805FFF
00006000
* SAMLIB 02810000 0281EFFF
0000f000
* WS2_32 02820000 02833FFF
00014000
* WS2HELP 02840000 02847FFF
00008000
* WLDAP32 02850000 02879FFF
0002a000
* DNSAPI 02880000 028A3FFF
00024000
* WSOCK32 028B0000 028B7FFF
00008000
* ole32 02CA0000 02D8BFFF
000ec000
* XOLEHLP 02E10000 02E17FFF
00008000
* MSDTCPRX 02E20000 02ED3FFF
000b4000
* MTXCLU 02EE0000 02EEFFFF
00010000
* VERSION 02EF0000 02EF6FFF
00007000
* LZ32 02F00000 02F05FFF
00006000
* CLUSAPI 02F10000 02F1FFFF
00010000
* RESUTILS 02F20000 02F2CFFF
0000d000
* USERENV 02F30000 02F90FFF
00061000
* rnr20 02FA0000 02FABFFF
0000c000
* iphlpapi 02FF0000 03002FFF
00013000
* ICMP 03010000 03014FFF
00005000
* MPRAPI 03020000 03036FFF
00017000
* OLEAUT32 03040000 030DAFFF
0009b000
* ACTIVEDS 030E0000 0310EFFF
0002f000
* ADSLDPC 03110000 03132FFF
00023000
* RTUTILS 03140000 0314DFFF
0000e000
* SETUPAPI 03150000 031DDFFF
0008e000
* RASAPI32 031E0000 03212FFF
00033000
* RASMAN 03220000 03230FFF
00011000
* TAPI32 03240000 03261FFF
00022000
* COMCTL32 03270000 032F3FFF
00084000
* SHLWAPI 03300000 03364FFF
00065000
* DHCPCSVC 03370000 03388FFF
00019000
* winrnr 03830000 03837FFF
00008000
* rasadhlp 03840000 03844FFF
00005000
* SSNMPN70 03F40000 03F45FFF
00006000
* SSNETLIB 03F50000 03F64FFF
00015000
* security 042A0000 042A3FFF
00004000
* msafd 04B90000 04BADFFF
0001e000
* wshtcpip 04C00000 04C06FFF
00007000
* SSmsLPCn 04CA0000 04CA6FFF
00007000
* ntdsapi 04D80000 04D90FFF
00011000
* SQLFTQRY 063E0000 06411FFF
00032000
* CLBCATQ 06420000 064A5FFF
00086000
* sqloledb 064C0000 06532FFF
00073000
* MSDART 06540000 0655EFFF
0001f000
* comdlg32 06560000 0659DFFF
0003e000
* SHELL32 06630000 06877FFF
00248000
* MSDATL3 06880000 06894FFF
00015000
* oledb32 06D30000 06D95FFF
00066000
* OLEDB32R 06DA0000 06DAFFFF
00010000
* msv1_0 06DB0000 06DCEFFF
0001f000
* CRYPT32 06DD0000 06E47FFF
00078000
* MSASN1 06E50000 06E5FFFF
00010000
* xpsqlbot 06E60000 06E65FFF
00006000
* rsabase 07010000 07032FFF
00023000
* xpstar 08830000 08876FFF
00047000
* SQLRESLD 08880000 08886FFF
00007000
* SQLSVC 08890000 088A6FFF
00017000
* ODBC32 088B0000 088E1FFF
00032000
* odbcbcp 088F0000 088F5FFF
00006000
* W95SCM 08900000 0890BFFF
0000c000
* SQLUNIRL 10000000 1002CFFF
0002d000
* WINSPOOL 08910000 0892DFFF
0001e000
* MPR 08930000 08940FFF
00011000
* SHFOLDER 08950000 08957FFF
00008000
* odbcint 08B20000 08B35FFF
00016000
* NDDEAPI 08B40000 08B46FFF
00007000
* SQLSVC 08B50000 08B55FFF
00006000
* xpstar 08B60000 08B68FFF
00009000
* mswsock 08EF0000 08F01FFF
00012000
* xplog70 09960000 09971FFF
00012000
* xplog70 09980000 09983FFF
00004000
* dbghelp 06E90000 06F44FFF
000b5000
*
ec_buftrace.Entry [62]
--
bpage = 0x1A010000 bhash = 0x00000000
bpageno = (1:744605)
bdbid = 59 breferences = 8336 bstat
= 0xb
bspin = 0 bnext = 0x00000000
ec_buftrace.Entry [63]
--
bpage = 0x42F52000 bhash = 0x00000000
bpageno = (1:849240)
bdbid = 59 breferences = 1406 bstat
= 0xb
bspin = 0 bnext = 0x00000000
EXCEPT (null) @.0x0DCEC148
--
exc_number = 0 exc_severity =
0
exc_func = MSQLErrorHandler+0 Line 0+0x0Under what circumstances do you see this? Also could you please paste the
"short stack dump" that is present in the error logs.
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.
We have a SQL Server creates a dump file & stops the
service. Any help is highly appeciated.
SQL 2000 (SP3A) on a Windows 2000 Box (SP4)
Thanks,
========================================
===================
==========
BugCheck
Dump
========================================
===================
==========
This file is generated by Microsoft SQL Server
8.00.760
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 PhoenixBIOS 4.0 Release
6.0
Current time is 13:27:01
06/18/04.
4 Intel x86 level 15, 3066 Mhz processor
(s).
Windows NT 5.0 Build 2195 CSD Service Pack
4.
Memory
MemoryLoad = 77%
Total Physical = 2046 MB
Available Physical = 465 MB
Total Page File = 3940 MB
Available Page File = 2463 MB
Total Virtual = 2047 MB
Available Virtual = 288 MB
*Dump thread - spid = 68, PSS = 0x52f031c8, EC =
0x52f034f0
*Stack Dump being sent to d:\Microsoft SQL
Server\MSSQL\log\SQLDump0001.txt
*
****************************************
*******************
******************
**
*
* BEGIN STACK
DUMP:
* 06/18/04 13:27:01 spid
68
*
*
*
* Input Buffer 224 bytes -
* CREATE UNIQUE CLUSTERED INDEX [PK_promo] ON [dbo].
[promo] ([promo_id]
* ) WITH DROP_EXISTING ON
[PRIMARY]
*
*
* MODULE BASE END
SIZE
* sqlservr 00400000 00B2CFFF
0072d000
* ntdll 77F80000 77FFAFFF
0007b000
* KERNEL32 7C570000 7C622FFF
000b3000
* ADVAPI32 7C2D0000 7C331FFF
00062000
* RPCRT4 77D30000 77D9DFFF
0006e000
* USER32 77E10000 77E6EFFF
0005f000
* GDI32 77F40000 77F78FFF
00039000
* OPENDS60 41060000 41065FFF
00006000
* MSVCRT 78000000 78044FFF
00045000
* UMS 41070000 4107CFFF
0000d000
* SQLSORT 42AE0000 42B6FFFF
00090000
* MSVCIRT 780A0000 780B1FFF
00012000
* sqlevn70 41080000 41086FFF
00007000
* NETAPI32 027A0000 027EEFFF
0004f000
* SECUR32 027F0000 027FEFFF
0000f000
* NETRAP 02800000 02805FFF
00006000
* SAMLIB 02810000 0281EFFF
0000f000
* WS2_32 02820000 02833FFF
00014000
* WS2HELP 02840000 02847FFF
00008000
* WLDAP32 02850000 02879FFF
0002a000
* DNSAPI 02880000 028A3FFF
00024000
* WSOCK32 028B0000 028B7FFF
00008000
* ole32 02CA0000 02D8BFFF
000ec000
* XOLEHLP 02E10000 02E17FFF
00008000
* MSDTCPRX 02E20000 02ED3FFF
000b4000
* MTXCLU 02EE0000 02EEFFFF
00010000
* VERSION 02EF0000 02EF6FFF
00007000
* LZ32 02F00000 02F05FFF
00006000
* CLUSAPI 02F10000 02F1FFFF
00010000
* RESUTILS 02F20000 02F2CFFF
0000d000
* USERENV 02F30000 02F90FFF
00061000
* rnr20 02FA0000 02FABFFF
0000c000
* iphlpapi 02FF0000 03002FFF
00013000
* ICMP 03010000 03014FFF
00005000
* MPRAPI 03020000 03036FFF
00017000
* OLEAUT32 03040000 030DAFFF
0009b000
* ACTIVEDS 030E0000 0310EFFF
0002f000
* ADSLDPC 03110000 03132FFF
00023000
* RTUTILS 03140000 0314DFFF
0000e000
* SETUPAPI 03150000 031DDFFF
0008e000
* RASAPI32 031E0000 03212FFF
00033000
* RASMAN 03220000 03230FFF
00011000
* TAPI32 03240000 03261FFF
00022000
* COMCTL32 03270000 032F3FFF
00084000
* SHLWAPI 03300000 03364FFF
00065000
* DHCPCSVC 03370000 03388FFF
00019000
* winrnr 03830000 03837FFF
00008000
* rasadhlp 03840000 03844FFF
00005000
* SSNMPN70 03F40000 03F45FFF
00006000
* SSNETLIB 03F50000 03F64FFF
00015000
* security 042A0000 042A3FFF
00004000
* msafd 04B90000 04BADFFF
0001e000
* wshtcpip 04C00000 04C06FFF
00007000
* SSmsLPCn 04CA0000 04CA6FFF
00007000
* ntdsapi 04D80000 04D90FFF
00011000
* SQLFTQRY 063E0000 06411FFF
00032000
* CLBCATQ 06420000 064A5FFF
00086000
* sqloledb 064C0000 06532FFF
00073000
* MSDART 06540000 0655EFFF
0001f000
* comdlg32 06560000 0659DFFF
0003e000
* SHELL32 06630000 06877FFF
00248000
* MSDATL3 06880000 06894FFF
00015000
* oledb32 06D30000 06D95FFF
00066000
* OLEDB32R 06DA0000 06DAFFFF
00010000
* msv1_0 06DB0000 06DCEFFF
0001f000
* CRYPT32 06DD0000 06E47FFF
00078000
* MSASN1 06E50000 06E5FFFF
00010000
* xpsqlbot 06E60000 06E65FFF
00006000
* rsabase 07010000 07032FFF
00023000
* xpstar 08830000 08876FFF
00047000
* SQLRESLD 08880000 08886FFF
00007000
* SQLSVC 08890000 088A6FFF
00017000
* ODBC32 088B0000 088E1FFF
00032000
* odbcbcp 088F0000 088F5FFF
00006000
* W95SCM 08900000 0890BFFF
0000c000
* SQLUNIRL 10000000 1002CFFF
0002d000
* WINSPOOL 08910000 0892DFFF
0001e000
* MPR 08930000 08940FFF
00011000
* SHFOLDER 08950000 08957FFF
00008000
* odbcint 08B20000 08B35FFF
00016000
* NDDEAPI 08B40000 08B46FFF
00007000
* SQLSVC 08B50000 08B55FFF
00006000
* xpstar 08B60000 08B68FFF
00009000
* mswsock 08EF0000 08F01FFF
00012000
* xplog70 09960000 09971FFF
00012000
* xplog70 09980000 09983FFF
00004000
* dbghelp 06E90000 06F44FFF
000b5000
*
ec_buftrace.Entry [62]
--
bpage = 0x1A010000 bhash = 0x00000000
bpageno = (1:744605)
bdbid = 59 breferences = 8336 bstat
= 0xb
bspin = 0 bnext = 0x00000000
ec_buftrace.Entry [63]
--
bpage = 0x42F52000 bhash = 0x00000000
bpageno = (1:849240)
bdbid = 59 breferences = 1406 bstat
= 0xb
bspin = 0 bnext = 0x00000000
EXCEPT (null) @.0x0DCEC148
--
exc_number = 0 exc_severity =
0
exc_func = MSQLErrorHandler+0 Line 0+0x0Under what circumstances do you see this? Also could you please paste the
"short stack dump" that is present in the error logs.
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.
Dumb question: How do I view a report?
I have SSRS installed, but when I try to navigate to it via IE, I'm prompted
for my username and password even though I'm using Windows integrated
security for SQL Server. What do I need to do to create/access reports?Never mind. I'd typed in http://localhost/ReportServices$SQLSERVER2005 when
I was prompted for a username and password. I should've typed in
http://localhost/Reports$SQLSERVER2005/Pages/ReportViewer.aspx ...
As I said, it's a dumb question ... hahaha.
"AlBruAn" wrote:
> I have SSRS installed, but when I try to navigate to it via IE, I'm prompted
> for my username and password even though I'm using Windows integrated
> security for SQL Server. What do I need to do to create/access reports?|||On Apr 9, 1:22 pm, AlBruAn <albr...@.hotmail.com.(donotspam)> wrote:
> I have SSRS installed, but when I try to navigate to it via IE, I'm prompted
> for my username and password even though I'm using Windows integrated
> security for SQL Server. What do I need to do to create/access reports?
If you are using a browser other than IE, this may occur. If not, then
you will want to check the Directory Security (for the Reports and
ReportServer virtual directories). You do this via: Right-click My
Computer -> Select Manage -> Navigate to Services and Applications ->
Internet Information Services -> Web Sites -> Default Web Site. Then,
right-click Reports (or ReportServer) and select Properties -> select
the Directory Security tab -> select the Edit button just below
'Anonymous access and authentication control' and check to see if you
have either 'Anonymous access' selected or 'Integrated Windows
Authentication.' If anonymous is selected, most likely SSRS will not
allow you to avoid providing authentication (if it allows navigation
to the URL at all). Hope this helps.
Regards,
Enrique Martinez
Sr. Software Consultant
for my username and password even though I'm using Windows integrated
security for SQL Server. What do I need to do to create/access reports?Never mind. I'd typed in http://localhost/ReportServices$SQLSERVER2005 when
I was prompted for a username and password. I should've typed in
http://localhost/Reports$SQLSERVER2005/Pages/ReportViewer.aspx ...
As I said, it's a dumb question ... hahaha.
"AlBruAn" wrote:
> I have SSRS installed, but when I try to navigate to it via IE, I'm prompted
> for my username and password even though I'm using Windows integrated
> security for SQL Server. What do I need to do to create/access reports?|||On Apr 9, 1:22 pm, AlBruAn <albr...@.hotmail.com.(donotspam)> wrote:
> I have SSRS installed, but when I try to navigate to it via IE, I'm prompted
> for my username and password even though I'm using Windows integrated
> security for SQL Server. What do I need to do to create/access reports?
If you are using a browser other than IE, this may occur. If not, then
you will want to check the Directory Security (for the Reports and
ReportServer virtual directories). You do this via: Right-click My
Computer -> Select Manage -> Navigate to Services and Applications ->
Internet Information Services -> Web Sites -> Default Web Site. Then,
right-click Reports (or ReportServer) and select Properties -> select
the Directory Security tab -> select the Edit button just below
'Anonymous access and authentication control' and check to see if you
have either 'Anonymous access' selected or 'Integrated Windows
Authentication.' If anonymous is selected, most likely SSRS will not
allow you to avoid providing authentication (if it allows navigation
to the URL at all). Hope this helps.
Regards,
Enrique Martinez
Sr. Software Consultant
Sunday, March 11, 2012
Dumb permissions question
Hi
I'm running SQL Server 2000 on a Windows 2003 SBS server. Much to my
horror I notice that that the SQL data directory has permissions set
for:
Domain\Administrator (full accesss)
Domain\Administrators (full accesss)
Authenticated users (read,list, read). I guess this isn't a good idea
at all!
What are the optimum permissions here (I can't seem to get a straight
answer). Do I set it for the SQL service to have full control only (at
the moment MSSQLSERVER service is logging on using
Domain\Administrator). Do I change this account? What about the other
SQL Server related services? Please also note I am also using Backup
Exec 9 to backup the databases.
Any suggestions you may have will be greatly appreciated!
Many thanks
Alex<postings@.alexshirley.com> wrote in message
news:1133285607.162678.51170@.g14g2000cwa.googlegroups.com...
> Hi
> I'm running SQL Server 2000 on a Windows 2003 SBS server. Much to my
> horror I notice that that the SQL data directory has permissions set
> for:
> Domain\Administrator (full accesss)
> Domain\Administrators (full accesss)
> Authenticated users (read,list, read). I guess this isn't a good idea
> at all!
> What are the optimum permissions here (I can't seem to get a straight
> answer). Do I set it for the SQL service to have full control only (at
> the moment MSSQLSERVER service is logging on using
> Domain\Administrator). Do I change this account? What about the other
> SQL Server related services? Please also note I am also using Backup
> Exec 9 to backup the databases.
> Any suggestions you may have will be greatly appreciated!
> Many thanks
> Alex
On my SQL Server 2000 database running on Windows 2003 standard server, the
permissions on the SQL data directory are just for Domain\Administrators,
full access. The MSSQLServer service is set to use the local system account.
If your authenticated users have access then you should be able to revoke
that without problem.
I don't know where Backup Exec fits into the picture - I don't use it - but
it shouldn't be backing up the files directly so it shouldn't need any
permissions on the folder.
Hope this is useful.
--
Brian Cryer
www.cryer.co.uk/brian|||Great, thanks for your help Brian...!
Alex
-->
Brian Cryer wrote:
> <postings@.alexshirley.com> wrote in message
> news:1133285607.162678.51170@.g14g2000cwa.googlegroups.com...
> On my SQL Server 2000 database running on Windows 2003 standard server, th
e
> permissions on the SQL data directory are just for Domain\Administrators,
> full access. The MSSQLServer service is set to use the local system accoun
t.
> If your authenticated users have access then you should be able to revoke
> that without problem.
> I don't know where Backup Exec fits into the picture - I don't use it - bu
t
> it shouldn't be backing up the files directly so it shouldn't need any
> permissions on the folder.
> Hope this is useful.
> --
> Brian Cryer
> www.cryer.co.uk/brian
I'm running SQL Server 2000 on a Windows 2003 SBS server. Much to my
horror I notice that that the SQL data directory has permissions set
for:
Domain\Administrator (full accesss)
Domain\Administrators (full accesss)
Authenticated users (read,list, read). I guess this isn't a good idea
at all!
What are the optimum permissions here (I can't seem to get a straight
answer). Do I set it for the SQL service to have full control only (at
the moment MSSQLSERVER service is logging on using
Domain\Administrator). Do I change this account? What about the other
SQL Server related services? Please also note I am also using Backup
Exec 9 to backup the databases.
Any suggestions you may have will be greatly appreciated!
Many thanks
Alex<postings@.alexshirley.com> wrote in message
news:1133285607.162678.51170@.g14g2000cwa.googlegroups.com...
> Hi
> I'm running SQL Server 2000 on a Windows 2003 SBS server. Much to my
> horror I notice that that the SQL data directory has permissions set
> for:
> Domain\Administrator (full accesss)
> Domain\Administrators (full accesss)
> Authenticated users (read,list, read). I guess this isn't a good idea
> at all!
> What are the optimum permissions here (I can't seem to get a straight
> answer). Do I set it for the SQL service to have full control only (at
> the moment MSSQLSERVER service is logging on using
> Domain\Administrator). Do I change this account? What about the other
> SQL Server related services? Please also note I am also using Backup
> Exec 9 to backup the databases.
> Any suggestions you may have will be greatly appreciated!
> Many thanks
> Alex
On my SQL Server 2000 database running on Windows 2003 standard server, the
permissions on the SQL data directory are just for Domain\Administrators,
full access. The MSSQLServer service is set to use the local system account.
If your authenticated users have access then you should be able to revoke
that without problem.
I don't know where Backup Exec fits into the picture - I don't use it - but
it shouldn't be backing up the files directly so it shouldn't need any
permissions on the folder.
Hope this is useful.
--
Brian Cryer
www.cryer.co.uk/brian|||Great, thanks for your help Brian...!
Alex
-->
Brian Cryer wrote:
> <postings@.alexshirley.com> wrote in message
> news:1133285607.162678.51170@.g14g2000cwa.googlegroups.com...
> On my SQL Server 2000 database running on Windows 2003 standard server, th
e
> permissions on the SQL data directory are just for Domain\Administrators,
> full access. The MSSQLServer service is set to use the local system accoun
t.
> If your authenticated users have access then you should be able to revoke
> that without problem.
> I don't know where Backup Exec fits into the picture - I don't use it - bu
t
> it shouldn't be backing up the files directly so it shouldn't need any
> permissions on the folder.
> Hope this is useful.
> --
> Brian Cryer
> www.cryer.co.uk/brian
Dumb permissions question
Hi
I'm running SQL Server 2000 on a Windows 2003 SBS server. Much to my
horror I notice that that the SQL data directory has permissions set
for:
Domain\Administrator (full accesss)
Domain\Administrators (full accesss)
Authenticated users (read,list, read). I guess this isn't a good idea
at all!
What are the optimum permissions here (I can't seem to get a straight
answer). Do I set it for the SQL service to have full control only (at
the moment MSSQLSERVER service is logging on using
Domain\Administrator). Do I change this account? What about the other
SQL Server related services? Please also note I am also using Backup
Exec 9 to backup the databases.
Any suggestions you may have will be greatly appreciated!
Many thanks
Alex
<postings@.alexshirley.com> wrote in message
news:1133285607.162678.51170@.g14g2000cwa.googlegro ups.com...
> Hi
> I'm running SQL Server 2000 on a Windows 2003 SBS server. Much to my
> horror I notice that that the SQL data directory has permissions set
> for:
> Domain\Administrator (full accesss)
> Domain\Administrators (full accesss)
> Authenticated users (read,list, read). I guess this isn't a good idea
> at all!
> What are the optimum permissions here (I can't seem to get a straight
> answer). Do I set it for the SQL service to have full control only (at
> the moment MSSQLSERVER service is logging on using
> Domain\Administrator). Do I change this account? What about the other
> SQL Server related services? Please also note I am also using Backup
> Exec 9 to backup the databases.
> Any suggestions you may have will be greatly appreciated!
> Many thanks
> Alex
On my SQL Server 2000 database running on Windows 2003 standard server, the
permissions on the SQL data directory are just for Domain\Administrators,
full access. The MSSQLServer service is set to use the local system account.
If your authenticated users have access then you should be able to revoke
that without problem.
I don't know where Backup Exec fits into the picture - I don't use it - but
it shouldn't be backing up the files directly so it shouldn't need any
permissions on the folder.
Hope this is useful.
Brian Cryer
www.cryer.co.uk/brian
|||Great, thanks for your help Brian...!
Alex
-->
Brian Cryer wrote:
> <postings@.alexshirley.com> wrote in message
> news:1133285607.162678.51170@.g14g2000cwa.googlegro ups.com...
> On my SQL Server 2000 database running on Windows 2003 standard server, the
> permissions on the SQL data directory are just for Domain\Administrators,
> full access. The MSSQLServer service is set to use the local system account.
> If your authenticated users have access then you should be able to revoke
> that without problem.
> I don't know where Backup Exec fits into the picture - I don't use it - but
> it shouldn't be backing up the files directly so it shouldn't need any
> permissions on the folder.
> Hope this is useful.
> --
> Brian Cryer
> www.cryer.co.uk/brian
I'm running SQL Server 2000 on a Windows 2003 SBS server. Much to my
horror I notice that that the SQL data directory has permissions set
for:
Domain\Administrator (full accesss)
Domain\Administrators (full accesss)
Authenticated users (read,list, read). I guess this isn't a good idea
at all!
What are the optimum permissions here (I can't seem to get a straight
answer). Do I set it for the SQL service to have full control only (at
the moment MSSQLSERVER service is logging on using
Domain\Administrator). Do I change this account? What about the other
SQL Server related services? Please also note I am also using Backup
Exec 9 to backup the databases.
Any suggestions you may have will be greatly appreciated!
Many thanks
Alex
<postings@.alexshirley.com> wrote in message
news:1133285607.162678.51170@.g14g2000cwa.googlegro ups.com...
> Hi
> I'm running SQL Server 2000 on a Windows 2003 SBS server. Much to my
> horror I notice that that the SQL data directory has permissions set
> for:
> Domain\Administrator (full accesss)
> Domain\Administrators (full accesss)
> Authenticated users (read,list, read). I guess this isn't a good idea
> at all!
> What are the optimum permissions here (I can't seem to get a straight
> answer). Do I set it for the SQL service to have full control only (at
> the moment MSSQLSERVER service is logging on using
> Domain\Administrator). Do I change this account? What about the other
> SQL Server related services? Please also note I am also using Backup
> Exec 9 to backup the databases.
> Any suggestions you may have will be greatly appreciated!
> Many thanks
> Alex
On my SQL Server 2000 database running on Windows 2003 standard server, the
permissions on the SQL data directory are just for Domain\Administrators,
full access. The MSSQLServer service is set to use the local system account.
If your authenticated users have access then you should be able to revoke
that without problem.
I don't know where Backup Exec fits into the picture - I don't use it - but
it shouldn't be backing up the files directly so it shouldn't need any
permissions on the folder.
Hope this is useful.
Brian Cryer
www.cryer.co.uk/brian
|||Great, thanks for your help Brian...!
Alex
-->
Brian Cryer wrote:
> <postings@.alexshirley.com> wrote in message
> news:1133285607.162678.51170@.g14g2000cwa.googlegro ups.com...
> On my SQL Server 2000 database running on Windows 2003 standard server, the
> permissions on the SQL data directory are just for Domain\Administrators,
> full access. The MSSQLServer service is set to use the local system account.
> If your authenticated users have access then you should be able to revoke
> that without problem.
> I don't know where Backup Exec fits into the picture - I don't use it - but
> it shouldn't be backing up the files directly so it shouldn't need any
> permissions on the folder.
> Hope this is useful.
> --
> Brian Cryer
> www.cryer.co.uk/brian
Dumb permissions question
Hi
I'm running SQL Server 2000 on a Windows 2003 SBS server. Much to my
horror I notice that that the SQL data directory has permissions set
for:
Domain\Administrator (full accesss)
Domain\Administrators (full accesss)
Authenticated users (read,list, read). I guess this isn't a good idea
at all!
What are the optimum permissions here (I can't seem to get a straight
answer). Do I set it for the SQL service to have full control only (at
the moment MSSQLSERVER service is logging on using
Domain\Administrator). Do I change this account? What about the other
SQL Server related services? Please also note I am also using Backup
Exec 9 to backup the databases.
Any suggestions you may have will be greatly appreciated!
Many thanks
Alex<postings@.alexshirley.com> wrote in message
news:1133285607.162678.51170@.g14g2000cwa.googlegroups.com...
> Hi
> I'm running SQL Server 2000 on a Windows 2003 SBS server. Much to my
> horror I notice that that the SQL data directory has permissions set
> for:
> Domain\Administrator (full accesss)
> Domain\Administrators (full accesss)
> Authenticated users (read,list, read). I guess this isn't a good idea
> at all!
> What are the optimum permissions here (I can't seem to get a straight
> answer). Do I set it for the SQL service to have full control only (at
> the moment MSSQLSERVER service is logging on using
> Domain\Administrator). Do I change this account? What about the other
> SQL Server related services? Please also note I am also using Backup
> Exec 9 to backup the databases.
> Any suggestions you may have will be greatly appreciated!
> Many thanks
> Alex
On my SQL Server 2000 database running on Windows 2003 standard server, the
permissions on the SQL data directory are just for Domain\Administrators,
full access. The MSSQLServer service is set to use the local system account.
If your authenticated users have access then you should be able to revoke
that without problem.
I don't know where Backup Exec fits into the picture - I don't use it - but
it shouldn't be backing up the files directly so it shouldn't need any
permissions on the folder.
Hope this is useful.
--
Brian Cryer
www.cryer.co.uk/brian|||Great, thanks for your help Brian...!
Alex
-->
Brian Cryer wrote:
> <postings@.alexshirley.com> wrote in message
> news:1133285607.162678.51170@.g14g2000cwa.googlegroups.com...
> > Hi
> >
> > I'm running SQL Server 2000 on a Windows 2003 SBS server. Much to my
> > horror I notice that that the SQL data directory has permissions set
> > for:
> > Domain\Administrator (full accesss)
> > Domain\Administrators (full accesss)
> > Authenticated users (read,list, read). I guess this isn't a good idea
> > at all!
> >
> > What are the optimum permissions here (I can't seem to get a straight
> > answer). Do I set it for the SQL service to have full control only (at
> > the moment MSSQLSERVER service is logging on using
> > Domain\Administrator). Do I change this account? What about the other
> > SQL Server related services? Please also note I am also using Backup
> > Exec 9 to backup the databases.
> >
> > Any suggestions you may have will be greatly appreciated!
> >
> > Many thanks
> >
> > Alex
> On my SQL Server 2000 database running on Windows 2003 standard server, the
> permissions on the SQL data directory are just for Domain\Administrators,
> full access. The MSSQLServer service is set to use the local system account.
> If your authenticated users have access then you should be able to revoke
> that without problem.
> I don't know where Backup Exec fits into the picture - I don't use it - but
> it shouldn't be backing up the files directly so it shouldn't need any
> permissions on the folder.
> Hope this is useful.
> --
> Brian Cryer
> www.cryer.co.uk/brian
I'm running SQL Server 2000 on a Windows 2003 SBS server. Much to my
horror I notice that that the SQL data directory has permissions set
for:
Domain\Administrator (full accesss)
Domain\Administrators (full accesss)
Authenticated users (read,list, read). I guess this isn't a good idea
at all!
What are the optimum permissions here (I can't seem to get a straight
answer). Do I set it for the SQL service to have full control only (at
the moment MSSQLSERVER service is logging on using
Domain\Administrator). Do I change this account? What about the other
SQL Server related services? Please also note I am also using Backup
Exec 9 to backup the databases.
Any suggestions you may have will be greatly appreciated!
Many thanks
Alex<postings@.alexshirley.com> wrote in message
news:1133285607.162678.51170@.g14g2000cwa.googlegroups.com...
> Hi
> I'm running SQL Server 2000 on a Windows 2003 SBS server. Much to my
> horror I notice that that the SQL data directory has permissions set
> for:
> Domain\Administrator (full accesss)
> Domain\Administrators (full accesss)
> Authenticated users (read,list, read). I guess this isn't a good idea
> at all!
> What are the optimum permissions here (I can't seem to get a straight
> answer). Do I set it for the SQL service to have full control only (at
> the moment MSSQLSERVER service is logging on using
> Domain\Administrator). Do I change this account? What about the other
> SQL Server related services? Please also note I am also using Backup
> Exec 9 to backup the databases.
> Any suggestions you may have will be greatly appreciated!
> Many thanks
> Alex
On my SQL Server 2000 database running on Windows 2003 standard server, the
permissions on the SQL data directory are just for Domain\Administrators,
full access. The MSSQLServer service is set to use the local system account.
If your authenticated users have access then you should be able to revoke
that without problem.
I don't know where Backup Exec fits into the picture - I don't use it - but
it shouldn't be backing up the files directly so it shouldn't need any
permissions on the folder.
Hope this is useful.
--
Brian Cryer
www.cryer.co.uk/brian|||Great, thanks for your help Brian...!
Alex
-->
Brian Cryer wrote:
> <postings@.alexshirley.com> wrote in message
> news:1133285607.162678.51170@.g14g2000cwa.googlegroups.com...
> > Hi
> >
> > I'm running SQL Server 2000 on a Windows 2003 SBS server. Much to my
> > horror I notice that that the SQL data directory has permissions set
> > for:
> > Domain\Administrator (full accesss)
> > Domain\Administrators (full accesss)
> > Authenticated users (read,list, read). I guess this isn't a good idea
> > at all!
> >
> > What are the optimum permissions here (I can't seem to get a straight
> > answer). Do I set it for the SQL service to have full control only (at
> > the moment MSSQLSERVER service is logging on using
> > Domain\Administrator). Do I change this account? What about the other
> > SQL Server related services? Please also note I am also using Backup
> > Exec 9 to backup the databases.
> >
> > Any suggestions you may have will be greatly appreciated!
> >
> > Many thanks
> >
> > Alex
> On my SQL Server 2000 database running on Windows 2003 standard server, the
> permissions on the SQL data directory are just for Domain\Administrators,
> full access. The MSSQLServer service is set to use the local system account.
> If your authenticated users have access then you should be able to revoke
> that without problem.
> I don't know where Backup Exec fits into the picture - I don't use it - but
> it shouldn't be backing up the files directly so it shouldn't need any
> permissions on the folder.
> Hope this is useful.
> --
> Brian Cryer
> www.cryer.co.uk/brian
Dual-boot with SQL 2000
A client has a program that uses a SQL database. They already have a Windows
2003 + SQL 2000 SP3a server they had planned to use with this app, then
discovered the vendor only will not support Windows 2003 + SQL 2000 SP3a
until the end of the year.
Our thought is to install Windows 2000 + SQL 2000 as a dual-boot with the
existing Windows 2003 + SQL 2000 installation. Set the SQL database and log
folders to the same folders in both installations, and when the vendor
certifies Windows 2003, boot into 2003 and immediately resume operations
with minimal downtime.
Is this workable? Or do we need to keep the two SQL installations completely
separate and do a backup from Win2000/SQL2000 and then restore to
Win2003/SQL2000?
--
Jeff Vandervoort
JRVsystems
http://jrvsystems.comAssuming that the folder for all database files are the same and the machine name is the same, yes
it should work. Not supported, though.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Jeff Vandervoort" <jeffv @. jrvsystems dot com> wrote in message
news:%2390OgxPnDHA.3612@.TK2MSFTNGP11.phx.gbl...
> A client has a program that uses a SQL database. They already have a Windows
> 2003 + SQL 2000 SP3a server they had planned to use with this app, then
> discovered the vendor only will not support Windows 2003 + SQL 2000 SP3a
> until the end of the year.
> Our thought is to install Windows 2000 + SQL 2000 as a dual-boot with the
> existing Windows 2003 + SQL 2000 installation. Set the SQL database and log
> folders to the same folders in both installations, and when the vendor
> certifies Windows 2003, boot into 2003 and immediately resume operations
> with minimal downtime.
> Is this workable? Or do we need to keep the two SQL installations completely
> separate and do a backup from Win2000/SQL2000 and then restore to
> Win2003/SQL2000?
> --
> Jeff Vandervoort
> JRVsystems
> http://jrvsystems.com
>|||Thanks for your reply, Tibor.
--
Jeff Vandervoort
JRVsystems
http://jrvsystems.com
"Tibor Karaszi" <tibor.please_reply_to_public_forum.karaszi@.cornerstone.se>
wrote in message news:%235lyAISnDHA.2312@.TK2MSFTNGP12.phx.gbl...
> Assuming that the folder for all database files are the same and the
machine name is the same, yes
> it should work. Not supported, though.
> --
> Tibor Karaszi, SQL Server MVP
> Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
>
> "Jeff Vandervoort" <jeffv @. jrvsystems dot com> wrote in message
> news:%2390OgxPnDHA.3612@.TK2MSFTNGP11.phx.gbl...
> > A client has a program that uses a SQL database. They already have a
Windows
> > 2003 + SQL 2000 SP3a server they had planned to use with this app, then
> > discovered the vendor only will not support Windows 2003 + SQL 2000 SP3a
> > until the end of the year.
> >
> > Our thought is to install Windows 2000 + SQL 2000 as a dual-boot with
the
> > existing Windows 2003 + SQL 2000 installation. Set the SQL database and
log
> > folders to the same folders in both installations, and when the vendor
> > certifies Windows 2003, boot into 2003 and immediately resume operations
> > with minimal downtime.
> >
> > Is this workable? Or do we need to keep the two SQL installations
completely
> > separate and do a backup from Win2000/SQL2000 and then restore to
> > Win2003/SQL2000?
> >
> > --
> >
> > Jeff Vandervoort
> > JRVsystems
> > http://jrvsystems.com
> >
> >
>
2003 + SQL 2000 SP3a server they had planned to use with this app, then
discovered the vendor only will not support Windows 2003 + SQL 2000 SP3a
until the end of the year.
Our thought is to install Windows 2000 + SQL 2000 as a dual-boot with the
existing Windows 2003 + SQL 2000 installation. Set the SQL database and log
folders to the same folders in both installations, and when the vendor
certifies Windows 2003, boot into 2003 and immediately resume operations
with minimal downtime.
Is this workable? Or do we need to keep the two SQL installations completely
separate and do a backup from Win2000/SQL2000 and then restore to
Win2003/SQL2000?
--
Jeff Vandervoort
JRVsystems
http://jrvsystems.comAssuming that the folder for all database files are the same and the machine name is the same, yes
it should work. Not supported, though.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Jeff Vandervoort" <jeffv @. jrvsystems dot com> wrote in message
news:%2390OgxPnDHA.3612@.TK2MSFTNGP11.phx.gbl...
> A client has a program that uses a SQL database. They already have a Windows
> 2003 + SQL 2000 SP3a server they had planned to use with this app, then
> discovered the vendor only will not support Windows 2003 + SQL 2000 SP3a
> until the end of the year.
> Our thought is to install Windows 2000 + SQL 2000 as a dual-boot with the
> existing Windows 2003 + SQL 2000 installation. Set the SQL database and log
> folders to the same folders in both installations, and when the vendor
> certifies Windows 2003, boot into 2003 and immediately resume operations
> with minimal downtime.
> Is this workable? Or do we need to keep the two SQL installations completely
> separate and do a backup from Win2000/SQL2000 and then restore to
> Win2003/SQL2000?
> --
> Jeff Vandervoort
> JRVsystems
> http://jrvsystems.com
>|||Thanks for your reply, Tibor.
--
Jeff Vandervoort
JRVsystems
http://jrvsystems.com
"Tibor Karaszi" <tibor.please_reply_to_public_forum.karaszi@.cornerstone.se>
wrote in message news:%235lyAISnDHA.2312@.TK2MSFTNGP12.phx.gbl...
> Assuming that the folder for all database files are the same and the
machine name is the same, yes
> it should work. Not supported, though.
> --
> Tibor Karaszi, SQL Server MVP
> Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
>
> "Jeff Vandervoort" <jeffv @. jrvsystems dot com> wrote in message
> news:%2390OgxPnDHA.3612@.TK2MSFTNGP11.phx.gbl...
> > A client has a program that uses a SQL database. They already have a
Windows
> > 2003 + SQL 2000 SP3a server they had planned to use with this app, then
> > discovered the vendor only will not support Windows 2003 + SQL 2000 SP3a
> > until the end of the year.
> >
> > Our thought is to install Windows 2000 + SQL 2000 as a dual-boot with
the
> > existing Windows 2003 + SQL 2000 installation. Set the SQL database and
log
> > folders to the same folders in both installations, and when the vendor
> > certifies Windows 2003, boot into 2003 and immediately resume operations
> > with minimal downtime.
> >
> > Is this workable? Or do we need to keep the two SQL installations
completely
> > separate and do a backup from Win2000/SQL2000 and then restore to
> > Win2003/SQL2000?
> >
> > --
> >
> > Jeff Vandervoort
> > JRVsystems
> > http://jrvsystems.com
> >
> >
>
Friday, March 9, 2012
Dual Core CPUs and SQL Server 2000
I need to configure and purchase two new servers running SQL 2000 Enterprise
Edition on Windows 2003 Enterprise Edition each equipped with 2 processors.
I'm wondering if anyone has experience with or knowledge of using dual core
Intel Xeon Processors with SQL Server, and if there are definite improvements
over single core higher clocked processors. I'm trying to decide whether to
configure the servers with two 2.8Ghz Dual Core Xeon processors or two 3.4Ghz
single core processors.
Thanks.
Hi
You may want to read this
http://www.sql-server-performance.com/jc_processor.asp although not
specifically about dual core I would expect dual core to be the akin to using
more than one processor.
John
"Marks70" wrote:
> I need to configure and purchase two new servers running SQL 2000 Enterprise
> Edition on Windows 2003 Enterprise Edition each equipped with 2 processors.
> I'm wondering if anyone has experience with or knowledge of using dual core
> Intel Xeon Processors with SQL Server, and if there are definite improvements
> over single core higher clocked processors. I'm trying to decide whether to
> configure the servers with two 2.8Ghz Dual Core Xeon processors or two 3.4Ghz
> single core processors.
> Thanks.
Edition on Windows 2003 Enterprise Edition each equipped with 2 processors.
I'm wondering if anyone has experience with or knowledge of using dual core
Intel Xeon Processors with SQL Server, and if there are definite improvements
over single core higher clocked processors. I'm trying to decide whether to
configure the servers with two 2.8Ghz Dual Core Xeon processors or two 3.4Ghz
single core processors.
Thanks.
Hi
You may want to read this
http://www.sql-server-performance.com/jc_processor.asp although not
specifically about dual core I would expect dual core to be the akin to using
more than one processor.
John
"Marks70" wrote:
> I need to configure and purchase two new servers running SQL 2000 Enterprise
> Edition on Windows 2003 Enterprise Edition each equipped with 2 processors.
> I'm wondering if anyone has experience with or knowledge of using dual core
> Intel Xeon Processors with SQL Server, and if there are definite improvements
> over single core higher clocked processors. I'm trying to decide whether to
> configure the servers with two 2.8Ghz Dual Core Xeon processors or two 3.4Ghz
> single core processors.
> Thanks.
Dual Core CPUs and SQL Server 2000
I need to configure and purchase two new servers running SQL 2000 Enterprise
Edition on Windows 2003 Enterprise Edition each equipped with 2 processors.
I'm wondering if anyone has experience with or knowledge of using dual core
Intel Xeon Processors with SQL Server, and if there are definite improvements
over single core higher clocked processors. I'm trying to decide whether to
configure the servers with two 2.8Ghz Dual Core Xeon processors or two 3.4Ghz
single core processors.
Thanks.Hi
You may want to read this
http://www.sql-server-performance.com/jc_processor.asp although not
specifically about dual core I would expect dual core to be the akin to using
more than one processor.
John
"Marks70" wrote:
> I need to configure and purchase two new servers running SQL 2000 Enterprise
> Edition on Windows 2003 Enterprise Edition each equipped with 2 processors.
> I'm wondering if anyone has experience with or knowledge of using dual core
> Intel Xeon Processors with SQL Server, and if there are definite improvements
> over single core higher clocked processors. I'm trying to decide whether to
> configure the servers with two 2.8Ghz Dual Core Xeon processors or two 3.4Ghz
> single core processors.
> Thanks.
Edition on Windows 2003 Enterprise Edition each equipped with 2 processors.
I'm wondering if anyone has experience with or knowledge of using dual core
Intel Xeon Processors with SQL Server, and if there are definite improvements
over single core higher clocked processors. I'm trying to decide whether to
configure the servers with two 2.8Ghz Dual Core Xeon processors or two 3.4Ghz
single core processors.
Thanks.Hi
You may want to read this
http://www.sql-server-performance.com/jc_processor.asp although not
specifically about dual core I would expect dual core to be the akin to using
more than one processor.
John
"Marks70" wrote:
> I need to configure and purchase two new servers running SQL 2000 Enterprise
> Edition on Windows 2003 Enterprise Edition each equipped with 2 processors.
> I'm wondering if anyone has experience with or knowledge of using dual core
> Intel Xeon Processors with SQL Server, and if there are definite improvements
> over single core higher clocked processors. I'm trying to decide whether to
> configure the servers with two 2.8Ghz Dual Core Xeon processors or two 3.4Ghz
> single core processors.
> Thanks.
Dual Core CPUs and SQL Server 2000
I need to configure and purchase two new servers running SQL 2000 Enterprise
Edition on Windows 2003 Enterprise Edition each equipped with 2 processors.
I'm wondering if anyone has experience with or knowledge of using dual core
Intel Xeon Processors with SQL Server, and if there are definite improvement
s
over single core higher clocked processors. I'm trying to decide whether to
configure the servers with two 2.8Ghz Dual Core Xeon processors or two 3.4Gh
z
single core processors.
Thanks.Hi
You may want to read this
http://www.sql-server-performance.com/jc_processor.asp although not
specifically about dual core I would expect dual core to be the akin to usin
g
more than one processor.
John
"Marks70" wrote:
> I need to configure and purchase two new servers running SQL 2000 Enterpri
se
> Edition on Windows 2003 Enterprise Edition each equipped with 2 processors
.
> I'm wondering if anyone has experience with or knowledge of using dual cor
e
> Intel Xeon Processors with SQL Server, and if there are definite improveme
nts
> over single core higher clocked processors. I'm trying to decide whether t
o
> configure the servers with two 2.8Ghz Dual Core Xeon processors or two 3.4
Ghz
> single core processors.
> Thanks.
Edition on Windows 2003 Enterprise Edition each equipped with 2 processors.
I'm wondering if anyone has experience with or knowledge of using dual core
Intel Xeon Processors with SQL Server, and if there are definite improvement
s
over single core higher clocked processors. I'm trying to decide whether to
configure the servers with two 2.8Ghz Dual Core Xeon processors or two 3.4Gh
z
single core processors.
Thanks.Hi
You may want to read this
http://www.sql-server-performance.com/jc_processor.asp although not
specifically about dual core I would expect dual core to be the akin to usin
g
more than one processor.
John
"Marks70" wrote:
> I need to configure and purchase two new servers running SQL 2000 Enterpri
se
> Edition on Windows 2003 Enterprise Edition each equipped with 2 processors
.
> I'm wondering if anyone has experience with or knowledge of using dual cor
e
> Intel Xeon Processors with SQL Server, and if there are definite improveme
nts
> over single core higher clocked processors. I'm trying to decide whether t
o
> configure the servers with two 2.8Ghz Dual Core Xeon processors or two 3.4
Ghz
> single core processors.
> Thanks.
Wednesday, March 7, 2012
DTSWizard Doesnt show new ODBC data source?
I've installed SQL Express SP1 on a Windows 2003 server and I'm trying to get a new MySQL datasource to be recognized in the DTSWizard. A MySQL database needs to be moved over to a MS SQL server due to software requirements (which weren't looked at before the site was created). I've installed the ODBC Connector/MySQL software and created the System DSN (named "MySQL DB Import) in the Administrative Tools/Data Sources (ODBC) tool. When I start up the DTS wizard for SQL Express however, I do not get my new data source in the selection options for data sources.
I am following the instructions on this page:
http://www.microsoft.com/technet/prodtechnol/sql/2000/deploy/mysql.mspx#ERJAE
What am I missing?
It is not you missing anything the DTS you got is very limited almost a copy wizard so it is not intelligent enough to move your MySQL database, so try the link below and download the eval it is good for 6 months. Remember it is the Enterprise edition so choose all components if there is a separate folder for tools install it. So you can use SQL Server integration services. Post again if you still have question. And please try to buy the no deployment developer edition it is less than $35.00. Hope this helps.
http://www.microsoft.com/downloads/details.aspx?familyid=6931fa7f-c094-49a2-a050-2d07993566ec&displaylang=en
|||It may be that the full SQL Integration Services are dumbed down in the evaluation too. The DTS tool in the evaluation edition wouldn't allow any new data sources either. I ended up deleting the Program Files SQL directories, the registry entries (for DTS, SQL Server, anything else that was installed with it), etc. but still no go. I'm a unix admin so this is rarely touched territory for me. What I ended up doing was exporting the database (luckily it's not yet in production) via third party tool (Navicat) to individual table MS Access databases, and then importing those via the DTS tool into MS SQL Server. I just have to wait now for the programmer to convert the site.
Thanks anyways.
DTSRun Utility Wont
I have been successful at setting up three or four DTS packages to run
using the DTSrun command line utility and the Windows scheduler until
now. The latest package gives me the following error no matter what I
try.
using the DTSrun command line utility and the Windows scheduler until
now. The latest package gives me the following error no matter what I
try.
Error: -2147217355 (80041035); Provider Error: 0 (0)
Error string: General error -2147217355 (80041035).
Error source: Microsoft Data Transformation Services (DTS) Package
Help file: sqldts80.hlp
Help context: 705
I googled the error but got only two hits, only one of which actually
discussed the error. That one talked about the security and ID context
of the system agent but I can't even run the package from the command
line, never mind using the Windows chron. The DTS command line I'm
using looks like this:
DTSRun /S MyServer\Instance /R DBName /N MyDTSPacakgeName /E
Variations included /U MyUserName /P MyPassWord and a couple others.
Next step would have been to use /!Y and /!C to create an encoded batch
file to use for the Windows scheduler.
Any help would be most appreciated.
RandyCan you run the DTS package from the designer (hopefully on the same
machine)? Just seeing if the error might be internal to the package.
Stu|||Runs like a champ from designer. Won't run scheduled from Enterprise
Manager, whether on a client machine or directly on the server and
won't run from a command line.|||And you can run other packages this same way? That would certainly
rule out any permissions problems, but I'm drawing a blank as to what's
going on.
Stu|||Exactly. I have one other package that runs every night but it's been
running for three or four months now. I have another package that I ran
one time last weekend using Windows scheduler again with no problem.
This third package needs to run every day from now on but I can't get
it to run from a command line which is the first step I take toward
building a batch file for scheduler.
And there are VERY few references to the error using Google, which
surprised me.
Sunday, February 26, 2012
DTSExec and Logging to Windows Event Log
I am trying to use either DTExec or DTExecUI to run a package while logging to the Windows Event log. This purports to be supported based on books online.
I have tried passing the CLSID and the ProgId on the command line and always get a message about the logger parameter being invalid.
I am using a command line like this:
dtexec /FILE "C:\Etl.dtsx" /MAXCONCURRENT " -1 " /CHECKPOINTING OFF /REPORTING EW /LOGGER "DTS.LogProviderEventLog.1"; /SET "\Package.DestinationDatabase";"Test15-1Warehouse" /SET "\Package.SourceDatabase";ATEST15D1
Message I get is:
Argument "DTS.LogProviderEventLog.1;" for option "logger" is not valid.
Same message with the CLSID.
Help!
Normally the Logger switch expects a 2nd configstring argument within the quotes. The Event Log doesn't have anything to configure, but it seems to want the semicolon that would normally precede the 2nd argument.Instead of /LOGGER "DTS.LogProviderEventLog.1",
please try /LOGGER "DTS.LogProviderEventLog.1;".|||Actually the semicolon is already specified (just outside the quotes instead of inside which should work (if not it is a bug). The problem is that the config string is not optional so the argument is missing the config string as far as DTExec is concerned. Try putting any character there and it should work as the event log provider ignores the config string.
/LOGGER "DTS.LogProviderEventLog.1;x".
thanks,|||Thanks.
Kind of stupid but that was it.
Friday, February 17, 2012
DTS w/ C#
I am executing a DTS package with a Console app and everything works fine.
I am now constructing a "Windows Application" to execute the package. This
fails (using the identical code). I can't figure out how to display the
package events using a WinForm (everything I find shows me how to use it
with a console app which is working just fine).
So ... how do I display errors in a Form?
... why do you think that it wont work in a form?
Because WinForms require the UI to be updated from the main thread, you need
to use BeginInvoke, see
http://samples.gotdotnet.com/quickst...rshalling.aspx
GertD@.SQLDev.Net
Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.
Copyright SQLDev.Net 1991-2005 All rights reserved.
"seth via droptable.com" <forum@.nospam.droptable.com> wrote in message
news:a77def4c0b414c65b4570e1e656aa5f0@.droptable.co m...
>I am executing a DTS package with a Console app and everything works fine.
> I am now constructing a "Windows Application" to execute the package.
> This
> fails (using the identical code). I can't figure out how to display the
> package events using a WinForm (everything I find shows me how to use it
> with a console app which is working just fine).
> So ... how do I display errors in a Form?
> ... why do you think that it wont work in a form?
I am now constructing a "Windows Application" to execute the package. This
fails (using the identical code). I can't figure out how to display the
package events using a WinForm (everything I find shows me how to use it
with a console app which is working just fine).
So ... how do I display errors in a Form?
... why do you think that it wont work in a form?
Because WinForms require the UI to be updated from the main thread, you need
to use BeginInvoke, see
http://samples.gotdotnet.com/quickst...rshalling.aspx
GertD@.SQLDev.Net
Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.
Copyright SQLDev.Net 1991-2005 All rights reserved.
"seth via droptable.com" <forum@.nospam.droptable.com> wrote in message
news:a77def4c0b414c65b4570e1e656aa5f0@.droptable.co m...
>I am executing a DTS package with a Console app and everything works fine.
> I am now constructing a "Windows Application" to execute the package.
> This
> fails (using the identical code). I can't figure out how to display the
> package events using a WinForm (everything I find shows me how to use it
> with a console app which is working just fine).
> So ... how do I display errors in a Form?
> ... why do you think that it wont work in a form?
Subscribe to:
Posts (Atom)