Office 2003 SP2 false detection?

D

dseg

Microsoft Update says I need to install Office 2003 SP2 -- already
installed, without a hitch, 3 weeks ago. AFAIK, there's been no reissue
of SP2. Anybody else in the same situation?

d seg
 
D

David ...M...

I have the same issue, Windows updater wants to re-install Office 2003 SP2
and MBSA also reports it as uninstalled, yet I installed it via Windows
Update on 4th October.

How can this be corrrected so MBSA etc know it is installed?
 
D

dseg

I saw your post. There are some differences: on my XPH SP2 non-networked
system, Microsoft Update history shows Office 2003 SP2 as installed...
And Office Update detects, correctly, that no update is needed. Sure,
there's every reason to ignore the offer to install a second time.

Thing is, my curiosity was aroused.

dseg

 
D

David ...M...

louis said:
There appears to a problem here. See posting "Office2003 SP2 update" below

I saw your post also, and my problem is like d seg. I have Office SP2
installed, Office update shows it installed OK but MBSA and Windows update
want to install it again. I can not easily simply reinstall SP to make this
prompt go away as I have since installed KB900725, KB901017, KB905749,
KB905414, KB904706, KB896688, KB902400, KB899589 and do not want to waste all
that time reinstalling SP2 then the patches again.

Anybody know how to get MBSA and Windows Update to acknowledge SP2 is
installed successfully?
 
R

Rambus

Definitely a glitch. On this link -
http://update.microsoft.com/microsoftupdate/v6/default.aspx?ln=en-us - I was
just informed I needed to install Office 2003 SP2. I had already installed
this on 28 Sep, as confirmed when I clicked on "Review your update history"
on the same link (where Office 2003 SP2 is listed with a green "succeeded"
tick). It's also confirmed when I go to Control Panel/Add or Remove
Programs (check "Show Updates"), where Office 2003 SP2 is listed as one of
the installed components.

What triggered this nonsense is when I installed "Update for Outlook 2003
Junk Email Filter (KB906173)" yesterday. I've always used this link to
update my Windows XP-Pro/Office 2003 Pro. I've checked microsoftupdate a
couple of times between 28 Sep & yesterday, and it never mentioned Office
2003 SP2 update until today! How can it list Office 2003 SP2 as being
successfully installed (in update history) as well as tell me it's a
critical update?

Under Help/About, each of my Office 2003 software components (Excel, Word,
etc.) has SP2 on the first line.

What now?
 
P

Peter Foldes

Standard includes Word,Excel.Power Point and Outlook. Do you have any other Office Apps installed like Access,Publisher,Front Page,Visio,One Note,Project, Viewers,Map Point,Business Contact Manager(Outlook) SBE, Add In's, etc,etc?
 
D

dseg

No other Office apps. Add-ins: Remove Hidden Data Tool, Outlook Personal
Folders Backup. Off 2003 did not come pre-installed.

As poster Rambus points out, the Outlook 2003 Junk Email Filter
(KB906173) update was installed Tuesday
evening, after Automatic Update notification. For the time being, I'm
not jumping to the conclusion that the OL filter update is causing the
glitch.

BTW, a security feature was added by KB906173, i.e. a new checkbox under
Tools, Options, Preferences, Junk E-mail; as usual, at least one
security setting is reverting to default as a result of the junk filter
update.

As I said, at most, an annoyance.

d seg
 
D

David ...M...

Office Pro for me, I have Access, Excel, FrontPage, OneNote, Outlook,
Project, Publisher, Visio & Word. Also installed the patches after SP2 as
indicated in my post above.

It was not preinstalled, but installed form CD.
 
R

ranphi

I'm having this problem as well. If I scan a workstation with my WSUS server
or with the Microsoft Update web site, it says Office 2003 SP2 needs to be
installed (when, in fact, the SP has already been installed on these
workstations).

If I scan the same workstations with the MS Office Update web site, it
(correctly) states that the SP has been installed and no further updates are
needed at this time.

I have Office 2003 Pro installed with Access, Excel, InfoPath, Powerpoint,
Publisher, Outlook and Word.

Office was not pre-installed on these machines.

The latest Outlook junk email update had been applied to these machines as
well.
 
D

David ...M...

Forgot to include PowerPoint in my list :-(. As per Ranphi I have just
installed the latest Outlook spam filter and MBSA / Windows Update still
report SP2 as missing.
 
J

Jose

If you have installe SP2 already please ignore this update. We are looking
into this.

Thanks

Joseph
Software Test Engineer
Microsoft


Legal Disclaimer: This posting is provided "AS IS" with no warranties, and
confers no rights.
 
G

Goose[MS]

I believe this issue has been addressed. The site should properly detect
Office 2003 SP2.

--
Gustavo
Software Test Engineer
Microsoft

Legal Disclaimer: This posting is provided "AS IS" with no warranties, and
confers no rights.
 
R

ranphi

Thanks for the update, Gustavo. It does seem the issue has been resolved (for
my network anyway).

Unfortunately, it doesn't seem to have happened in time to prevent my WSUS
server from re-applying Office 2003 SP2 to all my workstations last night.
:p

One user with a laptop took his laptop home last night, so it wasn't here on
the network and did not get SP2 reapplied to it by my WSUS server, so I
checked his machine today with the Microsoft Update web site and it correctly
stated that the laptop did not need SP2.

Also, I was still looking into this problem last night from home (as my
laptop on my home network was experiencing the same bug) and I found that by
uninstalling and then reinstalling the latest OL junk email filter update
that the Microsoft Update web site then correctly identified that my laptop
did not need Office 2003 SP2 (whereas before doing so, it was saying my
laptop needed SP2 even though it had previously been installed, just like all
the workstations in my office).

Can you offer any insight into what caused the problem and what exactly
fixed it? I'm curious to know.

Thanks!
 
D

David ...M...

I just checked and it is working OK now for me. MBSA reports no issues now
with Office SP2 so it has been fixed :)
 
T

txcatalyst

Careful, the binary patch was pulled from MU and replaced with the full
file patch, due to issues with needing access to source files for the
binary difference patch.

So, what you are seeing is the full file patch.

You should set this to Disregard.

The full file will decrease the likelihood of the source cabinets being
needed, but not eliminate the need in all environments.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top