Having trouble a with FileSite view in Outlook 2010? Is it repeatedly garbled (e.g. Outlook flag column included)? Perhaps it’s not available, instead showing the error message “Outlook cannot display this view”. In this article, I’ll provide a few troubleshooting tips, and what you may find is a decent fix.
If you’re having similar troubles with a different version of Outlook, perhaps without even FileSite, read on as well for links to other Outlook troubleshooting tips in this topic.
What happened to my view?
FileSite works with Outlook’s personalization infrastructure, to store how a particular user has modified the layout of a particular folder or view. This infrastructure sometimes gets garbled by ‘bad Outlook citizens’ that don’t follow the correct Microsoft integration protocols. Because FileSite ‘lives in’ Outlook, FileSite’s views are sometimes innocent victims of some other Outlook add-in’s overruns.
Confirm the cause
(ETA) Outlook’s conversation view is a common cause of this issue. Check whether this has been applied to the problematic FileSite view. If this does not resolve the problem, continue on…
Sadly, I can’t provide you a recipe to isolate which part of an Outlook ecosystem is overrunning a FileSite view, but I can help you to confirm that this is the trouble in a particular case.
- On the affected machine, close down Outlook completely. Confirm through Task Manager that it is no longer running.
- Navigate to this user’s profile folder, specifically Documents and Settings<username>Application DataiOutlook
- If you are running Outlook 2010 or Outlook 2007, you will see at least six “.vdm” files in this folder. Make a note of the last-modified dates on each of these files.
- Now, delete the file views.vdm. The file will be recreated with any of your FileSite saved views, and default views the next time Outlook/FileSite is launched.
- Launch Outlook and navigate to the affected view.
- If it’s still corrupt, go back to step 1 and this time delete all the vdm files from the folder.
- Re-launch Outlook and navigate to the affected view.
- Does the view now display correctly, in step 5 or 7? If it does, then it’s time to look into the views more closely.
Tech-talk: Outlook Views and FileSite
This is a description of the application functionality starting with the most generic and moving to the per-user, per-folder modifications.
As of WorkSite 8.5 and later, Outlook’s FileSite views are defined in vdm files. As part of installation on a given machine, these five files are stored in the program folder, e.g. C:Program FilesInterwovenWorkSiteiOutlook. Never delete these files. Their names and uses are:
- FileSite Default View – NRTView.vdm
- FileSite Email View – NRTEmailView.vdm
- FileSite Worklist View – NRTWorklistView.vdm
- Search Document View – SearchDocumentView.vdm
- Search Email View – SearchEmailView.vdm
When a particular user first launches FileSite, these five files are copied to that user’s profile folder. That’s where you located the views.vdm during the earlier troubleshooting: “Documents and Settings\<username>\Application Data\iOutlook”.
As long these local vdm copies exist, FileSite uses them instead of referring back to the main program folder. If/when you delete them as part of troubleshooting, a fresh copy will be taken from the program folder. When the user visits a container for the first time on this machine, Outlook learns that the view’s layout is defined by the appropriate vdm file for that container type according to FileSite. In concrete terms, when visiting a folder with an email address, FileSite tells Outlook to use NRTEmailView.vdm.
Any/all user changes to a view on a specific folder, e.g. a WorkSpace search folder or the FileSite Document Worklist View, this change is stored in the views.vdm file.
Getting hands-on with the vdm files
As I said, don’t delete the main copies of the vdm files stored in the program folder.
If you’ve found that deleting only the views.vdm fixed the problem, then it was something either user-driven or a misbehaving Outlook add-in.
If the problem was resolved after deleting views.vdm and the five iManage vdms, then likely the unwanted view layout had been saved inadvertently to the user’s local copy of that vdm.
If the problem recurs frequently and you can determine that it’s not the user’s <ahem> fault, then ping us at Cersys and/or contact iManage support.
Similar topics in the Cersys Blog: