Support Center

Name is required.
Email address is required.
Invalid email address
Answer is required.
Exceeding max length of 5KB

fsListFiles: Could not find a part of the path 'd:\data\logs'

Robert Eastman Feb 20, 2015 01:19PM PST

I have my two external TMG server in the array as my sources in TMGReporter. They both have displayed the following issue, one more than another. The log location on the TMG server is there but can't determine what this keeps reporting this issue.

Up 0 rated Down
Fastvue Feb 20, 2015 04:51PM PST FASTVUE Agent
Hey Bob,

Thanks for getting in touch about this.

Is D:\ a local drive or a mapped network drive? It seems that on occasion the Fastvue Arbiter has trouble accessing the path. The could potentially happen if the TMG Server is under resourced.

We may be able to get some more information about what is going on from a verbose diagnostic log.

Can you try these steps:
1. Restart the Fastvue Arbiter service on your TMG Server, as well as the Fastvue TMG Reporter service on the Fastvue server.
2. Go to Settings | Diagnostic and increase the logging level to 'Most'
3. Go to Settings | Sources and click View Issues | Clear All Issues (in the top right corner).
4. If the error occurs again, zip and upload the Dashboard.log (location also displayed in Settings | Diagnostic) to

We look forward to hearing from you.

Up 0 rated Down
Bob Eastman Feb 24, 2015 02:58PM PST
Scott, I have uploaded the file. I only had one of the array member display the error this time.
Up 0 rated Down
Fastvue Feb 24, 2015 04:01PM PST FASTVUE Agent
Hey Bob,

Unfortunately the Dashboard.log hasn't provided any extra information.

Is the source importing data? If so, the log location must be accessible, but if the service is sometimes throwing the error, then it could be a flakey network connection (which only makes sense if D:\ is a mapped network drive), or a flakey drive connection, or the TMG server is slightly under resource and preventing the Arbiter from querying the log location.

We can reproduce the issue by adding a nonexistent path into the Fastvue Arbiter Settings application, which is expected.

Have you edited the log paths in the Fastvue Arbiter Settings application at all? If you are logging to SQL Express (default) you do not need to do this. You only need to customize the path if you are logging to W3C text logs AND have also changed the logging location away from the default (C:\Program Files\Microsoft Forefront Threat Management Gateway\Logs).

I hope this helps! Let me know how you go.

Up 0 rated Down
Fastvue Mar 04, 2015 10:59AM PST FASTVUE Agent
Hey Bob,

I'm just checking in to see how everything is going with Fastvue TMG Reporter. Did my last email help resolve the import issues you were seeing?

Please let us know if there is anything else we can help you with!


Post Your Public Answer

Your name (required)
Your email address (required)
Answer (required)

Contact Us

  • Post a Public Question
  • Email Us
  • Chat with us

    Call Us @ 888.885.6711
seconds ago
a minute ago
minutes ago
an hour ago
hours ago
a day ago
days ago
Invalid characters found