There are special instructions for installing service packs on desktop edition installations -- command line options etc. How do you install hotfix roll-ups? Does build 2187 apply to desktop edition?
View 1 RepliesHi,
I'm planning to install the cumulative hotfix (build 2187) on my sql 2000 clustering server (SP4, 2040). And I would like to know if the cumulative hotfix is able to roll back. If possible, please provide me any information about that. Thanks in advance.
I want to know if there is Desktop edition for SQL 2000 Server and if so does it comes bundled on the same CD like it did for MSS 7.0.Also is there a limit to the size of DB's that can be build with it.
Thanks a Bunch
I have SQL Server 2000 installed on my laptop and am trying to install an instance of MSDE. I keep getting the error message: "The installation of SQL Server 2000 Desktop Engine has failed. Please see the Getting Started manual for further instructions."
I have done this installation before on other machines. Something must be corrupt on my machine (?). The error message is not very enlightening. Any ideas?
hi all, i dunno should i post it here or not but i cant other place topost this problem ..i am using windows XP professional service pack 1 .. when i try toinstall MS SQL 2000 Developer Edition to my system, it can works fineexcept when i try to set the user name and password then it promp outthis msgerror msg : setup cannot verify/grant logon as service right to the sqlserver logon account : 1332(0X534)can any 1 help me with this? if i choose windows authentichal passwordthen can run, i cannot set the password--qintian------------------------------------------------------------------------qintian's Profile: http://www.dbtalk.net/m671View this thread: http://www.dbtalk.net/t325996
View 7 Replies View RelatedMy laptop has VS 2005 installed. I am trying to install MS SQL Server 2000 Enterprise Edition, when i run "install database components", it gave error: "MS SQL Server 2000 Enterprise Edition component is not supported on this operating system. Only client components will be available for installation". then when i click on "ok", then "next", when i click on "next" on the "computer name" page, it gave another error: "A previous program installation created pending file operations on the installation moachine. You must restart the computer before running setup". I restarted my laptop following the instruction, but same thing happened when i run the installation. Plz help
View 19 Replies View RelatedHello.
I am attempting to install the first of the cumulative hotfix packages ( SQL2005-KB918222-x64-ENU.exe) after applying Service Pack 1 to a SQL Server 2005 std edn 64-bit installation. The service pack installed no problem but the hot fix fails with the following errors in the log file below.
I have installed the 32-bit versions of the hotfix packages onto a different server and I did not get these errors.
Any help on how to sort this out would be much appreciated!
08/23/2006 15:03:44.592 ================================================================================
08/23/2006 15:03:44.608 Hotfix package launched
08/23/2006 15:03:45.842 Product discovery successfully completed during the install process for MSSQLSERVER
08/23/2006 15:03:45.858 SP Level check successfully completed during the install process for MSSQLSERVER
08/23/2006 15:03:45.889 Product language check successfully completed during the install process for MSSQLSERVER
08/23/2006 15:03:45.905 Product version check successfully completed during the install process for MSSQLSERVER
08/23/2006 15:03:45.920 Command-line instance name check completed during the install process
08/23/2006 15:03:45.936 Baseline build check completed during the install process
08/23/2006 15:03:52.107 Attempting to install instance: MSSQLSERVER
08/23/2006 15:03:52.154 Attempting to install target: SRVLEBIZTALK
08/23/2006 15:03:52.170 Attempting to check for locked files: sqlrun_sql.msp
08/23/2006 15:03:52.232 Attempting to check for locked files: \SRVLEBIZTALKd$dd32a156dacc8dbe70a862647d70hotfixsqlFilessqlrun_sql.msp
08/23/2006 15:03:52.248 Creating MSP locked file check log at: C:WINDOWSHotfixSQL9LogsSQL9_Hotfix_KB918222_sqlrun_sql.msp.out
08/23/2006 15:04:02.107 MSP returned 1602: The user cancels installation.
08/23/2006 15:04:02.310 Successfully checked file: \SRVLEBIZTALKd$dd32a156dacc8dbe70a862647d70hotfixsqlFilessqlrun_sql.msp
08/23/2006 15:04:02.326 Successfully opened registry key: SystemCurrentControlSetControlSession Manager
08/23/2006 15:04:02.357 Failed to read registry key: PendingFileRenameOperations
08/23/2006 15:04:02.373 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnxmlfilt.dll
08/23/2006 15:04:02.388 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnThaWBrkr.dll
08/23/2006 15:04:02.435 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnquery.dll
08/23/2006 15:04:02.451 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnls400.dll.
-----------------------
It carries on with errors like the above but my post will be massive if I include it all, so below is the last few lines of the log file.
--------------------------
08/23/2006 15:04:07.591 Failed to read associated hotfix build information for the following file: C:Program Files (x86)Microsoft SQL Server90SharedMicrosoft.SqlSac.Public.dll
08/23/2006 15:04:07.653 Attempting to install file: sqlrun_sql.msp
08/23/2006 15:04:07.700 Attempting to install file: \SRVLEBIZTALKd$dd32a156dacc8dbe70a862647d70hotfixsqlFilessqlrun_sql.msp
08/23/2006 15:04:07.716 Creating MSP install log file at: C:WINDOWSHotfixSQL9LogsSQL9_Hotfix_KB918222_sqlrun_sql.msp.log
08/23/2006 15:04:07.732 Successfully opened registry key: SoftwarePoliciesMicrosoftWindowsInstaller
08/23/2006 15:04:07.747 Failed to read registry key: Debug
08/23/2006 15:05:11.197 MSP returned 1603: A fatal error occurred during installation.
08/23/2006 15:05:11.212 Successfully opened registry key: SoftwarePoliciesMicrosoftWindowsInstaller
08/23/2006 15:05:11.244 Failed to read registry key: Debug
08/23/2006 15:05:11.259 Unable to install MSP file: \SRVLEBIZTALKd$dd32a156dacc8dbe70a862647d70hotfixsqlFilessqlrun_sql.msp
08/23/2006 15:05:11.275 The following exception occurred: Unable to install Windows Installer MSP file Date: 08/23/2006 15:05:11.275 File: depotsqlvaultstablesetupmainl1setupsqlsesqlsedllcopyengine.cpp Line: 856
08/23/2006 15:05:11.322
08/23/2006 15:05:11.353 Product Status Summary:
08/23/2006 15:05:11.369 Product: SQL Server Database Services 2005 (64-bit)
08/23/2006 15:05:11.384 MSSQLSERVER - Failure
08/23/2006 15:05:11.415 Details: Unable to install Windows Installer MSP file
Hello,
We are trying to Install the Hot fix KB936305 on our SQL 2005 SP2 on Win2k3 machine. We are able to install the hotfix in our test environment but its failing in our PILOT environment. Below is the log for the installation. Any clues on why this happens??
=== Verbose logging started: 4/17/2008 4:46:37 Build type: SHIP UNICODE 3.01.4000.2435 Calling process: o:94d5ea5728f26407a1d7f52282hotfix.exe ===
MSI (c) (94:C0) [04:46:37:781]: Resetting cached policy values
MSI (c) (94:C0) [04:46:37:781]: Machine policy value 'Debug' is 0
MSI (c) (94:C0) [04:46:37:781]: ******* RunEngine:
******* Product: {EB76B218-8FC5-41DF-9F1F-7FF3E0448383}
******* Action:
******* CommandLine: **********
MSI (c) (94:C0) [04:46:37:781]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (94:C0) [04:46:37:781]: Grabbed execution mutex.
MSI (c) (94:C0) [04:46:37:875]: Cloaking enabled.
MSI (c) (94:C0) [04:46:37:875]: Attempting to enable all disabled priveleges before calling Install on Server
MSI (c) (94:C0) [04:46:37:890]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (C8:90) [04:46:37:937]: Grabbed execution mutex.
MSI (s) (C8:34) [04:46:37:937]: Resetting cached policy values
MSI (s) (C8:34) [04:46:37:937]: Machine policy value 'Debug' is 0
MSI (s) (C8:34) [04:46:37:937]: ******* RunEngine:
******* Product: {EB76B218-8FC5-41DF-9F1F-7FF3E0448383}
******* Action:
******* CommandLine: **********
MSI (s) (C8:34) [04:46:37:937]: Machine policy value 'DisableUserInstalls' is 0
MSI (s) (C8:34) [04:46:37:937]: Adding MSIINSTANCEGUID to command line.
MSI (s) (C8:34) [04:46:37:953]: End dialog not enabled
MSI (s) (C8:34) [04:46:37:953]: Original package ==> C:WINDOWSInstaller82f71.msi
MSI (s) (C8:34) [04:46:37:953]: Package we're running from ==> C:WINDOWSInstaller82f71.msi
MSI (s) (C8:34) [04:46:38:062]: APPCOMPAT: looking for appcompat database entry with ProductCode '{EB76B218-8FC5-41DF-9F1F-7FF3E0448383}'.
MSI (s) (C8:34) [04:46:38:062]: APPCOMPAT: no matching ProductCode found in database.
MSI (s) (C8:34) [04:46:38:062]: Detected that this product uses a multiple instance transform.
MSI (s) (C8:34) [04:46:38:078]: MSCOREE not loaded loading copy from system32
MSI (s) (C8:34) [04:46:38:078]: Applying multiple instance transform 'qlRun01.mst'...
MSI (s) (C8:34) [04:46:38:078]: Looking for storage transform: SqlRun01.mst
MSI (s) (C8:34) [04:46:38:078]: Validating transform 'SqlRun01.mst' with validation bits 0x809
MSI (s) (C8:34) [04:46:38:078]: Transform 'SqlRun01.mst' is valid.
MSI (s) (C8:34) [04:46:38:078]: Note: 1: 2205 2: 3: Patch
MSI (s) (C8:34) [04:46:38:078]: Note: 1: 2205 2: 3: PatchPackage
MSI (s) (C8:34) [04:46:38:078]: Note: 1: 2262 2: _Tables 3: -2147287038
MSI (s) (C8:34) [04:46:38:078]: Note: 1: 2262 2: _Columns 3: -2147287038
MSI (s) (C8:34) [04:46:38:078]: Note: 1: 2262 2: Media 3: -2147287038
MSI (s) (C8:34) [04:46:38:078]: Note: 1: 2262 2: File 3: -2147287038
MSI (s) (C8:34) [04:46:38:078]: TRANSFORM: 'PatchPackage' table is missing or empty. No pre-transform fixup necessary.
MSI (s) (C8:34) [04:46:38:078]: TRANSFORM: Applying regular transform to database.
MSI (s) (C8:34) [04:46:38:078]: Note: 1: 2262 2: _Tables 3: -2147287038
MSI (s) (C8:34) [04:46:38:078]: Note: 1: 2262 2: _Columns 3: -2147287038
MSI (s) (C8:34) [04:46:38:078]: Note: 1: 2262 2: _Validation 3: -2147287038
MSI (s) (C8:34) [04:46:38:078]: Note: 1: 2262 2: File 3: -2147287038
MSI (s) (C8:34) [04:46:38:078]: Note: 1: 2262 2: MsiFileHash 3: -2147287038
MSI (s) (C8:34) [04:46:38:078]: Note: 1: 2262 2: Signature 3: -2147287038
MSI (s) (C8:34) [04:46:38:078]: Note: 1: 2262 2: RegLocator 3: -2147287038
MSI (s) (C8:34) [04:46:38:078]: Note: 1: 2262 2: AppSearch 3: -2147287038
MSI (s) (C8:34) [04:46:38:078]: Note: 1: 2262 2: CompLocator 3: -2147287038
MSI (s) (C8:34) [04:46:38:078]: Note: 1: 2262 2: DrLocator 3: -2147287038
MSI (s) (C8:34) [04:46:38:078]: Note: 1: 2262 2: Binary 3: -2147287038
MSI (s) (C8:34) [04:46:38:078]: Note: 1: 2262 2: CustomAction 3: -2147287038
MSI (s) (C8:34) [04:46:38:078]: Note: 1: 2262 2: Directory 3: -2147287038
MSI (s) (C8:34) [04:46:38:078]: Note: 1: 2262 2: Registry 3: -2147287038
MSI (s) (C8:34) [04:46:38:078]: Note: 1: 2262 2: Condition 3: -2147287038
MSI (s) (C8:34) [04:46:38:078]: Note: 1: 2262 2: CreateFolder 3: -2147287038
MSI (s) (C8:34) [04:46:38:078]: Note: 1: 2262 2: _sqlObjectSecurity 3: -2147287038
MSI (s) (C8:34) [04:46:38:078]: Note: 1: 2262 2: Icon 3: -2147287038
MSI (s) (C8:34) [04:46:38:078]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (C8:34) [04:46:38:078]: Note: 1: 2262 2: InstallUISequence 3: -2147287038
MSI (s) (C8:34) [04:46:38:078]: Note: 1: 2262 2: AdminExecuteSequence 3: -2147287038
MSI (s) (C8:34) [04:46:38:078]: Note: 1: 2262 2: AdminUISequence 3: -2147287038
MSI (s) (C8:34) [04:46:38:078]: Note: 1: 2262 2: AdvtExecuteSequence 3: -2147287038
MSI (s) (C8:34) [04:46:38:078]: Note: 1: 2262 2: AdvtUISequence 3: -2147287038
MSI (s) (C8:34) [04:46:38:078]: Note: 1: 2262 2: _sqlAction 3: -2147287038
MSI (s) (C8:34) [04:46:38:078]: Note: 1: 2262 2: _sqlActionsModule 3: -2147287038
MSI (s) (C8:34) [04:46:38:078]: Note: 1: 2262 2: _sqlDriveType 3: -2147287038
MSI (s) (C8:34) [04:46:38:078]: Note: 1: 2262 2: ReserveCost 3: -2147287038
MSI (s) (C8:34) [04:46:38:078]: Note: 1: 2262 2: TypeLib 3: -2147287038
MSI (s) (C8:34) [04:46:38:078]: Note: 1: 2262 2: Feature 3: -2147287038
MSI (s) (C8:34) [04:46:38:078]: Note: 1: 2262 2: MsiAssembly 3: -2147287038
MSI (s) (C8:34) [04:46:38:078]: Note: 1: 2262 2: Class 3: -2147287038
MSI (s) (C8:34) [04:46:38:078]: Note: 1: 2262 2: Extension 3: -2147287038
MSI (s) (C8:34) [04:46:38:078]: Note: 1: 2262 2: PublishComponent 3: -2147287038
MSI (s) (C8:34) [04:46:38:078]: Note: 1: 2262 2: ServiceControl 3: -2147287038
MSI (s) (C8:34) [04:46:38:078]: Note: 1: 2262 2: ModuleDependency 3: -2147287038
MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: ModuleSignature 3: -2147287038
MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: ModuleExclusion 3: -2147287038
MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: ModuleComponents 3: -2147287038
MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlBuiltInAccounts 3: -2147287038
MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: MsiAssemblyName 3: -2147287038
MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: ServiceInstall 3: -2147287038
MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlNativeImage 3: -2147287038
MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlPropertyValues 3: -2147287038
MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlUserSecurity 3: -2147287038
MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlRegistry 3: -2147287038
MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlServiceControl 3: -2147287038
MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlHiveCopy 3: -2147287038
MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlRegSecurity 3: -2147287038
MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlGroup 3: -2147287038
MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlGroupMember 3: -2147287038
MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlConfig 3: -2147287038
MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlUpgradeScript 3: -2147287038
MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlHotfixScript 3: -2147287038
MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlScript 3: -2147287038
MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: ActionText 3: -2147287038
MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlSku 3: -2147287038
MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlStart 3: -2147287038
MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlServiceAccount 3: -2147287038
MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlDelimitProperty 3: -2147287038
MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlEquivalent 3: -2147287038
MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlWizardSequence 3: -2147287038
MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: Dialog 3: -2147287038
MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlMofcomp 3: -2147287038
MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlWMISecurity 3: -2147287038
MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlInstanceProperty 3: -2147287038
MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlInstanceComponents 3: -2147287038
MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlAssembly 3: -2147287038
MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlPerfCounters 3: -2147287038
MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlCollation 3: -2147287038
MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlExecutable 3: -2147287038
MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlFileSR 3: -2147287038
MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlUnmanagedComponent 3: -2147287038
MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlUpgradeComponent 3: -2147287038
MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlProducts 3: -2147287038
MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlTopLevelFeatureProducts 3: -2147287038
MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlFileRename 3: -2147287038
MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlFollowComponents 3: -2147287038
MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlLocalServers 3: -2147287038
MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlVerIndependentProgID 3: -2147287038
MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlServiceState 3: -2147287038
MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlServiceProperty 3: -2147287038
MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlServiceConfig 3: -2147287038
MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlSupportFiles 3: -2147287038
MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlDomainGroup 3: -2147287038
MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: FeatureComponents 3: -2147287038
MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: Control 3: -2147287038
MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: ControlEvent 3: -2147287038
MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: ControlCondition 3: -2147287038
MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: ListBox 3: -2147287038
MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: ListView 3: -2147287038
MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: ComboBox 3: -2147287038
MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: CheckBox 3: -2147287038
MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: EventMapping 3: -2147287038
MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: RadioButton 3: -2147287038
MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: Upgrade 3: -2147287038
MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: TextStyle 3: -2147287038
MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: UIText 3: -2147287038
MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: Media 3: -2147287038
MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: Shortcut 3: -2147287038
MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: SxsMsmGenComponents 3: -2147287038
MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: MsiSFCBypass 3: -2147287038
MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: RemoveFile 3: -2147287038
MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: RemoveRegistry 3: -2147287038
MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: Environment 3: -2147287038
MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlUpgradeFile 3: -2147287038
MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlUpgradeRegistry 3: -2147287038
MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlUpgradeFolders 3: -2147287038
MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _MsiPatchTransformView 3: -2147287038
MSI (s) (C8:34) [04:46:38:094]: Couldn't find local patch ''. Looking for it at its source.
MSI (s) (C8:34) [04:46:38:094]: Resolving Patch source.
MSI (s) (C8:34) [04:46:38:094]: User policy value 'SearchOrder' is 'nmu'
MSI (s) (C8:34) [04:46:38:094]: User policy value 'DisableMedia' is 0
MSI (s) (C8:34) [04:46:38:094]: Machine policy value 'AllowLockdownMedia' is 0
MSI (s) (C8:34) [04:46:38:094]: SOURCEMGMT: Media enabled only if package is safe.
MSI (s) (C8:34) [04:46:38:094]: SOURCEMGMT: Looking for sourcelist for product {4A35EF4A-D868-4B15-A84D-3E8925AA9558}
MSI (s) (C8:34) [04:46:38:094]: Note: 1: 1706 2: {4A35EF4A-D868-4B15-A84D-3E8925AA9558} 3:
MSI (s) (C8:34) [04:46:38:094]: SOURCEMGMT: Failed to resolve source
MSI (s) (C8:34) [04:46:38:094]: Note: 1: 1708
MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2729
MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2729
MSI (s) (C8:34) [04:46:38:094]: Product: Microsoft SQL Server 2005 -- Installation failed.
MSI (s) (C8:34) [04:46:38:140]: MainEngineThread is returning 1612
The installation source for this product is not available. Verify that the source exists and that you can access it.
C:WINDOWSInstaller82f71.msi
MSI (c) (94:C0) [04:46:38:140]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (94:C0) [04:46:38:140]: MainEngineThread is returning 1612
=== Verbose logging stopped: 4/17/2008 4:46:38 ===
I believe that I mistakenly attempted to apply the Analysis Services component of this update before applying the SQL Server component. The update now fails continuously with the following message:
02/05/2007 17:58:24.990 ================================================================================
02/05/2007 17:58:25.021 Hotfix package launched
02/05/2007 17:58:27.615 Product discovery successfully completed during the install process for MSSQLSERVER
02/05/2007 17:58:27.630 SP Level check successfully completed during the install process for MSSQLSERVER
02/05/2007 17:58:27.646 Product language check successfully completed during the install process for MSSQLSERVER
02/05/2007 17:58:27.661 Product version check successfully completed during the install process for MSSQLSERVER
02/05/2007 17:58:27.677 Command-line instance name check completed during the install process
02/05/2007 17:58:27.693 Baseline build check completed during the install process
02/05/2007 17:58:34.864 Attempting to install instance: MSSQLSERVER
02/05/2007 17:58:34.974 Attempting to install target: CHARLIDEVSRV
02/05/2007 17:58:35.005 Attempting to check for locked files: sqlrun_sql.msp
02/05/2007 17:58:35.052 Attempting to check for locked files: \CHARLIDEVSRVf$44923e05996203228c1608bea1hotfixsqlFilessqlrun_sql.msp
02/05/2007 17:58:35.067 Creating MSP locked file check log at: C:WINDOWSHotfixSQL9LogsSQL9_Hotfix_KB918222_sqlrun_sql.msp.out
02/05/2007 18:01:52.978 MSP returned 1635: This patch package could not be opened. Verify that the patch package exists and is accessible, or contact the application vendor to verify that this is a valid Windows Installer patch package.
02/05/2007 18:01:53.009 Unable to check MSP file: \CHARLIDEVSRVf$44923e05996203228c1608bea1hotfixsqlFilessqlrun_sql.msp
02/05/2007 18:01:53.025 The following exception occurred: Unable to install Windows Installer MSP file Date: 02/05/2007 18:01:53.025 File: depotsqlvaultstablesetupmainl1setupsqlsesqlsedllcopyengine.cpp Line: 689
02/05/2007 18:01:53.212 Failed to install instance: MSSQLSERVER
02/05/2007 18:01:53.259
02/05/2007 18:01:53.259 Product Status Summary:
02/05/2007 18:01:53.290 Product: SQL Server Database Services 2005
02/05/2007 18:01:53.306 MSSQLSERVER - Failure
02/05/2007 18:01:53.321
The update fails although I have cleaned the registry of any reference to it. Another article indicated that the hotfix may delete registry keys required, for instance, to operated SSIS if applied in the wrong order. Here, it appears to be preventing the hotfix from being reapplied. I have ensured that all necessary permissions are available and the services are running in domain user accounts with the necessary rights. I'm the administrator on the machine.
Is there a way to get this hotfix applied without having to completely rip and rebuild my server instance?
I am trying to use msde for the startup kits. but i cannot connect to it. How can I do a simple test to verify it is installed and that I can log into the db?
Thanks
Ron
Dear all,
I have developed a C# desktop application which uses SQL express as its database. It works just fine as I installed the application, used SQL express Server Management Studio CTP to create database with tables , stored procedures etc.
Now, I want to create an installer that will not only install my application to other machines but also create the database with all the tables and stored procedures with it.
How do I do so? I searched the answer in several places but none worked out for me. Can anyone please help me on this??
For your convenience I'm giving the following informations:
Database name: NorthPoleSQL sever Name: IshtiaqueSqlexpress (used Windows Authentication Mode)
I have detached the database from the original machine and have the NorthPole.mdf and NorthPole_Log.ldf files. I want to use these files and create the database in target machine rather than writing sql scrips and executing them.
Please help me with a descriptive, step by step instruction as I am new to this technology.
Thank you.
-Ishtiaque
hi, can I use sql server desktop edition to deploy my web application and at the same time I am not violating license agreement with Ms.
thanks
Al
What type of licence do I need to run Desktop Edition of SQL 7.0. Is there such a thing as desktop license.
How much Does it approximately cost.
Thanks
my application has a good amount of data that is specific to each company (where there is only one user). i am currently setting it up as a access project, but was wondering about another route. to store the local data would there be an advantage to setting it up as a access project, and use the sql server desktop engine for the data, or should i stick with mdb tables?
View 2 Replies View RelatedDuring installation of MSDE the installation hangs at "please wait while Windows configures microsoft sql server desktop engine" I always end up killing the installation process. I am trying to install Windows XPe dev kit and this is the step I am getting stuck on. If I try to skip this step and setup the database the setup obviously tells me that i dont have sql 200 or MSDE installed.
The KB article http://support.microsoft.com/kb/811479 describes the syptoms perfectly, but fast user switching isnt even enabled for this machine and is not the source of the problem.
its sql server 7.0 and im looking for the service network utility and service manager that it didnt come with.. where can i download it?
View 1 Replies View RelatedHello Everybody
I want to create SQL server 2005 mobile database on desktop programmatically with some inital data for my application and load it into device. We can create database only in VS2005 server explorer or SQL server 2005 application.
Anybody having this solution for this prob.
Regards
Chikuu
Hi-
I am doing some technology research for a new app and was wondering about the desktop operating system support for SQL Server compact edition. This app has a PC component and a mobile component, and both need to be data enabled, with syncronization between the PC and the mobile device.
So it seems like SSCE would be a good fit. Just run the SSCE client on both the PC and the device. But in the system requirements for SSCE it only gives XP as a valid desktop OS...
Is that correct? Obviously, desktop platform support for a production app will need to be broader than just XP.
Will SSCE desktop run on Win98,Win2000,XP Home, and Vista?
Hello,
I need to install 2187 hotfix to a sql server 2000 spanish version, but in the download section of the hotfix spanish is the only language that is not available, Anybody knows why?
Thanks in advance
Jordi.
Hi All,
We recently did the in-place upgrade of SQL 2000 server having the hotfix - 8.00.2191 (Intel IA-64). The server got upgraded successfully without any error and everything seems to work. However, after the upgrade the SQL 2000 hotfix -2191 - didn't get uninstalled. I would like to know :-
1. How we can remove this hotfix? if we remove from add
emove programs it doesn't get removed.
2. If we don't remove will it cause any problem?
Any help is highly appreciated.
Thanks,
Ritesh
My objective is to use Enterprise Manager to move (copy) my SQL db from the server to my windows desktop computer.
I downloaded MSDE and am having trouble installing it, no doubt because I do not understand the documentaion (ReadMeMSDE2000A.htm).
When I try to run setup, I get that message that says:
"A strong SA password is required for security reasons. Please use SAPWD switch to supply the same."
Considering my purpose, do I need a "strong" SA password? If not, how do I get around it? If yes, how do I set it up?
I am a Mac user so I have poor windows skills, please make it as painless as possible for me, thanks!
Ron
venu writes "Hi,
Am very new to MS SQL adminstration
Can anybody help me out how to work on Microsoft SQL Server 2000 Desktop Engine (MSDE 2000) Release A just for the practice.
The activity which am going to workout on MSDE is below.
How to install SQL(on XP)
How the layout will be(like if i insall MSDE what are all Application will be and how they depends on each other)
How to create/delete tables if so, how can we do it either by GUI or CUI
just i need a clarifications reg same
Thank you,
venu"
Hi there
Our ISP hosts our data on SQL Server Enterprise, but I also going to host the databases on my local machine.
As it's just local would Standard edition do? If I migrate the databases over, will it work?
Thanks in advance.
Help,
the installation process stops almost immediately telling me I need a superduper secure password thingy but when I try the command prompts suggested they don't work... I'm on XP home.
I have installed Visual Studio 2005 Prof Edition on a Vista machine and SQL Server 2005 Developer Edition on a Windows 2000 server. They will be used as a development environment for us. As we need to management the SQL Server 2005, we would like to install the 2005 Developer SSMS on the Vista machine such that we can manage the SQL Server 2005 developer instance installed on that Win2k machine. However, the system does not allow us to do it. We have the express edition autoamtically installed while we installed the Vistual Studio. Is there any workaround that i can still install the 2005 developer SSMS without uninstall the sql server 2005 Xpress version? Or, I have to uninstall the Xpress version before i can install the 2005 developer's SSMS? Please help!
View 11 Replies View RelatedI am getting the following warning on a Live SQL 2000 system:
This SQL Server has been optimized for 8 concurrent queries. This limit has been exceeded by 1 queries and performance may be adversely affected.
Reading about this error I realised that, by mistake, the version installed is a personal edition instead of the standard edition.
I am thinking to backup the databases, uninstall SQL 2000 Personal edition, install Standard edition and restore the databases back.
OR, disconnect the databases, uninstall the current version, install the standard version and re-connect the databases.
I haven't found within Microsoft any advice how to upgrade the personal version to the standard edition.
Because it is a live system, I would not like to mess the system up. Can you please advice?
Many thanks
I think I may have figured out the solution to my recent conundrum with SQL Server 2000 that had me stressed and depressed over the last couple of days. In a nutshell, after a HotFix was installed on a SQL2K database server I have space on, I was unable to perform INSERT or UPDATE queries on database table of type TEXT, when trying to either create or modify records with more than 4,000 characters of data. While it was frustrating as heck, it seemed too rigid to be random, so I did some snooping.
The HotFix was intended to solve a known problem of not being able to run UPDATEs against TEXT fields, but in so doing, caused another headache entirely: http://support.microsoft.com/?kbid=839523
Apparently this is a semi-known problem, in that a certain HotFix forces SQL Server 2000 to be a lot more stringent in requiring explicit declaration of data types and data lengths for parameters in stored procedure. In my client code, I was initially using the overloaded constructor of the SqlParameter object that took as arguments only the parameter name and a value, without specifying a value from the SQLDBType enumeration or length of the parameter (which in my case, needs to be TEXT and 16 (or 2147483647), respectively):
System.Data.SqlDataAdapter.InsertCommand.Parameters.Add(new SqlParameter("@parameterName",parameterValue);
It appears that after the HotFix is installed, if the client doesn’t syntactically set the type and length of data for a parameter, SQL Server and/or .NET will default to a type of NVARCHAR, which has the 4,000-character limit. This all makes sense. I’m going to now need to modify the code to straight out declare what’s going in the SPROC:
System.Data.SqlDataAdapter.InsertCommand.Parameters.Add(new SqlParameter("@parameterName",SqlDbType.Text);
System.Data.SqlDataAdapter.InsertCommand.Parameters["@parameterName"].Value = parameterValue;
It’s a minor change, and it sucks that I have to make it after the code had worked flawlessly over several thousands executions over several months, but c’est la vie! Better thay than have to rebuild my DB from scratch or switch to a new server. Changing the client code evidently is the only known fix at this time: http://support.microsoft.com/default.aspx?scid=kb%3ben-us%3b827366
Is it possible to install SQL 2000 desktop without installing a databaseserver? I need to have the interface to access my database servers, butdon't want the overhead of a server and the service on my laptop.Possible?ThanksDoug
View 2 Replies View RelatedHi all:-
How do I upgrade my local sql server 7 to sql 2000 ? Do I just put in the sql server 2000 CD and run it or is there an upgrade CD ? I have lots of stuff on my sql 7 and don't want to lose it.
Thanks in advance!
hI I M VERY MUCH NEWTO ASP.NET +SQL SERVER U CAN SAY I JUST INSTALL
BOTH WHEN I I FIRST INSTALL QUICKSTART TUTORIAL OF MS.NET2003 IT ASK ME
TO COPY MY DATABASE file to sqlserverosql -E -S (local)NetSDK -i InstPubs.sqlosql -E -S (local)NetSDK -i InstNwnd.sqlosql -E -S (local)NetSDK -i Portal.sqlosql -E -S (local)NetSDK -i Grocer.sqlwhen i tries to do that it give me the following errors
[DBMSLPCN]SQL Server does not exist or access denied.[DBMSLPCN]ConnectionOpen (Connect()).
well my sql server name is www
same as my computer name (www)services is sql servermy computer is running xp sp2and i m running .net1.1also please tell me how to Granting Access to the ASPNET usermy asp.net user name is ASP.NETif i have to reinstall sql server 2000 tell me what step i should follow to configure it correctlyi m waiting for ur QURU's answers hopefully soonhave a nice dayHUssain
I have a few questions about the SQL Server Desktop Engine (MSDE), sorry there are so many ..
1. Which software products does this come with ?
2. If I create a SQL Server Database and want to distribute it to clients, how do I actually do it with MDSE ?
3. If I need to "upgrade" my database at some point in the future (that may contain data at a client site) how would I go about getting all the data out - would I need to write an external app ?
4. What are it's pros and cons when compared to installing full SQL Server on a client site ?
5. I've heard that the preformance of an MSDE Database degrades severely after more than 5 concurrent connections, is this just due to the performance of the product or is it something to do with the licencing model ?
6. Is it possible to write applications in, say VB, to alter the database once it has been installed on client site e.g. modify/create tables, indexes, stored procedures ?
Thanks for any help in advance ..
Scott..
I have used the Upsizing Wizard in Access 2003 to convert a database to SQL. When I open it using SQL 2000 Desktop edition, I am finding a problem with the views and stored procedures.
When I open a query in design view, the tables are displayed in the upper pane without the details of the individual fields. All I get is a tick box next to *(All Columns)
If I create a new table, the same thing happens. If I create a new database, then make a table within it, any queries behave normally, with all the fields displayed.
I would be grateful for any ideas
Has anyone had trouble accessing SQL 2000 desktop install over the LAN on SBS 2003?
I cannot access my installation from the same domain, yet when I install it on a machine running something other than SBS 2003 there are no problems.
Everything seems shared correctly, and I have tried loggin on to the remote machine as Administrator with no success.
Any suggestions would be appreciated.