We recently began using replication using sybase anywhere/mobilink within an application. We have had minimal problems up to now (Adaptive Server Anywhere / Mobilink version 188.8.131.5202). I now have several users who can not synchronize with the consolidated database because of a particular remote1 file that gets created with a "pif" extension. It blows errors as listed below:
yea, we already went the re-extract route. I think the problem may be at the server level which is not allowing for any ".pif" files to be deleted, and thus causes the replication process to crap out. I did some research and found that the newest version (v9) accounts for this by allowing you to specify what file extensions you do not want dbremote to use (ie, you can exclude file extensions such as "exe", "pif", etc, so appearantly this was a noted issue - though it does not help me now because I am not on that version). I am working this issue as a server related issue regarding permissions on files contained in the messages folder (where remote1 files are stored on our server).
Thanks for the reply - I was hoping there were some others out there that experienced this problem - We'll see.