![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
We're using the Office Web Components (vers. 11) pivot table inside Internet Explorer as a client for our OLAP power users. They are pretty much free to drill all dimensions, and sometimes they come up with a combination that results in a long query. When that happens, they get shown the hourglass for ever. It looks to me like a timeout is happening somewhere along the chain between Internet Explorer, OWC, Pivot Table Services, IIS, OLE DB 9.0, and SSAS 2005. How can I find out what is happening ? Is there way to force a timeout in IIS so that Internet Explorer will show the hourglass for a maximum of 3 minutes (instead of for ever) and then come back to the users ? Thanks for any help, this is a big issue for us. |
#3
| |||
| |||
|
#4
| |||
| |||
|
|
Hello Pat, Thank you for using Microsoft MSDN newsgroup. I understand that you'd like to show pivottable to timeout when the query take too much time. If I'm off-base, please let me know. You may want to configure the timeout property of Pivottable to see if it resolves the issue. You could use some script in the page hosting pivottable. script language=VBScript Dim oPivot Set oPivot = PivotTable1.Object 'Set the timeout to 60 seconds oPivot.Connection.CommandTimeout = 60 /script Also, there is ServerTimeout property of AS 2005 that you could change for the query timeout in AS server. However, it is not recommended to change the value to too small because there shall be long queries. As I know, there is <SessionTimeout> configuration in msmdump.ini if you use HTTP Access to AS 2005: http://www.microsoft.com/technet/pro.../httpssas.mspx Since pivottable is a Activex control running on client side, I would think IIS related configurations shall not affect its timeout behavior. Please check if this helps. If you have further questions, please feel free to post back. Best Regards, Peter Yang MCSE2000/2003, MCSA, MCDBA Microsoft Online Partner Support When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from your issue. ================================================== === This posting is provided "AS IS" with no warranties, and confers no rights. |
#5
| |||
| |||
|
#6
| |||
| |||
|
|
Hello Pat, Thank you for your update. I took sometime to build an enviroment to test the issue on my side and I also found commandtimeout property does not take effect. Then I used the following connection string for pivottable and it does still does not take effect: Provider=MSOLAP.2;Data Source=myServerName;log file=c:\mymdx.txt;Initial Catalog=FoodMart 2000; timeout=5; I suspect there might be issues between OWC pivottable/AS 2005. To further troubleshoot the issue, I need more information of your environment, will you please get the following information? a. Click Start, click Run, type msinfo32 and press Enter. b. After the process of collection system information finish, select Save from File menu and save this nfo file c. Please email this nfo file to me at petery (AT) microsoft (DOT) com I'm looking forward to your update. Thanks. Best Regards, Peter Yang MCSE2000/2003, MCSA, MCDBA Microsoft Online Partner Support When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from your issue. ================================================== === This posting is provided "AS IS" with no warranties, and confers no rights. |
#7
| |||
| |||
|
![]() |
| Thread Tools | |
| Display Modes | |
| |