Anyone know what this error means? I captured it through Profiler.

Errors in the metadata manager. The server failed to create the processing
schedule, possibly due to concurrent metadata changes.

I'm only running a single job, nothing else is touching the cube.

What operation were you trying to perform and how complex is your design?

This error message occurs in two possible situations:
1. While building the schedule of objects involved in the operation, the
server tries to resolve an object and cannot find it -- so perhaps somehow
an object got deleted while the schedule was being built.
2. The scheduler tries to find dependencies and acquire objects in a loop --
if the first pass finds more objects are needed then it will add them in the
second pass, etc. If after 5 attempts the schedule still cannot be built
because more objects need to be added or they cannot be acquired, then it
fails with this error...

I can't guess which one of these you are running into but I'd suggest
looking to break down your operation (if it is a processing task) into
smaller pieces.

HTH,
Akshai
--
Try out the MSDN Forums for Analysis Services at:
http://forums.microsoft.com/MSDN/Sho...ID=83&SiteID=1

This posting is provided "AS IS" with no warranties, and confers no rights
Please do not send email directly to this alias. This alias is for newsgroup
purposes only.

"Jesse O." <jesperzz (AT) hotmail (DOT) com> wrote

We use AMO, it's fairly complicated.

First step is to delete partitions that are greater than 90 days old.
Usually one per day. These are each wrapped in a transaction.

Second step is to process the dimensions one by one. This is where the error
is thrown. These are each wrapped in a transaction.

Third step is to create and process partitions. If the partition already
exists it is deleted and recreated. These are each wrapped in a transaction.


My guess is to move the deletion of partitions that are greater than 90 days
old to the very last step.

I also noticed that when the job fails, the transactions actually dont
commit. I can't figure out why. It's like there's a transaction wrapped
around the entire thing.

Thanks for your reply, I can't wait to get these little kinks worked out.




"Akshai Mirchandani [MS]" <akshaim (AT) online (DOT) microsoft.com> wrote

And do you have lots of partitions/measure groups that depend on the
dimension being processed? Is the error being raised consistently on the
same dimension?

Thanks,
Akshai
--
Try out the MSDN Forums for Analysis Services at:
http://forums.microsoft.com/MSDN/Sho...ID=83&SiteID=1

This posting is provided "AS IS" with no warranties, and confers no rights
Please do not send email directly to this alias. This alias is for newsgroup
purposes only.

"Jesse O." <jesperzz (AT) hotmail (DOT) com> wrote

Right now just a single measure group with about 100 partitions.

And it happens consistently, not 100% of the time however. That is what's
odd. Driving me nuts.



"Akshai Mirchandani [MS]" <akshaim (AT) online (DOT) microsoft.com> wrote