You are viewing limited content. For full access, please sign in.

Question

Question

Cannot login to new web access repository

asked on June 22, 2018

Hey everyone, 

I am trying to add a repository to web access and everything connects just fine and it's set up exactly as I can tell as another repository but when I try to login, it says user name and password is incorrect.  When I look up the error logs, it says "Error reading configuration file...because it's being used by another process".  I'm not quite sure what to make of this.  Has anybody has anything similar?

 

Thanks


Drew

0 0

Answer

SELECTED ANSWER
replied on June 26, 2018

Figured out what it was.  Someone had set the "everyone" group to "deny". ugh...

0 0

Replies

replied on June 22, 2018

So, you went to the configuration page and added a second repository to where you already had one?  Can you still log in to the first?  I don't know what process would be holding an unshared write lock on the config file.  Of course Web Access needs to write to it but that lock is short-lived.  Sometimes anti-virus will do something like that.  If the problem hasn't resolved itself, I would suggest (in escalating order of disruption) recycling the Web Access app pool, resetting IIS or rebooting the machine.

0 0
replied on June 22, 2018

Hey Brian,

Yes, I went to the configuration page, added the new repository, says it connects to it just fine and everything.  When I select the new repository from the drop down and enter in my credentials, it says invalid user name or password.  

Another interesting piece is that I can access the new repository (or admin console) from the desktop client just fine but when I try to access it directly from the server that it is stored on, it gives me the invalid username or password too.  

0 0
replied on June 25, 2018

What kind of credentials are you trying to use?  Windows account, repository user, LFDS account, LDAP account?

0 0
replied on June 26, 2018

Windows account

0 0
SELECTED ANSWER
replied on June 26, 2018

Figured out what it was.  Someone had set the "everyone" group to "deny". ugh...

0 0
replied on June 26, 2018

With integrated Windows authentication, or you type in domain\username + password?  If the former, is Kerberos configured?

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.