Chris
This stuff is outside my area but in connection with other
issues, some information was posted. Could it be relevant here?
****************************************
Jonathan Woodward reported, "We finally tracked it down to
the security settings on the webserver where the application and
OLH files resided. The webserver was blocking use of .xml, .js, and
a few other important file types, thus causing the TOC to not load
properly when accessed from the application."
Jennifer Foster reported, "The problem was that IIS 6 doesn't
serve unregistered MIME types. For some reason, .js was not
registered in IIS. To fix this, I just allowed all unregistered
MIME types but doing an * as the extension and putting them as
application/octet-stream. A better solution, though, would probably
be to just register the .js file extension."
Help others by clicking Correct Answer if the question is answered. Found the answer elsewhere? Share it here. "Upvote" is for useful posts.