Cluster Model Viewer Timeout

Hi,

I am trying to browse a clustering model and encounter the following timeout error:

XML for Analysis parser: The XML for Analysis request timed out before it was completed.
Execution of the managed stored procedure GetNodeGraph failed with the following error: Exception has been thrown by the target of an invocation.Microsoft::AnalysisServices::AdomdServer::AdomdException.

Is there anything I can do to change settings to enable viewing of this model? Or, perhaps we have too many attributes in the model?

Thanks.

Please try the following:

In BI Dev Studio, go to the Tools menu and select Options\Business Intelligence Designers. Change the value of the Query Timeout to some larger value (600 would be a good start)

|||

Excellent, thanks Bogdan! That worked perfectly. For clarification, it's:

Tools --> Options

--> Browse left-side tree in the pop-up window to Designers --> Analysis Services Designers --> General

cluster error

We have a one node cluster that is receiving the below error messages in the cluster.log and the Event Viewer. In the SQL Server 2005 SP2 job that fails we receive a slighlty different message. The OS is Windows 2003 SP1. This is not a 64-bit box. We have checked the permissions of the cluster service account in SQL Server to be sure they are correct. Can anyone please help with this issue.

00000a0c.0000089c::2007/06/12-12:51:27.459 ERR SQL Server <SQL Server>: [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed
00000a0c.0000089c::2007/06/12-12:51:27.459 ERR SQL Server <SQL Server>: [sqsrvres] printODBCError: sqlstate = 08S01; native error = 2746; message = [Microsoft][SQL Native Client]TCP Provider: An existing connection was forcibly closed by the remote host.

00000a0c.0000089c::2007/06/12-12:51:27.459 ERR SQL Server <SQL Server>: [sqsrvres] printODBCError: sqlstate = 08S01; native error = 2746; message = [Microsoft][SQL Native Client]Communication link failure
00000a0c.0000089c::2007/06/12-12:51:27.459 ERR SQL Server <SQL Server>: [sqsrvres] OnlineThread: QP is not online.
00000a0c.0000089c::2007/06/12-12:51:27.459 ERR SQL Server <SQL Server>: [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed
00000a0c.0000089c::2007/06/12-12:51:27.459 ERR SQL Server <SQL Server>: [sqsrvres] printODBCError: sqlstate = 08S01; native error = 0; message = [Microsoft][SQL Native Client]Communication link failure
00000a0c.0000089c::2007/06/12-12:51:27.459 ERR SQL Server <SQL Server>: [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed
00000a0c.0000089c::2007/06/12-12:51:27.459 ERR SQL Server <SQL Server>: [sqsrvres] printODBCError: sqlstate = 08S01; native error = 0; message = [Microsoft][SQL Native Client]Communication link failure
00000a0c.0000089c::2007/06/12-12:51:27.459 ERR SQL Server <SQL Server>: [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed
00000a0c.0000089c::2007/06/12-12:51:27.459 ERR SQL Server <SQL Server>: [sqsrvres] printODBCError: sqlstate = 08S01; native error = 0; message = [Microsoft][SQL Native Client]Communication link failure
00000a0c.0000089c::2007/06/12-12:51:27.459 ERR SQL Server <SQL Server>: [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed
00000a0c.0000089c::2007/06/12-12:51:27.459 ERR SQL Server <SQL Server>: [sqsrvres] printODBCError: sqlstate = 08S01; native error = 0; message = [Microsoft][SQL Native Client]Communication link failure
00000a0c.0000089c::2007/06/12-12:51:27.459 ERR SQL Server <SQL Server>: [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed
00000a0c.0000089c::2007/06/12-12:51:27.459 ERR SQL Server <SQL Server>: [sqsrvres] printODBCError: sqlstate = 08S01; native error = 0; message = [Microsoft][SQL Native Client]Communication link failure

I'am having the same issue.|||

Moved to High Availablity forum...

(Please do not 'cluster' bomb so many forums with the same posting. Pick one, and give it time.)

|||What type of server (HP, Dell)?|||Anyone have any Ideas on this. I am having the same problem.

cluster error

We have a one node cluster that is receiving the below error messages in the cluster.log and the Event Viewer. In the SQL Server 2005 SP2 job that fails we receive a slighlty different message. The OS is Windows 2003 SP1. This is not a 64-bit box. We have checked the permissions of the cluster service account in SQL Server to be sure they are correct. Can anyone please help with this issue.

00000a0c.0000089c::2007/06/12-12:51:27.459 ERR SQL Server <SQL Server>: [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed
00000a0c.0000089c::2007/06/12-12:51:27.459 ERR SQL Server <SQL Server>: [sqsrvres] printODBCError: sqlstate = 08S01; native error = 2746; message = [Microsoft][SQL Native Client]TCP Provider: An existing connection was forcibly closed by the remote host.

00000a0c.0000089c::2007/06/12-12:51:27.459 ERR SQL Server <SQL Server>: [sqsrvres] printODBCError: sqlstate = 08S01; native error = 2746; message = [Microsoft][SQL Native Client]Communication link failure
00000a0c.0000089c::2007/06/12-12:51:27.459 ERR SQL Server <SQL Server>: [sqsrvres] OnlineThread: QP is not online.
00000a0c.0000089c::2007/06/12-12:51:27.459 ERR SQL Server <SQL Server>: [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed
00000a0c.0000089c::2007/06/12-12:51:27.459 ERR SQL Server <SQL Server>: [sqsrvres] printODBCError: sqlstate = 08S01; native error = 0; message = [Microsoft][SQL Native Client]Communication link failure
00000a0c.0000089c::2007/06/12-12:51:27.459 ERR SQL Server <SQL Server>: [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed
00000a0c.0000089c::2007/06/12-12:51:27.459 ERR SQL Server <SQL Server>: [sqsrvres] printODBCError: sqlstate = 08S01; native error = 0; message = [Microsoft][SQL Native Client]Communication link failure
00000a0c.0000089c::2007/06/12-12:51:27.459 ERR SQL Server <SQL Server>: [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed
00000a0c.0000089c::2007/06/12-12:51:27.459 ERR SQL Server <SQL Server>: [sqsrvres] printODBCError: sqlstate = 08S01; native error = 0; message = [Microsoft][SQL Native Client]Communication link failure
00000a0c.0000089c::2007/06/12-12:51:27.459 ERR SQL Server <SQL Server>: [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed
00000a0c.0000089c::2007/06/12-12:51:27.459 ERR SQL Server <SQL Server>: [sqsrvres] printODBCError: sqlstate = 08S01; native error = 0; message = [Microsoft][SQL Native Client]Communication link failure
00000a0c.0000089c::2007/06/12-12:51:27.459 ERR SQL Server <SQL Server>: [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed
00000a0c.0000089c::2007/06/12-12:51:27.459 ERR SQL Server <SQL Server>: [sqsrvres] printODBCError: sqlstate = 08S01; native error = 0; message = [Microsoft][SQL Native Client]Communication link failure

I'am having the same issue.|||

Moved to High Availablity forum...

(Please do not 'cluster' bomb so many forums with the same posting. Pick one, and give it time.)

|||What type of server (HP, Dell)?|||Anyone have any Ideas on this. I am having the same problem.

Closing IE Window used for exporting...

Taken from Reporting Services 2000 Help - 'When you click Export, the report
opens in a new browser window, in a viewer that is associated with the export
format. If in Step 2 you clicked TIFF, the report is displayed in a viewer
that supports TIFF file types.'
Is there any way to close this new browser window so it does not stay behind
and make the user close it?
Thanks for any input!Hi rheath,
Welcome to use MSDN Managed Newsgroup Support.
It is a by design issue in Reporting Service 2000 and was resolved in
Reporting Service 2005. If you try to export a report in Reporting Services
2005, the browser window will close and do not need to manually close it.
Thanks for your understanding.
Sincerely,
Wei Lu
Microsoft Online Community 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.|||Wei,
Do the reports have to be designed using Visual Studio 2005. I ask because
we are developing the reports using Visual Studio 2003 and depolying to a
Reporting Services 2005 server and I still get the browser window that does
not close when exporting.
Thanks,
Russ
"Wei Lu" wrote:
> Hi rheath,
> Welcome to use MSDN Managed Newsgroup Support.
> It is a by design issue in Reporting Service 2000 and was resolved in
> Reporting Service 2005. If you try to export a report in Reporting Services
> 2005, the browser window will close and do not need to manually close it.
> Thanks for your understanding.
> Sincerely,
> Wei Lu
> Microsoft Online Community 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.
>|||Hi Russ,
Thanks for the update.
I have tested on my side. I deploy a report to Report Services 2005 using
VS 2003. I get the browser closed when exporting.
Would you please test on another machine to access the report server and
try to export the report?
Does this issue occur?
Sincerely,
Wei Lu
Microsoft Online Community 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.