I had this same issue and made a call to ESRI to ask them about what the problem was. If you open the.xml document there is a line that indicates "[repllicaName]gen#". Compare this number to the one found under the gdb the replica was created from under Distributed Geodatabases/Manage Replicas and double click on the repllica you're trying to import a message from to open the Replica Properties. Under Relative Replica it will indicate it's generation number. For instance in the Replica I am trying to import an .xml message to says the generation is 3 and the .xml message I tried to import has a generation of 6. Therefore there should be two other .xml message files that were never imported/received on my side. As for the version part, make sure the version you created when you first created the replica is present. I always use DBO from our SDE so that other people in our company can import messages just in case I'm not around to do so and I guess that's just a better way to go. If you didn't do that to begin with when you created the replica I'd think it's too late for that. But just make sure the version is created with the same name and under the same account username as when you created the replica. Hope this helps! Jeanetta
... View more