Shell DefView Permission Denied

[Paul Baker]

I am implementing an IShellBrowser and using IShellFolder::CreateViewObject
to create a view of the Printers folder. Without going into details, this
did in fact generate a fully-functioning view of the Printers folder, with
only a couple of minor cosmetic issues.

I didn't change any code, I am using the same EXE. Recently, it started
misbehaving. I cannot be sure when it started, so I don't know if it is
related to a Windows Update critical update.

Now each time I create the view, there is an Internet Explorer Script Error
'Permission denied' at Line 219, Char 27 of printers.htt. It is the first
line of ShowInfo:

function ShowInfo() {
// this script updates the left info panel when you select
icons
var folder = FileList.Folder;

FileList has a CLSID of {1820FED0-473E-11D0-A96C-00C04FD705A2}, which in the
registry has a name of Shell DefView.

Web View is enabled and I have Windows 2000 Service Pack 4 with no
outstanding Windows Updates.

What is causing this? It it some misguided notion that because it is my
application that is hosting the view and not Explorer, that somehow there is
a security risk? How do I deal with it?

Paul

[David Lincoln]

I've had the same problem, and I'm pretty sure that it is to do with the SP that you have installed. Obviously, the "web view" panel
uses IE as its renderer, and MS have been making lots of changes to tighten up security generally. You may note that when you
implement IShellBrowser and IServiceProvider, you will get queried for lots of IIDs and CLSIDs that are not documented; they are
private MS interfaces. I'm pretty sure that one of these deals with this security issue.

I've posted on this board in the past about this issue with any luck :(

Perhaps someone else has an idea?

Cheers,
Dave.

"Paul Baker" <ask> wrote in message news:%23s6dyfG...@TK2MSFTNGP12.phx.gbl...

[Paul Baker]

Dave,

Thanks. It means a lot that someone has backed me up and that I am not
imagining it.

I do have Service Pack 4, and I believe it started happening around the same
time I installed it.

I tried it on a Windows 2000 Service Pack 3 machine with Internet Explorer 6
Service Pack 1 and there was no problem. I installed Service Pack 4, and the
problem immediately surfaced.

I think it's Service Pack 4, but I don't see a change in the release notes
that sounds related.

I don't have any intention of implementing any of the supposedly optional
undocumented interfaces.

Paul

"David Lincoln" <dave_...@hotmail.com> wrote in message
news:_XNRa.221458$1F6.2...@news.chello.at...