RE: Monitoring and Reporting Errors
- From: v-robeli@xxxxxxxxxxxxxxxxxxxx (Robert Li [MSFT])
- Date: Tue, 20 Mar 2007 08:16:04 GMT
Hi John,
Thanks for posting in our newsgroup.
From your description, I know that you get error when you view the reportfrom e-mail. If you change the DefaultAppPool to run as Local Service
account, the system works OK. If I am off-base, please don¡¯t hesitate to
let me know.
Based on my research, the DefaultAppPool runs under Network Service account
by default. If you change that to local system account, you will get Server
Application Unavailable error.
Please take the following steps to see if the problem can be resolved:
Step 1:Please verify the Monitoring VD settings in IIS server:
1. Open IIS snap-in.
2. Go to Default Web Site/Monitoring.S
3. Right click Monitoring and click Properties.
4. Click Virtual Directory tab.
5. Please ensure you have input proper Local Path (C:\Inetpub\Monitoring)
and also ensure the checkbox of Read, Log Visit and Index this resource are
checked.
And also ensure Application Settings as follows:
--Application Name: Monitoring
--Execute Permissions: Script only
--Application Pool: DefaultAppPool
6. Click Directory Security tab.
7. Click Edit under "Authentication and access control".
8. Make sure that only the option "Integrated Windows Authentication"
checked.
9. Click Edit under "IP address and domain name restriction".
10. Make sure that "Granted access" has been selected.
11. Click Edit under "Secure communications".
12. Make sure that "Require secure channel (SSL)" is UNchecked.
13. Please double-check the default application pool in IIS. To do so:
1). Open IIS Manager.
2). Go to Server/Application Pools/DefaultAppPool.
3). Right click DefaultAppPool and click Properties.
4). Click the Identity tab.
5). Make sure the application pool is using "Predefined: Network Service"
as its identify.
14. Run IISReset command and check whether the problem persists.
Step 2: Please change the ASP.NET version to 1.1.4322 on the Monitoring
Virtual Directory. To do so:
1. Open IIS snap-in.
2. Go to Default Web Site/Monitoring.
3. Right click Monitoring and click Properties.
4. Click ASP.NET tab, please change the ASP.NET version to 1.1.4322.
5. Run IISReset command to take effect the change.
Step 3: If the issue persists, please verify the permissions as follows:
1. Start Windows Explorer and go to C:\Windows\Microsoft.Net\Framework.
2. Right click the "v1.1.4322" folder and choose Properties.
3. Click the Security tab.
4. Click Add to add the "Local Service" and "Network Service" accounts and
then give them both the following permissions:
Read & Execute
List Folder Contents
Read
5. Double click to open the "v1.1.4322" folder. Right click the "Temporary
ASP.NET Files" folder and choose Properties.
6. Click the Security tab.
7. Add the "IIS_WPG", "Local Service" and "Network Service" accounts to the
list and then give them the "Full Control" permission. Click OK.
8. At a command prompt, type "IISRESET" (without the quotation mark) and
then press ENTER. Then check if everything is working well.
Step 4: Run the following command where at command prompt:
secedit /configure /db c:\windows\temp\seceditsv.sdb /cfg
"c:\windows\security\templates\setup security.inf" /log
c:\windows\temp\seceditsv.log
This sets the local security policy back to default, and allowed the
License Logging Service and other such services to start using the Network
service account. Restart the SBS Server to have a check
If the issue persists, please help me collect the following information for
analyze:
1. Please help to collect the IIS metabase for analyze:
To collect the IIS metabase on Server:
1). On Exchange Server, install .NET Framework Version 1.1:
http://www.microsoft.com/downloads/details.aspx?FamilyID=262d25e3-f589-4842-
8157-034d1e7cf3a3&DisplayLang=en.
2). Install MBExplorer by installing IIS 6 Resource Kit Tools:
http://www.microsoft.com/downloads/details.aspx?FamilyId=56FC92EE-A71A-4C73-
B628-ADE629C89499&displaylang=en.
3). Once it is installed, access it from Start, Programs, IIS Resources,
Metabase Explorer.
4). In the left pane, right click ''LM'' (under your server computer name)
to choose ''Export to file'', and then save it as IIS.mbk.
5). Compress this mbk file and send it to me for analysis. Please let me
know the password if you set on this iis mbk file.
2. Please collect the Setup MPS Reports for analyze:
1) Please download the MPSRPT_SETUPPerf.EXE from the following link and
then run this tool to gather some information from the problematic computer:
http://www.microsoft.com/downloads/details.aspx?familyid=cebf3c7c-7ca5-408f-
88b7-f9c79b7306c0&displaylang=en
2) Double-click on the MPSRPT_SETUPPerf.EXE file.
[Note] This process may take some time; however, it will not have a
negative effect on the performance.
c. A CAB file will be generated in the
%systemroot%\MPSReports\Setup\Reports\Cab directory called
%COMPUTERNAME%_MPSReports.CAB. The CAB file will contain the reports
generated by the MPS Reporting Tool.
Please send the log files to my mailbox: v-robeli@xxxxxxxxxxxxx with
subject: 38391797-Monitoring and Reporting Errors.
I am looking forward to hear from you.
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.
--------------------
<Thread-Topic: Monitoring and Reporting Errors
<thread-index: AcdqWMS1fFc92JpsSoaz8iM/NJwi6g==
<X-WBNR-Posting-Host: 24.69.165.189
<From: =?Utf-8?B?Sm9obiBfIFg=?= <JohnX@xxxxxxxxxxxxxxxxxxxxxxxxx>
<Subject: Monitoring and Reporting Errors
<Date: Mon, 19 Mar 2007 11:59:49 -0700
<Lines: 27
<Message-ID: <281C3092-3867-495C-B4C1-484DE997661C@xxxxxxxxxxxxx>
<MIME-Version: 1.0
<Content-Type: text/plain;
< charset="Utf-8"
<Content-Transfer-Encoding: 7bit
<X-Newsreader: Microsoft CDO for Windows 2000
<Content-Class: urn:content-classes:message
<Importance: normal
<Priority: normal
<X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2757
<Newsgroups: microsoft.public.windows.server.sbs
<Path: TK2MSFTNGHUB02.phx.gbl
<Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:23830
<NNTP-Posting-Host: tk2msftsbfm01.phx.gbl 10.40.244.148
<X-Tomcat-NG: microsoft.public.windows.server.sbs
<
<I have this error page when i try to view my reports locally or in my
daily
<email.
<It would appear to be an app problem, but i have narrowed it down to a
<security issue. If i run the DefaultAppPool as network auth/network
service,
<i get the error
<If i run it as a local service (i know..security issues) it runs fine.
<Any suggestions on how to get this back to net auth?
<
<
< Page error:
<The page cannot be displayed
<An error occurred on the page you are trying to view.
<
----------------------------------------------------------------------------
----
<
<To work around this problem, perform the following steps. After each step,
<try again to access the page.
<
<Ensure that the MSSQL$SBSMONITORING service is started.
<Ensure that the server is not low on memory or disk space.
<Restart the server.
<Verify that the server is functional and that there are no system-wide
<problems.
<Run the Set Up Monitoring Reports and Alerts task in the Server Management
<Monitoring and Reporting taskpad.
<
<
<
.
- Follow-Ups:
- RE: Monitoring and Reporting Errors
- From: John _ X
- RE: Monitoring and Reporting Errors
- Prev by Date: Re: <<VPN, SecureNat/Nat and Outlook clients not working after installing Windows Service Pack 2 in SBS 2003 Premium>>
- Next by Date: Re: companyweb
- Previous by thread: RE: Windows Server SP2
- Next by thread: RE: Monitoring and Reporting Errors
- Index(es):
Relevant Pages
|
Loading