@Ushani Weeraratne 

Do you have any other records in the repository tab?. If you have a record with * as document class in generating state which means this is the all the document classes default repository which is why you can observe the files checkin works even the repo set (ftp one)to usable state. 

Hi @Ushani Weeraratne,

The shared repository you have setup is not accessible through the environment. That’s why you are getting that error when the repository is set to generating. Please check whether the environment can access the network path you are adding as a shared location.

As for why its working when its set to :”usable”, it means that any new documents that is checked into the class for which the repository is setup will be checked into the next applicable “Generating” repository. Repositories are set as usable when the repository location is full or growing in size unnecessarily so any new documents for the class will be checked into a different “Generating” repository. For a certain document class there can only be one “Generating” document repository in a given time.

So in this case as Sahan mentioned above it might be checking into the Default database repository ( * document class) therefor you are not getting any errors. 

Setting up Shared repositories can be hard, because several things needs to work. Firstly, the username and password for the user set on the repository must be correct and that user need to have write access to the folder. Furthermore, any firewalls need to allow the network traffic and internal network settings in the container/cluster need to be correct as well.

It sometimes helps to have the Aurena Agent enabled when trying to check-in from the Document Revision page. When it fails you might get a more detailed error message.

This has been discussed here several times, perhaps you can find clues in other posts and replies as well.

PS. This is Remote deployment, right?