Re: Repairing IIS
- From: Bilbo <wlp<faux>fake<at>email<dot>hal-pc.org>
- Date: Sun, 20 Jan 2008 21:11:25 -0600
Problem apparently solved.
Re-installed SBS SP1; worked except for complaint about Outlook 2003
SP1. Non-issue as far as I can tell.
Bilbo
On Sat, 19 Jan 2008 13:10:15 -0600, Bilbo
<wlp<faux>fake<at>email<dot>hal-pc.org> wrote:
Hi Robert,
I'm in the middle of performing your procedure (under Info 2) and I
got a message after WSS installation that older components had
replaced newer ones and SBS SP1 was needed again.
I was NOT prompted for SBS2003 SP1 CD3 explicitly.
This is an SBS 2003 STANDARD installation and KB 832880 is apparently
not needed as the SBS install CD 3 has the proper certificate
expiration date. I'm confused here and I don't know how to proceed.
Thanks,
Bilbo
On Tue, 20 Nov 2007 06:53:20 GMT, v-robeli@xxxxxxxxxxxxxxxxxxxx
(Robert Li [MSFT]) wrote:
Hi Bilbo,
Thanks for posting in our newsgroup and also for Cris's input.
From your description, I know that the ISAPI Filter STSFLTR is missing fromcompanyweb and some folders are missing from C:\Program Files\Common
Files\Microsoft Shared\web server
extensions\60\BIN. If that's not right, please don't hesitate to let me
know.
Based on my research, when a virtual directory is extended by WSS, an ISAPI
filter, Stsfltr.dll, is installed. It is used to give SharePoint exclusive
access to the entire virtual directory including all the sub-webs
underneath. Since the stsfltr.dll locates at C:\Program Files\Common
Files\Microsoft Shared\web server extensions\60\BIN folder, you can't find
this filter in IIS if the folder is missing. It seems that the SharePoint
component was not installed successfully before, or the folders are deleted
by accident.
If you customer doesn't use SharePoint at all, you can leave the things as
they were because this SBS Best Practices Analyzer tool warning doesn't
affect their use. If you need to fix the warning, you need to reinstall the
SharePoint component and you don't need to repair IIS here.
Info 1. If you're using an SBS with SP1 (slipstream installed), you can
also follow KB 829114 for a reinstallation.
More information:
829114 How to remove and how to install the Windows Small Business Server
2003 SharePoint Services companyweb Web site
http://support.microsoft.com/default.aspx?scid=kb;EN-US;829114
Info 2. If you're using an SBS with SP1 upgraded from SP0, you should
follow these steps to reinstall SharePoint Companyweb.
1. Please strictly follow KB 829114 for reinstallation of SharePoint
companyweb (with SBS 2003 SP0 CD3 inserted).
2. If the system prompts you for SP1 installation CD3, follow these steps:
a) Open Registry Editor and set 'isrunfromweb' to '2', under
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SmallBusinessServer.
b) Download SBS 2003 SP1 (885918) to C:\.
c) Open CMD window and type "C:\SBS2003-KB885918-SP1-X86-ENU.EXE /x" (with
no quotation marks) and press Enter.
d) Specifying a path for the extracted files (such as C:\SBSSP1).
e) Point the system to the folder created in the previous steps
(C:\SBSSP1\CD3).
3. After finish the installation, install KB 832880.
More information:
832880 You cannot successfully install the intranet component or connect
to http://companyweb in Windows Small Business Server 2003
http://support.microsoft.com/default.aspx?scid=kb;EN-US;832880
4. Install WSS 2.0 SP1.
5. Install SBS 2003 SP1 again.
6. Reboot the server and check whether the problem persists.
Hope this helps.
If you need further assistance, please don't hesitate to let me know.
Best regards,
Robert Li(MSFT)
Microsoft CSS Online Newsgroup Support
Get Secure! - www.microsoft.com/security
=====================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.
Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.
For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.
Any input or comments in this thread are highly appreciated.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
<From: Bilbo <wlp<faux>fake<at>email<dot>hal-pc.org>
<Subject: Repairing IIS
<Date: Sun, 18 Nov 2007 20:51:29 -0600
<Message-ID: <sgt1k3d1glvf859sdlac39o50vedd01kg9@xxxxxxx>
<X-Newsreader: Forte Agent 1.93/32.576 English (American)
<MIME-Version: 1.0
<Content-Type: text/plain; charset=us-ascii
<Content-Transfer-Encoding: 7bit
<Newsgroups: microsoft.public.windows.server.sbs
<NNTP-Posting-Host: 206.180.133.7.adsl.hal-pc.org 206.180.133.7
<Lines: 1
<Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP04.phx.gbl
<Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:76707
<X-Tomcat-NG: microsoft.public.windows.server.sbs
<
<A customer's home-built server has five HDD; 3 in RAID-5 and 2 in
<RAID-1. 2 NICs running SBS 2K3 SP1 w/W2K3 SP2, Exch SP2.
<
<BPA reports that ISAPI Filter STSFLTR is missing from companyweb site.
<
<I've looked and I don't find this filter anywhere on the server.
<
<I think there's been some damage. On my SBS Premium server this
<filter resides in:
<
<C:\Program Files\Common Files\Microsoft Shared\web server
<extensions\60\BIN
<
<Actually, the ...\60\ folder has several subfolders on my server:
<
<ADMISAPI
<BIN
<CONFIG
<ISAPI
<TEMPLATE
<
<On the customer server, ONLY the TEMPLATE folder is present.
<
<Clearly, there's a problem, not least of which is "What does one do in
<a situation like this?"
<
<I know that removing IIS is a terrible idea. I've no idea whether the
<damage is confined to this one folder branch or not. I COULD run a
<SFC but I'm skeptical that it'd even detect anything in this path.
<
<Obviously, there's another question: "Who did this and how do we
<prevent a recurrence in the future?" The customer knows more than
<just enough to be dangerous. It's a problem.
<
<I'd be grateful for any suggestions that don't involve re-building the
<server from CDs. <grin>
<
<-Bilbo
<--
< BilBo
<
--
BilBo
.
- References:
- Re: Repairing IIS
- From: Bilbo
- Re: Repairing IIS
- Prev by Date: Re: Forever
- Next by Date: Re: Physical Network Connection
- Previous by thread: Re: Repairing IIS
- Next by thread: Re: Repairing IIS
- Index(es):
Relevant Pages
|
