Custom Field Crashes Cube Build

[Darrell]

I wanted to create what I thought would be a simple custom field that I could
use in Data Analysis views to filter out inactive projects by assigning a
lookup table containing only "Yes" and "No". I created the lookup table and
then created the custom field selecting "Project" for the "Entity" and "Text"
for the "Type". I assigned the lookup table, set a default value and selected
"Only allow codes with no subordinate values.†I then populated the field in
my schedules.

When I add this field to the Project cube dimension it builds OK and I can
see it in the “Project Non Timephased†cube. However, if I add it to the
Assignment cube dimension it causes the cube build to fail. I assumed that
since the MSP Project Timesheet cube contained the “Project List†that it
would accept “Project†cube data. So my question is – what should I be doing
differently to create a custom field that will allow me to filter out
“inactive projects†from my Data Analysis views in the same manner that I can
now filter out “inactive resources�

Darrell

 

[Marc Soester [MVP]]

Hi Darrel,

generally I would say that you set up everything just fine. If there would
be a name correlation MS project would have told you when you created the
custom field.

I have not come accross this issue to be honest, could you check out the
event log and PS Queue and send the errors that you see regarding the cube
build.
thanks
Marc

 

[Gary L. Chefetz]

Darrell:

Any chance you have a leading or trailing space in the value list? What name
did you give this field? A bad name might cause this as would errant
character data in the value list. If you can't islolate a cause along these
lines, try deleting the lookup table and field and try creating it again.

--
----------
Gary L. Chefetz, MVP
MSProjectExperts
Project Server Consulting: http://www.msprojectexperts.com
Project Server Training: http://www.projectservertraining.com
Project Server FAQS: http://www.projectserverexperts.com
Project Server Help Blog: http://www.projectserverhelp.com

 

[Darrell]

Marc,

Thx for the reply. I should clarify what I mean by "causes the cube build to
crash" it stops building because it runs out of memory when building. I will
get the actuals from ops and post them.

Darrell

 

[Darrell]

Gary,

Thx for the reply. I checked for spaces in the list and found nothing, again
it is simply a "Yes" and "No" value list. I should add that by "causes the
cube build to crash" that it actually runs out of memory while building and
stops. After the first time it did this I added it just to the Project
Dimension and Project Non Timephased cube and it built OK. When I then
attempted to add it to the Assignment dimension it again began to grow a huge
file size and ops killed it. I will get the actuals and post them.

Darrell

 

[Darrell]

Gary,

The custom field name is "Project Active" do you think that will have an
impact?

Darrell

 

[Gary L. Chefetz]

Sometimes you run across hidden reserved names. Does the same thing happen
when you call it Foo? I don't think this is it now that you've added "runs
out of memory," but what do you mean? Are you referring to drive space? If
so I think there are some known issues with temp db bloat. If you're talking
system memory, then you should open a support ticket.

--
----------
Gary L. Chefetz, MVP
MSProjectExperts
Project Server Consulting: http://www.msprojectexperts.com
Project Server Training: http://www.projectservertraining.com
Project Server FAQS: http://www.projectserverexperts.com
Project Server Help Blog: http://www.projectserverhelp.com

 

[Darrell]

What happened when the custom field was added to the Project, Assignment and
Timesheet dimensions was the "tempdb" being used to build the cube grew to
80GB and caused the application to crash when there was no more disk space.

When the custom field was added to just the Project Dimension the cube build
was succesful.

When it was added to just the Assignment dimension the "tempdb" began to
grow again and the process was stopped at 65GB so that it would not cause
another crash.

I will try renaming it to see if that helps, as well as researching file
bloat.

Darrell

 

[Marc Soester [MVP]]

Hi Darrell,

it seems that you have the "tempDB" bug this is a known issue whereby the
tempdb grows and grows and grows. I would recommend that you ensure to have
SP1, Infrastrucutre Update and Cumulateive December update installed for
Project Server.

In one of the last posts, Gary chefetz also suggested that SQL SP3 by
resolve some if this issue. Hopefully that will resolve the issue and
hopefully SP2 will finally resolve this issue all together ( haveing said
this, it is not just Project Server, there seems to be a SQL bug behind this
too).
Hope this makes sense
thanks

 

[Gary L. Chefetz]

I think this is mostly a SQL bug. One of the strategies is to make sure that
you have selected earliest project start and latest project finish date as
the time parameters for the cube build.

--
----------
Gary L. Chefetz, MVP
MSProjectExperts
Project Server Consulting: http://www.msprojectexperts.com
Project Server Training: http://www.projectservertraining.com
Project Server FAQS: http://www.projectserverexperts.com
Project Server Help Blog: http://www.projectserverhelp.com

 

[Darrell]

Marc & Gary,

Thx for the information. We just installed the December CU, we were
up-to-date except for that CU when we tried to add the custom field. I think
I will wait until we install SP2 and try to build the cube again with the
custom field in the Assignment group to see if it will work.

Thx again,
Darrell

 

[Gary L. Chefetz]

Darrell:

BTW, with the December CU installed, you have most of SP2.

--
----------
Gary L. Chefetz, MVP
MSProjectExperts
Project Server Consulting: http://www.msprojectexperts.com
Project Server Training: http://www.projectservertraining.com
Project Server FAQS: http://www.projectserverexperts.com
Project Server Help Blog: http://www.projectserverhelp.com