Microsoft Knowledge Base Email Alertz

(842695) - Describes a problem where you receive an error message when you use the Active Directory Users and Computers snap-in to open the Dial-in tab. Describes symptom details, the cause of the issue, and how to resolve the issue.

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Article ID: 842695 - Last Review: December 3, 2007 - Revision: 1.2

You may receive an error message when you try to open the Dial-in tab in Small Business Server 2003

Important This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986  (http://kbalertz.com/Feedback.aspx?kbNumber=256986/ ) Description of the Microsoft Windows Registry

SYMPTOMS

When you use the Active Directory Users and Computers snap-in in Microsoft Windows Small Business Server (SBS) 2003 and try to open the Dial-in tab in the properties of a user object, the Dial-in tab may not open. Additionally, you may receive an error message that is similar to the following error message:
Dial-in page error.
Could not load the Dial-in profile for this user because: Access is denied.
If the Dial-in tab does open, you may receive an error message that is similar to the following:
Dial-in page initialization failed.

CAUSE

This issue may occur if the Local Service account does not have the correct registry permissions.

RESOLUTION

Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.To resolve this issue, follow these steps:
  1. Click Start, click Run, type regedt32, and then click OK.
  2. Locate and click the following registry subkey:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurePipeServers\winreg
  3. Right-click winreg, and then click Permissions.
  4. Click Add, and then click Advanced.
  5. Click Find Now.
  6. In the Search results box, click Local Service, and then click OK.
  7. Under the Allow column, click to select the Read check box.
  8. Click OK.
  9. Make sure that read permissions for the Local Service account have been applied to the following registry subkey:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurePipeServers\winreg\AllowedPaths
    If read permissions for the Local Service account have been applied, go to step 10. If read permissions for the Local Service account have not been applied, give read permissions to the Local Service account for the
    AllowedPaths
    subkey. To do this, follow these steps:
    1. Locate and click the following registry subkey:
      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurePipeServers\winreg\AllowedPaths
    2. Right-click AllowedPaths, and then click Permissions.
    3. Click Add, and then click Advanced.
    4. Click Find Now.
    5. In the Search results box, click Local Service, and then click OK.
    6. Under the Allow column, click to select the Read check box.
    7. Click OK.
  10. Quit Registry Editor.

APPLIES TO
  • Microsoft Windows Small Business Server 2003 Standard Edition
  • Microsoft Windows Small Business Server 2003 Premium Edition
Keywords: 
kbprb KB842695
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate