Forum Discussion

Andy_Geluykens's avatar
13 years ago

File System Analyzer tool has topped working

I have installed the tool on a offline server with admin access to every share. Now when the scans starts, after a while the tool gives the following error:

 

 Description:

  Stopped working

 

Problem signature:

  Problem Event Name:                        CLR20r3

  Problem Signature 01:                       filesystemanalyzer.exe

  Problem Signature 02:                       1.12.0.3250

  Problem Signature 03:                       4babfa29

  Problem Signature 04:                       mscorlib

  Problem Signature 05:                       2.0.0.0

  Problem Signature 06:                       4ca2b851

  Problem Signature 07:                       2c1

  Problem Signature 08:                       25

  Problem Signature 09:                       System.ArgumentOutOfRange

  OS Version:                                          6.1.7601.2.1.0.272.7

  Locale ID:                                             2067

 

Read our privacy statement online:

  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

 

If the online privacy statement is not available, please read our privacy statement offline:

  C:\Windows\system32\en-US\erofflps.txt 

The server is not connected to the internet, the error is the same for the administrator and the backup service account.

What can be done to avoid this problem ?

  • I Asked my client to start the scan with unchecked full analyses. Also I asked for an update to the .NET 4 framework. I will post the results when I get them.

    If it still fails I will send the new version of the FSA tool.

  • Probably best to post internally to the forums at symc through your partner tools as you can't open a support case on it unfortunately
  • Okay - starting my scan.

     

    As a matter of interest what options did you select on the Analyzer?

    Did you opt for Full Analysis?  Have you tried unticking that?

  • It looks like a generic .NET error.  These are hard to diagnose as the .NET error is not very specific on what has crashed. 

    BTW, there is a newer version of FSA Analyzer, 1.14.2.

  • I Asked my client to start the scan with unchecked full analyses. Also I asked for an update to the .NET 4 framework. I will post the results when I get them.

    If it still fails I will send the new version of the FSA tool.

    • Qual's avatar
      Qual
      Level 2

      Is there a way that you could attach the latest version here please?