Similar issue here with v2. This is a clean install on a new machine. Windows 2003 server. I can start the service manually without a problem from the services.msc window.
When the machine starts, the service does not work. The windows event log gives Event ID 7009 Type: Error Timeout (30000 milliseconds) waiting for the Anti-Spam Smtp Proxy service to connect. 30,000 miliseconds is 30 seconds. Is that not long enough for the service to start completely with 5 workers? Seems like it should be. Anyone know where this threshold might be able to be increased. The exact same configuration (from an image) of windows 2003 server auto starts 1.4x just fine. On Thu, Sep 10, 2009 at 4:53 PM, Dave Watkins <[email protected]> wrote: > Don't have a forum logon and can't read the post without one seemingly, but > I suspect I'm seeing something similar. > > ASSP here doesn't start correctly as a service after a system reboot, but I > can start it manually after the system is up and running as a service. My > guess is that when the system originally boots all the disk activity is > causing ASSP to do as Grayhat says, it's not getting back to the SCM in time > and timing out (although I would have thought it would still actually be > running in background and just the SCM display would be wrong but that's not > the case) as it's taking longer to read all the disk data and load. > > I suppose another option may be to launch a "service control" thread when > running as a service rather than having it split out to a separate file. No > reconfiguring would then be needed. > > Dave > > -----Original Message----- > From: GrayHat [mailto:[email protected]] > Sent: Friday, 11 September 2009 4:39 a.m. > To: ASSP development mailing list > Subject: Re: [Assp-test] ASSP as a service (service did not respond) 1053 > > >> imVHo ripping the assp daemon/service code to a separate > >> module shouldn't be so difficult but for *sure* would help a lot > > > And then producing problems for several hundreds of running > > ASSP installations to solve a problem for one installation which > > is not even diagnosed properly? Ok, forget my asking. > > uh "producing problems" ? Nay Sir, all in all with version changes > and during the time we all had to make adjustments to our setups > so it would just be a matter of placing instructions for the people > updating to such a version (and such a thing was done in the past) > but, by the way, it's just an idea and if you don't like it there's no > need to react this way... oh well :P > > > > ------------------------------------------------------------------------------ > 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 > > > ------------------------------------------------------------------------------ > 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 > ------------------------------------------------------------------------------ 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
