title: Documents visible but "doesn't exist"
body: <p>I have been developing my application from a dev sandbox and want to push the reference data from &quot;dev&quot; to &quot;prod&quot;. I thought I'd succeeded by executing the following commands:</p>
  <p>On my OSX dev machine:</p>
  <pre><code>cbbackup http://127.0.0.1:8091 ~/couchbase-reference-data -b reference_data -u username -p password
  </code></pre>
  <p>Again on my OSX dev machine:</p>
  <pre><code>cbrestore ~/couchbase-reference-data http://prod.server.com:8091/ -u password -p password
  </code></pre>
  <p>Now when I go to the admin console on production I see this:</p>
  <p><img src="https://i.stack.imgur.com/ah56H.png" alt="enter image description here" /></p>
  <p>Looks good at this point. However, if I click any of the &quot;Edit Document&quot; button things go tragically wrong:</p>
  <p><img src="https://i.stack.imgur.com/ZPYq9.png" alt="enter image description here" /></p>
  <p>Any help would be GREATLY appreciated!</p>
  <h2>UPDATE:</h2>
  <p>I've noticed that now when I run the <code>cbrestore</code> command I get the following errors:</p>
  <pre><code> 2013-06-03 16:53:48,295: s0 error: CBSink.connect() for send: error: SASL auth exception: aws.internal-ip.com:11210, user: reference_data
   2013-06-03 16:53:48,295: s0 error: async operation: error: SASL auth exception: aws.internal-ip.com:11210, user: reference_data on sink:   http://prod.server.com:8091/(reference_data@127.0.0.1:8091)
  error: SASL auth exception: aws.internal-ip.com:11210, user: reference_data
  </code></pre>
  <p>This reminds me that I think what I did was copy the ~/couchbase-reference-data directory to the production environment and then ran the <code>cbrestore</code> from there. I have just done that now and get the following confirmation:</p>
  <pre><code>  [####################] 100.0% (189/189 msgs)
  bucket: reference_data, msgs transferred...
         :                total |       last |    per sec
   batch :                    1 |          1 |       16.1
   byte  :                36394 |      36394 |   585781.0
   msg   :                  189 |        189 |     3042.1
  done
  </code></pre>
  <p>After this process, however, the problem still exists in the same manner as described before.</p>
  <h2>UPDATE 2</h2>
  <p>I decided to delete, re-create, and re-import the bucket on production. All steps completed and I still have the same error but I'm wondering if the LOG file has any interesting information in it:</p>
  <p><img src="https://i.stack.imgur.com/LMSiM.png" alt="enter image description here" /></p>
  <p>The things that stand out as interesting to me are:</p>
  <ol>
  <li>The loading time was &quot;0 seconds&quot; ... as much as I'd like to believe that it may be a little too quick? It's not a ton of data but still.</li>
  <li>The &quot;module code&quot; is named 'ns_memecached001' ... is that an issue? Memcached? I did double check that I set this up as a couchbase bucket. It is.</li>
  </ol>