Apple Event: May 7th at 7 am PT

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

AddressBook-v22.abcddb.1.incompatible files in Trash OS X 10.7.2

I have a 10.6.8 server that provides services (DNS, DHCP, OD, AFP, Mail, Calendar, Address Book, Web, and Push notification) to my home/business network. I use network accounts with AFP network home folders. All services and apps have been working flawlessly with 10.6.xx clients.

I recently purchased a new MacBook Air that is running 10.7.2 Lion. I also recently upgraded my Mac Pro to 10.7.2 Lion from 10.6.8 Snow Leopard.

After the upgrade, I am now seeing multiple copies of files appear in the Trash such as:

AddressBook-v22.abcddb.1.incompatible

This happens whenever any app that accesses the Address Book database for autocomplete is launched (Mail, Skype, etc.). Emptying the trash fails because the files are in use. If I close all apps, sometimes the Trash will empty and sometimes it won't. Have had to clean out the .Trash folder with rm -Rfd * in the terminal; sometimes I have to ssh into my network account on the server to get this to work. Running the command in the terminal on the locally mounted network home does not work.

I have a CARDDAV account with all my addressbook entries on the 10.6.8 server; this problem seems to be worse if the CARDDAV account is configured in Address Book on the 10.7.2 client. I have tried removing the CARDDAV account and also moving the ~/Library/Application Support/Addressbook/ folder and relaunching Address Book. Neither results in the cessation of creation of the AddressBook-v22.abcddb.1.incompatible files in the Trash.

Also, when the CARDDAV account is configured in Address Book on the 10.7.2 client, it constantly tries to sync with the 10.6.8 server, and makes substantial numbers of duplicated groups call "Addressbook" and "My Contacts." However, the contacts are not duplicated in the Address Book on the 10.7.2 client. The Address Book server log shows continuous connections and PROPFIND requests from the 10.7.2 client. The CARDDAV data on the server appears to be intact as it works perfectly with iOS 5 clients (iPhone 4, and iPad) and 10.6.8 clients and is not damaged or duplicated.

I am using the same network account on both my Mac Pro and the MacBook Air. On the MAcBook Air, the account is mobile, with a synced portable home directory. I am no longer logging into 10.6.8 systems with this account as I have migrated all the preferences to 10.7.2. I have the same issues when using either computer.

I'm not sure if these two behaviours are related? Is anyone else having similar issues?

All the other services are configued and working fine on the 10.7.2 clients (iCal, Mail, etc).

Mac Pro, Mac OS X (10.7.2)

Posted on Dec 5, 2011 6:01 AM

39 replies

Dec 19, 2011 6:31 PM in response to mbraun1973

mbraun1973,

Did you delete the .db.sqlite file in the Address Book data store for your user account on the server?

This has to be done at the command line with root access. I explained in detail where to find the file and how the data store is setup.

Deleting this file and letting the AddressBook Server re-create it seemed to eliminate the last few problems that I was having; no more incompatible files and no more duplicate groups.

Early on, when I first noticed these problems, in addition to the "addressbook" duplicate groups, I also had duplicate groups called "My Contacts"; these were remnants from Mobile Me. One of my systems was still configured for Mobile Me; even though I was no longer syncing contacts, it was duplicating this old group from the Mobile Me server.

This is why I think that SyncServices has a role in all this nonsense. You may want to move/delete all of the files/plist for syncservices in addition to the files/plist for the Address Book on your client machines (although this is discouraged by apple); this also resets all of the sync setting for other devices and apps. It seems that a lot of these problems are carried over from managed accounts that had previously been configured under 10.6.8 and had syncservices syncing data in the background.

I have come to think that as a general rule with managed accounts, it is probably a best practice to start with fresh accounts and manually transfer important files and then reconfigure all services, than to try to upgrade accounts from running via 10.6.8 to 10.7.

You may also want to try to rebuild your mailbox in the Mail app; I did this also and cannot be sure if it was helpful or unneccessary.

Regards,

Randy

Dec 19, 2011 6:43 PM in response to mbraun1973

Hey Stefan and mbraun1973,

After recognizing some of the similiarities of the problems that mbraun1973 was having to my own, I became more convinced that syncservices was the culprit behind this nasty problem. So I did some Google searching on syncservices and came across this article from the apple knowledge base.

http://support.apple.com/kb/TS2481

It is for advanced troubleshooting of syncservices; oddly enough, if you read the section on correcting issues with syncing address books contacts and groups, their solution is almost exactly what I have figured out empirically.

In addition to what Apple has outlined above, I think it is still wise to delete the .db.sqlite database file on the 10.6.8 Address Book Server to reset everything to a baseline.

I sure wish I had came across this several weeks ago!!!

I think this is why both of you have continued to see issues even after going to iCloud. The problem is with syncservices, not the Address book app or the AddressBook Server.

Take a look and see if it helps!

Regards,

Randy

Dec 20, 2011 8:17 AM in response to Randall Rodrigues

Hi Randy, hi M,

i have followed every step you have mentioned, Randy. The result is as the following all on the same client machine:

1) doing it in the server managed account, it just take a few moments until the first incompatible file in the trash shows up again. I had cleaned the addressbook files and directories as discussed before and!!!! even deleted the __uids__ directory for that carddav account. I hadn't started the addressbook app when the incompatible file showed up. After starting the addressbook app it happened what expected after a while the first "auto" created group called "addressbook" (same as before) showed up. So no progress on my side with that.

2) after nearly getting mad with all that I had created a local account on my client machine. I have made a backup of the cards as described in the sync help. After doing all that described in the sync help I have reimported the cards. I don't know why but I am fine on that account. It is talking to the server service without any problems and even mail is runnig - which is more or less the same as on the server managed account as I am using the same imap accounts.

This evening I will try to connect the iphone 4 as the first mobile device to the addressbook server service to see what happens next.

Maybe it is caused by the syncing with the server managed user account but I can not find out where exactly is the problem........

Anyway many thanks for your help and support. It is already a great help to see, that I am not the only one facing this weired problem.

Regards

Stefan

MISC_IT

Level 1

7 points

Jan 26, 2012 3:32 PM in response to AppleSiebi

Hi All,

I am experiencing the same issues as you getting the AddressBook-v22.abcddb.1.incompatible file(s) in the trash of my Lion 10.7.2 clients who have Network Homes on a 10.6.8 server. I experience issues with all of the following scenarios:

1. Cardav account (Zimbra hosted) with Address Book will generate the above mentioned files, as well as, duplicate a 'Contacts' contact in the address book exponentially.

2. Contacts 'locally' stored in the users home dir (On My Mac). I get numerous copies of incomaptible abcddb files and periodically lose my contacts altogether. I am constantly importing from a back-up (once a week) due to the loss.

3. I tried to used iCloud to store my contacts and had the same issue as my Cardav...duplicate contacts.

I've tried resetting 'syncservices' per one of the discussion topics, I've deleted all things Addressbook related and tried to recreate from scratch. I've re-installed Lion from a .dmg, so as to eliminate any traces of Snow Leopard from the OS. I tried turning off auto-complete in Mail.app.

Nothing works! Very frustrated. Have been tempted to try installing Lion Server, however, I've read too many negative comments on the product. Crossing my fingers that Apple is aware and fixing in 10.7.3.

I'll be watching this thread closely...hopefully someone can stumble upon a solution.

MISC_IT

Level 1

7 points

Feb 2, 2012 12:48 PM in response to MISC_IT

All,

I may have found a culprit to the issue. I've searched high and low on the client machine to discover a culprit, since I'm not running Addressbook Server on my OS X Server. Today, I stumbled across the following message in the server console:

2/2/12 1:41:48 PMmdworker[26335]Incompatible address book database file detected, will attempt reimporting: Error Domain=NSCocoaErrorDomain Code=134130 UserInfo=0x10424b7a0 "Persistent store migration failed, missing source managed object model." {

URL = "file://localhost/Network/Servers/server.XXX.lan/Volumes/Data/Users/XXXXX/Libra ry/Application%20Support/AddressBook/AddressBook-v22.abcddb";

metadata = {

ABCoreDataImportCompleted = 1;

ABDatabaseVersion = "0.03";

NSPersistenceFrameworkVersion = 358;

NSStoreModelVersionHashes = {

ABCDAbstractGroup = <ba62cdec 9e60eadb ccdf6bf7 e9bc8a0b ca066fab e7ecabbd eb4e3d04 7630658a>;

ABCDAddressBookSource = <97b50fc1 a40f3561 664170fc 7f85db1a f058f6bf ab67ba08 27888ffd b9f416b1>;

ABCDCalendarURI = <f0d2c080 6f818b36 c73fc230 abc033cd b98b58d2 d582537f be080be8 4be8a7a0>;

ABCDContact = <6120888e 2b2fa7e1 98e54e12 f424a47d 1038ace5 438ef3b7 1ed94d87 efa521fc>;

ABCDContactDate = <12e47eaa 48c2c4e8 4d8826c0 41412b0e ade51814 ca23aa67 b08521cb 9cf3f8b5>;

ABCDContactIndex = <11142572 88b52afe b73fb637 b017ce5c 7240dba1 12536ea7 7635a3b1 9a5c8ef6>;

ABCDCustomProperty = <93c06f53 a31a18d6 6d9fcae8 8b9e99b2 378936a5 2ddc3ba1 17b616e1 9d1023a9>;

ABCDCustomPropertyValue = <ddd17ce4 7117ce4c bd8bf4e7 55da5cf3 31f34caa fadd081a f76b8680 c931b0e5>;

ABCDDeletedRecordLog = <391140e9 47f3a246 0b45ce58 f9a000af 8463886b ef8f2349 be03055f 694c7951>;

ABCDDistributionListConfig = <d957cd49 d761d183 75c1f415 4568846c 022b5d2d a22495d5 8b24a2b2 53fcff6f>;

ABCDEmailAddress = <439cb1eb 6a173008 c131f3e4 03293d28 35fac915 a6be0078 87de407b 8a6b21d1>;

ABCDGroup = <7e1f0684 f5982e5c 27a98786 affeb5f0 7e43fd41 a4e1f0f2 9fb98f8a 2d5159a3>;

ABCDInfo = <87e32bb4 31ae9549 00a004c3 6e4862ff f730c0de cc15cfa4 b72a6971 9e0311c0>;

ABCDMessagingAddress = <1791086c de4d02e7 38ced6c5 d6b7cbea 2bbc2fa2 b2bf504a fdc8d502 f222323a>;

ABCDNote = <f002a6d6 c7943190 beadc9c5 0da0541f 2ec61add dacff04d a3aa4fe9 314c32e0>;

ABCDPhoneNumber = <c8e81e27 fdcc2282 de359389 684f960d 5ec3d760 16e3b84b 4c3a322f f6406033>;

ABCDPostalAddress = <eede6e8d c263dc8c 09cfe1b8 24fdeb72 92cc4152 a7086cdd 85ccf602 3466b73e>;

ABCDRecord = <922e5694 9ff0af61 8a3cb83f c3b97885 10a9c197 5f3bedbb 7dac051f 6ded0005>;

ABCDRelatedName = <908876cc 529e37f5 af5baf59 2d6e56f0 ee165903 cb5c82df 238433c6 6aad8709>;

ABCDRemoteLocation = <90356d2d 68877daa e33bdfa7 047a67b6 0c314df4 6ea0cc14 b3e05161 4002fe16>;

ABCDService = <87219f66 6bc836f9 27b1a165 32286ba0 f43a3b75 f87d71ac 18574424 76ee3a7f>;

ABCDSharingAccessControlEntry = <7fcc1379 4fb722c2 34a0ffb4 10840c63 8543f351 3859bab0 d63a286a 822dca70>;

ABCDSmartGroup = <325826a1 de1b48f9 1b7e752c 8bfceb47 d5dbadbe a16c9ada 6796fc35 baa41f20>;

ABCDSocialProfile = <312de9e3 eb1c36d2 c38922e0 221c0a23 a773ed18 ecb400b4 6556263c 3ce5e060>;

ABCDSubscribedContact = <66a47df8 858c0478 dacdd416 f16a02ea eddac35e 78488924 7db644ef adef0fc3>;

ABCDSubscribedGroup = <b4b13039 920f9923 a5b41273 9e264768 6f3fd96d bb3670c8 aa7fc153 b1bbfa47>;

ABCDURLAddress = <072c933e 8b4ceb17 ff5b54ff 19e1f20f f6b7c164 219c9093 2e68e21c 81781a74>;

ABCDUnknownProperty = <522a8435 5e84e3d2 a3eeebe5 ccbb0c9b ac21eb11 e8623cf7 1a67bb5c bcfbd52a>;

};

NSStoreModelVersionHashesVersion = 3;

NSStoreModelVersionIdentifiers = (

);

NSStoreType = SQLite;

NSStoreUUID = "F1927E79-6EF7-4ED0-9772-516C038ED370";

"_NSAutoVacuumLevel" = 2;

};

reason = "Can't find model for source store";

}

I searched 'mdworker' and returned results focused on Spotlight. I had read a kb on Apple's site regarding Spotlight on sharepoint's that are multiple layers deep, so I decided to look at disabling Spotlight on the server. I disabled Spotlight on the 'Users' folder, in which the netwrok home directories reside. Since disabling Spotlight, I have not had the console message, nor duplicate contacts in my client addressbook. I will monitor this closely and report any changes. Let me know if this helps.

Aug 25, 2012 6:23 AM in response to Randall Rodrigues

did anyone realize that the autocomplete function of mail is only working for lokal adresses? If local adresses are empty and all contacts are in the carddav server as it should be the autocomplete doesnt find anything in the addressbook and will relay only on formerly sent email adresses.

The iOS is the undertaker of OS X ... 10.7.4 not working right and 10.8.0 allready released and not working right ether :-(

Sep 20, 2013 11:25 AM in response to Randall Rodrigues

I realize this is an old thread, but our school was only just now able to upgrade to Lion on our systems and we've been hit with this problem big-time.

I ran across this thread weeks ago and have followed all the instructions here, and the problems persist. Users will still lose Address Book (or Contacts on a few newer systems) data, even their "local" data. I've gone so far as to delete absolutely everything Address Book and sync related an all the staff users accounts, turned off the address book server completely, and deleted the shared address book account in each user account. Users will then usually get a couple days of Address Book use before all (or at least some of their contacts are again deleted) and .incompatible blah blah blah files start showing up in their trash.

It's a total nightmare. At this point I'm looking at testing the solution of a completely clean install of the OS and software on a select few computers, and then deleting and compltely rebuilding, from scratch, each staff user account on the server. (Mac OS X Snow Leopard server, fully updated).

Has anyone else come up with a sure-fire solution?

Has anyone blown everything compltely away and started from scratch like I'm planning to do? If so, did it work?

Thanks for any help you can provide...

Nov 25, 2015 2:46 PM in response to Randall Rodrigues

The article at http://support.apple.com/kb/TS2481 presents a 404 error. I would really like to try the solutions outlined there. Has it been moved?

-p

Dec 28, 2015 8:43 PM in response to Picoscope

Unless/until Apple fixes the 404 error, there’s a version at the Internet Archive Wayback Machine.

AddressBook-v22.abcddb.1.incompatible files in Trash OS X 10.7.2