I've got our beta server up and running with an Internal client, have loaded all of the GoMePubNew elements on the server, and performed the database setup as best as I can determine for a new age.
However, I am encountering a problem when a client references the age. The client insists on providing a new UUID for the age every time it requests the age, and it never matches the age UUID in the database. Therefore the age load fails for the client.
I must be missing the significance of one of the fields in the age or ageinfo entries. They are displayed below:
age
Code: Select all
nodeid createtime modifytime creatoracctid creatorid uuid_1 uuid_2 filename
192,265 2017-03-16 14:53:22 2017-03-16 14:53:22 8afc208e-12f2-4f53-9056-d841ade64b9c 192,265 8afc208e-12f2-4f53-9056-d841ade64b9c [NULL] GoMePubNew
Code: Select all
nodeid createtime modifytime creatoracctid creatorid int32_1 int32_2 int32_3 uint32_1 uint32_2 uint32_3 uuid_1 uuid_2 string64_2 string64_3 string64_4 text_1
192,270 2017-03-16 14:53:22 2017-03-16 14:53:22 8afc208e-12f2-4f53-9056-d841ade64b9c 192,265 0 [NULL] -1 192,265 0 0 8afc208e-12f2-4f53-9056-d841ade64b9c [NULL] GoMePubNew GoMePubNew [NULL]
Thanks ... as I said in the AGM, we're >< this close!
_R