RE: Monitoring Error no emails comming through
- From: "Ziguana" <Ziguana@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 12 Jan 2006 17:43:02 -0800
Charles thankyou for you excelemt responce, it was the ISA port info.
Have a nice weekend.
Regards
""Charles Yang [MSFT]"" wrote:
> HI,
>
> Welcome to SBS newsgroup.
>
> Issue description:
> ==============
>
> I understand that you encountered problem when you want to view the server
> reports on the SBS server managements.
>
> Analyzing and suggestion:
> ===============
>
> Before we go any further for trouble shooting, could you let us know if you
> can access other internal website such as OWA or backup reports?
>
> Here I assume that you only encountered problem on monitoring components,
> please first refer to my suggestion below to reinstall monitoring
> components:
>
> Here, I would like to suggest you reconfigure the Monitoring and Reporting
> wizard to see if the problem will be resolved:
>
> NOTE: After doing the following steps, the original performance and usage
> data will be removed. The server will start to collect new counter value
> from the beginning. Please note that you need to choose reinstall not
> modify when run the wizard.
>
> 1. Open Server Management console, navigate to ''Monitoring and
> Reporting'' snap-in. In the right panel, click ''Set Up Monitoring Reports
> and Alerts''.
>
> 2. In the wizard, click ''Next''->Select ''Reinstall monitoring
> features''->Select the options if you want to receive the report e-mails.
> Check ''View the usage report in Server Management'' option. If you want to
> receive the usage report e-mail, also check the option below->Add the users
> which you allow them to view the usage report to the authorized
> list->Select the option if you want to receive the performance
> alerts->Click ''Finish'' button to complete the configurations.
>
> 3. After doing the above steps, the performance and usage data will
> be reset. Please wait for 24 hours and then you will see the reports
> through the Monitoring and Reporting console.
>
> If the issue still exists, please follow the steps below to reinstall
> monitoring reports on SBS 2003 SP1
>
> You just need to change the value of 'isrunfromweb' to '2', under
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SmallBusinessServer Then you can run
> integrate setup to reinstall monitoring components on the SBS 2003.
>
> If after changing the registry, you still can not reinstall monitoring
> components, please refer to the steps below:
>
> The extraction process is listed below, please do follow the exact steps or
> the extracted files will be removed.
>
> 1. Start a cmd prompt and change directory to the SP1 download
> folder (or the SBS03_SP1 folder on PKG_CD2).
>
> 2. Then key 'SBS2003-KB885918-SP1-X86-ENU.EXE /?', the installer
> extracts files into a guid-like folder name, on my box, it's
> C:\b5469c25ed0a876e198de1b10efc.
>
> 3. Meanwhile, the help message box is displayed. Do not click
> OK, or the GUID-like folder will vanish.
>
> 4. Instead, we go to 'Task Manager', end the process
> 'SBS2003-KB885918-SP1-X86-ENU.EXE' first, then, end the 'update.exe'
> process. By doing this, the install folder will remain on your hard disk.
> Note that you need to end these 2 process in turn.
>
> 5. Now go the download or CD folder which contains
> SBS2003-KB891193-X86-ENU.EXE. Open up a command console and issue
> 'SBS2003-KB891193-X86-ENU.EXE /?'.
>
> 6. The files will be extracted to another GUID-like folder and
> the Help window comes up. Again, we will not click OK on the Help window.
>
> 7. Go to 'Task Manager', and then end the process '
> SBS2003-KB891193-X86-ENU.EXE' and 'update.exe' in turn. That will end the
> install process without cleaning up the extracted files.
>
> 8. Run the SBS Integrated setup, and when the setup program
> prompts for the CD3, point it to the GUID folder created above. If the
> first folder doesn't what the setup program wants, point to the second
> folder.
>
> If the issue still exists after you reinstall monitoring components, please
> follow the steps below:
>
> I suggest you to check if the MSDE or SQL service (if you have SQL
> installed) started correctly.
>
> 1. Open Services snap-in (Services.msc)
> 2. Find MSSQL$YourInstanceName and MSSQL$SHAREPOINT and confirm they start
> correctly
> 3. If not, please open the properties of both services. In the log on tab,
> check the logon account if it is a specific account. If it is, please
> change the log on to Local System Account, started the server.
> For the monitoring screen in Server Management issue, please refer to the
> following suggestions
>
> SBS2003 Premium:
> <Typically ISA is installed and thus Default Website is bounded to the
> internal IP only.>
> Go to IIS, Default Web Site, Web Site tab, Advanced. Server should have the
> internal IP on port 80 and 127.0.0.1 on port 80. If the loopback is
> missing, click Add, and type 127.0.0.1 for the IP, 80 for the port, and do
> NOT assign any host header to 127.0.0.1.
>
> SBS2003 Standard:
> <ISA is not installed and thus Default Website is bounded to All
> Unassigned.>
> Go to IIS, Default Web Site, Web Site tab, Advanced. Verify the IP address
> Default does not have a host header. Removed any host header assiged to
> Default. If you have to assign a host header to the default website, please
> add 127.0.0.1 with port 80 and NO host header to the default website.
>
> NOTE: Monitoring and Reporting, and Backup snapin in Server Management
> communicate with the IIS Default Website using 127.0.0.1. Make sure
> 127.0.0.1 port 80 is available and no host header is assigned to 127.0.0.1.
>
> I appreciate your understanding on this issue, please feel free to let me
> know the results. I am glad to be of assistance.
>
>
>
> Best regards,
>
> Charles Yang (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.
>
>
> =====================================================
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> --------------------
> | Thread-Topic: Monitoring Error no emails comming through
> | thread-index: AcYWYdJBGLOXdSQdRGikhR6jmnL4gA==
> | X-WBNR-Posting-Host: 203.202.148.238
> | From: "=?Utf-8?B?WmlndWFuYQ==?=" <Ziguana@xxxxxxxxxxxxxxxxxxxxxxxxx>
> | Subject: Monitoring Error no emails comming through
> | Date: Tue, 10 Jan 2006 19:48:02 -0800
> | Lines: 25
> | Message-ID: <B0C72D1E-CAC7-4840-A6E0-D089A8B0899A@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.0
> | Newsgroups: microsoft.public.windows.server.sbs
> | NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
> | Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
> | Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.windows.server.sbs:235672
> | X-Tomcat-NG: microsoft.public.windows.server.sbs
> |
> | For some reason all of a sudden my daily report that I have emailed to me
> | isn't coming through with the data, it comes through with an error.
> Anyone
> | any ideas?
> |
> | When I go into server management and monitoring and reporting the below
> | error comes up instead of the report. I have tried resetting up the
> reports
> | etc and have checked that the file it talks about is there and all
> appears to
> | be fine: -
> |
> | Server Error in '/' Application.
> ----------------------------------------------------------------------------
> ----
> |
> | The resource cannot be found.
> | Description: HTTP 404. The resource you are looking for (or one of its
> | dependencies) could have been removed, had its name changed, or is
> | temporarily unavailable. Please review the following URL and make sure
> that
> | it is spelled correctly.
> |
> | Requested Url: /monitoring/perf.aspx
> |
> |
> ----------------------------------------------------------------------------
> ----
> | Version Information: Microsoft .NET Framework Version:1.1.4322.2032;
> ASP.NET
> | Version:1.1.4322.2032
> |
> |
>
>
.
- Follow-Ups:
- RE: Monitoring Error no emails comming through
- From: "Charles Yang [MSFT]"
- RE: Monitoring Error no emails comming through
- References:
- RE: Monitoring Error no emails comming through
- From: "Charles Yang [MSFT]"
- RE: Monitoring Error no emails comming through
- Prev by Date: RE: J'ai perdu la main sur mon serveur !!!!!
- Next by Date: Re: invisible 4GB file on C: Drive
- Previous by thread: RE: Monitoring Error no emails comming through
- Next by thread: RE: Monitoring Error no emails comming through
- Index(es):