Can anyone confirm or deny _for certain_ that using a server's IIS for other
content in addition to Sharepoint would contribute to instabilities in
Sharepoint?
IE, let's say you have F:\somefolder and you use Frontpage on some client
machine to edit the files in there. There are .htm, .js and .class files
for the most part, and it serves up static content. IIS's virtual directory
called "somefolder" then points to F:\somefolder so that when you go to
http://server/somefolder, it brings up that content.
[another example would be the MacawSpsUtil, which I assume lots of people
use without problems]
Anyway, we recently moved a lot of content of strictly IIS-based content to
the server that also runs our SPS server and we're having to restart the
services every 2 or 3 hours. I don't know if it's related or not and
frankly, SPS doesn't give much by way of log files to try and determine the
issue.
In the W3SVC logs, the entries immediately before the requirement of a
restart don't give any consistent results. Each time, it's a different
file, user and directory being involved, and they don't necessarily show
access for the non-SPS content near it.
In the event logs, there are only entries for me stopping and starting the
services.
Does anyone know any better ways to troubleshoot? I'm almost tempted to
live with the instabilities of a new beta product rather than deal with this
headache any longer.