Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The remote server returned an error: (404) Not Found. at blob.FetchAttributes(); #22

Open
jbreuer opened this issue Jul 27, 2016 · 2 comments

Comments

@jbreuer
Copy link

jbreuer commented Jul 27, 2016

Hello,

The error message is the same as in #20, but now the error happens at another line.

blob.FetchAttributes();

Here is the stack trace:

The remote server returned an error: (404) Not Found.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Net.WebException: The remote server returned an error: (404) Not Found.

Source Error:

Line 250: {
Line 251: var blob = _blobContainer.GetBlockBlobReference(_rootFolder + name);
Line 252: blob.FetchAttributes();
Line 253: return new AzureIndexInput(this, blob);
Line 254: }

Source File: d:\data\inetpub\new-heroes\Sources\Project.Web.Core\ExamineAzure\AzureDirectory.cs Line: 252

Stack Trace:

[WebException: The remote server returned an error: (404) Not Found.]
System.Net.HttpWebRequest.GetResponse() +1740
Microsoft.WindowsAzure.Storage.Core.Executor.Executor.ExecuteSync(RESTCommand`1 cmd, IRetryPolicy policy, OperationContext operationContext) +1123

[StorageException: The remote server returned an error: (404) Not Found.]
Microsoft.WindowsAzure.Storage.Core.Executor.Executor.ExecuteSync(RESTCommand`1 cmd, IRetryPolicy policy, OperationContext operationContext) +2644
Examine.Directory.AzureDirectory.AzureDirectory.OpenInput(String name) in d:\data\inetpub\new-heroes\Sources\Project.Web.Core\ExamineAzure\AzureDirectory.cs:252

[FileNotFoundException: segments_3]
Lucene.Net.Index.FindSegmentsFile.Run(IndexCommit commit) +1494
Lucene.Net.Index.DirectoryReader.Open(Directory directory, IndexDeletionPolicy deletionPolicy, IndexCommit commit, Boolean readOnly, Int32 termInfosIndexDivisor) +87
UmbracoExamine.UmbracoExamineSearcher.OpenNewReader() +67
Examine.LuceneEngine.Providers.LuceneSearcher.ValidateSearcher(Boolean forceReopen) in X:\Projects\Examine\Examine\Projects\Examine\LuceneEngine\Providers\LuceneSearcher.cs:288

I hope it's just as easy to fix as the last time ;-).

I've also reported it here: https://our.umbraco.org/forum/extending-umbraco-and-using-the-api/78818-using-azuredirectory-with-examine#comment-252215

@richorama
Copy link
Member

I'm wondering if this is the correct behaviour. The blob does not exist, therefore a FileNotFoundException is thrown.

@jbreuer
Copy link
Author

jbreuer commented Jul 27, 2016

It might have been an error with Examine. A new beta is out with the following fixes. Now trying it: Shazwazza/Examine@92456aa

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants