PWA and Project Views Failure

[Nikkie Nicholson - Prism Research]

Hi everyone

It has recently been discovered on a client's project
server that publishing project plans fails to make them
available in Project Views with the text "There is no
information to display in this view. Either the project
manager has not published the project plan or there is no
information to display" being displayed instead of project
tasks. Upon further investigation, it was identified that
a series of error messages were being generated each time
a project plan was published.

I discovered a couple of Microsoft Knowledge Base articles
in relation to these errors and this problem specifically,
however, even after undertaking the steps suggested and
reviewing permission structures, etc., the problem has not
been rectified.

Is there a setting that I may have missed that is
preventing Project Views from being visible on project
plan publication or do we have to take the radical step of
uninstalling and reinstalling Project Server? Any
suggestions?

Any help would be greatly appreciated and will stop me
from going bald from tearing my hair out ;-). Seriously
though, thanks very much in advance.

Nikkie Nicholson
Prism Research

 

[Gary Chefetz [MVP]]

Nikkie:

Your query is quite vague. At the very least, you need to describe your
setup for anyone to take a stab at this. It's also helpful if you post the
error messages you're seeing, too! Are you using Windows Auth or Project
Server Auth?

--
Gary Chefetz [MVP]
http://www.msprojectexperts.com
"We wrote the book on Project Server"

*** Remember to look for line breaks in links posted to the news group, use
cut and paste for these.

 

[Ramesh]

Nikkie,

You had posted earlier that "it was found on our Project
Server that each time a project plan was published, an
error in relation to ViewsDrop (0x800004005) was being
generated"

I have the same pbm but I do not see any errors when
publishing. Also I see 3 project files in the View Drop
folder which are dated in March ( not sure what todo about
them).

 

[Jon]

Nikkie,

We had this same problem here. We found a reboot of the WEB Server
solved the problem. Check your services, specifically "Microsoft
Project Views Notification Service", make sure they are running.

You should also look in the viewdrop folder on your web server to make
sure the XML file is being dropped in there after a publish\save:
<ServerName>\ProjectServer\Bin\ViewDrop. Once the project is saved or
published to the server the XML file should appear in the viewdrop
folder. My experience has shown the web server takes up to an hour,
based on the size of your project, to build the data views within the
web server. The XML file will disappear once the process is complete.
After the XML file disappears you should be able to see your project
in the Web Server\Project view.

We never were able to determine what hammered the system/services but
since the reboot it has been fine.

Hope this works for you as well.

Jon

 

[Nikkie Nicholson]

Hi Jon

Thanks very much for your help. I'll let you know how I
get on.

Nikkie

 

[Gary Chefetz [MVP]]

Nikkie:

You don't have to worry about your messages being read here, many will read
your post. Getting folks to reply to you is the goal, so making that easier,
by providing information, helps.

These errors indicate that publishing actions are being attempted without
the proper authority in the system. There are likely backed up xml files in
your ViewDrop folder. Part of diagnosing the cause is to examine these files
to see what user this happening to and pursue a solution at the user level,
or whether it's all users, which would indicate you need to look at things
at the system level.

--
Gary Chefetz [MVP]
http://www.msprojectexperts.com
"We wrote the book on Project Server"

*** Remember to look for line breaks in links posted to the news group, use
cut and paste for these.

 

[KC]

We had the same problem too and it was fixed. The KB
Article 810596 helps a lot. Our problem was the account
is used to run the Microsoft Project Server Online
Analytical Processing (OLAP) Cube component has changed.
Just follow the workaround instructions for Method 4,
follow step 1 to 5 and make sure the account is correct.
If not create a new account/password for it. Your system
programmer should know how to do it.