Word 2007 does not open/save to Novell mapped network drive on Vis

[Warren]

I'm currently running a test PC in our office with Windows Vista Business,
Microsoft Office 2007 Enterprise Edition and Novell Client Technology Preview
release for Windows Vista.

When I've tried to open any Word document from a Novell mapped network drive
(such as my H:/drive after I've logged in using the Novell client) I keep
getting "access denied. Contact your administrator." This happens in other
Office 2007 applications as well.

I've tried changing the trusted locations and added the network H:/drive
there but still nothing.

Other applications work perfectly saving to the mapped drive on Vista
(OpenOffice, Firefox, Autocad) just not Office. Is there any reason for this?

 

[jfisk]

Has anyone figured out a fix for this yet? Files will not open directly off
the drives but will open after they are copied to the local drive. I have
noticed that it appears to spring up the message on the "downloading file"
portion of the loading.

 

[Terry Farrell]

What AV are you using?

Terry

Has anyone figured out a fix for this yet? Files will not open directly
off
the drives but will open after they are copied to the local drive. I have
noticed that it appears to spring up the message on the "downloading file"
portion of the loading.

 

[jfisk]

I have Symantec Corporate Edition 10.2, I don't think this product has a
Office plug-in (unless it is hiding somewhere).

 

[Terry Farrell]

No, it's not that causing the problem. I suggest going to the Novell support
site where other Novell users may be experiencing the same problem.

Terry

 

[jfisk]

Been there... Just wanted to check with the Microsoft side too see if anybody
had anything new on the issue.

 

[Warren]

I'm using Sophos Anti-Virus 6.5, which has been certified to run on Windows
Vista without any problems. As a test I also completely uninstalled Sophos
and tried to open any mapped drive files again - still nothing.

Testing Office 2007 Enterprise Edition on a Windows XP build I have seemed
to open fine from Novell mapped network drives. So it's either an issue with
Vista or the Novell client, or the way Office 2007 interacts with Vista.

 

[Terry Farrell]

Find the Winword.exe file, right-click and choose Run as Administrator. Does
it now work?

Terry

 

[jfisk]

For me that option is grayed out on winword.exe. One thing I have noticed if
the file is read only it will open the file fine. It appears that Word must
be attempting to write something to the file upon opening it that causes the
error.

 

[Terry Farrell]

What Word does on opening is write a temp file in the same location as the
document. This makes me think that there is a security setting stopping the
user writing in that location.

If you cannot use the run as admin option, this too seems to be the way that
the OS has been set up on your PC. Try logging in to your PC as
Administrator (not as a user with Admin rights but actually as
Administrator) and test again.

Terry

 

[Warren]

Terry,

I'm actually running the tests as Administrator, and getting exactly the
same bad results. I knew that there'd be a temporary file being opened
within the same Novell mapped network drive, but for some reason it's just
thrown out straight away.

I've narrowed things down a bit:

* Running Office 2007 on a Windows XP system with Novell Client 4.91 SP3 and
accessing the same files on the same Novell mapped drive works - perfectly.

* Running other applications on Windows Vista with Novell Client Technology
Preview for Vista allows me to read/write to the files on the same Novell
mapped drive (I tried OpenOffice, Autocad, Photoshop CS2 etc)

I have a feeling it's more the way Office 2007 and Vista interact with each
other that tends to lock down the security features, maybe?

 

[Terry Farrell]

It could well be so as Office 2007 integrates tightly with Vista. You can
see this if you look at the File Open/Save dialogs when using XP and then
when using Vista. But I don't think I can help any further with this as it
is a bug that it now beyond my knowledge. I guess you are going to have to
raise an event with Microsoft Support.

Terry