Ann, I had a similar problem. See techteacher's response to me to the
subject "Saving Excel/Word files to server after updates" on 2/21/05. The
culprit was indeed the KB885250. If you hear back from Microsoft on a fix to
this update, please advise.
"Ann" wrote:
> I have worked many hours with a tech at Microsoft the problem is not fixed
> yet. The tech was submitting it to research and would email a fix to me as
> soon as they have fixed it. The Update was KB885250. If you uninstall just
> that update you will not have the problem with the "save as" feature in the
> Microsoft Office Products.
>
> "liashke" wrote:
>
> > Not solved, exactly. I finally found where to make the hotfixes reappear in
> > Add/Remove Programs (via another post here, thanks to that poster!) and I
> > deleted all of the updates. That fixed it and when I redownloaded the
> > updates it seemed to work fine. I had a later problem with files being saved
> > across the network to my computer, though, which may or may not have been
> > related to this issue. Remapping the network fixed that one. I still don't
> > think everything's working quite right, but at least it's working.
> >
> > "james" wrote:
> >
> > > Did you get this problem solved? I'm having a similar issue when trying to
> > > save new files in Word or Excel to the server. Existing filenames can be
> > > saved fine. Happened right after these security updates were automatically
> > > installed.
> > >
> > > "liashke" wrote:
> > >
> > > > I downloaded the February critical updates on all of our office computers the
> > > > same morning, 2/9/2005. On every computer but one, all is well and I haven't
> > > > noticed any trouble. But on that one machine, when I go into Network Places
> > > > to connect to another computer in the workgroup, it doesn't recognize any of
> > > > the paths. If I click on "View Workgroup Computers", it just gives an error
> > > > beep without changing the screen.
> > > >
> > > > --the LAN appears to be working fine
> > > > --if I use one of the OK computers, I can still connect to the messed-up one
> > > > --re-establishing the network connection via the network setup wizard
> > > > doesn't change anything
> > > > --turning the firewall on/off to redo the connections doesn't change anything
> > > > --I've removed all of the Windows internet/network programs and reinstalled
> > > > them
> > > > --system restore isn't working with either checkpoint or software
> > > > distribution points, and I haven't done a manual system restore point for
> > > > months (because with the others in there it didn't seem necessary)
> > > > --I only found one of the updates in the Add/Remove Programs list (the .NET
> > > > Framework one, KB886903) and uninstalling it didn't change anything
> > > >
> > > > My best guess is that somehow in this particular update, a file got
> > > > confused. But I have no idea what else to try short of wiping the system and
> > > > reinstalling WindowsXP.
|