Excel 2007 users can not open files if anyone else on the network has them open.
We are starting to upgrade some of our users to Office 2007 and I have run into an extremely frustrating issue. If anyone on the network has an excel file open none of my excel 2007 users can access it. Where you would typically get a prompt to open the file read only because it is locked for editing by another user they are getting "t::\whatever the path is.xls cannot be found. Check your spelling or try a different path" I have tried the fixes on the Microsoft's website and nothing is working. This is across the board, every 2007 install we have. It doesn't matter if I have both 2003 and 2007 installed on the PC or just 2007, if it is a .xls or a .xlsx. It happens on the OEM installs and the VLA installs and whether you open it from within excel or by clicking the file. The code 701743 on the error window is different from the other postings. I read that anti-virus software and cause this behavior but I unloaded officescan on the PC and the issue persists.
We are using Novell servers. I just discovered that if I map a drive through windows networking to a PC with the file saved and open on the local drive I get the normal locked for editing window. So, it would appear, at least to me, it is a conflict with Novell and Office 2007. I still need the issue resolved but thought this might help anyone looking for an answer.
We are using Novell servers. I just discovered that if I map a drive through windows networking to a PC with the file saved and open on the local drive I get the normal locked for editing window. So, it would appear, at least to me, it is a conflict with Novell and Office 2007. I still need the issue resolved but thought this might help anyone looking for an answer.
701743
Ray
If you click within the list of items FIRST, it will allow you to press a letter and will jump to that letter.
NEVERMIND, wrong question.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
It was the Novell Client. We have not upgraded in some time and bringing it up to Novell Client 4.91 sp5 did the trick. Can't believe I missed that.