07-02-2013 12:45 PM
I just spent 5.25 hours on the phone with Act! tech support. Although they are nice, they really know nothing about their own product. What a huge waste of time! So after reinstall and every other possible change, 17, yes 17, restarts, I got excallated to a call tomorrow. My issue is this. Whenever I restart my computer, SQL Server (ACT7) stops working. so when I launch the app I get all the the annoying errors. I go to services and start SQL Server and the browser and I can launch without a problem. My issue is that I dis not buy a $411.00 software product to have to put bandaids all over it.
Is there a fix for this issue that in see affects hundres of users. Why does the service stop every time the machine is resarted? It's insane!
07-02-2013 12:55 PM - edited 07-02-2013 12:56 PM
Sorry you didn't have a good experience with customer support. I would assume after 5 hours there is more to it than this but one trick I've found works well is going into the properties of the SQL service and under the recovery tab, changing it to restart the service on first failure. On slower machines its good to change the wait time to 3 minutes or so.
Hope this helps or that support can help you tomorrow. Best of luck!
07-02-2013 12:58 PM
07-02-2013 01:42 PM
We, actually the Act! product team has verified that it's not simply a MS issue. There is a major error with Act! 2013 commuinicating with the database. This has been the subject os hundreds of recent blogs. We have reviewed all the event logs and there is nothing that indicates the root of the stoppage other than Act is communicating to the SQL DB to stut down at system shut down and not start up.
The good news is that I changed the startup status from automatic to auto delayed, and it works now. So there is something that happens within the Windows 7 environment, ONLY WITH 2013 premium, that causes the DB to fail. 2011 did not have this issue, because it worked until Saturday night when we went live on 2013.
07-02-2013 02:41 PM
07-03-2013 12:18 AM
My perspective would also have been that if the SQL service is not restarting with the PC, the root cause cannot be ACT! as the connection between the application and the ACT7 SQL instance is not attempted until the application is launched. If SQL does not crash until the application launch, then I'd seek to blame ACT!
...Having said this, I wonder whether it might be worth adjusting the 'Warmup' settings in ACTDiag (Server tab/Server Settings/Database Warmup tab). Here you can specify the number of most recently used databases that promptly open whenever SQL Server is started (to speed up the database load process). In this case, I assume that there is some ACT!/SQL activity engaged immediately upon the reboot.
I wonder whether it might have been worth disabling Automatic Warmup to see if that fixes the problem (or at least helps confirm whether the issues is directly ACT! related)?
09-02-2013 06:12 PM
There is a Startup process for Act! that pre-loads Act! into the local machine .NET Framework session cache to aid the JIT compiler. That's basically dev speak for "On system startup, Act! attempts o load aspects of itself into the local memory to speedup loading time".
If there is a systemic failiure to run either the SQL Browser or the SQL Server service itself, the pre-load sequence can in some casese error out thereby giving the impression that a on-load error has occured,
Essentially as others have suggested, the problems stem from the boot sequence causing delays for the SQLService to start within an "acceptable" time, this is why the Delayed Start allows the service to then start without hinderance.