Get Next Number: installing

Showing posts with label installing. Show all posts

Friday, March 23, 2012

Frustrating Installation Error

I was installing SQL Server on my machine and during installation my PC
freezed. It happens frequently on my machine as my bad luck sticks frequenctly to my side. So i tried after
restarting to install it again and since then i always get the same
error message:
"An error occurred while creating one or more registry entries. Please
see C:\WINDOWS\sqlstp.log for details. The problem could be caused by a
low registry quota condition"
I have tried to clean the registry during the installation bt chosing "advanced options" -> "Rebuild registry" and i don't know what else i could
do to solve this issue. I'd like to remark that i also deleted the SQL Server keys from Registry as suggested from Microsoft to delete default and special named instances.

I also deleted every thing under %TEMP%; I even installed third pary registry tools to clean the registry such as RegistryFix, Registry Mechanic and AMUST.

Finally, i'm using Windows XP Professional SP2.

Any help?

The log file lists the following:

14:22:27 Begin Setup
14:22:27 8.00.194
14:22:27 Mode = Normal
14:22:27 ModeType = NORMAL
14:22:27 GetDefinitionEx returned: 0, Extended: 0x0
14:22:27 ValueFTS returned: 1
14:22:27 ValuePID returned: 1
14:22:27 ValueLic returned: 0
14:22:27 System: Windows NT WorkStation
14:22:27 SQL Server ProductType: Developer Edition [0x3]
14:22:27 Begin Action: SetupInitialize
14:22:27 End Action SetupInitialize
14:22:27 Begin Action: SetupInstall
14:22:27 Reading
Software\Microsoft\Windows\CurrentVersion\CommonFilesDir ...
14:22:27 CommonFilesDir=C:\Programme\Gemeinsame Dateien
14:22:27 Windows Directory=C:\WINDOWS\
14:22:27 Program Files=C:\Programme\
14:22:27 TEMPDIR=C:\WINDOWS\TEMP\
14:22:27 Begin Action: SetupInstall
14:22:27 digpid size : 256
14:22:27 digpid size : 164
14:22:27 Begin Action: CheckFixedRequirements
14:22:27 Platform ID: 0xf000000
14:22:27 Version: 5.1.2600
14:22:27 File Version - C:\WINDOWS\system32\shdocvw.dll: 6.0.2900.2805
14:22:27 End Action: CheckFixedRequirements
14:22:27 Begin Action: ShowDialogs
14:22:27 Initial Dialog Mask: 0x83000f7, Disable Back=0x1
14:22:27 Begin Action ShowDialogsHlpr: 0x1
14:22:27 Begin Action: DialogShowSdWelcome
14:22:28 End Action DialogShowSdWelcome
14:22:28 Dialog 0x1 returned: 1
14:22:28 End Action ShowDialogsHlpr
14:22:28 ShowDialogsGetDialog returned: nCurrent=0x2,index=1
14:22:28 Begin Action ShowDialogsHlpr: 0x2
14:22:28 Begin Action: DialogShowSdMachineName
14:22:30 ShowDlgMachine returned: 1
14:22:30 Name = COOSA, Type = 0x1
14:22:30 Begin Action: CheckRequirements
14:22:30 Processor Architecture: x86 (Pentium)
14:22:30 Service Pack: 512
14:22:30 ComputerName: COOSA
14:22:30 User Name: admin
14:22:30 IsAllAccessAllowed returned: 1
14:22:30 OS Language: 0x401
14:22:30 End Action CheckRequirements
14:22:30 This combination of Package and Operating System allows a full
product install.
14:22:30 CreateSetupTopology(COOSA), Handle : 0x1b04098, returned : 0
14:22:30 CreateSetupTopology returned : 0, Handle : 0x1b04098
14:22:30 Topology Type : 1, Return Value : 0
14:22:30 ST_GetPhysicalNode returned : 0, PNHandle : 0x1b040c0
14:22:30 PN_EnumerateEx returned : 0
14:22:30 PN_GetSQLStates returned : 0, SqlStates : 0x80000000
14:22:30 PN_StartScan [0x1b040c0] returned : 0
14:22:30 PN_GetNext [0x1b040c0] returned : 18, Handle: [0x0]
14:22:30 No more items in enumeration.
14:22:30 ReleaseSetupTopology
14:22:30 Named instance limit: 100, quota: 0
14:22:30 End Action DialogShowSdMachineName
14:22:30 begin ShowDialogsUpdateMask
14:22:30 nFullMask = 0x83000f7, nCurrent = 0x2, nDirection = 0
14:22:30 Updated Dialog Mask: 0xbf00037, Disable Back = 0x1
14:22:30 Dialog 0x2 returned: 0
14:22:30 End Action ShowDialogsHlpr
14:22:30 ShowDialogsGetDialog returned: nCurrent=0x4,index=2
14:22:30 Begin Action ShowDialogsHlpr: 0x4
14:22:30 Begin Action: DialogShowSdInstallMode
14:22:36 ShowDlgInstallMode returned: 1
14:22:36 InstallMode : 0x1
14:22:36 End Action DialogShowSdInstallMode
14:22:36 begin ShowDialogsUpdateMask
14:22:36 nFullMask = 0xbf00037, nCurrent = 0x4, nDirection = 1
14:22:36 Updated Dialog Mask: 0xbf40037, Disable Back = 0x1
14:22:36 Dialog 0x4 returned: 1
14:22:36 End Action ShowDialogsHlpr
14:22:36 ShowDialogsGetDialog returned: nCurrent=0x10,index=4
14:22:36 Begin Action ShowDialogsHlpr: 0x10
14:22:36 Begin Action: DialogShowSdRegisterUserEx
14:22:42 End Action DialogShowSdRegisterUserEx
14:22:42 Dialog 0x10 returned: 1
14:22:42 End Action ShowDialogsHlpr
14:22:42 ShowDialogsGetDialog returned: nCurrent=0x20,index=5
14:22:42 Begin Action ShowDialogsHlpr: 0x20
14:22:42 Begin Action: DialogShowSdLicense
14:22:43 End Action DialogShowSdLicense
14:22:43 Dialog 0x20 returned: 1
14:22:43 End Action ShowDialogsHlpr
14:22:43 ShowDialogsGetDialog returned: nCurrent=0x40000,index=18
14:22:43 Begin Action ShowDialogsHlpr: 0x40000
14:22:43 Begin Action: DialogShowSdCliSvr
14:22:43 DisplaySystemPreReq
14:22:45 ShowDlgClientServerSelect returned: 1
14:22:45 Type : 0x2
14:22:45 End Action DialogShowSdCliSvr
14:22:45 begin ShowDialogsUpdateMask
14:22:45 nFullMask = 0xbf40037, nCurrent = 0x40000, nDirection = 1
14:22:45 Updated Dialog Mask: 0xbfc0037, Disable Back = 0x1
14:22:45 Dialog 0x40000 returned: 1
14:22:45 End Action ShowDialogsHlpr
14:22:45 ShowDialogsGetDialog returned: nCurrent=0x80000,index=19
14:22:45 Begin Action ShowDialogsHlpr: 0x80000
14:22:45 Begin Action: DialogShowSdInstanceName
14:22:45 Begin Action: ShowDlgInstanceName
14:22:47 End Action: ShowDlgInstanceName
14:22:47 ShowDlgInstanceName returned : 1
14:22:47 InstanceName : MSSQLSERVER
14:22:47 CreateSetupTopology(COOSA), Handle : 0x1b04098, returned : 0
14:22:47 CreateSetupTopology returned : 0, Handle : 0x1b04098
14:22:47 Topology Type : 1, Return Value : 0
14:22:47 ST_GetPhysicalNode returned : 0, PNHandle : 0x1b040c0
14:22:47 PN_EnumerateEx returned : 0
14:22:47 PN_GetSQLStates returned : 0, SqlStates : 0x80000000
14:22:47 PN_StartScan [0x1b040c0] returned : 0
14:22:47 PN_GetNext [0x1b040c0] returned : 18, Handle: [0x0]
14:22:47 No more items in enumeration.
14:22:47 ReleaseSetupTopology
14:22:47 End Action DialogShowSdInstanceName
14:22:47 begin ShowDialogsUpdateMask
14:22:47 nFullMask = 0xbfc0037, nCurrent = 0x80000, nDirection = 1
14:22:47 Updated Dialog Mask: 0xbfc0037, Disable Back = 0x1
14:22:47 Dialog 0x80000 returned: 1
14:22:47 End Action ShowDialogsHlpr
14:22:47 ShowDialogsGetDialog returned: nCurrent=0x100000,index=20
14:22:47 Begin Action ShowDialogsHlpr: 0x100000
14:22:47 Begin Action: DialogShowSdSetupType
14:22:47 Begin Action: Setup Type
14:23:05 SQL program folder: C:\Programme\Microsoft SQL Server
14:23:05 SQL data folder: C:\Programme\Microsoft SQL Server
14:23:05 Windows system folder: C:\WINDOWS\system32\
14:23:05 Prog req: 38073, Data req: 34432, Sys req: 158694
14:23:05 Prog avail: 1481708, Data avail: 1481708, Sys avail: 1481708
14:23:05 Prog req vs. avail, 231199, 1481708
14:23:05 Data req vs. avail, 34432, 1481708
14:23:05 Sys req vs. avail, 193126, 1481708
14:23:05 DisplaySystemPreReq
14:23:05 [SetupTypeSQL]
14:23:05 szDir = C:\Programme\Microsoft SQL Server
14:23:05 szDir = %PROGRAMFILES%\Microsoft SQL Server
14:23:05 Result = 301
14:23:05 szDataDir = C:\Programme\Microsoft SQL Server
14:23:05 szDataDir = %PROGRAMFILES%\Microsoft SQL Server
14:23:05 End Action: Setup Type
14:23:05 Setup Type: Typical (301)
14:23:05 End Action DialogShowSdSetupType
14:23:05 begin ShowDialogsUpdateMask
14:23:05 nFullMask = 0xbfc0037, nCurrent = 0x100000, nDirection = 301
14:23:05 Updated Dialog Mask: 0xbdc0037, Disable Back = 0x1
14:23:05 Dialog 0x100000 returned: 301
14:23:05 End Action ShowDialogsHlpr
14:23:05 ShowDialogsGetDialog returned: nCurrent=0x400000,index=22
14:23:05 Begin Action ShowDialogsHlpr: 0x400000
14:23:05 Begin Action: DlgServices
14:23:10 ShowDlgServices returned: 1
14:23:10 [DlgServices]
14:23:10 Local-Domain = 3855
14:23:10 AutoStart = 15
14:23:10 Result = 1
14:23:10 End Action DlgServices
14:23:10 begin ShowDialogsUpdateMask
14:23:10 nFullMask = 0xbdc0037, nCurrent = 0x400000, nDirection = 1
14:23:10 Updated Dialog Mask: 0xbdc0037, Disable Back = 0x1
14:23:10 Dialog 0x400000 returned: 1
14:23:10 End Action ShowDialogsHlpr
14:23:10 ShowDialogsGetDialog returned: nCurrent=0x800000,index=23
14:23:10 Begin Action ShowDialogsHlpr: 0x800000
14:23:10 Begin Action: DlgSQLSecurity
14:23:12 ShowDlgSQLSecurity returned: 1
14:23:12 LoginMode = 1,szPwd
14:23:12 End Action DlgSQLSecurity
14:23:12 begin ShowDialogsUpdateMask
14:23:12 nFullMask = 0xbdc0037, nCurrent = 0x800000, nDirection = 1
14:23:12 Updated Dialog Mask: 0xbdc0037, Disable Back = 0x1
14:23:12 Dialog 0x800000 returned: 1
14:23:12 End Action ShowDialogsHlpr
14:23:12 ShowDialogsGetDialog returned: nCurrent=0x1000000,index=24
14:23:12 Begin Action ShowDialogsHlpr: 0x1000000
14:23:12 Begin Action: DlgCollation
14:23:12 ShowDlgCollation returned: 1
14:23:12 collation_name = Arabic_CI_AS,locale_name = Arabic,lcid =
0x401,SortId = 0,dwCompFlags = 0x30001
14:23:12 End Action DlgCollation
14:23:12 begin ShowDialogsUpdateMask
14:23:12 nFullMask = 0xbdc0037, nCurrent = 0x1000000, nDirection = 1
14:23:12 Updated Dialog Mask: 0xbdc0037, Disable Back = 0x1
14:23:12 Dialog 0x1000000 returned: 1
14:23:12 End Action ShowDialogsHlpr
14:23:12 ShowDialogsGetDialog returned: nCurrent=0x2000000,index=25
14:23:12 Begin Action ShowDialogsHlpr: 0x2000000
14:23:12 Begin Action: DlgNetwork
14:23:12 ShowDlgNetwork returned: 1
14:23:12 [DlgServerNetwork]
14:23:12 NetworkLibs = 255
14:23:12 TCPPort = 1433
14:23:12 TCPPrxy = Default
14:23:12 NMPPipeName = \\.\pipe\sql\query
14:23:12 Result = 1
14:23:12 End Action DlgNetwork
14:23:12 begin ShowDialogsUpdateMask
14:23:12 nFullMask = 0xbdc0037, nCurrent = 0x2000000, nDirection = 1
14:23:12 Updated Dialog Mask: 0xbdc0037, Disable Back = 0x1
14:23:12 Dialog 0x2000000 returned: 1
14:23:12 End Action ShowDialogsHlpr
14:23:12 ShowDialogsGetDialog returned: nCurrent=0x8000000,index=27
14:23:12 Begin Action ShowDialogsHlpr: 0x8000000
14:23:12 Begin Action: DialogShowSdStartCopy
14:23:13 End Action DialogShowSdStartCopy
14:23:13 begin ShowDialogsUpdateMask
14:23:13 nFullMask = 0xbdc0037, nCurrent = 0x8000000, nDirection = 1
14:23:13 Updated Dialog Mask: 0xbdc0037, Disable Back = 0x1
14:23:13 Dialog 0x8000000 returned: 1
14:23:13 End Action ShowDialogsHlpr
14:23:13 ShowDialogsGetDialog returned: nCurrent=0x0,index=0
14:23:13 End Action ShowDialogs
14:23:13 Begin Action ProcessBeforeDataMove:
14:23:13 DeinstallStart returned (C:\Programme\Microsoft SQL
Server\MSSQL): 0
14:23:13 End Action ProcessBeforeDataMove:
14:23:13 Begin Action SetToolsComponentSelection:
14:23:13 End Action SetToolsComponentSelection:
14:23:13 Begin Action ProcessComponentSelection:
14:23:13 End Action ProcessComponentSelection
14:23:13 Begin Action LogSelectedComponents:
14:23:13 SQLProg
14:23:13 SQLProg\SQLServr
14:23:13 SQLProg\SQLServr\Help
14:23:13 SQLProg\SQLServr\SCMDev
14:23:13 SQLProg\SQLServr\SCMDev\SCMh
14:23:13 SQLProg\SQLServr\SCMDev\SCMX86Lb
14:23:13 SQLProg\SQLServr\SCMDev\SCMALb
14:23:13 SQLProg\SQLServr\Rs1033
14:23:13 SQLProg\SQLServr\RsIntl
14:23:13 SQLProg\SQLServr\ActiveX
14:23:13 SQLProg\SQLServr\System
14:23:13 SQLProg\UpgTools
14:23:13 SQLProg\UpgTools\UpgSys
14:23:13 SQLProg\UpgTools\ActiveX
14:23:13 SQLProg\UpgTools\Res1033
14:23:13 SQLProg\UpgTools\ResOther
14:23:13 SQLProg\UpgTools\Resld
14:23:13 SQLProg\ReplSupp
14:23:13 SQLProg\ReplSupp\ReplDat
14:23:13 SQLProg\ReplSupp\RepComm
14:23:13 SQLProg\ReplSupp\RepNoDk
14:23:13 SQLProg\ReplSupp\ActiveX
14:23:13 SQLProg\Install
14:23:13 SQLProg\System
14:23:13 SQLProg\SvrExt
14:23:13 SQLProg\SvrExt\Help
14:23:13 SQLProg\SvrExt\SvrExtRs
14:23:13 SQLProg\SvrExt\ResIntl
14:23:13 SQLProg\Dat
14:23:13 SQLProg\DatSmpl
14:23:13 SQLProg\BaseSys
14:23:13 SQLProg\BaseBinn
14:23:13 SQLProg\BaseInst
14:23:13 SQLProg\Symbols
14:23:13 SQLProg\Symbols\EXE
14:23:13 SQLProg\Symbols\DLL
14:23:13 SQLProg\Perfmon
14:23:13 SQLProg\Perfmon\System
14:23:13 SQLProg\Root
14:23:13 MgtTool
14:23:13 MgtTool\SEM
14:23:13 MgtTool\SEM\HTML
14:23:13 MgtTool\SEM\MSD98
14:23:13 MgtTool\SEM\MSD98SYS
14:23:13 MgtTool\SEM\MSD98Res
14:23:13 MgtTool\SEM\MSD98Hlp
14:23:13 MgtTool\SEM\Help
14:23:13 MgtTool\SEM\Res1033
14:23:13 MgtTool\SEM\ResIntl
14:23:13 MgtTool\SEM\MSD98RsI
14:23:13 MgtTool\SEM\ActiveX
14:23:13 MgtTool\SEM\ActiveX\Res1033
14:23:13 MgtTool\SEM\ActiveX\ResIntl
14:23:13 MgtTool\SEM\Scripts
14:23:13 MgtTool\SEM\OLEDB
14:23:13 MgtTool\SEM\OLEDB\Res1033
14:23:13 MgtTool\SEM\OLEDB\ResIntl
14:23:13 MgtTool\Profiler
14:23:13 MgtTool\Profiler\Help
14:23:13 MgtTool\Profiler\Res1033
14:23:13 MgtTool\Profiler\ResIntl
14:23:13 MgtTool\Qryanlz
14:23:13 MgtTool\Qryanlz\Help
14:23:13 MgtTool\Qryanlz\Res1033
14:23:13 MgtTool\Qryanlz\ResIntl
14:23:13 MgtTool\DTCCLi
14:23:13 MgtTool\Wzcnflct
14:23:13 MgtTool\Wzcnflct\WzcnHlp
14:23:13 MgtTool\Wzcnflct\Wzcn1033
14:23:13 MgtTool\Wzcnflct\WzcnOthr
14:23:13 MgtTool\Wzcnflct\WzcnCmn
14:23:13 MgtTool\UtilSys
14:23:13 MgtTool\UtilBinn
14:23:13 Connect
14:23:13 Connect\ConnSys
14:23:13 Books
14:23:13 Books\Bookso
14:23:13 Books\Bookso\Utils
14:23:13 DevTools
14:23:13 DevTools\Dbg Int
14:23:13 DevTools\Dbg Int\Dbg Int Common
14:23:13 DevTools\Dbg Int\EXE
14:23:13 CoreRepl
14:23:13 CoreRepl\Res1033
14:23:13 CoreRepl\ResIntl
14:23:13 Core
14:23:13 Core\Res1033
14:23:13 Core\ResOther
14:23:13 Repostry
14:23:13 Repostry\RepstSys
14:23:13 Repostry\Res1033
14:23:13 Repostry\ResIntl
14:23:13 CoreMisc
14:23:13 CoreMisc\ActiveX
14:23:13 CoreMisc\ActiveX\Res1033
14:23:13 CoreMisc\ActiveX\ResIntl
14:23:13 CoreMisc\Res1033
14:23:13 Monarch
14:23:13 Monarch\Monr1033
14:23:13 Monarch\MonrIntl
14:23:13 Jet
14:23:13 CoreInst
14:23:13 CoreCOM
14:23:13 CoreCOM\Res1033
14:23:13 CoreCOM\ResIntl
14:23:13 CoreTool
14:23:13 CoreTool\Res1033
14:23:13 CoreTool\ResOther
14:23:13 DBLibCli
14:23:13 SFExt
14:23:13 SFExt\ActiveX
14:23:13 SFExt\ActiveX\Res1033
14:23:13 SFExt\ActiveX\ResIntl
14:23:13 SFExt\Res1033
14:23:13 SFExt\ResIntl
14:23:13 Trace
14:23:13 Trace\Res1033
14:23:13 Trace\ResOther
14:23:13 MiscCore
14:23:13 MC
14:23:13 MC\MC1033
14:23:13 MC\MCIntl
14:23:13 MC\Help
14:23:13 SQLMgr
14:23:13 SQLMgr\Res1033
14:23:13 SQLMgr\ResIntl
14:23:13 SvrTool
14:23:13 SvrTool\Res1033
14:23:13 SvrTool\ResIntl
14:23:13 DTSUI
14:23:13 DTSUI\Res1033
14:23:13 DTSUI\ResIntl
14:23:13 MSOlap
14:23:13 MSOlap\Res1033
14:23:13 MSOlap\ResIntl
14:23:13 ATL
14:23:13 ATL\winnt
14:23:13 ATL\win9x
14:23:13 MFC42U
14:23:13 VC
14:23:13 VB
14:23:13 OCX1
14:23:13 SQLAdHlp
14:23:13 SQLAdHlp\Res1033
14:23:13 SQLAdHlp\ResOther
14:23:13 {E07FDDBE-5A21-11d2-9DAD-00C04F79D434}
14:23:13 {E07FDDC7-5A21-11d2-9DAD-00C04F79D434}
14:23:13 {E07FDDC0-5A21-11d2-9DAD-00C04F79D434}
14:23:13 {E07FDDBF-5A21-11d2-9DAD-00C04F79D434}
14:23:13 End Action LogSelectedComponents
14:23:13 Begin Action InstallPkgs:
14:23:13 Begin Action: Locked Connectivity Files Check
14:23:13 ConnectivityLocked returned: 0
14:23:13 Der Vorgang wurde erfolgreich beendet.

14:23:13 End Action: Locked Connectivity Files Check
14:23:13 Setup is installing Microsoft Data Access Components (MDAC)
...
14:23:13 E:\SOFTWA~1\DEV\DB\SQL200~1\x86\Other\sqlredis.exe /q:a
/C:"setupre.exe WARN=1 -s -SMS"
14:23:24 ExitCode: 0
14:23:24 Setup is installing Microsoft Distributed Transaction
Coordinator (MSDTC) ...
14:23:24 C:\WINDOWS\TEMP\SqlSetup\Bin\cldtcstp.exe -SupportDir
"C:\WINDOWS\TEMP\SqlSetup\Bin" -DTCPkg
"E:\SOFTWA~1\DEV\DB\SQL200~1\x86\Other\dtcsetup.exe" -LogFile
"C:\WINDOWS\sqlstp.log"
14:23:24 Process Exit Code: (0)
14:23:24 /Q:A /T:C:\WINDOWS\TEMP\ixp001.tmp
14:23:24 Setup is installing HTML Help ...
14:23:24 HTML Help installer exit code: 0
14:23:45 End Action InstallPkgs
14:23:45 Begin Action MoveFileData:
14:23:45 Enabled SELFREGISTERBATCH
14:23:45 Enabled CORECOMPONENTHANDLING
14:24:11 Begin Action: MoveFileDataSpecial
14:24:11 End Action: MoveFileDataSpecial
14:24:11 End Action MoveFileData
14:24:11 Begin Action ProcessAfterDataMove:
14:24:11 E:\SOFTWA~1\DEV\DB\SQL200~1\x86\Binn\hhcol.exe
C:\Programme\Microsoft SQL Server\80\Tools\Books
14:24:11 End Action ProcessAfterDataMove
14:24:11 Begin Action BuildServer:
14:24:11 C:\WINDOWS\TEMP\SqlSetup\Bin\scm.exe -Silent 1 -Action 5
-ExePath "C:\Programme\Microsoft SQL Server\MSSQL\binn\sqlservr.exe"
-Service "MSSQLSERVER"
14:24:12 Process Exit Code: (0)
14:24:12 Begin Action: CreateRegistrySetSQL
14:24:12 End Action: CreateRegistrySetSQL
14:24:12 Begin Action: RegWriteSetupEntry
14:24:12 End Action: RegWriteSetupEntry
14:24:12 Begin Action: CreateSer
14:24:12 End Action: CreateSer
14:24:12 Begin Action: SkuIt
14:24:12 End Action: SkuIt
14:24:12 SetFileSecuritySQLAndAdmin for C:\Programme\Microsoft SQL
Server\MSSQL returned: 0, 0
14:24:12 SetRegSecuritySQLAndAdmin for
Software\Microsoft\MSSQLServer\MSSQLServer returned: 0, 0
14:24:12 Begin Action: UpdateSystemPath
14:24:12 Path successfully updated.
14:24:12
%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;C:\Programme\Java\jdk1.5.0_04\bin;C:\Borland\BCC55\bin;"C:\Programme\Symantec\Norton
Ghost 2003\";C:\Programme\Microsoft SQL
Server\80\Tools\BINN;C:\Programme\MySQL\MySQL Server 5.0\bin
14:24:12 End Action: UpdateSystemPath
14:24:13 C:\Programme\Microsoft SQL Server\80\Tools\Binn\cnfgsvr.exe
-F "C:\WINDOWS\sqlstp.log" -I MSSQLSERVER -V 1 -M 0 -Q "Arabic_CI_AS"
-H 459924 -U sa -P
###############################################################################

Starting Service ...

Arabic_CI_AS

-m -Q -T4022 -T3659

Connecting to Server ...

driver={sql server};server=COOSA;UID=sa;PWD=;database=master

Configuring Server ...

EXEC sp_grantlogin N'VORDEFINIERT\Administratoren'

[Microsoft][ODBC SQL Server Driver][SQL Server]Granted login access to
'VORDEFINIERT\Administratoren'.

EXEC sp_addsrvrolemember N'VORDEFINIERT\Administratoren', 'sysadmin'

[Microsoft][ODBC SQL Server Driver][SQL
Server]'VORDEFINIERT\Administratoren' added to role 'sysadmin'.

update master.dbo.spt_server_info set attribute_value = @.@.version where
attribute_id = 2

EXEC sp_addserver N'COOSA', local

EXEC sp_configure 'allow updates', 1

[Microsoft][ODBC SQL Server Driver][SQL Server]DBCC execution
completed. If DBCC printed error messages, contact your system
administrator.

[Microsoft][ODBC SQL Server Driver][SQL Server]Configuration option
'allow updates' changed from 0 to 1. Run the RECONFIGURE statement to
install.

reconfigure with override

update master.dbo.sysaltfiles set size=1024 where name=N'tempdev'

EXEC sp_configure 'allow updates', 0

[Microsoft][ODBC SQL Server Driver][SQL Server]DBCC execution
completed. If DBCC printed error messages, contact your system
administrator.

[Microsoft][ODBC SQL Server Driver][SQL Server]Configuration option
'allow updates' changed from 1 to 0. Run the RECONFIGURE statement to
install.

reconfigure with override

Disconnecting from Server ...

Stopping Service ...

SQL Server has been successfully configured!

###############################################################################

14:24:42 Process Exit Code: (0)
14:24:42 End Action BuildServer
14:24:42 Begin Action SelfRegiser
14:24:42 DLLRegisterServer atl.dll: 0, 0x0
14:24:50 Return code: 0
14:24:50 Begin Action SelfRegisterOnCluster
14:24:50 End Action SelfRegisterOnCluster
14:24:50 Begin Action RegisterSvrReplFiles
14:24:50 **** File registered: C:\Programme\Microsoft SQL
Server\80\COM\snapshot.exe-unregserver
14:24:50 **** File registered: C:\Programme\Microsoft SQL
Server\80\COM\distrib.exe-unregserver
14:24:50 **** File registered: C:\Programme\Microsoft SQL
Server\80\COM\replmerg.exe-unregserver
14:24:50 **** File registered: C:\Programme\Microsoft SQL
Server\80\COM\logread.exe-unregserver
14:24:50 **** File registered: C:\Programme\Microsoft SQL
Server\80\COM\qrdrsvc.exe-unregserver
14:24:51 **** File registered: C:\Programme\Microsoft SQL
Server\80\COM\snapshot.exe-regserver
14:24:51 **** File registered: C:\Programme\Microsoft SQL
Server\80\COM\distrib.exe-regserver
14:24:51 **** File registered: C:\Programme\Microsoft SQL
Server\80\COM\replmerg.exe-regserver
14:24:51 **** File registered: C:\Programme\Microsoft SQL
Server\80\COM\logread.exe-regserver
14:24:51 **** File registered: C:\Programme\Microsoft SQL
Server\80\COM\qrdrsvc.exe-regserver
14:24:51 End Action RegisterSvrReplFiles
14:24:51 Begin Action SelfRegisterCOMShared
14:24:51 End Action SelfRegisterCOMShared
14:24:51 End Action SelfRegister
14:24:51 Begin Action SetupRegistry:
14:24:51 SNMP service has been detected.
14:24:51 Begin Action RegWriteInstalledInstances:
14:24:51 End Action RegWriteInstalledInstances
14:24:51 Register this installation of SQL Server with MDAC
14:24:51 Completed registering this installation of SQL Server with
MDAC
14:25:07 An error occurred while creating one or more registry entries.
Please see C:\WINDOWS\\\sqlstp.log for details. The problem could be
caused by a low registry quota condition.
14:25:07 Action CleanUpInstall:
14:25:07 C:\WINDOWS\TEMP\SqlSetup\Bin\scm.exe -Silent 1 -Action 4
-Service SQLSERVERAGENT
14:25:07 Process Exit Code: (1060) Der angegebene Dienst ist kein
installierter Dienst.

14:25:07 C:\WINDOWS\TEMP\SqlSetup\Bin\scm.exe -Silent 1 -Action 4
-Service MSSQLSERVER
14:25:07 Process Exit Code: (0)
14:25:07 StatsGenerate returned: 2
14:25:07 StatsGenerate
(0x80000000,0x1,0xf000000,0x200,1033,303,0x0,0x1,0,0,0
14:25:07 StatsGenerate -1,admin)
14:25:07 Installation Failed.

I got the indentical error when I attempted to install SQL 2000 Developer's Edition on XP Pro. My log file failure occurred at the same place yours did.

I had recently installed .Net framework, .Net SDK, and ASP Web Matrix. I made a lucky guess that they were causing the problem.

I did an uninstall of:
.Net framework
.Net SDK
ASP Web Matrix

I deleted the sub folders in c:\Program Files\Microsoft SQL Server.

Then SQL 2000 DE installed successfully, and I reinstalled the .Net framework & ASP Web Matrix.

Hope this helps.

Frustrating Installation Error

I also deleted every thing under %TEMP%; I even installed third pary registry tools to clean the registry such as RegistryFix, Registry Mechanic and AMUST.

Finally, i'm using Windows XP Professional SP2.

Any help?

The log file lists the following:

Starting Service ...

Arabic_CI_AS

-m -Q -T4022 -T3659

Connecting to Server ...

driver={sql server};server=COOSA;UID=sa;PWD=;database=master

Configuring Server ...

EXEC sp_grantlogin N'VORDEFINIERT\Administratoren'

[Microsoft][ODBC SQL Server Driver][SQL Server]Granted login access to
'VORDEFINIERT\Administratoren'.

EXEC sp_addsrvrolemember N'VORDEFINIERT\Administratoren', 'sysadmin'

[Microsoft][ODBC SQL Server Driver][SQL
Server]'VORDEFINIERT\Administratoren' added to role 'sysadmin'.

update master.dbo.spt_server_info set attribute_value = @.@.version where
attribute_id = 2

EXEC sp_addserver N'COOSA', local

EXEC sp_configure 'allow updates', 1

[Microsoft][ODBC SQL Server Driver][SQL Server]DBCC execution
completed. If DBCC printed error messages, contact your system
administrator.

[Microsoft][ODBC SQL Server Driver][SQL Server]Configuration option
'allow updates' changed from 0 to 1. Run the RECONFIGURE statement to
install.

reconfigure with override

update master.dbo.sysaltfiles set size=1024 where name=N'tempdev'

EXEC sp_configure 'allow updates', 0

[Microsoft][ODBC SQL Server Driver][SQL Server]DBCC execution
completed. If DBCC printed error messages, contact your system
administrator.

[Microsoft][ODBC SQL Server Driver][SQL Server]Configuration option
'allow updates' changed from 1 to 0. Run the RECONFIGURE statement to
install.

reconfigure with override

Disconnecting from Server ...

Stopping Service ...

SQL Server has been successfully configured!

###############################################################################

I got the indentical error when I attempted to install SQL 2000 Developer's Edition on XP Pro. My log file failure occurred at the same place yours did.

I had recently installed .Net framework, .Net SDK, and ASP Web Matrix. I made a lucky guess that they were causing the problem.

I did an uninstall of:
.Net framework
.Net SDK
ASP Web Matrix

I deleted the sub folders in c:\Program Files\Microsoft SQL Server.

Then SQL 2000 DE installed successfully, and I reinstalled the .Net framework & ASP Web Matrix.

Hope this helps.

Wednesday, March 21, 2012

From where to download sql MSDE CLIENT TOOLS

Hi,
I am installing MSDE 2000 on client machines. Where can I dowload the client
connectivity tools for MSDE so that users can see and work with thier
databases?
Do I have to download sql sp4 for that? Can someone please send me the link
for downloading the client tools?
Thanks
pmud
Microsoft does not provide any 'client tools' for MSDE.
Users must have an application, or programming environment such as Visual
Studio -or even Access.
There are some third party management tools on the internet -but I don't
recall that any of them where tools for "users can see and work with thier
databases", if by that you mean execute queries, etc.
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"pmud" <pmud@.discussions.microsoft.com> wrote in message
news:520FF8F8-271E-4AE3-84B0-7433C04B9E5A@.microsoft.com...
> Hi,
> I am installing MSDE 2000 on client machines. Where can I dowload the
> client
> connectivity tools for MSDE so that users can see and work with thier
> databases?
> Do I have to download sql sp4 for that? Can someone please send me the
> link
> for downloading the client tools?
> Thanks
> --
> pmud
|||Hi Arnie,
By users seeing the databases , I mean like in Enterpsir Manager, users can
see all the databases by right clicking and can see teh schema of the tables.
Also, I have SQL SErver 2000 CD with valid license. So do I think I can copy
the client tools from there and put it on all machines Ineed MSDE on?
Which files do i need to copy for taking the client tools only?
Thanks
pmud
"Arnie Rowland" wrote:

> Microsoft does not provide any 'client tools' for MSDE.
> Users must have an application, or programming environment such as Visual
> Studio -or even Access.
> There are some third party management tools on the internet -but I don't
> recall that any of them where tools for "users can see and work with thier
> databases", if by that you mean execute queries, etc.
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "pmud" <pmud@.discussions.microsoft.com> wrote in message
> news:520FF8F8-271E-4AE3-84B0-7433C04B9E5A@.microsoft.com...
>
>
|||The client tools you have on your "SQL SErver 2000 CD" are NOT be licensed
as client tools for MSDE.
Do all the of computers that you contemplate needing 'client tools'
currently have a SQL Server Client Access License (CAL)?
I would suggest that you verify with Microsoft licensing before you put your
company/agency at risk.
Licensing -VL Contact
(800) 426-9400
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"pmud" <pmud@.discussions.microsoft.com> wrote in message
news:23129FFE-B1D1-4C97-8E9B-6FE5F9913B7D@.microsoft.com...[vbcol=seagreen]
> Hi Arnie,
> By users seeing the databases , I mean like in Enterpsir Manager, users
> can
> see all the databases by right clicking and can see teh schema of the
> tables.
> Also, I have SQL SErver 2000 CD with valid license. So do I think I can
> copy
> the client tools from there and put it on all machines Ineed MSDE on?
> Which files do i need to copy for taking the client tools only?
> Thanks
> --
> pmud
>
> "Arnie Rowland" wrote:
|||Hi Arni e,
Thanks for your response. I think if we have Process license for sql server
2000, we should be able to install sql server 2000 teself on any no. of
mahcines...without worrying about installing sql msde 2000... What do you
think?
Thanks
pmud
"Arnie Rowland" wrote:

> The client tools you have on your "SQL SErver 2000 CD" are NOT be licensed
> as client tools for MSDE.
> Do all the of computers that you contemplate needing 'client tools'
> currently have a SQL Server Client Access License (CAL)?
> I would suggest that you verify with Microsoft licensing before you put your
> company/agency at risk.
> Licensing -VL Contact
> (800) 426-9400
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "pmud" <pmud@.discussions.microsoft.com> wrote in message
> news:23129FFE-B1D1-4C97-8E9B-6FE5F9913B7D@.microsoft.com...
>
>
|||If you are doing 'new' development, I suggest that you may wish to explore
SQL Server 2005 Developer Edition. Then there will be no question/issue
about client tools and licensing.
I believe the cost is about $50 (US) per developer, and you are allowed to
have as many SQL Servers as necessary to support your development efforts.
For more details:
Licensing -Developer Edition
My understanding of the Developers Edition license is that you are covered
for a Development server, an Integration/Staging server, even a QA/Test
server, local servers on the developers computer, etc. -as long as no one
except developers access those SQL Servers, and as long as each developer
and/or Tester has a Developer Edition License.
For a more definitive answer, check with the VL folks at: (800) 426-9400.
From: http://www.microsoft.com/sql/edition...r/default.mspx
Each license of SQL Server 2005 Developer Edition entitles one developer to
use the software on as many systems as necessary and additional developers
can use the software by purchasing additional licenses.
From:
http://download.microsoft.com/downlo...ensingv1.1.doc
DEVELOPER EDITION
SQL Server Developer Edition is a separate product and is used for
development and testing purposes only. It is licensed per developer or
tester (person).
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"pmud" <pmud@.discussions.microsoft.com> wrote in message
news:BC52F760-BD17-4C22-8DD0-916DDE4BB2B2@.microsoft.com...[vbcol=seagreen]
> Also Arnie, we have sql developer edition too. Do you think I can install
> that on the machines... since this will be for development only,... we
> wont
> be using this developer edition for production.
> Please let me know your thoughts.
> Thanks
> --
> pmud
>
> "Arnie Rowland" wrote:
|||Thanks Arnie. It was helpful.
pmud
"Arnie Rowland" wrote:

> That is not correct. Your 'processor' license allows you to install SQL
> Server on ONE computer, and allow unlimited clients to have access to that
> ONE SQL Server. And you must have one license per CPU in that computer.
> If you have a second SQL Server, it must have its own license.
> I suggest that you may wish to chat with Microsoft licensing to clear up any
> 'uncertainties'. And to also verify what is allowed use for SQL 2000 client
> tools and multiple installations of MSDE.
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "pmud" <pmud@.discussions.microsoft.com> wrote in message
> news:9406756B-9235-4387-B180-2A2ECFECAA9D@.microsoft.com...
>
>
|||Actually, Microsoft does have a tool for administering MSDE
databases. SQL Server Web Data Administrator was developed
with this in mind. You can download it from:
http://www.microsoft.com/downloads/d...displaylang=en
You can find a list of other alternatives, options at:
http://sqlserver2000.databases.aspfa...rver/msde.html
-Sue
On Tue, 26 Sep 2006 11:14:02 -0700, pmud
<pmud@.discussions.microsoft.com> wrote:

>Also Arnie, we have sql developer edition too. Do you think I can install
>that on the machines... since this will be for development only,... we wont
>be using this developer edition for production.
>Please let me know your thoughts.
>Thanks
|||Hi Sue,
Its great to know about the SQL Web Data Admin. I installed it , but then I
go to view the page from http://localhost/webadmin/default.aspx, its showing
me the code instead of the web page.
I know this is happening coz in IIS my web sites are not configured to
regonize to .aspx extension. How to configure IIS to understand .aspx
extension? I know we have to right lick on teh properties for the node called
Web Sites in IIS, then go to Home Diretory tab, click Configuration button at
the bottom, BUt what do I enter in the next window that pulls up , i.e what
will be the executable path for .aspx extension?
Thanks
pmud
"Sue Hoegemeier" wrote:

> Actually, Microsoft does have a tool for administering MSDE
> databases. SQL Server Web Data Administrator was developed
> with this in mind. You can download it from:
> http://www.microsoft.com/downloads/d...displaylang=en
> You can find a list of other alternatives, options at:
> http://sqlserver2000.databases.aspfa...rver/msde.html
> -Sue
> On Tue, 26 Sep 2006 11:14:02 -0700, pmud
> <pmud@.discussions.microsoft.com> wrote:
>
>
|||If you have the .Net framework installed and need to
configure IIS for ASP.Net, you should be able to just run
aspnet_regiis -i
from the framework's folder location and it will do the
necessary steps to configure IIS for ASP.NET
This article addresses the gist of what you would need to
do:
http://support.microsoft.com/?id=306005
-Sue
On Tue, 26 Sep 2006 15:24:02 -0700, pmud
<pmud@.discussions.microsoft.com> wrote:

>Hi Sue,
>Its great to know about the SQL Web Data Admin. I installed it , but then I
>go to view the page from http://localhost/webadmin/default.aspx, its showing
>me the code instead of the web page.
>I know this is happening coz in IIS my web sites are not configured to
>regonize to .aspx extension. How to configure IIS to understand .aspx
>extension? I know we have to right lick on teh properties for the node called
>Web Sites in IIS, then go to Home Diretory tab, click Configuration button at
>the bottom, BUt what do I enter in the next window that pulls up , i.e what
>will be the executable path for .aspx extension?
>Thanks

From where to download sql MSDE CLIENT TOOLS

Hi,
I am installing MSDE 2000 on client machines. Where can I dowload the client
connectivity tools for MSDE so that users can see and work with thier
databases?
Do I have to download sql sp4 for that? Can someone please send me the link
for downloading the client tools?
Thanks
pmudMicrosoft does not provide any 'client tools' for MSDE.
Users must have an application, or programming environment such as Visual
Studio -or even Access.
There are some third party management tools on the internet -but I don't
recall that any of them where tools for "users can see and work with thier
databases", if by that you mean execute queries, etc.
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"pmud" <pmud@.discussions.microsoft.com> wrote in message
news:520FF8F8-271E-4AE3-84B0-7433C04B9E5A@.microsoft.com...
> Hi,
> I am installing MSDE 2000 on client machines. Where can I dowload the
> client
> connectivity tools for MSDE so that users can see and work with thier
> databases?
> Do I have to download sql sp4 for that? Can someone please send me the
> link
> for downloading the client tools?
> Thanks
> --
> pmud|||The client tools you have on your "SQL SErver 2000 CD" are NOT be licensed
as client tools for MSDE.
Do all the of computers that you contemplate needing 'client tools'
currently have a SQL Server Client Access License (CAL)?
I would suggest that you verify with Microsoft licensing before you put your
company/agency at risk.
Licensing -VL Contact
(800) 426-9400
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"pmud" <pmud@.discussions.microsoft.com> wrote in message
news:23129FFE-B1D1-4C97-8E9B-6FE5F9913B7D@.microsoft.com...[vbcol=seagreen]
> Hi Arnie,
> By users seeing the databases , I mean like in Enterpsir Manager, users
> can
> see all the databases by right clicking and can see teh schema of the
> tables.
> Also, I have SQL SErver 2000 CD with valid license. So do I think I can
> copy
> the client tools from there and put it on all machines Ineed MSDE on?
> Which files do i need to copy for taking the client tools only?
> Thanks
> --
> pmud
>
> "Arnie Rowland" wrote:
>|||Hi Arni e,
Thanks for your response. I think if we have Process license for sql server
2000, we should be able to install sql server 2000 teself on any no. of
mahcines...without worrying about installing sql msde 2000... What do you
think?
Thanks
--
pmud
"Arnie Rowland" wrote:

> The client tools you have on your "SQL SErver 2000 CD" are NOT be licensed
> as client tools for MSDE.
> Do all the of computers that you contemplate needing 'client tools'
> currently have a SQL Server Client Access License (CAL)?
> I would suggest that you verify with Microsoft licensing before you put yo
ur
> company/agency at risk.
> Licensing -VL Contact
> (800) 426-9400
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "pmud" <pmud@.discussions.microsoft.com> wrote in message
> news:23129FFE-B1D1-4C97-8E9B-6FE5F9913B7D@.microsoft.com...
>
>|||Also Arnie, we have sql developer edition too. Do you think I can install
that on the machines... since this will be for development only,... we wont
be using this developer edition for production.
Please let me know your thoughts.
Thanks
pmud
"Arnie Rowland" wrote:

> The client tools you have on your "SQL SErver 2000 CD" are NOT be licensed
> as client tools for MSDE.
> Do all the of computers that you contemplate needing 'client tools'
> currently have a SQL Server Client Access License (CAL)?
> I would suggest that you verify with Microsoft licensing before you put yo
ur
> company/agency at risk.
> Licensing -VL Contact
> (800) 426-9400
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "pmud" <pmud@.discussions.microsoft.com> wrote in message
> news:23129FFE-B1D1-4C97-8E9B-6FE5F9913B7D@.microsoft.com...
>
>|||> Thanks for your response. I think if we have Process license for sql
> server
> 2000, we should be able to install sql server 2000 teself on any no. of
> mahcines...without worrying about installing sql msde 2000... What do you
That is not correct. Your 'processor' license allows you to install SQL
Server on ONE computer, and allow unlimited clients to have access to that
ONE SQL Server. And you must have one license per CPU in that computer.
If you have a second SQL Server, it must have its own license.
I suggest that you may wish to chat with Microsoft licensing to clear up any
'uncertainties'. And to also verify what is allowed use for SQL 2000 client
tools and multiple installations of MSDE.
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"pmud" <pmud@.discussions.microsoft.com> wrote in message
news:9406756B-9235-4387-B180-2A2ECFECAA9D@.microsoft.com...[vbcol=seagreen]
> Hi Arni e,
> Thanks for your response. I think if we have Process license for sql
> server
> 2000, we should be able to install sql server 2000 teself on any no. of
> mahcines...without worrying about installing sql msde 2000... What do you
> think?
> Thanks
> --
> pmud
>
> "Arnie Rowland" wrote:
>|||If you are doing 'new' development, I suggest that you may wish to explore
SQL Server 2005 Developer Edition. Then there will be no question/issue
about client tools and licensing.
I believe the cost is about $50 (US) per developer, and you are allowed to
have as many SQL Servers as necessary to support your development efforts.
For more details:
Licensing -Developer Edition
My understanding of the Developers Edition license is that you are covered
for a Development server, an Integration/Staging server, even a QA/Test
server, local servers on the developers computer, etc. -as long as no one
except developers access those SQL Servers, and as long as each developer
and/or Tester has a Developer Edition License.
For a more definitive answer, check with the VL folks at: (800) 426-9400.
From: http://www.microsoft.com/sql/editio...er/default.mspx
Each license of SQL Server 2005 Developer Edition entitles one developer to
use the software on as many systems as necessary and additional developers
can use the software by purchasing additional licenses.
From:
http://download.microsoft.com/downl...censingv1.1.doc
DEVELOPER EDITION
SQL Server Developer Edition is a separate product and is used for
development and testing purposes only. It is licensed per developer or
tester (person).
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"pmud" <pmud@.discussions.microsoft.com> wrote in message
news:BC52F760-BD17-4C22-8DD0-916DDE4BB2B2@.microsoft.com...[vbcol=seagreen]
> Also Arnie, we have sql developer edition too. Do you think I can install
> that on the machines... since this will be for development only,... we
> wont
> be using this developer edition for production.
> Please let me know your thoughts.
> Thanks
> --
> pmud
>
> "Arnie Rowland" wrote:
>|||Thanks Arnie. It was helpful.
pmud
"Arnie Rowland" wrote:

> That is not correct. Your 'processor' license allows you to install SQL
> Server on ONE computer, and allow unlimited clients to have access to that
> ONE SQL Server. And you must have one license per CPU in that computer.
> If you have a second SQL Server, it must have its own license.
> I suggest that you may wish to chat with Microsoft licensing to clear up a
ny
> 'uncertainties'. And to also verify what is allowed use for SQL 2000 clien
t
> tools and multiple installations of MSDE.
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "pmud" <pmud@.discussions.microsoft.com> wrote in message
> news:9406756B-9235-4387-B180-2A2ECFECAA9D@.microsoft.com...
>
>|||Actually, Microsoft does have a tool for administering MSDE
databases. SQL Server Web Data Administrator was developed
with this in mind. You can download it from:
http://www.microsoft.com/downloads/...&displaylang=en
You can find a list of other alternatives, options at:
[url]http://sqlserver2000.databases.aspfaq.com/how-do-i-manage-sql-server/msde.html[/ur
l]
-Sue
On Tue, 26 Sep 2006 11:14:02 -0700, pmud
<pmud@.discussions.microsoft.com> wrote:

>Also Arnie, we have sql developer edition too. Do you think I can install
>that on the machines... since this will be for development only,... we wont
>be using this developer edition for production.
>Please let me know your thoughts.
>Thanks|||Hi Sue,
Its great to know about the SQL Web Data Admin. I installed it , but then I
go to view the page from http://localhost/webadmin/default.aspx, its showing
me the code instead of the web page.
I know this is happening coz in IIS my web sites are not configured to
regonize to .aspx extension. How to configure IIS to understand .aspx
extension? I know we have to right lick on teh properties for the node calle
d
Web Sites in IIS, then go to Home Diretory tab, click Configuration button a
t
the bottom, BUt what do I enter in the next window that pulls up , i.e what
will be the executable path for .aspx extension?
Thanks
--
pmud
"Sue Hoegemeier" wrote:

> Actually, Microsoft does have a tool for administering MSDE
> databases. SQL Server Web Data Administrator was developed
> with this in mind. You can download it from:
> http://www.microsoft.com/downloads/...&displaylang=en
> You can find a list of other alternatives, options at:
> [url]http://sqlserver2000.databases.aspfaq.com/how-do-i-manage-sql-server/msde.html[/
url]
> -Sue
> On Tue, 26 Sep 2006 11:14:02 -0700, pmud
> <pmud@.discussions.microsoft.com> wrote:
>
>

Monday, March 19, 2012

From MySQL to MSSQL 2005

Hello! I'm installing the MSSQL 2005.
And i want to transfrom the DB from my old MySQL DataBase to new MSSQL Database. How can I do this? With Import|Export Utils I can't do this task =(

Pleasure Help me.

ThanksI have the same problem. Anyone know?|||First of all do you have MySQL ODBC driver installed on the same box you have SSIS? If you do - did you create ODBC data source?|||

In my case, the MySQL ODBC driver is installed on the server, and I'm able to create a linked server to the database. The problem is that the only mechinism for ODBC in the Import/Export Wizard is the .NET ODBC provider. When using this provider, the option to "Copy all tables" is greyed out because apparently it can't read the metadata.

Given that i have hundreds of tables to move, it is not helpful.

|||

Eyfel, I think the response I got from my similar question about PostreSQL will answer this one as well.

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=193071&SiteID=1

|||I've MySql ODBC driver 3.51 installed on the same box as SSIS and have created ODBC data source. What now?|||Is this a one time deal? If so, why not use mysqldump to create your scripts to create tables. I believe it even has options to make the DDL consistent with MSSQL.
Once you have the tables created, you should easily be able to import the data.
Larry Pope
|||

That is a good idea, but it still leaves a big problem. After you have the structure built, you still have to create a separate data reader with a sql statement for every table in the database. When you have hundreds of tables, it presents a time challenge. And on top of that, DTS can handle implicit data conversions (like boolean to bit), and SSIS requires explicit conversions for each of these data type changes.

That's why the SQL 2000 DTS Import is still superior, where you can pull the metadata to create the tables and the data transfer in one simple wizard driven setup. Five minutes versus several days or weeks. I just hope they resolve it.

|||

to make a connection I did the following, install Myodbc driver 3.51 from MySQL site Setup an DSN (system or user) from the ODBC options in Admin tools.

Use the import/Export wizard found on right click all tasks on an database in mssql 2005.

Set it as a .net framework provider for ODBC

Enter the following in the connection string

Dsn=DSNNAME;Driver={MYODBC3.dll};database=DATABASE;option=0;pwd=PASSWORD;port=0;

server=SERVER;uid=USERNAME

replace DSNNAME,DATABASE,PASSWORD and USERNAME with your information.

Works a treat.

Alan ;-)

|||

Alan, do you get the option to "Copy all Tables" when you do this? I'm not getting it when I do the same thing. I can use the wizard, but I'm forced to type a sql statement which limits me to one table per import. I need the "Copy all Tables" options so I can copy hundreds of tables fairly easily.

From what I can tell, the OLE ODBC used in SQL 2000 allows me to do this, but the .NET ODBC does not. Let me know if I'm missing something. Otherwise I'm stuck using SQL 2000's DTS indefinitely.

Thanks.

|||

I managed to get the "copy all tables" option enabled in the SSIS import wizard if I use the mysql.oledb connector (from Feb 2001) instead of the ODBC driver. Reads the meta-data fine (so far ...).

Caveat: I'm connecting to a MySql 4.0 DB and still in the experimental stage. Has anybody else gone down this path?

Bill

|||

Issues I've noticed so far with OLEDB:

a) mysql 4.0 date column type is not recognized (requires using "Edit" to change to change dest type from <blank> to Datetime).

b) mysql 4.0 tinyint column type is not recognized (as above, use "Edit" to change type from <blank> to tinyint).

c) meta-data names are displayed with a trailing [] (The square "I don't know what else to print" character) in the wizard. This occurs both in the source table and column names, and of course in the new table and column names (not sure what overall impact this has).

|||

Thanks for posting Bill. One question, how do you get the MySQL OLEODBC driver to show up in your driver list? I have it installed but it does not show up as an available driver.

I appreciate any help you can lend. In SQL 2000 the driver just shows up in the list so I'm not sure what I'm missing.

|||Hi,
just wondering, did anyone manage to get it to work properly?
Daren
|||I ended up using Select Into statements using Linked Servers and Openquery. I ran out of time to find a better solution.

From MySQL to MSSQL 2005

Hello! I'm installing the MSSQL 2005.
And i want to transfrom the DB from my old MySQL DataBase to new MSSQL Database. How can I do this? With Import|Export Utils I can't do this task =(

Pleasure Help me.

ThanksI have the same problem. Anyone know?|||First of all do you have MySQL ODBC driver installed on the same box you have SSIS? If you do - did you create ODBC data source?|||

Given that i have hundreds of tables to move, it is not helpful.

|||

Eyfel, I think the response I got from my similar question about PostreSQL will answer this one as well.

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=193071&SiteID=1

|||

to make a connection I did the following, install Myodbc driver 3.51 from MySQL site Setup an DSN (system or user) from the ODBC options in Admin tools.

Use the import/Export wizard found on right click all tasks on an database in mssql 2005.

Set it as a .net framework provider for ODBC

Enter the following in the connection string

Dsn=DSNNAME;Driver={MYODBC3.dll};database=DATABASE;option=0;pwd=PASSWORD;port=0;

server=SERVER;uid=USERNAME

replace DSNNAME,DATABASE,PASSWORD and USERNAME with your information.

Works a treat.

Alan ;-)

|||

From what I can tell, the OLE ODBC used in SQL 2000 allows me to do this, but the .NET ODBC does not. Let me know if I'm missing something. Otherwise I'm stuck using SQL 2000's DTS indefinitely.

Thanks.

|||

I managed to get the "copy all tables" option enabled in the SSIS import wizard if I use the mysql.oledb connector (from Feb 2001) instead of the ODBC driver. Reads the meta-data fine (so far ...).

Caveat: I'm connecting to a MySql 4.0 DB and still in the experimental stage. Has anybody else gone down this path?

Bill

|||

Issues I've noticed so far with OLEDB:

a) mysql 4.0 date column type is not recognized (requires using "Edit" to change to change dest type from <blank> to Datetime).

b) mysql 4.0 tinyint column type is not recognized (as above, use "Edit" to change type from <blank> to tinyint).

|||

Thanks for posting Bill. One question, how do you get the MySQL OLEODBC driver to show up in your driver list? I have it installed but it does not show up as an available driver.

I appreciate any help you can lend. In SQL 2000 the driver just shows up in the list so I'm not sure what I'm missing.

|||Hi,
just wondering, did anyone manage to get it to work properly?
Daren
|||I ended up using Select Into statements using Linked Servers and Openquery. I ran out of time to find a better solution.

From MySQL to MSSQL 2005

Hello! I'm installing the MSSQL 2005.
And i want to transfrom the DB from my old MySQL DataBase to new MSSQL Database. How can I do this? With Import|Export Utils I can't do this task =(

Pleasure Help me.

ThanksI have the same problem. Anyone know?|||First of all do you have MySQL ODBC driver installed on the same box you have SSIS? If you do - did you create ODBC data source?|||

Given that i have hundreds of tables to move, it is not helpful.

|||

Eyfel, I think the response I got from my similar question about PostreSQL will answer this one as well.

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=193071&SiteID=1

|||I've MySql ODBC driver 3.51 installed on the same box as SSIS and have created ODBC data source. What now?|||Is this a one time deal? If so, why not use mysqldump to create

your scripts to create tables. I believe it even has options to

make the DDL consistent with MSSQL.

Once you have the tables created, you should easily be able to import the data.

Larry Pope|||

|||

to make a connection I did the following, install Myodbc driver 3.51 from MySQL site Setup an DSN (system or user) from the ODBC options in Admin tools.

Use the import/Export wizard found on right click all tasks on an database in mssql 2005.

Set it as a .net framework provider for ODBC

Enter the following in the connection string

Dsn=DSNNAME;Driver={MYODBC3.dll};database=DATABASE;option=0;pwd=PASSWORD;port=0;

server=SERVER;uid=USERNAME

replace DSNNAME,DATABASE,PASSWORD and USERNAME with your information.

Works a treat.

Alan ;-)

|||

From what I can tell, the OLE ODBC used in SQL 2000 allows me to do this, but the .NET ODBC does not. Let me know if I'm missing something. Otherwise I'm stuck using SQL 2000's DTS indefinitely.

Thanks.

|||

I managed to get the "copy all tables" option enabled in the SSIS import wizard if I use the mysql.oledb connector (from Feb 2001) instead of the ODBC driver. Reads the meta-data fine (so far ...).

Caveat: I'm connecting to a MySql 4.0 DB and still in the experimental stage. Has anybody else gone down this path?

Bill

|||

Issues I've noticed so far with OLEDB:

a) mysql 4.0 date column type is not recognized (requires using "Edit" to change to change dest type from <blank> to Datetime).

b) mysql 4.0 tinyint column type is not recognized (as above, use "Edit" to change type from <blank> to tinyint).

|||

Thanks for posting Bill. One question, how do you get the MySQL OLEODBC driver to show up in your driver list? I have it installed but it does not show up as an available driver.

I appreciate any help you can lend. In SQL 2000 the driver just shows up in the list so I'm not sure what I'm missing.

|||Hi,

just wondering, did anyone manage to get it to work properly?

Daren|||I ended up using Select Into statements using Linked Servers and Openquery. I ran out of time to find a better solution.

From MySQL to MSSQL 2005

Hello! I'm installing the MSSQL 2005.
And i want to transfrom the DB from my old MySQL DataBase to new MSSQL Database. How can I do this? With Import|Export Utils I can't do this task =(

Pleasure Help me.

ThanksI have the same problem. Anyone know?|||First of all do you have MySQL ODBC driver installed on the same box you have SSIS? If you do - did you create ODBC data source?|||

Given that i have hundreds of tables to move, it is not helpful.

|||

Eyfel, I think the response I got from my similar question about PostreSQL will answer this one as well.

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=193071&SiteID=1

|||

to make a connection I did the following, install Myodbc driver 3.51 from MySQL site Setup an DSN (system or user) from the ODBC options in Admin tools.

Use the import/Export wizard found on right click all tasks on an database in mssql 2005.

Set it as a .net framework provider for ODBC

Enter the following in the connection string

Dsn=DSNNAME;Driver={MYODBC3.dll};database=DATABASE;option=0;pwd=PASSWORD;port=0;

server=SERVER;uid=USERNAME

replace DSNNAME,DATABASE,PASSWORD and USERNAME with your information.

Works a treat.

Alan ;-)

|||

From what I can tell, the OLE ODBC used in SQL 2000 allows me to do this, but the .NET ODBC does not. Let me know if I'm missing something. Otherwise I'm stuck using SQL 2000's DTS indefinitely.

Thanks.

|||

I managed to get the "copy all tables" option enabled in the SSIS import wizard if I use the mysql.oledb connector (from Feb 2001) instead of the ODBC driver. Reads the meta-data fine (so far ...).

Caveat: I'm connecting to a MySql 4.0 DB and still in the experimental stage. Has anybody else gone down this path?

Bill

|||

Issues I've noticed so far with OLEDB:

a) mysql 4.0 date column type is not recognized (requires using "Edit" to change to change dest type from <blank> to Datetime).

b) mysql 4.0 tinyint column type is not recognized (as above, use "Edit" to change type from <blank> to tinyint).

|||

Thanks for posting Bill. One question, how do you get the MySQL OLEODBC driver to show up in your driver list? I have it installed but it does not show up as an available driver.

I appreciate any help you can lend. In SQL 2000 the driver just shows up in the list so I'm not sure what I'm missing.

|||Hi,
just wondering, did anyone manage to get it to work properly?
Daren
|||I ended up using Select Into statements using Linked Servers and Openquery. I ran out of time to find a better solution.

From MySQL to MSSQL 2005

Hello! I'm installing the MSSQL 2005.
And i want to transfrom the DB from my old MySQL DataBase to new MSSQL Database. How can I do this? With Import|Export Utils I can't do this task =(

Pleasure Help me.

ThanksI have the same problem. Anyone know?|||First of all do you have MySQL ODBC driver installed on the same box you have SSIS? If you do - did you create ODBC data source?|||

Given that i have hundreds of tables to move, it is not helpful.

|||

Eyfel, I think the response I got from my similar question about PostreSQL will answer this one as well.

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=193071&SiteID=1

|||I've MySql ODBC driver 3.51 installed on the same box as SSIS and have created ODBC data source. What now?|||Is this a one time deal? If so, why not use mysqldump to create

your scripts to create tables. I believe it even has options to

make the DDL consistent with MSSQL.

Once you have the tables created, you should easily be able to import the data.

Larry Pope|||

|||

to make a connection I did the following, install Myodbc driver 3.51 from MySQL site Setup an DSN (system or user) from the ODBC options in Admin tools.

Use the import/Export wizard found on right click all tasks on an database in mssql 2005.

Set it as a .net framework provider for ODBC

Enter the following in the connection string

Dsn=DSNNAME;Driver={MYODBC3.dll};database=DATABASE;option=0;pwd=PASSWORD;port=0;

server=SERVER;uid=USERNAME

replace DSNNAME,DATABASE,PASSWORD and USERNAME with your information.

Works a treat.

Alan ;-)

|||

From what I can tell, the OLE ODBC used in SQL 2000 allows me to do this, but the .NET ODBC does not. Let me know if I'm missing something. Otherwise I'm stuck using SQL 2000's DTS indefinitely.

Thanks.

|||

I managed to get the "copy all tables" option enabled in the SSIS import wizard if I use the mysql.oledb connector (from Feb 2001) instead of the ODBC driver. Reads the meta-data fine (so far ...).

Caveat: I'm connecting to a MySql 4.0 DB and still in the experimental stage. Has anybody else gone down this path?

Bill

|||

Issues I've noticed so far with OLEDB:

a) mysql 4.0 date column type is not recognized (requires using "Edit" to change to change dest type from <blank> to Datetime).

b) mysql 4.0 tinyint column type is not recognized (as above, use "Edit" to change type from <blank> to tinyint).

|||

Thanks for posting Bill. One question, how do you get the MySQL OLEODBC driver to show up in your driver list? I have it installed but it does not show up as an available driver.

I appreciate any help you can lend. In SQL 2000 the driver just shows up in the list so I'm not sure what I'm missing.

|||Hi,

just wondering, did anyone manage to get it to work properly?

Daren|||I ended up using Select Into statements using Linked Servers and Openquery. I ran out of time to find a better solution.

From MySQL to MSSQL 2005

Hello! I'm installing the MSSQL 2005.
And i want to transfrom the DB from my old MySQL DataBase to new MSSQL Database. How can I do this? With Import|Export Utils I can't do this task =(

Pleasure Help me.

ThanksI have the same problem. Anyone know?|||First of all do you have MySQL ODBC driver installed on the same box you have SSIS? If you do - did you create ODBC data source?|||

Given that i have hundreds of tables to move, it is not helpful.

|||

Eyfel, I think the response I got from my similar question about PostreSQL will answer this one as well.

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=193071&SiteID=1

|||I've MySql ODBC driver 3.51 installed on the same box as SSIS and have created ODBC data source. What now?|||Is this a one time deal? If so, why not use mysqldump to create

your scripts to create tables. I believe it even has options to

make the DDL consistent with MSSQL.

Once you have the tables created, you should easily be able to import the data.

Larry Pope|||

|||

to make a connection I did the following, install Myodbc driver 3.51 from MySQL site Setup an DSN (system or user) from the ODBC options in Admin tools.

Use the import/Export wizard found on right click all tasks on an database in mssql 2005.

Set it as a .net framework provider for ODBC

Enter the following in the connection string

Dsn=DSNNAME;Driver={MYODBC3.dll};database=DATABASE;option=0;pwd=PASSWORD;port=0;

server=SERVER;uid=USERNAME

replace DSNNAME,DATABASE,PASSWORD and USERNAME with your information.

Works a treat.

Alan ;-)

|||

From what I can tell, the OLE ODBC used in SQL 2000 allows me to do this, but the .NET ODBC does not. Let me know if I'm missing something. Otherwise I'm stuck using SQL 2000's DTS indefinitely.

Thanks.

|||

I managed to get the "copy all tables" option enabled in the SSIS import wizard if I use the mysql.oledb connector (from Feb 2001) instead of the ODBC driver. Reads the meta-data fine (so far ...).

Caveat: I'm connecting to a MySql 4.0 DB and still in the experimental stage. Has anybody else gone down this path?

Bill

|||

Issues I've noticed so far with OLEDB:

a) mysql 4.0 date column type is not recognized (requires using "Edit" to change to change dest type from <blank> to Datetime).

b) mysql 4.0 tinyint column type is not recognized (as above, use "Edit" to change type from <blank> to tinyint).

|||

Thanks for posting Bill. One question, how do you get the MySQL OLEODBC driver to show up in your driver list? I have it installed but it does not show up as an available driver.

I appreciate any help you can lend. In SQL 2000 the driver just shows up in the list so I'm not sure what I'm missing.

|||Hi,

just wondering, did anyone manage to get it to work properly?

Daren|||I ended up using Select Into statements using Linked Servers and Openquery. I ran out of time to find a better solution.

From MySQL to MSSQL 2005

Hello! I'm installing the MSSQL 2005.
And i want to transfrom the DB from my old MySQL DataBase to new MSSQL Database. How can I do this? With Import|Export Utils I can't do this task =(

Pleasure Help me.

ThanksI have the same problem. Anyone know?|||First of all do you have MySQL ODBC driver installed on the same box you have SSIS? If you do - did you create ODBC data source?|||

Given that i have hundreds of tables to move, it is not helpful.

|||

Eyfel, I think the response I got from my similar question about PostreSQL will answer this one as well.

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=193071&SiteID=1

|||

to make a connection I did the following, install Myodbc driver 3.51 from MySQL site Setup an DSN (system or user) from the ODBC options in Admin tools.

Use the import/Export wizard found on right click all tasks on an database in mssql 2005.

Set it as a .net framework provider for ODBC

Enter the following in the connection string

Dsn=DSNNAME;Driver={MYODBC3.dll};database=DATABASE;option=0;pwd=PASSWORD;port=0;

server=SERVER;uid=USERNAME

replace DSNNAME,DATABASE,PASSWORD and USERNAME with your information.

Works a treat.

Alan ;-)

|||

From what I can tell, the OLE ODBC used in SQL 2000 allows me to do this, but the .NET ODBC does not. Let me know if I'm missing something. Otherwise I'm stuck using SQL 2000's DTS indefinitely.

Thanks.

|||

I managed to get the "copy all tables" option enabled in the SSIS import wizard if I use the mysql.oledb connector (from Feb 2001) instead of the ODBC driver. Reads the meta-data fine (so far ...).

Caveat: I'm connecting to a MySql 4.0 DB and still in the experimental stage. Has anybody else gone down this path?

Bill

|||

Issues I've noticed so far with OLEDB:

a) mysql 4.0 date column type is not recognized (requires using "Edit" to change to change dest type from <blank> to Datetime).

b) mysql 4.0 tinyint column type is not recognized (as above, use "Edit" to change type from <blank> to tinyint).

|||

Thanks for posting Bill. One question, how do you get the MySQL OLEODBC driver to show up in your driver list? I have it installed but it does not show up as an available driver.

I appreciate any help you can lend. In SQL 2000 the driver just shows up in the list so I'm not sure what I'm missing.

|||Hi,
just wondering, did anyone manage to get it to work properly?
Daren
|||I ended up using Select Into statements using Linked Servers and Openquery. I ran out of time to find a better solution.

Friday, March 23, 2012

Frustrating Installation Error

Frustrating Installation Error

Wednesday, March 21, 2012

From where to download sql MSDE CLIENT TOOLS

From where to download sql MSDE CLIENT TOOLS

Monday, March 19, 2012

From MySQL to MSSQL 2005

From MySQL to MSSQL 2005

From MySQL to MSSQL 2005

From MySQL to MSSQL 2005

From MySQL to MSSQL 2005

From MySQL to MSSQL 2005

From MySQL to MSSQL 2005

Get Next Number

Blog Archive

About Me