Re: error after updateing with latest Exchange updates
- From: "Adam Raff" <araff@xxxxxxxxxxxxxxxx>
- Date: Tue, 22 May 2007 14:17:12 -0400
Hi Robert,
Thanks for responding on this matter.
I wanted to clarify some information first. We have been running Exchange
2003 with SP2 for some time. When we updated our server with May updates
that is when I received the first error and that is after the reboot.
This was the events before and after the error. Also the error is in this
as well.
IIS is set for Automatic, I checked that first thing. I noticed that when I
rebooted the server I received those errors and I also noticed that the
event before and after
Event Type: Information
Event Source: Service Control Manager
Event Category: None
Event ID: 7040
Date: 5/17/2007
Time: 5:33:55 PM
User: HSPOP\Administrator
Computer: HSMAIL
Description:
The start type of the IIS Admin Service service was changed from auto start
to disabled.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10005
Date: 5/17/2007
Time: 5:34:09 PM
User: N/A
Computer: HSMAIL
Description:
DCOM got error "The service cannot be started, either because it is disabled
or because it has no enabled devices associated with it. " attempting to
start the service IISADMIN with arguments "" in order to run the server:
{A9E69610-B80D-11D0-B9B9-00A0C922E750}
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Event Type: Information
Event Source: Service Control Manager
Event Category: None
Event ID: 7040
Date: 5/17/2007
Time: 5:34:15 PM
User: HSPOP\Administrator
Computer: HSMAIL
Description:
The start type of the IIS Admin Service service was changed from disabled to
auto start.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
I am going to reboot the server to see if the error reappears and I will get
back to you on this matter when I do. If you have any other suggestions
please let me know. Also note that I did apply the Exchange update MS07-026
that was listed for May. Would the exchange update cause this error by
chance?
"Robert Li [MSFT]" <v-robeli@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:s2t53gFnHHA.1144@xxxxxxxxxxxxxxxxxxxxxxxxx
Hi Adam,
Thanks for posting in our newsgroup.
From your description, I know that after you updated our Exchange 2003
Sever SP2 with you received Event ID 10005. If I am off-base, please don't
hesitate to let me know.
Please take the following steps to see if the problem can be resolved:
Step 1: Based on my research, the IIS Admin Service is set to start
automatically. You can enable the service and see if the problem can be
reproduced:
1. Run services.msc command.
2. Double click IIS Admin Service.
3. On the General tab, select the start type to automatic.
4. Click Start.
5. Monitor if the problem will be reproduced.
More information:
Exchange Setup Fails with Error 0x80070422
http://support.microsoft.com/default.aspx?scid=KB;EN-US;295623
For the Event ID 1057 , I believe this warning can be safely ignored as
this warning is only related to the IMAP4 service. Typically, IMAP4
connections are used if there are either bandwidth limitations or firewall
port restrictions but greater flexibility is required than what POP3
connections can provide.
Otherwise, if you are using IMAP4 connections, since this error indicates
the certificate used by IMAP4 virtual server has expired, you can recreate
a new certificate. Please follow the "How to Configure Secure
Communications (Part One)" section in the article below
319278 HOW TO: Secure Internet Message Access Protocol Client Access in
http://support.microsoft.com/?id=319278
Hope the information helps.
If you need further assistance, please don't hesitate to let me know.
1.Visit
http://download.microsoft.com/download/b/b/1/bb139fcb-4aac-4fe5-a579-30b0bd9
15706/MPSRPT_Exchange.EXE to download the file.
2. Run the MPSRPT_Exchange.EXE on the server box.
3. Wait for 10~15 minutes.
4. Open Windows explorer, navigate to
%SYSTEMROOT%\MPSReports\Exchange\cab\
5. Send the .cab file directly to to v-robeli@xxxxxxxxxxxxx with subject:
error after updateing with latest Exchange updates.
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 Online Support
Microsoft Global Technical Support Center
Get Secure! - www.microsoft.com/security
=====================================================
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.
.
- Follow-Ups:
- Re: error after updateing with latest Exchange updates
- From: Robert Li [MSFT]
- Re: error after updateing with latest Exchange updates
- References:
- error after updateing with latest Exchange updates
- From: Adam Raff
- RE: error after updateing with latest Exchange updates
- From: Robert Li [MSFT]
- error after updateing with latest Exchange updates
- Prev by Date: Re: hundreds of messages from <> in my queue
- Next by Date: Re: ESEUTIL does not reduce the PRIV1.EBD and STM file
- Previous by thread: RE: error after updateing with latest Exchange updates
- Next by thread: Re: error after updateing with latest Exchange updates
- Index(es):
Relevant Pages
|
