Installing this update on a Windows 2003 SBS server in order for Vista to actually work with OWA. It comes up with an error that says "At minimum, you must have Service Pack 2 installed." This server DOES have SP2 installed on it. I even ran Windows Update and installed every update available. It still won't install and Vista still doesn't work with OWA. Is there a solution for this? I still can't believe Microsoft didn't bother to test OWA with Vista before it went to market. Yet another reason to hate Vista.

Hi, Please check the KB911829.log (C:\Windows) for further information. You can also post the log file here for further research. In addition, I think the Service Pack 2 is for Exchange Server. System Requirements Supported Operating Systems: Windows 2000 Service Pack 4; Windows Server 2003; Windows Server 2003 R2 (32-Bit x86); Windows Server 2003 Service Pack 1 Exchange 2003 SP2 must be installed prior to installing this update. Mike

[KB911829.log]0.188: ================================================================================0.188: 2008/07/19 14:44:20.046 (local)0.188: e:\3f7b816d0285bd95a98108efc4823a91\update\update.exe (version 6.1.22.4)0.250: DoInstallation: GetProcAddress(InitializeCustomizationDLL) Returned: 0x7f 0.297: Hotfix started with following command line: 0.375: CreateUserInterface: GetProcAddress for DefineInstallCustomUI failed: 0x7f0.375: DoInstallation: CustomizeCall Failed: 0xf076 0.375: Setup has detected that the version of the service packinstalled on your system is lower than what is necessary to apply this hotfix. At minimum, you must have Service Pack 2 installed.4.735: Message displayed to the user: Setup has detected that the version of the service packinstalled on your system is lower than what is necessary to apply this hotfix. At minimum, you must have Service Pack 2 installed.4.735: User Input: OK4.735: Update.exe extended error code = 0xf0764.735: Update.exe return code was masked to 0x643 for MSI custom action compliance.0.094: ================================================================================ I wonder why Microsoft Update didn't offer Exchange SP2? I checked and Exchange is only on SP1 for this server. Wonderful. Thanks for the info. I'll try that next.

Hi, I suggest you firstly have Exchange SP2 installed and check the result again. If the update still cannot be installed, please post the latest KB911829.log again. Mike

I have some similar problem when try to install KB930807, KB911829 and KB937788, but in my case Exchange 2003 have SP2 already installed. In Exchange server properties I see version 6.5 (Build 7638.2: Service Pack 2).Install log for KB937788 below.[install.log]0.031: ================================================================================0.031: 2009/03/23 09:38:00.464 (local)0.031: c:\4192a5827b07fffa66a7\update\update.exe (version 6.1.22.4)0.031: DoInstallation: GetProcAddress(InitializeCustomizationDLL) Returned: 0x7f 0.031: Hotfix started with following command line: /log:c:\install.log 0.047: CreateUserInterface: GetProcAddress for DefineInstallCustomUI failed: 0x7f0.047: DoInstallation: CustomizeCall Failed: 0xf076 0.047: Setup has detected that the version of the service packinstalled on your system is lower than what is necessary to apply this hotfix.At minimum, you must have Service Pack 2 installed.2.391: Message displayed to the user: Setup has detected that the version of the service packinstalled on your system is lower than what is necessary to apply this hotfix.At minimum, you must have Service Pack 2 installed.2.391: User Input: OK2.391: Update.exe extended error code = 0xf0762.391: Update.exe return code was masked to 0x643 for MSI custom action compliance.

Any ideas? i already have EXCH SP2 installed?? [KB911829.log] 0.156: ================================================================================ 0.156: 2009/08/25 12:05:59.574 (local) 0.156: d:\b273f46e9fa101bd3967b2\update\update.exe (version 6.1.22.4) 0.156: DoInstallation: GetProcAddress(InitializeCustomizationDLL) Returned: 0x7f 0.172: Hotfix started with following command line: 0.547: CreateUserInterface: GetProcAddress for DefineInstallCustomUI failed: 0x7f 0.547: DoInstallation: CustomizeCall Failed: 0xf076 0.547: Setup has detected that the version of the service pack installed on your system is lower than what is necessary to apply this hotfix. At minimum, you must have Service Pack 2 installed. 279.625: Message displayed to the user: Setup has detected that the version of the service pack installed on your system is lower than what is necessary to apply this hotfix. At minimum, you must have Service Pack 2 installed. 279.625: User Input: OK 279.625: Update.exe extended error code = 0xf076 279.625: Update.exe return code was masked to 0x643 for MSI custom action compliance.

I have some similar problem when try to install KB930807, KB911829 and KB937788, but in my case Exchange 2003 have SP2 already installed. In Exchange server properties I see version 6.5 (Build 7638.2: Service Pack 2). Install log for KB937788 below. [install.log] 0.031: ================================================================================ 0.031: 2009/03/23 09:38:00.464 (local) 0.031: c:\4192a5827b07fffa66a7\update\update.exe (version 6.1.22.4) 0.031: DoInstallation: GetProcAddress(InitializeCustomizationDLL) Returned: 0x7f 0.031: Hotfix started with following command line: /log:c:\install.log 0.047: CreateUserInterface: GetProcAddress for DefineInstallCustomUI failed: 0x7f 0.047: DoInstallation: CustomizeCall Failed: 0xf076 0.047: Setup has detected that the version of the service pack installed on your system is lower than what is necessary to apply this hotfix. At minimum, you must have Service Pack 2 installed. 2.391: Message displayed to the user: Setup has detected that the version of the service pack installed on your system is lower than what is necessary to apply this hotfix. At minimum, you must have Service Pack 2 installed. 2.391: User Input: OK 2.391: Update.exe extended error code = 0xf076 2.391: Update.exe return code was masked to 0x643 for MSI custom action compliance. did you manage to fix this issue?