Whenever i go to my url to access the DSS it says that it cannot connect to the server. It still brings up the login window, but wont actually log in.
In order to log in i have to remote into my server, stop all 6 SS services (5 backend, 1 apache) then restart them in order. Then I can log in no problem and the system works fine.
Try the same thing the next day, and I have to restart the services again before I can log in.
There is a fault tolerance mechanism built in to the TEM SUA (DSS SAM) system such that if the database server becomes unavailable or if the services can no longer authenticate to the database, the services will shut down rather than continue to churn on the box. So if the services appear to stop for no apparent reason (i.e. they don’t show “Started” in the Services snap in), it may be because some event interrupted their connection to the database overnight.
However, you stated you have to “stop … then restart them” suggesting that they are still running, but have become unresponsive. If this is the case, I suggest you open a support case and attach your server logs so we can help diagnose what’s going on.
I am experiencing the same issue (version 1.3.1.597), however not with as regular a frequency. There are times when running large reports (i.e. queries in excess of 1,000,000 results) that the “Results” show a number, but the gui never populates, and then I start getting “lost connection to the server” messages. The only way to recover fully is to stop and retart the apache and backend services. Was anything ever discovered on this issue?
I checked out server and somehow the DSS services got installed as my user rather than local system (sounds like a flaw in the installer if I ever did hear it). My user of course has a timeout as to how long it can run on a server. I switched them all over to local system and its as good as new.