{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":29651,"path":"it-operations-management/discovery/file-based-discovery-troubleshooting.md","title":"File-based Discovery issue resolution","bundle":null,"doc_type":null,"release":"australia","body":"\n# File-based Discovery issue resolution\n\nIf you have any issues while setting up or running File-based Discovery, follow the actions listed here to help resolve them.\n\n<table id=\"table_v13_l1v_phb\"><thead><tr><th>\n\nIssue\n\n</th><th>\n\nCause/Action\n\n</th></tr></thead><tbody><tr><td>\n\nError message: File Discovery data not yet synced...\n\n</td><td>\n\n-   Allow Content Data Service \\(CDS\\) time to synchronize the samp\\_file\\_\\* tables. Initial synchronization can take approximately 24 hours.\n-   Review the Data Services: Download Schedules \\(cds\\_client\\_schedule\\) table to check if the timestamp has been updated for “samp\\_file\\_\\*” tables.\n\n</td></tr><tr><td>\n\nFile-based Discovery is not triggered during discovery.\n\n</td><td>\n\n-   Feature has not been enabled. Check the Discovery Definition Configuration Console and verify that File-based Discovery is enabled.\n-   Interval between scans is too long. Check the interval setting on the Discovery Definition Configuration Console.\n\n</td></tr><tr><td>\n\nFile-based Discovery is not triggered during discovery.\n\n</td><td>\n\nCheck the Internal properties managed by the Discovery \\[discovery\\_private\\_properties\\] table for the following items. To view this table, enter **discovery\\_private\\_properties.list** in the navigation filter and press **Enter**.-   File\\_discovery.file\\_extensions\\_windows should contain a list of Windows file extensions to be scanned.\n-   File\\_discovery.unix\\_filename\\_timestamp should be something other than 1970 timestamp.\n-   File\\_discovery\\_windows\\_filename.timestamp should be something other than 1970 timestamp.\n\nIf either timestamp shows 1970, CDS content hasn't downloaded yet. To trigger an immediate download, navigate to the Data Services: Download Schedules \\(cds\\_client\\_schedule\\) table and search for records where the **Table** field is `samp_file_name`, `samp_file_map`, or `samp_file_set`. Open each record and select **Execute Now**. To verify the download, navigate to **System Logs &gt; Outbound HTTP Requests** and confirm the **Response status** is 200 for requests where the **URL hostname** is `sncdataservices.service-now.com`.\n\n</td></tr><tr><td>\n\nErrors in MID Server log from FileDiscoveryFilter or MID Server issue created.\n\n</td><td>\n\n-   Check if the File-based discovery inclusion list exists. The inclusion list is in the MID Server installation folder in `/agent/work`. If it does not exist, the synchronization did not succeed.\n-   Review the MID Server record on the instance to see if a MID Server issue was created.\n-   MID Server uses the GetMIDInfo scripted soap service to synchronize the inclusion list. See if errors are generated from this script.\n-   Select the **File discovery filter refresh** Related Link in the MID Server record to synchronize the file names to this MID Server.\n\n</td></tr><tr><td>\n\nPowerShell errors\n\n</td><td>\n\n-   Include the script in your anti-virus software.\n-   Add ServiceNow publisher to your trusted publisher repository.\n\n</td></tr></tbody>\n</table>**Related topics**  \n\n\n[File-based Discovery references](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/discovery/file-based-discovery-references.md)\n\n"}}