The repo file located in a shared drive is accessible in the Default space, however, the same repo file is not accessible in a different space. When attempting to access connectors in a different space, gives the following error. I am unable to change the read password in the Default space. I don’t even know the read password, only know the write password. User permissions between the spaces is identical.
Exception: MorphClientGeneralException
Get list failed. Invalid read password specified or repository data is corrupted
Call stack:
at Morph.DataDrivers.RepositoryProviders.ServerRepositoryProvider.#=zqQ4DS14iLjoN3quwzPaFVt4=.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Morph.DataDrivers.RepositoryProviders.ServerRepositoryProvider.#=ztWQDPazvBzpRlG3Zgl$YO7R6x81Ppu5Q2Q==.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Morph.DataDrivers.RepositoryProviders.RepositoryProviderBase.#=zWv4xIsKuVHXT1zTPnBQyI5U=.#=zhET296ty00TMpHorwgVBrLTUBR1p.MoveNext()
If the read password is configured and you don't know it, then it's not possible to make the repository available in another space without specifying the read password.
What you can do:
Option 1: Remove or change the read password in the 1st space.
Option 2: Create a brand new empty repository in Desktop (repo.sqlite), upload it to the second space and configure it to be used by the space. If the settings permit it, open the connectors from the 1st space in Desktop's Connector Manager, copy them, switch to the 2nd space and paste them there. As a result, you will create a clone of the 1st space's repository in the 2nd space.
May it be that you placed the .repo file to the server shared folder -- possibly copying it from the EasyMorph Desktop app, or, alternatively, you might have directly replaced the Server .repo file with your own at some point? If so, this approach will not work. Server-borne repositories can only be generated by the Server itself and could not be accessed by the Desktop.
If I'm correct at my guess, you'll need to recreate the repository in the Space and re-create connectors in that repository - but through EasyMorph Desktop and ServerLink, rather than modifying the .repo file directly.
As a side note, if 'shared drive' means a network drive, please avoid placing .repo files there. These .repo files are actually databases, and their integrity cannot be guaranteed on network drives.
Is it possible to recover the provenance and lineage of this speicifc .repo file? Maybe, it was copied from some other Server installation or the system was reinstalled etc? This information would help in identifying the root cause
Could the situation be as follows: initially, years ago, someone other than you set up one or two Spaces with this .repo on the Server and assigned a read password for it. Later, more recently, you or someone else added a fresh Space and tried to reuse this repository for this Space. However, the person who created the 3rd space or set up this repo for reuse did not know the read password and so we're getting the error.
In other words, am I right in understanding that this .repo is functioning in one or two Spaces that were set up earlier, but it doesn't work in the more recent Space?
