This was to be a consideration at some point but we believed it had to do with file encoding/corruption issues so we tried some different things.

Except for some curious anomalies all is working at this point.

Bill

>I suppose it would be an idea to set customErrors=Off in web.config on production to get a better idea of the error occuring.
>
>
>>Anonymous access, no impersonation. We have only seen the generic ASP.NET "friendly" message at this point.
>>
>>Looks like it has to do with file corruption of some sort, possibly due to VSS. Unless a "fix" can be found, the HTML portion of the file will probably havce to be recreated.
>>
>>>Are you doing any impersonation or hardwired username passwords? What is the error message? Is it a generic error message? Do you allow detailed errors to the client?
>>>
>>>-R!