Community
Vault Forum
Welcome to Autodesk’s Vault Forums. Share your knowledge, ask questions, and explore popular Vault topics.
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Replication errors in backup log

10 REPLIES 10
Reply
Message 1 of 11
pderby4
578 Views, 10 Replies

Replication errors in backup log

Can any body tell me why I am getting replication errors in my Vault log since upgrading to 2008.The backup still completes successfully. see part of my log below

24/05/2007 12:28:41 Replication could not replicate resource id: 4990 version id: 4991. Replication has tried all available sites.

24/05/2007 12:28:41 Replication continuing because orphans were allowed for this call.

24/05/2007 12:28:41 Replication could not replicate resource id: 10520 version id: 10521. Replication has tried all available sites.

24/05/2007 12:28:41 Replication continuing because orphans were allowed for this call.

24/05/2007 12:28:42 Replication could not replicate resource id: 2783 version id: 26342. Replication has tried all available sites.

24/05/2007 12:28:42 Replication continuing because orphans were allowed for this call.
10 REPLIES 10
Message 2 of 11
Anonymous
in reply to: pderby4

If you are not using Productstream Replicator 2008 then that means that your
vault has orphaned files. Orphaned files are when you have file iterations
in the vault database but not in the filestore.

-Bryan

"pderby" wrote in message news:5610671@discussion.autodesk.com...
Can any body tell me why I am getting replication errors in my Vault log
since upgrading to 2008.The backup still completes successfully. see part of
my log below

24/05/2007 12:28:41 Replication could not replicate resource id: 4990
version id: 4991. Replication has tried all available sites.

24/05/2007 12:28:41 Replication continuing because orphans were allowed for
this call.

24/05/2007 12:28:41 Replication could not replicate resource id: 10520
version id: 10521. Replication has tried all available sites.

24/05/2007 12:28:41 Replication continuing because orphans were allowed for
this call.

24/05/2007 12:28:42 Replication could not replicate resource id: 2783
version id: 26342. Replication has tried all available sites.

24/05/2007 12:28:42 Replication continuing because orphans were allowed for
this call.
Message 3 of 11
pderby4
in reply to: pderby4

Thanks for the information

So do I ignore these messages or how can I find the database entries to delete.
Message 4 of 11
brpiyer
in reply to: pderby4

Hi

Using product stream and replicator i have attached the file and when i try to open the file i getting the error has not copied to you local server as in attachment when i click on yes to all button i get the error message as following sites are not accessible at this time Message was edited by: brpiyer
Message 5 of 11
Anonymous
in reply to: pderby4

Could you attached the server vlog with the error. That would have more
detail on the specific connectivity problem.

The logs are located at:

C:\Documents and Settings\All Users\Application
Data\Autodesk\VaultServer\FileStore

Have you successfully replicated files in the past?

Paul Gunn
Message 6 of 11
brpiyer
in reply to: pderby4

Yes ! the logs file says it is not replicated it is happening from the day of installation what can be reason.

Log files as follows could not attach:

7/18/2008 1:50:19 PM Replication continuing because orphans were allowed for this call.

7/18/2008 1:50:23 PM Replication could not replicate resource id: 364142 version id: 373928. Replication has tried all available sites.

7/18/2008 1:50:23 PM Replication continuing because orphans were allowed for this call.

7/18/2008 1:50:28 PM Replication could not replicate resource id: 365132 version id: 376124. Replication has tried all available sites.

7/18/2008 1:50:28 PM Replication continuing because orphans were allowed for this call.

7/18/2008 1:50:33 PM Replication could not replicate resource id: 378924 version id: 379059. Replication has tried all available sites.

7/18/2008 1:50:33 PM Replication continuing because orphans were allowed for this call.

7/18/2008 1:50:38 PM Replication could not replicate resource id: 503079 version id: 503080. Replication has tried all available sites.

7/18/2008 1:50:38 PM Replication continuing because orph
Message 7 of 11
Anonymous
in reply to: pderby4

When the replicator is installed, it validates that all of the files in the
database exist in the filestore. And that the checksums for these files
match those in the filestore. What you are seeing are cases where that
initial validation is failing for certain files - this makes them
unavailable for replication.

How many files are you seeing this for?

Paul Gunn
Message 8 of 11
brpiyer
in reply to: pderby4

thanks Paul

replication error are happening every day in the log file since it is installed do you have any solution to debug this
Message 9 of 11
Anonymous
in reply to: pderby4

Hi,

If I could ask a few questions:

- Does this problem happen for new files that you add to the vault? e.g. can
you add a file to one server and access it from another server? ?
- When you mention seeing this errors in the log every day: are the errors
for the same set of files [ids]?
- About how many error entries do you see in the log files on a given day?
- Have you recently run a scandisk on your harddrive with the filestore? If
these are file checksum mismatches, disk problems can sometimes be the
culprit.

Thanks,
Paul
Message 10 of 11
brpiyer
in reply to: pderby4

it happens for every file yes i can add to one server but when i open on the other server it given the error as file not loaded to the local server how to run scandisk on the hard drive with the file store and it is a new server
Message 11 of 11
Anonymous
in reply to: pderby4

It is normal to see the 'file replication' dialog box in the scenario you
describe, since there would not have been time for a scheduled replication
to occur. However when you hit the 'yes' button, replication should either
work or there should be a specific error in the log file if the servers
can't talk to one another.

I'd recommend contacting product support so they can help you work through
this issue. This behavior is definitely not something I have seen before.

Sorry I couldn't be of more immediate help on this problem..

Paul

Can't find what you're looking for? Ask the community or share your knowledge.

Post to forums  

Autodesk Design & Make Report