unknown error trying to lock file

[David Lozzi]

Howdy,

I have Vista Ultimate, Office 2007 and using WSS 3.0. When I open a Word
doc, not docx, Word gives me the button to click to Edit Document. When I
click it I get the following error:

unknown error trying to lock file

So I have to save the document locally then make changes then upload it.
Very agravating. Anyone have a clue?

Thanks!!

--
David Lozzi
Delphi Technology Solutions
Blog: www.lozzi.net

[Chad Brouwer]

I am having the same problem. In my case it seems to have something to do
with alternate access mappings because if I use the origional url (the host
server's name) to get to the site everything works fine but when I use the
url that I set up in alternate access mapping I get the same error that you
are getting. Hopefully someone else can shed some more light on this.

[dlo...@delphi-ts.com]

So I think I may have fixed it. I added an exception to my Windows
Firewall, TCP port 445. So far so good!

On Nov 28 2007, 1:44 pm, David Lozzi <dlozzi(remove-this)@delphi-

[Chad Brouwer]

Thanks for the update. Just in case others are reading this I wanted to note
that my firewall is off and I am still having the problem. It sounds like we
maybe just have slightly different issues here.

Chad

[Lieven]

This is a really annoying bug which is bothering me for weeks. I hope they
fix this in Vista SP1!

[Mike Walsh]

Could you please give us a description of which SharePoint product you
have and when this file locking is affecting you.

(This newsgroup is for the SharePoint product called "Windows SharePoint
Services")

Mike Walsh
WSS FAQ www.wssfaq.com / wss.collutions.com
no private e-mail questions please

[David Lozzi]

Opening TCP 445 appeared to work for that moment. Since it's broken again. I
notice that if I'm VPN'd into a customer site, then disconnect (more often
with Cisco VPN Client) and I jump on our SharePoint server I can edit
documents fine. After I close out and come back even 10 minutes later I
cannot again.

It definitely is something with Vista networking "features". Discouraging to
see that even turning off the firewall we still cannot access these files
correctly. What other issues are we having with other apps that we don't even
know about?! Anyway...

I'm using Windows SharePoint Services 3.0 SP1 on a SBS 2003 SP1 w/ Win2k3
SP2 installed next to WSS2. I'm running Windows Vista Ultimate 32-bit, Office
2007 SP1.

Thanks!!
--
David Lozzi
Delphi Technology Solutions
Blog: www.lozzi.net

[David Lozzi]

Sorry if this is a duplicate post, i didn't see a confirmation....

Opening TCP 445 appeared to work for that moment. Since it's broken again. I
notice that if I'm VPN'd into a customer site, then disconnect (more often
with Cisco VPN Client) and I jump on our SharePoint server I can edit
documents fine. After I close out and come back even 10 minutes later I
cannot again.

It definitely is something with Vista networking "features". Discouraging to
see that even turning off the firewall we still cannot access these files
correctly. What other issues are we having with other apps that we don't even
know about?! Anyway...

I'm using Windows SharePoint Services 3.0 SP1 on a SBS 2003 SP1 w/ Win2k3
SP2 installed next to WSS2. I'm running Windows Vista Ultimate 32-bit, Office
2007 SP1.

Thanks!!

--
David Lozzi
Delphi Technology Solutions
Blog: www.lozzi.net

[David Lozzi]

A little more discovery on the issue at hand.

I was at a customer site today, and I was able to access all documents I
needed to, i could edit them and save them back to WSS. I have since come
home and now I cannot, and tihs is a different network from my office. I'm
convinced it's a networking or tcp protocol issue.

Any ideas yet Microsoft?

--
David Lozzi
Delphi Technology Solutions
Blog: www.lozzi.net

[David Lozzi]

In further investigation I have found that it works fine internally. We use
the public URL as our default home page, even when we're connected to the
internal network. When i switched to use the internal DNS name, i can edit
documents fine.

Is ISA blocking something? But why would it work at some other locations and
VPNs and not others. Very odd.

[Pete]

David, this information was very helpful. We implemented this with our
Juniper Firewall and it is working on both a MOSS and WSS implemenation. We
also had a recent client that experienced the same issue with their ISA
firwall. After reading this today, I contacted them and told them to open up
that port....vioala...it is working for them as well. The intricacies with
Vista and WSS 3.0 have been strange to say the least. I am glad we are all
here for a common reason.

Pete

[Pete]

For everyone's knowledge, I just found out that this same problem is visible
in both XP and Vista. We have both enterprise implementations of WSS 3.0 and
MOSS and both are fixed now that that port has been opened.

[Deraeve@discussions.microsoft.com Mark Deraeve]

Hi,

I don't know of this is the same error I'm getting. It's very strange. When
I open a file larger then +- 200 KB I see e refresh but nithing happens, on
other browers I get a page not found error. Smaller files are opened perfect.
It has nothing to do with the setting in WSS of document size and nothing to
do woth the timeout setting in IIS.
In the logfile, when I click a file larger then 200 KB I get these messages:
02/25/2008 11:08:37.20 w3wp.exe (0x1D1C)
0x1988 Windows SharePoint Services General
8k44 Medium lockFile: try lock
file=C:\WINDOWS\TEMP\WebTempDir\1D1C19886C00441AA4F5AD808F63B51F_1.tmp
mode="rb"=0x0 shareReally wait
02/25/2008 11:08:37.20 w3wp.exe (0x1D1C)
0x1988 Windows SharePoint Services General
8k45 Medium lockFile: got lock
file=C:\WINDOWS\TEMP\WebTempDir\1D1C19886C00441AA4F5AD808F63B51F_1.tmp

Is this the same problem, do I have to request opening port 445?

[Pete]

That error looks suspiciously similar. If you are accessing this file
externally, I would bet that port would need to be opened. Your firewall
folks could always check to see if there are denials from that IP address on
that port and protocol. I am also not certain what version of office you are
using, but our testing was only with Office 2007, Excel specifically, and XP
or Vista for the OS. Hope this helps.

Pete

[David Lozzi]

I just found this thread again. This is still an issue for me. I am now on a
WinXP Office 2003 box and it works fine. my Vista Office 2007 box still
errors, and that port is open. Any hope Vista SP1 helps?

--
David Lozzi
Delphi Technology Solutions

www.delphi-ts.com

"Pete" <Pe...@discussions.microsoft.com> wrote in message
news:ED02D1A6-8BF5-4006...@microsoft.com...

[Pete]

David, the only way to really verify is to do a Telnet or Third party port
utility. You can try going to a command prompt and typing - telnet "FQDN" 445
then hit enter. If you come up with anything but a blank black screen,
the port is being blocked somewhere. We went to a company and they told us
they opened it, but after the telnet test, we verified it was not.

E.G. " telnet MOSS.Server.com 445 "

Pete

[David Lozzi]

OK, I have 445 open through ISA. Before opening it the telnet would time
out, now it instantly responds with connect failed. The ISA logs shows
several Initiated Connection and Closed Connection entries for port 445. No
errors. What is handling 445, should something be running?

Thanks,
David Lozzi

"Pete" <Pe...@discussions.microsoft.com> wrote in message

news:D16AF68B-185F-4CFF...@microsoft.com...

[Deraeve@discussions.microsoft.com Mark Deraeve]

Hi,

I found the problem and the solution to the problem, it had nothing to do
with the clients, but rather the server.
I wrote the solution on my blog:
http://www.dailycode.net/blog/post/3GB-option-in-the-Boot.ini-(cannot-open-large-files).aspx