Skip to content

Unable to analyze logs on network directory #10

@JamesSkemp

Description

@JamesSkemp

I'm attempting to use ELMAH Log Analyzer to analyze logs available via a network directory, \example\path\to\elmah

When opening ELMAH Log Analyzer there's no option under Connect that allows me to access the share (unless I map the directory).

When I try to open the path via the command line, as detailed on https://code.google.com/archive/p/elmah-loganalyzer/wikis/CommandLineArguments.wiki, I get the following error when the program loads:

System.AggregateException: One or more errors occurred. ---> System.ApplicationException: The directory: \example\path\to\Elmah.Errors" was not found
at ElmahLogAnalyzer.Core.Domain.FileErrorLogSource.GetLogs()
at ElmahLogAnalyzer.Core.Domain.ErrorLogRepository.Initialize()
at ElmahLogAnalyzer.UI.Program.<>c__DisplayClass10.b__6(Task previousTask)
at System.Threading.Tasks.ContinuationTaskFromTask.InnerInvoke()
at System.Threading.Tasks.Task.Execute()
--- End of inner exception stack trace ---
---> (Inner Exception #0) System.ApplicationException: The directory: \example\path\to\Elmah.Errors" was not found
at ElmahLogAnalyzer.Core.Domain.FileErrorLogSource.GetLogs()
at ElmahLogAnalyzer.Core.Domain.ErrorLogRepository.Initialize()
at ElmahLogAnalyzer.UI.Program.<>c__DisplayClass10.b__6(Task previousTask)
at System.Threading.Tasks.ContinuationTaskFromTask.InnerInvoke()
at System.Threading.Tasks.Task.Execute()<---

I've tried running the command line as normal, as well as as an adminstrator, with the same message.

Is it possible to support network shares without having to map them to a drive first?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions