Cube Processing Error

Hello,
I'm getting an error while processing some cubes. "Cannot lock object
'lazy processing token'. Error: Connection to the server is lost." This
only occurs while processing certain cubes on the 64-bit version of AS
and occurs just after the 'Writing Aggregations and indexes' portion of
processing.
Any recommendations or ideas would be appreciated.
-Justin
Justin,
I am having the same problem. Let me know if you were able to find a solution.
Luke

Quote:

Originally posted by Justin
Hello,
I'm getting an error while processing some cubes. "Cannot lock object
'lazy processing token'. Error: Connection to the server is lost." This
only occurs while processing certain cubes on the 64-bit version of AS
and occurs just after the 'Writing Aggregations and indexes' portion of
processing.
Any recommendations or ideas would be appreciated.
-Justin

|||

Quote:

Originally posted by Justin
Hello,
We also have same problem. "Cannot lock object
'lazy processing token'. Error: Connection to the server is lost." We are using separate servers, one for sql (64-bit MS SQL server on Win2003-Microsoft SQL Server 2000 - 8.00.760 (Intel IA-64)
Feb 6 2003 16:07:24
Copyright (c) 1988-2003 Microsoft Corporation
Enterprise Edition (64-bit) on Windows NT 5.2 (Build 3790: ) and another for AS server (64-bit AS on Win2003-Microsoft SQL Server Analysis Services
Microsoft Corporation Version: 8.00.382). And we are processing the cubes from 64-bit AS. Some of the cubes fail (not all of them). When we process the cubes from another 32-bit AS it doesn't fail. Do you have the similar system configuration?
When we redesigned the cube, which failing on 64-bit AS, did not fail..
-Selma

|||Our problem was most likely related to a firewall setting as described in an earlier post. The cube could process locally, or from a DTS package, but not remotely. I found out our firewall kills inactive connections after 30 minutes.
The cube processing only fails at the last second, after it has been giving status for the entire process. My guess is there are two connections opened; one is used to show status messages and is active throughout the process; not sure what the other one is used for, but it is inactive until the commit, which explains why our firewall is dropping the connection - and then the commit fails.
Luke

Quote:

Originally posted by Selma