Skip to main content
September 11, 2009
Question

verity do not start after coldfusion upgrade from 7 to 8 on windows 2003 server

  • September 11, 2009
  • 1 reply
  • 1140 views

I had upgrade coldfusion from 7 to 8 on windows 2003 server with IIS 6 in malty server version. Everything works fine but no verity.
Verity cannot start automatically. I went to the server and start it manually by clicking on the .exe files.
The verity had open the command prompt window and started, but search services did not show up in the services list.
If I just close the command prompt window, it wills shutdown the verity service. If verity can run, when manually started, why it wound start with coldfusion??
I did not have any error during installation. Everything seems like installed successfully and I had reinstalled it twice with the exactly same result.
I already install the coldfusion 8 with this installation file on my testing server and everything works correctly up there…
Please help, I ran out of ideas.

    This topic has been closed for replies.

    1 reply

    Inspiring
    September 11, 2009

    Is anything being logged during CF start-up which might point to a problem?  If you're running on Windows, is anything going in the event log (is there an equivalent of same on *nix systems?  I presume so)?

    Is it that Verity isn't starting (like the service is failing to start), or there's just some disconnect between CF and Verity?  Have you checked that CF is sending Verity requests to a port Verity is listening on?

    --

    Adam

    September 14, 2009

    This is windows 2003 server with IIS. In event logs I do not see anything related to verity.

    Verity cannot start automatically but I can start it manually and it will be working until command prompt window is open.

    In the verity status log all verity processes starting and the next minute shutting down…

    If these is disconnect between CF and Verity, how they can work fine when I start Verity manually?