Categories: Report a problem :

Google Drive PRIMARY KEY error

Showing 1-208 of 208 messages
Google Drive PRIMARY KEY error samwtheck 4/27/12 1:25 PM

While Google Drive (Windows 7 x64) was syncing a lot of files, it stopped with the following error:

"Sorry, Google Drive needs to quit.

An unknown issue occurred and Google Drive needs to quit. Error: PRIMARY KEY must be unique

If you see this error repeatedly, try disconnecting your account"

I attach an screenshot.
Re: Google Drive PRIMARY KEY error Himanshu V 4/27/12 2:05 PM
Can you restart your client and follow the steps bellow to send us a log file?

  1. Press the Shift key and open the Google Drive menu
  2. Select "Enable diagnostic mode."
  3. Click Start logging.
  4. Reproduce the problem you experienced (Click ''Retry all''). For example, if you receive an error message when you add a file to the Google Drive folder on your computer, repeat that action while logging is active.
  5. When you’re done, click Send report to Google.
  6. When the logging file is sent, you’ll receive a Report ID. Write the Report ID down and share it here.

If step 6 fails, you’ll see an error message saying the the sync log couldn’t be sent to Google. To manually send the sync log to Google:
  1. Click the OK button.
  2. The folder on your computer that contains the sync log file will open.
  3. Attach the sync log to this thread.
Re: Google Drive PRIMARY KEY error Buravchik 4/27/12 10:00 PM
Same happens with me. Here is log:
Here is part of log:
2012-04-28 08:34:02,996 1056:LocalFSPoller   common.local_watcher:898 LocalFSPoller first pass started. Waiting for localWatcher to start watching.
2012-04-28 08:34:02,996 4904:Worker-1        logging:1448 Exception occurred in thread Worker-1: PRIMARY KEY must be unique. More info: Traceback (most recent call last):
  File "P:\p\agents\hpam3.eem\recipes\151852664\base\b\drb\googleclient\apps\webdrive_sync\windows\build\pyi.win32\main\outPYZ1.pyz/common.sync_client_thread", line 44, in run
  File "P:\p\agents\hpam3.eem\recipes\151852664\base\b\drb\googleclient\apps\webdrive_sync\windows\build\pyi.win32\main\outPYZ1.pyz/common.sync_client_thread", line 164, in Run
  File "P:\p\agents\hpam3.eem\recipes\151852664\base\b\drb\googleclient\apps\webdrive_sync\windows\build\pyi.win32\main\outPYZ1.pyz/common.fatal_exceptions", line 34, in CheckException
IntegrityError: PRIMARY KEY must be unique
Re: Google Drive PRIMARY KEY error stephenm00 4/28/12 10:19 AM
Im getting this as well!
Re: Google Drive PRIMARY KEY error RiceyB 4/28/12 9:00 PM
I got his too.
 
Do I need to send my logs?
Re: Google Drive PRIMARY KEY error rlsayre 4/29/12 8:20 AM
Same thing happens to me. I have run through diagnostic mode yet, but in my case it appears to have something to do with similar filenames inside one directory.

I believe that one application I have executes the following steps when you "save" the file you are working on:
--Assume you are working on "filexyz.suffix"
--The application saves it as "~filexyz.suffix"
--Once it is saved, it erases "filexyz.suffix"
--Renames "~filexyz.suffix" to "filexyz.suffix"

If this is a large file, and Google Drive tries to synch during this time, things go crazy, and I get the dreaded message that "primary key must be unique" and Google Drive must quit.

If I look at the "Google Drive" on my local hard drive, "~filexyz.suffix" is still there. If I look at my Google Drive on the web, I find two files. One named "filexyz.suffix" and one named "filexyz[conflict].suffix. Google Drive will not restart under these conditions.

If I erase "filexyz[conflict].suffix" and "~filexyz.suffix" then Google Drive will start.

This may not be the case, but it looks like Google Drive is ignoring "~" as part of a file name when generating a key for a data base entry to keep track of everything. Or it may not have anything to do with it. But it's a clue.
Papa Bear 4/29/12 1:28 PM <This message has been deleted.>
Re: Google Drive PRIMARY KEY error mentalist 4/30/12 9:57 PM
Same problem here on XP
Re: Google Drive PRIMARY KEY error Shannon Poole 5/1/12 5:58 AM
I am having the same issue. I attempted to do the diagnostic log but when the error occurs I can no longer press the Send report to Google button because it forces me to click the close button. This has happened three times now and I had to reconnect my drive and basically re-sync my whole drive to fix it. This is a pain because you have to start with an empty folder and if you are not sure what is synced and what isn't you have to be careful not to remove any files that have not made it into the cloud yet. 
Re: Google Drive PRIMARY KEY error mathewfoster 5/1/12 6:01 AM
I am getting the Primary Key must be unique error as well.

Report ID - ED46136B61E0517A
Re: Google Drive PRIMARY KEY error mathewfoster 5/1/12 6:11 AM
2012-05-01 07:51:48,000 47608:MainThread      logging:1473 OS: Windows/6.1.7601-SP1
2012-05-01 07:51:48,002 47608:MainThread      logging:1473 Google Drive (build 1.0.2960.1377)
2012-05-01 07:51:52,493 44664:CloudWatcher    common.cloud_watcher:193 Got 934 cloud entries
2012-05-01 07:51:52,582 44664:CloudWatcher    common.cloud_snapshot_diff_helper:448 Prepopulated RID-to-inodes cache
2012-05-01 07:51:52,584 44664:CloudWatcher    common.cloud_snapshot_diff_helper:470 Processed 0 entries
2012-05-01 07:51:53,244 44664:CloudWatcher    common.cloud_watcher:235 Done with full snapshot diff.
2012-05-01 07:51:53,246 44664:CloudWatcher    common.cloud_watcher:269 CloudWatcher generated FSChange(Direction.DOWNLOAD, Action.MODIFY, ino: 4785074604089055, rid: file:0ByQ0t4y3X2cHWTlhZ2dvUUhOX2s, parent ino: 1970324836998407, modified: 1335874744, checksum: 0ef24812cb1472ba3f0852123d88ad04)
2012-05-01 07:51:53,335 35544:Fetcher         common.fetcher:280 There are no blacklisted requests.
2012-05-01 07:51:53,345 46420:Worker-2        logging:1473 Worker starting on FSChange(Direction.DOWNLOAD, Action.MODIFY, ino: 4785074604089055, rid: file:0ByQ0t4y3X2cHWTlhZ2dvUUhOX2s, parent ino: 1970324836998407, modified: 1335874744, checksum: 0ef24812cb1472ba3f0852123d88ad04)
2012-05-01 07:51:53,355 46420:Worker-2        logging:1473 Detected conflict while trying to download file to D:\Shop\Google Drive\Jobs_Current\Snap Fitness_2995A\Snap Fitness_2995A.cvj. Copying conflicted file to D:\Shop\Google Drive\Jobs_Current\Snap Fitness_2995A\Snap Fitness_2995A[Conflict 4].cvj
2012-05-01 07:51:53,579 46420:Worker-2        common.docs_client:1740 Downloading: Snap Fitness_2995A.cvj
2012-05-01 07:51:53,634 43032:LocalFSPoller   common.local_watcher:889 Cloud scan complete. Preparing to start LocalFSPoller
2012-05-01 07:51:55,907 46420:Worker-2        common.proxy_manager:106 Exception while auto resolving proxy.
ProxyInfoResolutionError: inner_error=(12180, 'WinHttpGetProxyForUrl', 'The Proxy Auto-configuration URL was not found.')
2012-05-01 07:51:56,598 46420:Worker-2        logging:1473 Updating inode in snapshot. old=4785074604089055, new=1407374883577140
2012-05-01 07:51:56,598 46420:Worker-2        common.snapshot_sqlite:447 Removing local relation child_inode=4785074604089055, parent_inode=1970324836998407
2012-05-01 07:51:56,599 46420:Worker-2        common.snapshot_sqlite:467 Removing Mapping inode=4785074604089055, resource_id=file:0ByQ0t4y3X2cHWTlhZ2dvUUhOX2s
2012-05-01 07:51:56,599 46420:Worker-2        common.snapshot_sqlite:151 Removing local entry inode=4785074604089055
2012-05-01 07:51:56,601 46420:Worker-2        common.snapshot_sqlite:140 Adding local entry inode=1407374883577140, filename=None
2012-05-01 07:51:56,602 46420:Worker-2        logging:1448 Exception while processing change FSChange(Direction.DOWNLOAD, Action.MODIFY, ino: 4785074604089055, rid: file:0ByQ0t4y3X2cHWTlhZ2dvUUhOX2s, parent ino: 1970324836998407, modified: 1335874744, checksum: 0ef24812cb1472ba3f0852123d88ad04)
IntegrityError: PRIMARY KEY must be unique
More info: Traceback (most recent call last):
  File "P:\p\agents\hpam2.eem\recipes\154662341\base\b\drb\googleclient\apps\webdrive_sync\windows\build\pyi.win32\main\outPYZ1.pyz/common.workers", line 138, in Process
  File "P:\p\agents\hpam2.eem\recipes\154662341\base\b\drb\googleclient\apps\webdrive_sync\windows\build\pyi.win32\main\outPYZ1.pyz/common.persistence_sqlite", line 125, in Wrapper
  File "P:\p\agents\hpam2.eem\recipes\154662341\base\b\drb\googleclient\apps\webdrive_sync\windows\build\pyi.win32\main\outPYZ1.pyz/common.workers", line 267, in _ProcessDownloads
  File "P:\p\agents\hpam2.eem\recipes\154662341\base\b\drb\googleclient\apps\webdrive_sync\windows\build\pyi.win32\main\outPYZ1.pyz/common.workers", line 624, in _DownloadModify
  File "P:\p\agents\hpam2.eem\recipes\154662341\base\b\drb\googleclient\apps\webdrive_sync\windows\build\pyi.win32\main\outPYZ1.pyz/common.workers", line 968, in _UpdateINodeNumber
  File "P:\p\agents\hpam2.eem\recipes\154662341\base\b\drb\googleclient\apps\webdrive_sync\windows\build\pyi.win32\main\outPYZ1.pyz/common.snapshot_sqlite", line 147, in AddLocalEntry
  File "P:\p\agents\hpam2.eem\recipes\154662341\base\b\drb\googleclient\apps\webdrive_sync\windows\build\pyi.win32\main\outPYZ1.pyz/common.sqlite_operations", line 136, in Insert
IntegrityError: PRIMARY KEY must be unique

2012-05-01 07:51:56,602 46420:Worker-2        logging:1473 Crash reporting disabled. Ignoring report.
2012-05-01 07:51:56,604 46420:Worker-2        logging:1448 Fatal error occurred: Traceback (most recent call last):
  File "P:\p\agents\hpam2.eem\recipes\154662341\base\b\drb\googleclient\apps\webdrive_sync\windows\build\pyi.win32\main\outPYZ1.pyz/common.workers", line 138, in Process
  File "P:\p\agents\hpam2.eem\recipes\154662341\base\b\drb\googleclient\apps\webdrive_sync\windows\build\pyi.win32\main\outPYZ1.pyz/common.persistence_sqlite", line 125, in Wrapper
  File "P:\p\agents\hpam2.eem\recipes\154662341\base\b\drb\googleclient\apps\webdrive_sync\windows\build\pyi.win32\main\outPYZ1.pyz/common.workers", line 267, in _ProcessDownloads
  File "P:\p\agents\hpam2.eem\recipes\154662341\base\b\drb\googleclient\apps\webdrive_sync\windows\build\pyi.win32\main\outPYZ1.pyz/common.workers", line 624, in _DownloadModify
  File "P:\p\agents\hpam2.eem\recipes\154662341\base\b\drb\googleclient\apps\webdrive_sync\windows\build\pyi.win32\main\outPYZ1.pyz/common.workers", line 968, in _UpdateINodeNumber
  File "P:\p\agents\hpam2.eem\recipes\154662341\base\b\drb\googleclient\apps\webdrive_sync\windows\build\pyi.win32\main\outPYZ1.pyz/common.snapshot_sqlite", line 147, in AddLocalEntry
  File "P:\p\agents\hpam2.eem\recipes\154662341\base\b\drb\googleclient\apps\webdrive_sync\windows\build\pyi.win32\main\outPYZ1.pyz/common.sqlite_operations", line 136, in Insert
IntegrityError: PRIMARY KEY must be unique

2012-05-01 07:51:57,348 46420:Worker-2        logging:1448 The following request has been blacklisted: FSChange(Direction.DOWNLOAD, Action.MODIFY, ino: 4785074604089055, rid: file:0ByQ0t4y3X2cHWTlhZ2dvUUhOX2s, parent ino: 1970324836998407, modified: 1335874744, checksum: 0ef24812cb1472ba3f0852123d88ad04)
2012-05-01 07:51:57,410 46420:Worker-2        logging:1473 Crash reporting disabled. Ignoring report.
2012-05-01 07:51:57,410 43032:LocalFSPoller   common.local_watcher:898 LocalFSPoller first pass started. Waiting for localWatcher to start watching.
2012-05-01 07:51:57,410 46420:Worker-2        logging:1448 Fatal error occurred: Traceback (most recent call last):
  File "P:\p\agents\hpam2.eem\recipes\154662341\base\b\drb\googleclient\apps\webdrive_sync\windows\build\pyi.win32\main\outPYZ1.pyz/common.sync_client_thread", line 157, in Run
  File "P:\p\agents\hpam2.eem\recipes\154662341\base\b\drb\googleclient\apps\webdrive_sync\windows\build\pyi.win32\main\outPYZ1.pyz/common.workers", line 110, in _RunInLoop
  File "P:\p\agents\hpam2.eem\recipes\154662341\base\b\drb\googleclient\apps\webdrive_sync\windows\build\pyi.win32\main\outPYZ1.pyz/common.workers", line 183, in Process
  File "P:\p\agents\hpam2.eem\recipes\154662341\base\b\drb\googleclient\apps\webdrive_sync\windows\build\pyi.win32\main\outPYZ1.pyz/common.fatal_exceptions", line 34, in CheckException
IntegrityError: PRIMARY KEY must be unique

2012-05-01 07:51:57,410 46420:Worker-2        logging:1448 Exception occurred in thread Worker-2: PRIMARY KEY must be unique. More info: Traceback (most recent call last):
  File "P:\p\agents\hpam2.eem\recipes\154662341\base\b\drb\googleclient\apps\webdrive_sync\windows\build\pyi.win32\main\outPYZ1.pyz/common.sync_client_thread", line 44, in run
  File "P:\p\agents\hpam2.eem\recipes\154662341\base\b\drb\googleclient\apps\webdrive_sync\windows\build\pyi.win32\main\outPYZ1.pyz/common.sync_client_thread", line 164, in Run
  File "P:\p\agents\hpam2.eem\recipes\154662341\base\b\drb\googleclient\apps\webdrive_sync\windows\build\pyi.win32\main\outPYZ1.pyz/common.fatal_exceptions", line 34, in CheckException
IntegrityError: PRIMARY KEY must be unique

2012-05-01 07:51:57,410 46420:Worker-2        logging:1473 Crash reporting disabled. Ignoring report.
2012-05-01 07:51:57,410 46420:Worker-2        logging:1448 notified exit condition <threading._Event object at 0x0481CBF0>
2012-05-01 07:51:57,457 46000:LocalWatcher    common.local_watcher:134 LocalWatcher is up.
2012-05-01 07:51:57,457 46228:EventAggregator logging:1473 EventAggregator run loop has terminated.
2012-05-01 07:51:57,471 44664:CloudWatcher    logging:1473 CloudWatcher run loop has terminated.
2012-05-01 07:51:57,471 35544:Fetcher         logging:1473 Fetcher run loop has terminated.
2012-05-01 07:51:57,519 47660:CrashReportUploaderThread logging:1473 Thread suspended. Skipping crash reporting
2012-05-01 07:51:57,690 47628:Worker-0        logging:1473 Worker-0 run loop has terminated.
2012-05-01 07:51:57,690 47992:Worker-1        logging:1473 Worker-1 run loop has terminated.
2012-05-01 07:51:58,049 43032:LocalFSPoller   common.local_watcher:936 Finished local disk scan.
2012-05-01 07:51:58,081 43032:LocalFSPoller   logging:1473 LocalFSPoller run loop has terminated.
2012-05-01 07:52:03,033 47940:ThreadMonitor   logging:1448 Threads are still alive: ThreadMonitor, LocalWatcher, MainThread
2012-05-01 07:52:03,033 47940:ThreadMonitor   logging:1448 Exiting due to critical failure: PRIMARY KEY must be unique
More info: None

2012-05-01 07:52:03,033 47940:ThreadMonitor   logging:1473 Crash reporting disabled. Ignoring report.
2012-05-01 07:52:03,033 47940:ThreadMonitor   logging:1448 GetErrorCode called but there wasn't anexception to handle: (None, None, None)
2012-05-01 07:57:00,115 46976:MainThread      logging:1473 OS: Windows/6.1.7601-SP1
2012-05-01 07:57:00,115 46976:MainThread      logging:1473 Google Drive (build 1.0.2960.1377)
2012-05-01 07:57:02,243 47920:LaunchThreads   common.proxy_manager:106 Exception while auto resolving proxy.
ProxyInfoResolutionError: inner_error=(12180, 'WinHttpGetProxyForUrl', 'The Proxy Auto-configuration URL was not found.')
2012-05-01 07:57:02,622 47920:LaunchThreads   logging:1473 Config:
Sync root: D:\Shop\Google Drive
Sync collections: set([])
Upgrade number: 5
App version: 1.0.2960.1377
Selective sync: False
2012-05-01 07:57:02,878 47252:EventAggregator logging:1473 EventAggregator run loop has started.
2012-05-01 07:57:02,892 47792:CrashReportUploaderThread logging:1473 Starting CrashReportUploaderThread.
2012-05-01 07:57:02,892 47896:CloudWatcher    logging:1473 CloudWatcher run loop has started.
2012-05-01 07:57:02,892 46516:LocalFSPoller   logging:1473 LocalFSPoller run loop has started.
2012-05-01 07:57:02,892 47864:Worker-1        logging:1473 Worker-1 run loop has started.
2012-05-01 07:57:02,908 47896:CloudWatcher    common.cloud_watcher:214 Performing full snapshot diff.
2012-05-01 07:57:02,908 47208:Worker-2        logging:1473 Worker-2 run loop has started.
2012-05-01 07:57:02,908 47248:LocalWatcher    common.local_watcher:126 LocalWatcher Run invoked.Will wait for first pass of local scan to start
2012-05-01 07:57:02,908 47896:CloudWatcher    common.cloud_watcher:294 Getting cloud resources via regular and changelog feeds.
2012-05-01 07:57:02,908 47528:Fetcher         logging:1473 Fetcher run loop has started.
2012-05-01 07:57:02,908 42564:Worker-0        logging:1473 Worker-0 run loop has started.
2012-05-01 07:57:03,345 47896:CloudWatcher    logging:1473 Requesting Doc List: /feeds/default/private/changes?start-index=57546&showroot=true
2012-05-01 07:57:03,486 47896:CloudWatcher    logging:1473 Requesting Doc List: /feeds/default/private/full?showroot=true&showfolders=true
2012-05-01 07:57:08,668 47896:CloudWatcher    common.cloud_watcher:193 Got 934 cloud entries
2012-05-01 07:57:08,756 47896:CloudWatcher    common.cloud_snapshot_diff_helper:448 Prepopulated RID-to-inodes cache
2012-05-01 07:57:08,759 47896:CloudWatcher    common.cloud_snapshot_diff_helper:470 Processed 0 entries
2012-05-01 07:57:09,420 47896:CloudWatcher    common.cloud_watcher:235 Done with full snapshot diff.
2012-05-01 07:57:09,421 47896:CloudWatcher    common.cloud_watcher:269 CloudWatcher generated FSChange(Direction.DOWNLOAD, Action.MODIFY, ino: 4785074604089055, rid: file:0ByQ0t4y3X2cHWTlhZ2dvUUhOX2s, parent ino: 1970324836998407, modified: 1335874744, checksum: 0ef24812cb1472ba3f0852123d88ad04)
2012-05-01 07:57:09,617 47528:Fetcher         common.fetcher:280 There are no blacklisted requests.
2012-05-01 07:57:09,664 47864:Worker-1        logging:1473 Worker starting on FSChange(Direction.DOWNLOAD, Action.MODIFY, ino: 4785074604089055, rid: file:0ByQ0t4y3X2cHWTlhZ2dvUUhOX2s, parent ino: 1970324836998407, modified: 1335874744, checksum: 0ef24812cb1472ba3f0852123d88ad04)
2012-05-01 07:57:09,664 47864:Worker-1        logging:1473 Detected conflict while trying to download file to D:\Shop\Google Drive\Jobs_Current\Snap Fitness_2995A\Snap Fitness_2995A.cvj. Copying conflicted file to D:\Shop\Google Drive\Jobs_Current\Snap Fitness_2995A\Snap Fitness_2995A[Conflict 5].cvj
2012-05-01 07:57:09,898 47864:Worker-1        common.docs_client:1740 Downloading: Snap Fitness_2995A.cvj
2012-05-01 07:57:09,944 46516:LocalFSPoller   common.local_watcher:889 Cloud scan complete. Preparing to start LocalFSPoller
2012-05-01 07:57:12,214 47864:Worker-1        common.proxy_manager:106 Exception while auto resolving proxy.
ProxyInfoResolutionError: inner_error=(12180, 'WinHttpGetProxyForUrl', 'The Proxy Auto-configuration URL was not found.')
2012-05-01 07:57:12,825 47864:Worker-1        logging:1473 Updating inode in snapshot. old=4785074604089055, new=1407374883577140
2012-05-01 07:57:12,825 47864:Worker-1        common.snapshot_sqlite:447 Removing local relation child_inode=4785074604089055, parent_inode=1970324836998407
2012-05-01 07:57:12,828 47864:Worker-1        common.snapshot_sqlite:467 Removing Mapping inode=4785074604089055, resource_id=file:0ByQ0t4y3X2cHWTlhZ2dvUUhOX2s
2012-05-01 07:57:12,828 47864:Worker-1        common.snapshot_sqlite:151 Removing local entry inode=4785074604089055
2012-05-01 07:57:12,828 47864:Worker-1        common.snapshot_sqlite:140 Adding local entry inode=1407374883577140, filename=None
2012-05-01 07:57:12,829 47864:Worker-1        logging:1448 Exception while processing change FSChange(Direction.DOWNLOAD, Action.MODIFY, ino: 4785074604089055, rid: file:0ByQ0t4y3X2cHWTlhZ2dvUUhOX2s, parent ino: 1970324836998407, modified: 1335874744, checksum: 0ef24812cb1472ba3f0852123d88ad04)
IntegrityError: PRIMARY KEY must be unique
More info: Traceback (most recent call last):
  File "P:\p\agents\hpam2.eem\recipes\154662341\base\b\drb\googleclient\apps\webdrive_sync\windows\build\pyi.win32\main\outPYZ1.pyz/common.workers", line 138, in Process
  File "P:\p\agents\hpam2.eem\recipes\154662341\base\b\drb\googleclient\apps\webdrive_sync\windows\build\pyi.win32\main\outPYZ1.pyz/common.persistence_sqlite", line 125, in Wrapper
  File "P:\p\agents\hpam2.eem\recipes\154662341\base\b\drb\googleclient\apps\webdrive_sync\windows\build\pyi.win32\main\outPYZ1.pyz/common.workers", line 267, in _ProcessDownloads
  File "P:\p\agents\hpam2.eem\recipes\154662341\base\b\drb\googleclient\apps\webdrive_sync\windows\build\pyi.win32\main\outPYZ1.pyz/common.workers", line 624, in _DownloadModify
  File "P:\p\agents\hpam2.eem\recipes\154662341\base\b\drb\googleclient\apps\webdrive_sync\windows\build\pyi.win32\main\outPYZ1.pyz/common.workers", line 968, in _UpdateINodeNumber
  File "P:\p\agents\hpam2.eem\recipes\154662341\base\b\drb\googleclient\apps\webdrive_sync\windows\build\pyi.win32\main\outPYZ1.pyz/common.snapshot_sqlite", line 147, in AddLocalEntry
  File "P:\p\agents\hpam2.eem\recipes\154662341\base\b\drb\googleclient\apps\webdrive_sync\windows\build\pyi.win32\main\outPYZ1.pyz/common.sqlite_operations", line 136, in Insert
IntegrityError: PRIMARY KEY must be unique

2012-05-01 07:57:12,831 47864:Worker-1        logging:1473 Crash reporting disabled. Ignoring report.
2012-05-01 07:57:12,831 47864:Worker-1        logging:1448 Fatal error occurred: Traceback (most recent call last):
  File "P:\p\agents\hpam2.eem\recipes\154662341\base\b\drb\googleclient\apps\webdrive_sync\windows\build\pyi.win32\main\outPYZ1.pyz/common.workers", line 138, in Process
  File "P:\p\agents\hpam2.eem\recipes\154662341\base\b\drb\googleclient\apps\webdrive_sync\windows\build\pyi.win32\main\outPYZ1.pyz/common.persistence_sqlite", line 125, in Wrapper
  File "P:\p\agents\hpam2.eem\recipes\154662341\base\b\drb\googleclient\apps\webdrive_sync\windows\build\pyi.win32\main\outPYZ1.pyz/common.workers", line 267, in _ProcessDownloads
  File "P:\p\agents\hpam2.eem\recipes\154662341\base\b\drb\googleclient\apps\webdrive_sync\windows\build\pyi.win32\main\outPYZ1.pyz/common.workers", line 624, in _DownloadModify
  File "P:\p\agents\hpam2.eem\recipes\154662341\base\b\drb\googleclient\apps\webdrive_sync\windows\build\pyi.win32\main\outPYZ1.pyz/common.workers", line 968, in _UpdateINodeNumber
  File "P:\p\agents\hpam2.eem\recipes\154662341\base\b\drb\googleclient\apps\webdrive_sync\windows\build\pyi.win32\main\outPYZ1.pyz/common.snapshot_sqlite", line 147, in AddLocalEntry
  File "P:\p\agents\hpam2.eem\recipes\154662341\base\b\drb\googleclient\apps\webdrive_sync\windows\build\pyi.win32\main\outPYZ1.pyz/common.sqlite_operations", line 136, in Insert
IntegrityError: PRIMARY KEY must be unique

2012-05-01 07:57:13,631 47864:Worker-1        logging:1448 The following request has been blacklisted: FSChange(Direction.DOWNLOAD, Action.MODIFY, ino: 4785074604089055, rid: file:0ByQ0t4y3X2cHWTlhZ2dvUUhOX2s, parent ino: 1970324836998407, modified: 1335874744, checksum: 0ef24812cb1472ba3f0852123d88ad04)
2012-05-01 07:57:13,746 47864:Worker-1        logging:1473 Crash reporting disabled. Ignoring report.
2012-05-01 07:57:13,746 46516:LocalFSPoller   common.local_watcher:898 LocalFSPoller first pass started. Waiting for localWatcher to start watching.
2012-05-01 07:57:13,746 47864:Worker-1        logging:1448 Fatal error occurred: Traceback (most recent call last):
  File "P:\p\agents\hpam2.eem\recipes\154662341\base\b\drb\googleclient\apps\webdrive_sync\windows\build\pyi.win32\main\outPYZ1.pyz/common.sync_client_thread", line 157, in Run
  File "P:\p\agents\hpam2.eem\recipes\154662341\base\b\drb\googleclient\apps\webdrive_sync\windows\build\pyi.win32\main\outPYZ1.pyz/common.workers", line 110, in _RunInLoop
  File "P:\p\agents\hpam2.eem\recipes\154662341\base\b\drb\googleclient\apps\webdrive_sync\windows\build\pyi.win32\main\outPYZ1.pyz/common.workers", line 183, in Process
  File "P:\p\agents\hpam2.eem\recipes\154662341\base\b\drb\googleclient\apps\webdrive_sync\windows\build\pyi.win32\main\outPYZ1.pyz/common.fatal_exceptions", line 34, in CheckException
IntegrityError: PRIMARY KEY must be unique

2012-05-01 07:57:13,747 47864:Worker-1        logging:1448 Exception occurred in thread Worker-1: PRIMARY KEY must be unique. More info: Traceback (most recent call last):
  File "P:\p\agents\hpam2.eem\recipes\154662341\base\b\drb\googleclient\apps\webdrive_sync\windows\build\pyi.win32\main\outPYZ1.pyz/common.sync_client_thread", line 44, in run
  File "P:\p\agents\hpam2.eem\recipes\154662341\base\b\drb\googleclient\apps\webdrive_sync\windows\build\pyi.win32\main\outPYZ1.pyz/common.sync_client_thread", line 164, in Run
  File "P:\p\agents\hpam2.eem\recipes\154662341\base\b\drb\googleclient\apps\webdrive_sync\windows\build\pyi.win32\main\outPYZ1.pyz/common.fatal_exceptions", line 34, in CheckException
IntegrityError: PRIMARY KEY must be unique

2012-05-01 07:57:13,747 47864:Worker-1        logging:1473 Crash reporting disabled. Ignoring report.
2012-05-01 07:57:13,747 47864:Worker-1        logging:1448 notified exit condition <threading._Event object at 0x0478CBF0>
2012-05-01 07:57:13,773 47248:LocalWatcher    common.local_watcher:134 LocalWatcher is up.
2012-05-01 07:57:13,782 47252:EventAggregator logging:1473 EventAggregator run loop has terminated.
2012-05-01 07:57:13,798 47896:CloudWatcher    logging:1473 CloudWatcher run loop has terminated.
2012-05-01 07:57:13,812 46516:LocalFSPoller   common.local_watcher:907 Finished waiting for LocalWatcher.
2012-05-01 07:57:13,812 46516:LocalFSPoller   common.local_watcher:909 Starting a local disk scan.
2012-05-01 07:57:13,813 46516:LocalFSPoller   common.local_watcher:797 Ignoring file D:\Shop\Google Drive\desktop.ini
2012-05-01 07:57:14,308 47376:Thread-1        logging:1473 Sending file to Google C:\Users\MATTFO~1.MAC\AppData\Local\Google\Drive\sync_log.log
2012-05-01 07:57:14,318 46516:LocalFSPoller   common.local_watcher:936 Finished local disk scan.
2012-05-01 07:57:14,367 47792:CrashReportUploaderThread logging:1473 Thread suspended. Skipping crash reporting
2012-05-01 07:57:14,367 47528:Fetcher         logging:1473 Fetcher run loop has terminated.
2012-05-01 07:57:14,368 46516:LocalFSPoller   logging:1473 LocalFSPoller run loop has terminated.
2012-05-01 07:57:14,948 47208:Worker-2        logging:1473 Worker-2 run loop has terminated.
2012-05-01 07:57:14,950 42564:Worker-0        logging:1473 Worker-0 run loop has terminated.
2012-05-01 07:57:14,993 47608:ThreadMonitor   logging:1448 Threads are still alive: MainThread, Thread-1, ThreadMonitor
2012-05-01 07:57:14,993 47608:ThreadMonitor   logging:1448 Exiting due to critical failure: PRIMARY KEY must be unique
More info: None

2012-05-01 07:57:14,993 47608:ThreadMonitor   logging:1473 Crash reporting disabled. Ignoring report.
2012-05-01 07:57:14,993 47608:ThreadMonitor   logging:1448 GetErrorCode called but there wasn't anexception to handle: (None, None, None)
2012-05-01 07:57:16,651 47376:Thread-1        common.proxy_manager:106 Exception while auto resolving proxy.
ProxyInfoResolutionError: inner_error=(12180, 'WinHttpGetProxyForUrl', 'The Proxy Auto-configuration URL was not found.')
2012-05-01 07:57:16,864 47376:Thread-1        logging:1473 crash report uploaded:ed46136b61e0517a

Re: Google Drive PRIMARY KEY error Teddy.ind 5/1/12 6:43 AM
I tried creating an eclipse workspace in Google Drive and tested with a project.
Google Drive has been unable to keep up with the continuous creation of multiple versions!
I plan to switch on googledrivesync after closing Eclipse, so that files can be synced. They don't seem to be able to work together.

I guess Google engineers could use eclipse to stress test Google Drive. 
1. Move a small project to Google drive
2. Use refactoring to rename one widely used class file. 
3. Done! You have hundreds of files which have new versions to sync to Drive.
Re: Google Drive PRIMARY KEY error Shannon Poole 5/1/12 7:10 AM
I was also using a Google Drive folder as an eclipse workspace. It was working fine for a couple of days but then I started receiving errors. You're right it must have trouble keeping up with the built-in version control in eclipse.
Re: Google Drive PRIMARY KEY error eberdinis 5/1/12 9:20 PM
Same problem with PRIMARY KEY must be unique. Logging won't work either because I can't send the report unless the ERROR window is closed -- doing this closes the logging window as well.

I am also currently working on several eclipse projects that are in my google drive so that could be the problem.
Re: Google Drive PRIMARY KEY error gm10 5/2/12 5:12 AM
Same problem with PRIMARY KEY after sync has been completed. Was recommended to disconnect, which I did. Now I can't sign in 'coz Google Drive is expected to be empty.
Report ID 6A2E5291B8A0E599
Re: Google Drive PRIMARY KEY error Xero88 5/2/12 5:55 AM
Same for me, I'm using Eclipse too, the issue must come from this.
Re: Google Drive PRIMARY KEY error mathewfoster 5/2/12 6:18 AM
I am NOT using Eclipse and still getting this error.
Re: Google Drive PRIMARY KEY error fabianoo 5/2/12 12:30 PM
Same problem... and I do use Eclipse. Once I removed the workspace from Google Drive, it worked out.

Re: Google Drive PRIMARY KEY error cyc115 5/2/12 8:52 PM
so it's eclipse that's causing this problem ?!
Re: Google Drive PRIMARY KEY error mathewfoster 5/3/12 5:48 AM
Not exclusive to eclipse. I am not using eclipse. I have my google drive folder on my secondary partitioned hard drive and get this same error.
Re: Google Drive PRIMARY KEY error dertut 5/3/12 8:45 AM
Still the same Problem here with " PRIMARY KEY must be unique". I have some portable Apps in my shared space. Any Idea how to solve the problem?

best regards!


Re: Google Drive PRIMARY KEY error Papa Bear 5/3/12 9:19 AM
@mathewfoster

I see in your log:

2012-05-01 07:51:55,907 46420:Worker-2        common.proxy_manager:106 Exception while auto resolving proxy.
ProxyInfoResolutionError: inner_error=(12180, 'WinHttpGetProxyForUrl', 'The Proxy Auto-configuration URL was not found.')

Re: Google Drive PRIMARY KEY error gforsi 5/4/12 4:49 AM
Same here. I am using LiberKey with approx. 55.000 files. One app, for example is Chrome. 
Consequently, while using Chrome and Gdrive is active it trys to sync temporary files generated by Chrome. 
Some files cannot be synced, because they are locked. Anyway, I always get the Primary Key Error.
When disconnecting the account there is no way to set up google drive for the same directory again. Thus, I have to delete everything and set up google drive completely new. :(
Syncing takes more than one day Oo
Re: Google Drive PRIMARY KEY error edu67 5/5/12 2:41 AM
Same problem with W7 x64...
Re: Google Drive PRIMARY KEY error stephenm00 5/5/12 8:25 AM
Im getting this problem if I run Sickbeard on my google drive, if I take it out it works fine. 
Re: Google Drive PRIMARY KEY error Giorgi Shonia 5/6/12 6:03 PM
same error, w7 x64

very bumpy start on number of occasions. I'm out of this product, back to Dropbox
Re: Google Drive PRIMARY KEY error quads17 5/6/12 7:10 PM
Having the same problem when syncing a lot of pictures. hope this gets a resolutions soon...
Re: Google Drive PRIMARY KEY error haplessg00n 5/7/12 2:53 PM
I found a fix for eclipse at least. It was hitting a wall when trying to sync the recorded data usage files. For me these were located at 

F:\Google Drive\Workspace\.metadata\.plugins\org.eclipse.epp.usagedata.recording

I turned off data collection in eclipse and deleted the files in that directory and now it works fine :)
Re: Google Drive PRIMARY KEY error Saša Gošović 5/7/12 9:45 PM
Save problem here. Windows XP x86. It occurred when I backup files from synced folder (with backup software). Then I must leave account and sign again. So far it works ok. When I backup, i will shutdown sync.
Re: Google Drive PRIMARY KEY error ranger203 5/8/12 4:19 AM
Same here, I bought Google Drive to keep an online backup of my Pictures (~30 GB), and I just started syncing last night.  I moved all my pictures into the google drive folder and it crashed at 9% synced.
Re: Google Drive PRIMARY KEY error ScottTromley 5/8/12 6:22 AM
For what it's worth I got the same error in OS X after syncing like 135,000 files or so.
Re: Google Drive PRIMARY KEY error ohioguy67 5/11/12 6:46 AM
I am having the exact same problem with several large MS Excel files that are in my Drive whenever I save them after editing.  In my case, Excel creates temporary file(s) during the save process, those are getting uploaded and then deleted from the Drive, but something in the final steps of the save is causing the error (I think it's deleting the last temporary file since the updated spreadsheet appears to be correct when viewed on the web).  It's frustrating because the only way to fix the problem is to disconnect, rename the Google Drive folder on the local PC, reconnect and re-sync.  This hasn't happened on smaller files.
 
I did discover a workaround that if I "pause" Drive before saving and then re-enable it afterwards, this error doesn't happen (it will sync the changes after being re-enabled).
 
Re: Google Drive PRIMARY KEY error brianhaddock 5/11/12 9:47 AM
Getting the same "primary key must be unique" error here.  I am on Windows 7 64-bit.  Running Google Drive on 3 different computers and 2 Android devices.  Only one computer is experiencing the problem (my primary server).  It started after I moved a large folder on another machine and all change were synced back to the server.
Re: Google Drive PRIMARY KEY error Alrokayan 5/13/12 7:31 PM
Same issue here :(
Re: Google Drive PRIMARY KEY error will.j.richardson 5/14/12 9:11 AM
Does anyone know how often new releases will be released for google drive? Does it update itself or does it need to be downloaded again? I am getting this error too, I've uploaded 51 GB with 35 GB to go. I do not want to disconnect my account as I think I would have to re-upload all files and even then I'm not convinced the error will go away. I like the pricing on google drive but may have to switch to another solution if they can't fix this soon. 
Re: Google Drive PRIMARY KEY error pilottrent 5/14/12 9:24 AM
For myself, this has become a limiting factor in using Google Drive.   When I keep having google drive crash with the "primary key" error and the only solution being disconnect the account,  that doesn't work for me.   Uploading 25 gigs over and over again is not something I plan on doing every couple days because it keeps crashing.   If I had some comfort in knowing this might be fixed, I would try the product again because I would really like to keep using Google Drive!
Re: Google Drive PRIMARY KEY error wholeeo 5/14/12 2:03 PM
Hi folks,

Thanks for identifying this issue for us. We're investigating now and will circle back when we need more information. Please send us your Report ID if you haven't already done so.

Talk soon,
Julio
Re: Google Drive PRIMARY KEY error Chris Long 5/14/12 10:00 PM
Same problem (Windows 7 x64) - report ID: B5E3D07947930D62
Re: Google Drive PRIMARY KEY error simes1960 5/15/12 2:45 AM
I have the same problem - "Primary Key Must Be Unique".  The crash happens every time I start Google drive, sometimes almost immediately.  I suspect it is to do with duplicate or near-duplicate filenames.  Several new files are created in my local folder with [Conflict] added to the filename.  (After several attempts there are files with names [Conflict 1], [Conflict 2], and so on.)

I have tried to create a log as requested by Himanshu V but when Google Drive crashes, the crash report window appears and the log window is locked, so I cannot click 'Send Report to Google' and no Report ID is created.  When I close the crash report window, it also closes the log window so the chance to click the Send Report button is gone!  How can I send the report manually?
Re: Google Drive PRIMARY KEY error will.j.richardson 5/15/12 9:43 AM
Same problem (Windows 7 x64) - report ID: 578F214713CF2B98.  Google Drive version: 1.0.2975.8828
Re: Google Drive PRIMARY KEY error Chris Long 5/15/12 12:45 PM
If you click 'Disconnect Account' then the crash window should close without also closing the log report window, which then lets you click 'Send Report to Google'. (Of course disconnecting your account will mean you need to download all of your Google Drive files again when you re-connect it).
Re: Google Drive PRIMARY KEY error xlnja 5/15/12 9:58 PM
I moved the location of "My Documents" to Google Drive.  It contains over 30GB, and the entire folder synced to Google Drive without any problem a couple of weeks ago. However, in the last few days I started getting the PRIMARY KEY error.  For awhile I just ignored it, and the error would not appear for a day or so.  Today I got the error again and decided to disconnect Google Drive (big mistake!).  When I tried to reconnect it to my existing Google Drive folder, it said the folder was not empty (because it contains the "My Documents" folder). That means that I have to delete the "My Documents" folder and download the entire folder from Google Drive.

My main problem now is how to get the "My Documents" folder back into Google Drive and still have Windows recognize it as THE "My Documents" folder, not just a folder named "My Documents" (the "My Documents" folder has special properties). I have to delete all the folders in the Google Drive before I can reconnect the account. I'm not very happy about this. I am going to have to do a lot of file manipulation to make this work. Google Drive should always consider the files on the computer to be the main source and should not require you to download them again. When reconnecting the account, it should re-upload the files in the Google Drive folder and either replace those in the cloud or merge them. I was hoping by having the "My Documents" folder in Google Drive I would no longer need Carbonite online backup. I love Google's products, but this is a big problem. If they don't get this fixed soon, I will have to reconsider using Google Drive.
Re: Google Drive PRIMARY KEY error will.j.richardson 5/16/12 6:41 AM
Julio,

Do you have an update for us on this issue? I do not want to disconnect my account and I still can't synchronize the rest of the files I want too because of this error.

Thanks,
Will
Re: Google Drive PRIMARY KEY error Theleme 5/16/12 7:18 AM
no idea if this will help, but I always find after Quitting following a "Primary Key" failure that there is a file in the Google Drive PC folder with the same name as one recently saved but with " [conflict]" appended to the file name.  If I delete this from the PC before restarting Google Drive, it syncs OK again.

This has occurred particularly with MS Excel files (I have automatic saves on) but also with MS Word files (I have automatic saves switched on).

(Sadly) I am on a PC/Vista
Re: Google Drive PRIMARY KEY error will.j.richardson 5/16/12 9:23 AM
I removed the conflict files (I had 15 conflicts on the same file). Started and same error. I then removed conflict and the original file and it is synchronizing again. So after the files are done, I'll try that file again. 
Re: Google Drive PRIMARY KEY error echancrure 5/16/12 11:44 PM
Same here, and disconnected Google Drive as per pop up advice after primary error (which I think I did before with no problems) but the effect seems to have changed: I now have to download all my files again : 60812 of them.
In addition it did not sync my changes from yesterday, so I'll have to trawl through my files to see which ones are out of date ...

Not fun 
Re: Google Drive PRIMARY KEY error simes1960 5/17/12 2:07 AM
Thanks for the advice re. disconnecting the account to obtain the report id.  However I am trying to avoid the need to download all the files again because I have over 1Gb of them and am on a capped-download broadband plan!  So I hope others' reports ids will be sufficient.
Re: Google Drive PRIMARY KEY error Warwick H. 5/17/12 3:09 PM
Same issue here. On a Mac.  I seem to get the issue when using Autocad for Mac.  I have disconnected, downloaded again, and the problem continues. 
Re: Google Drive PRIMARY KEY error GooglePanda 5/19/12 11:19 AM
Same issue on Windows 7 Ultimate. Happened after trying to sync a small PDF
Re: Google Drive PRIMARY KEY error GooglePanda 5/19/12 11:24 AM
It has been a really long time and no fix yet... 
Re: Google Drive PRIMARY KEY error websea 5/19/12 10:49 PM
This application isn't stable enough. I'll use it when will be more mature. I was very enthusiastic when I found Google Drive App, because it seemed that is the solution to my multiple work pc's.
Re: Google Drive PRIMARY KEY error Brausmith 5/20/12 12:57 AM
Julio, there is no way to obtain a Report ID. I enter diagnostics mode and then start it, then when the error occurs it has focus and I can't submit the log.
This error for me occurs just after scanning the web when it says that the sync is complete.

And BTW, since I've only just uploaded all my files, there is no way at this stage that I am disconnecting to only have to re-sync the files back to the desktop. Google really need to fix the way it identifies existing docs. If they are the same as what is on the server, then they really shouldn't require re-syncing. The way it is is really bad functionality.
Re: Google Drive PRIMARY KEY error brianhaddock 5/20/12 8:06 AM
I'm seeing the same problem on Windows 7 64-bit.  I disconnected and redownloaded all files (almost 80GB worth - takes 2-3 days - ouch) and it worked ok for a few days and then started again.  I believe the last time it happened I was running Quicken (and I sync the Quicken directory).  Anyone else running Quicken?
Re: Google Drive PRIMARY KEY error GooglePanda 5/20/12 8:27 AM
This is how it happened to me and how I avoided the Disconnect.  - a matter of luck.

1. I hover over the Drive icon and noticed that it said two unsyncable files, click it, and choose to view those files. There were only two, and they were easy to remember. One was a PDF and another was a OneNote file.

2. On that window I told Drive to Try Again to sync the files. Soon after that, I got that message about the primary key. 

3. I quit Drive and tried again. Same error.

4. I googled about it. Landed here. A disconnect and to sync ALL those 23 GB of data!!! Not on my watch. I rather go back to GoDaddy's Online Folder.

5. I gave it a try to locate the PDF and delete it. Tried again. Same Error.

7. Second attempt, it gotta be the One Note File. Looked its Folder, found it. There were 4 types of the same file, 3 of them had an unusual name in brackets [] that I wish I could remember - I was in a hurry to leave and just deleted them and backed to my desktop the one without the brackets. Ah! Eureka I remember, it was [conflict]. Ch12[conflict].ont.

8. Run Google Drive again. Bliss, the thing synced and said sync was complete. Readded the PDF to its folder. Synced well. Opened the backed one Note filed, and saved As to its folder. Synced well. 

In conclusion, the OneNote filed was the culprit of my problem. I will suggest that you do a File Search of you whole Google Drive folder on "conflict" and see which one is the file, back it up, delete it, and command to sync, then add it.

OneNote is a compulsive program that saves often, I wonder if programs as such conflict with Google Drive. Maybe OneNote is trying to overwrite the file, but Google Drive creates a new one a duplicate or something, again and again and that leads to this "Primary Key" error. 

I hope it helps a bit. 



Re: Google Drive PRIMARY KEY error Brausmith 5/20/12 3:53 PM
Well done with those investigative skills!
As I read step 7 it struck me that I did something just before the error. So I went to the folder I suspected and I too had the same [conflict] named files. I tried deleting the conflict but it didn't work. So I went into the Preferences and unchecked the folder in question, restarted Drive and it un-synced. This time there was no error. So I checked that folder back on, and everything is now synced correctly, WITHOUT having to do a full re-sync of all folders which I had checked.

Google: You really need to provide more details with this error. This was easy fixed once knowing where the error was.

Thanks RedPanda! You saved me a ton of download data which I have almost maxed out for this month.
Re: Google Drive PRIMARY KEY error GooglePanda 5/20/12 4:06 PM
Glad to help. I do hope Google looks at what is causing these [conflict] files and a fix is found. :)
Re: Google Drive PRIMARY KEY error Ayush Sharma 5/21/12 10:08 AM
Here's another Report ID: 3A36470E9794D84B

Hope this helps. It seems to be happening when I have two computers signed in on the same Wi-Fi connection.

A
Re: Google Drive PRIMARY KEY error wholeeo 5/21/12 10:53 AM
Hi all,

I've reached out to some of you offline to grab more information. We're still working on a fix - will report back once we have more. Sorry about the trouble here, this should be resolved soon.

Best,
Julio
Re: Google Drive PRIMARY KEY error brianhaddock 5/23/12 6:16 PM
Found the problem on my scenario.  The OFXLOG.DAT Quicken files.  On my local machine they had unique names generated with (1), (2), etc. in the file name.  On Google Drive Web there were the same files with identical names (no (1), (2), etc. appended in the file name).  I deleted the files on my local machine and through Google Drive Web and it synced fine after that.  In Quicken, the OFXLOG.DAT files are created when you download transactions and I was able to safely delete them.  Problem is, Quicken recreates the file each time you download transactions so I have to shut down Google Drive when I'm using Quicken and delete the files when I'm done.
Re: Google Drive PRIMARY KEY error Doug T. 5/24/12 10:05 AM
This was exactly my problem as well.  Thanks!
Re: Google Drive PRIMARY KEY error xlnja 5/24/12 11:18 AM
Quicken appears to be a common culprit for this error.  I also had the same problem with the OFXLOG.DAT Quicken file.  That was the only file in my Google Drive folder that had a duplicate with the suffix, "[conflict]".  On Google Drive on the web, the file appears twice with the same OFXLOG.DAT name (i.e., without the suffix, "[conflict]").
Re: Google Drive PRIMARY KEY error echancrure 5/25/12 12:17 AM
Eclipse is the problem with me when my workspace is part of my Google Drive and I am working on it, PRIMARY KEY error is generated and I get conflict files in the .metadata folder such as:
.bak_0.log
.bak_0[Conflict 1].log
.bak_0[Conflict].log 

After closing the Drive client and restarting it the error was gone.

Re: Google Drive PRIMARY KEY error echancrure 5/25/12 12:21 AM
Update, the error is not gone ... it says the sync is complete but the pop up warning about Primary Key error is also generated and I have to close the client again.

As per previous posts, removing some of the conflict files will probably solve the problem...
Re: Google Drive PRIMARY KEY error juneeighteen 5/25/12 10:37 AM
Just to chime in - I too am seeing the same issue on a Server 2008 R2 64-bit machine, but only when using Eclipse IDE and my workspace is on the Google Drive.
Re: Google Drive PRIMARY KEY error the_roggy 5/26/12 9:34 AM
It's a pity this takes a rather long time to solve... while the solution seems easy (at first sight)... as there are 
1) reports of people having files renamed that contain brackets: everything between brackets is stripped
2) primary key errors...

Adding that up... if you have files with the same filename except for an additional piece added between brackets... you get 2 files with the same name in one folder... and you cannot have 2 files with the same name in a folder... 
And as in database teminology a primary key is a kind of index that is required to be unique... the circle is round.

So just solve the problem of pieces in filenames between brackets (both [...] and (...)) getting stripped... and this problem is solved for free as well...

But by just picking out one piece of info without knowing the impact on other pieces of the system it is always easy to find a solution... so probably there are some complications making it not so easy :-(...
Re: Google Drive PRIMARY KEY error DKnow 5/27/12 4:19 PM
I have the same problem. Pausing the drive before working with Excel files seems to successfully workaround the problem.

This problem and the error messages you get makes it impossible for me to recommend Google Drive to my less technical friends. (Otherwise, I'm loving the service, the price, and not having to worry about losing the 14.2 GB of files that I have on my Google Drive.)

Re: Google Drive PRIMARY KEY error TMZU 5/30/12 7:02 AM
I also have this problem on two different accounts for two different computers. I haven't even gotten to use it, it has this problem almost immediately. Disconnecting and reconnecting the account doesn't help like it suggests and causes trouble. The only thing that fixes it is deleted the [conflict] files it creates. No idea why it even needs to make those since both Google Drive's are used exclusively on one computer. Now I have a major problem in that it's started generating [conflict] files as soon as I start it so it immediately closes before I can even delete them!
Re: Google Drive PRIMARY KEY error manunkind 6/1/12 3:36 PM
Same issue here on Windows 7.  "An unknown issue occurred and Google Drive needs to quit. Error: PRIMARY KEY must be unique".  Today, it won't stay open at all.
Re: Google Drive PRIMARY KEY error @missedbeat 6/2/12 12:18 PM
I had the Primary Key error three weeks ago and have not been able to log back into Google Drive since. Whenever I try it believes I am trying to set-up a new account and ignores the 30GB already uploaded!

Peter H
Re: Google Drive PRIMARY KEY error stevenroose 6/2/12 2:04 PM
It seems to me that when I just click "Learn more" that Drive can sync along without problems :)
Re: Google Drive PRIMARY KEY error jseemann 6/3/12 6:11 AM
Add another one to the list.  Seems to happen about every other day.  A reboot usually resolves it, though once I had to disconnect and resync - an immensely frustrating process.  I too moved the location of "My Documents" to Google Drive.
Re: Google Drive PRIMARY KEY error Tobbev 6/5/12 8:24 AM
Same error here. Bought 100GB storage yesterday and I'm trying to upload my 20GB of Photos. Really really frustrating. Money down the drain?
Re: Google Drive PRIMARY KEY error DKnow 6/5/12 10:48 AM
I think the issue is fixed since Version 1.1.3019.0542 of Google Drive. I've had no crashes of the Drive software and no manual intervention to correct issues. I have seen a few spreadsheet files that were rapidly modified and saved cause some files to show the X icon temporarily, but it resolved itself.
Re: Google Drive PRIMARY KEY error @missedbeat 6/5/12 10:50 AM
I am afraid not, that is the version I a trying to use and have not been able to connect too since the 14th May!!

Peter H
Re: Google Drive PRIMARY KEY error gmailuser11 6/9/12 9:53 AM
hello,
same happens to me, 
i've found files with same name in google drive web folder, i've delete the duplicates and gdrive has returned to life.
PLEASE Google inc. DO something for the file naming,
thank you
Re: Google Drive PRIMARY KEY error baespey 6/9/12 3:08 PM
Thanks for the update Julio. I think you were the one working with me. I'm sorry I've been so frustrated, it's just that I've lost probably 50 hours of wasting time trying to troubleshoot, upload, redownload and it's just driving me crazy. I have about 95% of my 80GB uploaded, I just wish I could get past these latest crashes. This error keeps happening to me too. I love Google Drive and tell everyone about it, I just hope we don't have to redownload with the new fix. Oh and I keep e-mailing back so that I can aid in your troubleshooting. Anything us users can do to help, I know we'd be more than happy to. Nobody really wants to go back to Dropbox.
Re: Google Drive PRIMARY KEY error simes1960 6/11/12 12:47 AM
Has there been an update?  Where is it, please?
Re: Google Drive PRIMARY KEY error baespey 6/11/12 7:01 AM
There's not an update and probably won't be one for a few weeks. Google knows about it, I really think they just don't know how to fix it.
baespey 6/11/12 7:18 AM <This message has been deleted.>
Re: Google Drive PRIMARY KEY error baespey 6/11/12 7:19 AM
The same kept happening to me and I could actually replicate it. The main problem, I believe, is it can't upload due to a duplicate file. The key is to find that file and get to it before it crashes. Because if it crashes, you can't see what files couldn't sync. I tried to wait till it finished doing the initial scan of the web and my files and start uploading files, but it took a few tries. Eventually though, I was able to right click Google Drive and see it said, "1 unsyncable file." The moment I clicked it, it crashed. So I got it just in time (it might take a few times). I saw it was a bookmark file and I just put that off to the side and deleted it from Google Drive. Turns out, it did sync twice and there were two of those folders on my Google Drive web. That was what fixed it for me.
Re: Google Drive PRIMARY KEY error EvilMoe 6/18/12 12:52 PM
I have the same problem. Any solution?
Re: Google Drive PRIMARY KEY error baespey 6/18/12 1:29 PM
There's no solution. Google knows about it, but it will be a few weeks before anything is fixed. It's typically due to a duplicate file. If you read my last post, that should help you in at least identifying the troubled file. Get that out of there and continue syncing.
Re: Google Drive PRIMARY KEY error stephenm00 6/18/12 6:44 PM
Actually I had this problem fairly frequently but haven't gotten it since I upgraded to Google Drive 1.2.3101.4994. 
Re: Google Drive PRIMARY KEY error roeygoro 6/18/12 9:55 PM
Google! Please help!
Re: Google Drive PRIMARY KEY error wholeeo 6/19/12 6:09 AM
Hey folks, 

Thanks for your continued patience here. We're still debugging the issue and are attempting a fix. I will report back once we know more. 

Talk soon, 
Julio
Re: Google Drive PRIMARY KEY error baespey 6/19/12 6:58 AM
Yes Google's aware of it, but give them time. Keep in mind, Google Drive is still in it's initial stage of deployment. Just because Dropbox and SkyDrive don't have a primary key error doesn't mean they never did. They have years ahead of Google. But I have full confidence their staff is hard at work on this. Google does care more than you think. Just give them time.
Re: Google Drive PRIMARY KEY error georgiecasey 6/19/12 8:54 AM
Agreed, I came here to rant about this problem but 300megs has just successfully synced as of version 1.2.3101.4994.
Re: Google Drive PRIMARY KEY error Online Department 6/28/12 2:52 AM
Same problem here in our office. We use drive on our Google Apps account with 6 users. The same message appears on multiple accounts / computers. Since we don't have a local server we really need this issue to be solved as soon as possible. My partners are already thinking about moving back to dropbox.
Re: Google Drive PRIMARY KEY error OC_Com 6/30/12 5:31 AM
Google Drive crashes about 20 times a work day.
Still waiting for a solution.

Re: Google Drive PRIMARY KEY error GooglePanda 6/30/12 3:53 PM
Ugh! My laptop now has the issue... This is getting old. I'm really getting tired of Google slow response to everything. Everything feels beta. Seriously, Android fragmentation and need to rely on a community online who resorts to tell you to install custom ROMs is what has my attention and my business needs toward Apple's iPhone.

I think for the price, Office365 Enterprise looks much better now. Never had such an issue with them. 
Re: Google Drive PRIMARY KEY error FairfaxITC 7/3/12 5:51 AM
Same story for me. I have a Win 7 x64 professional pc. I get the "primary key must be unique" error periodically. I'm not positive, but I think that it could be my Quickbooks data file that snags it up. I keep the quickbooks files in my sync folder. Seems to happen after doing a lot of work in Quickbooks.

Note: I tried to send in my log reports, but by the time i actually get the error the whole program crashes and I can't actually send it in. I found and attached my log file.

Thanks and let me know if I can provide more useful information.
Re: Google Drive PRIMARY KEY error JJBaker85 7/3/12 6:18 PM
I have the same problem. Please fix, it has been over 2 months.
Re: Google Drive PRIMARY KEY error Adnan Doric 7/4/12 3:28 AM
same issue here...
Re: Google Drive PRIMARY KEY error websea 7/4/12 7:30 AM
Is Google drive Support alive?
Re: Google Drive PRIMARY KEY error bobby ballow 7/6/12 1:33 PM
Same for me. You should add a "beta" to this product because since it was launch I encounter bug and bug and bug ...
Re: Google Drive PRIMARY KEY error stan_elie 7/7/12 7:24 PM
Same for me, it keeps crashing on me.
Re: Google Drive PRIMARY KEY error dlinford 7/10/12 9:34 AM
I get this week every week or so.  With 100 Gigabytes of data to sync the resetup and resync process takes more than a day.  Then I have to track making sure the most up to date files or include in the new Google Drive folder from the Old Google Drive.  This resyncing process is unacceptable.  Has anyone found a solution.  Hurry.

David
Re: Google Drive PRIMARY KEY error xlnja 7/10/12 10:23 AM
David, some others have posted the workaround earlier in this thread, but essentially there are duplicate files in the Google Drive on the web that cause the crash.  You must search for and remove the files with the suffix, "[Conflict]", attached to the end of the file name from the Google Drive folder on the computer and then also delete the related duplicate file on Google Drive on the web.  Restart Google Drive, and everything should sync fine.  If not, also move the original file out of the Google Drive folder and then back again.  I know this is annoying, but it has worked for me.  The issue appears to affect files that are quickly updated on the computer, not giving Google Drive time to sync them.  Quicken files are commonly affected.  What I do now is pause Google Drive when I open Quicken and then resume when I am finished.

--Dan
Re: Google Drive PRIMARY KEY error bobby ballow 7/10/12 10:39 AM
This is not an acceptable solution. Google should consider to hire good developpers, not noobs. This product was launched too soon. For example, solutions like insync work better.
Re: Google Drive PRIMARY KEY error fedetipito 7/10/12 6:49 PM
Yo también tengo el mismo error. Ya me pasó unas 5 veces en los últimos dos meses. Y sincronizar toda la información otra vez lleva mucho mucho tiempo.
Además estaría bueno que soporte FAT32 además de NTFS, porque esta limitación me ha causado varios problemas, y me imagino que no debo ser el único.

Espero que saquen una actualización pronto  que corrija los errores..
Re: Google Drive PRIMARY KEY error Wedgen 7/10/12 8:41 PM
any update?! I just got this error today. 

I couldn't send the report cause the app crashes before i can click submit.
Re: Google Drive PRIMARY KEY error b2h2caldwell 7/11/12 5:05 AM
Getting the same error on Windows 7 with 11,000+/- files.

Any update Google?
Re: Google Drive PRIMARY KEY error sawright 7/11/12 7:27 AM
This is exactly what I figured out. It worked out. not an easy fix, but MUCH better than restarting the whole sync process again
Re: Google Drive PRIMARY KEY error bobby ballow 7/11/12 3:52 PM
Wow so first post is 27 April... 

Ok 3 month and no solution... It's a new record from Google!!! Maybe Google should ask Dropbox how to fix it XD
Re: Google Drive PRIMARY KEY error Arrabiata 7/14/12 12:02 PM
 I cannot get a log file out of the crash.  I cannot even send a report to google because both crash.  Very frustrating. I have removed all of the files that it lists as having to sync, but still it crashes.  The desktop.ini file in the google drive folder keeps reappearing on start up even after I delete it and it has the sync symbol every single time.  Don't know if that is the cause. 
Re: Google Drive PRIMARY KEY error Teresa - Docs & Drive Community Manager 7/19/12 11:30 AM
Hi everyone - thank you for your continued patience. We're still working on a fix for this and will keep you in the loop about any new updates.
Re: Google Drive PRIMARY KEY error Arrabiata 7/19/12 6:55 PM
Perhaps you fired the last engineer that was working on this problem?  That would be helpful.  I think I am going to ditch google drive if this problem is not fixed by next week.  The time frame to fix an issue is incredible and negligent.  This product was not ready for public use.
Re: Google Drive PRIMARY KEY error Shannon Poole 7/20/12 6:46 AM
Thanks Teresa. 

If it helps, I find that the issue really only happens when I use when I use Drive on multiple machines and accounts sharing the same folder. In my case I am using Drive for my eclipse workspace folder. So while I am at work I am using my Google Apps account. If I have to work from home on occasion I use my personal account which has the same folder shared with it. The problem hasn't come up in a couple of days and I haven't worked from home so it might be related. I think it might have to do with the permissions and owners of a file when it's created. For example if I am using my personal account the files are created with my personal account as the owner even though the original folder is owned by my Apps account. So while eclipse is writing log files or indexes and what not it may delete one and start another but since it was owned by the other account it doesn't update on the other end fast enough and creates a conflict of the same file name but two different owners. I think its pretty clear that the [conflict] files are the reason for the crash and I just do a search on the folder and delete all files with [conflict]. Restart Drive. Sometimes it takes a rinse and repeat but after 1-3 times it usually works itself out.

I'm no Google Engineer, just figured I would give some input. 
Re: Google Drive PRIMARY KEY error Giorgi Shonia 7/22/12 6:01 PM
been trying to downgrade drive account for weeks now. 
first it was over the free limit and took 24 hours after deleting files to update the quota info.
now there is problem with wallet. 
not to say that primary key problem has been hanging around for three month now.

honestly, google is microsoft of 2010s'. those guys (MS), at least they could charge my credit card. 
Re: Google Drive PRIMARY KEY error jos_osc 7/23/12 11:39 AM
Thanks Teresa, also waiting for a solution for this. To me it happened after renaming a lot of files using Adobe Lightroom.
Re: Google Drive PRIMARY KEY error klnjbh 7/23/12 1:19 PM
Same issue....awaiting a solution!
Re: Google Drive PRIMARY KEY error jmrodriguez 7/23/12 3:18 PM
He encontrado una solución para mi caso (50.000 archivos más o menos). El problema es que hay algunos archivos duplicados en el mismo directorio y eso no es normal y a Google Drive no le gusta.

He buscado y eliminado los archivos duplicados. Para ello he utilizado la aplicación DuplicateCleaner. He buscado los archivos duplicados y luego he ordenado por directorio. De esa manera he encontrado los archivos duplicados en el mismo directorio.

Los he borrado, he vuelto a sincronizar y he solucionado el problema.

Saludos.

---------------------------------------

I found a solution for my case (about 50,000 files). The problem is there are some duplicate files in the same directory and that is not normal and does not like Google Drive.

I have searched and removed duplicate files. For this I used the application DuplicateCleaner. I searched for duplicate files and then I ordered by directory column. Then, I have found duplicate files in the same directory.

I have deleted, resynchronized and the problem has been resolved.

Greetings.
Re: Google Drive PRIMARY KEY error .ZiP 7/24/12 1:02 AM
I have the same problems ( primary key and sync speed ) but without the huge CPU usage and huge memory usage though it constantly uses ~160MB of memory.
Another thing I came across is that when you have unsyncable files ( that for example can be temporary lock files or files that "point to an invalid online Google Doc" ) you can't skip or skip all and GDrive keeps on trying to sync those files. So this would be another thing to consider adding as the LAN sync which would ( in my opinion ) reduce the load on your servers thus leaving more bandwidth for other users to sync files faster.
Good luck with your work, you have a lot of things to do.
Re: Google Drive PRIMARY KEY error .ZiP 7/24/12 1:17 AM
I forgot to mention that i use Version 1.2.3123.0250 on Win7 Home Premium - I7 quad core
Re: Google Drive PRIMARY KEY error allmoney.ws 7/24/12 7:43 AM
Why you so long fix this bug? 2 months left :(
Re: Google Drive PRIMARY KEY error bobby ballow 7/24/12 7:56 AM
Because unfortunatly it's not the only bug. Drive is a big bug :D

I switch to another solution. I will wait at least one year that users debug it and developpers finish code it...
Re: Google Drive PRIMARY KEY error mn4gd 7/24/12 12:14 PM
I had this exact same problem. I figured (using sync_log from %appdata%  >  /local/google/drive ) this happened because of a folder created by reference/citation manager software called Zotero. Zotero creates and modifies lots of files in that folder. I removed the Zotero database folder and syncing process worked fine without disconnecting and re-syncing. Then I put the zotero folder and synced it without any problem.
Re: Google Drive PRIMARY KEY error jos_osc 7/25/12 12:16 PM
While waiting for the official fix, you can work-around the problem like this:
  1. Start the Google Drive client.
  2. Hold Shift, right-click on the task bar icon.
  3. Select "Enable diagnostics mode".
  4. Click "Start logging".
  5. Wait until it crashes. You won't be able to send an error report to Google because it's not possible to focus that window when the crash popup is shown.
  6. Go to Computer. In the "address" field, enter %APPDATA%, click Enter.
  7. Go up one step, so you're located outside the "Roaming" folder. 
  8. Enter the "Local" > "Google" > "Drive" folder.
  9. Open "sync_log.log" in notepad (or another text editor).
  10. Look for any file from your Google Drive folders, any file you recognize. When you find one, move them outside the Google Drive folder temporarly (to a location not synced by Google Drive).
  11. Start the crashed Google Drive client again.
  12. If is still crashes, redo the same procedure.
When I did this a few times, it stopped crashing. I then put the problematic files and folders back inside my Google Drive directory, and everything was well again. Until next time that is ;)
Re: Google Drive PRIMARY KEY error imoatama 7/26/12 7:37 AM
For me it was a file with the same name except an extra tilde. Given this is the default location that GVim stores its auto-recover file, this is going to be an big problem for me if there are primary key collisions for file names that differ only by ~.

Please fix this already Google!
Re: Google Drive PRIMARY KEY error nonorganic 7/27/12 3:57 PM
This one worked for me. I have the problem working with a Visual Studio 2010 solution inside the Google Drive folder.
Re: Google Drive PRIMARY KEY error Steffen Laursen 7/28/12 10:29 AM
Second that. I too have been using google drive with an eclipse workspace, causing this dreaded error to occur. 
Re: Google Drive PRIMARY KEY error Jorek 7/30/12 2:31 AM
Thank you! This helped much. I had duplicates to remove from the Web.
Re: Google Drive PRIMARY KEY error ChristianVolkmer 7/30/12 8:20 AM
The same under OSX 10.8. 
On nearly every mac in our office.
@Google: Please do something about drive: Very very slow and full of problems!
Re: Google Drive PRIMARY KEY error MattLeese 7/30/12 8:39 PM
Repord ID: CDDB3290122CAC7F

I'm highly frustrated with this because I've got 50 gigs of work files that I have to re-download :(  This combined with another issue is making me give Google Drive a bit of a lower rating now... Please fix this stuff, Google!
Re: Google Drive PRIMARY KEY error bobby ballow 7/31/12 12:40 AM
It's funny when I redownload my 60gigs of files they are binary different from original. I compare backup folder before send and gg drive folder with winmerge...
Re: Google Drive PRIMARY KEY error JoeTextilis 8/3/12 3:52 AM
I have the same problem
Re: Google Drive PRIMARY KEY error SHBlende 8/3/12 12:13 PM
I have the same problem on Win7 64-bit. Report ID is 05428E7987C10206.

Steve
Re: Google Drive PRIMARY KEY error dlange 8/3/12 3:10 PM
Hi, wanted to give Google Drive another try (after the bad start I had with it after the release). And even after having known of this issue for three months, it still persists. Is there any update, or any information on when we can count on a fix for this?
Re: Google Drive PRIMARY KEY error Stan Shaw Vancouver 8/8/12 5:53 AM
Thanks, this was a great help. My problem was identical to yours., and yes, once I found files in conflict, the fix was easy. The error message, and suggestion to disconnect Google Drive and re-synch the entire account without investigating this simple solution seems too drastic.
Re: Google Drive PRIMARY KEY error Warun Kietduriyakul 8/8/12 10:23 PM
Report ID: FBD7E1E066BB3FCF

Have the same problem in difference machines. I have 3 laptop synchonized.
Re: Google Drive PRIMARY KEY error spengilley 8/9/12 4:06 AM
I also have had this problem for some time. At the moment I am using dropbox... Would like to use google drive though!
Re: Google Drive PRIMARY KEY error superettepierre 8/11/12 12:21 AM
I'm having the same problem since I've started to upload big photo files (>100 MB). When I restart the drive it continues uploading, but it's saying that it's uploading over a 100 files when they should have been uploaded before.
Re: Google Drive PRIMARY KEY error superettepierre 8/11/12 12:24 AM
I'm using Mac OS 10.7.4 by the way.
Re: Google Drive PRIMARY KEY error .ZiP 8/11/12 12:43 AM
I've been using premium GD for a month now and had tons of problems so two days ago I said enough is enough and I started using Dropbox. It took me less then 7h to upload everything I had on GD ( ~14GB mostly really small files ) while on GD took two full days o_O .
I will cancel my subscription as soon as the files will get deleted from the GD servers because even that is slow :/ .
BIG disappointment.
Re: Google Drive PRIMARY KEY error MrUpss 8/11/12 9:50 AM
it is certain that they do duplicate files in GD! Today I deleted the duplicate files on GD and synchronization working again.
Duplicate files I deleted by the application Syncovery 6.03, which can also serve as an alternative application of GD. (translate by google translate - srry for my English) :)
Re: Google Drive PRIMARY KEY error Jose Cordovilla 8/15/12 5:00 AM
I have the same problem, as well as the occasional overheating nightmare from loop syncing.
Anyone out there at Google? We need help on this.
Re: Google Drive PRIMARY KEY error RockAndRollBot 8/15/12 9:28 AM
I tried enabling logging, but the app crashes and forces me to quit, which makes it so I cannot send the log file or get an issue ID.  I cannot attach my zipped log file since it is too large.  Is there an address I can send it to?
Re: Google Drive PRIMARY KEY error triac 8/15/12 1:12 PM
Same here for months now.
That's it. Screw Drive. What's the point of cheap prices if it's unable to do what it's supposed to do?
And it's not even the only problem with it. The whole ting is just a huge pain.
Re: Google Drive PRIMARY KEY error ChristianVolkmer 8/15/12 1:42 PM
I am truly shocked that Google gives a sh*t about their users and didn't even answer for months.
We switched new to google apps for your domain and are thinking about canceling everything as the
support for drive is a total desaster. I would fire the complete drive team! What a shame for google!
Re: Google Drive PRIMARY KEY error Oliver Hamilton 8/22/12 9:29 AM
I'm using it for Visual Studio 2010 projects on W7 x64 and I'm getting the same error.

I have recently upgraded to the 100GB package and would love to know it was worth it.

Please Google, can you indicated when a fix might be in place?
Re: Google Drive PRIMARY KEY error Brian the Fisher 8/22/12 1:34 PM
How were you able to generate this log? When I get the primary key error it kills my diagnostic mode.
Re: Google Drive PRIMARY KEY error KlemensP 8/28/12 11:11 AM
This problem is now known for 4 months and there neither a solution nor a proof that google is really working on this issue.
I have this problem twice a week and I think it's really time now to leave google drive. I can't stand it any longer to empty my drive folder twice a week and then start that very slow upload procedure again. Every time I do this, google drive tells me I'm using two or three times more than my real data usage.
Even if it's a free service it should be working fine - like others offer.
Thanks
Re: Google Drive PRIMARY KEY error MachielBrink 9/5/12 1:27 AM
Seems google is doing nothing with all their problems with duplicate files and Primary key issue. There should come a usefull statement from google very soon(this week). If there's no info then I'm going to transfer my files to dropbox. This just doesn't work. Back to the 5 GB free part.
P Root 9/12/12 10:29 AM <This message has been deleted.>
Re: Google Drive PRIMARY KEY error P Root 9/12/12 11:04 AM
The only time I get this error is if I am compiling Latex docs too frequently.  It would appear that GD cannot keep up with syncs if I compile twice within 5 secs of each other (each compile creates ~5 log files).  If I don't compile as frequently, GD never hiccups.  I tend to pause GD when I am making numerous revisions and then let it sync before I leave for the day.  It is the best hack I can find for now.
Re: Google Drive PRIMARY KEY error MachielBrink 9/19/12 6:16 AM
Following my post on the 5th of september, I've just stopped my google storage payments.
There's no service from this Google Group, nor there Google+ profile nor any other way.
Besides that this problem is allready half a year old.

Because Google is absolutely not being clear about when and if it ever will be solved I switched to dropbox.
Yes it's double the price, but my docs are more secure over there.
Lost a few because of these very annoying errors.

Thanks google drive developers and support center for a great product
Re: Google Drive PRIMARY KEY error MattLeese 9/19/12 6:22 AM
Yeah, after having watched this forum full of other annoyed customers for a few months now with not even a single comment from Google, I have also switched back to Dropbox and honestly don't regret anything. I'd rather pay a little bit more for reliability and the peace of mind that the files I create for my business are safe. 

Sorry Google, but you should be ashamed of your lack of customer service. 
Re: Google Drive PRIMARY KEY error oldranger 9/21/12 7:26 AM
Win 7, 64 bit.  The only things I save are standard documents, video and images.  Had this issue before so I resynced.  Took all night because I have a lot of files.  Solved the problem for a month, now it's back. I started paying for expanded storage a month ago, please help me correct this asap.  I don't have time to resync constantly.  Considering going back to Dropbox.
Re: Google Drive PRIMARY KEY error Robert Spitz 9/24/12 2:24 PM
My problem did not occur from the amount of time that I used Quickbooks, but rather from when I did a backup of my Quickbooks company data on my Google Drive. When Quickbooks does a backup it saves a couple of files with the same name, but they add either (1) or [1] to the name (I'm not sure which). Google Drive doesn't seem to be able to distinguish the file names, but has no problem after I rename one of them.I wonder if other programs have similar file naming conventions that cause a similar problem.
Re: Google Drive PRIMARY KEY error adioguardi 10/2/12 2:04 PM
Same happens to me intermittently upon compiling latex code. It usually happens if I compile the same tex file more than once in rapid succession.
Re: Google Drive PRIMARY KEY error Jim Emlet 10/5/12 5:51 PM
Is there a resolution to this yet?  I've disconnected my google drive when I received the primary key error and now I cannot reconnect it properly.  For a paid service if this has not been resolved, it shouldn't cost anything.
Re: Google Drive PRIMARY KEY error Andi Nunez 10/6/12 1:30 PM
I don't know if it's pertinent, and I don't have the knowledge of these things to back this up, but I have some clues that relate to my own experience with this error:

1) On my computer, I use SRWare Iron Portable for personal stuf, I use Chrome for work stuf. These are open most of the time, together, with never any problems. For the pages/forms/buttons that won't work with Chrome, I keep IE7 on board, but only open when I need it, and always log out of whatever account it's logged into before I close it.

2) Iron Portable and Chrome are logged into two different accounts, and I've never had any issue....ever. Until....I didn't log out of whatever Google account I had IE logged into before closing the browser.  This is when my own "Primary Key" problems started.  

Suddenly, Two separate names cannot be logged into Iron Portable & Chrome. The Primary Key error comes right up as soon at it senses two different names.  

Why? My version of Iron resides on a flash drive and shouldn't interfere with passwords and tokens and stuf.

Also, I notice that when it's time to log back into Drive, it uses an IE window, not a Chrome window. Why wouldn't it "go native" and use it's own Google products?  

I might be babbling, and I hope there's something here that can give someone, anyone a hint.  I'd definitely like to get this problem solved.

But as long as I'm only logged into one Google account in one browser, all is well.
Re: Google Drive PRIMARY KEY error David-M 10/13/12 7:57 PM
Google Drive was working fine until I purchased storage and moved more files onto it.  Now I get this error every time I re-start Google Drive...which makes it impossible to send the requested log because GD crashes and takes down the log window with it.  Here's an interim log ID A0AF4E4A50CDD4E6 .  GD hadn't crashed yet, but it did  minute or two later.

I don't use Eclipse or any constantly versioning development environment.

I see that this bug has been unfixed for 6 months.  Is there any hope of it being fixed?  Soon?  Disconnecting and-resyncing is not practical with 105 GB of storage as doing so would blow through my ISP's bandwidth limit and leave me with no internet connection whatsoever.

Google, please give us a status update.  Thanks.
Re: Google Drive PRIMARY KEY error Patrick Bryant 10/16/12 11:02 AM
Please copy me in on this fix.  I have been getting the PRIMARY KEY error for a while now.  I could not even get a log b/c once the error comes the logging box is unavailable.  I can't even get to step 5 above "When you’re done, click Send report to Google."

Please help!

Thx
Re: Google Drive PRIMARY KEY error Nyan - Support 10/16/12 12:54 PM
Hi,

Here are some troubleshooting steps you can take on your own to address the majority of primary key errors.

If your Google Drive app quits unexpectedly and displays ‘Primary key error’, please first exit the desktop Drive application.
1. Go into your ‘Google Drive’ folder.
2. Search for any files with a [Conflict] tag next to the filename.

3. Remove all copies of the file including the original file without the [Conflict] tag out of the ‘Google Drive’ folder.
4. Log into your web Drive at drive.google.com.
5. Repeat step 3 for your web Drive.
6. Download and reinstall the latest version of Drive for desktop. You do not need to disconnect.
https://tools.google.com/dlpage/drive?hl=en_US#eula
7. Start up your Drive app and continue syncing.
8. Once sync completes, place only one copy of the removed file(s) into your ‘Google Drive’ folder. You may delete the copies.

As rlsayre mentioned, symbols and characters in parentheses ( ) or brackets [ ] may not be preserved during the sync process. When this occurs, you result in multiple files with the same filename but different unique identifiers - the primary key value for a given database table.
Re: Google Drive PRIMARY KEY error Mutt978 10/20/12 10:41 AM
Perhaps Google should fix the problem instead of expecting their paying customers to search for files that are conflicting.  You know there's a problem.  It only happens with Google Drive.  The programs work fine outside of Google.  This has gone on long enough.
Re: Google Drive PRIMARY KEY error Niels Rot 10/22/12 12:28 AM
I've tried the suggested fixes, but it doesn't work. The only thing that works for a couple of days is to decouple the account and download all files anew. After some days the error comes again, and I can start all over again. This is a major nuisance as I use google drive for my start-up with my team and we keep having to sync files anew.

If this problem isn't solved soon, I might go back to Dropbox. Many thanks for taking it up and providing us with a solid fix. 
Re: Google Drive PRIMARY KEY error MachielBrink 10/22/12 12:48 AM
I've tried Nyan's solution with the Free version of Google Drive(i've stopped paying for a service which doesn't work) but after a few days the same error keeps coming.

If you can't use parentheses and brackets with filenames we shouldn't fix the names but google should fix their Google Drive.
When Dropbox, Sugarsync and perhaps also other fileservices can work with all kind of files and filenames Google Drive should do that too.

I'm still waiting for a permantely working fix. Perhaps I will come back to Google Drive's payed version by then.
Re: Google Drive PRIMARY KEY error baxcanna 10/27/12 6:37 AM
Please tell us when an actual fix is implemented.
Re: Google Drive PRIMARY KEY error Luizsalomon 10/28/12 4:27 AM
Hey there Nyan.
Tell me a little more about this [Conflict] tag.
I opened up Windows Explorer and made a search on my Google Drive for the word "conflict".
In my case, I had 47 occurences, but none of my files had the word "Conflict" or a [Conflict] tag in front of the filename.
Is that what you suggested? Should I look for a file called "xxxxxx[Conflict].txt" or "whatever[Conflict].doc"??

Thanks,
Luiz




Re: Google Drive PRIMARY KEY error MrUpss 11/1/12 4:48 AM
I strated to use for syncing my Google drive account Syncovery application (http://www.syncovery.com/). This app. have a funkcion - "delete duplicates file names" and this funkcion prevent this problem. I use it for a half year withou any problem. I recomend it!

As i see the google drive sync app will never fix this problem. It´s a waste of time to wait for a fix, i think..
Re: Google Drive PRIMARY KEY error qhawk 11/4/12 10:42 AM
I can't do step #5 "Click Send report to Google" because as soon as I close the error dialog, Drive exits.  Where is the log file stored?  
Re: Google Drive PRIMARY KEY error nadworksnet 11/5/12 1:05 PM
What a pile of junk. This "error: primary key must be unique" keeps coming up every once in a while and my storage of >100GB is not "re-connectable" that easily. I am also unable to search for duplicate files or get a clue from the sync_log either.

Google, this sucks massively. Months with this issue and no solution? This is not cloud storing, this is rubbish!
Re: Google Drive PRIMARY KEY error DonAIM 11/6/12 10:12 AM
I too am receiving the primary key error on multiple machines. Searching through multiple forums, this has been a known issue for months. If anyone has found a fix, (not a workaround), please let us know? I have 22 users and restarting machines, nuking, reinstalling, etc is not an answer.

Please note that Avatar Investment Management email and website domains are AvatarInvMgmt.com

 

This communication is from Momentum Investment Partners, LLC, d/b/a/ Avatar Investment Management, an SEC-registered investment advisor. Information and use of materials contained in this email, including text and attachments, is confidential and is for the use of the intended recipient(s) only. All original Avatar materials are the property of Avatar and are protected by U.S. Copyright Laws. They are not to be reproduced without permission. They are not to copyright protected. If received in error, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please reply to the sender and delete the original message and any copy of it from your systems. . 

 

Be also advised that email communications are not secure. All e-mail sent to or from this address will be recorded by Avatar's email system and is subject to archival, monitoring, and inspection by Avatar and the SEC. Please direct any matters regarding this policy to compliance@avatarinvmgmt.com.

Re: Google Drive PRIMARY KEY error Nyan - Support 11/8/12 7:04 AM
Hi Lulz, 
Yes, those are what I'm referring to. 
Re: Google Drive PRIMARY KEY error Nyan - Support 11/8/12 7:05 AM
The log file is stored in the local appdata folder. You can also search in the Help Center for Drive to look up how to submit an error report from Cmd prompt.
Re: Google Drive PRIMARY KEY error Nyan - Support 11/8/12 7:07 AM
The latest update of Drive addressed a large number of causes of the primary key error. However, if you're still encountering them and the above troubleshooting steps did not work for you, you can submit a ticket to Drive Support to have one of our specialists try to diagnose the issue. 

In the meantime, make sure to submit an error report to Google. Engineering will need the data in order to address it in future updates. Thanks.
Re: Google Drive PRIMARY KEY error baxcanna 11/14/12 11:15 PM
Did it address the number 1 problem? That the files are not detected that we would have to waste hundreds of gigabytes unnecessarily downloading every file again, even though they are still residing on the drive?
Until you answer this question I cannot proceed with this service.
Re: Google Drive PRIMARY KEY error keisar 11/29/12 5:23 AM
Maybe this will help some of you, I had problems finding the conflicted files and this helped me
I started the diagnostics mode by Shift + right click on the Google Drive tray icon, I opened the log file in AppData\Local\Google\Drive\sync_log.log
look for the Primary key error and you will see the conflicted file, now follow the instructions Nyan wrote before...

I have to say that Google is quite disappointing here:
1. Why doesn't Google drive let me know what is the conflicted file so I can work it out, why do I need to search for a word or look at logs !?
2. On my computer the locale is set to Hebrew so instead of searching for [Conflict] I should have searched for the word in Hebrew - I think you should have mentioned that (if you did and I missed it - I apologize)
3. This is a really stupid thing but I can't send you the error report because Google Drive crashes before I can click on the "Send Report to google" button at the diagnostics screen - You really should have tested this...

Also telling people to download their files again is ridicules, I have uploaded 100GB, downloading it again is not an option...

I hope you will fix these issues quickly, I have to say that currently the only advantage you hold against Dropbox is that your Sharing Model is much more fair than Dropbox's, if Dropbox would to change their sharing model to yours I would have transferred all of my files in a heartbeat...

Eran.
Re: Google Drive PRIMARY KEY error qhawk 11/29/12 2:57 PM
Awesome.  I has the same *STUPID* issue: "Google Drive crashes before I can click on the "Send Report to google" button at the diagnostics screen." 
Re: Google Drive PRIMARY KEY error Phillip Wu 12/7/12 9:12 AM
STILL no fix. Ridiculous.
Re: Google Drive PRIMARY KEY error sinrise 12/20/12 5:40 PM
This is when I started having problems. Also, with Minecraft. Google Drive seems incapable of handling too much at once. Weird. It might be time to try DropBox. :(
Re: Google Drive PRIMARY KEY error matt splat 12/27/12 6:55 PM
I have been using Google Drive for about 9 months now and today is the first time I have gotten this Primary Key error. I too can not send a log file since Google Drive closes before it is possible to get the log.  I did upgrade to the new version but still getting the key error.  This solution to search for and delete conflicted copies is not acceptable, nor is decoupling my account, and so I hope that Google fixes this soon or, like others, I will have to switch to a more dependable cloud service.
Re: Google Drive PRIMARY KEY error Luizsalomon 1/4/13 1:16 AM
It seems that this Primary Key error occurs when you are first backing up your files.
In my case, I was backing up a 29GB folder. Took over 2 months to complete the upload of a little over 60.000 files and 8.000 folders, with the computer very well compromised with 50% of it's processing capacity with Google Drive (I bet Google Drive compacts our files (like zip or rar) before uploading so they can use less space and charge the full amount. Very wise, by the way).
Well, it took another extra month because I had this Primary Key situation and innocently disconnected my drive... Had to backup all over again.
But, when the big directories and big chunks of files stopped going up, no more Primary Key problem.
Now the situation is worse: confidence.
Even though I had the message that all files where synced, I found out that a folder wasn't backed up. And after that I found out that more folders weren't (yes, I checked one by one...).
Got around this situation by closing Google Drive and reopening it again (not disconnecting!!!).
So, the good news is that the Primary Key situation disappears along the time. The bad news is that you have other situations awaiting for you after that.
I was granted with an "out of space" award yesterday (and, of course, my files weren't synced anymore). How I've discovered this situation? On this "solution" of mine, of closing Google Drive once and then, I saw that 57 files weren't synced. The problem "out of space".
If my math was correct, 60GB is around 60% of my 100GB storage plan. And as far as I could tell, a little over half full (or half empty).
How this was solved? This morning (right now, by the way) it was all working... after a shoutout on the other forum topic.
I don't believe in witches, but they surely exist.

Cheers,
Luiz.
Re: Google Drive PRIMARY KEY error christiankraak 1/14/13 9:26 AM
I'm also getting this error.. using drive for Eclipse.. Aint it time to resolve this problem now? Would be nice to know if someone is actually working on this. (hint hint google). 
Re: Google Drive PRIMARY KEY error Luizsalomon 1/18/13 9:29 AM
Hello there again Nyan,
Long time since I came here for the last time, but yesterday I had, again, the primary key error. I restarted Google Drive and it worked by itself.
A few moments ago I was messing with some files and found this file:
 - LCD Assembly[Conflito].mcs
So this is why I could find the [Conflict] you told me :) on the conflicted files.
Google Drive does this translation for itself, in the language in which it was installed.

Cheers,
Luiz.
Re: Google Drive PRIMARY KEY error Taneya Koonce 1/20/13 11:26 AM
Thank you so much for this! I searched for conflict files, removed them and the error message went away. 
Re: Google Drive PRIMARY KEY error Pieter Van Gorp 2/6/13 2:32 AM
Same problem here, using XP.  Is there a scripted approach to finding the conflicting file(s)?
Re: Google Drive PRIMARY KEY error matt pepperski 2/6/13 10:33 AM
I did not remove any conflicted files - Instead I disconnected and then reconnected my GDrive account.  This was a very unsatisfactory solution since it means all my 3Gb files had to down load again but after this I no longer had the primary key problem.  I did this about 3 weeks ago and the primary key issue has not returned.  In fact i DO still have conflicted files so I am not sure why some people have to delete them to fix the problem yet I did not.

As far as I know, unlike DropBox, in GDrive you can not discount your account and then reconnect and point at your existing files on your hardrive - GDrive does not seem to allow this and so all files must be re-downloaded (which seems like a very poor design decision) - if you try to COPY all your files back in to your reconnected account then EVERYTHING becomes conflicted - at least that is what happened to me.
Re: Google Drive PRIMARY KEY error Taneya Koonce 2/6/13 10:37 AM
Hi Matt - the first time I received the error message I did exactly as you - disconnected my account. As you note, that was a mistake b/c you can't keep the documents in the same location AND you have to re-download everything (and I have about 25GB worth of info). So, I was very hesitant to do it again when I got the 2nd error message.  But, fortunately, removing the conflicted files worked this time around and I didn't have to disconnect my account. 
Re: Google Drive PRIMARY KEY error matt pepperski 2/6/13 10:45 AM
Thanks, I will try that next time.
Re: Google Drive PRIMARY KEY error heavymarks 2/8/13 4:23 PM
First day of trying Google Drive instead of Dropbox since I liked the idea of being able to search for files like I can with Gmail, but it seems while the search is much better than Dropbox that's about it. Dropbox has never had issues and in the first day I'm already getting issues to which the best answer on here is to rename files locally, online, and reinstall. No thanks, back to dropbox.
Re: Google Drive PRIMARY KEY error meadowsjared 3/18/13 9:04 AM
I was getting this problem.  I sync about 150K files between my work and home computers (which was a PAIN to get set up using drive).

First of all Nyan's answer did not work for me, I'm sorry, however when I'd try to generate the report as he suggested, as soon as the error pops up, I am unable to submit the report, and as soon as I hit "Quit" on the dialog, the report closes along with it, so I'm sorry, that really didn't help.

However, I did find one solution I thought I'd share that worked for me...

Out of 150K files, there were only about 7 files that were still causing this error, so, I went and deleted them and now it's working great!

So, whoever is having this problem, go into your Gdrive, and look for folders that don't have the green checkmark on them (green checkmark means it's sync'd).  Then copy them somewhere else to back them up, and delete them all out of your Gdrive.  Shortly after that, your Gdrive should be able to sync.  At that point, you can possibly move the files back, or maybe look into renaming the files if necessary before moving them back, maybe that might help?  I know for me, I just deleted the files, as they were duplicates anyhow. :-)

I hope that helps you all, it worked for me, good luck!!!

Re: Google Drive PRIMARY KEY error heavymarks 3/18/13 9:22 AM
Unfortunately, deleting any files that Google does not like now and in the future is not a resolution since if we could delete any file or didn't care if any file got corrupt then we would simply leave files on our computer and not add them to GDrive in the first place.

These are bugs that need to be resolved as they do not happen in Dropbox. The only benefit o GDrive is it's cheaper, and better integration with Gmail including attachments and being able to search Gmail for emails and all GDrive files.

Re: Google Drive PRIMARY KEY error meadowsjared 3/18/13 9:53 AM
I agree completely, it's just the best workaround if you don't want to use Dropbox.  Until Google fixes this, they cannot compete with the likes of Dropbox, just because their software is just too darn buggy. :-(

I was just thinking my answer was closer to an answer than the one Nyan suggested considering you CANNOT possibly do what Nyan said considering the program freezes when that error popped up, making his suggestion impossible to do.

Really Google? c'mon, update Drive already, it desperately needs it!!!

Re: Google Drive PRIMARY KEY error ____________________________ 3/19/13 1:14 PM
A quick web search indicates that thousands of people are having this problem and Google isn't doing anything about it.

That is why I switched to Dropbox.

Re: Google Drive PRIMARY KEY error RyanWard 3/20/13 4:08 PM
So,Let me Get this straight.....

Google CREATES a conflict file, great.

Then....it terminates the program because it cannot deal with said file?

Can google change its convention, so instead it creates a file with _conflict_ or any other special character??My log File is attached.

This seems ridiculous. Our company pays for Google Drive to work, and it is seriously hindering our productivity day in and day out.
I have tried the above method. i found and deleted all instances of [conflict] files on both the Web interface and the local machine.I am still receiving this error message.

Re: Google Drive PRIMARY KEY error jtwright 3/26/13 3:21 PM
I've had this issue twice in the last 2 months since I started sharing folders.  I've invited some colleages to test run Google as a cloud server.  I was considering switching the company over to Google apps but everything is just way to glitchy and unreliable.  The lack of response on this issue is also discouraging.  I love Google drive and sync when it is working.

I wouldn't complain if I could just delete a conflict file and move on but I have to disconnect and re-sync everything to resolve my issues

Re: Google Drive PRIMARY KEY error websea 3/26/13 11:57 PM
Does Google team works on this application anymore?
Re: Google Drive PRIMARY KEY error hkpeoples 3/28/13 1:16 AM
Has anyone tried using insync?  Will that solve this problem?
Re: Google Drive PRIMARY KEY error websea 3/28/13 1:30 AM
I've tried Insync. It is ok, but rarely, when I delete a folder from my laptop and the Pc is still syncronizing with other files and the Laptop did not finish the sync of the deleted files (1000+), when the PC begin to sync the files that where deleted from laptop, it will do a mess, many files in no folder. I hope I was explicit.

In my case, Insync was not good enough. I work with projects with many files. Maybe they resolved this issue meantime.

Re: Google Drive PRIMARY KEY error hkpeoples 3/28/13 1:33 AM
It recently went from beta to 1.0, so it may be worth another try?

I don't know.

I just signed up for 5gb on box.com and will use that for projects where there is a lot of collaboration.

At the moment google drive is not usable for me (at least for these types of projects)

Re: Google Drive PRIMARY KEY error meadowsjared 3/28/13 9:16 AM
You know, with Google's Lack of attention to the Windows PC client for drive, and with their API's where I believe you can actually code your own version of drive and... heaven forbid... throw a touch of ERROR HANDLING and workaround in just for S&G's (you know... what Google has YET to DO).  I'm tempted to write my own Drive client and use that instead, at least then I can get some dang software updates and bug fixes UNLIKE Google drive's normal software.

I think either way I'm going to try and post something a little more public than here and try and get some kind of response, or recognition that they are in fact ignoring us Windows PC Drive users, and maybe even bug them enough to ACTUALLY DO SOMETHING!  I recommend y'all do the same. :-)  Who knows, maybe the higher-ups don't even realize how broken to hell Drive for PC is??? :-\

Re: Google Drive PRIMARY KEY error David-M 3/28/13 10:04 AM
What's worked for me in the past with various vendors, including Google for Calendar which also didn't work for years on some very basic stuff, is to contact editors of lots of magazines, web shows, TV shows, big blogs, etc. and give them a tip on a story.  In this case, an interesting story is millions of clients (including me) paying for Google Drive when the basics don't work and paid support is worthless too.  The reporters can get access to influential people at Google, to interview them for the story.  In the Google Calendar case, a set of basic bugs that had gone unaddressed for years got fixed in a month or two after the media coverage I and others created raised awareness.  A bunch of you may want to pursue this approach.  The more who contact the media, the more coverage will be created, the more Google will pay attention.  Google-ites who have been ignoring this may start to fear for their jobs, because they haven't been doing them.
Re: Google Drive PRIMARY KEY error Cole Bonham 4/9/13 2:07 PM
I have over 30,000 files I uploaded and constantly have crashing errors.  This unique key problem is new.  I cannot spend time during my business day of running my own business to look through 30,000 files and delete any X files.  If I am to pay for this, there surely is a better solution.  Please advise
Re: Google Drive PRIMARY KEY error adeb1 4/10/13 2:00 AM
I started getting this yesterday after activating offline docs. Not sure if that will fix it but just trying to roll-back to when it was stable.

The lack of official response here is very concerning though.

Re: Google Drive PRIMARY KEY error johnnya23 4/27/13 1:13 PM
I have over 100,000 files on google drive, how do I find the conflicts?
Re: Google Drive PRIMARY KEY error Tajddin Maghni 5/3/13 1:43 PM
I've also just experienced this and I have two instances of Visual Studio open, Photoshop, Skype and Chrome.  
Re: Google Drive PRIMARY KEY error Cole Bonham 5/3/13 1:54 PM
You don't find the conflicts, instead you tell Google that Drive sucks and then you switch to Dropbox.  I made the change and have not had any problems whatsoever!  It automatically updates instantly and I have not ever had a crash since the time I posted this G-Drive problem.  Won't recommend Drive to anyone!
Re: Google Drive PRIMARY KEY error johnnya23 5/14/13 2:26 PM
have you (google) solved this problem yet?
Re: Google Drive PRIMARY KEY error David O'Malley 5/25/13 6:23 AM
My files did not have any conflict tag, re-downloading all files is not an option and really poor support.
Also marking your own answer as helpful is not helpful, if your advise helped the poster or anyone else they can mark it
Re: Google Drive PRIMARY KEY error David B Berman 5/27/13 2:58 PM
I am wishing to follow your instruction to "Search for any files with a [Conflict] tag next to the filename". What does the [Conflict] tag look like? And are you saying do a visual scan for this tag on a list of my entire drive, or are you saying there is some way to request a list of just the files with the [Conflict] tag?. I have the identical questions for your step 5. Thank you, David
Re: Google Drive PRIMARY KEY error Luizsalomon 5/28/13 10:49 AM
Hey David,
In my case, since my Windows 7 is in portuguese, the conflict files where like "readme[Conflito].txt" or "test[Conflito].doc".
"Conflito" means conflict in portuguese. A guy from Croatia posted that his files had a [sukob] in front, since sukob means conflict in croatian.
Anyway, it's a ridiculous problem that should have been solved by Google a long time ago.

Cheers,
Luiz.

Re: Google Drive PRIMARY KEY error Wingerr 6/5/13 10:46 PM
I got into this same situation when using Audacity for editing a large audio files within a Google Drive folder.  Apparently it's not good to have the Google Drive sync running while doing this, because it's trying to maintain sync with rapidly changing files, and gets things all obfuscated.
Good thing this thread came up on top of the search for google drive primary key, otherwise I might have clicked on the Disconnect drive as the popup suggested, which would have made for a difficult recovery to set up another GD sync folder.
Searched for all the CONFLICT tagged files, which were in the audio file directory I as working with, and deleted them.  That resolved the problem-thanks.
Re: Google Drive PRIMARY KEY error adeb1 6/6/13 12:44 AM
I found this solution after my second incident of the 'primary key' error and this worked for me - http://thesunstroke.blogspot.co.uk/2013/01/google-drive-still-unreliable-how-to.html. I hope it helps.
Re: Google Drive PRIMARY KEY error Wingerr 6/6/13 6:43 AM
That's useful to know-  

 Maybe it'd be best to pause or turn sync off during the time you're actively working with the files to avoid getting it scrambled up from trying to maintain sync with rapidly changing files.

Re: Google Drive PRIMARY KEY error xlnja 6/6/13 8:04 AM
That's what I do, Wingerr.  I have only received the Primary Key error with Quicken files.  Now, before I open Quicken, I pause Google Drive.  Since doing this, I have never again received the Primary Key error.

If you think about it, the Quicken files are updated rapidly like internal program files.  I don't include program or system files in Google Drive because they typically don't include personal data that I work with or care about putting in the cloud.  Quicken is an exception.  I don't think Google intended Google Drive to be used for rapidly updated files but more like documents, photos, etc.

Although it's annoying that Google hasn't resolved this issue, the workaround is easy, and I haven't had any issues in the last 6 months or so.  I have my entire "My Documents" folder in Google Drive and having the ability to access and work with all of those files from anywhere more than makes up for the annoyance.

Re: Google Drive PRIMARY KEY error Luke Hagenbach 6/27/13 12:20 PM
The last post from a Google employee on this issue was 11/08/12. Since then, there have been many people posting that this issue still exists. I get the issue regularly, and have nothing funny going on in my Google Drive folder on my Windows 7 PC.

I wish Google Drive would work half as seamlessly as Dropbox does. Dropbox works wonderfully and never, ever has an issue. I would stick with it, but have picked up a Chromebook Pixel which doesn't support Dropbox natively and I have 1TB of Drive space.

More topics »