by Mike May >> Wed, 11 Oct 2006 10:28:20 GMT
Having just fixed a problem with a Jade web site I thought I'd share my findings.
After a server failure, we moved all our Jade databases to a fresh server. We did this by simply copying the database folders across. Whilst Jade itself worked correctly on the new server, Jade web sites gave us HTTP 500 - Internal Server Error - responses. I (eventually) ran Sysinternals FileMon and saw that IIS was looking for msvcr71.dll. It turns out that this file is (of course) in the Jade bin folder. The Jade installation procedure adds the Jade bin folder to the environment path, so the file will be found by any process that needs it. However, we hadn't done any installation of Jade on the new server, so the path hadn't been updated. Temporary solution was to stick msvcr71.dll into system32; proper solution is to update the environment path and restart the server.
Hope that's of use to someone one day.