service pack 2 office xp Results

Page 1 of 4.
Results 1...20 of 76

Sponsored Links:

General opinions of Service Pack 2 for Office XP or links to good/bad about this pack

Hi There,

I have posted a like message in the Outlook newsgroup which details the
same problem I have been having post WinXP SP2. I have done my best to
confirm that it is indeed Service Pack 2 that is causing the bug, and
not a configuration issue. The software involved is Windows XP
Professional, Windows XP Home and Office 2000 SP3 and updates.

The Problem: Under WinXP SP1a I was able to perform the toolbar command
to insertHTMLbgsound in Word or Outlook with Word as the editor. This
would allow the MIDI or WAV to be embedded into an email message or
into a Word document. I installed Service Pack 2 and the command no
longer works, giving me an error that says:

"The server application, source file, or item can not be found. Make
sure the application is properly installed, and that it has not been
deleted, moved or renamed."

I can still, however, insert a bgsound into an Outlook Express email,
but I require the use of Outlooks tables, though, so OE is not an
option, and I do require the ability to have a background sound on email
and on word documents so that there is no user intervention required.

What I have done to verify and rectify: I have tried repairing the
Office installation but that did not help. I then tried installing
Office on this computer which has Open Office and Thunderbird and has
never had office on. This machine uses WinXP Pro and had service pack 2
installed prior to my installing Office. Again, the same error message
comes up. So I patched Office to SP3 and again the same. I finally dug
out one of the surplus computers and a blank hard drive and installed
WinXP and left it at the SP1a level. I installed Office 2000 and updated
it to SP3, tried to insert sound into a word document and into an
Outlook email using Word as the editor and it worked fine. I then
installed WinXP SP2 on the test machine, and, again, the product fail to
deliver the function and I get nothing more than a window with the
aforementioned error in it.

I don't know if this was a mistake made on the part of the SP2
development team, or if Microsoft thinks it is feasible to phase out
older products by fading them out with subtle crippling effects and
reductions of functionality built in the name of security patches and
"updates". I do so hope it is the former, but the requirement of Norton
2004 for Windows integration tells a tale, don't you think? Not that I
am worried, Norton has looked after itself fine for years without
Windows Security Center


(remove NO MEAT to respond)

I downloaded Office XP Service Pack 2 and have tried to install it and it won't take. First it asked me to put in the Office CD w/ Outlook on it which I did. Then it started "Gathering information about Word" and said "The expected version of the product was not found on your system." I have a genuine, non-pirated copy of Office XP Developer, which has been registered w/ Microsoft over the phone. Any ideas/suggestions?


Patch Tuesday for December 2009, last of this year

Microsoft is set to release six patches on December 8, 2009. Three of the six patches are marked as "critical", Microsoft's highest

rating, while the other three patches are labeled as "Important". These six patches should be the last release package of the year from Microsoft.

Microsoft will be patching a remote code execution on fix out of six patches and one denial of service security hole. The six patches that will be released on Tuesday will patch holes in Windows, Microsoft , and Internet Explorer.

The patches will fix security holes in:

Internet Explorer 5, 6, 7 & 8Windows 2000 Service Pack 4Windows XP Service Pack 2 & 3Windows Vista Service Pack 1 & 2*Windows Server 2003 Service Pack 2*Windows Server 2008 Systems Service Pack 2*Office XP Service Pack 3Office 2003 Service Pack 3* Both 32bit and 64bit architecture

I have Windows and Office XP installed. All have been running fine for
months. Installed Windows XP SP 2 and Outlook broke. Clicking on New
Message would open multiple Outlook windows AND multiple Internet Explorer
windows! Outlook locked frequently just reading messages. I killed all
memory resident stuff, including antivirus, turned off the firewall, and
stripped it down to bare essentials. Problem persisted. I uninstalled SP 2
(not a pretty process, by the way) and Outlook now works perfectly again.

Anyone else seen this? Beware!

I downloaded and installed the latest security patch from microsoft MS04-028 to my administrative installation of office. Big mistake. It applied SP 3 without saying that it was doing so. The documentation on this was VERY vague: "Office XP Service Pack 3 (SP3) must be installed. Before you install this update, install Office XP SP3. For additional information about how to install Office XP SP3, see Microsoft Knowledge Base Article 832671. The administrative update can also be installed on systems that are running Office XP Service Pack 2 or Office XP Service Pack 3. The security update for Office XP Service Pack 2 is only provided as part of the Office XP administrative security update."
From the last sentence, I assumed that there was a version that you could install to an SP 2 admin install. I then clicked on a link that said Microsoft Office XP SP2 - download administrative update.
Luckily I was able to restore from backup. Has anyone else run into anything like this? Does anyone know if there really is a version you can apply to SP2 without upgrading to SP3?

This addresses some issues that haven't been fixed previously including one I think I've seen in the lounge which is jpeg distortion when pasted in an Office doc and then embedded in OLE/or OE if you prefer. This includes all the hotfixes that have been released since SP2, and requires that SP1 and SP2 which requires SP1 already be installed. This also might be convenient for those who have recently purchased Office XP either on a computer or in a box. It has been reduced since Office 2003 is coming close to Halloween.

Q823327: Availability of the Office XP Post-Service Pack 2 Rollup Package: July 3, 2003


Terminology Confusion:

Woody has said “Word 2002 Service Pack 3 (that's the version of Word in Office XP.”

I am running Win XP, Version 2002, Service Pack 2. (Word 2002)

Under Microsoft Office Programs, I have Office and Office 10.

Question: what does “that’s the version of Word in Office XP” mean?

Does it mean because I didn't download SP 3 my info is still showing as SP2? If I were to download it, would that info be reflected in my System Properties' General tab?

Thank you.


I just downloaded Service Pack 2 for Office XP. Before I install it has anybody heard any horror stories about this service pack which I ought to be aware of?

How do I determine if I have Service pack 1 installed? Apparently I need this done before installing service pack 2.

Hello, i've bought a pc not long ago and it was running windows 7 (64bit)
Running PERFECTLY , never a single freeze or a bsod.
Yesterday i went to my brother's office 2 play some games and i didnt take my monitor with me. There was plenty of monitors in the office so i took the first one and plugged it to my pc.
Surprisingly windows loaded with a black screen and i could move mouse but nothing was happening. So i restarted same thing black monitor nothing's happening, i plugged another monitor and another but all had same problem. Black screen after loading right where the username and password supposed to come. So i went home took my monitor and hell black screen, i decided to wait and i waited for about 15 minutes and black screen disappeared windows loaded, i thought nightmare was over but after that when i entered "starcraft2" i got a blue screen of death and pc restarted. For last 16 hours i was trying to fix this problem but nothing is helping. Windows is restarting whenever it wants , either if i enter a game such as "fallout 3 ,starcraft2, half life 2, or similar" or even when im just browsing internet. First i get message IE has stopped working windows is looking for a solution. I enter world of warcraft i get critical error game closes few minutes bsod again.
I reinstalled windows 7, bsods were still coming, i formatted drive and installed windows XP sp2 updated all drivers and still i get critical error and system restarts. I upgraded winxp to windows 7 and after installing all drivers from ATI and MSI i still get bsods i formatted drive again and install windows XP again. But im giving up, reinstalling windows and drivers just doesnt help. There must be something more advanced which a simple user cant know.. Such as maybe default onboard video card is causing problem or automatic bios update with msi live update 4 did something to the computer.
I m guessing its possible to read some info from dump file but i dont understand anything there. Can somebody help me?

Here's the current condition of the computer
System Information
Operating System: Windows XP Home Edition (5.1, Build 2600) Service Pack 2 (2600.xpsp_sp2_gdr.100216-1441)
Language: English (Regional Setting: English)
System Manufacturer: MSI
System Model: MS-7636
BIOS: Default System BIOS
Processor: Intel(R) Core(TM) i3 CPU 530 @ 2.93GHz (4 CPUs)
Memory: 3064MB RAM
Page File: 283MB used, 4665MB available
Windows Dir: C:WINDOWS
DirectX Version: DirectX 9.0c (4.09.0000.0904)
DX Setup Parameters: Not found
DxDiag Version: 5.03.2600.2180 32bit Unicode

ATI Radeon HD 5600 Series
ATI Technologiec Inc.
ATI Radeon Graphics Processor (0x68D8)
Internal DAC (400MHz)
1024.0 MB
Plug and Play Monitor
No problems found.

Im going to install a fresh new copy of windows 7 right now and hopefully it will work but if it doesnt then i will upload a dump file.
If anybody had similar problems i would appreciate any advice.

I have been having problems with my home network since installing XP
service pack 2 on my two computers. What I would like to do is share
the broadband connection on the host with the client and enable file
sharing between the two computers. The computers are joined by cable
with onboard ethernet adapters on both. The host machine is using
Kerio Personal Firewall and Norton Antivirus. The client is using the
Microsoft Firewall in SP2 and AVG Anti Virus.

The host machine has the following network settings:

The client has:

After setting up the network using the Home / Small Office Network
wizard, the network works fine for two days then fails. The two
computers simply cannot see each other (including when using Ping).
I've noticed that when the IP address is obtained automatically after
network failure on the client, the address is obtained.
I have also tried setting up the network manually - again it appears
fine for a couple of days then refuses to work, even if the ip address
appears to be valid. NetBIOS is enabled on both computers.

The only way I have found to reset the network is to reinstall the
network cards, then run the Home / Small Office Network wizard. As
you can imagine, doing this every other day has got old very fast!

Does anyone have any idea what the problem might be?



My computer got upgraded with Service Pack 2.

During boot-up, the Microsoft Office toolbar is loaded -
with no buttons shown - , and the computer is frozen for
more than a minute until the buttons appear.


I have 3 computers set up as a home office network with a
Linksys router, but only one printer attached to one of
the computers.

I was able to send output to the printer from any of the
3 computers.

NO MORE AFTER THE UPGRADE, unless I disable the firewall.

Going from bad to worse, with nobody to complain to or
request assistance.

Of course I can always use the restore point before the
upgrade, or re-install windows from the original CD.

I wish I could use my computer which I paid for with my
own money the way I want to, but unfortunately that will
only happen when Bill Gates goes to hell.

After a successful installation of XP SP2, I was told that I needed to
reboot the computer to continue. I restarted and the machine refused
to boot. I get an error right after POST stating the ntldr is
missing, press CTRL-ALT-DEL to continue. I've detailed the steps
from the support team to fix this problem (although it didn't work) at
the bottom of this message.

Background: Windows XP Home - freshly installed about 2 months ago
because of new hard drive - 256 MB RAM, 1 Ghz PIII - Perfectly stable
machine - On 24 hrs/day.

[INDIA RANT ON] After searching the web for a solution, I called
Microsoft Technical Support for Service Pack 2. As it turns out,
Technical Support for this company is in India and these folks have no
clue what to do. When they run out of answers, they have no one to
turn to for help. Besides the fact that they weren't helpful, they
spoke terrible English and we kept repeating ourselves. What a waste
of time. Their final answer, delete your hard drive partition and
reinstall the OS and all of your applications! I was told that I
MIGHT lose some data doing this. Also, I was told that I should boot
into safe mode. I spent 5 minutes explaining what the OS loader's
(ntldr) function was -- booting. No OS loader, no safe mode. Any
Indian that is remotely qualified quickly quits their $3/hr job and
comes to America to do better. This doesn't leave much. Sorry for
the rant, but why have unqualified people answering the phone with no
escalation path!!! [INDIA RANT OFF]

Back to the problem and resolution... Here are the steps that we
tried. Maybe it'll help someone else.

1) Boot into Recovery Console using the CD
2) FIXMBR - this supposedly fixes problems with the Master Boot Record
3) FIXBOOT - this rewrites a new boot partition
4) Assumed ntldr is corrupt, so copy a new version of ntldr and from d:i386 where d: is the CD.
6) BOOTCFG /REBUILD - this rebuilds the boot.ini file if it
7) I was even asked to reinstall Windows. However, this solves
nothing, since a Windows installation does not touch the boot
partition, unless the OS finds that it is a complete new installation
on a new partition. I tried both a repair installation of Windows and
a Fresh installation of Windows. Neither would boot.

After each of these commands, we ended up rebooting the computer. In
my case, none of these steps fixed the problem. Once I deleted the
partition and reinstalled Windows, I was back up and running. Now,
I'm 2 hours into my 6 hours reinstallation ordeal! I now have XP home
loaded, + SP2, + Office. Much more to do.

ADVICE: BACKUP YOUR DATA before corrupting your system with SP2.

The technican had no advice for being able to save my data. Luckily,
this was a sedonday machine and had nothing important on it.


I just built a new machine with a clean install of Win XP Pro and SP2. I'm
in the process of installing my software programs (i.e quicken, MS office,
Photoshop etc.). I have 2 programs that will not install, whether they are
run from a hard drive or a cd rom. When I double click the setup.exe file, I
get nothing but a quick glance at the hourglass on my mouse/pointer.

One program is my Camedia software for my digital camera, another is an
Adobe program. Both programs initialize and install perfectly fine when run
on my Win98 box--they do nothing on my Windows XP machine (both are networked
on a VPN). Any help on why the setup files won't run and start the install
process is greatly appreciated!!

Here's what I've tried to install the software--all with the same result:
1. Copied installation software from cd-rom or hard drive to XP machine's C:
drive or slave drive. Run or double click setup.exe file -- nothing.
2. Swapped 2 different CD rom drives and tried the instal from both..
3. Put CD in Win 98 cd rom and tried running on XP machine thru explorer.
Did same with install files residing on Win 98 box while accessing from Win
XP box.
4. Tried same and used remote desktop from 98 box to run XP box.
5. Tried changing compatibility wizard and settings of EXE file.
6. Turned off hyperthreading in Bios.
7. Limited swap file to 512 MB from 1 gig
8. Tried installing from Safe mode.
9. uninstalled SP2
10. changed screen resolution and color depth
That's all my brain can remember.

The setup.exe file is: InstallShield Corporation file version:

System Info:
OS Name Microsoft Windows XP Professional
Version 5.1.2600 Service Pack 2 Build 2600
OS Manufacturer Microsoft Corporation
System Type X86-based PC
Processor x86 Family 15 Model 2 Stepping 9 GenuineIntel ~2806 Mhz
Processor x86 Family 15 Model 2 Stepping 9 GenuineIntel ~2806 Mhz
BIOS Version/Date American Megatrends Inc. 1002.002, 2/25/2004
SMBIOS Version 2.3
Windows Directory C:WINDOWS
System Directory C:WINDOWSsystem32
Boot Device DeviceHarddiskVolume1
Locale United States
Hardware Abstraction Layer Version = "5.1.2600.2180 (xpsp_sp2_rtm.....)"
Total Physical Memory 1,024.00 MB
Available Physical Memory 764.39 MB
Total Virtual Memory 2.00 GB
Available Virtual Memory 1.96 GB
Page File Space 2.40 GB
Page File C:pagefile.sys

Any help is appreciated. Thanks in advance.

I have the exact same problem with my HP (a530n). Installed everything the
manufacturer requested, then installed SP2 from a Microsoft SP2 CD.
Everything appears to work fine, but the computer hangs when restart is
selected. If I turn it off, then turn it back on, it boots perfectly. The
RESTART option is the only thing that is apparently no longer working. The
screen goes black (LCD monitor) and the HD light stays constantly lit, even
though the HD is not active. A friend of mine has the exact same system with
the exact same problem. BTW, the bios has been updated and all drivers are

I'm really surprised that so many people are having this problem, and no
simple solution is available (yet another MS patch, or something).
Re-installing or manually modifying OS files is not a simple solution.

Can anyone help with resolving this problem?

"Rock" wrote:

Sixpack wrote:

When I try to "Restart" with XP SP2 my computer hangs at "Windows is shutting
down...". If I do a "Turn Off", it works fine. Any thoughts on how to
fix this.

Ignore user 1. His whole purpose, it seems, is to jump on anyone's post
who has a any type of problem post SP2 and offer no help but to blame
SP2. His only resolution is remove SP2.

As to your shutdown problem this can happen in any version of Windows
XP. See this excellent troubleshooting tool for shutdown problems.

To get a good install of SP2 make sure the system is running good with
no malware. See these links for preparation:

Installing Service Packs

Pre-Install, Install, Cleaning Up Afterwards

What to Know Before You Download and Install Windows XP Service Pack 2

Get the Latest Updates and Information from Your PC Manufacturer Before
Installing Windows XP Service Pack 2

Using programs and hardware with Service Pack 2 (SP2);ln;xpsp2swhw

Programs that may behave differently in Windows XP Service Pack 2

If running Office 2003 make sure you have the latest Service Pack

Changes to Functionality in Microsoft Windows XP Service Pack 2

Windows XP Service Pack 2: What's New for Internet Explorer and Outlook

Windows XP Service Pack 2 Support Center;windowsxpsp2

Free Technical Support for SP2

So there seems to be a problem with DCOM or RPC over the Windows XP SP2

The problem above manifests itself when you use MSinfo32.exe to collect info
on an external computer. And also appears when you try access the disk
manager of the remote pc, via the Computer Management Snap-in. Also the
Resultant Set of Policy: - "RPC Server is Unavailable"

Discounted all other things, as RSoP and all of the above works just fine
with the firewall turned off.

Also note, that all the firewall settings are being pushed via Group Policy,
and that the policy is not being overidden by anything above it, the
application of the correct settings can be observed live on the client.

Now via Group Policy, you can set some settings that are suppose to open up
all the management ports you could need within your lan/domain:

Windows Firewall: Allow local program exceptions

This will open up the following ports on the client machines:

TCP Port 135 for (DCOM) (DCE/RCP Endpoint Mapper)
TCP Port 445 for (RPC)

Allows remote administration of this computer using administrative tools
such as the Microsoft Management Console (MMC) and Windows Management
Instrumentation (WMI). To do this, Windows Firewall opens TCP ports 135 and
445. Services typically use these ports to communicate using remote
procedure calls (RPC) and Distributed Component Object Model (DCOM). This
policy setting also allows SVCHOST.EXE and LSASS.EXE to receive unsolicited
incoming messages and allows hosted services to open additional
dynamically-assigned ports, typically in the range of 1024 to 1034.
If you enable this policy setting, Windows Firewall allows the computer to
receive the unsolicited incoming messages associated with remote
administration. You must specify the IP addresses or subnets from which
these incoming messages are allowed.
If you disable or do not configure this policy setting, Windows Firewall
does not open TCP port 135 or 445. Also, Windows Firewall prevents
SVCHOST.EXE and LSASS.EXE from receiving unsolicited incoming messages, and
prevents hosted services from opening additional dynamically-assigned ports.
Because disabling this policy setting does not block TCP port 445, it does
not conflict with the "Windows Firewall: Allow file and printer sharing
exception" policy setting.
Note: Malicious users often attempt to attack networks and computers using
RPC and DCOM. We recommend that you contact the manufacturers of your
critical programs to determine if they are hosted by SVCHOST.exe or
LSASS.exe or if they require RPC and DCOM communication. If they do not,
then do not enable this policy setting.
Note: If any policy setting opens TCP port 445, Windows Firewall allows
inbound ICMP echo request messages (the message sent by the Ping utility),
even if the "Windows Firewall: Allow ICMP exceptions" policy setting would
block them. Policy settings that can open TCP port 445 include "Windows
Firewall: Allow file and printer sharing exception," "Windows Firewall:
Allow remote administration exception," and "Windows Firewall: Define port

Then you also have this one:

Windows Firewall: Allow File and Print Sharing exception

This will open up the following ports on the client machines:

TCP Port 139 (Netbios Session Service)
TCP Port 445 (RPC)
UDP Port 137 (Netbios Name Service)
UDP Port 138 (Netbios Datagram Service)

Allows file and printer sharing. To do this, Windows Firewall opens UDP
ports 137 and 138, and TCP ports 139 and 445.
If you enable this policy setting, Windows Firewall opens these ports so
that this computer can receive print jobs and requests for access to shared
files. You must specify the IP addresses or subnets from which these
incoming messages are allowed. In the Windows Firewall component of Control
Panel, the "File and Printer Sharing" check box is selected and
administrators cannot clear it.
If you disable this policy setting, Windows Firewall blocks these ports,
which prevents this computer from sharing files and printers. If an
administrator attempts to open any of these ports by adding them to a local
port exceptions list, Windows Firewall does not open the port. In the
Windows Firewall component of Control Panel, the "File and Printer Sharing"
check box is cleared and administrators cannot select it.
If you do not configure this policy setting, Windows Firewall does not open
these ports. Therefore, the computer cannot share files or printers unless
an administrator uses other policy settings to open the required ports. In
the Windows Firewall component of Control Panel, the "File and Printer
Sharing" check box is cleared. Administrators can change this check box.
Note: If any policy setting opens TCP port 445, Windows Firewall allows
inbound ICMP echo requests (the message sent by the Ping utility), even if
the "Windows Firewall: Allow ICMP exceptions" policy setting would block
them. Policy settings that can open TCP port 445 include "Windows Firewall:
Allow file and printer sharing exception," "Windows Firewall: Allow remote
administration exception," and "Windows Firewall: Define port exceptions."

But unfortunatly, this doesnt seem to help.

Now MS KB article 875605 (How to troubleshoot WMI-related issues in Windows
XP SP2) also tells me to
- Create a program exeption for uncecapp.exe - Done, no dice
- Explicitly open port 135 - Done, still no dice.
- Edit the DCOM remote launch permissions. - Done, officer, I still dont
have any dice.

I really cant think of anything else at this point. I guess I will have to
dig into DCOM and pull out the network monitor for this. *sigh*

Consulted sources so far: - SP2 Windows Firewall
programs exceptions list issues... - Direct Hosting of SMB Over TCP/IP;en-us;840634 - You receive
an "Access denied" or "The network path was not found" error message when
you try to remotely manage a computer that is running Windows XP Service
Pack 2 -
Changes to Functionality in Microsoft Windows XP Service Pack 2 - Diskpart
And Nu2menu Problem -
Managing Windows XP Service Pack 2 Features Using Group Policy

If anyone has any idea's, it would be appraciated!

I am using Outlook XP to access an IMAP mail account. Office XP was installed as an upgrade to Office 2000, and Outlook migrated all of the settings from the previous version to XP.

I was having some stability problems with Outlook 2002, so I was playing with my rules. Prior to my upgrade I had one rule which would move a copy of all messages I sent to a server-based Sent Items folder. This worked without a problem for months with Outlook 2000.

When I reviewed the Rules, it prompted me to upgrade the rules for better functionality with Outlook 2002. Since then, my rule does not work. I can get different rules to work, but this rule will no longer move a copy of my messages I send to the Sent Items folder on the server.

I have deleted and recreated this rule multiple times, and I have also tried different rules to make sure that the rules mechanism works (which it does, as I can have it move a copy of all new messages to my local Inbox (within the .PST) as they arrive within the IMAP Inbox.

Anybody have any ideas. My version of Outlook is mentioned above (Build 10.2930.2625), running on Windows 2000 Pro, Service Pack 2. I have also applied the first update MS released for Outlook 2002.


I have a user with the following problem:
Many times, when she open up a Word document, the document will open and be displayed on the screen. Word will then pause for about 45 seconds before allowing one to continue. This happens on even small documents.
She was using Office 2000 with all current patches. I upgraded her PC to Office XP (with service pack 2 and patches) but the problem persists.
She is running Windows 2000.
Any ideas on what would cause and/or fix this?
Thanks a bunch,

I decided to download the express installer as a
preliminary to the suggested XP Service Pack 2 download. Bummer - my
office machine is running XP in Spanish (I live in Spain) & having
completed the download of the installer all I got was an eror message
saying it couldn't be installed as my version of XP is in another
language. Help!

With thanks in advance,

Page 1 of 4.
Results 1...20 of 76