[mythosaz]

I've researched this problem here and by google (of course), but I'm running only into other people showing the same problem.

I have an administrative install point for Office 2000. It was originally SP1, and was correct patched to SP3 with all post-SP3 patches. OfficeUpdate correctly identifies all the post-SP3 patches, but shows that I need SP3. [I do not need SP3, it's just an error through OfficeUpdate.]

I've read a few times that this is the fault of bad settings in the SETUP.INI, but, frankly, there aren't settings in my SETUP.INI

Suggestions? Similar experiences?

[DLF]

Try searching on the M$ Office site, they must be aware of it if like you say so many people are getting same error.
P.S. Simple solution = get Office 2003 (with SP1 slipstreamed in of course).

[prathapml]

Well, the first suggestion of course would be to get a proper, un-modified Office2000 disk, and make an Admin-install point again from it. So after that, it will be at SP0 level. Then, merge SP3 directly into this source. That should most likely fix it.

[mythosaz]

Quote

Well, the first suggestion of course would be to get a proper, un-modified Office2000 disk, and make an Admin-install point again from it. So after that, it will be at SP0 level. Then, merge SP3 directly into this source. That should most likely fix it.

Nope. SP3 for Office 2000 is for SP1 and replaces SP2. You can't do a no-SP to SP3 upgrade.

Quote

Note Prior to installing SP3, you must install Office 2000 Service Release 1a (SR1a) Update.

My administrative install point is correctly built from the "prescribed" method. SP1a media from Licensing.Microsoft.COM, updated with SP3 from /downloads, then all post-SP3 administrative transforms applied manually with msiexec /p.

All products show as SP3, and all post-SP3 patches show as installed. Only OfficeUpdate is fooled.

[mythosaz]

Similar problems are reported here, but this doesn't appear to be my problem:
http://www.mcse.ms/message526646.html

And another
http://groups-beta.google.com/group/micros...67c10126d86913b

[mythosaz]

The non-administratively available Outlook View Control SR-1 update was the culprit as stated in the first article I linked.

Thanks anyway.

http://support.micro...om/?kbid=303833

Relevant Portion of the Article:

Quote

Administrative Update:
An administrative version is not available for the Outlook View Control update. The Microsoft Office 2000 Resource Kit contains several options for deploying the client update in your enterprise environment. For more information, click the following link:
http://www.microsoft...urn/ol2k-vc.htm
If your Office 2000 installation was performed from an Administrative installation point and you are using Admin patches, you can still apply this client patch to your machines because it is not a Windows Installer patch. The ActiveX control mentioned in this article that this patch is designed for is not part of the original product so there is no reference to these files in the Data1.msi which will enable this patch to be distributed to the client machines.
How to Determine Whether the Update Is Installed
The update adds or replaces the Outlctlx.dll. Outlctlx.dll version will be updated to 10.0.0.3124.

Other Information
The Outlook View Control was never installed as a component of an Office or Outlook installation. If you have this ActiveX control installed on your computer it has been installed by using one of the methods outlined in the Microsoft Knowledge Base article Q281618. For additional information, click the article number below to view the article in the Microsoft Knowledge Base:
281618 OL2000: General Information About the Outlook View Control

NOTE: You can install the Outlook View Control update even if you do not yet have the Outlook View Control installed on your computer. This ensures that you have the updated version of the ActiveX control installed on your computer so that you are protected in the event you utilize the control in the future.