MSDE Failed Install: instance

Showing posts with label instance. Show all posts

Friday, March 30, 2012

MSDE Tookit thinks MSDE is not installed when it is.

I have multiple applications that will use the same named instance of MSDE. When I try to setup my second application using the MSDE Deployment addin it thinks that MSDE needs to be installed again. According to the flowchart it should bypass this and
just install my appliation. Any suggestions as to why my setup insists in needs to install another instance? My instance name is the same for all applications.
Thanks,
Bill
Bill in one of the previous messages someone from Microsoft mentioned that it is a known bug in the beta version of the toolkit. Hopefully it will be fixed.
goodluck
dev
|||Thanks for the info. Does anyone know when the full release will be out?
sql

MSDE startup problem

Hi
MSDE installed on one of our clients PC is having problems with startup.
What could cause such problems (error log below - computer, instance
and user database names are changed to protect user information)?
Client's OS is Windows ME.
Hilarion
2004-10-20 15:27:11.88 server Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Desktop Engine on Windows 4.90 (Build 3000: )
2004-10-20 15:27:11.88 server Copyright (C) 1988-2002 Microsoft Corporation.
2004-10-20 15:27:11.88 server All rights reserved.
2004-10-20 15:27:11.88 server Server Process ID is -1747957.
2004-10-20 15:27:11.88 server Logging SQL Server messages in file 'C:\PROGRAM FILES\Microsoft SQL
Server\MSSQL$INSTANCE_NAME\LOG\ERRORLOG'.
2004-10-20 15:27:11.90 server SQL Server is starting at priority class 'normal'(1 CPU detected).
2004-10-20 15:27:11.95 server SQL Server configured for thread mode processing.
2004-10-20 15:27:11.95 server Using dynamic lock allocation. [500] Lock Blocks, [1000] Lock Owner Blocks.
2004-10-20 15:27:11.97 spid3 Starting up database 'master'.
2004-10-20 15:27:12.42 spid5 Starting up database 'model'.
2004-10-20 15:27:12.47 server Using 'dbghelp.dll' version '4.0.5'
*Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
2004-10-20 15:27:12.54 server SqlDumpExceptionHandler: Process -2094925 generated fatal exception c0000005
EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
* *******************************************************************************
*
* BEGIN STACK DUMP:
* 10/20/04 15:27:12 spid 0
*
* Exception Address = 42CF2293 (ConnectionListen + 0000107E Line 0+00000000)
* Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
* Access Violation occurred reading address FFFFFFFF
2004-10-20 15:27:12.54 spid3 Server name is 'COMPUTER_NAME\INSTANCE_NAME'.
* 0051739E Module(SQLSERVR+0011739E)
2004-10-20 15:27:12.62 spid8 Starting up database 'msdb* BFF79391 Module(KERNEL32+00019391) (HeapCreate+0000032E)
* BFF76E3A Module(KERNEL32+00016E3A) (VirtualQueryEx+00001774)
* BFF76D37 Module(KERNEL32+00016D37) (VirtualQueryEx+00001671)
2004-10-20 15:27:12.65 spid9 Starting up database 'MY_DATABASE'.
* 0070042B Module(SQLSERVR+0030042B) (GetIMallocForMsxml+00096397)
* ----
*Dump thread - spid = 1, PSS = 0x1a5ea098, EC = 0x1a5ea3c0
*Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
* *******************************************************************************
*
* BEGIN STACK DUMP:
* 10/20/04 15:27:12 spid 1
*
* StackDump (all)
*
*
*
* Edi: C1A822E0:
* Esi: 00000001:
* Eax: 002A005C:
* Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161512
* Ecx: 018AFC08: 018AFED0 00982517 00000000 018AFC94 00517E27 000003E8
* Edx: 00000100:
* Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
* Ebp: 018AFB98: 018AFBD0 410721D6 00E013F0 1A5EA564 018AFBD0 000003E8
* SegCs: 0000019F:
* EFlags: 00000246:
* Esp: 018AFB40: FFFFFFFF BFF831BC C1A822E0 FFFFFFFF 00000001 BFF8318C
* SegSs: 000001A7:
* *******************************************************************************
* ----
* Short Stack Dump
* BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
* 410721D6 Module(UMS+000021D6) (UmsScheduler::Suspend+00000066)
* 00879042 Module(SQLSERVR+00479042) (GetOSErrString+0000230F)
* 00517E27 Module(SQLSERVR+00117E27)
* 00517DB5 Module(SQLSERVR+00117DB5)
* 41075002 Module(UMS+00005002) (UmsThreadScheduler::Context+00000532)
* 41074698 Module(UMS+00004698) (UmsThreadScheduler::~UmsThreadScheduler+00000198)
* 542868FF Module(UNKNOWN+00000000)
* ----
*Dump thread - spid = 2, PSS = 0x1a62a098, EC = 0x1a62a3c0
*Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
* *******************************************************************************
*
* BEGIN STACK DUMP:
* 10/20/04 15:27:13 spid 2
*
* StackDump (all)
*
*
*
* Edi: C1A827E0:
* Esi: 00000001:
* Eax: 002A005C:
* Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161516
* Ecx: 019EFA4C: 019EFECC 00982517 00000000 019EFA74 004017CB FFFFFFFF
* Edx: 00000100:
* Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
* Ebp: 019EF9DC: 019EFA14 410721D6 00E01280 1A62A564 019EFA14 000007D0
* SegCs: 0000019F:
* EFlags: 00000246:
* Esp: 019EF984: FFFFFFFF BFF831BC C1A827E0 FFFFFFFF 00000001 BFF8318C
* SegSs: 000001A7:
* *******************************************************************************
* ----
* Short Stack Dump
* BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
* 410721D6 Module(UMS+000021D6) (UmsScheduler::Suspend+00000066)
* 00879042 Module(SQLSERVR+00479042) (GetOSErrString+0000230F)
* 004017CB Module(SQLSERVR+000017CB)
* 00401662 Module(SQLSERVR+00001662)
* 00516B22 Module(SQLSERVR+00116B22)
* 41075002 Module(UMS+00005002) (UmsThreadScheduler::Context+00000532)
* 41074698 Module(UMS+00004698) (UmsThreadScheduler::~UmsThreadScheduler+00000198)
* 542868FF Module(UNKNOWN+00000000)
* ----
*Dump thread - spid = 3, PSS = 0x1a628098, EC = 0x1a6283c0
*Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
* *******************************************************************************
*
* BEGIN STACK DUMP:
* 10/20/04 15:27:13 spid 3
*
* StackDump (all)
*
*
*
* Edi: C1A82A60:
* Esi: 00000001:
* Eax: 002A005C:
* Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161512
* Ecx: 01A8F9F4: 01A8FEC8 0097E819 00000002 01A8FED4 005196A1 00000002
* Edx: 00000100:
* Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
* Ebp: 01A8F530: 01A8F568 410721D6 00E01110 01A8F59C 01A8F568 FFFFFFFF
* SegCs: 0000019F:
* EFlags: 00000246:
* Esp: 01A8F4D8: FFFFFFFF BFF831BC C1A82A60 FFFFFFFF 00000001 BFF8318C
* SegSs: 000001A7:
* *******************************************************************************
* ----
* Short Stack Dump
* BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
* 410721D6 Module(UMS+000021D6) (UmsScheduler::Suspend+00000066)
* 41072DD9 Module(UMS+00002DD9) (UmsEvent::WaitMultiple+00000019)
* 005196A1 Module(SQLSERVR+001196A1)
* 00518066 Module(SQLSERVR+00118066)
* 41074698 Module(UMS+00004698) (UmsThreadScheduler::~UmsThreadScheduler+00000198)
* 542868FF Module(UNKNOWN+00000000)
* ----
*Dump thread - spid = 4, PSS = 0x1a622098, EC = 0x1a6223c0
*Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
* *******************************************************************************
*
* BEGIN STACK DUMP:
* 10/20/04 15:27:13 spid 4
*
* StackDump (all)
*
*
*
* Edi: C1A82040:
* Esi: 00000001:
* Eax: 002A005C:
* Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161516
* Ecx: 0180FDC8: 0180FE94 00982517 00000000 0180FDF0 004017CB 00001388
* Edx: 00000100:
* Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
* Ebp: 0180FD58: 0180FD90 410721D6 00E02F90 1A622564 0180FD90 000007D0
* SegCs: 0000019F:
* EFlags: 00000246:
* Esp: 0180FD00: FFFFFFFF BFF831BC C1A82040 FFFFFFFF 00000001 BFF8318C
* SegSs: 000001A7:
* *******************************************************************************
* ----
* Short Stack Dump
* BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
* 410721D6 Module(UMS+000021D6) (UmsScheduler::Suspend+00000066)
* 00879042 Module(SQLSERVR+00479042) (GetOSErrString+0000230F)
* 004017CB Module(SQLSERVR+000017CB)
* 00401662 Module(SQLSERVR+00001662)
* 00516F4E Module(SQLSERVR+00116F4E)
* 00516CC4 Module(SQLSERVR+00116CC4)
* 41075002 Module(UMS+00005002) (UmsThreadScheduler::Context+00000532)
* 41074698 Module(UMS+00004698) (UmsThreadScheduler::~UmsThreadScheduler+00000198)
* 542868FF Module(UNKNOWN+00000000)
* ----
*Dump thread - spid = 5, PSS = 0x1a630098, EC = 0x1a6303c0
*Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
* *******************************************************************************
*
2004-10-20 15:27:13.48 spid5 Clearing tempdb database.
kDump (all)
*
*
*
* Edi: C1A83E80:
* Esi: 00000001:
* Eax: 002A005C:
* Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161512
* Ecx: 01C9F484: 011420B4 00200000 00100000 01C9F4CC 00483C40 00000001
* Edx: 00000100:
* Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
* Ebp: 01C9F3D4: 01C9F418 0040C9C9 000000D0 00012000 00000000 1A6B4000
* SegCs: 0000019F:
* EFlags: 00000246:
* Esp: 01C9F35C: 011420B4 00200002 00200000 01C9F374 00415052 00000004
* SegSs: 000001A7:
* *******************************************************************************
* ----
* Short Stack Dump
* BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
* 0040C9C9 Module(SQLSERVR+0000C9C9)
* 00485EFA Module(SQLSERVR+00085EFA)
* 00485FF5 Module(SQLSERVR+00085FF5)
* 00483C40 Module(SQLSERVR+00083C40)
* 01C9FBA2 Module(UNKNOWN+00000000)
* ----
*Dump thread - spid = 6, PSS = 0x1a634098, EC = 0x1a6343c0
*Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
* *******************************************************************************
*
* BEGIN STACK DUMP:
* 10/20/04 15:27:13 spid 6
*
* StackDump (all)
*
*
*
* Edi: C1A82CE0:
* Esi: 00000001:
* Eax: 002A005C:
* Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161512
* Ecx: 01B2FC50: 01B2FED0 00982517 00000000 01B2FC78 004017CB FFFFFFFF
* Edx: 00000100:
* Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
* Ebp: 01B2FBE0: 01B2FC18 410721D6 00E02C90 1A634564 01B2FC18 000007D0
* SegCs: 0000019F:
* EFlags: 00000246:
* Esp: 01B2FB88: FFFFFFFF BFF831BC C1A82CE0 FFFFFFFF 00000001 BFF8318C
* SegSs: 000001A7:
* *******************************************************************************
* ----
* Short Stack Dump
* BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
* 410721D6 Module(UMS+000021D6) (UmsScheduler::Suspend+00000066)
* 00879042 Module(SQLSERVR+00479042) (GetOSErrString+0000230F)
* 004017CB Module(SQLSERVR+000017CB)
* 00401662 Module(SQLSERVR+00001662)
* 00517249 Module(SQLSERVR+00117249)
* 41075002 Module(UMS+00005002) (UmsThreadScheduler::Context+00000532)
* 41074698 Module(UMS+00004698) (UmsThreadScheduler::~UmsThreadScheduler+00000198)
* 542868FF Module(UNKNOWN+00000000)
* ----
*Dump thread - spid = 7, PSS = 0x1a684098, EC = 0x1a6843c0
*Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
* *******************************************************************************
*
* BEGIN STACK DUMP:
* 10/20/04 15:27:13 spid 7
*
* StackDump (all)
*
*
*
* Edi: C1A82560:
* Esi: 00000001:
* Eax: 002A005C:
* Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161512
* Ecx: 0194FC3C: 0194FED0 00982517 00000000 0194FC64 004017CB FFFFFFFF
* Edx: 00000100:
* Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
* Ebp: 0194FBCC: 0194FC04 410721D6 00E02E20 1A684564 0194FC04 000007D0
* SegCs: 0000019F:
* EFlags: 00000246:
* Esp: 0194FB74: FFFFFFFF BFF831BC C1A82560 FFFFFFFF 00000001 BFF8318C
* SegSs: 000001A7:
* *******************************************************************************
* ----
* Short Stack Dump
* BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
* 410721D6 Module(UMS+000021D6) (UmsScheduler::Suspend+00000066)
* 00879042 Module(SQLSERVR+00479042) (GetOSErrString+0000230F)
* 004017CB Module(SQLSERVR+000017CB)
* 00401662 Module(SQLSERVR+00001662)
* 0051876D Module(SQLSERVR+0011876D)
* 41075002 Module(UMS+00005002) (UmsThreadScheduler::Context+00000532)
* 41074698 Module(UMS+00004698) (UmsThreadScheduler::~UmsThreadScheduler+00000198)
* 542868FF Module(UNKNOWN+00000000)
* ----
*Dump thread - spid = 8, PSS = 0x1a6b8098, EC = 0x1a6b83c0
*Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
* *******************************************************************************
*
* BEGIN STACK DUMP:
* 10/20/04 15:27:13 spid 8
*
* StackDump (all)
*
*
*
* Edi: C1A84670:
* Esi: 00000001:
* Eax: 002A005C:
* Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161512
* Ecx: 0225E550: 0225E64C 0097E7BA FFFFFFFF 0225E58C 0040330A 1A6B2030
* Edx: 00000100:
* Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
* Ebp: 0225E4D4: 0225E504 00440F0C 1A6F2000 00002000 0009C000 00000000
* SegCs: 0000019F:
* EFlags: 00000246:
* Esp: 0225E454: FFFFFFFF BFF831BC C1A84670 FFFFFFFF 00000001 BFF8318C
* SegSs: 000001A7:
* *******************************************************************************
* ----
* Short Stack Dump
* BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
* 00440F0C Module(SQLSERVR+00040F0C)
* 00441154 Module(SQLSERVR+00041154)
* 0040330A Module(SQLSERVR+0000330A)
* 00403E2F Module(SQLSERVR+00003E2F)
* 00406528 Module(SQLSERVR+00006528)
* 004061CB Module(SQLSERVR+000061CB)
* 00405DF8 Module(SQLSERVR+00005DF8)
* 004F7294 Module(SQLSERVR+000F7294)
* 004050F7 Module(SQLSERVR+000050F7)
* 00409E39 Module(SQLSERVR+00009E39)
* 00409C49 Module(SQLSERVR+00009C49)
* 00515096 Module(SQLSERVR+00115096)
* 00514FB7 Module(SQLSERVR+00114FB7)
* 0050C0EB Module(SQLSERVR+0010C0EB)
* 005100FF Module(SQLSERVR+001100FF)
* 0050F152 Module(SQLSERVR+0010F152)
* 00519C2D Module(SQLSERVR+00119C2D)
* 41075002 Module(UMS+00005002) (UmsThreadScheduler::Context+00000532)
* 41074698 Module(UMS+00004698) (UmsThreadScheduler::~UmsThreadScheduler+00000198)
* 542868FF Module(UNKNOWN+00000000)
* ----
*Dump thread - spid = 9, PSS = 0x1a6b0098, EC = 0x1a6b03c0
*Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
* *******************************************************************************
*
* BEGIN STACK DUMP:
* 10/20/04 15:27:13 spid 9
*
* StackDump (all)
*
*
*
* Edi: C1A848E0:
* Esi: 00000001:
* Eax: 002A005C:
* Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161512
* Ecx: 022FF05C: 022FF654 00980D9F 00000000 022FF660 0050FFC8 00000002
* Edx: 00000100:
* Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
* Ebp: 022FC784: 022FCBBC 00571383 022FE000 00001000 0037C000 00000000
* SegCs: 0000019F:
* EFlags: 00000246:
* Esp: 022FC704: FFFFFFFF BFF831BC C1A848E0 FFFFFFFF 00000001 BFF8318C
* SegSs: 000001A7:
* *******************************************************************************
* ----
* Short Stack Dump
* BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
* 00571383 Module(SQLSERVR+00171383) (SQLExit+0004B903)
* 00571315 Module(SQLSERVR+00171315) (SQLExit+0004B895)
* 00571741 Module(SQLSERVR+00171741) (SQLExit+0004BCC1)
* 00511A3D Module(SQLSERVR+00111A3D)
* 0050FFC8 Module(SQLSERVR+0010FFC8)
* 0050F152 Module(SQLSERVR+0010F152)
* 00519C2D Module(SQLSERVR+00119C2D)
* 41075002 Module(UMS+00005002) (UmsThreadScheduler::Context+00000532)
* 41074698 Module(UMS+00004698) (UmsThreadScheduler::~UmsThreadScheduler+00000198)
* 542868FF Module(UNKNOWN+00000000)
* ----
2004-10-20 15:27:13.69 server SQL Server is aborting. Fatal exception c0000005 caught.Seems like SQL Server craps out when trying to recover the model database. You can search the Net
for 3607, 3608 or 3609 and see which of these makes SQL server not recover model, see if you can get
SQL server started to see if you can restore a backup of your model database. If that doesn't help,
I suggest you open a case with MS Support...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Hilarion" <hilarion@.noemail.nospam> wrote in message news:e6N5rMrtEHA.3088@.tk2msftngp13.phx.gbl...
> Hi
> MSDE installed on one of our clients PC is having problems with startup.
> What could cause such problems (error log below - computer, instance
> and user database names are changed to protect user information)?
> Client's OS is Windows ME.
> Hilarion
>
> 2004-10-20 15:27:11.88 server Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
> Dec 17 2002 14:22:05
> Copyright (c) 1988-2003 Microsoft Corporation
> Desktop Engine on Windows 4.90 (Build 3000: )
> 2004-10-20 15:27:11.88 server Copyright (C) 1988-2002 Microsoft Corporation.
> 2004-10-20 15:27:11.88 server All rights reserved.
> 2004-10-20 15:27:11.88 server Server Process ID is -1747957.
> 2004-10-20 15:27:11.88 server Logging SQL Server messages in file 'C:\PROGRAM FILES\Microsoft
> SQL Server\MSSQL$INSTANCE_NAME\LOG\ERRORLOG'.
> 2004-10-20 15:27:11.90 server SQL Server is starting at priority class 'normal'(1 CPU
> detected).
> 2004-10-20 15:27:11.95 server SQL Server configured for thread mode processing.
> 2004-10-20 15:27:11.95 server Using dynamic lock allocation. [500] Lock Blocks, [1000] Lock
> Owner Blocks.
> 2004-10-20 15:27:11.97 spid3 Starting up database 'master'.
> 2004-10-20 15:27:12.42 spid5 Starting up database 'model'.
> 2004-10-20 15:27:12.47 server Using 'dbghelp.dll' version '4.0.5'
> *Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL
> Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
> 2004-10-20 15:27:12.54 server SqlDumpExceptionHandler: Process -2094925 generated fatal
> exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
> * *******************************************************************************
> *
> * BEGIN STACK DUMP:
> * 10/20/04 15:27:12 spid 0
> *
> * Exception Address = 42CF2293 (ConnectionListen + 0000107E Line 0+00000000)
> * Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
> * Access Violation occurred reading address FFFFFFFF
> 2004-10-20 15:27:12.54 spid3 Server name is 'COMPUTER_NAME\INSTANCE_NAME'.
> * 0051739E Module(SQLSERVR+0011739E)
> 2004-10-20 15:27:12.62 spid8 Starting up database 'msdb* BFF79391 Module(KERNEL32+00019391)
> (HeapCreate+0000032E)
> * BFF76E3A Module(KERNEL32+00016E3A) (VirtualQueryEx+00001774)
> * BFF76D37 Module(KERNEL32+00016D37) (VirtualQueryEx+00001671)
> 2004-10-20 15:27:12.65 spid9 Starting up database 'MY_DATABASE'.
> * 0070042B Module(SQLSERVR+0030042B) (GetIMallocForMsxml+00096397)
> * ----
> *Dump thread - spid = 1, PSS = 0x1a5ea098, EC = 0x1a5ea3c0
> *Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL
> Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
> * *******************************************************************************
> *
> * BEGIN STACK DUMP:
> * 10/20/04 15:27:12 spid 1
> *
> * StackDump (all)
> *
> *
> *
> * Edi: C1A822E0:
> * Esi: 00000001:
> * Eax: 002A005C:
> * Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161512
> * Ecx: 018AFC08: 018AFED0 00982517 00000000 018AFC94 00517E27 000003E8
> * Edx: 00000100:
> * Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
> * Ebp: 018AFB98: 018AFBD0 410721D6 00E013F0 1A5EA564 018AFBD0 000003E8
> * SegCs: 0000019F:
> * EFlags: 00000246:
> * Esp: 018AFB40: FFFFFFFF BFF831BC C1A822E0 FFFFFFFF 00000001 BFF8318C
> * SegSs: 000001A7:
> * *******************************************************************************
> * ----
> * Short Stack Dump
> * BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
> * 410721D6 Module(UMS+000021D6) (UmsScheduler::Suspend+00000066)
> * 00879042 Module(SQLSERVR+00479042) (GetOSErrString+0000230F)
> * 00517E27 Module(SQLSERVR+00117E27)
> * 00517DB5 Module(SQLSERVR+00117DB5)
> * 41075002 Module(UMS+00005002) (UmsThreadScheduler::Context+00000532)
> * 41074698 Module(UMS+00004698) (UmsThreadScheduler::~UmsThreadScheduler+00000198)
> * 542868FF Module(UNKNOWN+00000000)
> * ----
> *Dump thread - spid = 2, PSS = 0x1a62a098, EC = 0x1a62a3c0
> *Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL
> Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
> * *******************************************************************************
> *
> * BEGIN STACK DUMP:
> * 10/20/04 15:27:13 spid 2
> *
> * StackDump (all)
> *
> *
> *
> * Edi: C1A827E0:
> * Esi: 00000001:
> * Eax: 002A005C:
> * Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161516
> * Ecx: 019EFA4C: 019EFECC 00982517 00000000 019EFA74 004017CB FFFFFFFF
> * Edx: 00000100:
> * Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
> * Ebp: 019EF9DC: 019EFA14 410721D6 00E01280 1A62A564 019EFA14 000007D0
> * SegCs: 0000019F:
> * EFlags: 00000246:
> * Esp: 019EF984: FFFFFFFF BFF831BC C1A827E0 FFFFFFFF 00000001 BFF8318C
> * SegSs: 000001A7:
> * *******************************************************************************
> * ----
> * Short Stack Dump
> * BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
> * 410721D6 Module(UMS+000021D6) (UmsScheduler::Suspend+00000066)
> * 00879042 Module(SQLSERVR+00479042) (GetOSErrString+0000230F)
> * 004017CB Module(SQLSERVR+000017CB)
> * 00401662 Module(SQLSERVR+00001662)
> * 00516B22 Module(SQLSERVR+00116B22)
> * 41075002 Module(UMS+00005002) (UmsThreadScheduler::Context+00000532)
> * 41074698 Module(UMS+00004698) (UmsThreadScheduler::~UmsThreadScheduler+00000198)
> * 542868FF Module(UNKNOWN+00000000)
> * ----
> *Dump thread - spid = 3, PSS = 0x1a628098, EC = 0x1a6283c0
> *Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL
> Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
> * *******************************************************************************
> *
> * BEGIN STACK DUMP:
> * 10/20/04 15:27:13 spid 3
> *
> * StackDump (all)
> *
> *
> *
> * Edi: C1A82A60:
> * Esi: 00000001:
> * Eax: 002A005C:
> * Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161512
> * Ecx: 01A8F9F4: 01A8FEC8 0097E819 00000002 01A8FED4 005196A1 00000002
> * Edx: 00000100:
> * Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
> * Ebp: 01A8F530: 01A8F568 410721D6 00E01110 01A8F59C 01A8F568 FFFFFFFF
> * SegCs: 0000019F:
> * EFlags: 00000246:
> * Esp: 01A8F4D8: FFFFFFFF BFF831BC C1A82A60 FFFFFFFF 00000001 BFF8318C
> * SegSs: 000001A7:
> * *******************************************************************************
> * ----
> * Short Stack Dump
> * BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
> * 410721D6 Module(UMS+000021D6) (UmsScheduler::Suspend+00000066)
> * 41072DD9 Module(UMS+00002DD9) (UmsEvent::WaitMultiple+00000019)
> * 005196A1 Module(SQLSERVR+001196A1)
> * 00518066 Module(SQLSERVR+00118066)
> * 41074698 Module(UMS+00004698) (UmsThreadScheduler::~UmsThreadScheduler+00000198)
> * 542868FF Module(UNKNOWN+00000000)
> * ----
> *Dump thread - spid = 4, PSS = 0x1a622098, EC = 0x1a6223c0
> *Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL
> Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
> * *******************************************************************************
> *
> * BEGIN STACK DUMP:
> * 10/20/04 15:27:13 spid 4
> *
> * StackDump (all)
> *
> *
> *
> * Edi: C1A82040:
> * Esi: 00000001:
> * Eax: 002A005C:
> * Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161516
> * Ecx: 0180FDC8: 0180FE94 00982517 00000000 0180FDF0 004017CB 00001388
> * Edx: 00000100:
> * Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
> * Ebp: 0180FD58: 0180FD90 410721D6 00E02F90 1A622564 0180FD90 000007D0
> * SegCs: 0000019F:
> * EFlags: 00000246:
> * Esp: 0180FD00: FFFFFFFF BFF831BC C1A82040 FFFFFFFF 00000001 BFF8318C
> * SegSs: 000001A7:
> * *******************************************************************************
> * ----
> * Short Stack Dump
> * BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
> * 410721D6 Module(UMS+000021D6) (UmsScheduler::Suspend+00000066)
> * 00879042 Module(SQLSERVR+00479042) (GetOSErrString+0000230F)
> * 004017CB Module(SQLSERVR+000017CB)
> * 00401662 Module(SQLSERVR+00001662)
> * 00516F4E Module(SQLSERVR+00116F4E)
> * 00516CC4 Module(SQLSERVR+00116CC4)
> * 41075002 Module(UMS+00005002) (UmsThreadScheduler::Context+00000532)
> * 41074698 Module(UMS+00004698) (UmsThreadScheduler::~UmsThreadScheduler+00000198)
> * 542868FF Module(UNKNOWN+00000000)
> * ----
> *Dump thread - spid = 5, PSS = 0x1a630098, EC = 0x1a6303c0
> *Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL
> Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
> * *******************************************************************************
> *
> 2004-10-20 15:27:13.48 spid5 Clearing tempdb database.
> kDump (all)
> *
> *
> *
> * Edi: C1A83E80:
> * Esi: 00000001:
> * Eax: 002A005C:
> * Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161512
> * Ecx: 01C9F484: 011420B4 00200000 00100000 01C9F4CC 00483C40 00000001
> * Edx: 00000100:
> * Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
> * Ebp: 01C9F3D4: 01C9F418 0040C9C9 000000D0 00012000 00000000 1A6B4000
> * SegCs: 0000019F:
> * EFlags: 00000246:
> * Esp: 01C9F35C: 011420B4 00200002 00200000 01C9F374 00415052 00000004
> * SegSs: 000001A7:
> * *******************************************************************************
> * ----
> * Short Stack Dump
> * BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
> * 0040C9C9 Module(SQLSERVR+0000C9C9)
> * 00485EFA Module(SQLSERVR+00085EFA)
> * 00485FF5 Module(SQLSERVR+00085FF5)
> * 00483C40 Module(SQLSERVR+00083C40)
> * 01C9FBA2 Module(UNKNOWN+00000000)
> * ----
> *Dump thread - spid = 6, PSS = 0x1a634098, EC = 0x1a6343c0
> *Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL
> Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
> * *******************************************************************************
> *
> * BEGIN STACK DUMP:
> * 10/20/04 15:27:13 spid 6
> *
> * StackDump (all)
> *
> *
> *
> * Edi: C1A82CE0:
> * Esi: 00000001:
> * Eax: 002A005C:
> * Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161512
> * Ecx: 01B2FC50: 01B2FED0 00982517 00000000 01B2FC78 004017CB FFFFFFFF
> * Edx: 00000100:
> * Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
> * Ebp: 01B2FBE0: 01B2FC18 410721D6 00E02C90 1A634564 01B2FC18 000007D0
> * SegCs: 0000019F:
> * EFlags: 00000246:
> * Esp: 01B2FB88: FFFFFFFF BFF831BC C1A82CE0 FFFFFFFF 00000001 BFF8318C
> * SegSs: 000001A7:
> * *******************************************************************************
> * ----
> * Short Stack Dump
> * BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
> * 410721D6 Module(UMS+000021D6) (UmsScheduler::Suspend+00000066)
> * 00879042 Module(SQLSERVR+00479042) (GetOSErrString+0000230F)
> * 004017CB Module(SQLSERVR+000017CB)
> * 00401662 Module(SQLSERVR+00001662)
> * 00517249 Module(SQLSERVR+00117249)
> * 41075002 Module(UMS+00005002) (UmsThreadScheduler::Context+00000532)
> * 41074698 Module(UMS+00004698) (UmsThreadScheduler::~UmsThreadScheduler+00000198)
> * 542868FF Module(UNKNOWN+00000000)
> * ----
> *Dump thread - spid = 7, PSS = 0x1a684098, EC = 0x1a6843c0
> *Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL
> Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
> * *******************************************************************************
> *
> * BEGIN STACK DUMP:
> * 10/20/04 15:27:13 spid 7
> *
> * StackDump (all)
> *
> *
> *
> * Edi: C1A82560:
> * Esi: 00000001:
> * Eax: 002A005C:
> * Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161512
> * Ecx: 0194FC3C: 0194FED0 00982517 00000000 0194FC64 004017CB FFFFFFFF
> * Edx: 00000100:
> * Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
> * Ebp: 0194FBCC: 0194FC04 410721D6 00E02E20 1A684564 0194FC04 000007D0
> * SegCs: 0000019F:
> * EFlags: 00000246:
> * Esp: 0194FB74: FFFFFFFF BFF831BC C1A82560 FFFFFFFF 00000001 BFF8318C
> * SegSs: 000001A7:
> * *******************************************************************************
> * ----
> * Short Stack Dump
> * BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
> * 410721D6 Module(UMS+000021D6) (UmsScheduler::Suspend+00000066)
> * 00879042 Module(SQLSERVR+00479042) (GetOSErrString+0000230F)
> * 004017CB Module(SQLSERVR+000017CB)
> * 00401662 Module(SQLSERVR+00001662)
> * 0051876D Module(SQLSERVR+0011876D)
> * 41075002 Module(UMS+00005002) (UmsThreadScheduler::Context+00000532)
> * 41074698 Module(UMS+00004698) (UmsThreadScheduler::~UmsThreadScheduler+00000198)
> * 542868FF Module(UNKNOWN+00000000)
> * ----
> *Dump thread - spid = 8, PSS = 0x1a6b8098, EC = 0x1a6b83c0
> *Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL
> Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
> * *******************************************************************************
> *
> * BEGIN STACK DUMP:
> * 10/20/04 15:27:13 spid 8
> *
> * StackDump (all)
> *
> *
> *
> * Edi: C1A84670:
> * Esi: 00000001:
> * Eax: 002A005C:
> * Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161512
> * Ecx: 0225E550: 0225E64C 0097E7BA FFFFFFFF 0225E58C 0040330A 1A6B2030
> * Edx: 00000100:
> * Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
> * Ebp: 0225E4D4: 0225E504 00440F0C 1A6F2000 00002000 0009C000 00000000
> * SegCs: 0000019F:
> * EFlags: 00000246:
> * Esp: 0225E454: FFFFFFFF BFF831BC C1A84670 FFFFFFFF 00000001 BFF8318C
> * SegSs: 000001A7:
> * *******************************************************************************
> * ----
> * Short Stack Dump
> * BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
> * 00440F0C Module(SQLSERVR+00040F0C)
> * 00441154 Module(SQLSERVR+00041154)
> * 0040330A Module(SQLSERVR+0000330A)
> * 00403E2F Module(SQLSERVR+00003E2F)
> * 00406528 Module(SQLSERVR+00006528)
> * 004061CB Module(SQLSERVR+000061CB)
> * 00405DF8 Module(SQLSERVR+00005DF8)
> * 004F7294 Module(SQLSERVR+000F7294)
> * 004050F7 Module(SQLSERVR+000050F7)
> * 00409E39 Module(SQLSERVR+00009E39)
> * 00409C49 Module(SQLSERVR+00009C49)
> * 00515096 Module(SQLSERVR+00115096)
> * 00514FB7 Module(SQLSERVR+00114FB7)
> * 0050C0EB Module(SQLSERVR+0010C0EB)
> * 005100FF Module(SQLSERVR+001100FF)
> * 0050F152 Module(SQLSERVR+0010F152)
> * 00519C2D Module(SQLSERVR+00119C2D)
> * 41075002 Module(UMS+00005002) (UmsThreadScheduler::Context+00000532)
> * 41074698 Module(UMS+00004698) (UmsThreadScheduler::~UmsThreadScheduler+00000198)
> * 542868FF Module(UNKNOWN+00000000)
> * ----
> *Dump thread - spid = 9, PSS = 0x1a6b0098, EC = 0x1a6b03c0
> *Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL
> Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
> * *******************************************************************************
> *
> * BEGIN STACK DUMP:
> * 10/20/04 15:27:13 spid 9
> *
> * StackDump (all)
> *
> *
> *
> * Edi: C1A848E0:
> * Esi: 00000001:
> * Eax: 002A005C:
> * Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161512
> * Ecx: 022FF05C: 022FF654 00980D9F 00000000 022FF660 0050FFC8 00000002
> * Edx: 00000100:
> * Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
> * Ebp: 022FC784: 022FCBBC 00571383 022FE000 00001000 0037C000 00000000
> * SegCs: 0000019F:
> * EFlags: 00000246:
> * Esp: 022FC704: FFFFFFFF BFF831BC C1A848E0 FFFFFFFF 00000001 BFF8318C
> * SegSs: 000001A7:
> * *******************************************************************************
> * ----
> * Short Stack Dump
> * BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
> * 00571383 Module(SQLSERVR+00171383) (SQLExit+0004B903)
> * 00571315 Module(SQLSERVR+00171315) (SQLExit+0004B895)
> * 00571741 Module(SQLSERVR+00171741) (SQLExit+0004BCC1)
> * 00511A3D Module(SQLSERVR+00111A3D)
> * 0050FFC8 Module(SQLSERVR+0010FFC8)
> * 0050F152 Module(SQLSERVR+0010F152)
> * 00519C2D Module(SQLSERVR+00119C2D)
> * 41075002 Module(UMS+00005002) (UmsThreadScheduler::Context+00000532)
> * 41074698 Module(UMS+00004698) (UmsThreadScheduler::~UmsThreadScheduler+00000198)
> * 542868FF Module(UNKNOWN+00000000)
> * ----
> 2004-10-20 15:27:13.69 server SQL Server is aborting. Fatal exception c0000005 caught.
>|||Hi
The problem is solved. The client had his network card damaged
and apparently this caused problems (or something related
to the card configuration) cause after replacing it the
server started up.
I'm curious what is so important in network configuration
that could disable SQL server startup?
Hilarion|||> Tibor Karaszi, SQL Server MVP
Thanks for your time anyway.
Hilarion|||Hi Hilarion,
It's great to hear that it was resolved by replacing the damaged network
card. SQL Server startup need configure net library and it is entirely
possible to cause the access violation when it fails based on my experience
Anyway, to find out the root cause of this issue we may need to analyze
memory dumps, this work has to be done by contacting Microsoft Product
Support Services.
Thank you for your patience and corperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Michael Cheng
Online Partner Support Specialist
Partner Support Group
Microsoft Global Technical Support Center
---
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!

MSDE SQL Server marked as SUSPECT

Hello all! I have an instance of MSDE that is marked as SUSPECT. In
the error log I get:
I/O error on backup or restore restart-checkpoint file 'C:\Program
Files\Microsoft SQL Server\MSSQL$SBSMONITORING\backup\model4IDR.ckp'.
Operating system error 3(The system cannot find the path specified.).
The statement is proceeding but is non-restartable.
We don't have Enteprise Manager to look any closer at the DB. Do any of
you have a suggestion as to how to get this DB operational?
Jason
Restore it from a known good backup.
Jim
"Jason Hunsberger" <systems182@.nospam_andersontech.com> wrote in message
news:u1ZDFhWDFHA.3020@.TK2MSFTNGP09.phx.gbl...
> Hello all! I have an instance of MSDE that is marked as SUSPECT. In the
> error log I get:
> I/O error on backup or restore restart-checkpoint file 'C:\Program
> Files\Microsoft SQL Server\MSSQL$SBSMONITORING\backup\model4IDR.ckp'.
> Operating system error 3(The system cannot find the path specified.). The
> statement is proceeding but is non-restartable.
> We don't have Enteprise Manager to look any closer at the DB. Do any of
> you have a suggestion as to how to get this DB operational?
> Jason
sql

MSDE SQL Database Marked SUSPECT

Hello all! I have an instance of MSDE that is marked as SUSPECT. In
the error log I get:
I/O error on backup or restore restart-checkpoint file 'C:\Program
Files\Microsoft SQL Server\MSSQL$SBSMONITORING\backup\model4IDR.ckp'.
Operating system error 3(The system cannot find the path specified.).
The statement is proceeding but is non-restartable.
We don't have Enteprise Manager to look any closer at the DB. Do any of
you have a suggestion as to how to get this DB operational?
Jason
Jason,
You might check with Veritas regarding the Backup Exec.. The 4IDR part of
the filenames may have to do with their Intelligent Disaster Recovery..
Hope that helps,
David Copeland
Microsoft Small Business Server Support
This posting is provided "AS IS" with no warranties, and confers no rights.
SBS Newsgroups:
SBS v4.x: microsoft.public.backoffice.smallbiz
SBS 2000: microsoft.public.backoffice.smallbiz2000
SBS 2003: microsoft.public.windows.server.sbs
"Jason Hunsberger" <systems182@.nospam_andersontech.com> wrote in message
news:umOi6EWDFHA.208@.TK2MSFTNGP12.phx.gbl...
> Hello all! I have an instance of MSDE that is marked as SUSPECT. In
> the error log I get:
> I/O error on backup or restore restart-checkpoint file 'C:\Program
> Files\Microsoft SQL Server\MSSQL$SBSMONITORING\backup\model4IDR.ckp'.
> Operating system error 3(The system cannot find the path specified.).
> The statement is proceeding but is non-restartable.
> We don't have Enteprise Manager to look any closer at the DB. Do any of
> you have a suggestion as to how to get this DB operational?
> Jason

MSDE SP4 Install problems - invalid instance name

Hi,
Seen this question posted in several places, but none of the fixes stated
have done the trick. I'm trying to patch several MSDE instances installed by
Sharepoint. Instance names are SHAREPOINT.All three instances are installed
on W2k3 Servers. When I run the install from the cmd prompt, I use:
<install Dir>\setup /upgradesp sqlrun INSTANCENAME=SHAREPOINT /L*v
c:\MSDELog.log
I have also tried
<install Dir>\setup /upgradesp sqlrun INSTANCENAME=SHAREPOINT
DISABLENETWORKPROTOCOLS=0 /L*v c:\MSDELog.log
Same thing happens. I get an errors that states:"The instance name specified
is invalid". I know this to be untrue - I can query the databases in it
using SQL Client tools (Query analyser)
I've checked out the install package that was used in the registry(
HKEY_CLASSES_ROOT\Installer\Products\95C756568A324 7948B0EAB40BE0DE4F4\SourceList)
which suggests SQLRUN16.msi was used for the install. As this is the case,
all the documentation says I can use SQL2000.MSDE-KB884525-SP4-x86-ENU.EXE
for the installation. However, it still fails.
I have also had to install SP4 onto several instances created by the MS CRM
Outlook client. To do this I have used the following cmd in the cmd prompt:
<install Dir>\setup /upgradesp sqlrun INSTANCENAME=CRM /L*v c:\MSDELog.log
This works perfectly.However, I cannot do this on any of my SHAREPOINT
Instances.
Can anyone assist please?
Many Thanks
John
hi John,
John wrote:
> Hi,
> Seen this question posted in several places, but none of the fixes
> stated have done the trick. I'm trying to patch several MSDE
> instances installed by Sharepoint. Instance names are SHAREPOINT.All
> three instances are installed on W2k3 Servers. When I run the install
> from the cmd prompt, I use:
from the sp4 readme file,
"MSDE 2000 SP4 updates instances of SQL Server 2000 MSDE 2000 and MSDE 2000
Release A. "
Share Point installs a different version of MSDE, known as WMSDE where some
intrinsic MSDE limits has been removed (2gb data file per database) in order
to fullfill Share Point needs and requirements...
so, in my understanding, I think you have to get the new WMSDE package to
upgrade your Share Point instances...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Hi Andrea
First of all, many thanks for the reply. Could you post a URL to where I can
download the new WMSDE Patch? I've searched, but all I could find was a
Critical Update and a service pack for Sharepoint. Do I need to install the
who service pack? I thought I had already done that, and my SMS 2003 is not
telling me that the Service Pack is required, only the msde instance
requires updating
Many Thanks
Regards,
John
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3h8f6oFfh31iU1@.individual.net...
> hi John,
> John wrote:
> from the sp4 readme file,
> "MSDE 2000 SP4 updates instances of SQL Server 2000 MSDE 2000 and MSDE
> 2000 Release A. "
> Share Point installs a different version of MSDE, known as WMSDE where
> some intrinsic MSDE limits has been removed (2gb data file per database)
> in order to fullfill Share Point needs and requirements...
> so, in my understanding, I think you have to get the new WMSDE package to
> upgrade your Share Point instances...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||hi John,
John wrote:
> Hi Andrea
> First of all, many thanks for the reply. Could you post a URL to
> where I can download the new WMSDE Patch? I've searched, but all I
> could find was a Critical Update and a service pack for Sharepoint.
> Do I need to install the who service pack? I thought I had already
> done that, and my SMS 2003 is not telling me that the Service Pack is
> required, only the msde instance requires updating
>
unfortunately I'm not a Share Point guy... have you tried asking in its NG
hyerarchy?
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Hi Andrea. Thanks for all your help, I'll try there.
Regards,
John
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3hb3r4Fg7op9U1@.individual.net...
> hi John,
> John wrote:
> unfortunately I'm not a Share Point guy... have you tried asking in its NG
> hyerarchy?
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>

Wednesday, March 28, 2012

MSDE SP4

Can anyone please help me with upgrading to MSDE 2000 SP4
I need to upgrade BKUPExec Instance from SP3 to SP4 on Windows 2003 server.
The instance was installed by default while installing BKUPExec. Evry time I
run the upgrade from the command line using
setup /upgradesp sqlrun INSTANCENAME = BKUPEXEC /L*v C:\MSDElog.log
the upgrade fails. I am guessing it is failing becasue it was not installed
using the MSDE 2000 setup CD. Is it any way to upgrade it and getting working.
Thank you for your help.
Suhail
Hi
This command seems to have been recommended in other posts except there was
no spaces around the "=" see http://tinyurl.com/b4lbw
John
"suhail" wrote:

> Can anyone please help me with upgrading to MSDE 2000 SP4
> I need to upgrade BKUPExec Instance from SP3 to SP4 on Windows 2003 server.
> The instance was installed by default while installing BKUPExec. Evry time I
> run the upgrade from the command line using
> setup /upgradesp sqlrun INSTANCENAME = BKUPEXEC /L*v C:\MSDElog.log
> the upgrade fails. I am guessing it is failing becasue it was not installed
> using the MSDE 2000 setup CD. Is it any way to upgrade it and getting working.
> Thank you for your help.
> Suhail

MSDE SP4

Can anyone please help me with upgrading to MSDE 2000 SP4
I need to upgrade BKUPExec Instance from SP3 to SP4 on Windows 2003 server.
The instance was installed by default while installing BKUPExec. Evry time I
run the upgrade from the command line using
setup /upgradesp sqlrun INSTANCENAME = BKUPEXEC /L*v C:\MSDElog.log
the upgrade fails. I am guessing it is failing becasue it was not installed
using the MSDE 2000 setup CD. Is it any way to upgrade it and getting workin
g.
Thank you for your help.
SuhailHi
This command seems to have been recommended in other posts except there was
no spaces around the "=" see http://tinyurl.com/b4lbw
John
"suhail" wrote:

> Can anyone please help me with upgrading to MSDE 2000 SP4
> I need to upgrade BKUPExec Instance from SP3 to SP4 on Windows 2003 server
.
> The instance was installed by default while installing BKUPExec. Evry time
I
> run the upgrade from the command line using
> setup /upgradesp sqlrun INSTANCENAME = BKUPEXEC /L*v C:\MSDElog.log
> the upgrade fails. I am guessing it is failing becasue it was not installe
d
> using the MSDE 2000 setup CD. Is it any way to upgrade it and getting work
ing.
> Thank you for your help.
> Suhail

MSDE SP4

Can anyone please help me with upgrading to MSDE 2000 SP4
I need to upgrade BKUPExec Instance from SP3 to SP4 on Windows 2003 server.
The instance was installed by default while installing BKUPExec. Evry time I
run the upgrade from the command line using
setup /upgradesp sqlrun INSTANCENAME = BKUPEXEC /L*v C:\MSDElog.log
the upgrade fails. I am guessing it is failing becasue it was not installed
using the MSDE 2000 setup CD. Is it any way to upgrade it and getting working.
Thank you for your help.
SuhailHi
This command seems to have been recommended in other posts except there was
no spaces around the "=" see http://tinyurl.com/b4lbw
John
"suhail" wrote:
> Can anyone please help me with upgrading to MSDE 2000 SP4
> I need to upgrade BKUPExec Instance from SP3 to SP4 on Windows 2003 server.
> The instance was installed by default while installing BKUPExec. Evry time I
> run the upgrade from the command line using
> setup /upgradesp sqlrun INSTANCENAME = BKUPEXEC /L*v C:\MSDElog.log
> the upgrade fails. I am guessing it is failing becasue it was not installed
> using the MSDE 2000 setup CD. Is it any way to upgrade it and getting working.
> Thank you for your help.
> Suhailsql

MSDE sp3a install w/ no password

I was just wondering how I could install an instance of MSDE sp3a (on an XP
machine) without a SAPWD. Thanks.
Anthony
hi Anthony,
Anthony wrote:
> I was just wondering how I could install an instance of MSDE sp3a (on
> an XP machine) without a SAPWD. Thanks.
just provide the
BLANKSAPWD=1
parameter to the setup.exe boostrap installer...
http://msdn.microsoft.com/library/de...stsql_84xl.asp
BTW, just consider this is not a best practice... :D
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Thanks a million. And I agree, probably not a best practice.
Anthony
"Andrea Montanari" wrote:

> hi Anthony,
> Anthony wrote:
> just provide the
> BLANKSAPWD=1
> parameter to the setup.exe boostrap installer...
> http://msdn.microsoft.com/library/de...stsql_84xl.asp
> BTW, just consider this is not a best practice... :D
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
>

MSDE SP3a and XP SP2 on Localhost

I've upgraded to SP 2 for Windows XP and now none of my apps can see MSDE
default instance on localhost (i.e. not over the network). I found where an
upgrade to SP3 was required for MSDE to coexist with XP SP2, so I upgraded
and it's still not working.
Is there something else I'm missing?
thanks in advance
XP SP2 installs a new local firewall that prevents applications from opening
listening ports. You will need to configure the local firewall to allow
sqlservr.exe open listening ports.
See:
http://www.microsoft.com/sql/techinf...inxpsp2faq.asp
Jim
"tg2" <tg2@.discussions.microsoft.com> wrote in message
news:344BFC99-5751-46FB-B637-75A70398763B@.microsoft.com...
> I've upgraded to SP 2 for Windows XP and now none of my apps can see MSDE
> default instance on localhost (i.e. not over the network). I found where
an
> upgrade to SP3 was required for MSDE to coexist with XP SP2, so I upgraded
> and it's still not working.
> Is there something else I'm missing?
> thanks in advance
|||Except when running on the localhost (i.e. NOT using the network), the
firewall doesn't come into play. My application is using shared memory to
connect to the MSDE database and as such, never opens a network library --
thus opening the firewall doesn't fix the problem.
But thank you for your reply anyway...
"Jim Young" wrote:

> XP SP2 installs a new local firewall that prevents applications from opening
> listening ports. You will need to configure the local firewall to allow
> sqlservr.exe open listening ports.
> See:
> http://www.microsoft.com/sql/techinf...inxpsp2faq.asp
> Jim
> "tg2" <tg2@.discussions.microsoft.com> wrote in message
> news:344BFC99-5751-46FB-B637-75A70398763B@.microsoft.com...
> an
>
>
|||I have precisely the same problem. My application relies entirely on local
instance of MSDE.
Process associated with sqlservr does not show any port to be opened when
checked with "netstat" command. Any ideas how to work around it?
"tg2" wrote:

> Except when running on the localhost (i.e. NOT using the network), the
> firewall doesn't come into play. My application is using shared memory to
> connect to the MSDE database and as such, never opens a network library --
> thus opening the firewall doesn't fix the problem.
> But thank you for your reply anyway...
>
sql

Monday, March 26, 2012

MSDE security (still confused!)

I am distributing my application which includes MSDE 2000. My setup program
attaches .MDF and .LDF files once instance of MSDE 2000 is installed on the
customer’s computer. Now my worry is how can I restrict customers running W2k
or XP from accessing my database using EM or third party GUI’s. If customers
are running W2k or XP and have administrative privileges they can easily
register the installed instance of MSDE with EM and access the data
structure, stored proc etc?
I tested it on a computer which is running W2k, I logged in as
Administrator, ran my Setup program to install MSDE, attach .MDF and .LDF,
..NET framework, MDAC and my application. Then I installed EM and registered
an instance of installed MSDE with it. I could access everything in the
attached db.
How can I prevent this, as data structure, stored proc etc means a lot and
can’t let anyone steal it.
Thanks
Hi Job,
You're not going to like the answer but you can't. If the user has admin
privileges on the system, you can't keep them out. You can make it difficult
for them but you can't actually keep them out. There are many things they
can do to get back in.
You might need to look at encrypting your stored procs (ie create them WITH
ENCRYPTION). That at least might be a start.
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Job Lot" <JobLot@.discussions.microsoft.com> wrote in message
news:1AACA558-6859-43A6-BF6B-0550D0F7750C@.microsoft.com...
>I am distributing my application which includes MSDE 2000. My setup program
> attaches .MDF and .LDF files once instance of MSDE 2000 is installed on
> the
> customer's computer. Now my worry is how can I restrict customers running
> W2k
> or XP from accessing my database using EM or third party GUI's. If
> customers
> are running W2k or XP and have administrative privileges they can easily
> register the installed instance of MSDE with EM and access the data
> structure, stored proc etc?
> I tested it on a computer which is running W2k, I logged in as
> Administrator, ran my Setup program to install MSDE, attach .MDF and .LDF,
> .NET framework, MDAC and my application. Then I installed EM and
> registered
> an instance of installed MSDE with it. I could access everything in the
> attached db.
> How can I prevent this, as data structure, stored proc etc means a lot and
> can't let anyone steal it.
> Thanks
>
|||That was the last thing I wanted to hear. What’s the point of having windows
authentication in first place, when its will leave your database system
vulnerable. Why MS has designed it this way, where does all security features
goes? How can you ensure that you are designing robust and secure database
system? Imagine you spending weeks on designing your database system to find
out that there’s no secured way to conceal it. I can’t even use Access as I
can’t run stored proc with it? Is there any other better solution available?
"Greg Low [MVP]" wrote:

> Hi Job,
> You're not going to like the answer but you can't. If the user has admin
> privileges on the system, you can't keep them out. You can make it difficult
> for them but you can't actually keep them out. There are many things they
> can do to get back in.
> You might need to look at encrypting your stored procs (ie create them WITH
> ENCRYPTION). That at least might be a start.
> HTH,
>
> --
> Greg Low [MVP]
> MSDE Manager SQL Tools
> www.whitebearconsulting.com
> "Job Lot" <JobLot@.discussions.microsoft.com> wrote in message
> news:1AACA558-6859-43A6-BF6B-0550D0F7750C@.microsoft.com...
>
>
|||"Job Lot" <JobLot@.discussions.microsoft.com> wrote in message
news:3D7C097D-4567-46DA-9C98-29139C6B5FAF@.microsoft.com...
> That was the last thing I wanted to hear. What's the point of having
windows
> authentication in first place, when its will leave your database system
> vulnerable. Why MS has designed it this way, where does all security
features
> goes? How can you ensure that you are designing robust and secure database
> system? Imagine you spending weeks on designing your database system to
find
> out that there's no secured way to conceal it. I can't even use Access as
I
> can't run stored proc with it? Is there any other better solution
available?
A logical move would be from MSDE to SQL Server running on a server
platform. While similar issues exist with folks that have local
administrative access, you can lock down your instance of SQL Server fairly
tightly. Combine that with stored procedure encryption and possibly, file
level encryption you should be able to go a long way to protect your
intellectual investment.
Steve

MSDE Reboot Question (2 parts)

1) When I install and MSDE instance for the first time on a machine,
the install states that I must reboot the machine. However if I
manually start the instance, then my programs can access that instance
without a reboot.
2) If I uninstall the instance done in 1 above, through the Add/Remove
programs process, then subsequent installs of the same instance do not
prompt for a reboot.
So my basic question is:
Is a reboot REALLY necessary and if I manually (or programmatically)
start the instance? If a reboot is NOT really necessary, is there a
command line option that will keep that prompt from being displayed?
TIA for all replies
Wardell Castles
hi Wardell,
"Wardell Castles" <wardellcastles@.hotmail.com> ha scritto nel messaggio
news:65f20689.0412020822.1f340d53@.posting.google.c om
> 1) When I install and MSDE instance for the first time on a machine,
> the install states that I must reboot the machine. However if I
> manually start the instance, then my programs can access that instance
> without a reboot.
> 2) If I uninstall the instance done in 1 above, through the Add/Remove
> programs process, then subsequent installs of the same instance do not
> prompt for a reboot.
> So my basic question is:
> Is a reboot REALLY necessary and if I manually (or programmatically)
> start the instance? If a reboot is NOT really necessary, is there a
> command line option that will keep that prompt from being displayed?
> TIA for all replies
> Wardell Castles
usually a reboot is required to fullfill and commit all COM pending
registrations and services setting... and, when prompted, it's usually a
good idea to do it...
I do think that Windows Installer support a REBOOT=ReallySuppress
declaration, but I never used it... please have a look at
http://tinyurl.com/3tx4a
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

Friday, March 23, 2012

MSDE password change for "sa"

Hello,
If I can get into the default instance of MSDE using a Windows
account (trusted connection) using 'osql -E' is it possible for me to
change the 'sa' SQL account if I don't know the current password? The
Windows account is a domain admin and local box admin if that matters.
Also, can anyone point me to a Q article that will give me a step
by step on how to upgrade from MSDE to SQL so I can get past this 2GB
limitation?
If anyone can answer these I am definitely buying beers!!
Thanks,
DanIf you can login as an admin on the box and the
builtin\administrators group login was not removed or
modified, you will be logged in as a member of the sysadmins
server role. As a sysadmin, you can execute the following to
change the sa password:
sp_password NULL, 'NewSaPassword', 'sa'
Upgrading to SQL Server isn't too bad. Run the SQL Server
installation CD. You will be asked if you want to upgrade
your existing instance or install a new one. Choose to
upgrade.
For more detailed steps on upgrading, you can refer to the
SQL Server Books Online topic:
How to perform an edition upgrade within SQL Server 2000
(Setup)
http://msdn.microsoft.com/library/en-us/howtosql/ht_install_1d7y.asp
-Sue
On 15 Jun 2004 17:41:11 -0700, dankennedy24@.hotmail.com (Dan
Kennedy) wrote:
>Hello,
> If I can get into the default instance of MSDE using a Windows
>account (trusted connection) using 'osql -E' is it possible for me to
>change the 'sa' SQL account if I don't know the current password? The
>Windows account is a domain admin and local box admin if that matters.
> Also, can anyone point me to a Q article that will give me a step
>by step on how to upgrade from MSDE to SQL so I can get past this 2GB
>limitation?
>If anyone can answer these I am definitely buying beers!!
>Thanks,
>Dan|||But the current "sa" password isn't blank... will that statement still
work? I login to the machine as a local admin and connect via the
osql statement as the same ID as I logon to the machine with.
Sue Hoegemeier <Sue_H@.nomail.please> wrote in message news:<np8vc0p2v2lfj8ke5mm0vf6f8vmrfg9plg@.4ax.com>...
> If you can login as an admin on the box and the
> builtin\administrators group login was not removed or
> modified, you will be logged in as a member of the sysadmins
> server role. As a sysadmin, you can execute the following to
> change the sa password:
> sp_password NULL, 'NewSaPassword', 'sa'
> Upgrading to SQL Server isn't too bad. Run the SQL Server
> installation CD. You will be asked if you want to upgrade
> your existing instance or install a new one. Choose to
> upgrade.
> For more detailed steps on upgrading, you can refer to the
> SQL Server Books Online topic:
> How to perform an edition upgrade within SQL Server 2000
> (Setup)
> http://msdn.microsoft.com/library/en-us/howtosql/ht_install_1d7y.asp
> -Sue
> On 15 Jun 2004 17:41:11 -0700, dankennedy24@.hotmail.com (Dan
> Kennedy) wrote:
> >Hello,
> > If I can get into the default instance of MSDE using a Windows
> >account (trusted connection) using 'osql -E' is it possible for me to
> >change the 'sa' SQL account if I don't know the current password? The
> >Windows account is a domain admin and local box admin if that matters.
> > Also, can anyone point me to a Q article that will give me a step
> >by step on how to upgrade from MSDE to SQL so I can get past this 2GB
> >limitation?
> >
> >If anyone can answer these I am definitely buying beers!!
> >
> >Thanks,
> >Dan|||Yes...it will still work. That's what you would use to reset any
password when you are logged in as a sysadmin. Just pass null for the
old password. It doesn't mean the password is null. It means you
aren't supplying the old password.
-Sue
On 16 Jun 2004 11:26:10 -0700, dankennedy24@.hotmail.com (Dan Kennedy)
wrote:
>But the current "sa" password isn't blank... will that statement still
>work? I login to the machine as a local admin and connect via the
>osql statement as the same ID as I logon to the machine with.
>Sue Hoegemeier <Sue_H@.nomail.please> wrote in message news:<np8vc0p2v2lfj8ke5mm0vf6f8vmrfg9plg@.4ax.com>...
>> If you can login as an admin on the box and the
>> builtin\administrators group login was not removed or
>> modified, you will be logged in as a member of the sysadmins
>> server role. As a sysadmin, you can execute the following to
>> change the sa password:
>> sp_password NULL, 'NewSaPassword', 'sa'
>> Upgrading to SQL Server isn't too bad. Run the SQL Server
>> installation CD. You will be asked if you want to upgrade
>> your existing instance or install a new one. Choose to
>> upgrade.
>> For more detailed steps on upgrading, you can refer to the
>> SQL Server Books Online topic:
>> How to perform an edition upgrade within SQL Server 2000
>> (Setup)
>> http://msdn.microsoft.com/library/en-us/howtosql/ht_install_1d7y.asp
>> -Sue
>> On 15 Jun 2004 17:41:11 -0700, dankennedy24@.hotmail.com (Dan
>> Kennedy) wrote:
>> >Hello,
>> > If I can get into the default instance of MSDE using a Windows
>> >account (trusted connection) using 'osql -E' is it possible for me to
>> >change the 'sa' SQL account if I don't know the current password? The
>> >Windows account is a domain admin and local box admin if that matters.
>> > Also, can anyone point me to a Q article that will give me a step
>> >by step on how to upgrade from MSDE to SQL so I can get past this 2GB
>> >limitation?
>> >
>> >If anyone can answer these I am definitely buying beers!!
>> >
>> >Thanks,
>> >Dan

MSDE password change for "sa"

Wednesday, March 21, 2012

MSDE or VS.NET Problem

I recently installed a named MSDE instance and created a DB with SQLDMO. I can see the instance in VS.NET, but can't see the tables that SQLDMO created. When I rerun the script to create the tables, I get a SQL Server ODBC driver error saying the tables already exist. I have tried restarting the machine and the services, but still can't see the tables in VS.NET. The other strange thing is I also can't load data into the tables because SQLDMO says my tables are not in the Tables collection. I didn't get any errors when I originally ran the script that created my tables. When I checked the SQL log, I didn't see any errors, but also didn't see anything indicating the tables were created. Would SQL Server have logged this?

Please copy an replies to pearsonbe@.aol.com.Can you check if the SQLDMO statements used the same login as you are using to view the contents of the database? Do you use the correct name for the tables (server.database.owner.tablename)?|||Yes, I'm using the same login info in the code w/SQLDMO as well as when connecting in Visual Studio. For some reason, the ExecuteImmediate does not work with the DB script that was produced by my SQLDMO DB object. I was able to create a new table in VS and then delete it with SQLDMO, so my current workaround is to just deatch the original DB and reattach to the new DB.

Thanks.

MSDE on XP running, but not recognized in ODBC

I installed an MSDE instance for a user running XP with an
admin Windows account. The MSDE Server icon appears in
the notification area, but without the green arrow. Task
manager shows that it is running. Trying to start it up
manually doesn't do anything. When I go to add the Data
Source in ODBC, System DSN (MDAC 2.8 is installed), when
we go to pick the MSDE Server, it doesn't appear in the
drop down when picking a server. Any thoughts or ideas
would be great. Thanks, JRaub.
hi JRaub,
JRaub wrote:
> I installed an MSDE instance for a user running XP with an
> admin Windows account. The MSDE Server icon appears in
> the notification area, but without the green arrow. Task
> manager shows that it is running. Trying to start it up
> manually doesn't do anything. When I go to add the Data
> Source in ODBC, System DSN (MDAC 2.8 is installed), when
> we go to pick the MSDE Server, it doesn't appear in the
> drop down when picking a server. Any thoughts or ideas
> would be great. Thanks, JRaub.
please have a look at
http://support.microsoft.com/default...b;EN-US;814132
if you want to modify the networkprotocols setting, please run the Server
Network Utility (svrnetcn.exe) and enable the desired protocol
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Thanks. I'll give this a shot. Nothing else has worked.[vbcol=seagreen]
>--Original Message--
>hi JRaub,
>JRaub wrote:
an[vbcol=seagreen]
Task
>please have a look at
>http://support.microsoft.com/default.aspx?scid=kb;EN-
US;814132
>if you want to modify the networkprotocols setting,
please run the Server
>Network Utility (svrnetcn.exe) and enable the desired
protocol
>--
>Andrea Montanari (Microsoft MVP - SQL Server)
>http://www.asql.biz/DbaMgr.shtm
http://italy.mvps.org
>DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
>(my vb6+sql-dmo little try to provide MS MSDE 1.0 and
MSDE 2000 a visual
>interface)
>-- remove DMO to reply
>
>.
>

MSDE on SBS2003 from Network

I have created a new MSDE instance on my SBS 2003 Standard server, using
MSDE setup.
The service is started, and I can access the MSDE instance locally on the
server, but I am unable to access it from other PCs on the network (in the
domain).
Specifically, I am using SQL Server Enterprise Manager. It reports the
message "Sql Server does not exist or access denied" when I try to connect
to the instance (using "myserver\instance-name"). I tried ISQL and also get
access denied.
I installed Enterprise Manager locally on the server and it connects to the
instance without problem.
Looking at the Properties/General/Network Configuration I can see TCPIP is
enabled and now using port 1433 (although it was set to port 0 after
installation?).
My user account is a valid login with the "System Administrator" role an has
dbo access to all databases.
The Windows Firewall allows port 1433 at the client and no firewall on the
server.
What else to check?
richlm wrote:

>I have created a new MSDE instance on my SBS 2003 Standard server, using
>MSDE setup.
>The service is started, and I can access the MSDE instance locally on the
>server, but I am unable to access it from other PCs on the network (in the
>domain).
>Specifically, I am using SQL Server Enterprise Manager. It reports the
>message "Sql Server does not exist or access denied" when I try to connect
>to the instance (using "myserver\instance-name"). I tried ISQL and also
>get access denied.
The default for MSDE is to not listen to the network, only the local
machine.

>I installed Enterprise Manager locally on the server and it connects to
>the instance without problem.
>Looking at the Properties/General/Network Configuration I can see TCPIP is
>enabled and now using port 1433 (although it was set to port 0 after
>installation?).
This was in the Server Network Utility, yes?
Has the MSDE instance been restarted since you enabled a network protocol?

>My user account is a valid login with the "System Administrator" role an
>has dbo access to all databases.
>The Windows Firewall allows port 1433 at the client and no firewall on the
>server.
The Windows Firewall on a client is irrelevant, since it has no impact on
outgoing connections. It would only be of interest if MSDE (or SQL) was
installed on the workstation itself.
Out of interest, where did you get the SQL client utilities from? They're
not included with SBS2003 Standard, nor are you licenced to use them in an
SBS2003 Standard environment.
Steve Foster [SBS MVP]
MVPs do not work for Microsoft. Please reply only to the newsgroups.
|||Yes, TCP 1433 is at the top of the list of "enabled protocols" in the server
network utility, and I restarted the MSDE service after setting the port.
But I just realized that cliconfg does not allow me to choose which MSDE
instance to apply the changes to.
I just found a Microsoft support notice "Server Network Utility may display
incorrect protocol properties in SQL Server 2000" at
http://support.microsoft.com/?kbid=887700 - I'll investigate this further
(although I'm using SP4 so the hotfix does not apply).
As for licencing, I have an MSDN Universal subscription which includes the
use of SQL client tools for development purposes. But thanks for the
reminder, and I'll re-check the licence terms to make sure I've not
misunderstood something about where the tools can be used.
Richard.
|||richlm wrote:

>Yes, TCP 1433 is at the top of the list of "enabled protocols" in the
>server network utility, and I restarted the MSDE service after setting the
>port.
>But I just realized that cliconfg does not allow me to choose which MSDE
>instance to apply the changes to.
Eh?

>I just found a Microsoft support notice "Server Network Utility may
>display incorrect protocol properties in SQL Server 2000" at
>http://support.microsoft.com/?kbid=887700 - I'll investigate this further
>(although I'm using SP4 so the hotfix does not apply).
>As for licencing, I have an MSDN Universal subscription which includes the
>use of SQL client tools for development purposes. But thanks for the
>reminder, and I'll re-check the licence terms to make sure I've not
>misunderstood something about where the tools can be used.
AIUI, the MSDN licence does not cover using the SQL client utilities to
manage a production server. So, unless your SBS is only used for your
development network, you are not legally allowed to use the MSDN licence
to manage SQL services on SBS. But hey, IANAL, nor a member of the licence
police...
Steve Foster [SBS MVP]
MVPs do not work for Microsoft. Please reply only to the newsgroups.
|||OK - I should be running svrnetcn.exe and not cliconfg.exe...
Now I can choose the instance - and can confirm that the problem referred to
at http://support.microsoft.com/?kbid=887700 also applies to SP4. The
workaround suggested there (choose another instance then go back to the one
you really wanted) refreshes the UI correctly.
But I still can't connect remotely using EM or OSQL - yet both work locally.
I've googled to the end of the earth and not found other suggestions so my
guess now is it's probably due to the fact I have installed VS2005 on my
client - which also installs SQL 2005 express.
When I try to connect using OSQL I get the following error:
[SQL Native Client]Unable to complete login process due to delay in opening
server connection.
This perhaps implies my client PC is "broken" for connecting to SQL 2000
instances?
The version of "SQL Server Native Client" I currently use is 9.00.1314.06.
I think I'll wait for SQL 2005 launch in a couple of weeks, where
(hopefully) this problem goes away.
Can anyone confirm this?
|||Richard Money wrote:

>OK - I should be running svrnetcn.exe and not cliconfg.exe...
>Now I can choose the instance - and can confirm that the problem referred
>to at http://support.microsoft.com/?kbid=887700 also applies to SP4. The
>workaround suggested there (choose another instance then go back to the
>one you really wanted) refreshes the UI correctly.
>But I still can't connect remotely using EM or OSQL - yet both work
>locally. I've googled to the end of the earth and not found other
>suggestions so my guess now is it's probably due to the fact I have
>installed VS2005 on my client - which also installs SQL 2005 express.
>When I try to connect using OSQL I get the following error:
>[SQL Native Client]Unable to complete login process due to delay in
>opening server connection.
>This perhaps implies my client PC is "broken" for connecting to SQL 2000
>instances?
>The version of "SQL Server Native Client" I currently use is 9.00.1314.06.
>I think I'll wait for SQL 2005 launch in a couple of weeks, where
>(hopefully) this problem goes away.
>Can anyone confirm this?
I don't know whether SQL2005 beta client tools can communicate with
SQL2000. I suspect that that is something likely to be left until very
close to RTM (and may require that SQL2000 gets an update of some sort).
I'd stick to trying with SQL2000 client utilities.
Steve Foster [SBS MVP]
MVPs do not work for Microsoft. Please reply only to the newsgroups.
|||Pretty sure that my problem connecting to MSDE over network was due to a
pre-release version of SQL2005 Express (sept. CTP) on my client.
Have just successfully installed the RTM of SQL Express on SBS as a named
instance, enabled networking using the SQL Server Configuration Manager, and
I can connect to the instance from VS2005 (RTM) running on another machine.
The default SBS instances for Sharepoint and SBSMonitoring are still running
MSDE (and still work!).
Now I'm happy:-)

MSDE on machine with SQL Server

Hello,
A named instance of MSDE will be installed on our clients machines along with our VB.Net during the installation. Will this work fine even if the client already has SQL Server on his/her machine. I mean will the installation of named instance of MSDE wor
k smoothly even if SQL Server already exists. If yes, then does that apply for both SQL Server 7 & 2000. If no, then what should I do.
Thanks
dev
You should have no problems, as long as you are installing a uniquely named
instance. This is true even if SQL Server 7 is already installed on the
system.
Jim
"dev" <anonymous@.discussions.microsoft.com> wrote in message
news:B46C4961-748E-47E1-AD22-2A712100428F@.microsoft.com...
> Hello,
> A named instance of MSDE will be installed on our clients machines along
with our VB.Net during the installation. Will this work fine even if the
client already has SQL Server on his/her machine. I mean will the
installation of named instance of MSDE work smoothly even if SQL Server
already exists. If yes, then does that apply for both SQL Server 7 & 2000.
If no, then what should I do.
> Thanks
> dev
sql

Monday, March 19, 2012

MSDE no show in server explorer

I have installed default instance of SQLServer 2005 DE on Windows Server 2003 host. I also installed a named instance of MSDE rel A. I can connect to the MSDE instance from Management Studio but it does not appear in the list of servers when I try to add the connection in VS2005 server explorer. What am I doing wrong?

- Dick

Anybody?

I can connect to the named MSDE instance (now upgraded to SP4) with management studio and osql, but it does not appear in the server list in VS2005 studio explorer, or in the OS ODBC DataSources utility.

The log shows the MSDE instance is listening on shared memory. I cannot configure it for named pipes because I can only see the default SS2K5 instance in SQL Server Configuration Manager.

All contributions massively appreciated.

|||

MSDE instances listening only on shared memory generally do not show up in the list boxes you mention.

You can configure the MSDE to listen on named pipes (or TCP) through the Server Network Utility.

|||

Thanks Peter

That cracked it. Here's what I did:

- I ran Microsoft SQL Server\80\Tools\binn\SVRNETCN.exe and enabled Named Pipes and TCP/IP

- restarted the server instance but it did not fix it.

- rebooted the machine, got various system errors e.g. reporting services could not connect to db. There was a conflict on port 1433.

- re-ran Server Network Configuration utility, set TCP/IP port to 0. (Bit confused by this, I thought MSDE sp 3 sorted out port sharing issue ...? I havn't tried a remote connection yet)

- Ran SQL Configuration Manager and created np aliases for both the default and named instances.

- rebooted and everything fixed. Able to create a System DSN. MSDE instance did not appear in server list when I tried to add a new a connection in VS2005 server explorer, but I was able to type in the server name and connect ok.

As a general observation I have to say I am not a member of SQL Server 2005 fan club yet. It promises simplicity, but delivers frustration.

Friday, March 30, 2012

MSDE Tookit thinks MSDE is not installed when it is.

MSDE startup problem

MSDE SQL Server marked as SUSPECT

MSDE SQL Database Marked SUSPECT

MSDE SP4 Install problems - invalid instance name

Wednesday, March 28, 2012

MSDE SP4

MSDE SP4

MSDE SP4

MSDE sp3a install w/ no password

MSDE SP3a and XP SP2 on Localhost

Monday, March 26, 2012

MSDE security (still confused!)

MSDE Reboot Question (2 parts)

Friday, March 23, 2012

MSDE password change for "sa"

MSDE password change for "sa"

MSDE password change for "sa"

Wednesday, March 21, 2012

MSDE or VS.NET Problem

MSDE on XP running, but not recognized in ODBC

MSDE on SBS2003 from Network

MSDE on machine with SQL Server

Monday, March 19, 2012

MSDE no show in server explorer

MSDE Failed Install

Blog Archive

About Me