Knowledgebase: Server Administration
Can't access the repository share
Posted by Mont Rothstein on 25 October 2010 11:36 PM

How to test and troubleshoot access to the repository share:

  1. Enter the UNC path to the share in Windows Explorer on the server from which it is shared. Ex: \\servername\Repository. If this doesn't work check:
    1. Share settings - the repository owner needs Full Control
    2. Directory settings - If the Foray Technologies directory has not been created then the repository owner needs Full Control of the shared directory. If the Foray Technologies directory has been created then the repository owner needs to have full control and be the owner. From a security standpoint no other objects should have access.
    3. Server name - double check the spelling and that it can be accessed from the command line (try ping)
    4. Repository owner account - test the username and password by trying to login to the server using this account. The account may need to have interactive logon temporarily enabled if it is disabled in order to perform this test.
  2. Enter the UNC path to the share in Windows Explorer on a client workstation. Ex: \\servername\Repository. It this doesn't work check:
    1. Server name - double check the spelling and that it can be accessed from the command line (try ping)
  3. Run Configure Adams on the server and test the repository access. If this doesn't work check:
    1. Server name - double check the spelling and that it can be accessed from the command line (try ping)
    2. Share name
    3. Repository owner account - double check the username and password
  4. Run Configure Adams on a client workstation and test the repository access. If 1-3 work but this doesn't then it may be one of the following group policies.
    1. Impersonate a client after authentication - Without this privilege impersonation of the repository owner account is prevented.
      1. Test locally
        1. Administrative Tools->Local Security Policy
        2. Security Settings->Local Policies->User Rights Assignment->Impersonate a client after authentication
        3. Right click->Properties
        4. Add the repository owner account to the list of accounts
        5. Re-test. If access now works then this can be fixed at the domain level so that it doesn't have to be overridden on each workstation
      2. Fix globally
        1. On the domain controller: Administrative Tools->Group Policy Management
        2. Group Policy Management->Forest->Domains-><DOMAIN NAME>->Group Policy Objects->Default Domain Controllers Policy
        3. Settings tab
        4. Right-click anywhere in tab details->Edit ... this opens the Group Policy Management Editor
        5. Default Domain Controllers Policy->Computer Configuration->Policies->Windows Settings->Security Settings->Local Policies->User Rights Assignment->Impersonate a client after authentication
        6. Right-click->Properties
        7. This policy will have the "Define these policy settings" checked
        8. Add the repository owner account
        9. Users will need to log out and back in for this policy to be pulled down from the domain controller.
    2. Access this computer from the network - Without this privilege the repository owner account will not be able to access the network share from another machine.
      1. Test locally - Modify the local policy on the server hosting the repository share.
        1. Administrative Tools->Local Security Policy
        2. Security Settings->Local Policies->User Rights Assignment->Access this computer from the network
        3. Right click->Properties
        4. Add the repository owner account to the list of accounts
        5. Re-test. If access now works then it must be fixed at the domain level so that it the privilege isn't removed when the GPO is re-applied to the server.
      2. Fix globally
        1. Set the Access this computer from the network policy so that the repository owner account has this privilege on the server hosting the repository share.
        2. Reboot the server to test that access is still allowed after then reboot.
  5. Start AdamsWeb and attempt to access the login page
    1. In some environments everything except AdamsWeb will work.  Configure Adams and Digital Workplace will work fine but AdamsWeb will throw a LogonFailedException.  In the case the issue may be group policy blocking AdamsWeb from impersonating the Repository Owner account.  Try the following: 
    2. Remove the group policy "Deny Local Logon" for the repository owner account. AdamsWeb or anything that requires local access to a secure directory needs this privilege.
    3. Explicitly add the Repository Owner account to the "Allow log on locally" privilege.  This can be either directly or via a group.

 


Comments (0)