WDS 3b2 - file type list is truncated
On one of the machines where I have installed the second beta of WDS 3, the list of file types on the advanced page stops at "mda". No extensions below that in the alphabet even appear, nor can I add them manually (when I do so, it seems to work but the the added extensions doesn't stick - the next time I open the file types setting page, it is again truncated).
Running on XP home SP2 - and by the way, all the registered file types show up properly when viewed from the menu in an Explorer window. Thanks for any help
[545 byte] By [
rolian] at [2008-2-15]
What did that investigation find? Because I'm having the same problem.
I also had WDS 3.0 beta installed, I uninstalled it, rebooted, installed WDS 3.0 RTW, and for me the file type list stops at .bat; extensions that alphabetically come after that can be added, but they don't "stick".
E.g., I install the MSG iFilter (by Microsoft) from http://gallery.live.com/liveItemDetail.aspx?li=8bff8943-4613-4efb-a8e6-b17dc8c086e5&l=3, it SHOULD add .msg to the file types list, but after installation completes, it's not on the list.
I had this same problem with the beta, the file type list stopped at .bat then also.
Any tips on truly and thoroughly uninstalling so there's no trace that WDS was ever on my system, so I can reinstall cleanly? Assuming the beta left cruft in the registry that I have to remove by hand, what keys should I be looking at?
--Peter
I'm also seeing this problem, first when upgrading to 3.0 (release) and still with 3.01. The File Types list ends at 'asax'.
OS: Windows XP SP2 (with all updates)
Edward Leigh
This sounds like an registry issue.
Using regedit, in the HKEY_CLASS_ROOT section, what is the next file extension entry under .asax? (I see .asc on my machine)
The next extension listed is '.asc' and, as Ilia hinted, it had no permissions set. After checking 'Full Control' (for Administrators), WDS then showed more extensions under File Types.
But then it stopped at '.bat' and, yes, the next extension ('.bcp') also had no permissions set.
Then '.doc', '.dot', '.mdb', '.pot', '.pps', '.ppt', '.rtf', '.xlb', ,'.xlc', '.xls', and '.xlt' where the next problem extensions. In each case the key had permissions set, but the PersistentHandler subkey's permissions had no users or groups associated with it. I added the group Administrators to the subkey, setting no permissions initially. On re-examining the permissions, all permissions had been granted to Administrators but were not editable, and permissions had also appeared for my own user account, 'RESTRICTED', and 'SYSTEM' - all uneditable.
I searched for problems associated with the PersistentHandler subkey and turned up a long discussion on how these 'missing' registry permissions were blocking installation of WDS 3.0:
http://www.office12watch.com/desktop-search-error/
Clearly this is still an unsolved bug in 3.01.
I have Office 2003 installed, along with OneNote 2007.
Thanks for your assistance in pointing me towards the solution.
Regards,
Edward
