100% cpu utilization during save as

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

itsupport@jdsweid.com - 18 Mar 2008 21:59 GMT

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

Reply to this Message

Terry Farrell - 19 Mar 2008 09:55 GMT

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?

Signature

Terry Farrell - MSWord MVP

> 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
[quoted text clipped - 8 lines]
>
> --Cam

Reply to this Message

itsupport@jdsweid.com - 25 Mar 2008 18:07 GMT

> If this is only to a network location, it suggests a problem on the network
> side - or permissions.
[quoted text clipped - 24 lines]
>
> - 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).

Reply to this Message

Terry Farrell - 25 Mar 2008 18:34 GMT

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).

Reply to this Message

Bob - 25 Mar 2008 19:20 GMT

Might sfc /scannow fix the problem?

> So it is possibly a profile corruption problem. In my experience, these
> can be extremely difficult to diagnose - often unsuccessfully: creating
[quoted text clipped - 10 lines]
> happening) by re-creating the user profiles for the users affected by
> this (including myself).

Reply to this Message

Rate this thread: