WSS 2 trouble browsing network place

I am posting this question here as according to a Sharepoint specialist this
may be a WebDav issue.

All of the below is referring to Sharepoint Services 2.0

I have a single large document library which works great. It is subdivided
into folders and some of the folders have a large number of documents
(thousands) in them.

I have added the library to my network places,
\\server\sites\sitename\doclib. This allows me to get to the library without
HTTP. When I browse everything is fine EXCEPT when I try some of the larger
directories.

"I get "\\server\sites\sitename\doclib\folder is not accessible. You might
not have permission to use the network resource. Contact the administrator
of this server to find out if you have access permissions. A device attached
to the system is not functioning".

It seems it may be a timeout issue?

Any ideas?
Bob

Hello,

Thank you for using newsgroup!

From your post, I was unable to understand your situation clearly. I'd like
to confirm the following information with you:
1. Is "\\server\sites\sitename\doclib" a shared folder path?
2. Could you clarify that how you create this shared resource?

I have the following suggestions to narrow down the problem:
1. Check the ACL on the shared "doclib\folder", to make sure that you have
the permissions to access.
2. Logon to server, add the library to my network places, to check if this
problem occurs.

Please update me with the result, I look forward to your reply.

Mike Luo

Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security

================================================== ===
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.

1. Is "\\server\sites\sitename\doclib" a shared folder path?

It is actually a doclibrary inside of Sharepoint 2003. Note that I can
browse "\\server\sites\sitename\doclib" and I can get into the majority of
the folders but not all: i.e. I can get into
"\\server\sites\sitename\doclib\joe" but "\\server\sites\sitename\doclib\jim"
does not work.

Also note that if I go via "http://server/sites/sitename/doclibrary/folder"
it works fine so the security is probably not the issue.

2. Could you clarify that how you create this shared resource?
I simply added it to network places

2. Logon to server, add the library to my network places, to check if this
problem occurs.
I did try this. I had to start the "webclient" service. I received the
same error

As for checking the ACLs, I am not sure about how to go about that given the
share is actually in Sharepoint 2003. The security, through sharepoint, is
correct as can be witnessed by the ability to browse other folders on the
doclibrary without an issue.

My guess is it is timing out due to the large number of docs under that
particular folder.

Thanks,
Bob



"Mike Luo [MSFT]" wrote:

> Hello,
>
> Thank you for using newsgroup!
>
> From your post, I was unable to understand your situation clearly. I'd like
> to confirm the following information with you:
> 1. Is "\\server\sites\sitename\doclib" a shared folder path?
> 2. Could you clarify that how you create this shared resource?
>
> I have the following suggestions to narrow down the problem:
> 1. Check the ACL on the shared "doclib\folder", to make sure that you have
> the permissions to access.
> 2. Logon to server, add the library to my network places, to check if this
> problem occurs.
>
> Please update me with the result, I look forward to your reply.
>
> Mike Luo
>
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
>
> ================================================== ===
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>

I ran a test from the local server and the svchost process used a good
portion of the CPU (as expected when browsing a large network) for about 210
seconds at which time it threw the error.

Seems to me it is a timeout issue. If so, how/where do I increase the
timeout? IIS? Client? etc.

Thanks,
Bob

"Mike Luo [MSFT]" wrote:

> Hello,
>
> Thank you for using newsgroup!
>
> From your post, I was unable to understand your situation clearly. I'd like
> to confirm the following information with you:
> 1. Is "\\server\sites\sitename\doclib" a shared folder path?
> 2. Could you clarify that how you create this shared resource?
>
> I have the following suggestions to narrow down the problem:
> 1. Check the ACL on the shared "doclib\folder", to make sure that you have
> the permissions to access.
> 2. Logon to server, add the library to my network places, to check if this
> problem occurs.
>
> Please update me with the result, I look forward to your reply.
>
> Mike Luo
>
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
>
> ================================================== ===
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>

Thank you for the update!

This is a quick note to let you know that I am performing research on this
issue and will get back to you as soon as possible. I appreciate your
patience.

Mike Luo

Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security

================================================== ===
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.

Hello Bob,

Based on my knowledge, WSS requires IIS to handle those requests from the
client, we can set the time out settings on IIS to control WSS time out.

If you increase the time out range, this problem will persist. I have the
following suggestions:

1. Use WSS Administrator to access the docment library folder, to check if
the problem occurs. The WSS Administrator always has permission to access
the docment library folder. If using Administrator to access, the problem
still appears, we can ensure that the problem isn't related to permissions.
2. Create a new folder on the WSS site, move those files into this folder,
to check if the problem occurs.

Thanks & Regards,

Mike Luo

Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security

================================================== ===
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.

Which timeout values should I work with in IIS?

Thanks,
Bob

"Mike Luo [MSFT]" wrote:

> Hello Bob,
>
> Based on my knowledge, WSS requires IIS to handle those requests from the
> client, we can set the time out settings on IIS to control WSS time out.
>
> If you increase the time out range, this problem will persist. I have the
> following suggestions:
>
> 1. Use WSS Administrator to access the docment library folder, to check if
> the problem occurs. The WSS Administrator always has permission to access
> the docment library folder. If using Administrator to access, the problem
> still appears, we can ensure that the problem isn't related to permissions.
> 2. Create a new folder on the WSS site, move those files into this folder,
> to check if the problem occurs.
>
> Thanks & Regards,
>
> Mike Luo
>
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
>
> ================================================== ===
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>

Hello Bob,

The value rely on the number of file and folder under the document library.
By defualt, the timeout is set to 120 seconds, you may increase this to 300
or higher, to see if the problem persist. To modify the timeout value,
follow this steps:
1. Open IIS console.
2. Expand Server Name, Right-click Web Sites and select properties.
3. Set Connection Timeout to 300 or higher.
4. Right-click Server Name, select All Tasks->Restart IIS.

Thanks & Regards,

Mike Luo

Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security

================================================== ===
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.

I increased up to 800, reset IIS and still experienced the issue. Is it
possibel there are other limits I am exceeding? I.e. the many settings in
the app pool?

Thanks,
Bob

"Mike Luo [MSFT]" wrote:

> Hello Bob,
>
> The value rely on the number of file and folder under the document library.
> By defualt, the timeout is set to 120 seconds, you may increase this to 300
> or higher, to see if the problem persist. To modify the timeout value,
> follow this steps:
> 1. Open IIS console.
> 2. Expand Server Name, Right-click Web Sites and select properties.
> 3. Set Connection Timeout to 300 or higher.
> 4. Right-click Server Name, select All Tasks->Restart IIS.
>
> Thanks & Regards,
>
> Mike Luo
>
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
>
> ================================================== ===
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>

Not sure what to make of this.
http://www.tek-tips.com/viewthread.c...1311845&page=6

I am gettign VERY concerned however, as I have found I can not view the
document library folders in the explorer view in IE either. This effectively
means I can not move any documents out of the library.

Bob

"Mike Luo [MSFT]" wrote:

> Hello Bob,
>
> The value rely on the number of file and folder under the document library.
> By defualt, the timeout is set to 120 seconds, you may increase this to 300
> or higher, to see if the problem persist. To modify the timeout value,
> follow this steps:
> 1. Open IIS console.
> 2. Expand Server Name, Right-click Web Sites and select properties.
> 3. Set Connection Timeout to 300 or higher.
> 4. Right-click Server Name, select All Tasks->Restart IIS.
>
> Thanks & Regards,
>
> Mike Luo
>
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
>
> ================================================== ===
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>