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

Question

Question

Permission Denied registering server in Admin Console

asked on February 2, 2015

Is there some different protocol for being able to see the server between the Client and Admin Console?  

We have a user that has both the Client and the Administration Console on their workstation.  They can attach the repository in the Client using the servername or the IP address no problem.  However when we try to register the server in the Administration Console by name or IP address is gives 9013 Permission Denied.  Not sure what the difference is.

 

Thanks

0 0

Replies

replied on February 2, 2015

Admin console and the client are both on the same machine?

0 0
replied on February 2, 2015

Yes, the user has both the Client and the Administration Console on their workstation.

0 0
replied on February 2, 2015

Please make sure that the user had Admin rights. 

0 0
replied on February 2, 2015 Show version history

So this is not logging into the repository.  This is simply registering the server in the admin console before even logging in.  Are you talking about local admin rights on the machine or admin rights in Laserfiche? 

0 0
replied on February 2, 2015 Show version history

On the LF Server, open the LF Admin Console, in the Left pane, go to the System Managers node and make sure the AD domain user that is trying to create the repository is present.

replied on February 2, 2015 Show version history

We are not trying to create or register any repository.  We are trying to simply register the server in the Administration Console.  When you first open the Admin Console it asks you for the name of the server.  

 

It finds the server name but we cannot connect to it because of Access Denied.  We can register the repository/see the server no problem through the full client.

0 0
replied on February 2, 2015

Do you have a firewall or security software on the server that might block that connection? Does the admin console on the sever connect with error?

0 0
replied on February 2, 2015

No that I am aware of.  The question is, is the traffic between the admin console and the server different than the client and the server?  Client connects and works fine.  Admin console connects and works fine from the server.  Probably best to start a support case.

0 0
replied on February 2, 2015

Is the user able to login to the Client once they have attached it to the server? Is the user a named user already?

0 0
replied on February 2, 2015

Yes, they can log into the Client.  They are a named user using Windows Authentication.  

0 0
replied on February 2, 2015

What port is the LF server service using?  If the port was changed, did you use that when registering the server in the Admin console as well?

0 0
replied on February 2, 2015

Default ports, no change in ports.  Other workstations can connect just fine with the admin console so it is not ports or firewalls.  IT has just said the are going to re-image the machine and do a clean install of the newest version since it makes no sense.  I guess we'll try some more stuff after the upgrade and start a case if it is still not working.

0 0
replied on February 2, 2015

Sounds good. Have a good day

0 0
replied on October 21, 2015

My customer is getting the same issue. Was there any resolution on this?

0 0
replied on August 18, 2017

We recently ran into this same problem. 

Adding the domain account for the user to the System Managers list resolved this.

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

Sign in to reply to this post.