After Deleting the PWA Instance, I am unable to create new PWA.

[waqas sarwar]

Hi Folks,

I have fell into a serious problem, i am trying to migrate the 4 pwa
instance from test envirnoment to Prodcution envirnoment, But it was not done
sucessfully.here the complete story.

1st i delete 2 PWA instance from Prodcution site which was created 2 days
before for the testing purpose.
i backup the all dbs from test envirnoment and restore it on the production
envirnoment.
now i create a new webpp and then trying to create to PWA with exisitng 4 DBs.
but the result is SSP stuck some and did not change its status from "waiting
for resources" last 24 hours.

then i saw the event log their are sequence of error and its occured just
after the deleteing the 2 pwa instance on the Production. Error # 7626 & 7019
(total 4 occurance on every min, 2 for each pwa.
and then i saw the timer job definations in the Central Admin and their are
2 jobs running
Project Server 'SharedServices:http://ghkperi:777/pwa1' job
'ApplyResourceCapacityTimeRangeJob'
Project Server 'SharedServices:http://ghkperi:777/pwa2' job
'ApplyResourceCapacityTimeRangeJob'

i dont know what i have to do with it, their is no option to delete these
sites, just i can disable it.

Please help me how can i get rid of it and able to create the new pwa
instance, which is still saying waiting for resources.

thanks

 

[Gary Chefetz]

Wagas:

When you remove the PWA instance, it doesn't cleanup IIS completely. You
need to manually remove the websites and application pools. Does this help
at all?

 

[waqas sarwar]

Thanks Gary,

I check the IIS on all front end and application server but i did not found
it anywhere, More interesting thing, when i took the full farm backup at that
time i saw 8 errors due to those 2 PWA instances (all 8 dbs fails to backup,
but they did not exists). i dont know wrong with them, i delete PWA instances
every where and dbs from SQL server. Now when i am trying to create a new pwa
instance, its status never changed from Waiting for resources.

thanks

--
Waqas Sarwar

Wagas:

When you remove the PWA instance, it doesn't cleanup IIS completely. You
need to manually remove the websites and application pools. Does this help
at all?

 

[Gary Chefetz]

Waqas:

I've seen the SSPs become corrupt and unusable. You might also try creating
a new SSP.

Thanks Gary,

I check the IIS on all front end and application server but i did not
found
it anywhere, More interesting thing, when i took the full farm backup at
that
time i saw 8 errors due to those 2 PWA instances (all 8 dbs fails to
backup,
but they did not exists). i dont know wrong with them, i delete PWA
instances
every where and dbs from SQL server. Now when i am trying to create a new
pwa
instance, its status never changed from Waiting for resources.

thanks

 

[waqas sarwar]

Thanks Gary,

OK i got your point, but tell me how can i get rid of the pwa instance which
is still saying "Waiting for resource". I did not find any command to kill
this process, Could you please guide me in this regard. How can i kill the
PWA which is still under process since last 36 hours.

thanks

 

[JoeData]

I work with Waqas at AOUSC, and we initially tried to change the database
collations of our Project Server databases. We had to open a support call,
and the Project Server support team eventually told us we'd have to
completely rebuild the instances.

....

We provisioned two instances to test these collations, which we were trying
to delete. As they were never provisioned correctly, so as you suggest, they
may have corrupted the SSP.

Somehow, though, a WSS site got involved.

We didn't know about SSP corruption, so the fastest course of action to get
rid of the errant instances was to rebuild the farm. However, we attempted to
restore a SharePoint Web application independant of Project Server, which
failed, with the resulting errors relating back to the two other PWA
instances. Not sure how that's even possible as we were using the "-item"
argument of the restore operation for the SharePoint site.

So this action may have set off the SSP corruption again, which is why we
can't provision any further PWA instances in this server farm.

We've been following Gaurav Wason's helpful instructions on how to move PWA
instances, which have usually worked for us well, minus changing the database
collations...
http://proj2007.blogspot.com/2008/10/steps-to-move-project-server-2007-from.html

Next course of action: Rebuild farm again, this time provisioning PWA before
restore tainted SharePoint site.

....In the mean time, we have more students for Dale...

 

[Gary Chefetz]

Waqas:

Essentially, you create the new SSP, assign any existing applications that
you need to preserve to it, and then delete the old SSP. See Brian Smith's
post on this below. Brian gives you some other things you can try to shake
things loose, but I suspect your SSP is corrupt and non-functional

http://blogs.msdn.com/brismith/arch...-provision-a-new-project-web-access-site.aspx

 

[Gary Chefetz]

JoeData:

Sounds like you could use a good virtualized test environment, too!

 

[waqas sarwar]

Thanks Gary,

ITs worked and we really appreciated your time and say thank to you.

thanks

 

[Gary Chefetz]

My pleasure Waqas