URGENT - Project saved and published but not in project center2007

P

PedroJose

Hello,
I have project server 2007, and sp1, single server farm. I have imported a
new project, published it, and it does not appear of project center views. I
have created a one line project and imported it, published it, and it does
show. Basically used exactly the same procedure but the small project shows,
the big one doesn't. I've used the same procedure always and it always
worked... Could it be spaces in project server databases?? if so, how do i
check? how do i increase the size of dbs?? Please help... !!!
 
P

Paul Conroy

Check the Queue to see if anything is blocking or causing your project to
fail to publish.
 
P

PedroJose

Paul,

The queue shows a successful job, in fact there are no failed jobs. The
project plan is in the published database, the workspace link appears in the
Workspaces webpart. It just does not appear in project center and no tasks
are published....

It is very weird, because I do exactly the same thing with a very small plan
and it works like a charm. The real plan though, a 1000 line plan with many
custom fields, etc. does not have the same luck.

Any ideas?

Thanks.
 
P

Paul Conroy

I've seen this once before on a very large deployment of PS2007, see extract
of call with MSFT Support below.


It appears that some rows had disappeared from the
MSP_WEB_SECURITY_PROJECT_OWNERS table in the _Published database so this was
not returning all the projects that were expected when security stored
procedures were executed. The following query can be used to identify
“invisible†projects if you run into something similar. The rows are easily
reconstructed but as we don’t have root cause please contact support if you
come across this.



select PROJ_UID, PROJ_NAME from MSP_PROJECTS

where NOT EXISTS

(Select *

FROM MSP_WEB_SECURITY_PROJECT_OWNERS

where PROJ_UID = MSP_PROJECTS.PROJ_UID)
 
P

PedroJose

Paul,

Thank you very much! We solved the problem in the following manner:

I was able to re-open the project plan that did not appear in project center
or tasks. It had no content at all!! blank! this is weird because the
importing/saving/publishing jobs completed with no issue whatsoever.

In the meantime, the sysadmin increased the size of all DB as it appeared
that they had very little space available (how can this be?????).

I then deleted the empty plan, and re-imported it, saved it and published
it. And it all worked OK.!! Very strange.

Now the issue is 1. DB space that seems to run out, or otherwise be a
problem and 2. the Manage Queue page cannot be accessed (it just gives an
error, this started last week) so the only way I have to see the status of
the jobs is through my personal settings

I've read about the log file size increasing exponentially, but do not know
how to fix this, or where to look for these files, any ideas?

The issue with the Manage Queue page is a bad one.... it actually started
right after installing SP1.... any ideas???

Thanks again for the help with the first issue!!
 
P

Paul Conroy

Your DB Admin should configure the database to autogrow should they start to
run out of space. It is however best practice to manually grow them, but
keeping autogrow enabled, just in case you need it. I normally make the
databases reasonably large to start with (dependant on the size of
deployment, this may be anywhere from 1-10GB). BY default SQL DB's are only
a couple of MB, so it's very easy for them to run out of space.

Obvisouly you're going to need enough disk space to accommodate the DBs and
their logs.

SQL DB's for a prodcution system should be run in full recovery mode so that
they can be restored to a single point in time (providing you have the logs).
The log files should be backed on a frequent basis, at least daily, but
often at lesser intervals depending on the businesses requirements.

Sharepoint/WSS logs can grow to enourmous sizes. The key with these is to
keep logging to a minimum unless troubleshooting a particular issue. The
location of these logs can be found from central admin/operations/diagnostic
logging.

I've not heard of issues with the Manage Q page post SP1, sorry.
 
J

jpa

Hi PedroJose,

I also faced the problem as you described.
We just installed MS PS 2007 with using default DB settings...
Could you please indicate
1) which DB parameter to increase?
2) what do you precisely mean with "I then DELETED THE EMPTY PLAN, and
RE-IMPORTED it, SAVED it..."? Is-it a necessary steps? Or when publishing a
new project said new project will become visible in Project Center?

Thanks for your inputs
jpa
 
Top