I have faced "Timeout expired" Problem when i was processing cube in DTS package,
I have change the following paramter on AS,

Step 1 : Go to AS Properties.
: Go to Processing tab
: remove the Server Timeout checkbox if it is set true.

After changing this setting I have never got time out problem.
If it may help you.

Kris






"Varad" <varad01 (AT) hotmail (DOT) com> wrote

This might not apply to you but if you wrap up Analysis Services processing
tasks in an inner package (i.e. you have a set of processing tasks in one
"inner" package, then include that package in an outer package and try and
schedule the outer package) then you'll experience problems scheduling it -
it won't get executed. Can anyone at Microsoft confirm that this is a known
bug?

"Varad" <varad01 (AT) hotmail (DOT) com> wrote

The DTS OLAP Processing task is written in VB6. As such, it is single
apartment-model threaded. This means that it must be created on the DTS main
thread. And any task that attempts to invoke it and/or touch any of its
properties must be on the main thread. My guess is that somewhere in your
package hierarchy you have a task that is not invoked on the main thread and
thus the task fails -- sometimes you just get a unhandled access violation
in the main process.

When the designer creates a DTS OLAP Processing task it automatically sets
the "run on main thread" attribute, but it does not handle the
package/subpackage invoking; nor if you have another task that touches the
Processing task's properties.

This is the reason that the SSABI DTS packages do all of their OLAP work in
separate packages and are not invoked as subpackages, but rather use the
Process Command Line task (invoke a dtsrun command line) and startup the
package in it own process.
--
Dave Wickert [MSFT]
dwickert (AT) online (DOT) microsoft.com
Program Manager
BI Practices Team
SQL BI Product Unit (Analysis Services)
--
This posting is provided "AS IS" with no warranties, and confers no rights.

"James Taylor" <james.taylor (AT) dwl (DOT) co.uk> wrote