Time Out Error due to
Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached.
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
In SQL 2000
Expand a server group> Right-click a server, and then click Properties> Click the Connections tab.
Under Remote server connections, in the Query time-out (sec, 0 = unlimited) box, type or select a value from 0 through 2147483647 to set the maximum number seconds that Microsoft® SQL Server™ will wait before timing out.
In SQL 2005 or higher Version
Now you want to change the server property and for doing the same you needs to follow following steps;
1. Connect to SSAS services using SSMS and right click on instance name and select "Properties" option.
2. When you click on "Properties" option, you will get "Analysis Server Properties" window. Check the checkbox "Show Advanced(All) Properties" and go to the property named "ExternalCommandTimeout". You will find the default value as 3600 sec. Change the value as per your requirement and click OK button.
You do not need to restart services after changing the value of property.
After changing property, your cube processing will not fail till the value you have set for ExternalCommandTimeout property.
Source:http://sapost.blogspot.in/
0 comments:
Post a Comment