Export Project Server 2007 web parts to MOSS 2007 sites failure

A

a

Hi,

Any help on the following appreciated:

In a development environment, with EPM (Project Server 2007) and MOSS 2007
installed as part of the same server farm, we have been able to export EPM
web parts from PWA and use them in a MOSS portal (held in different web
applications and site collections - all in the same farm).

The procedure to do this was in line with this blog entry by Christophe
Fiessinger:

http://blogs.msdn.com/chrisfie/arch...-epm-web-part-to-another-sharepoint-site.aspx


The steps outlined above also requried a little workaround to get the
project center and project details (drill down) webparts working:
When adding the webparts to a MOSS site page, we found that adding the EPM
Timesheet part to a page before the other parts ensured that no access or
permissions errors were not being returned.

Moving over into production, we find that the drill down and project center
parts do not render any data. On page load, there is a brief message of
'loading grid' before the following message is returned (almost instantly, so
I don't believe this to be a DB timeout issue):


"Project Center cannot access the project(s) you are trying to view. It is
most likely that you either don't have permissions to view the project,
another user has deleted this project(s) before you were able to view it or
that another user is in the process of publishing the project"


Farm setup: (NTLM authenitcation with AD),
2 x WFE's (Load balanced URLs using NLB for PWA and MOSS portals)
1 x App server (with PWA service running on it)
1 x SQL Server (SQL Server 2005 Std)

Have also disabled IIS Compression on all servers for the MOSS and PWA sites.

OS: Windows Server 2008 Std.

Project plans have been created and published
All EPM web parts are working fine in PWA and in project workspaces
Other web parts, such as Timesheet, MyReminders etc DO work in MOSS pages.
We also have custom developed webparts that are pulling data from EPM and
giving links to workspaces and plans.
Application pool accounts for MOSS appear to be correctly permissioned in
SQL Server for the farm config DB and the project databases (published, draft
etc)


Any ideas on how to diagnose and resolve greatly appreciated as this is
giving real headaches to all involved!
Really hoping it is something very simple and obvious rather than a complex
fix.


TIA.
 
A

a

Hi Andrew,

Thanks for replying.
Yes, for all the EPM webparts, we repeated the export process in production
as we did before:

Exported the *.dwp files, edited them to ensure that the PsiUrl was set
correctly to the production URL before importing them into the web part
gallery of our MOSS portal.
 
A

Andrew Lavinsky

Hmmm....could be a Project Server security issue. Have you tried adding
the Timesheet webpart to that page again to see if that resolves the issue?

I've seen this happen before, but forget how it was solved. I'll have to
ask around.


- Andrew Lavinsky
Blog: http://blogs.catapultsystems.com/epm
 
A

a

Hello Andrew,

Yes, we have gone through the process of deleting the web parts from the web
part gallery (MOSS), exporting them in again and adding in the timsheet or
reminders web parts in first. These work with no issues as expected.

Was wondering if there any other steps or things I could check, ACL settings
for directories in the servers for example?

Thanks again.
 
A

a

Sorry, just to clarify previous message (not very clear)

We have repeated the process of importing the EPM webparts into the MOSS web
parts gallery.

When adding the web parts to a site page, we have added in one (or both!) of
the MyReminder or Timesheet web parts.
These are added successfully with no issues.

The next step of trying to add in the drill down or project center parts
results in the same problem.

Hope that is clear.

TIA
 
A

a

Andrew,

We are logged in as administrator account (recognised in PWA and MOSS).
Do we need to be a 'real' user to do this?

Also, regarding your earlier comment about synchronising with a site, can I
be clear on what you meant exactly (EPM is not my strongest skill!)?

If you are referring to project workspaces, then PWA is configured to
automatically create one when a plan is created and published. Please let me
know if this is not what you are referring to.

Thanks.
 
P

Piet Remen

I too have seen this behaviour before and the workaround was delete the web
parts from the page. Add in the Timesheet web part. The add the project
centre or whatever web part you are getting the error with into the same web
part zone. If this works I have had to keep the timesheet web part on the
page still but instead of deleting it, hide it. Just a note though, view
hidden web parts on a page by appending the following text to the page URL.

?contents=1

If this sequence does work, you may need to recreate the project workspace
site template in the new MOSS environment using the exact same steps,
remembering to 'hide' the timesheet webpart.

If this still does not work then Im not sure. May be security related, are
you using kerberos or NTLM? Try a different account to test, making sure this
account has access to both PWA and the MOSS workspace site. Also look for
further help in the event viewer and SharePoint ULS logs and see what you can
find.

Regards,

Piet Remen
www.projectserver.com.au
 
A

Andrew Lavinsky

Just thinking out loud. You may wish to test if the following variables
have any effect:

1) Adding the webpart to a site template, then provisioning the site from
MPP using the new template.
2) Adding the webpart after the site has been provisioned.

My guess is that #1 is ideal, but you may be attempting #2? Not sure if
either really has an impact on the situation, but worth trying out.


- Andrew Lavinsky
Blog: http://blogs.catapultsystems.com/epm
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top