Can N1QL work with the new Couchbase 3 beta

I am been trying to run some test using Couchbase server 3 and N1QL however i am getting this message
{
“error”: {
“caller”: “view_index:200”,
“code”: 5000,
“key”: “Internal Error”,
“message”: “Bucket xxxxxx not found.”
}
}

the buckets have been created and no password has been set for them

i am also seeing the following message in the console

15:12:11.655429 ERROR: Unable to access view - cause: error executing view req at http://localhost:8092/xxxxxx/_all_docs?limit=1001: 400 Bad Request - {“error”:“bad_request”,“reason”:"_all_docs is no longer supported"}
– couchbase.(*viewIndex).ScanRange() at view_index.go:186
15:12:11.655443 Checking bucket URI: /pools/default/buckets/xxxxxx?bucket_uuid=068d293c13379cadc7b331fb2fa4f61c
15:12:11.655464 ERROR: Get /pools/default/buckets/xxxxxx?bucket_uuid=068d293c13379cadc7b331fb2fa4f61c: unsupported protocol scheme “” – couchbase.(*viewIndex).ScanRange() at view_index.go:192

I have same issue.

I make upgrade from CB 2.5 to CB 3.0 with the new N1QL preview 3, i backup data with cbbackup and then restore this backup with cbrestore.
When i call some SELECT:
cbq> SELECT * FROM xxx;
Requested resource not found.

And in log:
07:17:00.072695 ERROR: Unable to access view - cause: error executing view req at http://xxxx:xxxxx@127.0.0.1:8092/xxx/_all_docs?limit=1001: 400 Bad Request - {“error”:“bad_request”,“reason”:"_all_docs is no longer supported"}
– couchbase.(*viewIndex).ScanRange() at view_index.go:186
07:17:00.072738 Checking bucket URI: /pools/default/buckets/xxx?bucket_uuid=6b2a05c4ec5b8d80f3c4b01a0f309d95
07:17:00.072782 ERROR: Get /pools/default/buckets/xxx?bucket_uuid=6b2a05c4ec5b8d80f3c4b01a0f309d95: unsupported protocol scheme “” – couchbase.(*viewIndex).ScanRange() at view_index.go:192

Have you created a primary index per the instructions? Based on what you’re seeing, it looks like perhaps not.

As mentioned by ingenthr:
(From the instructions in the N1QL page :
Step 5: Before issuing queries against a Couchbase bucket,
run the following command from the query command line:

CREATE PRIMARY INDEX ON [bucket-name]

That was my fault, I did not notice last point in installation instructions . Thank you