• Multi-Server replications problems.

    By Amir Gilboa 2 decades ago

    We have just updated to 1.5.3, and are having problems keeping a 2nd server with a working replica. The tags/lables are not finding the right language values, and show such info as:



    (?)outMaint1Header

    (?)outdefmain1 view01

    (?)outdefmain1 view02 (0)

    (?)outdefmain1 view03 (11)



    etc..



    This happens if the 2nd replica is local or on another Domino server.



    We have two offices and need a good working local copy in each location for speed/preformance. However we don't want two seperate help-desk databases, so we can distribute which person helps regardless of where they work.



    Thanks in advance.



    Amir.

    • Might be a replication issue

      By Thomas Schulte 2 decades ago

      We have !!HELP!! installed on four different servers and no problems like that. It might be that your replication is not replication all the documents due to missing right or something like that.

      • It corrupts the original replica

        By Amir Gilboa 2 decades ago

        I don't think replication by itself explains why the original replica also gets corupted in the same way… I think its the language settings/environment settings that get messed up. And I can't run the language selector after it happens.

        Amir.

        • he language settings can not be the problem

          By Thomas Schulte 2 decades ago

          because. If you use the language selector this is saved locally in the notes.ini

          If you decheck the language it first uses the users region for finding the language that should be used and if he does not find it the default language is used.



          So there must be another problem and i still believe it has something to do with the rights your server has while replicating



          Just look at the alldocuments view on the server that does not work and tell me if you see documents named ConfigLanguage.

          • I've fixed it.

            By Amir Gilboa 2 decades ago

            I Had to reload ALL the lang docs… but that fixed things on both systems… now it seams to work fine. I suspect something went wrong during the upgrade from 1.5.0 to 1.5.3 that didn't show up until we replicated the dbs.



            Thanks for the tips.



            Amir.