Problems creating new Workspaces

[PI]

When SP2 came out for MOSS/MOPS it caused some problems for us and I had to
restore from SharePoint backups, ever since then when projects are updated
they are trying to go to a different web app than they should. Also non of
the projects list a workspace address, but if you click on the project name
they go to the correct address.

If i try to change the web app in Project Server -PWA Server Settings, I
can't, it only lists one, even though there is more.


Why is it only showing one web application in the Edit Workspace address?

 

[PI]

Ok, I have the choice now for project workspaces on a different web app. My
main problem though is all the old project webspaces are on http://servername
but I don't have that choice, it is all http://servername:7349 or
another port.

 

[PI]

TTT

 

[C_A_D]

OK this is quite difficult to troubleshoot without all the info at
hand but, if you're not seeing the webapps in the pulldown list, it
could be that the application pool that hosts the webapp running the
PWA site is different from the one running the other web apps and you
may not have permissions to view the webapps associated to the
different app pool.

try creating a new temp web app under the same app pool as pwa and see
if that can be seen in Workspace Provisioning Settings etc

of course there could be another underlying problem here (as you have
encountered an issue when installing SP2 already)

 

[PI]

I checked the app pools and the indentiies they were running under and
compared them to our working virtual image (pre CU updates) of this server
and everything checked out fine.


I think I have a clue as to why the problem is occuring but not sure where
to trace it down to.

On our current setup if I try and go to Project Workspace Provisioning
settings, and try and change the web app to a different one and save or if I
try and tell it to not provision workspaces in the area it is currently doing
it I get "No site or site collection exists at the site URL specified. Enter
a site URL for a valid site or site collection and try again. "

Which makes sense If I go to central admin and check the site collections
for each web app, /project is only under site collection http://servername,
which is where it should be.

There part that doesn't make sense is that we can still publish projects to
the http://servername:6767, and it creates a workspace there.

I would like to get it back to http://server name, but that is where I am
stuck at.

 

[PI]

Okay now I'm trying to create a new project instance next to this one and I
can't choose http://servername, it has to be one with an odd port number.

Why can't 80 be listed?