Site does not exist or is not configured for Project Server

W

Walt N.

We are running Project Server 2003 with SP2a and have previously been able to
publish projects to create WSS sites for the projects. Recently, however,
the function to create a WSS site from Project Server began failing. When we
go to the PWA Admin page to create the site manually we receive the message
"Error occurred creating site. Site does not seem to exist".

We decided to go to WSS Administration and manually create the site,
"sites/projectserver_150". But, when we try to Edit the Site Address in the
PWA Admin page to set it to "projectserver_150" we get the message, "The Web
site does not exist or is not configured for Project Server. Enter a Web
site that has been extended with a Project Server compatible template".

We created the site using the default "Project Workspace" template, so I
don't think the problem is with the template. There are no special
characters in the project name. This operation used to work correctly. What
could cause this functionality to stop working? Other PWA/WSS functionality
is still working correctly (like using Documents and Issues from the PWA
pages).

What is it that Project Server is looking for when it creates WSS sites that
it is not finding?

-Walt
 
W

Wegz

Walt. I am having the exact same error. Down to the letter!!!

In my case, i actually unregistered the ProjectWorkspace Template (by
mistake) and that was when it stopped working. I havent been able to
work out how to put it back in as the file has been lost forever and
have no idea how to recreate it.

The fact we get teh same error makes me think that maybe there is an
issue with the template. If you know how to reset up the
projectworkspace template i suggest try that to see if the error goes
away.
 
W

Walt N.

Thanks. However, we have already tried several templates (both the original
as well as several derivative templates) to no avail, so I don't think the
problem is with any given template. The event log does show a critical
failure of the PJOBJPRV dll that I'm going to investigate.
 
V

Vaughn Fox

I'm getting the identical error as well, have you guys discovered a solution
you'd care to share?
 
W

Wegz

My version of the error we determined was caused by the security
settings that we had (kerbros - i forget the spelling)

It was solved by the following way.

We backed up the project server database (and then did a maual back up
also of the projects and enterprise global to be safe --> that took a
while)

We then delted the databases except project server.

Then we unistalled WSS and Project Server

Then reinstalled everything like it was a fresh install and pointed to
the project server database instead of creating that as new..

The only different thing we did was to change the WSS security to NTLM
or whatever it was called.

It all worked a ok after that.

Sorry it is a little vague but we did it late at night and i am still
waiting to get the technical procedure document from the company who
helped me out on the night.

But if you dont use Kerbros then it would be a totally different issue.
 

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