Hello Gary,
I realize this post is a bit old, but I have a question about the kinds of problems you elude to.
We are using MSP2007 Enterprise Server and several projects on the server, and PWA by individuals to update tasks either directly or via time sheets.
3 of these projects use master files with 5 - 10 sub projects each.
I get the error message Hari started this thread with, but I get it "occasionally" and on a couple different sub files. What's more, the files being complained about do not exist in the file the error message calls out, in fact the file being called out as the "other" master this sub file is included into, is not a master but a standalone project file. So, I am confused by the error message.
A bigger issue we are having, is that we have alot of what appears to be dataloss when comparing what is submitted against tasks on timesheets to what eventually gets into the working & then published databases.
So, although the error does not seem to make sense, I was wondering if you know how this problem (should it really exist) potentially affect actuals work hours getting from time sheets into the working database?
One last thing to know, we are using Codeplex as a 3rd party SW.
Any suggestions / advice is welcomed.
Gary L. Chefetz [MVP] wrote:
You're setting yourself up for problems.
16-May-08
You're setting yourself up for problems. You can use cross project linking
for task dependencies without creating permanent master projects. To get a
master project view of things, you simply need to go to Project Center, hold
the ctrl key and select the projects you want to see in the master view, and
click edit. This will open a master project that you can simply choose not
to save. If you have smartly designed Project Center views using good
project level attribution you can make this very easy for your users to
create temporary master files for their viewing pleasure
--
Gary L. Chefetz, MV
MSProjectExpert
For Project Server Consulting:
http://www.msprojectexperts.co
For Project Server FAQS:
http://www.projectserverexperts.co
Previous Posts In This Thread:
Master Project error
When I am saving a master project which has several sub-projects and
sub-sub-projects, I am receiving this prompt
" The current project has inserted projects that are present as inserted
projects in other master projects as well. This may prevent the current
project from being published.
Is there a way to avoid this and still accomplish what I need.
Re: Master Project error
Hari
The message is warning you that you've inserted one project into more than
one Master Project. The system isn't designed to handle this. Stick to the
one-master-per-sub-project rule and the you won't get the error
--
Gary L. Chefetz, MV
MSProjectExpert
For Project Server Consulting:
http://www.msprojectexperts.co
For Project Server FAQS:
http://www.projectserverexperts.co
Hi Gary,If I stick to one-master per sub-project, our whole idea of creating
Hi Gary
If I stick to one-master per sub-project, our whole idea of creating master
project will be in vain
Let me describe in more detail, so someone can help
There are different product categories and each category has a project
manager
The way we planned is each category manager takes part of his own
projects(lets say A). But the stakeholders or portfolio managers have a big
picture of viewing the entire projects on category basis and even be able to
print reports
Now the project (A) which the manager is managing has again sub-projects in
it, as that specific part belongs to other department and will be handled by
that department and when they update the progress, it automatically updates
project A and consequently updates the Main master Project.
Thank you in adavance,
Hari
:
Hi Gary,Even though it gave me that prompt, am able to publish the project to
Hi Gary,
Even though it gave me that prompt, am able to publish the project to PWA.
Also if you notice the message prompt, it says "may prevent"
:
You're setting yourself up for problems.
You're setting yourself up for problems. You can use cross project linking
for task dependencies without creating permanent master projects. To get a
master project view of things, you simply need to go to Project Center, hold
the ctrl key and select the projects you want to see in the master view, and
click edit. This will open a master project that you can simply choose not
to save. If you have smartly designed Project Center views using good
project level attribution you can make this very easy for your users to
create temporary master files for their viewing pleasure.
--
Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting:
http://www.msprojectexperts.com
For Project Server FAQS:
http://www.projectserverexperts.com
From documentation (and experience) don't try to put more than 20 maxprojects
From documentation (and experience) do not try to put more than 20 max
projects into a master project
http://technet.microsoft.com/en-us/library/cc197693.aspx
Submitted via EggHeadCafe - Software Developer Portal of Choice
Setting A Maximum Execution Time on a Thread
http://www.eggheadcafe.com/tutorial...1-8846cc118dfe/setting-a-maximum-executi.aspx