I'm getting a similar issue. We're using CuteEditor in a section of our site that is password-protected. I'm getting the same exact error detailed in this thread from the .NET forum.

 

Is there a fix for the ASP Classic version of CuteEditor? I couldn't find anything that looked similar.