Server Config Single server Windows 2003 Enterprise SP2 SQL 2000 SP4 SharePoint 2003 (a.k.a WSS 2.0) SP3 Office Portal Server 2003 C partition is cramped, so I wanted to move the Usage & Analysis Processing logs from C: over to E:. The location on E already exists, and SPS_WPG and STS_WPG both have full control to it. Yet on the Central Admin page where I would make the change, whatever I do on that page doesn't seem to "take." I hit the OK button and it doesn't seem to DO anything, staying on the same screen. So then I go to do the one other thing I wanted to get done today, which is to add a new content database. From the Central Admin tool, I navigate to the right page for adding the database, I specify the content dataase server, which is the same as this one, and give it the database name, the number of warnings, the number of sites, and hit OK, and again the OK button just seems sort of faulty. Doesn't actually DO anything. Just stays on the same screen. I've tried making these changees using different administrative accounts including what should be the Farm account. (I didn't set this thing up, but that account is the only one that will take STSADM commands, so it seems to be the all powerful farm admin account.) Anyone have any ideas on where to look? Most of my SharePoint experience is with 2007\2010, and this 2003 thing keeps throwing curveballs at me. Lady_M MCITP SharePoint 2010

> SharePoint 2003 (a.k.a WSS 2.0) SP3 > Office Portal Server 2003 The first thing is that you either have WSS 2.0 installed or you have SPS 2003 installed, you can't have both. (If you have SPS 2003 you do need to have the service packs named WSS 2.0 and SPS 2003 added and not just the SPS 2003 Service Pack) The second is that there is no such thing as Office Portal Server 2003 as the word Office was only added to the product name in the 2007 version. That said, can we assume that you are running SPS 2003 and that you have installed both the WSS 2.0 SP3 and the SPS 2003 SP3 ? Moderator SP 2010 "FAQ" (mainly useful links): http://wssv4faq.mindsharp.com/default.aspx WSS3/MOSS FAQ (FAQ and Links) http://wssv3faq.mindsharp.com/default.aspx Both also have links to extensive book lists and to (free) on-line chapters

Hi Mike, thanks for your response. Like I said, I started learning SharePoint with 2007 which was called office server. When I go back to look at MS's website today, they are calling it "Office SharePoint Portal Server 2003" now, so don't nitpick me on that please! http://technet.microsoft.com/en-us/office/sharepointserver/bb267364.aspx Nope. I'm well aware that we are in an "unsupported" state, missing that service pack. I've been told that previous attempts to install it "broke everying." But I don't have any details on what happened. It's on my to-do list for sure, but I've been working on trying to get a parallel test environment going so I've got avenues of escape in case I "break everything." Currently waitiing on delivery of some SharePoint 2003 books, since my old friends Bing and Google aren't even being much help these days with this older software. Was hoping for some ideas on this particular issue of trying to make changes in CA, but if no one has any ideas, then I'll assume\hope that my test environment can help reveal something, and that the service pack will help. Lady_M MCITP SharePoint 2010

OK. Thanks. I suspect that wasn't the name in 2003 (I've seen MS articles (especially KB articles) get the names of even current SP products wrong) but let's move on. It's reasonable for you to call it what a MS site calls it :) Do you know if you have the SPS 2003 SP2 installed? If so it might be a good idea to uninstall WSS 2.0 SP3 so at least you have a matched set of SPs for your SPS 2003 installation. (After a backup of course and also perhaps a re-try at installing the SPS 2003 SP3). I have no idea if the present mis-match is causing problems or not but a solid base is always useful when error-finding. Mike SP 2010 "FAQ" (mainly useful links): http://wssv4faq.mindsharp.com/default.aspx WSS3/MOSS FAQ (FAQ and Links) http://wssv3faq.mindsharp.com/default.aspx Both also have links to extensive book lists and to (free) on-line chapters

Hellooo again, I'm unmarking this as answered because I don't really have a resolution yet. I can only work on this server on certain weekends, and have not yet been able to try as Mike suggested. Honestly, I'm planning to just do a disaster recovery with the thing ... move the content database over to another server, rebuild the admin database, and hope that applying service packs will work after that. Hope. Meanwhile, I've been trying to delete old outdated sites. Most I have no problem with most of them. But a few what I would call top-level sites (i.e. http : //servernme/sites/sitename) are not letting me back them up with FrontPage 2003 first. I can connect to the site with FrontPage like the others, but my only option when I go to Tools > Server ends up being "Site Administration Home," but "Back Up Site" and "Restore Site" are grayed out on the menu. Any ideas if this is just me doing something wrong, or if it all sounds related? Lady_M MCITP SharePoint 2010

Making progress!!! I've rebuilt the farm in a test environment, creating a new config database and attaching the content database. Seems to be pretty successful, and I can make the changes in CA in this test environment that I could not in my main environment. Along the way, I did just figure out my issue with not being able to back up sites with FrontPage ... http://social.msdn.microsoft.com/forums/en-US/sharepointcustomization/thread/3ae663d9-fcb3-45d1-8b8c-d8e068b9ed1a/ I went into the Onet.XML files for the template used for these sites, and edited it to remove a whole list of things behind "DisableWebDesignFeatures=" such as backup website, restore website, etc. IISreset, and done. Lady_M MCITP SharePoint 2010