February 10, 2009 at 7:07 am
Hi
I have the 32-bit version of SQL Server 2000 (SP4) running on a 64-bit server.
The server has 64gb of memory, but sql server is only using 32gb. I've identified hotfix KP899761 (http://support.microsoft.com/kb/899761) to solve this problem. This should patch to version 8.00.2040
I tried it out on 2 32-bit test servers and the problem was solved.
However, when i run it on the 64-bit server it will not let me patch sql server. The error is "The product does not have a prerequisite update installed. The installation is dependent on the prerequisite update and cannot be installed. Exit setup and refer to the Knowledge Base article to find the prerequisite patch. Install the prerequisite and rerun the installation."
The hotfix seems to think the instance is at RTM, but the server properties clearly state 8.00.2039 SP4.
The hotfix says the installation exe if for both x86 and x64 servers.
Any help would be appreciated.
David Uden
February 15, 2009 at 1:24 pm
anyone, please ?
February 16, 2009 at 3:16 am
What is the result of select serverproperty('productlevel'),serverproperty('productversion') on your problematic server?
MJ
February 16, 2009 at 3:38 am
Hi MJ
They return the correct values as per the server properties window, i.e. SP4, 2039.
@@VERSION also returns the correct values
Cheers
David
February 16, 2009 at 6:13 am
Does the log file for the hotfix install give any clues? Assuming the hotfix is a .msi you can add a parameter /LOG "C:\hotfixlog.txt" If you have a .exe the syntax sometimes needs to be /LOG:"C:\hotfixlog.txt"
If you can get a root cause error message from the log, Google may give you an idea on ho to get round the problem. However, if the install really is complaining about something that is already in place you may need to raise a problem ticket with Microsoft.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
February 17, 2009 at 1:46 am
Hi
I ran with the log file switch, but it doesn't really give any indication of why it thinks ther version is RTM.
Log file:-
[loghf.log]
0.062: ================================================================================
0.062: 2009/02/17 08:16:54.597 (local)
0.062: e:\4cfd2639cb15477cefa5bdd967\amd64\update\update.exe (version 6.1.22.5)
0.328: SQL DLL: Adding /allinstances switch
0.328: SQL DLL: User account information not provided on command line
0.328: SQL DLL: Parsing product attributes
0.343: SQL DLL: Product instance MSSQLServer was disqualified due to SP Level mismatch
0.359: SQL DLL: Adding product instance MSSQLServer to uninstall state list
0.359: SQL DLL: There were 1 product instances added to the uninstall state list
0.359: Hotfix started with following command line: /LOG:D:\loghf.log
0.375: SQL DLL: Callback Function DefineInstallCustomUI
0.375: SQL DLL: Adding custom UI for attended mode
0.375: CreateUserInterface: DefineInstallCustomUI returned 0x0
0.375: SQL DLL: Callback Function BeginInstallation
0.375: SQL DLL: Skipping authentication checks since running in attended mode
1.468: In Function TestVolatileFlag, line 11660, RegOpenKeyEx failed with error 0x2
1.468: In Function TestVolatileFlag, line 11692, RegOpenKeyEx failed with error 0x2
1.468: ---- Old Information In The Registry ------
1.468: Source:C:\Program Files (x86)\Sophos\Sophos Anti-Virus\62ad41a7.stf
1.468: Destination:
1.468: Source:C:\WINDOWS\system32\567a1e38.stf (1.0.0.3821)
1.468: Destination:
1.468: Source:C:\Program Files (x86)\Sophos\Sophos Anti-Virus\567a1e38.stf (1.0.0.3821)
1.468: Destination:
1.468: ---- New Information In The Registry ------
1.468: Source:C:\Program Files (x86)\Sophos\Sophos Anti-Virus\62ad41a7.stf
1.468: Destination:
1.468: Source:C:\WINDOWS\system32\567a1e38.stf (1.0.0.3821)
1.468: Destination:
1.468: Source:C:\Program Files (x86)\Sophos\Sophos Anti-Virus\567a1e38.stf (1.0.0.3821)
1.468: Destination:
1.468: SetProductTypes: InfProductBuildType=BuildType.IA
1.468: SetAltOsLoaderPath: No section uses DirId 65701; done.
1.468: IncludeDirectoryIdFromInfSection: No DirId found for: DontRemoveOnUninst.DirId
1.468: SQL DLL: Callback Function DynamicStringInstancePath
1.468: SQL DLL: Error, DynamicStringInstancePath failed because no active product instance found
1.468: SetDynamicDirectoryId: Failure while generating dynamic path, 0xf111
1.484: DoInstallation: FetchSourceURL for e:\4cfd2639cb15477cefa5bdd967\amd64\update\update.inf failed
1.500: LoadFileQueues: UpdSpGetSourceFileLocation for hal.dll failed: 0xe0000102
1.500: BuildCabinetManifest: update.url absent
1.515: Starting AnalyzeComponents
1.515: AnalyzePhaseZero used 0 ticks
1.515: OEM file scan used 0 ticks
1.515: AnalyzePhaseOne: used 0 ticks
1.515: AnalyzeComponents: Hotpatch analysis disabled; skipping.
1.515: AnalyzeComponents: Hotpatching is disabled.
1.515: AnalyzePhaseTwo used 0 ticks
1.515: AnalyzePhaseThree used 0 ticks
1.515: AnalyzePhaseFive used 0 ticks
1.515: AnalyzePhaseSix used 0 ticks
4.062: AnalyzeComponents used 2547 ticks
4.062: Downloading 0 files
4.062: bPatchMode = FALSE
4.062: Inventory complete: ReturnStatus=0, 2562 ticks
14.078: Message displayed to the user: Are you sure you want to cancel?
14.078: User Input: YES
16.515: SQL DLL: Callback Function EndInstallation
16.515: SQL DLL: Callback Function FailedInstallation
16.515: KB899761(ENU) Setup canceled.
17.984: Message displayed to the user: KB899761(ENU) Setup canceled.
17.984: User Input: OK
17.984: Update.exe extended error code = 0xf00d
17.984: Update.exe return code was masked to 0x643 for MSI custom action compliance.
February 17, 2009 at 3:54 am
I think you have a couple of options...
1) Try the latest CU update for SP4. See http://support.microsoft.com/kb/894905/ for details. The problem you have may be fixed in a later CU.
2) Running SQL 2000 32-bit on a 64-bit server is not a common situation. You may be hitting a bug in the install process. In this situation you will need to contact Microsoft for assistance.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply