The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
|
|
Query Timeout Expired
Posted: 22 Feb 10 10:57 AM
|
Client upgraded from 7.0 to 7.5.2. No problems in 7.0 environment.
New 7.5.2 environment upon upgrade.
SQL Server 2008 and SalesLogix Application Server on Windows 2008 R2 64-bit. 12 GB RAM
Query Timeout Expired has happened for the second time since upgrading 1.15.2010. Restarting the SLXServer service on fixes the problem. Looking at memory, 11.5 is used up before restart of service. Seems to run fine for about 2-3 weeks and then errors occur.
There is minimal customization. Has anyone seen this before? Any ideas on what to look for? Obviously a memory leak. Could this be a result of customization if it is happening on the Application Server?
Thanks in advance.
Daryl |
|
|
|
Re: Query Timeout Expired
Posted: 22 Feb 10 11:02 AM
|
You probably will need to do some logging when these errors ocurred.
Is the query being sent to the DB? Are there any locks on the DB or is it being returned right away, but still getting a timeout on the Client?
Also, queries are not ran through the SLX Server. The queries are parsed locally (For web clients by the Individual Web Server) and then ran directly against the DB.
Restarting SLX Server may be clearing up Lock on the DB....
Again, I would profile the DB and keep an eye out for Locks, and before Restarting SLX Server, make a note of which PIDs it has and what locks (if any it is causing).... |
|
|
|
Re: Query Timeout Expired
Posted: 22 Feb 10 11:44 AM
|
Update.
Of the 12GB of RAM, 10.5 was allocated to SQL Server so not much was available to anything else. Reduced the amount of memory available to SQL Server 2008 and we will see what happens. |
|
|
|
Re: Query Timeout Expired
Posted: 22 Feb 10 11:48 AM
|
| Thanks Raul. I will give this a try next time it happens so I have more info to act on. |
|
|
|
Re: Query Timeout Expired
Posted: 02 Mar 10 5:00 PM
|
Well it turned out Speedsearch was the problem. There were over 4,000,000 records in indexupdates. SpeedSearch uses this table to determine what to update when doing an incremental index update. I had to manually delete the records. A full rebuild should have deleted the rows but I suspect it was taking so long to do the delete that speedsearch was reporting the time out.
We found the error in the application event log on the speedsearch machine which was the clue. |
|
|
|
Re: Query Timeout Expired
Posted: 11 Apr 11 12:29 PM
|
We're having the same problem. Was there any difficulty/extra steps you had to take after deleting the records from indexupdates? |
|
|
|
Re: Query Timeout Expired
Posted: 11 Apr 11 2:45 PM
|
Yes. If you do not use S/Search (and 4M rows suggest the other person doesn't!) then you need to disable it completely.
update slxtriggers set enabled = 'F' where path = 'SlxSearchTrigger.dll'
S/Search should consume those entries - but if it's not running then the trigger will still operate (this is an SLX Trigger) and populate the table. Use "truncate table indexupdates" to delete all rows after disabling trigger (you should also stop s/search service).
If you want to enable it later on, just reverse step and reconfigure.
Regards
Mike |
|
|
|