Can we distribute MSDE2000A.exe?

The MSDE redistribution agreement is unclear (to me). It talks about
redistributing specific parts of MSDE. I just want to put the whole
MSDE2000A.exe setup program on a CD with my app's setup program. Is that
allowed?
Thanks!
J.
hi,
Process Patrol wrote:
> The MSDE redistribution agreement is unclear (to me). It talks about
> redistributing specific parts of MSDE. I just want to put the whole
> MSDE2000A.exe setup program on a CD with my app's setup program. Is
> that allowed?
yes... you only have to (freely) register for distributions rights at
http://www.microsoft.com/sql/msde/ho...stregister.asp
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
sql

Can they co-exist ?

Hi,
Can MSDE and SQl server 2000 standard edition co-exist.
Arvind.Hi
Yes, one just has to be a named instance, not listening on port 1433.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Arvi" <Arvi@.discussions.microsoft.com> wrote in message
news:A8C80E5D-DDAC-4219-9383-712651A275EE@.microsoft.com...
> Hi,
> Can MSDE and SQl server 2000 standard edition co-exist.
> Arvind.|||Yes.
--
Please post DDL, sample data and desired results.
See http://www.aspfaq.com/5006 for info.
"Arvi" <Arvi@.discussions.microsoft.com> wrote in message
news:A8C80E5D-DDAC-4219-9383-712651A275EE@.microsoft.com...
> Hi,
> Can MSDE and SQl server 2000 standard edition co-exist.
> Arvind.|||Hi Mike and Aaron,
Thanks for your reply, in that case why would the installation of SQl
server 2000 std edition on Win 2K3 64 bit server not complete, it just hangs
at the point
"Setup is configuring your selected options " and it never completes the
installation.
No matter what uninstalling previous editions of SQL server or MSDE nothing
helps.
This is waht the end of log file reads like:
--
15:50:34 Monarch
15:50:34 Monarch\Monr1033
15:50:34 Monarch\MonrIntl
15:50:34 Jet
15:50:34 CoreInst
15:50:34 CoreCOM
15:50:34 CoreCOM\Res1033
15:50:34 CoreCOM\ResIntl
15:50:34 CoreTool
15:50:34 CoreTool\Res1033
15:50:34 CoreTool\ResOther
15:50:34 DBLibCli
15:50:34 SFExt
15:50:34 SFExt\ActiveX
15:50:34 SFExt\ActiveX\Res1033
15:50:34 SFExt\ActiveX\ResIntl
15:50:34 SFExt\Res1033
15:50:34 SFExt\ResIntl
15:50:34 Trace
15:50:34 Trace\Res1033
15:50:34 Trace\ResOther
15:50:34 MiscCore
15:50:34 MC
15:50:34 MC\MC1033
15:50:34 MC\MCIntl
15:50:34 MC\Help
15:50:34 SQLMgr
15:50:34 SQLMgr\Res1033
15:50:34 SQLMgr\ResIntl
15:50:34 SvrTool
15:50:34 SvrTool\Res1033
15:50:34 SvrTool\ResIntl
15:50:34 DTSUI
15:50:34 DTSUI\Res1033
15:50:34 DTSUI\ResIntl
15:50:34 MSOlap
15:50:34 MSOlap\Res1033
15:50:34 MSOlap\ResIntl
15:50:34 ATL
15:50:34 ATL\winnt
15:50:34 ATL\win9x
15:50:34 MFC42U
15:50:34 VC
15:50:35 VB
15:50:35 OCX1
15:50:35 SQLAdHlp
15:50:35 SQLAdHlp\Res1033
15:50:35 SQLAdHlp\ResOther
15:50:35 {E07FDDBE-5A21-11d2-9DAD-00C04F79D434}
15:50:35 {E07FDDC7-5A21-11d2-9DAD-00C04F79D434}
15:50:35 {E07FDDC0-5A21-11d2-9DAD-00C04F79D434}
15:50:35 {E07FDDBF-5A21-11d2-9DAD-00C04F79D434}
15:50:35 End Action LogSelectedComponents
15:50:35 Begin Action InstallPkgs:
15:50:35 Begin Action: Locked Connectivity Files Check
15:50:35 ConnectivityLocked returned: 0
15:50:35 The operation completed successfully.
15:50:35 End Action: Locked Connectivity Files Check
15:50:35 Setup is installing Microsoft Data Access Components (MDAC) ...
15:50:35 F:\MS_sql2k\X86\Other\sqlredis.exe /q:a /C:"setupre.exe WARN=1 -s
-SMS"
15:50:45 ExitCode: 0
15:50:45 Setup is installing Microsoft Distributed Transaction Coordinator
(MSDTC) ...
15:50:45 C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\SqlSetup\Bin\cldtcstp.exe
-SupportDir "C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\SqlSetup\Bin" -DTCPkg
"F:\MS_sql2k\X86\Other\dtcsetup.exe" -LogFile "C:\WINDOWS\sqlstp.log"
15:50:45 Process Exit Code: (0)
15:50:45 InstallMSSearch instance: MSSQLSERVER
15:50:45 Software\Microsoft\Search\Install:Version : 9.107.5512
15:50:45 MSSearch 2.0 or greater version check returned 1
15:50:45 Setup is installing the Microsoft Full-Text Search Engine ...
15:50:45 "F:\MS_sql2k\X86\FullText\MSSearch\Search\SearchStp.exe" /s
/a:SQLServer
15:50:48 Process Exit Code: (0)
15:50:48 /Q:A /T:C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\ixp001.tmp
15:50:48 Setup is installing HTML Help ...
15:50:48 HTML Help installer exit code: 0
15:51:10 End Action InstallPkgs
15:51:10 Begin Action MoveFileData:
15:51:10 Enabled SELFREGISTERBATCH
15:51:10 Enabled CORECOMPONENTHANDLING
15:51:34 Begin Action: MoveFileDataSpecial
15:51:35 End Action: MoveFileDataSpecial
15:51:35 End Action MoveFileData
15:51:35 Begin Action ProcessAfterDataMove:
15:51:35 F:\MS_sql2k\X86\Binn\hhcol.exe C:\Program Files (x86)\Microsoft SQL
Server\80\Tools\Books
15:51:35 End Action ProcessAfterDataMove
15:51:35 Begin Action BuildServer:
15:51:36 C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\SqlSetup\Bin\scm.exe -Silent 1
-Action 5 -ExePath "C:\Program Files (x86)\Microsoft SQL
Server\MSSQL\binn\sqlservr.exe" -Service "MSSQLSERVER"
15:51:36 Process Exit Code: (0)
15:51:36 Begin Action: CreateRegistrySetSQL
15:51:36 End Action: CreateRegistrySetSQL
15:51:36 Begin Action: RegWriteSetupEntry
15:51:36 End Action: RegWriteSetupEntry
15:51:36 Begin Action: CreateSer
15:51:36 End Action: CreateSer
15:51:36 Begin Action: SkuIt
15:51:36 End Action: SkuIt
15:51:36 SetFileSecuritySQLAndAdmin for C:\Program Files (x86)\Microsoft SQL
Server\MSSQL returned: 0, 0
15:51:36 SetRegSecuritySQLAndAdmin for
Software\Microsoft\MSSQLServer\MSSQLServer returned: 0, 0
15:51:36 Begin Action: UpdateSystemPath
15:51:36 Path successfully updated.
15:51:36 C:\Program Files\Support
Tools\;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;C:\Program Files (x86)\Microsoft SQL Server\80\Tools\BINN
15:51:36 End Action: UpdateSystemPath
15:51:37 C:\Program Files (x86)\Microsoft SQL
Server\80\Tools\Binn\cnfgsvr.exe -F "C:\WINDOWS\sqlstp.log" -I MSSQLSERVER
-V 1 -M 0 -Q "SQL_Latin1_General_CP1_CI_AS" -H 131446 -U sa -P
###############################################################################
Starting Service ...
SQL_Latin1_General_CP1_CI_AS
-m -Q -T4022 -T3659
---
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> Yes, one just has to be a named instance, not listening on port 1433.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Arvi" <Arvi@.discussions.microsoft.com> wrote in message
> news:A8C80E5D-DDAC-4219-9383-712651A275EE@.microsoft.com...
> > Hi,
> > Can MSDE and SQl server 2000 standard edition co-exist.
> >
> > Arvind.
>
>|||Hi
AFAIK, SQL Server 2000 with SP4 is compatible with X64, earlier versions are
not. SP4 is in beta.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Arvi" <Arvi@.discussions.microsoft.com> wrote in message
news:1D6E61ED-713D-4E50-8210-C0696C82AB2A@.microsoft.com...
> Hi Mike and Aaron,
> Thanks for your reply, in that case why would the installation of SQl
> server 2000 std edition on Win 2K3 64 bit server not complete, it just
hangs
> at the point
> "Setup is configuring your selected options " and it never completes the
> installation.
> No matter what uninstalling previous editions of SQL server or MSDE
nothing
> helps.
> This is waht the end of log file reads like:
> --
> 15:50:34 Monarch
> 15:50:34 Monarch\Monr1033
> 15:50:34 Monarch\MonrIntl
> 15:50:34 Jet
> 15:50:34 CoreInst
> 15:50:34 CoreCOM
> 15:50:34 CoreCOM\Res1033
> 15:50:34 CoreCOM\ResIntl
> 15:50:34 CoreTool
> 15:50:34 CoreTool\Res1033
> 15:50:34 CoreTool\ResOther
> 15:50:34 DBLibCli
> 15:50:34 SFExt
> 15:50:34 SFExt\ActiveX
> 15:50:34 SFExt\ActiveX\Res1033
> 15:50:34 SFExt\ActiveX\ResIntl
> 15:50:34 SFExt\Res1033
> 15:50:34 SFExt\ResIntl
> 15:50:34 Trace
> 15:50:34 Trace\Res1033
> 15:50:34 Trace\ResOther
> 15:50:34 MiscCore
> 15:50:34 MC
> 15:50:34 MC\MC1033
> 15:50:34 MC\MCIntl
> 15:50:34 MC\Help
> 15:50:34 SQLMgr
> 15:50:34 SQLMgr\Res1033
> 15:50:34 SQLMgr\ResIntl
> 15:50:34 SvrTool
> 15:50:34 SvrTool\Res1033
> 15:50:34 SvrTool\ResIntl
> 15:50:34 DTSUI
> 15:50:34 DTSUI\Res1033
> 15:50:34 DTSUI\ResIntl
> 15:50:34 MSOlap
> 15:50:34 MSOlap\Res1033
> 15:50:34 MSOlap\ResIntl
> 15:50:34 ATL
> 15:50:34 ATL\winnt
> 15:50:34 ATL\win9x
> 15:50:34 MFC42U
> 15:50:34 VC
> 15:50:35 VB
> 15:50:35 OCX1
> 15:50:35 SQLAdHlp
> 15:50:35 SQLAdHlp\Res1033
> 15:50:35 SQLAdHlp\ResOther
> 15:50:35 {E07FDDBE-5A21-11d2-9DAD-00C04F79D434}
> 15:50:35 {E07FDDC7-5A21-11d2-9DAD-00C04F79D434}
> 15:50:35 {E07FDDC0-5A21-11d2-9DAD-00C04F79D434}
> 15:50:35 {E07FDDBF-5A21-11d2-9DAD-00C04F79D434}
> 15:50:35 End Action LogSelectedComponents
> 15:50:35 Begin Action InstallPkgs:
> 15:50:35 Begin Action: Locked Connectivity Files Check
> 15:50:35 ConnectivityLocked returned: 0
> 15:50:35 The operation completed successfully.
> 15:50:35 End Action: Locked Connectivity Files Check
> 15:50:35 Setup is installing Microsoft Data Access Components (MDAC) ...
> 15:50:35 F:\MS_sql2k\X86\Other\sqlredis.exe /q:a /C:"setupre.exe WARN=1 -s
> -SMS"
> 15:50:45 ExitCode: 0
> 15:50:45 Setup is installing Microsoft Distributed Transaction Coordinator
> (MSDTC) ...
> 15:50:45 C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\SqlSetup\Bin\cldtcstp.exe
> -SupportDir "C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\SqlSetup\Bin" -DTCPkg
> "F:\MS_sql2k\X86\Other\dtcsetup.exe" -LogFile "C:\WINDOWS\sqlstp.log"
> 15:50:45 Process Exit Code: (0)
> 15:50:45 InstallMSSearch instance: MSSQLSERVER
> 15:50:45 Software\Microsoft\Search\Install:Version : 9.107.5512
> 15:50:45 MSSearch 2.0 or greater version check returned 1
> 15:50:45 Setup is installing the Microsoft Full-Text Search Engine ...
> 15:50:45 "F:\MS_sql2k\X86\FullText\MSSearch\Search\SearchStp.exe" /s
> /a:SQLServer
> 15:50:48 Process Exit Code: (0)
> 15:50:48 /Q:A /T:C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\ixp001.tmp
> 15:50:48 Setup is installing HTML Help ...
> 15:50:48 HTML Help installer exit code: 0
> 15:51:10 End Action InstallPkgs
> 15:51:10 Begin Action MoveFileData:
> 15:51:10 Enabled SELFREGISTERBATCH
> 15:51:10 Enabled CORECOMPONENTHANDLING
> 15:51:34 Begin Action: MoveFileDataSpecial
> 15:51:35 End Action: MoveFileDataSpecial
> 15:51:35 End Action MoveFileData
> 15:51:35 Begin Action ProcessAfterDataMove:
> 15:51:35 F:\MS_sql2k\X86\Binn\hhcol.exe C:\Program Files (x86)\Microsoft
SQL
> Server\80\Tools\Books
> 15:51:35 End Action ProcessAfterDataMove
> 15:51:35 Begin Action BuildServer:
> 15:51:36 C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\SqlSetup\Bin\scm.exe -Silent
1
> -Action 5 -ExePath "C:\Program Files (x86)\Microsoft SQL
> Server\MSSQL\binn\sqlservr.exe" -Service "MSSQLSERVER"
> 15:51:36 Process Exit Code: (0)
> 15:51:36 Begin Action: CreateRegistrySetSQL
> 15:51:36 End Action: CreateRegistrySetSQL
> 15:51:36 Begin Action: RegWriteSetupEntry
> 15:51:36 End Action: RegWriteSetupEntry
> 15:51:36 Begin Action: CreateSer
> 15:51:36 End Action: CreateSer
> 15:51:36 Begin Action: SkuIt
> 15:51:36 End Action: SkuIt
> 15:51:36 SetFileSecuritySQLAndAdmin for C:\Program Files (x86)\Microsoft
SQL
> Server\MSSQL returned: 0, 0
> 15:51:36 SetRegSecuritySQLAndAdmin for
> Software\Microsoft\MSSQLServer\MSSQLServer returned: 0, 0
> 15:51:36 Begin Action: UpdateSystemPath
> 15:51:36 Path successfully updated.
> 15:51:36 C:\Program Files\Support
>
Tools\;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;C:\Prog
ram Files (x86)\Microsoft SQL Server\80\Tools\BINN
> 15:51:36 End Action: UpdateSystemPath
> 15:51:37 C:\Program Files (x86)\Microsoft SQL
> Server\80\Tools\Binn\cnfgsvr.exe -F "C:\WINDOWS\sqlstp.log" -I
MSSQLSERVER
> -V 1 -M 0 -Q "SQL_Latin1_General_CP1_CI_AS" -H 131446 -U sa -P
>
############################################################################
###
>
> Starting Service ...
> SQL_Latin1_General_CP1_CI_AS
> -m -Q -T4022 -T3659
> ---
>
> "Mike Epprecht (SQL MVP)" wrote:
> > Hi
> >
> > Yes, one just has to be a named instance, not listening on port 1433.
> >
> > Regards
> > --
> > Mike Epprecht, Microsoft SQL Server MVP
> > Zurich, Switzerland
> >
> > IM: mike@.epprecht.net
> >
> > MVP Program: http://www.microsoft.com/mvp
> >
> > Blog: http://www.msmvps.com/epprecht/
> >
> > "Arvi" <Arvi@.discussions.microsoft.com> wrote in message
> > news:A8C80E5D-DDAC-4219-9383-712651A275EE@.microsoft.com...
> > > Hi,
> > > Can MSDE and SQl server 2000 standard edition co-exist.
> > >
> > > Arvind.
> >
> >
> >

Can they co-exist ?

Hi,
Can MSDE and SQl server 2000 standard edition co-exist.
Arvind.
Hi
Yes, one just has to be a named instance, not listening on port 1433.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Arvi" <Arvi@.discussions.microsoft.com> wrote in message
news:A8C80E5D-DDAC-4219-9383-712651A275EE@.microsoft.com...
> Hi,
> Can MSDE and SQl server 2000 standard edition co-exist.
> Arvind.
|||Yes.
Please post DDL, sample data and desired results.
See http://www.aspfaq.com/5006 for info.
"Arvi" <Arvi@.discussions.microsoft.com> wrote in message
news:A8C80E5D-DDAC-4219-9383-712651A275EE@.microsoft.com...
> Hi,
> Can MSDE and SQl server 2000 standard edition co-exist.
> Arvind.
|||Hi Mike and Aaron,
Thanks for your reply, in that case why would the installation of SQl
server 2000 std edition on Win 2K3 64 bit server not complete, it just hangs
at the point
"Setup is configuring your selected options " and it never completes the
installation.
No matter what uninstalling previous editions of SQL server or MSDE nothing
helps.
This is waht the end of log file reads like:
15:50:34 Monarch
15:50:34 Monarch\Monr1033
15:50:34 Monarch\MonrIntl
15:50:34 Jet
15:50:34 CoreInst
15:50:34 CoreCOM
15:50:34 CoreCOM\Res1033
15:50:34 CoreCOM\ResIntl
15:50:34 CoreTool
15:50:34 CoreTool\Res1033
15:50:34 CoreTool\ResOther
15:50:34 DBLibCli
15:50:34 SFExt
15:50:34 SFExt\ActiveX
15:50:34 SFExt\ActiveX\Res1033
15:50:34 SFExt\ActiveX\ResIntl
15:50:34 SFExt\Res1033
15:50:34 SFExt\ResIntl
15:50:34 Trace
15:50:34 Trace\Res1033
15:50:34 Trace\ResOther
15:50:34 MiscCore
15:50:34 MC
15:50:34 MC\MC1033
15:50:34 MC\MCIntl
15:50:34 MC\Help
15:50:34 SQLMgr
15:50:34 SQLMgr\Res1033
15:50:34 SQLMgr\ResIntl
15:50:34 SvrTool
15:50:34 SvrTool\Res1033
15:50:34 SvrTool\ResIntl
15:50:34 DTSUI
15:50:34 DTSUI\Res1033
15:50:34 DTSUI\ResIntl
15:50:34 MSOlap
15:50:34 MSOlap\Res1033
15:50:34 MSOlap\ResIntl
15:50:34 ATL
15:50:34 ATL\winnt
15:50:34 ATL\win9x
15:50:34 MFC42U
15:50:34 VC
15:50:35 VB
15:50:35 OCX1
15:50:35 SQLAdHlp
15:50:35 SQLAdHlp\Res1033
15:50:35 SQLAdHlp\ResOther
15:50:35 {E07FDDBE-5A21-11d2-9DAD-00C04F79D434}
15:50:35 {E07FDDC7-5A21-11d2-9DAD-00C04F79D434}
15:50:35 {E07FDDC0-5A21-11d2-9DAD-00C04F79D434}
15:50:35 {E07FDDBF-5A21-11d2-9DAD-00C04F79D434}
15:50:35 End Action LogSelectedComponents
15:50:35 Begin Action InstallPkgs:
15:50:35 Begin Action: Locked Connectivity Files Check
15:50:35 ConnectivityLocked returned: 0
15:50:35 The operation completed successfully.
15:50:35 End Action: Locked Connectivity Files Check
15:50:35 Setup is installing Microsoft Data Access Components (MDAC) ...
15:50:35 F:\MS_sql2k\X86\Other\sqlredis.exe /q:a /C:"setupre.exe WARN=1 -s
-SMS"
15:50:45 ExitCode: 0
15:50:45 Setup is installing Microsoft Distributed Transaction Coordinator
(MSDTC) ...
15:50:45 C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\SqlSetup\Bin\cl dtcstp.exe
-SupportDir "C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\SqlSetup\B in" -DTCPkg
"F:\MS_sql2k\X86\Other\dtcsetup.exe" -LogFile "C:\WINDOWS\sqlstp.log"
15:50:45 Process Exit Code: (0)
15:50:45 InstallMSSearch instance: MSSQLSERVER
15:50:45 Software\Microsoft\Search\Install:Version : 9.107.5512
15:50:45 MSSearch 2.0 or greater version check returned 1
15:50:45 Setup is installing the Microsoft Full-Text Search Engine ...
15:50:45 "F:\MS_sql2k\X86\FullText\MSSearch\Search\SearchSt p.exe" /s
/a:SQLServer
15:50:48 Process Exit Code: (0)
15:50:48 /Q:A /T:C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\ixp001.tmp
15:50:48 Setup is installing HTML Help ...
15:50:48 HTML Help installer exit code: 0
15:51:10 End Action InstallPkgs
15:51:10 Begin Action MoveFileData:
15:51:10 Enabled SELFREGISTERBATCH
15:51:10 Enabled CORECOMPONENTHANDLING
15:51:34 Begin Action: MoveFileDataSpecial
15:51:35 End Action: MoveFileDataSpecial
15:51:35 End Action MoveFileData
15:51:35 Begin Action ProcessAfterDataMove:
15:51:35 F:\MS_sql2k\X86\Binn\hhcol.exe C:\Program Files (x86)\Microsoft SQL
Server\80\Tools\Books
15:51:35 End Action ProcessAfterDataMove
15:51:35 Begin Action BuildServer:
15:51:36 C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\SqlSetup\Bin\sc m.exe -Silent 1
-Action 5 -ExePath "C:\Program Files (x86)\Microsoft SQL
Server\MSSQL\binn\sqlservr.exe" -Service "MSSQLSERVER"
15:51:36 Process Exit Code: (0)
15:51:36 Begin Action: CreateRegistrySetSQL
15:51:36 End Action: CreateRegistrySetSQL
15:51:36 Begin Action: RegWriteSetupEntry
15:51:36 End Action: RegWriteSetupEntry
15:51:36 Begin Action: CreateSer
15:51:36 End Action: CreateSer
15:51:36 Begin Action: SkuIt
15:51:36 End Action: SkuIt
15:51:36 SetFileSecuritySQLAndAdmin for C:\Program Files (x86)\Microsoft SQL
Server\MSSQL returned: 0, 0
15:51:36 SetRegSecuritySQLAndAdmin for
Software\Microsoft\MSSQLServer\MSSQLServer returned: 0, 0
15:51:36 Begin Action: UpdateSystemPath
15:51:36 Path successfully updated.
15:51:36 C:\Program Files\Support
Tools\;%SystemRoot%\system32;%SystemRoot%;%SystemR oot%\System32\Wbem;C:\Program Files (x86)\Microsoft SQL Server\80\Tools\BINN
15:51:36 End Action: UpdateSystemPath
15:51:37 C:\Program Files (x86)\Microsoft SQL
Server\80\Tools\Binn\cnfgsvr.exe -F "C:\WINDOWS\sqlstp.log" -I MSSQLSERVER
-V 1 -M 0 -Q "SQL_Latin1_General_CP1_CI_AS" -H 131446 -U sa -P
################################################## #############################
Starting Service ...
SQL_Latin1_General_CP1_CI_AS
-m -Q -T4022 -T3659
"Mike Epprecht (SQL MVP)" wrote:

> Hi
> Yes, one just has to be a named instance, not listening on port 1433.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Arvi" <Arvi@.discussions.microsoft.com> wrote in message
> news:A8C80E5D-DDAC-4219-9383-712651A275EE@.microsoft.com...
>
>
|||Hi
AFAIK, SQL Server 2000 with SP4 is compatible with X64, earlier versions are
not. SP4 is in beta.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Arvi" <Arvi@.discussions.microsoft.com> wrote in message
news:1D6E61ED-713D-4E50-8210-C0696C82AB2A@.microsoft.com...
> Hi Mike and Aaron,
> Thanks for your reply, in that case why would the installation of SQl
> server 2000 std edition on Win 2K3 64 bit server not complete, it just
hangs
> at the point
> "Setup is configuring your selected options " and it never completes the
> installation.
> No matter what uninstalling previous editions of SQL server or MSDE
nothing
> helps.
> This is waht the end of log file reads like:
> --
> 15:50:34 Monarch
> 15:50:34 Monarch\Monr1033
> 15:50:34 Monarch\MonrIntl
> 15:50:34 Jet
> 15:50:34 CoreInst
> 15:50:34 CoreCOM
> 15:50:34 CoreCOM\Res1033
> 15:50:34 CoreCOM\ResIntl
> 15:50:34 CoreTool
> 15:50:34 CoreTool\Res1033
> 15:50:34 CoreTool\ResOther
> 15:50:34 DBLibCli
> 15:50:34 SFExt
> 15:50:34 SFExt\ActiveX
> 15:50:34 SFExt\ActiveX\Res1033
> 15:50:34 SFExt\ActiveX\ResIntl
> 15:50:34 SFExt\Res1033
> 15:50:34 SFExt\ResIntl
> 15:50:34 Trace
> 15:50:34 Trace\Res1033
> 15:50:34 Trace\ResOther
> 15:50:34 MiscCore
> 15:50:34 MC
> 15:50:34 MC\MC1033
> 15:50:34 MC\MCIntl
> 15:50:34 MC\Help
> 15:50:34 SQLMgr
> 15:50:34 SQLMgr\Res1033
> 15:50:34 SQLMgr\ResIntl
> 15:50:34 SvrTool
> 15:50:34 SvrTool\Res1033
> 15:50:34 SvrTool\ResIntl
> 15:50:34 DTSUI
> 15:50:34 DTSUI\Res1033
> 15:50:34 DTSUI\ResIntl
> 15:50:34 MSOlap
> 15:50:34 MSOlap\Res1033
> 15:50:34 MSOlap\ResIntl
> 15:50:34 ATL
> 15:50:34 ATL\winnt
> 15:50:34 ATL\win9x
> 15:50:34 MFC42U
> 15:50:34 VC
> 15:50:35 VB
> 15:50:35 OCX1
> 15:50:35 SQLAdHlp
> 15:50:35 SQLAdHlp\Res1033
> 15:50:35 SQLAdHlp\ResOther
> 15:50:35 {E07FDDBE-5A21-11d2-9DAD-00C04F79D434}
> 15:50:35 {E07FDDC7-5A21-11d2-9DAD-00C04F79D434}
> 15:50:35 {E07FDDC0-5A21-11d2-9DAD-00C04F79D434}
> 15:50:35 {E07FDDBF-5A21-11d2-9DAD-00C04F79D434}
> 15:50:35 End Action LogSelectedComponents
> 15:50:35 Begin Action InstallPkgs:
> 15:50:35 Begin Action: Locked Connectivity Files Check
> 15:50:35 ConnectivityLocked returned: 0
> 15:50:35 The operation completed successfully.
> 15:50:35 End Action: Locked Connectivity Files Check
> 15:50:35 Setup is installing Microsoft Data Access Components (MDAC) ...
> 15:50:35 F:\MS_sql2k\X86\Other\sqlredis.exe /q:a /C:"setupre.exe WARN=1 -s
> -SMS"
> 15:50:45 ExitCode: 0
> 15:50:45 Setup is installing Microsoft Distributed Transaction Coordinator
> (MSDTC) ...
> 15:50:45 C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\SqlSetup\Bin\cl dtcstp.exe
> -SupportDir "C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\SqlSetup\B in" -DTCPkg
> "F:\MS_sql2k\X86\Other\dtcsetup.exe" -LogFile "C:\WINDOWS\sqlstp.log"
> 15:50:45 Process Exit Code: (0)
> 15:50:45 InstallMSSearch instance: MSSQLSERVER
> 15:50:45 Software\Microsoft\Search\Install:Version : 9.107.5512
> 15:50:45 MSSearch 2.0 or greater version check returned 1
> 15:50:45 Setup is installing the Microsoft Full-Text Search Engine ...
> 15:50:45 "F:\MS_sql2k\X86\FullText\MSSearch\Search\SearchSt p.exe" /s
> /a:SQLServer
> 15:50:48 Process Exit Code: (0)
> 15:50:48 /Q:A /T:C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\ixp001.tmp
> 15:50:48 Setup is installing HTML Help ...
> 15:50:48 HTML Help installer exit code: 0
> 15:51:10 End Action InstallPkgs
> 15:51:10 Begin Action MoveFileData:
> 15:51:10 Enabled SELFREGISTERBATCH
> 15:51:10 Enabled CORECOMPONENTHANDLING
> 15:51:34 Begin Action: MoveFileDataSpecial
> 15:51:35 End Action: MoveFileDataSpecial
> 15:51:35 End Action MoveFileData
> 15:51:35 Begin Action ProcessAfterDataMove:
> 15:51:35 F:\MS_sql2k\X86\Binn\hhcol.exe C:\Program Files (x86)\Microsoft
SQL
> Server\80\Tools\Books
> 15:51:35 End Action ProcessAfterDataMove
> 15:51:35 Begin Action BuildServer:
> 15:51:36 C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\SqlSetup\Bin\sc m.exe -Silent
1
> -Action 5 -ExePath "C:\Program Files (x86)\Microsoft SQL
> Server\MSSQL\binn\sqlservr.exe" -Service "MSSQLSERVER"
> 15:51:36 Process Exit Code: (0)
> 15:51:36 Begin Action: CreateRegistrySetSQL
> 15:51:36 End Action: CreateRegistrySetSQL
> 15:51:36 Begin Action: RegWriteSetupEntry
> 15:51:36 End Action: RegWriteSetupEntry
> 15:51:36 Begin Action: CreateSer
> 15:51:36 End Action: CreateSer
> 15:51:36 Begin Action: SkuIt
> 15:51:36 End Action: SkuIt
> 15:51:36 SetFileSecuritySQLAndAdmin for C:\Program Files (x86)\Microsoft
SQL
> Server\MSSQL returned: 0, 0
> 15:51:36 SetRegSecuritySQLAndAdmin for
> Software\Microsoft\MSSQLServer\MSSQLServer returned: 0, 0
> 15:51:36 Begin Action: UpdateSystemPath
> 15:51:36 Path successfully updated.
> 15:51:36 C:\Program Files\Support
>
Tools\;%SystemRoot%\system32;%SystemRoot%;%SystemR oot%\System32\Wbem;C:\Prog
ram Files (x86)\Microsoft SQL Server\80\Tools\BINN
> 15:51:36 End Action: UpdateSystemPath
> 15:51:37 C:\Program Files (x86)\Microsoft SQL
> Server\80\Tools\Binn\cnfgsvr.exe -F "C:\WINDOWS\sqlstp.log" -I
MSSQLSERVER
> -V 1 -M 0 -Q "SQL_Latin1_General_CP1_CI_AS" -H 131446 -U sa -P
>
################################################## ##########################
###[vbcol=seagreen]
>
> Starting Service ...
> SQL_Latin1_General_CP1_CI_AS
> -m -Q -T4022 -T3659
>
> "Mike Epprecht (SQL MVP)" wrote:

Can they co-exist ?

Hi,
Can MSDE and SQl server 2000 standard edition co-exist.
Arvind.Hi
Yes, one just has to be a named instance, not listening on port 1433.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Arvi" <Arvi@.discussions.microsoft.com> wrote in message
news:A8C80E5D-DDAC-4219-9383-712651A275EE@.microsoft.com...
> Hi,
> Can MSDE and SQl server 2000 standard edition co-exist.
> Arvind.|||Yes.
Please post DDL, sample data and desired results.
See http://www.aspfaq.com/5006 for info.
"Arvi" <Arvi@.discussions.microsoft.com> wrote in message
news:A8C80E5D-DDAC-4219-9383-712651A275EE@.microsoft.com...
> Hi,
> Can MSDE and SQl server 2000 standard edition co-exist.
> Arvind.|||Hi Mike and Aaron,
Thanks for your reply, in that case why would the installation of SQl
server 2000 std edition on Win 2K3 64 bit server not complete, it just hangs
at the point
"Setup is configuring your selected options " and it never completes the
installation.
No matter what uninstalling previous editions of SQL server or MSDE nothing
helps.
This is waht the end of log file reads like:
15:50:34 Monarch
15:50:34 Monarch\Monr1033
15:50:34 Monarch\MonrIntl
15:50:34 Jet
15:50:34 CoreInst
15:50:34 CoreCOM
15:50:34 CoreCOM\Res1033
15:50:34 CoreCOM\ResIntl
15:50:34 CoreTool
15:50:34 CoreTool\Res1033
15:50:34 CoreTool\ResOther
15:50:34 DBLibCli
15:50:34 SFExt
15:50:34 SFExt\ActiveX
15:50:34 SFExt\ActiveX\Res1033
15:50:34 SFExt\ActiveX\ResIntl
15:50:34 SFExt\Res1033
15:50:34 SFExt\ResIntl
15:50:34 Trace
15:50:34 Trace\Res1033
15:50:34 Trace\ResOther
15:50:34 MiscCore
15:50:34 MC
15:50:34 MC\MC1033
15:50:34 MC\MCIntl
15:50:34 MC\Help
15:50:34 SQLMgr
15:50:34 SQLMgr\Res1033
15:50:34 SQLMgr\ResIntl
15:50:34 SvrTool
15:50:34 SvrTool\Res1033
15:50:34 SvrTool\ResIntl
15:50:34 DTSUI
15:50:34 DTSUI\Res1033
15:50:34 DTSUI\ResIntl
15:50:34 MSOlap
15:50:34 MSOlap\Res1033
15:50:34 MSOlap\ResIntl
15:50:34 ATL
15:50:34 ATL\winnt
15:50:34 ATL\win9x
15:50:34 MFC42U
15:50:34 VC
15:50:35 VB
15:50:35 OCX1
15:50:35 SQLAdHlp
15:50:35 SQLAdHlp\Res1033
15:50:35 SQLAdHlp\ResOther
15:50:35 {E07FDDBE-5A21-11d2-9DAD-00C04F79D434}
15:50:35 {E07FDDC7-5A21-11d2-9DAD-00C04F79D434}
15:50:35 {E07FDDC0-5A21-11d2-9DAD-00C04F79D434}
15:50:35 {E07FDDBF-5A21-11d2-9DAD-00C04F79D434}
15:50:35 End Action LogSelectedComponents
15:50:35 Begin Action InstallPkgs:
15:50:35 Begin Action: Locked Connectivity Files Check
15:50:35 ConnectivityLocked returned: 0
15:50:35 The operation completed successfully.
15:50:35 End Action: Locked Connectivity Files Check
15:50:35 Setup is installing Microsoft Data Access Components (MDAC) ...
15:50:35 F:\MS_sql2k\X86\Other\sqlredis.exe /q:a /C:"setupre.exe WARN=1 -s
-SMS"
15:50:45 ExitCode: 0
15:50:45 Setup is installing Microsoft Distributed Transaction Coordinator
(MSDTC) ...
15:50:45 C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\SqlSe
tup\Bin\cldtcstp.exe
-SupportDir " C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\SqlSe
tup\Bin" -DTCPkg
"F:\MS_sql2k\X86\Other\dtcsetup.exe" -LogFile "C:\WINDOWS\sqlstp.log"
15:50:45 Process Exit Code: (0)
15:50:45 InstallMSSearch instance: MSSQLSERVER
15:50:45 Software\Microsoft\Search\Install:Versio
n : 9.107.5512
15:50:45 MSSearch 2.0 or greater version check returned 1
15:50:45 Setup is installing the Microsoft Full-Text Search Engine ...
15:50:45 " F:\MS_sql2k\X86\FullText\MSSearch\Search
\SearchStp.exe" /s
/a:SQLServer
15:50:48 Process Exit Code: (0)
15:50:48 /Q:A / T:C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\ixp
001.tmp
15:50:48 Setup is installing HTML Help ...
15:50:48 HTML Help installer exit code: 0
15:51:10 End Action InstallPkgs
15:51:10 Begin Action MoveFileData:
15:51:10 Enabled SELFREGISTERBATCH
15:51:10 Enabled CORECOMPONENTHANDLING
15:51:34 Begin Action: MoveFileDataSpecial
15:51:35 End Action: MoveFileDataSpecial
15:51:35 End Action MoveFileData
15:51:35 Begin Action ProcessAfterDataMove:
15:51:35 F:\MS_sql2k\X86\Binn\hhcol.exe C:\Program Files (x86)\Microsoft SQL
Server\80\Tools\Books
15:51:35 End Action ProcessAfterDataMove
15:51:35 Begin Action BuildServer:
15:51:36 C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\SqlSe
tup\Bin\scm.exe -Silent 1
-Action 5 -ExePath "C:\Program Files (x86)\Microsoft SQL
Server\MSSQL\binn\sqlservr.exe" -Service "MSSQLSERVER"
15:51:36 Process Exit Code: (0)
15:51:36 Begin Action: CreateRegistrySetSQL
15:51:36 End Action: CreateRegistrySetSQL
15:51:36 Begin Action: RegWriteSetupEntry
15:51:36 End Action: RegWriteSetupEntry
15:51:36 Begin Action: CreateSer
15:51:36 End Action: CreateSer
15:51:36 Begin Action: SkuIt
15:51:36 End Action: SkuIt
15:51:36 SetFileSecuritySQLAndAdmin for C:\Program Files (x86)\Microsoft SQL
Server\MSSQL returned: 0, 0
15:51:36 SetRegSecuritySQLAndAdmin for
Software\Microsoft\MSSQLServer\MSSQLServ
er returned: 0, 0
15:51:36 Begin Action: UpdateSystemPath
15:51:36 Path successfully updated.
15:51:36 C:\Program Files\Support
Tools\;%SystemRoot%\system32;%SystemRoot
%;%SystemRoot%\System32\Wbem;C:\Prog
ram Files (x86)\Microsoft SQL Server\80\Tools\BINN
15:51:36 End Action: UpdateSystemPath
15:51:37 C:\Program Files (x86)\Microsoft SQL
Server\80\Tools\Binn\cnfgsvr.exe -F "C:\WINDOWS\sqlstp.log" -I MSSQLSERVER
-V 1 -M 0 -Q "SQL_Latin1_General_CP1_CI_AS" -H 131446 -U sa -P
########################################
####################################
###
Starting Service ...
SQL_Latin1_General_CP1_CI_AS
-m -Q -T4022 -T3659
---
"Mike Epprecht (SQL MVP)" wrote:

> Hi
> Yes, one just has to be a named instance, not listening on port 1433.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Arvi" <Arvi@.discussions.microsoft.com> wrote in message
> news:A8C80E5D-DDAC-4219-9383-712651A275EE@.microsoft.com...
>
>|||Hi
AFAIK, SQL Server 2000 with SP4 is compatible with X64, earlier versions are
not. SP4 is in beta.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Arvi" <Arvi@.discussions.microsoft.com> wrote in message
news:1D6E61ED-713D-4E50-8210-C0696C82AB2A@.microsoft.com...
> Hi Mike and Aaron,
> Thanks for your reply, in that case why would the installation of SQl
> server 2000 std edition on Win 2K3 64 bit server not complete, it just
hangs
> at the point
> "Setup is configuring your selected options " and it never completes the
> installation.
> No matter what uninstalling previous editions of SQL server or MSDE
nothing
> helps.
> This is waht the end of log file reads like:
> --
> 15:50:34 Monarch
> 15:50:34 Monarch\Monr1033
> 15:50:34 Monarch\MonrIntl
> 15:50:34 Jet
> 15:50:34 CoreInst
> 15:50:34 CoreCOM
> 15:50:34 CoreCOM\Res1033
> 15:50:34 CoreCOM\ResIntl
> 15:50:34 CoreTool
> 15:50:34 CoreTool\Res1033
> 15:50:34 CoreTool\ResOther
> 15:50:34 DBLibCli
> 15:50:34 SFExt
> 15:50:34 SFExt\ActiveX
> 15:50:34 SFExt\ActiveX\Res1033
> 15:50:34 SFExt\ActiveX\ResIntl
> 15:50:34 SFExt\Res1033
> 15:50:34 SFExt\ResIntl
> 15:50:34 Trace
> 15:50:34 Trace\Res1033
> 15:50:34 Trace\ResOther
> 15:50:34 MiscCore
> 15:50:34 MC
> 15:50:34 MC\MC1033
> 15:50:34 MC\MCIntl
> 15:50:34 MC\Help
> 15:50:34 SQLMgr
> 15:50:34 SQLMgr\Res1033
> 15:50:34 SQLMgr\ResIntl
> 15:50:34 SvrTool
> 15:50:34 SvrTool\Res1033
> 15:50:34 SvrTool\ResIntl
> 15:50:34 DTSUI
> 15:50:34 DTSUI\Res1033
> 15:50:34 DTSUI\ResIntl
> 15:50:34 MSOlap
> 15:50:34 MSOlap\Res1033
> 15:50:34 MSOlap\ResIntl
> 15:50:34 ATL
> 15:50:34 ATL\winnt
> 15:50:34 ATL\win9x
> 15:50:34 MFC42U
> 15:50:34 VC
> 15:50:35 VB
> 15:50:35 OCX1
> 15:50:35 SQLAdHlp
> 15:50:35 SQLAdHlp\Res1033
> 15:50:35 SQLAdHlp\ResOther
> 15:50:35 {E07FDDBE-5A21-11d2-9DAD-00C04F79D434}
> 15:50:35 {E07FDDC7-5A21-11d2-9DAD-00C04F79D434}
> 15:50:35 {E07FDDC0-5A21-11d2-9DAD-00C04F79D434}
> 15:50:35 {E07FDDBF-5A21-11d2-9DAD-00C04F79D434}
> 15:50:35 End Action LogSelectedComponents
> 15:50:35 Begin Action InstallPkgs:
> 15:50:35 Begin Action: Locked Connectivity Files Check
> 15:50:35 ConnectivityLocked returned: 0
> 15:50:35 The operation completed successfully.
> 15:50:35 End Action: Locked Connectivity Files Check
> 15:50:35 Setup is installing Microsoft Data Access Components (MDAC) ...
> 15:50:35 F:\MS_sql2k\X86\Other\sqlredis.exe /q:a /C:"setupre.exe WARN=1 -s
> -SMS"
> 15:50:45 ExitCode: 0
> 15:50:45 Setup is installing Microsoft Distributed Transaction Coordinator
> (MSDTC) ...
> 15:50:45 C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\SqlSe
tup\Bin\cldtcstp.exe
> -SupportDir " C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\SqlSe
tup\Bin" -DTCPkg
> "F:\MS_sql2k\X86\Other\dtcsetup.exe" -LogFile "C:\WINDOWS\sqlstp.log"
> 15:50:45 Process Exit Code: (0)
> 15:50:45 InstallMSSearch instance: MSSQLSERVER
> 15:50:45 Software\Microsoft\Search\Install:Versio
n : 9.107.5512
> 15:50:45 MSSearch 2.0 or greater version check returned 1
> 15:50:45 Setup is installing the Microsoft Full-Text Search Engine ...
> 15:50:45 " F:\MS_sql2k\X86\FullText\MSSearch\Search
\SearchStp.exe" /s
> /a:SQLServer
> 15:50:48 Process Exit Code: (0)
> 15:50:48 /Q:A / T:C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\ixp
001.tmp
> 15:50:48 Setup is installing HTML Help ...
> 15:50:48 HTML Help installer exit code: 0
> 15:51:10 End Action InstallPkgs
> 15:51:10 Begin Action MoveFileData:
> 15:51:10 Enabled SELFREGISTERBATCH
> 15:51:10 Enabled CORECOMPONENTHANDLING
> 15:51:34 Begin Action: MoveFileDataSpecial
> 15:51:35 End Action: MoveFileDataSpecial
> 15:51:35 End Action MoveFileData
> 15:51:35 Begin Action ProcessAfterDataMove:
> 15:51:35 F:\MS_sql2k\X86\Binn\hhcol.exe C:\Program Files (x86)\Microsoft
SQL
> Server\80\Tools\Books
> 15:51:35 End Action ProcessAfterDataMove
> 15:51:35 Begin Action BuildServer:
> 15:51:36 C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\SqlSe
tup\Bin\scm.exe -Silent
1
> -Action 5 -ExePath "C:\Program Files (x86)\Microsoft SQL
> Server\MSSQL\binn\sqlservr.exe" -Service "MSSQLSERVER"
> 15:51:36 Process Exit Code: (0)
> 15:51:36 Begin Action: CreateRegistrySetSQL
> 15:51:36 End Action: CreateRegistrySetSQL
> 15:51:36 Begin Action: RegWriteSetupEntry
> 15:51:36 End Action: RegWriteSetupEntry
> 15:51:36 Begin Action: CreateSer
> 15:51:36 End Action: CreateSer
> 15:51:36 Begin Action: SkuIt
> 15:51:36 End Action: SkuIt
> 15:51:36 SetFileSecuritySQLAndAdmin for C:\Program Files (x86)\Microsoft
SQL
> Server\MSSQL returned: 0, 0
> 15:51:36 SetRegSecuritySQLAndAdmin for
> Software\Microsoft\MSSQLServer\MSSQLServ
er returned: 0, 0
> 15:51:36 Begin Action: UpdateSystemPath
> 15:51:36 Path successfully updated.
> 15:51:36 C:\Program Files\Support
>
Tools\;%SystemRoot%\system32;%SystemRoot
%;%SystemRoot%\System32\Wbem;C:\Prog
ram Files (x86)\Microsoft SQL Server\80\Tools\BINN
> 15:51:36 End Action: UpdateSystemPath
> 15:51:37 C:\Program Files (x86)\Microsoft SQL
> Server\80\Tools\Binn\cnfgsvr.exe -F "C:\WINDOWS\sqlstp.log" -I
MSSQLSERVER
> -V 1 -M 0 -Q "SQL_Latin1_General_CP1_CI_AS" -H 131446 -U sa -P
>
########################################
####################################
###[vbcol=seagreen]
>
> Starting Service ...
> SQL_Latin1_General_CP1_CI_AS
> -m -Q -T4022 -T3659
> ---
>
> "Mike Epprecht (SQL MVP)" wrote:
>

Can the JDBC Driver provided by Microsoft connect MSDE?

I plan to use MSDE because it sues my needs, but doese the
JDBC provided by MS connect to MSDE?
Yes, you can connect to an MSDE instance. You will have to specify the
instance name using the <servername>\<instancename> syntax in your
connection URL.
Carb Simien, MCSE MCDBA MCAD
Microsoft Developer Support - Web Data
Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection
Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/security.
"Benny" <BennyInCanada2883@.hotmail.com> wrote in message
news:13cfc01c412b1$60b8ed60$a101280a@.phx.gbl...
> I plan to use MSDE because it sues my needs, but doese the
> JDBC provided by MS connect to MSDE?

Can start new database from Web Matrix

I am running Web Matrix version 0.5, .Net version 1.1 on a computer with XP Pro.

Web Matrix works fine and returns forms properly.

I installed MSDE from the website (SQL2KDeskSP3a.exe) Ibelieve that SQL Server IS running, because I see the tower icon with agreen arrow; when I double-click that I get a message that it isrunning SQL Server.

When I click the "data" tab in Web Matrix I get the blankworkspace. Then I click the New Connection icon at the top left,which opens up a dialog box. I change "Windows Authentication" to"SQL Authentication." That opens up the Username/Passwordprompt. I am entering "sa" for the username (I AM NOT SURE IFTHAT IS CORRECT) and "**secret**" for the password (that's what Ientered in the command prompt when I setup the MSDE). Then Iclick "Create a New Database." I am asked to enter a name.

After a pause, I get an error message: "Unable to connect tothe database server. SQL Server does not exist or access denied.Connection Open (Connect ( )). OK

Do you have any ideas?

I installed the newer (version 0.6) Matrix and now I can find the database.

Can SQL Server 7.0 handle a SQL Server 2000 mdf?

I've got MSDE, SQL Server 7.0, installed. I want to handle an .mdf
developed by someone else so I loaded the .mdf into my /DATA folder.
But, MSDE/ODBC can't see the database. I subsequently discovered that
it was created using SQL Server 2000. Is this the reason that my MSDE
7.0 doesn't see the .mdf? If so, how can I use this database with my
7.0? Backup from 2000, restore to 7.0?

Thanks for any help.Mike Watson (mike@.connectingsoftware.it) writes:
> I've got MSDE, SQL Server 7.0, installed. I want to handle an .mdf
> developed by someone else so I loaded the .mdf into my /DATA folder.
> But, MSDE/ODBC can't see the database. I subsequently discovered that
> it was created using SQL Server 2000. Is this the reason that my MSDE
> 7.0 doesn't see the .mdf? If so, how can I use this database with my
> 7.0? Backup from 2000, restore to 7.0?

Well, there's actually two problems here.

The fact that MSDE/ODBC can't see the database has nothing to do with
the versions of SQL Server. Putting a file into your data directory has
no effect. You would have to do sp_attach_db to make the database available.
And for sp_attach_db the .mdf is not sufficient; you would need the log
file too. There is sp_attach_single_file_db for this situation, but the
database must have been shut down cleanly for this. (Well, this applies
to sp_attach_db as well as I recall.)

But for all this to work, the target server must be the same version or
later than the source server, so you can never do anything with that file
without access to SQL 2000. To restore that database on SQL 7, you would
have to script it and bulk out all data. And if the database makes use
of features not in SQL 7, not even this method would work.

Since MSDE for SQL 2000 is freely available, it appears to be a good idea
to download and install it.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||Erland Sommarskog <esquel@.sommarskog.se> wrote in message news:<Xns9619844A49F0FYazorman@.127.0.0.1>...
> Mike Watson (mike@.connectingsoftware.it) writes:
> > I've got MSDE, SQL Server 7.0, installed. I want to handle an .mdf
> > developed by someone else so I loaded the .mdf into my /DATA folder.
> > But, MSDE/ODBC can't see the database. I subsequently discovered that
> > it was created using SQL Server 2000. Is this the reason that my MSDE
> > 7.0 doesn't see the .mdf? If so, how can I use this database with my
> > 7.0? Backup from 2000, restore to 7.0?
> Well, there's actually two problems here.
> The fact that MSDE/ODBC can't see the database has nothing to do with
> the versions of SQL Server. Putting a file into your data directory has
> no effect. You would have to do sp_attach_db to make the database available.
> And for sp_attach_db the .mdf is not sufficient; you would need the log
> file too. There is sp_attach_single_file_db for this situation, but the
> database must have been shut down cleanly for this. (Well, this applies
> to sp_attach_db as well as I recall.)
> But for all this to work, the target server must be the same version or
> later than the source server, so you can never do anything with that file
> without access to SQL 2000. To restore that database on SQL 7, you would
> have to script it and bulk out all data. And if the database makes use
> of features not in SQL 7, not even this method would work.
> Since MSDE for SQL 2000 is freely available, it appears to be a good idea
> to download and install it.

Thank you Erland, for your answer. We've got the log file. So,
following your advice I will look for and install MSDE 2000. After
that I presume I have to run the 'sp_attach_db' procedure to make the
db available to MSDE 2000 so that I can create an ODBC to see it from
Access 2000. Could you please confirm if that is correct?

Mike Watson|||Mike Watson (mike@.connectingsoftware.it) writes:
> Thank you Erland, for your answer. We've got the log file. So,
> following your advice I will look for and install MSDE 2000. After
> that I presume I have to run the 'sp_attach_db' procedure to make the
> db available to MSDE 2000 so that I can create an ODBC to see it from
> Access 2000. Could you please confirm if that is correct?

That should work just fine.

Once you have MSDE 2000 up, do a SELECT @.@.version, and make sure that
you have at least 8.00.760, so you have SP3 and the fix for the Slammer
worm.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||Erland Sommarskog <esquel@.sommarskog.se> wrote in message news:<Xns961AE57BC3805Yazorman@.127.0.0.1>...
> Mike Watson (mike@.connectingsoftware.it) writes:
> > Thank you Erland, for your answer. We've got the log file. So,
> > following your advice I will look for and install MSDE 2000. After
> > that I presume I have to run the 'sp_attach_db' procedure to make the
> > db available to MSDE 2000 so that I can create an ODBC to see it from
> > Access 2000. Could you please confirm if that is correct?
> That should work just fine.
> Once you have MSDE 2000 up, do a SELECT @.@.version, and make sure that
> you have at least 8.00.760, so you have SP3 and the fix for the Slammer
> worm.

Erland,

I've downloaded MSDE 2000 (Italian version), expanded the zip, read
the readme.txt, checked the things they tell me to check. I started
the setup with:

setup SAPWD="password" SECURITYMODE=SQL

The install fails with roughly 3 - 5 seconds remaining with following
message:

"Impossible to configure the Server. For further information examine
the error logs..."

The last 2 messages in the log are:

Warning: override, autoexec procedures skipped.

and

Closing down SQL Server because of a interruption request from the
Service control handler (my translation)

I can't see what's going wrong. Can you help me?

Mike Watson|||Mike Watson (mike@.connectingsoftware.it) writes:
> I've downloaded MSDE 2000 (Italian version), expanded the zip, read
> the readme.txt, checked the things they tell me to check. I started
> the setup with:
> setup SAPWD="password" SECURITYMODE=SQL
> The install fails with roughly 3 - 5 seconds remaining with following
> message:
> "Impossible to configure the Server. For further information examine
> the error logs..."
> The last 2 messages in the log are:
> Warning: override, autoexec procedures skipped.
> and
> Closing down SQL Server because of a interruption request from the
> Service control handler (my translation)
> I can't see what's going wrong. Can you help me?

Unfortunately, I have no experience of running the MSDE setup, so
there is not much I can assist with.

Do you run the setup on the machine where you already have MSDE 7, or
do you run it on some other machine?

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||Erland Sommarskog <esquel@.sommarskog.se> wrote in message news:<Xns961BF3EFC447BYazorman@.127.0.0.1>...
> Mike Watson (mike@.connectingsoftware.it) writes:
> > I've downloaded MSDE 2000 (Italian version), expanded the zip, read
> > the readme.txt, checked the things they tell me to check. I started
> > the setup with:
> > setup SAPWD="password" SECURITYMODE=SQL
> > The install fails with roughly 3 - 5 seconds remaining with following
> > message:
> > "Impossible to configure the Server. For further information examine
> > the error logs..."
> > The last 2 messages in the log are:
> > Warning: override, autoexec procedures skipped.
> > and
> > Closing down SQL Server because of a interruption request from the
> > Service control handler (my translation)
> > I can't see what's going wrong. Can you help me?
> Unfortunately, I have no experience of running the MSDE setup, so
> there is not much I can assist with.
> Do you run the setup on the machine where you already have MSDE 7, or
> do you run it on some other machine?

Erland,

I'm doing the install on another machine where there is no previous
copy of SQL or MSDE. It's Windows XP.

Mike Watson|||Mike Watson (mike@.connectingsoftware.it) writes:
> I'm doing the install on another machine where there is no previous
> copy of SQL or MSDE. It's Windows XP.

Darn! Then I can't even suggest that as a remedy. I believe that there
is a newsgroup microsoft.public.sqlserver.msde.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp

Can SQL Server 2005 Express and MSDE CoExist?

I read in the installation requirements document for SQL Server 2005 Express the section on upgrading MSDE to SQL Server 2005 Express. The section indicated that if MSDE is installed via an application installation, that application will have to be uninstalled to remove MSDE. This leads to my question.

The small application I'm looking into developing will require SQL Server 2005 Express. What if a customer is using an application that installed MSDE? Can the two products coexist without problems?

Thanks!!

hi,

yes, MSDE 2000 and SQLExpress can coexists...

SQLExpress installation will upgrade the installed COM based binaries (SQL-DMO) to SQL Server 2005 level, but they have been tested to be retro-compatible and I'm personally not aware of troubles in this area..

regards

Can SQL Express 2005 & MSDE reside on the same box?

Is the installation of MSDE and SQL Express 2005 on the same computer a supported configuration?

Many thanks

Yes, you can run Express and MSDE/WMSDE in the same machine using different instance names.

Can SQL 2000 and WID coexist

My question is can the new version of MSDE (Windows Internal Database or SQL Express) reside on the server along with SQL 2000 without causing problems? We cannot upgrade the SQL 2000 because of an older application that doesn't work with SQL 2005. Currently we run WSUS 2.0 using MSDE and have no problems.

See replies to your similar post in the Getting Started with SQL Server forum.

Often, the quality of the responses received is related to our ability to ‘bounce’ ideas off of each other. In the future, to make it easier for us to offer you assistance, and to prevent folks from wasting time on already answered questions, please don't post to multiple newsgroups. Choose the one that best fits your question and post there. Only post to another newsgroup if you get no answer in a day or two (or if you accidentally posted to the wrong newsgroup –and you indicate that you've already posted elsewhere).

Can only log into a MSDE ODBC Connection as Administrator

When trying to log into a ODBC connection as a power user on a network we
receive the following error:
Connection failed:
SQLState:'01000'
SQL Server Error: 53
[Microsoft][ODBC SQL Server Driver][DBNET]ConnectionOpen (/cibbect ()),
Connection failed:
SQLState:'08001'
SQL server Error:178
[microsoft][odbc sql server driver][dbnetlib]sql server does not exist or
access denied.
Change the user to Administrator and they are able to login.
Did you add logins for other users who aren't members of the
local admin group on the box where MSDE is installed? It
sounds like they may not have logins setup in MSDE.
By default, members of the local admins group will have
access. For other users, you need to add logins.
-Sue
On Thu, 27 Oct 2005 19:25:02 -0700, "bw"
<bw@.discussions.microsoft.com> wrote:

>When trying to log into a ODBC connection as a power user on a network we
>receive the following error:
>Connection failed:
>SQLState:'01000'
>SQL Server Error: 53
>[Microsoft][ODBC SQL Server Driver][DBNET]ConnectionOpen (/cibbect ()),
>Connection failed:
>SQLState:'08001'
>SQL server Error:178
>[microsoft][odbc sql server driver][dbnetlib]sql server does not exist or
>access denied.
>Change the user to Administrator and they are able to login.
|||Sue,
Yes I did add them to the system as a user. Then created an MSDE Group.
The Group has the following rights:
GROUP EVERYONE - Read to Program Files
MSDE GROUP DOES NOT HAVE FULL CONTROL, NO DEL FOLDERS, TAKE OWNERSHIP,
CREATE FOLDER OR CHANGE PERMISSION TO THE MSDE/SYSTEM FOLDER OR MSDE/SERVER
FOLDER
USING A NOTEBOOK WITH ENTERPRISE MANAGER WE HAD GIVE THE MSDE GROUP -
PUBLIC, DB_WRITER, DB_READER AND DB_BACKUP OPERATOR
APPLIED SERVICE PACK 2 TO THE SYSTEM THAT IS RUNNING THE MSDE SERVICE AND
NOW THE SYSTEM RUNNING ENTERPRISE MANAGER GETS THE FOLLOWING ERROR WHEN
ATTEMPTING TO CONNECT TO THE SYSTEM MAP DRIVE THAT HAS THE MSDE INSTALLED WE
GET THE FOLLOWING ERROR:
AN ERROR OCCURRED WHILE RECONNECTING TO A LOCAL CONNECTION . MICROSOFT
WINDOWN NETWORK. THE LOCAL DEVICE NAME IS ALREADY IN USE.
CANNOT CONNECT THE ENTERPRISE MANAGER TO THE MSDE DATABASE NOW.
I APPRECIATE YOUR HELP.
"Sue Hoegemeier" wrote:

> Did you add logins for other users who aren't members of the
> local admin group on the box where MSDE is installed? It
> sounds like they may not have logins setup in MSDE.
> By default, members of the local admins group will have
> access. For other users, you need to add logins.
> -Sue
> On Thu, 27 Oct 2005 19:25:02 -0700, "bw"
> <bw@.discussions.microsoft.com> wrote:
>
>
|||No need to yell. Using caps is considered yelling in
newsgroups.
By adding the users as logins in SQL Server, that doesn't
have anything to do with adding them to groups on the box
where MSDE is running.
How exactly are you trying to connect? I think something is
missing here as mapping drives is not necessary, giving
users full control on MSDE folders, etc is generally not
necessary either.
-Sue
On Fri, 28 Oct 2005 15:13:03 -0700, "bw"
<bw@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Sue,
>Yes I did add them to the system as a user. Then created an MSDE Group.
>The Group has the following rights:
> GROUP EVERYONE - Read to Program Files
> MSDE GROUP DOES NOT HAVE FULL CONTROL, NO DEL FOLDERS, TAKE OWNERSHIP,
>CREATE FOLDER OR CHANGE PERMISSION TO THE MSDE/SYSTEM FOLDER OR MSDE/SERVER
>FOLDER
>USING A NOTEBOOK WITH ENTERPRISE MANAGER WE HAD GIVE THE MSDE GROUP -
>PUBLIC, DB_WRITER, DB_READER AND DB_BACKUP OPERATOR
>APPLIED SERVICE PACK 2 TO THE SYSTEM THAT IS RUNNING THE MSDE SERVICE AND
>NOW THE SYSTEM RUNNING ENTERPRISE MANAGER GETS THE FOLLOWING ERROR WHEN
>ATTEMPTING TO CONNECT TO THE SYSTEM MAP DRIVE THAT HAS THE MSDE INSTALLED WE
>GET THE FOLLOWING ERROR:
>AN ERROR OCCURRED WHILE RECONNECTING TO A LOCAL CONNECTION . MICROSOFT
>WINDOWN NETWORK. THE LOCAL DEVICE NAME IS ALREADY IN USE.
>CANNOT CONNECT THE ENTERPRISE MANAGER TO THE MSDE DATABASE NOW.
>I APPRECIATE YOUR HELP.
>
>"Sue Hoegemeier" wrote:
|||I apologize I did not know that caps were yelling, I am happy for the help.
Since we are testing this on our network, I am logging into our domain where
both systems reside. The MSDE is running on an XP workstation and we have
other workstations attempting to log into it. When we go into the ODBC setup
we can see the MSDE instance but cannot log on to it.
Bonnie
"Sue Hoegemeier" wrote:

> No need to yell. Using caps is considered yelling in
> newsgroups.
> By adding the users as logins in SQL Server, that doesn't
> have anything to do with adding them to groups on the box
> where MSDE is running.
> How exactly are you trying to connect? I think something is
> missing here as mapping drives is not necessary, giving
> users full control on MSDE folders, etc is generally not
> necessary either.
> -Sue
> On Fri, 28 Oct 2005 15:13:03 -0700, "bw"
> <bw@.discussions.microsoft.com> wrote:
>
>
|||No problem...figured you just didn't know about the caps
thing. Anyway, check the event logs on the XP workstation
where MSDE is running to see if there are any security
errors. Make sure the MSDE instance is listening on TCP/IP
and that the clients are configure to connect with TCP/IP.
You would probably want to start by running through the
following article - it's long but connectivity issues aren't
real easy to resolve as it can be so many different things.
Potential causes of the "SQL Server does not exist or access
denied" error message
http://support.microsoft.com/?id=328306
-Sue
On Mon, 31 Oct 2005 07:01:07 -0800, "bw"
<bw@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>I apologize I did not know that caps were yelling, I am happy for the help.
>Since we are testing this on our network, I am logging into our domain where
>both systems reside. The MSDE is running on an XP workstation and we have
>other workstations attempting to log into it. When we go into the ODBC setup
>we can see the MSDE instance but cannot log on to it.
>Bonnie
>
>"Sue Hoegemeier" wrote:
|||Sue,
We found out we were using the wrong port for MSDE. MSDE was listening on
Port 1143. We were using the SQL default of 1443 Thank you for your help. I
have another question now that this one is resolved. I'll start a new
thread. Thank you again for your help.
"Sue Hoegemeier" wrote:

> No problem...figured you just didn't know about the caps
> thing. Anyway, check the event logs on the XP workstation
> where MSDE is running to see if there are any security
> errors. Make sure the MSDE instance is listening on TCP/IP
> and that the clients are configure to connect with TCP/IP.
> You would probably want to start by running through the
> following article - it's long but connectivity issues aren't
> real easy to resolve as it can be so many different things.
> Potential causes of the "SQL Server does not exist or access
> denied" error message
> http://support.microsoft.com/?id=328306
> -Sue
> On Mon, 31 Oct 2005 07:01:07 -0800, "bw"
> <bw@.discussions.microsoft.com> wrote:
>
>

Can only log into a MSDE ODBC Connection as Administrator

When trying to log into a ODBC connection as a power user on a network we
receive the following error:
Connection failed:
SQLState:'01000'
SQL Server Error: 53
[Microsoft][ODBC SQL Server Driver][DBNET]ConnectionOpen (/cibbe
ct ()),
Connection failed:
SQLState:'08001'
SQL server Error:178
[microsoft][odbc sql server driver][dbnetlib]sql server does not
exist or
access denied.
Change the user to Administrator and they are able to login.Did you add logins for other users who aren't members of the
local admin group on the box where MSDE is installed? It
sounds like they may not have logins setup in MSDE.
By default, members of the local admins group will have
access. For other users, you need to add logins.
-Sue
On Thu, 27 Oct 2005 19:25:02 -0700, "bw"
<bw@.discussions.microsoft.com> wrote:

>When trying to log into a ODBC connection as a power user on a network we
>receive the following error:
>Connection failed:
>SQLState:'01000'
>SQL Server Error: 53
>[Microsoft][ODBC SQL Server Driver][DBNET]ConnectionOpen (/cibb
ect ()),
>Connection failed:
>SQLState:'08001'
>SQL server Error:178
>[microsoft][odbc sql server driver][dbnetlib]sql server does no
t exist or
>access denied.
>Change the user to Administrator and they are able to login.|||Sue,
Yes I did add them to the system as a user. Then created an MSDE Group.
The Group has the following rights:
GROUP EVERYONE - Read to Program Files
MSDE GROUP DOES NOT HAVE FULL CONTROL, NO DEL FOLDERS, TAKE OWNERSHIP,
CREATE FOLDER OR CHANGE PERMISSION TO THE MSDE/SYSTEM FOLDER OR MSDE/SERVER
FOLDER
USING A NOTEBOOK WITH ENTERPRISE MANAGER WE HAD GIVE THE MSDE GROUP -
PUBLIC, DB_WRITER, DB_READER AND DB_BACKUP OPERATOR
APPLIED SERVICE PACK 2 TO THE SYSTEM THAT IS RUNNING THE MSDE SERVICE AND
NOW THE SYSTEM RUNNING ENTERPRISE MANAGER GETS THE FOLLOWING ERROR WHEN
ATTEMPTING TO CONNECT TO THE SYSTEM MAP DRIVE THAT HAS THE MSDE INSTALLED WE
GET THE FOLLOWING ERROR:
AN ERROR OCCURRED WHILE RECONNECTING TO A LOCAL CONNECTION . MICROSOFT
WINDOWN NETWORK. THE LOCAL DEVICE NAME IS ALREADY IN USE.
CANNOT CONNECT THE ENTERPRISE MANAGER TO THE MSDE DATABASE NOW.
I APPRECIATE YOUR HELP.
"Sue Hoegemeier" wrote:

> Did you add logins for other users who aren't members of the
> local admin group on the box where MSDE is installed? It
> sounds like they may not have logins setup in MSDE.
> By default, members of the local admins group will have
> access. For other users, you need to add logins.
> -Sue
> On Thu, 27 Oct 2005 19:25:02 -0700, "bw"
> <bw@.discussions.microsoft.com> wrote:
>
>|||No need to yell. Using caps is considered yelling in
newsgroups.
By adding the users as logins in SQL Server, that doesn't
have anything to do with adding them to groups on the box
where MSDE is running.
How exactly are you trying to connect? I think something is
missing here as mapping drives is not necessary, giving
users full control on MSDE folders, etc is generally not
necessary either.
-Sue
On Fri, 28 Oct 2005 15:13:03 -0700, "bw"
<bw@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Sue,
>Yes I did add them to the system as a user. Then created an MSDE Group.
>The Group has the following rights:
> GROUP EVERYONE - Read to Program Files
> MSDE GROUP DOES NOT HAVE FULL CONTROL, NO DEL FOLDERS, TAKE OWNERSHIP,
>CREATE FOLDER OR CHANGE PERMISSION TO THE MSDE/SYSTEM FOLDER OR MSDE/SERVER
>FOLDER
>USING A NOTEBOOK WITH ENTERPRISE MANAGER WE HAD GIVE THE MSDE GROUP -
>PUBLIC, DB_WRITER, DB_READER AND DB_BACKUP OPERATOR
>APPLIED SERVICE PACK 2 TO THE SYSTEM THAT IS RUNNING THE MSDE SERVICE AND
>NOW THE SYSTEM RUNNING ENTERPRISE MANAGER GETS THE FOLLOWING ERROR WHEN
>ATTEMPTING TO CONNECT TO THE SYSTEM MAP DRIVE THAT HAS THE MSDE INSTALLED W
E
>GET THE FOLLOWING ERROR:
>AN ERROR OCCURRED WHILE RECONNECTING TO A LOCAL CONNECTION . MICROSOFT
>WINDOWN NETWORK. THE LOCAL DEVICE NAME IS ALREADY IN USE.
>CANNOT CONNECT THE ENTERPRISE MANAGER TO THE MSDE DATABASE NOW.
>I APPRECIATE YOUR HELP.
>
>"Sue Hoegemeier" wrote:
>|||I apologize I did not know that caps were yelling, I am happy for the help.
Since we are testing this on our network, I am logging into our domain where
both systems reside. The MSDE is running on an XP workstation and we have
other workstations attempting to log into it. When we go into the ODBC setu
p
we can see the MSDE instance but cannot log on to it.
Bonnie
"Sue Hoegemeier" wrote:

> No need to yell. Using caps is considered yelling in
> newsgroups.
> By adding the users as logins in SQL Server, that doesn't
> have anything to do with adding them to groups on the box
> where MSDE is running.
> How exactly are you trying to connect? I think something is
> missing here as mapping drives is not necessary, giving
> users full control on MSDE folders, etc is generally not
> necessary either.
> -Sue
> On Fri, 28 Oct 2005 15:13:03 -0700, "bw"
> <bw@.discussions.microsoft.com> wrote:
>
>|||No problem...figured you just didn't know about the caps
thing. Anyway, check the event logs on the XP workstation
where MSDE is running to see if there are any security
errors. Make sure the MSDE instance is listening on TCP/IP
and that the clients are configure to connect with TCP/IP.
You would probably want to start by running through the
following article - it's long but connectivity issues aren't
real easy to resolve as it can be so many different things.
Potential causes of the "SQL Server does not exist or access
denied" error message
http://support.microsoft.com/?id=328306
-Sue
On Mon, 31 Oct 2005 07:01:07 -0800, "bw"
<bw@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>I apologize I did not know that caps were yelling, I am happy for the help.
>Since we are testing this on our network, I am logging into our domain wher
e
>both systems reside. The MSDE is running on an XP workstation and we have
>other workstations attempting to log into it. When we go into the ODBC set
up
>we can see the MSDE instance but cannot log on to it.
>Bonnie
>
>"Sue Hoegemeier" wrote:
>|||Sue,
We found out we were using the wrong port for MSDE. MSDE was listening on
Port 1143. We were using the SQL default of 1443 Thank you for your help.
I
have another question now that this one is resolved. I'll start a new
thread. Thank you again for your help.
"Sue Hoegemeier" wrote:

> No problem...figured you just didn't know about the caps
> thing. Anyway, check the event logs on the XP workstation
> where MSDE is running to see if there are any security
> errors. Make sure the MSDE instance is listening on TCP/IP
> and that the clients are configure to connect with TCP/IP.
> You would probably want to start by running through the
> following article - it's long but connectivity issues aren't
> real easy to resolve as it can be so many different things.
> Potential causes of the "SQL Server does not exist or access
> denied" error message
> http://support.microsoft.com/?id=328306
> -Sue
> On Mon, 31 Oct 2005 07:01:07 -0800, "bw"
> <bw@.discussions.microsoft.com> wrote:
>
>

Can not start tcp port 1433 on MSDE

I've got an installation of MSDE that insists on only allowing shared memory
access. This works fine but I would like to access th db via tcp. I have
ran SVRNETCN.exe and verified that TCP is selected. I have even verified
that the port number etc. is set in the registry. It just refuses to
avtivate tcp when I restart MSDE or the box it's runinning on.
Here's the errorlog:
2004-04-30 00:03:33.20 server Microsoft SQL Server 2000 - 8.00.884
(Intel X86)
Nov 29 2003 20:52:47
Copyright (c) 1988-2003 Microsoft Corporation
Desktop Engine (Windows) on Windows NT 5.2 (Build 3790: )
2004-04-30 00:03:33.20 server Copyright (C) 1988-2002 Microsoft
Corporation.
2004-04-30 00:03:33.20 server All rights reserved.
2004-04-30 00:03:33.20 server Server Process ID is 4416.
2004-04-30 00:03:33.20 server Logging SQL Server messages in file
'C:\Program Files\Microsoft SQL Server\MSSQL$SHAREPOINT\LOG\ERRORLOG'.
2004-04-30 00:03:33.30 server SQL Server is starting at priority class
'normal'(1 CPU detected).
2004-04-30 00:03:33.38 server SQL Server configured for thread mode
processing.
2004-04-30 00:03:33.38 server Using dynamic lock allocation. [500] Lock
Blocks, [1000] Lock Owner Blocks.
2004-04-30 00:03:33.40 spid3 Starting up database 'master'.
2004-04-30 00:03:34.20 server Using 'SSNETLIB.DLL' version '8.0.880'.
2004-04-30 00:03:34.21 server SQL server listening on Shared Memory.
2004-04-30 00:03:34.21 server SQL Server is ready for client connections
2004-04-30 00:03:34.21 spid5 Starting up database 'model'.
2004-04-30 00:03:34.27 spid3 Server name is 'CHEF\SHAREPOINT'.
2004-04-30 00:03:34.27 spid3 Skipping startup of clean database id 4
2004-04-30 00:03:34.27 spid3 Skipping startup of clean database id 5
2004-04-30 00:03:34.27 spid3 Skipping startup of clean database id 6
2004-04-30 00:03:34.44 spid5 Clearing tempdb database.
2004-04-30 00:03:35.35 spid5 Starting up database 'tempdb'.
2004-04-30 00:03:35.55 spid3 Recovery complete.
Where in that log do you see evidence of SQL Server "refusing to activate
tcp"? Did you really mean, "I can't connect to SQL Server on port 1433"?
If so, I would check your network/router/firewall settings before assuming
the problem is service- or machine-specific.
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"Karl Foley" <karl@.thefoleyhouse.co.uk> wrote in message
news:e3R9sIkLEHA.2456@.TK2MSFTNGP12.phx.gbl...
> I've got an installation of MSDE that insists on only allowing shared
> memory
> access. This works fine but I would like to access th db via tcp. I have
> ran SVRNETCN.exe and verified that TCP is selected. I have even verified
> that the port number etc. is set in the registry. It just refuses to
> avtivate tcp when I restart MSDE or the box it's runinning on.
> Here's the errorlog:
> 2004-04-30 00:03:33.20 server Microsoft SQL Server 2000 - 8.00.884
> (Intel X86)
> Nov 29 2003 20:52:47
> Copyright (c) 1988-2003 Microsoft Corporation
> Desktop Engine (Windows) on Windows NT 5.2 (Build 3790: )
> 2004-04-30 00:03:33.20 server Copyright (C) 1988-2002 Microsoft
> Corporation.
> 2004-04-30 00:03:33.20 server All rights reserved.
> 2004-04-30 00:03:33.20 server Server Process ID is 4416.
> 2004-04-30 00:03:33.20 server Logging SQL Server messages in file
> 'C:\Program Files\Microsoft SQL Server\MSSQL$SHAREPOINT\LOG\ERRORLOG'.
> 2004-04-30 00:03:33.30 server SQL Server is starting at priority class
> 'normal'(1 CPU detected).
> 2004-04-30 00:03:33.38 server SQL Server configured for thread mode
> processing.
> 2004-04-30 00:03:33.38 server Using dynamic lock allocation. [500] Lock
> Blocks, [1000] Lock Owner Blocks.
> 2004-04-30 00:03:33.40 spid3 Starting up database 'master'.
> 2004-04-30 00:03:34.20 server Using 'SSNETLIB.DLL' version '8.0.880'.
> 2004-04-30 00:03:34.21 server SQL server listening on Shared Memory.
> 2004-04-30 00:03:34.21 server SQL Server is ready for client
> connections
> 2004-04-30 00:03:34.21 spid5 Starting up database 'model'.
> 2004-04-30 00:03:34.27 spid3 Server name is 'CHEF\SHAREPOINT'.
> 2004-04-30 00:03:34.27 spid3 Skipping startup of clean database id 4
> 2004-04-30 00:03:34.27 spid3 Skipping startup of clean database id 5
> 2004-04-30 00:03:34.27 spid3 Skipping startup of clean database id 6
> 2004-04-30 00:03:34.44 spid5 Clearing tempdb database.
> 2004-04-30 00:03:35.35 spid5 Starting up database 'tempdb'.
> 2004-04-30 00:03:35.55 spid3 Recovery complete.
>
>
|||"Aaron Bertrand [MVP]" <aaron@.TRASHaspfaq.com> wrote in message
news:%237IBIxnLEHA.2592@.tk2msftngp13.phx.gbl...
> Where in that log do you see evidence of SQL Server "refusing to activate
> tcp"?
Thanks for the offer of help, I'm just abut ready to give up on this!
Just about here:
2004-04-30 00:03:34.20 server Using 'SSNETLIB.DLL' version '8.0.880'.
2004-04-30 00:03:34.21 server SQL server listening on Shared Memory.
2004-04-30 00:03:34.21 server SQL Server is ready for client connections
You can see it's only using shared memory.

> Did you really mean, "I can't connect to SQL Server on port 1433"?
> If so, I would check your network/router/firewall settings before assuming
> the problem is service- or machine-specific.
No. I've tried to read all the posts on here regarding the problem and have
done multiple searches on google to try and solve this problem. No matter
what I do, MSDE will not listen on TCP port 1433. Here's a quick snip of
the output of netstat -an:
Active Connections
Proto Local Address Foreign Address State
TCP 0.0.0.0:25 0.0.0.0:0 LISTENING
TCP 0.0.0.0:53 0.0.0.0:0 LISTENING
[Snip]
TCP 0.0.0.0:691 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1025 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1026 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1028 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1533 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1723 0.0.0.0:0 LISTENING
[Snip]
As you can see, no port 1433 is listening here. I have only tried
connecting to port 1433 from this machine but can't see the point of trying
another machine if I can see the port is not open. This machine does not
have any firewall software enabled\installed on it. That functionality is
being provided by a hardware device.
As the version of MSDE seems so much newer than anything else I've seen
posted I am beginning to wonder if it is some kind of security feature...
|||> As the version of MSDE seems so much newer
Yes, 880 is quite a recent patch. Care to share where you obtained it?
Anyway, run svrnetcn.exe (it should execute from command line just like
that, otherwise it's in SQL Server's Tools\Binn folder) and make sure TCP/IP
is on the enabled side. If it isn't, move it over, hit apply, and restart
SQL Server. If that doesn't help, highlight TCP/IP and hit properties.
Make sure hide server is unchecked, then try changing the default TCP port
to some other number, hit apply, restart SQL Server, then change the default
TCP port back to 1433, hit apply, and restart SQL Server.
If TCP/IP is the ONLY enabled protocol, you might try enabling named pipes
just for fun, and then see http://support.microsoft.com/?id=306865 for a
registry setting that may need a fix.
If this is the way it has worked since you installed MSDE, you might
consider uninstalling and reinstalling (from SP3a) making sure to set
DISABLENETWORKPROTOCOL=0 in the setup ini file. Your patch level of 880
leads me to believe that installing from scratch would be the cleanest
solution anyway... sometimes these one-off patches have various side effects
that simply haven't been tested (which is why they are typically not
announced and readily available to the masses).
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
|||You might also need to check to see if it is truly MSDE or is it WMSDE.. If
it is WMSDE it can only be accessed from the same machine. Based on the
instance name of SharePoint I would assume that it is really WMSDE..
http://www.microsoft.com/resources/d...us/stsf17.mspx
If you need to access/use it for other purposes and/or from other machines
you will need to upgrade the instance to full SQL server.. or another
possible option would be to use a different instance of MSDE for your other
needs.

Hope that helps,
David Copeland
Microsoft Small Business Server Support
This posting is provided "AS IS" with no warranties, and confers no rights.
"Aaron Bertrand [MVP]" <aaron@.TRASHaspfaq.com> wrote in message
news:u0HZpsyLEHA.2148@.TK2MSFTNGP09.phx.gbl...
> Yes, 880 is quite a recent patch. Care to share where you obtained it?
> Anyway, run svrnetcn.exe (it should execute from command line just like
> that, otherwise it's in SQL Server's Tools\Binn folder) and make sure
TCP/IP
> is on the enabled side. If it isn't, move it over, hit apply, and restart
> SQL Server. If that doesn't help, highlight TCP/IP and hit properties.
> Make sure hide server is unchecked, then try changing the default TCP port
> to some other number, hit apply, restart SQL Server, then change the
default
> TCP port back to 1433, hit apply, and restart SQL Server.
> If TCP/IP is the ONLY enabled protocol, you might try enabling named pipes
> just for fun, and then see http://support.microsoft.com/?id=306865 for a
> registry setting that may need a fix.
> If this is the way it has worked since you installed MSDE, you might
> consider uninstalling and reinstalling (from SP3a) making sure to set
> DISABLENETWORKPROTOCOL=0 in the setup ini file. Your patch level of 880
> leads me to believe that installing from scratch would be the cleanest
> solution anyway... sometimes these one-off patches have various side
effects
> that simply haven't been tested (which is why they are typically not
> announced and readily available to the masses).
> --
> Aaron Bertrand
> SQL Server MVP
> http://www.aspfaq.com/
>
|||"David Copeland [MSFT]" <davidcop@.online.microsoft.com> wrote in message
news:e7Aoio6LEHA.3216@.TK2MSFTNGP12.phx.gbl...
> You might also need to check to see if it is truly MSDE or is it WMSDE..
If
> it is WMSDE it can only be accessed from the same machine. Based on the
> instance name of SharePoint I would assume that it is really WMSDE..
Fantastic - That's exactly it.
I installed another instance of MSDE and this runs perfectly over TCP port
1433 as expected. I found it confusing because:
I didn't know that WMSDE was a different product to MSDE or that WMSDE
indeed even existed.
The tools are all there to enable network connectivity even though WMSDE
doesn't use them.
Thanks everyone.

Can not start MSDE Service on win98

Can anyone please help me out, i installed the lastest MSDE on a win98 OS-Ver: 4.10.2222A
the install goes well, but when i restart the computer the sqlService manager icon appears blank, or red,

When i double click on the icon the SQL Server service manager appears but it can not access any instance running on my computer(it doesn't even find anything) by default the server and services comboboxes are empty and when i open those comboboxes they stay empty :(

I also can not use OSQL to log into the server, all i get is the following error: [TCP/IP sockets] specified sql server not found OS Error 120 (null)

I tried to do the following net start mssql$matrix
but it would just tell me that it has not service by that name.. even though i know it was installed with that instance name,

Inside the mssql$[someInstance] folder in my progfiles\sql server directory i read the error log and it says: SQL Server is terminating due to stop request from service control manager

What am i supposed to do now? DId anyone get this sort of trouble on a windows 98 SE machine?

ThanksCan you right click on the icon, and then from there select Start?

MSDE does work on Win98 SE.|||yes, it does install MSDE
but when i open up the sql manager app and try to start it manually i get this sweet error:

50 - Network request is not supported occured while performing this service operation on the MSSQLServer service

The network request is not supported.

God i've been spending hours on this looking for answer on the internet and nothing so far.|||well i just got another test PC out and this time it installed alright on the same type of Win98 machine. Weird.

But I still have a small problem inside OSQL I try to run the attach db statement

And I get this error message:
Msg 5172
Level 16
State 15
Server pc
Line 1

Header file for (filename) is not a valid database file header. The pageAudit property is incorrect.

What am i doing wrong? the statement is right...

Can not remote login to MSDE

I installed MSDE at my server at home, and that works fine.
On the server I can access my MSDE perfectly.
But, from a remote computer it seems impossible to connect.

Some (maybe) important information:

To create a user at my msde I used:

sp_addlogin (@. the MASTER DB)
sp_adduser (@. My DB)
sp_addrolemember (@. My DB)

Then I runned SVRNETCN.exe and enabled TCP/IP.

btw: I don't have a firewall running and both computers are on the same local network.is it trying to use windows integrated auth to connect, or mixed mode?|||It's configured for Mixed Mode...
I want to use sql-authentication and not windows authentication.
(it works localy, but not from an other computer)|||if it's running on a remote computer and U R using a firewall (XP...)
then try to open some port (1433) for the SQL Server DTS with the IP of the server...|||Nope, I don't have a firewall running...
I tried to telnet to 1433 to the MSDE, but even on the computer where my MSDE is running on, I can't get a telnet connection to 1433.
SQLServer uses tcp/ip, doesn't it?
I can't connect with VS.NET, Query Analyser, ... to my MSDE from an computer diferent than the computer that is running MSDE.|||I found out than my MSDE isn't 'registered' in my 'Data Sources (ODBC)'.
I registered it but...
It still doesn't work, but I think I am on the right spot :-)|||Ok, totaly wrong...
It has nothing to do with 'Data Sources (ODBC)'.
I tried everything!
It seems like MSDE isn't capable of listening at tcp/ip 1433.
Is this disabled in MSDE?|||try to check this:
on SQL Server configuration properties -> Connections
make sure the number is 0 (unlimited) or set it to 10 (for the test)
+
I did not hear U say U don't have a firewall on the server...|||I found it!!
I guess it's a bug in the install.
There is a key in the registry that contains no value:
..\MSSQLServer\SuperSocketNetLib\Tcp\tcpPort
The value has to be: 1433

But what if you have more than one instance?
You can't bind them all to the same port...
..\MSSQLServer\SuperSocketNetLib\Tcp\TcpDynamicPorts
It also doesn't contain a value...

Can not login to MSDE

I have a windows 2000 server with Veritas Backup Exec 9.1 and when you
install veritas it installs MSDE version 8.00.760. When i try to connect to
the msde using enterprise manager i get an error mesage stating that Reason:
SQL Server does not exist or access denied. I was told that the sa password
is blank. I tried logging in to the machine using Administrator account and
same error. Any suggestions on how to get around this.
I also ran svrnetcn.exe and made sure that tcp/ip is enabled.
Hope this Helps
Dan V
This posting is provided "AS IS" with no warranties, and confers no rights
"Dan" <anonymous@.discussions.microsoft.com> wrote in message
news:ue1EIliIEHA.2244@.TK2MSFTNGP09.phx.gbl...
> I have a windows 2000 server with Veritas Backup Exec 9.1 and when you
> install veritas it installs MSDE version 8.00.760. When i try to connect
to
> the msde using enterprise manager i get an error mesage stating that
Reason:
> SQL Server does not exist or access denied. I was told that the sa
password
> is blank. I tried logging in to the machine using Administrator account
and
> same error. Any suggestions on how to get around this.
>
|||hey Dan,
I'm having the same problems without using Veritas. When i try to connect it says the server does not exist or access is denied. When i installed SQL it did not set up my server name as local or localhost like a lot of these manuals i have says it will do
. It set it up as (myname)\NETSDK. Is your server set up as local or something else?