Hi
Its me again.
We have been trying to investigate and have found the following -
Looks like the Site Usage Report function calls a series of Stored Procs in Content and SSP DB's. In this case, it fails in SSP DB.
The error logs report Connection Timeout as follows -
App=Windows SharePoint Services;Timeout=15' ConnectionState: Closed ConnectionTimeout: 15
There's a property called 'database-connection-timeout' which can be set using 'stsadm'. We have tried to change this from default '15' to '30' and then '45' and then '60'. Originally it was failing on 'dbo.proc_ANL_WebTopClickthroughPagesByHits'.
With a timeout of '30' it progressed further and was failing on 'dbo.proc_ANL_WebSummary'.
With a timeout of '45' it progressed further and was failing on 'dbo.proc_ANL_WebTopReferrersByHits'
Sadly, the stsadm is not setting the timeout to '60' although it does report a successful run of the command (stsadm -o property...).
The silly thing is that the Usage Report for the 'Site Collection' runs fine and that has a bigger footprint.
We are stuck with this completely.
We have re-started the Timer service as well, but to no avail and are going to run the Config wizard later on.
Can someone pl help/advice.
thanks