We had a DNN with DMX installed on a development VM. We had the same problems with pdf searching that so many people have had, but resolved them with downloading the appropriate filters.
We then downloaded the VHD that that had the development environment, and a hosting company created a new virtual machine for our client from the vhd (now the production environment). It was virtually cloned, so everything should have been the same.
Except that the client recently installed some Windows updates. Which actually made the site go down, we had to change the web.config file to specifically reference the name of the server instead of the "generic" reference of (local). We have no idea why this became a problem, as previously we had not had to specify the name of the server in the web.config file.
Now the pdf search isn't working again. I don't know if the Windows updates could have caused the problem, but it's my only theory. Or something happened when the new VM was created, but I don't see what. There should be the exact same filters and service packs on the new VM, as it was cloned from the old one.
What can I look for to diagnose the problem? We're on Windows 2003RS, Servive Pack I, DNN CE version 6.02, DMX version 6.0.3.
Any help/suggestions appreciated, this site is supposed to go LIVE except people can't search for document content.
|