> Is this the reason for the trouble the user have, or is it just a > general description of the mechanism? > Hundred of installations are running ASSP as a windows service, there > were no bug reports in this regard.
Both :) see, the cause of the issue is the fact that ASSP calls the SCM later-on, after loading stuff and so on; now the simple solution (for ASSP) would be calling the SCM earlier; while the real cause of the issue, given the (few if any) informations may probably be some "big" file being loaded by ASSP on startup, a network issue (which cause ASSP to take too much to reach the "service" code) or filesystem issues (e.g. corrupted FS); in a past I suggested moving the ASSP service/daemon code in a separate module (e.g. asspdaemon.pl) which should then handle all the service/daemon stuff and in turn launch the assp process, monitor it and restart it if/when needed (and btw that daemon process should also signal assp to stop in case a stop signal -either service or daemon- is received); imVVVho such an approach would SOLVE such issue once and forever ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Assp-test mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-test
