iis security: Summary: I am trying to resolve a javascript security error in IE6,
that calls Word 2000, with a URL on our WebDAV server.
===============================================================================
Details: My ASP.NET application has a page called CaseDocuments.aspx
that provides the user the ability to click a link to open a document
from the web server. Clicking the link, streams the document from the
db to the http://server/DocumentControl/Documents dir, and the
following javascript is executed when the page is executed on the
return trip:

<script event="onload" for="window">
var wrd = new ActiveXObject("Word.Application");
wrd.Visible = true;
wrd.Documents.Open("http://server/DocumentControl/Documents/42.doc");
</script>

Setting the appropriate security settings on IE (Initialize and script
activex controls not marked safe, etc.) results in a document
successfully opening in some limited cases. In other cases, I get a
javascript error ("Permission Denied"). (In either case, the document
is sucessfully copied to the virtual directory, and is available if i
manually open word and point to that location. I can also browse the
directory, and open the document.)

The cases in which this is not successful, I think, are when the
client is running a specific combination of Word 2000, and
MSDAIPP.DLL. i have documented the combinations that are successful
or otherwise, and can provide them.

We have ruled out the server for now, b/c some clients are
consistently successful at retrieving documents while others are not.
This is where i fall short. The problem "feels" like it may be a tcp
header problem; ie, the correct combination of requests is not being
made, thus not being responded to.

Does this sound familiar to anyone? Any suggestions for a next step?
Can anyone recommend a good trace program? Any help or speculation is
welcome.

Thanks in advance.
Jim Little

Thanks for your reply!!

Registering the dll turned out not to be the problem. A nuance of the
way in which we launch Word has turned out to be the problem. We have
two configurations for our application; client and server on one
machine for demo purposes, and client and server on separate machines
for production. We set DCOMCNFG for the latter configuration, but it
caused some trouble with the former configuration.

In production, we lock an accout on the server for Word to run as. We
make the appropriate settins in DCOMCNFG, and this works fine.

In demo, we did the same thing not realizing that we ALREADY had a
user logged on; the person doing the demo. So the settings we made
prevented Word from "playing nicely", as described in my original
message. Once we resolved the DCOMCNFG settings, we were able to
resolve the problem.

Thanks again.

Hi Jim,

Based on my experience on this issue, you can follow the steps below to
register the msdaipp.dll.

1.In Windows Explorer, browse to \Program Files\Common Files\System\Ole DB\
and double-click msdaipp.dll.
The Caution dialog box appears.
2.Click Open With.
The Open With dialog box appears.
3.Click Other.
The Open With dialog box appears.
4.Browse to \WINNT\system32\ and double-click regsvr32.exe.
The Open With dialog box appears.
5.Make sure Microsoft Register Server is selected and click OK.
A message box appears.
6.Click OK.

Does this answer your question? Thank you for using Microsoft NewsGroup!

Wei-Dong Xu
Microsoft Product Support Services
Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.

Hi Jim,

Thank you for replying and the detailed information about this issue!

You are very welcome!

If you have any further question, please feel free to let me know.

Thank you once more for using Microsoft NewsGroup!

Wei-Dong Xu
Microsoft Product Support Services
Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.