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

Question

Question

un-register and re-registering a working repository

asked on November 3, 2016

Hi,

If we happen to unregister a working laserfiche repository from admin console and then try to re-register it using same database and same path, then do we need to update it's UUID? If yes, then why is it necessary to update the UUID? Is there any other workaround for re-registering the repository other than UUID update? 

0 0

Replies

replied on November 3, 2016

Hi Harshada,

 

Simply un-registering and then re-registering the same repository will not require you to change the UUID with no changes made. You can simply follow the registration wizard steps and attach the repository.

 

Hope this helps answer your question smiley

0 0
replied on November 3, 2016

Hi Chris,

 

Thanks for prompt response.

But what if there are multiple repository's already registered on single laserfiche server and we need to unregister and re-register only one of the repository on same laserfiche server? 

 

When we are trying to do the above mentioned, we are encountering the error 'Could not attach repository. Another repository with same UUID already exists.'

error.JPG
error.JPG (38.78 KB)
0 0
replied on November 3, 2016

Ah, ok, so it seems you have a copied DB with the same UUID attached already. You will need to update the UUID so it doesn't match the currently attached repository.

0 0
replied on November 3, 2016

We had updated UUID before attaching the database to the second repository and it was working fine until yesterday. But unfortunately we unregistered it yesterday and are trying to register it again.

0 0
replied on November 3, 2016

Sounds like you might have to update the UUID again or something has gone wrong.

 

You can update it using the utility in the KB article here - https://support.laserfiche.com/kb/1012907/using-the-repositoryuuidupdater-exe-utility-to-modify-a-repositorys-uuid-

1 0
replied on November 22, 2016

Hi we have LF server where we have 2 repositories but only 1 Web application and we switch over to repositories as per our need. ( one is SQL 2008 and one is 2016). Both using the same SVC account.after configuring the repository back to 2008 from 2016 we have done all the required configurations in web config and config files. but we landed up in a error "Account Locked". Then we thought to change the application pool log on and changed it to my own name. we also changed the services from LS server 
(user account and user management) and given my name as log on and the problem gone away and it started working. but now no one else is able to login , not even windows users but the Retail Auditor and others as well.

The different kind of errors as below .

 You do not have access to this application. ( Latest error )

Account locked: exceeded maximum period of inactivity.

pls guide us if its to do with svc account mismatch and used by others as well at the same point of time. 

The interesting thing i did that , i stopped sql 2016 completely and tried the LF application and it started saying the operation time out and if i start it again it will show the same error. i am sure that in web config there is no connection to sql 2016 .

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

Sign in to reply to this post.