Job History Filters

Filters are a flexible and powerful way to extract information of interest from the transfer logs.  To analyze the errors in your event log, it is generally best to first select a type of error from the All Statuses filter at the very top of the modal, such as read-error or write-error.  You can then use the Search tool that is just to the right of All Statuses to further refine your selection.The Search tool has fields, which enable you to select a general job attribute such as a directory or file size, and filters, such as ‘Contains,’ which allow you to narrow your search all paths to only those that contain a specific subset of that attribute, such as paths that contain ‘Documents.’

Match filters are a special type of filter that use regular expressions (regex) to do compound searching.

All Statuses:

Click on the All Statuses menu to select the type of error you wish to analyze:

The menu listings will only include the error types in your particular job run.  Some of the more common statuses you may see listed are:

  • success:  file transferred successfully.
  • match-exists:  the source and target instances of the file or folder were identical, so it wasn’t transferred.
  • match-current: the current version on the source matches the current version on the target, so the file wasn’t transferred.  For jobs where file version transfer has been selected.
  • read-error (failed to read file on source) and write-error (failed to write file to target).
  • source-missing:  this simply means a file was found on the target that did not exist on the source.
  • filtered:  files such as hidden files and system files are not transferred by default; many cloud providers exclude them anyway.  If you have additionally configured your job with date filters or other filename filters, these will also be listed as filtered. These files were not transferred.
  • deleted:  files that were deleted from the target during the run; for jobs where Mirror deletions has been selected.
  • target-path-missing:  there was a file or folder that was present on the target, but not on the source, at the time that the target was scanned, and Mirror Deletions was selected for the job.  When CFP went back to delete the item, it was no longer present (presumably because the user deleted it between the time the target was scanned and when CFP was ready to actually delete the item).
  • size-exceeded: file size is larger than the target server supports.
  • batch-queued: the item has transferred successfully to the Azure layer of the Microsoft tenant, but CFP has not received confirmation that the batch has transferred successfully to the final destination on SPO/OneDrive. This status is only seen in jobs that have Decoupled SPO Migration Jobs selected as an advanced option on an SPO or OneDrive target.
  • match-future-time: file mtime on the source is in the future, and future mtimes (e.g., 8/1/2034) are not supported on the target. When that happens, CFP will attempt to save the file to the target on the first run with the correct mtime, but the target converts that, typically to the time that the file was saved to the target. When CFP does a sync, the file would normally be transferred again because the source file is newer than the target, but CFP does not transfer the file and simply labels it as match-future-time as long as the size is the same. Future mtimes can occur if files are uploaded to Windows servers from devices such as older cell phones.

Search Terms:

Click the magnifying glass icon to the left of the All Statuses menu to further narrow down your listings. There are two types of filters in the Search form:

  • Include/Exclude filters. These are ‘Contains,’ ‘Matches,’ ‘Equals,’ ‘Existence,’ and their respective exclude (not) filters.
  • Text string and regex filters. Regex filters are only used with the ‘Matches’ and ‘Does not match’ filters.

Include/Exclude Filters

These enable you to further refine your selection to a string within the path name of the file or error message.

CONTAINS: This returns all results that contain the string entered. If you want to return all instances of the directory ‘My Documents,’ you would enter /My Documents in the Source field.

MATCHES: This returns all results that match the string expression entered. Some examples are:

  1. To return all instances of csv files, you would enter [.]csv$ in the Source field.  This will find a period, then look for a match of the string “csv;” the ‘$’ character indicates the end of a line.
  2. To return all instances of folder names for /Kate Jones and /Kate Smith-Jones, you would enter /Kate[^/]*Jones in the Source field.  This would look for the string “/Kate” followed by 0 or more characters that are not a forward slash (‘/’), followed by the string “Jones.”
  3. To return all gif and jpg files, you would enter [.]gif$|[.]jpg$ in the Source field.

EQUALS:  returns an exact match of the entire string.  This is primarily useful if you are interested in the status of a particular file or the instances of a specific error.  You must enter the full path and filename to return a match.  If you are searching for a file /ksmith/My Documents/myFile.docx, that is what you enter when using the ‘Equals’ evaluator.  Transfer log paths do not include any target directory. To search for specific errors, the ‘Contains’ and ‘Matches’ filters generally work better, as many of the error message strings will include data such as file name and file size that are specific to the file that did not transfer.

EXISTENCE:  Provides a boolean (true/false) operator that is primarily useful when used with other search filters. For example, if you wanted to search for all files on the target that do not have extensions, you could enter Target Extension does not exist in the Target tab, and then select Type is not a directory in the General tab.

Fields in the Job History Filters

Source and Target Tabs

SOURCE/TARGET:  Search for a full path or path fragment, on source or target.

SOURCE/TARGET EXTENSION: Search for all instances of a particular file extension in your job.  Enter the extension without a leading period.  For example, to search for all docx files, enter docx.

SOURCE/TARGET CATEGORY:  Select a type of file. Supported types, and the files returned, are:

  • AUDIO:  a52, aac, ac3, aiff, au, aup, dts, flac, itdb, itl, m3u, m4a, m4b, m4r, mka, mp1, mp2, mp3, mpa, nra, ogg, rm, sfap0, spx, wav, wma, wmdb, wpk, wpl
  • CONFIGURATION:  cf, cfg, conf, config, csf, icc, ini, properties, reg, setting, udl
  • CONTAINER:  7z, 7zip, ace, arc, arj, b64, bkf, bz2, bza, c2d, cab, cdi, cpio, deb, dmg, enc, gca, gho, gz, gza, ha, img, imz, iso, ize, jar, lha, lzh, nrg, pak, pdi, pk3, rar, rpm, sit, tar, tbz, tgz, tz, uue, v2i, z, zip
  • DATA:  bqy, csv, dat, data, wab, xml
  • DATABASE FILES: accdb, accdc, accde, accdr, accdt, accdw, accft, db, dbf, fdb, ib, ldb, ldf, mdb, mdf, pdx, sdf, sql, sqlite
  • GRAPHIC FILES:  ai, ani, arw, b3d, bmp, cam, cdr, clp, cr2, crw, cur, dcm, dcr, dcx, dds, dib, djvu, dng, dwg, ecw, emd, emf, eps, fh10, fh11, fh6, fh7, fh8, fh9, fpx, fsh, g3, gif, icl, ico, iff, indd, iw44, j2k, jp2, jpc, jpe, jpeg, jpg, jpm, k25, kdc, lwf, mef, mng, mos, mrw, nef, ngg, nlm, nol, orf, pbm, pcd, pcx, pdn, pef, pgm, png, pnx, ppm, ps, psd, psp, qtif, raf, ras, raw, sff, sgi, skm, sr2, srf, svg, tga, tif, tiff, ufo, wbmp, wmf, xbm, xpm
  • HELP FILES: aw, chm, cnt, gid, hlp, hxa, hxc, hxf, hxk, hxs, hxt, toc
  • INTERNET FILES: asmx, asp, aspx, cfm, cgi, css, htaccess, htm, html, htpassword, htt, js, mht, php, php5, shtml, url, ascx
  • MAIL FILES: 0tx, edb, eml, emlx, msg, ndk, nsf, ntf, oft, olk, olm, ost, pst, rwz, wab, mbox
  • OFFICE FILES AND DOCUMENTS: 123, book, dic, doc, docm, docx, dot, dotm, dotx, fm, frx, lex, lwp, mde, mdt, mpp, mwp, nk2, odm, odp, odt, one, onebin, onecache, onepkg, onetoc, onetoc2, onetmp, pdf, pip, pot, potx, pps, ppt, pptm, pptx, pub, pwi, rtf, sam, thmx, vdx, vsd, vss, wks, wk1, wk2, wk3, wk4, xla, xlam, xlk, xlr, xls, xlsx, xlsm, xlsb, xlt, xltm, xltx, xlw
  • PC VIRTUALIZATION FILES: vhd, vhdx, vfd, vmdk, vmem, vmsn, vmss, vmx, vsv, vud
  • PROGRAM FILES: manifest, 8bf, bat, bpl, class, cmd, com, dll, exe, itxib, jar, lnk, mo, msc, mui, ocx, pm, rll, scr, so, vbx, x86, xpt
  • SOFTWARE DEVELOPMENT FILES: dbg, a, ahk, asm, bdsgroup, bml, bpg, bpi, bpk, bpr, c, cbl, cpp, cs, dcr, dcu, def, dess, dfm, dof, dpk, dpr, drc, dtd, elf, exp, fmx, frm, git, h, hg, hmx, hmxp, hpp, idl, inc, inl, ise, ism, iss, java, jsl, json, lib, lic, lpk, mak, map, mds, mk, ncp, nrmap, o, obj, pas, pch, pdb, pfx, pl, ps1, psd1, psm1, py, rc, rc2, rdl, res, resources, resx, rgs, scs, shfb, sln, snippet, src, suo, svn, swd, swt, targets, tcl, tcLLP, tcScript, tlb, trx, tt, vb, vbp, vbs, vbw, vcproj, vcxproj, vsp, vsprops, vssettings, vstemplate, wsdl, wxl, wxs, xaml, xcodeproj, xdr, xfm, xsd, xsl
  • SYSTEM FILES: adm, admx, afm, ax, cat, cdf-ms, cer, cpl, dmp, drv, ds_store, dxt, evt, evtx, fon, gpd, icm, inf, inf_loc, isp, man, mmm, mof, msi, msm, msp, msu, mum, nlp, nls, otf, pfb, pfm, pnf, ptxml, rbf, rdp, spc, sys, theme, ttc, ttf, vst, vxd, wer
  • TEMPORARY AND BACKUP FILES: —, $$$, bak, cache, chk, dmp, err, old, tmp
  • TEXT FILES: 1st, asc, latex, log, nfo, tex, txt
  • VIDEO FILES: aif, ape, asf, avi, divx, dv, fla, flv, idx, ifo, m1v, m2ts, m2v, m4v, mid, midi, mkv, mov, mp4, mpeg, mpeg1, mpeg2, mpeg4, mpg, mpv, mts, ogm, ra, snd, srt, sub, swc, swf, ts, vob, wmv

OWNER:  search for the account name of the data’s owner. Available for account mapping jobs only.

General Tab

TYPE:  This is one of the more popular fields.  It has two options:  ‘Type is directory’ returns all paths ending in directories, and ‘Type is not directory’ returns all files. So if you want to list only files in your transfer report, select ‘Type is not directory.’

BYTES, TRANSFER START DATE, MODIFIED DATE:  These fields can help you narrow down the transfer report to files of a specific size or date range.

MESSAGE:  This is another popular field that enables you to identify all errors in your job.  See ‘Identifying All Types of Errors in a Job’ below for additional information.

About Linked Files

Linked files – such as .xlsx and other Office files – have specialized reporting features that will enable you to see the paths to which the dependent spreadsheets are linked.

  • There is a filter in transfer reports now, which enables you to filter for linked files:
  • If you select a linked file in a transfer report, there is a Links tab in the Details pane that will list the files that are linked into the current one.
  • Transfer reports have a new column for links, which will list linked inputs for applicable files.
  • Encrypted and password-protected files do not have accessible content, and their links will not be reported.

Identifying All Types of Errors in a Job

Some jobs may have a large number of one error, and a handful of other errors that still need to be isolated and addressed. For example, you may have hundreds of permissions errors and a few other files that failed to transfer for some other reason. To identify all of the errors in a job, do the following:

  1. It’s helpful to select the class of error – e.g., read-error – from the All Statuses menu.
  2. Click on the Magnifying class to call up the Search box, and select ‘Does not match’ from the menu next to the Message field (General tab) in the Search box.
  3. Enter the most common message you received in the Message field. For example, if you had a lot of EPERM code errors in your event log, you can simply enter ‘EPERM.’ You’ll see results displayed for all of the files and directories that do NOT have this error.
  4. Click on any one of the files/directories in the list, and you’ll see details on this file at the bottom of the screen. Look for the error message for this file in the Message field.
  5. Add the error to the Search box message field using the following format:  errorMessage1|errorMessage2. So for example, if your first error was an EPERM and your second message was “The network path was not found.”, you would enter EPERM|The network path was not found..
  6. This will either return a smaller set of files and directories that do not have either error, or it will return no results. It it returns no results, you know that the only errors in the job were the two that you entered. It it still returns results, click on a file or directory in the list again, identify the error, and add it to the Message field in the Search box as you did previously. Continue until no files are displayed. You will then have identified all of the errors for your job.  Note that if you have filtered for read-errors or write-errors, you will have to repeat the process for the other class of error.
Updated on October 21, 2020

Was this article helpful?

Related Articles

Leave a Comment