4 Replies Latest reply on Feb 28, 2017 9:21 AM by brad.e.smith

    ErrorScan folder explosion after Windows 10 install

    brad.e.smith Apprentice

      One of our smaller partner companies has begun running Windows 10 Enterprise. Since going live in production, we have noticed that most if not all of their inventory scans have started falling into the ErrorScan folder. We quickly identified this being a VarChar limit as a result of our scanning of .DAT files (some of our vendor updates rely on DAT files in lieu of version numbers.


      Our DAT file scan is accomplished in Manage Software LIst>Settings>DataFileExtensions. We then thought to exclude the folders/file paths in question but hit a wall.


      Ex. of some of the problematic file paths in our ErrorScan SCN files:




      Software - Data Files - (Path:C:\ (ÎX Ä[...\0\0-NAMESPACE-HTTPS???NEXT-SERVICES.APPS.MICROSOFT.COM?BROWSE?6.3.9600-0?788?EN-US?C?US?NAMESPACE?PC?00000000-0000-0000-0000-000000000000?00000000-0000-0000-0000-000000000000-.DAT) - File Name =0-NAMESPACE-HTTPS???NEXT-SERVICES.APPS.MICROSOFT.COM?BROWSE?6.3.9600-0?788?EN-US?C?US?NAMESPACE?PC?00000000-0000-0000-0000-000000000000?00000000-0000-0000-0000-000000000000-.DAT




      Has anyone encountered this? If so, how did you resolve the issue.


      If you haven't encountered this but are familiar with problems of this nature, what would you suggest?


      We've just started deploying 9.6 SP3 and will be going to 2016 in the next few months.

        • 1. Re: ErrorScan folder explosion after Windows 10 install
          cjensen SupportEmployee

          Hi Brad,


          Is there by chance an error message logged within the Windows Event Viewer when these scans are processed? It seems like we need to increase the varchar limit within the database for this path. The error in the Windows Event Viewer should tell us specifically what table the issue is occurring on. Please let me know,



          • 2. Re: ErrorScan folder explosion after Windows 10 install
            phoffmann SupportEmployee

            I've been running 2016 across a bunch of my accounts / customers & have never seen anything like THAT come back. Quite interesting.


            So "technically" the explanation here is super simple. "String is (way) too long to fit into the relevant DB field ... so scan is rejected". That's not what you want to troubleshoot though.


            You want to check what on earth is producing such massive strings (and - to my eyes - that looks like a bunch of corrupted data there).


            Is it possible you're dealing with a bunch of duff OS installs (or duff / corrupt / "really bad" package installs) that result in such corrupted data on the client itself? The Inventory Scanner is "just" reporting what the client is seeing ... if the data on the client is corrupted (happens semi-regularly with WMI for instance), then it's just going to pass on the bad/corrupt data.


            So - check whether it's all "the same software package" that's messing you up (the stuff that the path is pointing to), for instance. Or if there's other shenanigans ("untrustworthy end users who love to install crap and for some reason still have admin rights" for instance) going on.

            1 of 1 people found this helpful
            • 3. Re: ErrorScan folder explosion after Windows 10 install
              brad.e.smith Apprentice

              We're still running down the rabbit hole on this one.

              I have a ticket open with support so hopefully we'll have a "cause" and "resolution" to report back with soon.

              • 4. Re: ErrorScan folder explosion after Windows 10 install
                brad.e.smith Apprentice

                Removal of ".DAT” from DataFileExtensions in Manage Software Lists>Settings appears to have resolved our issue.

                DAT was placed in that setting after a previous support ticket was opened last year. While it initially fixed the problem we were having, it was overkill.