100% cpu utilization during save as

[itsupport]

I'm wondering if anyone here can help me with this. When I'm typing a
filename in the Save As dialog box in Excel 2003, excel.exe shoots up
to 100% CPU utilization and it takes a second or two for the letters
I've typed to show up. This only happens when I'm trying to save to a
network location. The same issue comes up in Word 2003 and Powerpoint
2003, but not in any other windows applications.

Any ideas?

Thanks

--Cam

 

[Terry Farrell]

If this is only to a network location, it suggests a problem on the network
side - or permissions.

But are you using mapped drives for this? If so, try deleting the mapped
drives and then test SaveAs and navigate to the network drive manually: does
it save without the problems?

 

[itsupport]

If this is only to a network location, it suggests a problem on the network
side - or permissions.

But are you using mapped drives for this? If so, try deleting the mapped
drives and then test SaveAs and navigate to the network drive manually: does
it save without the problems?

--
Terry Farrell - MSWord MVP







- Show quoted text -

Hi Terry, thanks for your response

Unfortunately the problem still happens no matter if its a mapped
drive or if I navigate to the server manually. This was even
happening using a domain admin account, so I don't think it's a user
rights issue. I managed to fix it (or at least stop this from
happening) by re-creating the user profiles for the users affected by
this (including myself).

 

[Terry Farrell]

So it is possibly a profile corruption problem. In my experience, these can
be extremely difficult to diagnose - often unsuccessfully: creating new
profiles probably the best solution.

Terry

Hi Terry, thanks for your response

Unfortunately the problem still happens no matter if its a mapped
drive or if I navigate to the server manually. This was even
happening using a domain admin account, so I don't think it's a user
rights issue. I managed to fix it (or at least stop this from
happening) by re-creating the user profiles for the users affected by
this (including myself).