Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Project Server Destroyed my STS site! Help!

0 views
Skip to first unread message

Pierre-Philippe Le Bel

unread,
Jul 15, 2002, 3:55:20 PM7/15/02
to
Group,

I installed Project Server on my STS web site (knowing that Project Server
apply some changes in STS). After some technical difficulties with Project
Server (that's another story for later), I uninstall it according to MS
documentation, but now, 90% of the document folders are broken (but not the
normal list). The "allitems" page is blank, and for the last 10% they have a
rendering error in the upload page. Is there any way to fix that?

TIA

Philippe Le Bel


Dustin Miller

unread,
Jul 15, 2002, 4:28:27 PM7/15/02
to

Yikes... You can try re-installing STS on its own from an Office XP Pro
w/FrontPage or FrontPage CD. Actually, you can install it from the
Project Server 2002 CD as well (just DON'T run the configuration utility
-- you've seen what that does!) :)

Let me know here in the groups if you need more assistance.


--
Dustin Miller, President, SharePoint Experts (a division of FuseWerx LTD)
SharePoint Team Services, .NET, ColdFusion and ASP Consulting/Integration
http://www.sharepointexperts.com/ - http://www.fusewerx.com/
STS FAQ, by Mike Walsh: http://www.collutions.com/Lists/FAQ/

Pierre-Philippe Le Bel

unread,
Jul 16, 2002, 9:39:05 AM7/16/02
to
Thanks Dustin,

Been there, done that, got the T-Shirt! ;-)

I did re-install STS, but it didn't change anything. What I found so far is
PS is changing the "allitems" page source code by adding (or changing) some
Java script to make the document folder "compatible" with PS. But when you
un-install PS, it removed the OWS dll (I don't remember the name), but
leaves the Java script in the page, result, the page basically doesn't load,
but doesn't generate any error either (???).

So fare, the only way I found to resolve this (buckle your seatbelt), is by
going the following:

- Go in the database with SQL Enterprise manager
- Find the "project number" of the STS site in the STS tables (because I
lost the link to the document folder customization page)
- Find the name of the folder created by STS from the table name (usually it
starts with u_)
- Append the name of the table to the following link (http://<intranet
URL>/_layouts/listedit.htm?List=u_<list name>)
- Then I have access to the Customization page of the list
- Rename the list with "List name OLD"
- Create a new document list with the original name
- Move all the document with FrontPage or directly from the server to the
new list folder
- Make all the appropriate changes that makes reference to the old list
(like removing it from the quick link)

No need to say that this is very time consuming, and I have probably
hundreds of these document list that are corrupted.

BTW, MS recommend to un-install STS and re-install it. According to them, it
should resolved the problem (this is very ugly!). But because I did that to
myself, so I won't complaint to much about it...


Anyway, I though I should share this with you... ;-)

Philippe Le Bel

"Dustin Miller" <dustin-...@sharepointexperts.com> wrote in message
news:Xns924C9D8E1...@207.46.239.39...

0 new messages