Announcement

**Ray** · Mar-11-2009, 03:07 AM

ASP.NET and IIS are notorious for useless error messages.

Check that you have the correct version of ASP.NET specified as described here.

Make sure you have the index files generated by Zoom, placed or uploaded in the same folder.

**Keith** · Mar-11-2009, 04:15 PM

I followed the steps outlined in the User Guide. ASP.NET version 2.057. I placed all search files generated in the folder where I installed the control. And, yes, "notorious for useless error messages" is a very accurate statement. I really think it has to be something simple, just not obvious to me as to what it is. I've checked security on the files and folder. I can get the JS version to work just fine, but would prefer the ASPX model.

**Ray** · Mar-12-2009, 05:54 AM

I suspect there may have been some configuration changes in your IIS setup, which is causing it to display this very brief error message rather than the more usual one (though I can't be sure, I've not seen it before anyhow).

However, we do have an alternative solution for using Zoom with an ASPX website. It involves using the CGI option and creating a ASPX wrapper page to call it. This is described in detail here and you may want to give this a try instead:
http://www.wrensoft.com/zoom/support/aspdotnet.html

**Keith** · Mar-13-2009, 04:51 AM

Thanks, Ray, I'll try this out. After stripping components from the page, one by one, I was able to isolate a form conflict with an imbedded form control added by a different product. With the imbedded form located in the master page definitions, it's hard to work around...hopefully, this CGI approach will work.

**Ray** · Mar-13-2009, 06:49 AM

See the bottom of the above linked support page. It provides an alternative to not using a <form> at all, that way you can have the search box inside another form without issue.

Announcement

ASP.NET "Internal error occurred."

ASP.NET "Internal error occurred."

Comment

Comment

Comment

Comment

Comment