Defragment index on fact tables - Server Time Out

[former_member244885]

Whenever I attempt to Optimize my model with "Index Defragmentation" checked I receive a "Server Time Out" message:

Full Optimize, without checking Index Defragmentation, completes without issue.  I have a feeling it is actually completing with Index Defragmentation on SSAS, and this is just a front end connection issue.  Has anyone seen this, or have a fix?

[Former Member · Accepted solution]

Hi Jon,

try increasing the executionTimeout to 36000 in web.config of all appservers restart IIS and see if after it work.

I've had this issue also connected with issue between dbserver and appserver.

Regards

     Roberto

[former_member244885 · Accepted solution]

I changed the setting and re-ran with Index Defrag.  It ran successfully, however the job completed in under 10 mins this time though, LOL (smh).

Thanks for the reply though, it totally makes sense and everyone should probably increase that timeout either way.

[former_member244885 · Accepted solution]

I experienced the timeout issue again today.  Is anyone else seeing this issue / have any other suggestions or workarounds?

[Former Member · Accepted solution]

I have seen this issue and it's not clear what is causing it but it looks like a front end issue as the actual process on the server doesn't even start when this happens.

It normally goes away next time you try.

How often does that happen?

[former_member244885 · Accepted solution]

This happens for me more often than not if I check both compress and index defrag.

[april_shultz]

Hey Jon,

Double check the web config file and make sure the change you made is still there. I have seen in the past where a customer makes a change and the changes are not reflected for some odd reason.

If you guys have multiple web servers make sure you set each web config file for each server.

If that is not it do you see any thing relevant in the application/system event logs on either the app or db server?

Thanks

April

[former_member244885]

Hi April,

I have double checked the web config file and verified the change is still there.  (I also performed IIS reset and server reboots to validate).  I did verify this on the two web servers we are running.

I've been able to work around this by first running full optimize without compress or index, and then re-running with compress and index a second time.

I'll post any error messages I see the next time I get the issue.