Save as - Initializing Folders

[Birdman]

Hi
This is a first post here, and I searched and found many people with the a similar issue going back 2007



My issue is a little different as the file Im using is on a mapped drive - moswt solutions say to disconnect the mapped drives. in my case I cannot.

This is now happened on 2 different machines, in 2 buildings over 2 weeks with 2 different users and different files and locations.

Standard PC Image:
XP Fully Patched
Office 2007 Fully Patched
Drives mapped by logon script.
All drives Active and available.

This is where mine differs a little.
If I open a file off one of the Mapped drives (T:\subfolder\subfolder\ file size 700kb) in Word then edit the file then go FILE - SAVE AS... the save as window opens as per normal.

But when I go to change the drive with the drop down menu, like many others - this is where it goes pear shaped. I get the Initializing Folders message and it takes ages. You cant cancel it, you cant stop it without task manager.

So I decided to leave it and waited 10 mins it comes back to life and in the drop down menu there is no T Drive - remembering this is where the file was opened from..
All other drives show up. In the background I go to My Computer, all mapped drives are there and available including T drive - and no Red X.

There are 15 other users who can access this file, edit it, and save it and save as without a problem.

So far I've
Tested all mapped drives work fine in My Computer.
Tested all mapped drives work fine in My Computer while doing the file save as and its initializing..

Deleted the mapped drive, rebooted so it remaps drives and retried = fail
Deleted the mapped drive, shut down (powered off) and restarted machine so it remaps drives and retried = fail
Delete the mapped drive and manually remapped it and retried = fail.

Just thought - I haven't tried another user login on the machines. surely not.

Apart from that, I'm at a loss.

I've googled and only got about 50 billion hits to the issue, not many suitable solutions though - 99% say to remove the mapped drives, which I cannot do in this corp environment.

Any other suggestions?
Thanks.

[macropod]

Hi Birdman,

Two possibilities spring to mind:
1. A hardware fault. If everything works fine for you when you use a different PC, that's the most likely cause. This is especially so if it doesn't work for other users when they use your PC.
2. A user profile fault. If it still doesn't work for you when you use a different PC, that's the most likely cause. This is especially so if everything works fine for other users when they use your PC.

[Birdman]

Thanks for the reply.

Originally Posted by macropod

Hi Birdman,

Two possibilities spring to mind:
1. A hardware fault.
If everything works fine for you when you use a different PC, that's the most likely cause. This is especially so if it doesn't work for other users when they use your PC.

I'm thinking not so much a hardware fault, since it happens on 1 laptop, 1 workstation of different makes in 2 different buildings (although same subnet).
I'll try another user account on each machine first.

2. A user profile fault.
If it still doesn't work for you when you use a different PC, that's the most likely cause. This is especially so if everything works fine for other users when they use your PC.

I am leaning towards this - or corrupt office installation.


My head is struggling to get around the Missing T Drive from the drop down menu, with the file open from that location. Yea, know you can open files, and then disconnect the drive and continue working, but...

x


Thanks again

[macropod]

Originally Posted by Birdman

I'm thinking not so much a hardware fault, since it happens on 1 laptop, 1 workstation of different makes in 2 different buildings (although same subnet).

A hardware fault on the server could easily account for this, as might a software fault there.