coverage analysis failed. failed to initialize external storage

Completed

Hi All!

I'm trying (desperatly) to run a test coverage but I keep getting the message "coverage analysis failed. failed to initialize external storage". What can this be? There is no external storage involved at all.

Thanks,
Karl

8 comments

Hello Karl,

Could you please send us log files? If you run tests from within Visual Studio, start Visual Studio with the following command line arguments: devenv.exe /ReSharper.LogLevel Trace /ReSharper.LogFile. You will find log files in the '%Temp%\JetLogs' folder. Please empty this folder before you launch Visual Studio and start working with dotCover.


 

Kind regards,
Maria

0

Hi again. Any results from analyzing the files or didn't you get them?

A small update from me. I recently got my license upgraded (and are no longer using the evaluation version of DC 3) and now everything runs significantly faster. Still same error though but I do not have to wait a long, long time for it to show.

0

Hello Karl,

Unfortunately, I haven't received any files. Could you please upload them to our ftp server: ftp://ftp.intellij.net/.uploads/ ?


Kind regards,

Maria

 

 

0

Hi again!


Seems like it works fine if running VS as administrator.

I'll do that when running DC.
0

Same problem for me.

VS2015, R# Ultimate 10.0.2.

My development account runs using UAC (User Access Control).  Dot Cover fails with this error.  The work-around mentioned (launch VS2015 with elevated privilege) works, but it's generally not good practice to develop with elevated privilege.

0

Hi David,

We have found the cause of the problem and it turned out that this is not dotCover's fault. There can be some third-party applications in a system that block WCF services registered without administrative rights. As a result dotCover can't connect to its external process.

Please have a look at https://youtrack.jetbrains.com/issue/DCVR-7906.

0

Thanks for the quick reply.  I have read through the notes and will find out which piece of software is causing the issue.

0

Got into the same problem, I had to reinstall DotCover to fix this issue

0

Please sign in to leave a comment.