KB157069 - "Can't Access This Folder. Path Is Too Long" Error

Article ID: 157069

Article Last Modified on 11/1/2006

Microsoft Windows NT Server 4.0, Terminal Server Edition
Microsoft Windows NT Workstation 4.0 Developer Edition
Microsoft Windows NT Server 4.0 Standard Edition
Microsoft BackOffice Small Business Server 4.0
Microsoft BackOffice Small Business Server 4.0a
Microsoft BackOffice Small Business Server 4.5

This article was previously published under Q157069

SYMPTOMS

When you log on to a computer running Windows NT Workstation or Server, you get a dialog box with the following error message or you get a blank desktop:

Can't access this folder. The path is too long.

RESOLUTION

Log on as the local Administrator and verify that either the user or a group (of which the user is a member) has at least read access to the root of the system drive. To accomplish this if the desktop is blank, follow the procedure below:

Start Task Manager by pressing CTRL+ALT+DELETE.
On the File menu, click New Task.
In the Run dialog box, start Explorer.exe or Winfile.exe.
View the security permissions of the system drive.

If the user or group does not have this access, add it to the directory permissions for the user or group. Do not select the Apply To Subdirectories check box.

For additional information, please see the following article in the Microsoft Knowledge Base:

ARTICLE-ID: 148437
TITLE : Default NTFS Permissions in Windows NT

MORE INFORMATION

If a user logs on to a workstation (either locally or to a domain) and is not listed by group or name to have any access permissions to the root directory where the system files reside, the following problems can occur:

If the user logs on to the domain from the workstation or member server, he or she will get a dialog box with the following error, followed by a blank desktop:
Can't access this folder. The path is too long.
However, a profile is created in the %SystemRoot%\Profiles directory for that user.
If the workstation or server is not a member of a domain, or if the user decides to log on locally, the error message may or may not be displayed, but a blank desktop with the profile created in the profiles directory will occur.

The scenarios described above have only been confirmed with Windows NT 4.0 clients. The domain that a user logs on to can be either a Windows NT 3.51 or a Windows NT 4.0 domain with the same results. This is one type of scenario that can occur if directory permissions are not set up properly on a client.

Additional query words: path profiles

Keywords: kbprb KB157069