Install security patch ms03-031 on sql2k sp3 server

Tried to install security patch ms03-031 on sql2k sp3
server, but got message said that there is no valid
instance for the patch. Anyone else had this problem?I would first run Select @.@.version from Query Analyzer to verify that the
version is 2000.8.00.760 (SP3)
Rand
This posting is provided "as is" with no warranties and confers no rights.|||Thanks for the response, Rand.
Yes, I did that and even tried to reapply sp3 but still
can't install that patch with same message. Any other
reasons?
>--Original Message--
>I would first run Select @.@.version from Query Analyzer to
verify that the
>version is 2000.8.00.760 (SP3)
>Rand
>This posting is provided "as is" with no warranties and
confers no rights.
>.
>|||Check the registry for the version number.
HKLM\Software\Microsoft\MSSQLServer\MSSQLServer\CurrentVersion\CSDVersion.
Make sure it also say 8.00.760
Rand.
This posting is provided "as is" with no warranties and confers no rights.|||Thanks for the response, Rand. That was first thing I do
and it returned correct result. I even tried reapply sp3
but still got message said that can't find instance for
the patch. Any other reasons?
>--Original Message--
>I would first run Select @.@.version from Query Analyzer to
verify that the
>version is 2000.8.00.760 (SP3)
>Rand
>This posting is provided "as is" with no warranties and
confers no rights.
>.
>|||It says 8.00.534, I changed it to 8.00.760 but still
doesn't let me apply the patch.
>--Original Message--
>Check the registry for the version number.
>HKLM\Software\Microsoft\MSSQLServer\MSSQLServer\CurrentVer
sion\CSDVersion.
>Make sure it also say 8.00.760
>Rand.
>This posting is provided "as is" with no warranties and
confers no rights.
>.
>

Install of MSDE on XP Pro Failed, HELP Please ANYONE!

I have for the past 1.5 weeks been trying to get MSDE installed on a Windows
XP computer. We are installing MSDE sp3 which we have installed on more
than 20+ computers. Some computers Windows 2003 Servers some Windows XP
Pro. We have NEVER had a problem. So before anyone suggest it, I don't
think going to MSDE sp4 will help with this problem. We have formatted the
computer MANY times and started over. We have updated with ALL of the
Windows update and it did not work. We formatted and install only SP2 on
Windows XP. We have taken off all other software, virus scanners, office,
etc. The computer is BLANK. It is on the network and I am remote
desktopped in when I try to install. Now I have done this MANY time remote
desktopped to a machine and no problem. We have made sure that network
items like File and Print Sharing are on. I have tried to install as the
administrator of the computer, as a user who have administrative priveleges,
etc. This computer is a Windows XP computer, not on a domain, the software
is XP Pro, and everything looks good. I am at a lost.
When I install I have it dump out the logs, here is some of the log I get,
it is
to long to post all of it. I have also added the SQL
Error logs that are left below this log. Then below that I have attached
the cnfgsvr.out
Any help is GREATLY appriecated, I can not blank out and install XP any
more.
=== Verbose logging started: 7/25/2007 17:43:02 Build type: SHIP UNICODE
3.00.3790.2180 Calling process: C:\WINDOWS\system32\msiexec.exe ===
MSI (c) (10:C0) [17:43:02:687]: Resetting cached policy values
MSI (c) (10:C0) [17:43:02:687]: Machine policy value 'Debug' is 0
MSI (c) (10:C0) [17:43:02:687]: ******* RunEngine:
******* Product: C:\ONSInstall\sql2ksp3\MSDE\Setup\SqlRun01.msi
******* Action:
******* CommandLine: **********
MSI (c) (10:C0) [17:43:02:718]: Machine policy value 'DisableUserInstalls'
is 0
MSI (c) (10:C0) [17:43:02:843]: SOFTWARE RESTRICTION POLICY: Verifying
package --> 'C:\ONSInstall\sql2ksp3\MSDE\Setup\SqlRun01.msi' against
software restriction policy
MSI (c) (10:C0) [17:43:02:843]: Note: 1: 2262 2: DigitalSignature
3: -2147287038
MSI (c) (10:C0) [17:43:02:843]: SOFTWARE RESTRICTION POLICY:
C:\ONSInstall\sql2ksp3\MSDE\Setup\SqlRun01.msi is not digitally signed
MSI (c) (10:C0) [17:43:02:843]: SOFTWARE RESTRICTION POLICY:
C:\ONSInstall\sql2ksp3\MSDE\Setup\SqlRun01.msi is permitted to run at the
'unrestricted' authorization level.
MSI (c) (10:C0) [17:43:02:968]: Cloaking enabled.
MSI (c) (10:C0) [17:43:02:968]: Attempting to enable all disabled priveleges
before calling Install on Server
MSI (c) (10:C0) [17:43:03:000]: End dialog not enabled
MSI (c) (10:C0) [17:43:03:000]: Original package ==>
C:\ONSInstall\sql2ksp3\MSDE\Setup\SqlRun01.msi
MSI (c) (10:C0) [17:43:03:000]: Package we're running from ==>
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\2557a1.msi
MSI (c) (10:C0) [17:43:03:015]: APPCOMPAT: looking for appcompat database
entry with ProductCode '{E09B48B5-E141-427A-AB0C-D3605127224A}'.
MSI (c) (10:C0) [17:43:03:015]: APPCOMPAT: no matching ProductCode found in
database.
MSI (c) (10:C0) [17:43:03:015]: MSCOREE not loaded loading copy from
system32
MSI (c) (10:C0) [17:43:03:015]: Machine policy value 'TransformsSecure' is 0
MSI (c) (10:C0) [17:43:03:015]: User policy value 'TransformsAtSource' is 0
MSI (c) (10:C0) [17:43:03:015]: Note: 1: 2205 2: 3: MsiFileHash
MSI (c) (10:C0) [17:43:03:015]: Machine policy value 'DisablePatch' is 0
MSI (c) (10:C0) [17:43:03:015]: Machine policy value 'AllowLockdownPatch' is
0
MSI (c) (10:C0) [17:43:03:015]: Machine policy value 'DisableLUAPatching' is
0
MSI (c) (10:C0) [17:43:03:015]: Machine policy value
'DisableFlyWeightPatching' is 0
MSI (c) (10:C0) [17:43:03:015]: APPCOMPAT: looking for appcompat database
entry with ProductCode '{E09B48B5-E141-427A-AB0C-D3605127224A}'.
MSI (c) (10:C0) [17:43:03:015]: APPCOMPAT: no matching ProductCode found in
database.
MSI (c) (10:C0) [17:43:03:015]: Transforms are not secure.
MSI (c) (10:C0) [17:43:03:015]: Note: 1: 2262 2: Control 3: -2147287038
MSI (c) (10:C0) [17:43:03:015]: Command Line: instancename=ThinkHealth
SECURITYMODE=SQL SA...
MSI (c) (10:C0) [17:43:03:015]: PROPERTY CHANGE: Adding PackageCode
property. Its value is '{D29DCF7A-8199-4373-BA0D-2F3635EC940C}'.
MSI (c) (10:C0) [17:43:03:015]: Product Code passed to Engine.Initialize:
''
MSI (c) (10:C0) [17:43:03:015]: Product Code from property table before
transforms: '{E09B48B5-E141-427A-AB0C-D3605127224A}'
MSI (c) (10:C0) [17:43:03:015]: Product Code from property table after
transforms: '{E09B48B5-E141-427A-AB0C-D3605127224A}'
MSI (c) (10:C0) [17:43:03:015]: Product not registered: beginning first-time
install
MSI (c) (10:C0) [17:43:03:015]: PROPERTY CHANGE: Adding ProductState
property. Its value is '-1'.
MSI (c) (10:C0) [17:43:03:015]: Entering
CMsiConfigurationManager::SetLastUsedSource.
MSI (c) (10:C0) [17:43:03:015]: User policy value 'SearchOrder' is 'nmu'
MSI (c) (10:C0) [17:43:03:015]: Adding new sources is allowed.
MSI (c) (10:C0) [17:43:03:015]: PROPERTY CHANGE: Adding PackagecodeChanging
property. Its value is '1'.
MSI (c) (10:C0) [17:43:03:015]: Package name extracted from package path:
'SqlRun01.msi'
MSI (c) (10:C0) [17:43:03:015]: Package to be registered: 'SqlRun01.msi'
MSI (c) (10:C0) [17:43:03:031]: Note: 1: 2262 2: AdminProperties
3: -2147287038
MSI (c) (10:C0) [17:43:03:031]: Machine policy value 'DisableMsi' is 0
MSI (c) (10:C0) [17:43:03:031]: Machine policy value 'AlwaysInstallElevated'
is 0
MSI (c) (10:C0) [17:43:03:031]: User policy value 'AlwaysInstallElevated' is
0
MSI (c) (10:C0) [17:43:03:031]: Product installation will be elevated
because user is admin and product is being installed per-machine.
MSI (c) (10:C0) [17:43:03:031]: Running product
'{E09B48B5-E141-427A-AB0C-D3605127224A}' with elevated privileges: Product
is assigned.
*********************************
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
TempFolder is
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\
Loading extended custom action library
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sqlcax.dll
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
Starting custom action InstallPerfMon
Registering performance counters from sqlctr.ini
MSI (s) (00:4C) [17:43:38:156]: Executing op:
ActionStart(Name=InstallSQLAdHlp.2D02443E_7002_4C0 B_ABC9_EAB2C064397B,,)
MSI (s) (00:4C) [17:43:38:156]: Executing op:
CustomActionSchedule(Action=InstallSQLAdHlp.2D0244 3E_7002_4C0B_ABC9_EAB2C064397B,ActionType=1025,Sou rce=BinaryData,Target=InstallSQLAdHlp,)
MSI (s) (00:BC) [17:43:38:171]: Invoking remote custom action. DLL:
C:\WINDOWS\Installer\MSI2A.tmp, Entrypoint: InstallSQLAdHlp
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
TempFolder is
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\
Loading extended custom action library
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sqlcax.dll
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
Starting custom action CallSQLAdHlp
C:\Program Files\Microsoft SQL Server\80\Tools\Binn\sqladhlp.exe : 0
MSI (s) (00:4C) [17:43:38:593]: Executing op:
ActionStart(Name=RollbackAgentSecurity.2D02443E_70 02_4C0B_ABC9_EAB2C064397B,,)
MSI (s) (00:4C) [17:43:38:593]: Executing op:
CustomActionSchedule(Action=RollbackAgentSecurity. 2D02443E_7002_4C0B_ABC9_EAB2C064397B,ActionType=12 81,Source=BinaryData,Target=UnInstSQLAgentSecurity ,)
MSI (s) (00:4C) [17:43:38:593]: Executing op:
ActionStart(Name=InstallAgentSecurity.2D02443E_700 2_4C0B_ABC9_EAB2C064397B,,)
MSI (s) (00:4C) [17:43:38:593]: Executing op:
CustomActionSchedule(Action=InstallAgentSecurity.2 D02443E_7002_4C0B_ABC9_EAB2C064397B,ActionType=102 5,Source=BinaryData,Target=InstallSQLAgentSecurity ,)
MSI (s) (00:90) [17:43:38:609]: Invoking remote custom action. DLL:
C:\WINDOWS\Installer\MSI2B.tmp, Entrypoint: InstallSQLAgentSecurity
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
TempFolder is
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\
Loading extended custom action library
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sqlcax.dll
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
Starting custom action InstallSQLAgentSecurity
InstallSQLAgentSecurity succeeded
MSI (s) (00:4C) [17:43:38:671]: Executing op:
ActionStart(Name=SkuIt.2D02443E_7002_4C0B_ABC9_EAB 2C064397B,,)
MSI (s) (00:4C) [17:43:38:687]: Executing op:
CustomActionSchedule(Action=SkuIt.2D02443E_7002_4C 0B_ABC9_EAB2C064397B,ActionType=1025,Source=Binary Data,Target=SkuIt,)
MSI (s) (00:78) [17:43:38:687]: Invoking remote custom action. DLL:
C:\WINDOWS\Installer\MSI2C.tmp, Entrypoint: SkuIt
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
TempFolder is
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\
Loading extended custom action library
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sqlcax.dll
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
Starting custom action SkuIt
MSI (s) (00:4C) [17:43:38:796]: Executing op:
ActionStart(Name=ConfigServer.2D02443E_7002_4C0B_A BC9_EAB2C064397B...
MSI (s) (00:4C) [17:43:38:796]: Executing op:
CustomActionSchedule(Action=ConfigServer.2D02443E_ 7002_4C0B_ABC9_EAB2C064397B...
MSI (s) (00:10) [17:43:38:796]: Invoking remote custom action. DLL:
C:\WINDOWS\Installer\MSI2D.tmp, Entrypoint: ConfigServer
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
TempFolder is
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\
Loading extended custom action library
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sqlcax.dll
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
Starting custom action ConfigServer
Executing "C:\Program Files\Microsoft SQL
Server\80\Tools\Binn\cnfgsvr.exe -V 1 -M 1 -U sa -I "THINKHEALTH" -Q
"SQL_Latin1_General_CP1_CI_AS""
MSI (c) (10:50) [17:45:59:531]: Font created. Charset: Req=0, Ret=0, Font:
Req=MS Shell Dlg, Ret=MS Shell Dlg
Setup failed to configure the server. Refer to the server error logs and
setup error logs for more information.
MSI (s) (00!F4) [17:46:12:140]: Product: Microsoft SQL Server Desktop
Engine -- Setup failed to configure the server. Refer to the server error
logs and setup error logs for more information.
Action ended 17:46:12: InstallFinalize. Return value 3.
MSI (s) (00:4C) [17:46:12:171]: User policy value 'DisableRollback' is 0
MSI (s) (00:4C) [17:46:12:171]: Machine policy value 'DisableRollback' is 0
MSI (s) (00:4C) [17:46:12:187]: Executing op:
Header(Signature=1397708873,Version=300,Timestamp= 922324328,LangId=1033,Platform=0,ScriptType=2,Scri ptMajorVersion=21,ScriptMinorVersion=4,ScriptAttri butes=1)
MSI (s) (00:4C) [17:46:12:187]: Executing op:
DialogInfo(Type=0,Argument=1033)
MSI (s) (00:4C) [17:46:12:187]: Executing op:
DialogInfo(Type=1,Argument=Microsoft SQL Server Desktop Engine)
MSI (s) (00:4C) [17:46:12:187]: Executing op:
RollbackInfo(,RollbackAction=Rollback,RollbackDesc ription=Rolling back
action:,RollbackTemplate=[1],CleanupAction=RollbackCleanup,CleanupDescription= Removing
backup files,CleanupTemplate=File: [1])
MSI (s) (00:4C) [17:46:12:203]: Executing op:
ActionStart(Name=ConfigServer.2D02443E_7002_4C0B_A BC9_EAB2C064397B...
MSI (s) (00:4C) [17:46:12:203]: Executing op:
ProductInfo(ProductKey={E09B48B5-E141-427A-AB0C-D3605127224A},ProductName=Microsoft
SQL Server Desktop
Engine,PackageName=SqlRun01.msi,Language=1033,Vers ion=134218489,Assignment=1,ObsoleteArg=0,,,Package Code={D29DCF7A-8199-4373-BA0D-2F3635EC940C},,,InstanceType=0,LUASetting=0)
MSI (s) (00:4C) [17:46:12:203]: Executing op:
ActionStart(Name=SkuIt.2D02443E_7002_4C0B_ABC9_EAB 2C064397B,,)
MSI (s) (00:4C) [17:46:12:203]: Executing op:
ActionStart(Name=InstallAgentSecurity.2D02443E_700 2_4C0B_ABC9_EAB2C064397B,,)
MSI (s) (00:4C) [17:46:12:203]: Executing op:
ActionStart(Name=RollbackAgentSecurity.2D02443E_70 02_4C0B_ABC9_EAB2C064397B,,)
MSI (s) (00:4C) [17:46:12:203]: Executing op:
CustomActionRollback(Action=RollbackAgentSecurity. 2D02443E_7002_4C0B_ABC9_EAB2C064397B,ActionType=12 81,Source=BinaryData,Target=UnInstSQLAgentSecurity ,)
MSI (s) (00:28) [17:46:12:218]: Invoking remote custom action. DLL:
C:\WINDOWS\Installer\MSI2E.tmp, Entrypoint: UnInstSQLAgentSecurity
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
TempFolder is
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\
Loading extended custom action library
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sqlcax.dll
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
Starting custom action UnInstSQLAgentSecurity
Starting custom action UnInstSQLAgentSecurity
************************************************** ***
Property(S): ProductState = -1
Property(S): PackagecodeChanging = 1
Property(S): INSTANCENAME = ThinkHealth
Property(S): SA...
Property(S): SECURITYMODE = SQL
Property(S): CURRENTDIRECTORY = C:\ONSInstall\sql2ksp3\MSDE
Property(S): CLIENTUILEVEL = 0
Property(S): CLIENTPROCESSID = 1808
Property(S): USERNAME = Discovery
Property(S): COMPANYNAME = Discovery-uttuwah
Property(S): ACTION = INSTALL
Property(S): VersionDatabase = 110
Property(S): VersionMsi = 3.00
Property(S): WindowsBuild = 2600
Property(S): ServicePackLevel = 2
Property(S): ServicePackLevelMinor = 0
Property(S): MsiNTProductType = 1
Property(S): WindowsFolder = C:\WINDOWS\
Property(S): WindowsVolume = C:\
Property(S): System16Folder = C:\WINDOWS\system\
Property(S): RemoteAdminTS = 1
Property(S): TempFolder = C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\
Property(S): ProgramFilesFolder = C:\Program Files\
Property(S): CommonFilesFolder = C:\Program Files\Common Files\
Property(S): AppDataFolder = C:\Documents and
Settings\Administrator\Application Data\
Property(S): FavoritesFolder = C:\Documents and
Settings\Administrator\Favorites\
Property(S): NetHoodFolder = C:\Documents and
Settings\Administrator\NetHood\
Property(S): PersonalFolder = C:\Documents and Settings\Administrator\My
Documents\
Property(S): PrintHoodFolder = C:\Documents and
Settings\Administrator\PrintHood\
Property(S): RecentFolder = C:\Documents and Settings\Administrator\Recent\
Property(S): SendToFolder = C:\Documents and Settings\Administrator\SendTo\
Property(S): TemplateFolder = C:\Documents and Settings\All Users\Templates\
Property(S): CommonAppDataFolder = C:\Documents and Settings\All
Users\Application Data\
Property(S): LocalAppDataFolder = C:\Documents and
Settings\Administrator\Local Settings\Application Data\
Property(S): MyPicturesFolder = C:\Documents and Settings\Administrator\My
Documents\My Pictures\
Property(S): AdminToolsFolder = C:\Documents and Settings\All Users\Start
Menu\Programs\Administrative Tools\
Property(S): StartupFolder = C:\Documents and Settings\All Users\Start
Menu\Programs\Startup\
Property(S): ProgramMenuFolder = C:\Documents and Settings\All Users\Start
Menu\Programs\
Property(S): StartMenuFolder = C:\Documents and Settings\All Users\Start
Menu\
Property(S): DesktopFolder = C:\Documents and Settings\All Users\Desktop\
Property(S): FontsFolder = C:\WINDOWS\Fonts\
Property(S): GPTSupport = 1
Property(S): OLEAdvtSupport = 1
Property(S): ShellAdvtSupport = 1
Property(S): Intel = 15
Property(S): PhysicalMemory = 447
Property(S): VirtualMemory = 933
Property(S): AdminUser = 1
Property(S): LogonUser = Administrator
Property(S): UserSID = S-1-5-21-1202660629-1450960922-725345543-500
Property(S): UserLanguageID = 1033
Property(S): ComputerName = DISCOVSERVER
Property(S): SystemLanguageID = 1033
Property(S): ScreenX = 1024
Property(S): ScreenY = 768
Property(S): CaptionHeight = 26
Property(S): BorderTop = 1
Property(S): BorderSide = 1
Property(S): TextHeight = 16
Property(S): ColorBits = 32
Property(S): TTCSupport = 1
Property(S): MsiWin32AssemblySupport = 5.1.2600.2180
Property(S): RedirectedDllSupport = 2
Property(S): Time = 17:46:21
Property(S): Date = 7/25/2007
Property(S): Privileged = 1
Property(S): DATABASE = C:\WINDOWS\Installer\255937.msi
Property(S): OriginalDatabase =
C:\ONSInstall\sql2ksp3\MSDE\Setup\SqlRun01.msi
Property(S): UILevel = 3
Property(S): AgentServiceName = SQLAgent$THINKHEALTH
Property(S): InstanceRegKey = Microsoft SQL Server\THINKHEALTH
Property(S): InstanceSubDir = MSSQL$THINKHEALTH
Property(S): SqlPerfMonRegKey = SQLCTR$THINKHEALTH
Property(S): SQLServiceName = MSSQL$THINKHEALTH
Property(S): SqlStates = 0
Property(S): ROOTDRIVE = C:\
Property(S): CostingComplete = 1
Property(S): OutOfDiskSpace = 0
Property(S): OutOfNoRbDiskSpace = 0
Property(S): PrimaryVolumeSpaceAvailable = 0
Property(S): PrimaryVolumeSpaceRequired = 0
Property(S): PrimaryVolumeSpaceRemaining = 0
Property(S): SqlFeature = SqlRun
Property(S): SOURCEDIR = C:\ONSInstall\sql2ksp3\MSDE\Setup\
Property(S): SourcedirProduct = {E09B48B5-E141-427A-AB0C-D3605127224A}
Property(S): ProductToBeRegistered = 1
MSI (s) (00:4C) [17:46:21:453]: MainEngineThread is returning 1603
MSI (s) (00:38) [17:46:21:453]: Destroying RemoteAPI object.
MSI (s) (00:5C) [17:46:21:453]: Custom Action Manager thread ending.
MSI (c) (10:C0) [17:46:21:484]: Back from server. Return value: 1603
MSI (c) (10:C0) [17:46:21:484]: Decrementing counter to disable shutdown. If
counter >= 0, shutdown will be denied. Counter after decrement: -1
Action ended 17:46:21: INSTALL. Return value 3.
Property(C): UpgradeCode = {421A321C-2214-4713-B3EB-253F2FBCCE49}
Property(C): VersionNT = 501
Property(C): ALLUSERS = 1
Property(C): ARPNOMODIFY = 1
Property(C): DefaultUIFont = Tahoma8
Property(C): INSTALLLEVEL = 3
Property(C): LIMITUI = 1
Property(C): Manufacturer = Microsoft Corporation
Property(C): ProductCode = {E09B48B5-E141-427A-AB0C-D3605127224A}
Property(C): ProductLanguage = 1033
Property(C): ProductName = Microsoft SQL Server Desktop Engine
Property(C): ProductVersion = 8.00.761
Property(C): MsiHiddenProperties = SqlSa...
Property(C): SQLVersion.2D02443E_7002_4C0B_ABC9_EAB2C064397B = 8.00.194
Property(C): SQLExitCode.2D02443E_7002_4C0B_ABC9_EAB2C064397B = 1603
Property(C): APPS_TEST = 1
Property(C): SQLMSDESelected = 1
Property(C): CSDVersionNumber = 768
Property(C): CSDVersion = 8.00.761
Property(C): SystemFolder = C:\WINDOWS\system32\
Property(C): PackageCode = {D29DCF7A-8199-4373-BA0D-2F3635EC940C}
Property(C): ProductState = -1
Property(C): PackagecodeChanging = 1
Property(C): INSTANCENAME = ThinkHealth
Property(C): SA...
Property(C): SECURITYMODE = SQL
Property(C): CURRENTDIRECTORY = C:\ONSInstall\sql2ksp3\MSDE
Property(C): CLIENTUILEVEL = 0
Property(C): CLIENTPROCESSID = 1808
Property(C): VersionDatabase = 110
Property(C): VersionMsi = 3.00
Property(C): WindowsBuild = 2600
Property(C): ServicePackLevel = 2
Property(C): ServicePackLevelMinor = 0
Property(C): MsiNTProductType = 1
Property(C): WindowsFolder = C:\WINDOWS\
Property(C): WindowsVolume = C:\
Property(C): System16Folder = C:\WINDOWS\system\
Property(C): RemoteAdminTS = 1
Property(C): TempFolder = C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\
Property(C): ProgramFilesFolder = C:\Program Files\
Property(C): CommonFilesFolder = C:\Program Files\Common Files\
Property(C): AppDataFolder = C:\Documents and
Settings\Administrator\Application Data\
Property(C): FavoritesFolder = C:\Documents and
Settings\Administrator\Favorites\
Property(C): NetHoodFolder = C:\Documents and
Settings\Administrator\NetHood\
Property(C): PersonalFolder = C:\Documents and Settings\Administrator\My
Documents\
Property(C): PrintHoodFolder = C:\Documents and
Settings\Administrator\PrintHood\
Property(C): RecentFolder = C:\Documents and Settings\Administrator\Recent\
Property(C): SendToFolder = C:\Documents and Settings\Administrator\SendTo\
Property(C): TemplateFolder = C:\Documents and Settings\All Users\Templates\
Property(C): CommonAppDataFolder = C:\Documents and Settings\All
Users\Application Data\
Property(C): LocalAppDataFolder = C:\Documents and
Settings\Administrator\Local Settings\Application Data\
Property(C): MyPicturesFolder = C:\Documents and Settings\Administrator\My
Documents\My Pictures\
Property(C): AdminToolsFolder = C:\Documents and Settings\All Users\Start
Menu\Programs\Administrative Tools\
Property(C): StartupFolder = C:\Documents and Settings\All Users\Start
Menu\Programs\Startup\
Property(C): ProgramMenuFolder = C:\Documents and Settings\All Users\Start
Menu\Programs\
Property(C): StartMenuFolder = C:\Documents and Settings\All Users\Start
Menu\
Property(C): DesktopFolder = C:\Documents and Settings\All Users\Desktop\
Property(C): FontsFolder = C:\WINDOWS\Fonts\
Property(C): GPTSupport = 1
Property(C): OLEAdvtSupport = 1
Property(C): ShellAdvtSupport = 1
Property(C): Intel = 15
Property(C): PhysicalMemory = 447
Property(C): VirtualMemory = 936
Property(C): AdminUser = 1
Property(C): LogonUser = Administrator
Property(C): UserSID = S-1-5-21-1202660629-1450960922-725345543-500
Property(C): UserLanguageID = 1033
Property(C): ComputerName = DISCOVSERVER
Property(C): SystemLanguageID = 1033
Property(C): ScreenX = 1280
Property(C): ScreenY = 1024
Property(C): CaptionHeight = 26
Property(C): BorderTop = 1
Property(C): BorderSide = 1
Property(C): TextHeight = 16
Property(C): ColorBits = 16
Property(C): TTCSupport = 1
Property(C): MsiWin32AssemblySupport = 5.1.2600.2180
Property(C): RedirectedDllSupport = 2
Property(C): Time = 17:46:21
Property(C): Date = 7/25/2007
Property(C): Privileged = 1
Property(C): USERNAME = Discovery
Property(C): COMPANYNAME = Discovery-uttuwah
Property(C): DATABASE = C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\2557a1.msi
Property(C): OriginalDatabase =
C:\ONSInstall\sql2ksp3\MSDE\Setup\SqlRun01.msi
Property(C): UILevel = 3
Property(C): ACTION = INSTALL
=== Logging stopped: 7/25/2007 17:46:21 ===
MSI (c) (10:C0) [17:46:21:531]: Note: 1: 1708
MSI (c) (10:C0) [17:46:21:531]: Product: Microsoft SQL Server Desktop
Engine -- Installation operation failed.
MSI (c) (10:C0) [17:46:21:531]: Grabbed execution mutex.
MSI (c) (10:C0) [17:46:21:531]: Cleaning up uninstalled install packages, if
any exist
MSI (c) (10:C0) [17:46:21:546]: MainEngineThread is returning 1603
=== Verbose logging stopped: 7/25/2007 17:46:21 ===
2007-07-25 17:43:39.59 server Microsoft SQL Server 2000 - 8.00.760
(Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 2)
2007-07-25 17:43:39.59 server Copyright (C) 1988-2002 Microsoft
Corporation.
2007-07-25 17:43:39.59 server All rights reserved.
2007-07-25 17:43:39.59 server Server Process ID is 1880.
2007-07-25 17:43:39.59 server Logging SQL Server messages in file
'C:\Program Files\Microsoft SQL Server\MSSQL$THINKHEALTH\LOG\ERRORLOG'.
2007-07-25 17:43:39.60 server SQL Server is starting at priority class
'normal'(1 CPU detected).
2007-07-25 17:43:39.78 server SQL Server configured for thread mode
processing.
2007-07-25 17:43:39.79 server Using dynamic lock allocation. [500] Lock
Blocks, [1000] Lock Owner Blocks.
2007-07-25 17:43:39.92 spid3 Warning ******************
2007-07-25 17:43:39.92 spid3 SQL Server started in single user mode.
Updates allowed to system catalogs.
2007-07-25 17:43:39.93 spid3 Starting up database 'master'.
2007-07-25 17:43:40.40 server Using 'SSNETLIB.DLL' version '8.0.766'.
2007-07-25 17:43:40.40 spid5 Starting up database 'model'.
2007-07-25 17:43:40.49 spid3 Server name is 'DISCOVSERVER\THINKHEALTH'.
2007-07-25 17:43:40.49 spid3 Skipping startup of clean database id 5
2007-07-25 17:43:40.49 spid3 Skipping startup of clean database id 6
2007-07-25 17:43:40.49 spid3 Starting up database 'msdb'.
2007-07-25 17:43:40.67 server SQL server listening on Shared Memory.
2007-07-25 17:43:40.67 server SQL Server is ready for client connections
2007-07-25 17:43:40.74 spid5 Clearing tempdb database.
2007-07-25 17:43:41.29 spid5 Starting up database 'tempdb'.
2007-07-25 17:43:41.40 spid3 Recovery complete.
2007-07-25 17:43:41.40 spid3 SQL global counter collection task is
created.
2007-07-25 17:43:41.43 spid3 Warning: override, autoexec procedures
skipped.
2007-07-25 17:45:44.74 spid3 SQL Server is terminating due to 'stop'
request from Service Control Manager.
################################################## #############################
Starting Service ...
SQL_Latin1_General_CP1_CI_AS
-m -Q -T4022 -T3659
An error occurred while attempting to start the service (1460)
SQL Server configuration failed.
################################################## #############################
hi,
Microsoft News wrote:
> I have for the past 1.5 weeks been trying to get MSDE installed on a
> Windows XP computer. We are installing MSDE sp3 which we have
> installed on more than 20+ computers. Some computers Windows 2003
> Servers some Windows XP Pro. We have NEVER had a problem. So before
> anyone suggest it, I don't think going to MSDE sp4 will help with
> this problem. We have formatted the computer MANY times and started
> over. We have updated with ALL of the Windows update and it did not
> work. We formatted and install only SP2 on Windows XP. We have
> taken off all other software, virus scanners, office, etc. The
> computer is BLANK. It is on the network and I am remote desktopped
> in when I try to install. Now I have done this MANY time remote
> desktopped to a machine and no problem. We have made sure that
> network items like File and Print Sharing are on. I have tried to
> install as the administrator of the computer, as a user who have
> administrative priveleges, etc. This computer is a Windows XP
> computer, not on a domain, the software is XP Pro, and everything
> looks good. I am at a lost.
> When I install I have it dump out the logs, here is some of the log I
> get, it is
> to long to post all of it. I have also added the SQL
> Error logs that are left below this log. Then below that I have
> attached the cnfgsvr.out
> Any help is GREATLY appriecated, I can not blank out and install XP
> any more.
<-->
Setup failed to configure the server. Refer to the server error logs and
setup error logs for more information.
MSI (s) (00!F4) [17:46:12:140]: Product: Microsoft SQL Server Desktop
Engine -- Setup failed to configure the server. Refer to the server error
logs and setup error logs for more information.
Action ended 17:46:12: InstallFinalize. Return value 3.
<-->
this exception is usually related to
http://support.microsoft.com/default.aspx?scid=kb;en-us;816499&Product=sql
is the "Server" service up and running as well?
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz http://italy.mvps.org
DbaMgr2k ver 0.21.0 - DbaMgr ver 0.65.0 and further SQL Tools
-- remove DMO to reply
|||Andrea
Thank you for your response, as I said in my email this is a BLANK computer,
never had anything installed on it so the link does not help me with this
but I will try to install it in another directory just to see if there is
something wrong with trying to install it in the default location.
What do you mean by:
> is the "Server" service up and running as well?
Thank you
Clyde
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:5graglF37hkkqU1@.mid.individual.net...
> hi,
> Microsoft News wrote:
>
> <-->
> Setup failed to configure the server. Refer to the server error logs and
> setup error logs for more information.
> MSI (s) (00!F4) [17:46:12:140]: Product: Microsoft SQL Server Desktop
> Engine -- Setup failed to configure the server. Refer to the server error
> logs and setup error logs for more information.
> Action ended 17:46:12: InstallFinalize. Return value 3.
> <-->
> this exception is usually related to
> http://support.microsoft.com/default.aspx?scid=kb;en-us;816499&Product=sql
> is the "Server" service up and running as well?
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz http://italy.mvps.org
> DbaMgr2k ver 0.21.0 - DbaMgr ver 0.65.0 and further SQL Tools
> -- remove DMO to reply
>
|||hi,
> What do you mean by:
>
go in the Administrative Tools and select the Services Applet... scroll down
till you find a service called "Server" (Supports file, print, and
named-pipe sharing over the network for this computer. If this service is
stopped, these functions will be unavailable. If this service is disabled,
any services that explicitly depend on it will fail to start.)
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz http://italy.mvps.org
DbaMgr2k ver 0.21.0 - DbaMgr ver 0.65.0 and further SQL Tools
-- remove DMO to reply
|||Andrea
You are a great help but that was not it. The service is up and running. I
even stopped it and started it, then checked the event log to make sure no
error occured. But everything worked fine. The server service is working
file.
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:5gsig1F3i3s7nU1@.mid.individual.net...
> hi,
> go in the Administrative Tools and select the Services Applet... scroll
> down till you find a service called "Server" (Supports file, print, and
> named-pipe sharing over the network for this computer. If this service is
> stopped, these functions will be unavailable. If this service is disabled,
> any services that explicitly depend on it will fail to start.)
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz http://italy.mvps.org
> DbaMgr2k ver 0.21.0 - DbaMgr ver 0.65.0 and further SQL Tools
> -- remove DMO to reply
>
|||hi,
Microsoft News wrote:
> Andrea
> You are a great help but that was not it. The service is up and
> running. I even stopped it and started it, then checked the event
> log to make sure no error occured. But everything worked fine. The
> server service is working file.
Sometimes you may need to delete this key:
HKLM\Software\Microsoft\Windows\CurrentVersion\Set up\ExceptionComponents,
then reinstall the SQL Server again.
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz http://italy.mvps.org
DbaMgr2k ver 0.21.0 - DbaMgr ver 0.65.0 and further SQL Tools
-- remove DMO to reply
|||Andrea,
I tried removing the key after wiping out any registry settings and the
folder from the computer after the last install. I also tried installing in
a different folder since I read some where that might help. But getting rid
of the registry key you meantioned below along with changing the path did
not fix the problem. I still get the same error.
Thank you
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:5gtuueF3hi7apU1@.mid.individual.net...
> hi,
> Microsoft News wrote:
> Sometimes you may need to delete this key:
> HKLM\Software\Microsoft\Windows\CurrentVersion\Set up\ExceptionComponents,
> then reinstall the SQL Server again.
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz http://italy.mvps.org
> DbaMgr2k ver 0.21.0 - DbaMgr ver 0.65.0 and further SQL Tools
> -- remove DMO to reply
>
|||This is a long shot but you aren't trying to install this through a Terminal
Server connection are you? This will fail with a 1460 error similar to what
you're seeing. The log indicates SQL Server service installed and started
successfully and then shut down. You might try installing with different
options to see if that makes a difference. Since you messed around with the
registry, you may now get different failures related to the registry key
being partially there. SQL Server uses several thousand registry key so I'm
reasonably certain you didn't remove them all.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Microsoft News" <Name@.coxinet.net> wrote in message
news:el2nANG0HHA.3768@.TK2MSFTNGP06.phx.gbl...
> Andrea,
> I tried removing the key after wiping out any registry settings and the
> folder from the computer after the last install. I also tried installing
> in a different folder since I read some where that might help. But
> getting rid of the registry key you meantioned below along with changing
> the path did not fix the problem. I still get the same error.
> Thank you
> "Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
> news:5gtuueF3hi7apU1@.mid.individual.net...
>
|||Roger,
Yes I am installing through a terminal server connection. I had read
another post were people pointed to that as a POSSIBLE problem but it was
not clear as to why. We have installed over 20+ MSDE systems through
Terminal Server connection and NEVER a problem. But tomorrow I will try to
install on a BLANK machine but this time I will have a local user run the
MSDE install.

> successfully and then shut down. You might try installing with different
> options to see if that makes a difference. Since you messed around with
> the
What different options are you referring to? I am installing with the
following command line:
setup instancename=<OurInstance> SECURITYMODE=SQL SAPWD=<SomePassword> /L*V
C:\msde.log

> options to see if that makes a difference. Since you messed around with
> the registry, you may now get different failures related to the registry
> key being partially there. SQL Server uses several thousand registry key
> so I'm reasonably certain you didn't remove them all.
Some time we try to install again after the install fails, what I do is go
into the registry and strip out everything that has SQL or MSSQL in the key,
that does not relate to ODBC. I figured that was cleaning up everything
because if you could look at the log file what you would see is that MSDE
rollback the install and remove all those thousands of registry keys. But
even if we do not get them all, as I said before we have tried MANY time to
format and re-install on a blank computer. I get the same error whether I
strip out keys or format. So your assumption of a different failures
related to registry key being partially there is incorrect.
Thanks for you help and advice, I will try to install locally and not
remoted, on a blank computer and see what happens. Any more suggestions
would be VERY helpful.
Clyde
"Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
news:48A8AC3E-F262-4875-BCCF-315DB9BDC51A@.microsoft.com...
> This is a long shot but you aren't trying to install this through a
> Terminal Server connection are you? This will fail with a 1460 error
> similar to what you're seeing. The log indicates SQL Server service
> installed and started successfully and then shut down. You might try
> installing with different options to see if that makes a difference.
> Since you messed around with the registry, you may now get different
> failures related to the registry key being partially there. SQL Server
> uses several thousand registry key so I'm reasonably certain you didn't
> remove them all.
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "Microsoft News" <Name@.coxinet.net> wrote in message
> news:el2nANG0HHA.3768@.TK2MSFTNGP06.phx.gbl...
>
|||Roger,
Ok, we were able to install on a BLANK xp computer, we did nothing but
install XP, service pack 2, we did not install any hardware drivers (network
card or video card drivers, etc) we took all the windows defaults.
Plus, we did not remote in and try the installation, we just did the install
locally. The last thing we did was use MSDE sp4 not MSDE sp3 which I do not
think made a difference but I wanted to make sure anyone reading this would
know.
It all installed fine. I think the issue might have either been some other
driver or not installing remotely but we have installed remotely on a lot of
computers so I don't see the reason that would not work. The drivers are
the only other thing I can think of which might be the issue.
But thank to you and Andrea for all your help and I am glad this has been
solved.
Clyde W.
"Microsoft News" <Name@.coxinet.net> wrote in message
news:OzZdD2w0HHA.5380@.TK2MSFTNGP04.phx.gbl...
> Roger,
> Yes I am installing through a terminal server connection. I had read
> another post were people pointed to that as a POSSIBLE problem but it was
> not clear as to why. We have installed over 20+ MSDE systems through
> Terminal Server connection and NEVER a problem. But tomorrow I will try
> to install on a BLANK machine but this time I will have a local user run
> the MSDE install.
>
> What different options are you referring to? I am installing with the
> following command line:
> setup instancename=<OurInstance> SECURITYMODE=SQL SAPWD=<SomePassword>
> /L*V C:\msde.log
>
> Some time we try to install again after the install fails, what I do is go
> into the registry and strip out everything that has SQL or MSSQL in the
> key, that does not relate to ODBC. I figured that was cleaning up
> everything because if you could look at the log file what you would see is
> that MSDE rollback the install and remove all those thousands of registry
> keys. But even if we do not get them all, as I said before we have tried
> MANY time to format and re-install on a blank computer. I get the same
> error whether I strip out keys or format. So your assumption of a
> different failures related to registry key being partially there is
> incorrect.
> Thanks for you help and advice, I will try to install locally and not
> remoted, on a blank computer and see what happens. Any more suggestions
> would be VERY helpful.
> Clyde
> "Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
> news:48A8AC3E-F262-4875-BCCF-315DB9BDC51A@.microsoft.com...
>

Install MSDE with SP3 without User intervention

I have a 5 user app that uses MSDE as the database. It is run on a "SERVER"
any computer actually that they will use to use the same database.
I need an easy way for my low-tech users to stick in my install CD, select
Server installation , and I offer a named instance of SQL server using SQL
Security... Also needs to create a new copy of the database, offer them a
prompt for the DB password and more.
I need this to be as easy as possible.
What is the best route in doing this?
If it requires an DBA or high-tech user to install, then that will rule out
most of my clients, and make distributing this app and using MSDE not a very
wise choice.
Thanks for any help,
ShaneShane,
Your app sound very similar to ours and so do your users :> )
This is what I have just done and it works very well.
Our install software is InstallShield DevStudio 9.1 and it allows you to
conditionally install MSDE 2000. BTW it does not allow you to conditional
install MSDE 1.0. It also allows you to put in an instance name if you want
one.
So all I did was change the setup type screen that normally reads 'typical',
'minimum' and 'custom' to read 'server', 'client' and 'custom'. A Server
selection installs MSDE plus the client components and a Client selection
will not install MSDE.
As for the database itself I scripted all the schema, you can do that thru
EM, and enough table data to get the application going. ie Default Data.
You can run this either via a vbScript or batch file using the osql command.
We elected to script the data because some of our customers already have SQL
and they often want to use that, especially if there are large numbers of
users. It also gets over the problem of a customer having SQL, wanting to
use it, and their sort order is different to yours.
In the batch or vbscript you could offer prompts for sa password. Install
MSDE with a blank or known password, run the database scripts, ask for a new
password, change it and your done.
There's no easy way to do what you want, ie giving the user options like
passwords instance names etc., and I've tried them all. If you didn't want
to have the flexibility and wanted a set install then Installshield would do
it all. Just click on setup and it would install your app, msde, make the
instance, have a set sa password and attach or run a batch file to install
your databases. But, you have to make the decision.
Hope this helps.
Greg
--
greghines@.bigfoot.com.NOSPAM
Remove NOSPAM when replying
"SStory" <TheStorys@.TAKEOUTTHISSPAMBUSTERsofthome.net> wrote in message
news:eCkwq$QEEHA.628@.TK2MSFTNGP10.phx.gbl...
> I have a 5 user app that uses MSDE as the database. It is run on a
"SERVER"
> any computer actually that they will use to use the same database.
> I need an easy way for my low-tech users to stick in my install CD, select
> Server installation , and I offer a named instance of SQL server using SQL
> Security... Also needs to create a new copy of the database, offer them a
> prompt for the DB password and more.
> I need this to be as easy as possible.
> What is the best route in doing this?
> If it requires an DBA or high-tech user to install, then that will rule
out
> most of my clients, and make distributing this app and using MSDE not a
very
> wise choice.
> Thanks for any help,
> Shane
>|||Thanks Greg.
Does the msde 2000 copy you are installing have SP3 already applied?
I installed on my dev machine using the one from VB.NET I think.
Also when you mention scripting with vbscript...is that from inside of
Install Shield or are you running that from wsh or something?
Since .NET comes with a decent installer I was thinking about making it with
that. Don't have a lot of funds to buy another installer.
But I could have two separate ones. One that installs the app, then another
that installs MSDE, and maybe have them both run from a webpage that starts
with autorun. Let them type sa password to use in the webpage and somehow
use javascript or something to run the actual MSDE with the appropriate
params. I don't know that might be hard. These are some things I have
thought of.
I know we are licensed to use MSDE for owning .NET Pro. There seem to be
several flavors of MSDE, and seems I saw one that would install with SP3
included. Guess I need to research some more.
At present, I have a new fire to put out. Did a restore on the database and
now ADO.NET fails to connect.
So can't do much else until I resolve this.
I am just gathering information on each area that I need or will need in
order to distribute the project easily.
Thanks for all your advice.
It is very helpful to hear from you,
Shane
"Greg Hines" <greghines@.bigfoot.com.NOSPAM> wrote in message
news:1080108879.380672@.gw-gos.nlc.net.au...
> Shane,
> Your app sound very similar to ours and so do your users :> )
> This is what I have just done and it works very well.
> Our install software is InstallShield DevStudio 9.1 and it allows you to
> conditionally install MSDE 2000. BTW it does not allow you to conditional
> install MSDE 1.0. It also allows you to put in an instance name if you
want
> one.
> So all I did was change the setup type screen that normally reads
'typical',
> 'minimum' and 'custom' to read 'server', 'client' and 'custom'. A Server
> selection installs MSDE plus the client components and a Client selection
> will not install MSDE.
> As for the database itself I scripted all the schema, you can do that thru
> EM, and enough table data to get the application going. ie Default Data.
> You can run this either via a vbScript or batch file using the osql
command.
> We elected to script the data because some of our customers already have
SQL
> and they often want to use that, especially if there are large numbers of
> users. It also gets over the problem of a customer having SQL, wanting to
> use it, and their sort order is different to yours.
> In the batch or vbscript you could offer prompts for sa password. Install
> MSDE with a blank or known password, run the database scripts, ask for a
new
> password, change it and your done.
> There's no easy way to do what you want, ie giving the user options like
> passwords instance names etc., and I've tried them all. If you didn't
want
> to have the flexibility and wanted a set install then Installshield would
do
> it all. Just click on setup and it would install your app, msde, make the
> instance, have a set sa password and attach or run a batch file to install
> your databases. But, you have to make the decision.
> Hope this helps.
> Greg
> --
> greghines@.bigfoot.com.NOSPAM
> Remove NOSPAM when replying
> "SStory" <TheStorys@.TAKEOUTTHISSPAMBUSTERsofthome.net> wrote in message
> news:eCkwq$QEEHA.628@.TK2MSFTNGP10.phx.gbl...
> "SERVER"
select
SQL
a
> out
> very
>|||One Question, sp2kdesksp3.exe
I ran it to install to a local folder.
This says to have an install complete with SP3.
Is this the one I should use for install?
If so, then I just need a front end and to prompt for sa password and I am
set. Then using the scripting and such that you spoke of with OSQL to
install the database and such.
Thanks,
Shane
I downloaded a file called,
"Greg Hines" <greghines@.bigfoot.com.NOSPAM> wrote in message
news:1080108879.380672@.gw-gos.nlc.net.au...
> Shane,
> Your app sound very similar to ours and so do your users :> )
> This is what I have just done and it works very well.
> Our install software is InstallShield DevStudio 9.1 and it allows you to
> conditionally install MSDE 2000. BTW it does not allow you to conditional
> install MSDE 1.0. It also allows you to put in an instance name if you
want
> one.
> So all I did was change the setup type screen that normally reads
'typical',
> 'minimum' and 'custom' to read 'server', 'client' and 'custom'. A Server
> selection installs MSDE plus the client components and a Client selection
> will not install MSDE.
> As for the database itself I scripted all the schema, you can do that thru
> EM, and enough table data to get the application going. ie Default Data.
> You can run this either via a vbScript or batch file using the osql
command.
> We elected to script the data because some of our customers already have
SQL
> and they often want to use that, especially if there are large numbers of
> users. It also gets over the problem of a customer having SQL, wanting to
> use it, and their sort order is different to yours.
> In the batch or vbscript you could offer prompts for sa password. Install
> MSDE with a blank or known password, run the database scripts, ask for a
new
> password, change it and your done.
> There's no easy way to do what you want, ie giving the user options like
> passwords instance names etc., and I've tried them all. If you didn't
want
> to have the flexibility and wanted a set install then Installshield would
do
> it all. Just click on setup and it would install your app, msde, make the
> instance, have a set sa password and attach or run a batch file to install
> your databases. But, you have to make the decision.
> Hope this helps.
> Greg
> --
> greghines@.bigfoot.com.NOSPAM
> Remove NOSPAM when replying
> "SStory" <TheStorys@.TAKEOUTTHISSPAMBUSTERsofthome.net> wrote in message
> news:eCkwq$QEEHA.628@.TK2MSFTNGP10.phx.gbl...
> "SERVER"
select
SQL
a
> out
> very
>|||Shane,
The MSDE 2000 Merge Module with DevStudio 9 does have SP3 already applied,
so you don't have to worry about applying it.
DevStudio allows either Installshield Scripting or a VBScript to be run from
inside Installshield. So you can do things like:-
a) Installer selects the type of setup. Typical, Min. Custom etc.
b) This opens your custom dialog with say some questions to answer. eg sa
password. Their responses are stored in variables.
c) They click on Next to proceed with the installation.
Or you could do:-
a) Install a default installation of MSDE 2000 SP3 with a blank sa password.
b) After setup finishes run either a vbScript or Installshield script that
asks for an sa password.
c) Within that script run an osql command to change the sa password.
If you want to go with MSDE 2000 then there is no reason to have 2 install
apps. DevStudio 9 will do all you want and more.
As I said earlier I've been installing MSDE 1.0 and more recently MSDE 2000
with our apps. for sometime now and the MSDE 2000 Merge Module with
DevStudio is by far the easiest as it can be conditionally installed. If
you want to go with MSDE 1.0 then it has to be script driven as MSDE 1.0
cannot be conditionally installed.
Hope I've been helpful.
Regards,
Greg
--
greghines@.bigfoot.com.NOSPAM
Remove NOSPAM when replying
"SStory" <TheStorys@.TAKEOUTTHISSPAMBUSTERsofthome.net> wrote in message
news:epF$cacEEHA.3788@.TK2MSFTNGP10.phx.gbl...
> Thanks Greg.
> Does the msde 2000 copy you are installing have SP3 already applied?
> I installed on my dev machine using the one from VB.NET I think.
> Also when you mention scripting with vbscript...is that from inside of
> Install Shield or are you running that from wsh or something?
> Since .NET comes with a decent installer I was thinking about making it
with
> that. Don't have a lot of funds to buy another installer.
> But I could have two separate ones. One that installs the app, then
another
> that installs MSDE, and maybe have them both run from a webpage that
starts
> with autorun. Let them type sa password to use in the webpage and somehow
> use javascript or something to run the actual MSDE with the appropriate
> params. I don't know that might be hard. These are some things I have
> thought of.
> I know we are licensed to use MSDE for owning .NET Pro. There seem to be
> several flavors of MSDE, and seems I saw one that would install with SP3
> included. Guess I need to research some more.
> At present, I have a new fire to put out. Did a restore on the database
and
> now ADO.NET fails to connect.
> So can't do much else until I resolve this.
> I am just gathering information on each area that I need or will need in
> order to distribute the project easily.
> Thanks for all your advice.
> It is very helpful to hear from you,
> Shane
>
> "Greg Hines" <greghines@.bigfoot.com.NOSPAM> wrote in message
> news:1080108879.380672@.gw-gos.nlc.net.au...
conditional
> want
> 'typical',
selection
thru
Data.
> command.
> SQL
of
to
Install
> new
> want
would
> do
the
install
> select
> SQL
them
> a
rule
a
>|||Thanks Greg.
I appreciate the info.
Since I don't have a budget to buy additional setup software right now.
I chose to create a prompting VC++ app to do my server setup.
It prompts for all the needed info, creates the setup.ini file in a temp dir
and then calls the setup.exe program for MSDE passing the right parameters,
then it calls a batch file passing that info, so that I can create the
structure with calls to osql with scripts and then will copy the data as
soon as I learn how.
How can I copy data into the new database?
Is BCP the only option. Seems complicated. I was hoping for an easier way
to do that. The amount of data needing to be copied is less than 100 rows
in 8 tables.
Thanks,
Shane
"Greg Hines" <greghines@.bigfoot.com.NOSPAM> wrote in message
news:1080511923.196920@.gw-gos.nlc.net.au...
> Shane,
> The MSDE 2000 Merge Module with DevStudio 9 does have SP3 already applied,
> so you don't have to worry about applying it.
> DevStudio allows either Installshield Scripting or a VBScript to be run
from
> inside Installshield. So you can do things like:-
> a) Installer selects the type of setup. Typical, Min. Custom etc.
> b) This opens your custom dialog with say some questions to answer. eg sa
> password. Their responses are stored in variables.
> c) They click on Next to proceed with the installation.
> Or you could do:-
> a) Install a default installation of MSDE 2000 SP3 with a blank sa
password.
> b) After setup finishes run either a vbScript or Installshield script that
> asks for an sa password.
> c) Within that script run an osql command to change the sa password.
> If you want to go with MSDE 2000 then there is no reason to have 2 install
> apps. DevStudio 9 will do all you want and more.
> As I said earlier I've been installing MSDE 1.0 and more recently MSDE
2000
> with our apps. for sometime now and the MSDE 2000 Merge Module with
> DevStudio is by far the easiest as it can be conditionally installed. If
> you want to go with MSDE 1.0 then it has to be script driven as MSDE 1.0
> cannot be conditionally installed.
> Hope I've been helpful.
> Regards,
> Greg
> --
> greghines@.bigfoot.com.NOSPAM
> Remove NOSPAM when replying
> "SStory" <TheStorys@.TAKEOUTTHISSPAMBUSTERsofthome.net> wrote in message
> news:epF$cacEEHA.3788@.TK2MSFTNGP10.phx.gbl...
> with
> another
> starts
somehow
be
> and
to
> conditional
you
Server
> selection
> thru
> Data.
have
> of
wanting
> to
> Install
a
like
> would
> the
> install
message
using
> them
> rule
not
> a
>

Install Help

Hello:
I am new to Reporting Services and I am having a problem displayingReporting Manager. I am running Win 2003 with IIS 6 and SQL Svr2000 SP3. VS 2003 has been installed and the developmentenvironment works fine.
I cannot get Report Manager to work I try to access the page and I get the following error:
Error
The request failed with HTTP Status 400: Bad Request
Their is a link for Home but when I click on it I get the same message.
When I try to access Report Server using //servername/reportmanager, Iget prompted for a user name and password. I put in thecredentials for a local admin and it brings me to a page that has the servername/reportserver. At the bottom is some versioninformation and that's all there is.
I have researched and tried a variety a solutions like running reactivate and rsconfig to no avail.
IIS is set up with a reports website and 2 virtual dorectories, onepointing to the appropriate folder in the MSSQL folder for reportmanager and report server.
I'm out of idea. If anyone can provide some ways I can troubleshoot, I would appreciate it
Brennan
Did you have the SSL option unchecked while you were installing the RS ? or are you using SSL ?|||The SSL option was unchecked.
Thanks
|||sorry I am out of ideas too..it was a big hassle for me when I first downloaded Rs and tried to get it work..and I do remember being popped up with username/pwd but I cant remember what xactly I did ..I had to set up forms based authentication so I followedthis article.see if that will help.|||Thanks

Install failure: "Error 29550. Cannot connect to the SQL server instance

I'm trying to install the Dev version of Reporting Services (RS) on one
box and have it use an Sql Server 2000 (w/SP3) instance on another box.
Both the RS and SqlServer boxes are Windows 2000 Servers. Neither are
part of a "windows domain"--neither will they ever be. We only connect
to SqlServer via a user/pwd pair. Additionally, there are 2 instances of
SqlServer running on the box and both of them listen on custom ports. (I
have confirmed that I can successfully connect to the desired SqlServer
instance from the RS box.)
The error I got was the "Login failed for user '(null)'. Reason: Not
associated with a trusted SQL Server connection.". The installer
attempts a domain login when I explicitly told it *not* to. I found no
way to get the installer to successfully connect to the database. The
solutions I've found on the web/Usenet have not worked either.
Since I couldn't get it to install through the GUI, I switched to using
an .ini file. Of course, it's not working either. The (500KB!) log file
the installer produces has only one useful line in it: "Error 29550.
Cannot connect to the SQL server instance ." That meant that the problem
was the RSDATABASESERVER variable. The instructions tell me to specify
an "SQL Server 2000 instance in format MACHINE\INSTANCENAME". I played
around with that value a lot; I wondered how it could figure out what
port to connect to for one thing. While doing so, I tried sniffing the
network to see if that would help me at all--it just got me more
frustrated: no attempt is made to contact the server! Ever.
First off: WHY choose this uncommon, inadequate format for specifying a
server? Why not just use an alias from "cliconfg" like everything else?
Second: why doesn't the installer even *try* to login to the server? If
there's a reason it can't access the network, wouldn't you think that
500KB log file is a good place to mention it?
What do I do? (Hint: don't suggest making either box part of a windows
domain)
GrangerTo have setup use sql auth during setup you must pass in command line
parameters. The params are RSSETUPACCOUNT and RSSETUPPASSWORD
so run this command
setup.exe RSSETUPACCOUNT=foo RSSETUPPASSWORD=bar
This will allow you to use the setup GUI still but all communication with
the backend server will use sql auth. Note that the setup user needs to be
a dbo. You can safely use the sa account as it is only used during setup.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Granger Godbold" <granger.godbold@.FILLER.prometric.com> wrote in message
news:e4VCZaIEFHA.3888@.TK2MSFTNGP10.phx.gbl...
> I'm trying to install the Dev version of Reporting Services (RS) on one
> box and have it use an Sql Server 2000 (w/SP3) instance on another box.
> Both the RS and SqlServer boxes are Windows 2000 Servers. Neither are part
> of a "windows domain"--neither will they ever be. We only connect to
> SqlServer via a user/pwd pair. Additionally, there are 2 instances of
> SqlServer running on the box and both of them listen on custom ports. (I
> have confirmed that I can successfully connect to the desired SqlServer
> instance from the RS box.)
> The error I got was the "Login failed for user '(null)'. Reason: Not
> associated with a trusted SQL Server connection.". The installer attempts
> a domain login when I explicitly told it *not* to. I found no way to get
> the installer to successfully connect to the database. The solutions I've
> found on the web/Usenet have not worked either.
> Since I couldn't get it to install through the GUI, I switched to using an
> .ini file. Of course, it's not working either. The (500KB!) log file the
> installer produces has only one useful line in it: "Error 29550. Cannot
> connect to the SQL server instance ." That meant that the problem was the
> RSDATABASESERVER variable. The instructions tell me to specify an "SQL
> Server 2000 instance in format MACHINE\INSTANCENAME". I played around with
> that value a lot; I wondered how it could figure out what port to connect
> to for one thing. While doing so, I tried sniffing the network to see if
> that would help me at all--it just got me more frustrated: no attempt is
> made to contact the server! Ever.
> First off: WHY choose this uncommon, inadequate format for specifying a
> server? Why not just use an alias from "cliconfg" like everything else?
> Second: why doesn't the installer even *try* to login to the server? If
> there's a reason it can't access the network, wouldn't you think that
> 500KB log file is a good place to mention it?
> What do I do? (Hint: don't suggest making either box part of a windows
> domain)
> Granger|||Thanks for trying, but no, that doesn't work; I was already doing that. I was
trying to use the "sa" account from the beginning because the instructions say
the "setup" account is only used during setup.
My problem is still that the installer doesn't even *try* to connect to the
database server. Once I can get around that, my problem will be that it will
want to use Windows Authentication because the connection information only
consists of "server\instance"; that's why it has to login: to figure out the
port the instance lives at.
If anyone knows the person responsible for the decision to use this connection
method, please smack them upside the head for me.
Other ideas?
Granger
Daniel Reib [MSFT] wrote:
> To have setup use sql auth during setup you must pass in command line
> parameters. The params are RSSETUPACCOUNT and RSSETUPPASSWORD
> so run this command
> setup.exe RSSETUPACCOUNT=foo RSSETUPPASSWORD=bar
> This will allow you to use the setup GUI still but all communication with
> the backend server will use sql auth. Note that the setup user needs to be
> a dbo. You can safely use the sa account as it is only used during setup.
>|||Well first of all, if you want it to connect, what does your client
configuration say?
I take it that on the general tab you have TCP/IP listed at the top - click
the properties tab and is the port set correctly for your particular
instance?
I am running reporting services stand-alone - with SQL Server NOT IN A
DOMAIN - and it runs just fine.
You can also create an ALIAS name to the server instance in the SQL Server
Client Network utility.
Finally, just to be sure we are "connecting the dots" here - fire up the SQL
Server Network utility and verify that the TCP/IP properties are also
listening on the correct port. (I bet they are since you are using the
system successfully)
Last but not least, even if you are using SQL Server authentication, you
should be able to use windows authentication only when doing the setup -
since as you said you have full control over the dev box - then you have
local admin rights - therefore you should be able to logon unless you have
modifed the BUILTIN\Administrators security for that machine. (I assume that
this is not the case).
Please let me know if you are still having an issue, I'll be happy to help
you out.
Of course, this may come as a dumb question, but I assume nothing: Did you
install SP3a for SQL Server? (I assume yes), did you install the SQL Server
hotfix 859 ?
=-Chris
"Granger Godbold" <granger.godbold@.invalid.prometric.com> wrote in message
news:ucLN4gZEFHA.3256@.tk2msftngp13.phx.gbl...
> Thanks for trying, but no, that doesn't work; I was already doing that. I
> was trying to use the "sa" account from the beginning because the
> instructions say the "setup" account is only used during setup.
> My problem is still that the installer doesn't even *try* to connect to
> the database server. Once I can get around that, my problem will be that
> it will want to use Windows Authentication because the connection
> information only consists of "server\instance"; that's why it has to
> login: to figure out the port the instance lives at.
> If anyone knows the person responsible for the decision to use this
> connection method, please smack them upside the head for me.
> Other ideas?
> Granger
>
> Daniel Reib [MSFT] wrote:
>> To have setup use sql auth during setup you must pass in command line
>> parameters. The params are RSSETUPACCOUNT and RSSETUPPASSWORD
>> so run this command
>> setup.exe RSSETUPACCOUNT=foo RSSETUPPASSWORD=bar
>> This will allow you to use the setup GUI still but all communication with
>> the backend server will use sql auth. Note that the setup user needs to
>> be a dbo. You can safely use the sa account as it is only used during
>> setup.|||Thanks Chris.
The connectivity is all OK. It appears I'm just going to have to go
sync the administrators on each of the boxes during the install.
However, that won't be for a while; I just gave up and installed
everything on my own box for now. When I've had a chance to play with it
for a while, I'll do another install attempt in a more "proper" DEV
environment.
As far as the updates on the database go, my DBA says he's only done
security bulletin stuff. I looked it over and it seems the DEV box has
SP3 not SP3a (I checked the Ssnetlib.dll; we have 2000.80.760 not
2000.80.766
(http://support.microsoft.com/default.aspx?scid=kb;en-us;819334)). Also,
since Enterprise Manager reports 8.00.760, I gather he's not done any
hotfixes. This KnowledgeBase article
(http://support.microsoft.com/default.aspx?scid=kb;en-us;888007) implies
we should be at least at .977. I'll go tease him for being a slacker. ;)
I wouldn't guess the hotfixes would have anything to do with my
problem, however, since my local database only has SP3 installed on it
and ReportingServices installed fine.
Again, thanks Chris =)
Granger
Christopher Conner wrote:
<snip>
> Last but not least, even if you are using SQL Server authentication, you
> should be able to use windows authentication only when doing the setup -
> since as you said you have full control over the dev box - then you have
> local admin rights - therefore you should be able to logon unless you have
> modifed the BUILTIN\Administrators security for that machine. (I assume that
> this is not the case).
> Please let me know if you are still having an issue, I'll be happy to help
> you out.
> Of course, this may come as a dumb question, but I assume nothing: Did you
> install SP3a for SQL Server? (I assume yes), did you install the SQL Server
> hotfix 859 ?
> =-Chris
>sql

Install both SQL7 and SQL8 on same server

Hello all,

Is there any special procedure to install a SQL7 (plus sp3) and a SQL8 server on a Windows 2000 Server.

I did succed installing both of them, but all of my applications are behaving strangely ()error msg ect)...So I may supose that there some kind of predefined process to have those kind of installation working properly..?

Any idea would be welcomed !

Thanks a lot in advance,

Regards,

Benj.how did you do it? there should'nt be any problems if you used named instances. If however you did'nt used named instances and you installed SQL 2K on top of SQL7, yes you can have a number of problems. off the top of my head I think there is an issue with programmers that used qoutes in their stored procedures.|||Just two standard installs...nothing really complex.

Yes, I did use instances for SQL8:

MYSERVER => for accessing SQL7 DB

MYSERVER\APLTEST => for accessing SQL8 DB

But year I tried to trace from both side (profiler and ODBC trace log), and did find some weird error messages:

DIAG [S0002] [Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name 'ScalaDBProperties'. (208)...

And basically my application crashes after trying to do this command (checking if the table exists):

SELECT NULL FROM SY050000 WHERE 1 = 2

Here it dies...

Ghost

But what's the best is that this table exist, I can querry it without any issue.. Also tried to do a connection from another server with MS Access..just in case...It also worked fine..

Also last point I tried to recreate a user for this DB by deleting the main software user called Scala and recreating it.. Nothing worked..

I'm really lost here, so if anyone would have a hint..I would be very happy !

Thanks again,

Benj.|||Am I missing something here? Your query does not seem to make any sense.

It seems you are returning the value null when the number 1 = number 2 which is a mathmatical impossibility.

1 is not a column name. I seem to remember that column names can not start with numbers.

Am I wrong?|||Erf... that's the SQL statement the program we have issue.

From what I was thinking, the program is just trying to check if the table SY050000 exists but I'm not certain of it and since my knowledge of SQL is pretty limited (just trying to debug the thingy) I cannot assure you that this command syntax is actually right..

But I tried from a querry analyzer and it doesn't give me any error and it returns me :

(No column Name)

If I try the same command on a table that doesn't exists I have this erro message:

Server: Msg 208, Level 16, State 1, Line 1
Invalid object name 'SY05000'.

Would there be any tests to do from a SQL point of view, on the SY050000 table to check if everything is alright ? Is there anything else I could try to test my SQL install or my ODBC connection please ?

In any case thanks for trying to help :) that's much apreciated :D

Install Analysis Services SP3

Hi,
I'm have downloaded database components SP3- SQL2KSP3.exe SP3a.
When i tried to installed , it gave me this error "An error occurred during
the move data process: -145"
why? please help and guide me on what to do next.
thx,
jessJessica,
Here are few possible issues:
- first of all, don't get mad with this bullet, but check whether you have
AS installed on the computer
- next, you can check the olapsp.log file to see what went wrong
- check the support article at http://www.support.microsoft.com/?id=814462
whether it applies to your case
- I've succeeded to install AS SP3a after this error when I stopped all
unnecessary services.
Dejan Sarka, SQL Server MVP
Associate Mentor
Solid Quality Learning
More than just Training
www.SolidQualityLearning.com
"Jessica" <Jessica@.discussions.microsoft.com> wrote in message
news:6EB3D551-0613-436B-8411-D6853C1370A7@.microsoft.com...
> Hi,
> I'm have downloaded database components SP3- SQL2KSP3.exe SP3a.
> When i tried to installed , it gave me this error "An error occurred
during
> the move data process: -145"
> why? please help and guide me on what to do next.
> thx,
> jess

Install Analysis Services SP3

Hi,
I'm have downloaded database components SP3- SQL2KSP3.exe SP3a.
When i tried to installed , it gave me this error "An error occurred during
the move data process: -145"
why? please help and guide me on what to do next.
thx,
jessJessica,
Here are few possible issues:
- first of all, don't get mad with this bullet, but check whether you have
AS installed on the computer
- next, you can check the olapsp.log file to see what went wrong
- check the support article at http://www.support.microsoft.com/?id=814462
whether it applies to your case
- I've succeeded to install AS SP3a after this error when I stopped all
unnecessary services.
Dejan Sarka, SQL Server MVP
Associate Mentor
Solid Quality Learning
More than just Training
www.SolidQualityLearning.com
"Jessica" <Jessica@.discussions.microsoft.com> wrote in message
news:6EB3D551-0613-436B-8411-D6853C1370A7@.microsoft.com...
> Hi,
> I'm have downloaded database components SP3- SQL2KSP3.exe SP3a.
> When i tried to installed , it gave me this error "An error occurred
during
> the move data process: -145"
> why? please help and guide me on what to do next.
> thx,
> jess

Install Analysis Services SP3

Hi,
I'm have downloaded database components SP3- SQL2KSP3.exe SP3a.
When i tried to installed , it gave me this error "An error occurred during
the move data process: -145"
why? please help and guide me on what to do next.
thx,
jess
Jessica,
Here are few possible issues:
- first of all, don't get mad with this bullet, but check whether you have
AS installed on the computer
- next, you can check the olapsp.log file to see what went wrong
- check the support article at http://www.support.microsoft.com/?id=814462
whether it applies to your case
- I've succeeded to install AS SP3a after this error when I stopped all
unnecessary services.
Dejan Sarka, SQL Server MVP
Associate Mentor
Solid Quality Learning
More than just Training
www.SolidQualityLearning.com
"Jessica" <Jessica@.discussions.microsoft.com> wrote in message
news:6EB3D551-0613-436B-8411-D6853C1370A7@.microsoft.com...
> Hi,
> I'm have downloaded database components SP3- SQL2KSP3.exe SP3a.
> When i tried to installed , it gave me this error "An error occurred
during
> the move data process: -145"
> why? please help and guide me on what to do next.
> thx,
> jess