After move PS 2007 installation, PWA fail. (File not found error)

P

Pablo M

Hello, I need to move the contents of the single farm instalation
(production) to an testing environment. For this I made backup with stsadm
and central admin
I installed a new virtual environment with MOSS and PS 2007 (same production
scenario) with the same updates as the production environment. Then I start
the service of Project Server and SharePoint search service. Finally I did a
full farm restore (I tried the two types of backup). The restore completed
successfully (no errors or warnings).
Is being installed on a server with another name and service users are
switching for a domain user (server's local administrator) does not have
access to production enviroment.
When I try to access the PWA presents an error stating "File Not Found."
More detail:
Server Error in '/' Application
--------------------------------------------------------------------------------

The resource cannot be found.
Description: HTTP 404. The resource you are looking for (or one of its
dependencies) could have been removed, had its name changed, or is
temporarily unavailable. Please review the following URL and make sure that
it is spelled correctly.
Requested URL: /PWA/default.aspx
----------------------------------------------------

The PWA has no customizations.
If I access directly to the link PWA settings page is working properly (But
the default PWA page does not open)
Is it correct the procedure for moving from one environment to another?
It's missing some step?

after restore, the following appears once in the event viewer error:
----------------------------------------------
Event Type: Error
Event Source: Office SharePoint Server
Event Category: Project Server Queue
Event ID: 7704
Date: 4/16/2010
Time: 6:11:36 PM
User: N/A
Computer: SRVTEST
Description:
Standard Information:pSI Entry Point:
Project User: DOMAIN\USER_Service
Correlation Id: b0a692f5-aa92-491a-8d31-a917e6140196
PWA Site URL: http://srvtest/PWA
SSP Name: SharedServices1
PSError: GeneralQueueJobFailed (26000)
A queue job has failed. This is a general error logged by the Project Server
Queue everytime a job fails - for effective troubleshooting use this error
message with other more specific error messages (if any), the Operations
guide (which documents more details about queued jobs) and the trace log
(which could provide more detailed context). More information about the
failed job follows. GUID of the failed job:
49aeb654-b8aa-498d-acd6-d8e0846c53cf. Name of the computer that processed
this job: SRVTEST (to debug further, you need to look at the trace log from
this computer). Failed job type: SynchronizeSingleUserMembershipInWss. Failed
sub-job type: SynchronizeSingleUserMembershipInWssMessage2. Failed sub-job
ID: 26. Stage where sub-job failed: (this is useful when one sub-job has
more than one logical processing stages).
 
G

Gerard Wojcik

Pablo - I would suggest that you reseach "Alternate Access Mapping" - try
adding the orginal hostname into the mapping, so that there is an entry for
both the new and old hostnames. I hope that this helps.
 

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