Re: sbs2003 sp1 - cannot browse /remote, /monitoring, /outlook

Jenny, thanks for your response.

I have done many things in an attempt to correct this issue:
1. re-run CEICW and created a new certificate.
2. disabled socket pooling
3. verified (ping) that ISA Server 2004 destination set for 'publish' web
services is the internal LAN (192.168.16.2)
4. verified that the Default web properties is listening on 192.168.16.2

I then suspected asp.net was the problem...
5. re-registered ASP.Net using aspnet_regiis.exe -i
6. verified that the web service extension for asp.net 1.1.4322 is allowed

7. I downloaded/installed the WSTools for Win2003 SP1 and ran the portqry on
both the server. Results are:

PortQry Log File
System Date: Thu Aug 25 09:31:23 2005
Command run:
portqry -n smhserver -l C:portqrysmhsvr.txt
Local computer name:
SMHSERVER
Querying target system called:
smhserver
Attempting to resolve name to IP address...
Name resolved to 192.168.16.2
TCP port 80 (http service): LISTENING
========= end of log file =========

8. I have attached the netsh -v log hoping this will shed some light on the
problem.

9. The problem: cannot access published web services (/remote, /companyweb,
/owa) from the outside (ISA2004 returns a response 'Server error in 'xxx'
application, where 'xxx' is replaced by ' remote ' (for example).
Internally, logged on to the server as an administrator, when I run Server
Management and click on Monitoring and Reporting, I get a more detailed
error message :

Server Error in '/Monitoring' Application.
--------------------------------------------------------------------------------

Failed to map the path '/'.
Description: An unhandled exception occurred during the execution of the
current web request. Please review the stack trace for more information
about the error and where it originated in the code.

Exception Details: System.Web.HttpException: Failed to map the path '/'.

Source Error:

An unhandled exception was generated during the execution of the
current web request. Information regarding the origin and location of the
exception can be identified using the exception stack trace below.

Stack Trace:

[HttpException (0x80004005): Failed to map the path '/'.]
System.Web.Hosting.ISAPIWorkerRequestInProcForIIS6.MapPathSlowUsingIISCore(String
path) +240
System.Web.Hosting.ISAPIWorkerRequest.MapPath(String path) +419
System.Web.Configuration.HttpConfigurationSystem.ComposeConfig(String
reqPath, IHttpMapPath configmap) +519
System.Web.HttpContext.GetCompleteConfigRecord(String reqpath,
IHttpMapPath configmap) +437
System.Web.HttpContext.GetCompleteConfig() +50
System.Web.HttpContext.GetConfig(String name) +197
System.Web.CustomErrors.GetSettings(HttpContext context, Boolean
canThrow) +20
System.Web.HttpResponse.ReportRuntimeError(Exception e, Boolean canThrow)
+40
System.Web.HttpRuntime.FinishRequest(HttpWorkerRequest wr, HttpContext
context, Exception e) +480



--------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:1.1.4322.2300; ASP.NET
Version:1.1.4322.2300

This error message comes up for all IIS Default services. Please advise as
to my next step.

Thanks
... rick


""Jenny wu [MSFT]"" <v-yanniw@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:ZUsp2jUqFHA.3148@xxxxxxxxxxxxxxxxxxxxxxxx
> Hi Rick,
>
> Thanks for your update!
>
> A solution that changes IIS to monitor on the internal NIC will not affect
> the ISA settings. Actually, it should be the default setting after
> running
> CEICW. So please double check the settings in A solution pointed which
> should be configured as A solution. If not, please correct and then try to
> test to resolve the issue.
>
> If the issue persists, let us use Portqry.exe to double check what process
> is monitoring on the TCP port 80 of the external NIC:
>
> The Portqry.exe tool is not automatically installed when you install
> Windows Server 2003 SP1. To install the Windows Support Tools on a
> computer
> that is running Windows Server 2003, run the Suptools.msi program that is
> in the Support\Tools folder on the Windows Server 2003 SP1 CD.
>
> And also you can download the updated Windows Support Tools from internet,
> please visit the following Microsoft Web site:
>
>
> http://www.microsoft.com/downloads/details.aspx?FamilyId=6EC50B78-8BE1-4E81-
> B3BE-4E7AC4F0912D
>
> For more information about how to obtain Windows Server 2003 SP1, click
> the
> following article number to view the article in the Microsoft Knowledge
> Base:
> KBLink:889100.KB.[LN]: How to obtain the latest service pack for Windows
> Server 2003
> http://support.microsoft.com/?id=889100
>
> *Note: If you have an earlier version of the Windows Support Tools
> installed on your computer, you must remove this version before you
> install
> the Windows Server 2003 SP1 Support Tools.
>
> Please refer to the following steps to use the tool:
>
> a. Extract portqry.exe:
> b. Open a Command Prompt window, and then run "portqry -local -l -v
> c:\portqry.txt".
> c. Check the file c:\portqry.txt to find what process is monitoring on the
> TCP port 80 of the external NIC and stop that process which is not IIS.
> You may send it to me so that I can check for you. My email address is
> v-yanniw@xxxxxxxxxxxxx
> And then try to test, how about the result?
>
> If that is ok, the issue still persists, I suggest that you export all
> your
> ISA rules and then run CEICW to try to test. How about the result?
>
> I appreciate your time and effort to perform test. I am currently standing
> by for you about the test result. I am always happy to be of further
> assistance.
>
> Have a nice day!
>
> Best Regards,
>
> Jenny Wu
> 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: "Rick" <nospam7@xxxxxxxxxx>
>>References: <OnL#k1BqFHA.2240@xxxxxxxxxxxxxxxxxxxx>
> <xX20tcKqFHA.2952@xxxxxxxxxxxxxxxxxxxxx>
>>Subject: Re: sbs2003 sp1 - cannot browse /remote, /monitoring, /outlook
>>Date: Wed, 24 Aug 2005 10:41:16 -0400
>>Lines: 195
>>X-Priority: 3
>>X-MSMail-Priority: Normal
>>X-Newsreader: Microsoft Outlook Express 6.00.2900.2670
>>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670
>>X-RFC2646: Format=Flowed; Original
>>Message-ID: <#3aSknLqFHA.3724@xxxxxxxxxxxxxxxxxxxx>
>>Newsgroups: microsoft.public.windows.server.sbs
>>NNTP-Posting-Host: cpe0004e24c204f-cm000039450660.cpe.net.cable.rogers.com
> 69.198.148.135
>>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP12.phx.gbl
>>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:147382
>>X-Tomcat-NG: microsoft.public.windows.server.sbs
>>
>>Jenny, thank you for your response.
>>
>>I re-ran CEICW and the problem still exists. I disabled socket pooling as
>>per http://support.microsoft.com/default.aspx?scid=KB;EN-US;238131 but
> that
>>didn't fix the problem either.
>>
>>Before I proceed with Step A (I don't want to take ISA out of the loop
> which
>>is what Step B looks like it does) could you please confirm that if I
> change
>>IIS to listen on the <internal IP> 192.168.16.2 and localhost (step A. 2)
>>and then change IIS Default web site to listen there I do not have to
> change
>>any settings in the ISA2004 firewall rules for the /rww, /owa, OL via RPC,
>>etc. They will be passed to the LAN?
>>
>>I will await your reply before proceeding.
>>
>>Thanks.
>>Rick
>>
>>
>>""Jenny wu [MSFT]"" <v-yanniw@xxxxxxxxxxxxxxxxxxxx> wrote in message
>>news:xX20tcKqFHA.2952@xxxxxxxxxxxxxxxxxxxxxxxx
>>> Hi Rick,
>>>
>>> Thanks for posting here.
>>>
>>> For your description, I understand that the issue is: you can not access
>>> RWW, OWA and OL from internet and get ISA Web Proxy - error 14200 and
>>> 14148. I am off base, please don't hesitate to let me know.
>>>
>>> This issue can occur if the Web Proxy service is unable to register
> itself
>>> to listen on the IP address and port that is specified. The Web Proxy
>>> service cannot listen on the port if the port is being used by another
>>> program, usually Internet Information Services (IIS) or another Web
>>> server.
>>>
>>> At first please try to rerun CEICW to ensure you have configured correct
>>> settings. You can refer to the following KB article:
>>> 825763 How to configure Internet access in Windows Small Business Server
>>> 2003
>>> http://support.microsoft.com/?id=825763
>>>
>>> 867483 How to configure networks in ISA Server 2004
>>> http://support.microsoft.com/?id=867483
>>>
>>> Try to test, how about the result?
>>>
>>> If the issue persists, please Use one of the resolutions below to clear
>>> the
>>> conflict.
>>>
>>> A. Configure the Default Web Site not to listen on the external IP.
>>>
>>> 1. Install the Support Tools from SBS 2003 CD #2 by running
>>> <cdromdrive:>\Support\Tools\suptools.msi
>>>
>>> 2. Run the following commands from a command prompt:
>>> a. C:\Program Files\Support Tools\httpcfg set iplisten -i <internal ip>
>>> b. C:\Program Files\Support Tools\httpcfg set iplisten -i 127.0.0.1
>>> c. net stop http /y
>>> d. net start w3svc
>>>
>>> 3. Configure the Default Web Site to listen on the Internal IP address.
>>> a. Click Start, point to Administrative Tools, and then click Internet
>>> Information Services (IIS) Manager.
>>> b. In Internet Information Services Manager, expand Server_Name, and
> then
>>> expand Web Sites.
>>> c. Right-click the Default Web Site, and then click Properties.
>>> d. On the Web Site tab, click the IP address drop down list and select
>>> the Internal IP address.
>>> e. Click OK.
>>>
>>> B. Disable the web publishing rule in ISA 2004.
>>> 1. Click Start, point to Programs, point to Microsoft ISA Server, and
> then
>>> click ISA Management.
>>> 2. In the ISA 2004 management console, expand ISAServerName , where
>>> ISAServerName is the name of your ISA 2004 server.
>>> 3. Click Firewall Policy.
>>> 4. In the Firewall Policy pane of the ISA 2004 management console,
>>> right-click the web publishing rule and click Disable.
>>> 5. In the Firewall Policy pane of the ISA 2004 management console, click
>>> Apply to apply the changes.
>>>
>>> I appreciate you time and effort. I am currently standing by for you
>>> about
>>> the test result. I am always happy to be of further assistance.
>>>
>>> Have a nice day!
>>>
>>> Best Regards,
>>>
>>> Jenny Wu
>>> 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: "Rick" <nospam7@xxxxxxxxxx>
>>>>Subject: sbs2003 sp1 - cannot browse /remote, /monitoring, /outlook
>>>>Date: Tue, 23 Aug 2005 16:01:10 -0400
>>>>Lines: 47
>>>>X-Priority: 3
>>>>X-MSMail-Priority: Normal
>>>>X-Newsreader: Microsoft Outlook Express 6.00.2900.2670
>>>>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670
>>>>X-RFC2646: Format=Flowed; Original
>>>>Message-ID: <OnL#k1BqFHA.2240@xxxxxxxxxxxxxxxxxxxx>
>>>>Newsgroups: microsoft.public.windows.server.sbs
>>>>NNTP-Posting-Host:
> cpe0004e24c204f-cm000039450660.cpe.net.cable.rogers.com
>>> 69.198.148.135
>>>>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!tk2msftngp13.phx.gbl
>>>>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:147110
>>>>X-Tomcat-NG: microsoft.public.windows.server.sbs
>>>>
>>>>Things were running fine until Sunday when no-one could connect to RWW,
>>> OWA
>>>>or OL via the Internet. They can connect to /companyweb however. The
> error
>>>>message from ISA is 'There is a server error in '/Remote' application.'
>>>>
>>>>We got application event errors on ISA Web Proxy - error 14200 and 14148
> -
>>>>failed to bind, and failed to map the path.
>>>>
>>>>All clients within the LAN are working OK, however, when I did a remote
> ts
>>>>connection to the server then tried to go to https://localhost/remote I
>>> get
>>>>the message:
>>>>Failed to map the path '/'.
>>>>Description: An unhandled exception occurred during the execution of the
>>>>current web request. Please review the stack trace for more information
>>>>about the error and where it originated in the code.
>>>>
>>>>Exception Details: System.Web.HttpException: Failed to map the path '/'.
>>>>
>>>>Source Error:
>>>>
>>>> An unhandled exception was generated during the execution of the
>>>>current web request. Information regarding the origin and location of
>>>>the
>>>>exception can be identified using the exception stack trace below.
>>>>
>>>>Stack Trace:
>>>>
>>>>[HttpException (0x80004005): Failed to map the path '/'.]
>>>>
>>>
> System.Web.Hosting.ISAPIWorkerRequestInProcForIIS6.MapPathSlowUsingIISCore(S
>>> tring
>>>>path) +240
>>>> System.Web.Hosting.ISAPIWorkerRequest.MapPath(String path) +419
>>>> System.Web.Configuration.HttpConfigurationSystem.ComposeConfig(String
>>>>reqPath, IHttpMapPath configmap) +519
>>>> System.Web.HttpContext.GetCompleteConfigRecord(String reqpath,
>>>>IHttpMapPath configmap) +437
>>>> System.Web.HttpContext.GetCompleteConfig() +50
>>>> System.Web.HttpContext.GetConfig(String name) +197
>>>> System.Web.CustomErrors.GetSettings(HttpContext context, Boolean
>>>>canThrow) +20
>>>> System.Web.HttpResponse.ReportRuntimeError(Exception e, Boolean
>>> canThrow)
>>>>+40
>>>> System.Web.HttpRuntime.FinishRequest(HttpWorkerRequest wr,
>>>> HttpContext
>>>>context, Exception e) +480
>>>>
>>>>
>>>>
>>>>How do I get ISA 2004 rules 2, 3, and 4 to publish to IIS Default?
>>>>
>>>>
>>>>
>>>
>>
>>
>>
>



.

Relevant Pages

  • Re: RWW Timing
    ... If you have installed ISA, ... Expand the server node and highlight ''Monitoring''. ... In the following website you can find many useful resources related to SBS ... Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.windows.server.sbs)
  • Re: Nagging Autorization issue for Companyweb after ISA04 install
    ... Check the companyweb CNAME entry in the DNS Server. ... Does the situation occur when you access companyweb from the ISA ... > 'Microsoft Firewall' service. ... > This newsgroup only focuses on SBS technical issues. ...
    (microsoft.public.windows.server.sbs)
  • Re: IIS web config
    ... The 1 IP 1 Port listener is by design on ISA Server. ... 'Microsoft Firewall' service. ... Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.windows.server.sbs)
  • RE: sloww web browsing
    ... and ISA 2004, the internet access became slower than it used to be. ... Open the ISA Server management console, ... Click Start, point to Programs, point to Microsoft ISA server, and then ... will you be able to access the internet from the internal client ...
    (microsoft.public.windows.server.sbs)
  • RE: ISA 2004 SP1 - Microsoft Firewall service not starting
    ... Then open the ISA management console, right click Cache and select Disable ... How to delete the Web cache in Internet Security and Acceleration Server ... Microsoft CSS Online Newsgroup Support ... This newsgroup only focuses on SBS technical issues. ...
    (microsoft.public.windows.server.sbs)