Error provisioning PWA

[Andres Rojas]

Hi everybody, this is my scenario:

- Windows Server 2003 x64 SP2 R2 full update.
- WSS 3.0
- MOSS 2007
- MOPS 2007.
- There is no project published in mops, this is a new installation.

When i try to provisioning a pwa access, this wokrs fine, but, when i try to
connect to the instance (http://myserver:90/pwa), mops showed the following
error:

-----------------------------------------------
An unexpected error has occurred.
Web Parts Maintenance Page: If you have permission, you can use this page to
temporarily close Web Parts or remove personal settings. For more
information, contact your site administrator.
Troubleshoot issues with Windows SharePoint Services
-----------------------------------------------

once the error is shown, I give click in the web parts maintenance page
link, I drop the tasks web parts and after doing this, I can enter to the
instance pwa.

Some suggestion about?

 

[C_A_D]

what version of MOSS/MOPS/WSS are you running
have all the components been isntalled on all servers to the same
level
have you finalised the wss config wizard after isntalling all
components

let me know teh above and IL happily have more of a think

 

[Andres Rojas]

Hi, the versions are:

WSS 3.0 SP2, MOSS 2007 SP2, MOPS 2007 SP2 and SQL Server 2005 SP2

All in one server, i have only one server in the farm.

- All Components was installed to the same level.

- Yes, i ran the wss configuration wizard after the installation.

Look, i found other problem, when i going to modify some resource, mops
display an dialog with this information: "i have not permission to modify the
resource. please contact to administrator". The only user in the web site is
the project server admin!!! this is very complicated, it is the first time
that appears to me these two problems in an installation of EPM 2007.

Remember, I could see the Web site after drop the tasks Web Part.

I am really needing his collaboration, I do not have idea that doing with
these problems.

Thanks in advance.

Andres Rojas
MCP, MCTS, MCT

 

[C_A_D]

Hmmm... not sure here. it sounds as if the queue job that builds the
initial permissions when you provision the farm is not completing.

is there anything in the event log for the server from just after the
time of provisioning that may give some hints here.

did you install the components under the same install account? what
account is running the mops queue service?

the following kb talks through resetting farm account permissions...
its worth running through this to ensure that the relvant accounts
have the right permissions

http://support.microsoft.com/default.aspx/kb/934838

come back with any useful event log details that may have a clue to
this...

 

[C_A_D]

and just one more thing.... are you using language packs?? if so,
which are installed to what level??