Solved

Can't restart smtpsvc?

Posted on 2009-07-07
9
1,512 Views
Last Modified: 2012-05-07
I'm experiencing the problem detailed in http://support.microsoft.com/kb/950757 on my Exchange server.  I read in another thread here on EE, that an alternative to installing the hotfix from Microsoft is to set up a scheduled task to manually stop and start the smtpsvc, with the idea being that NDRs will be generated for any messages still in the queue at that time.

I've set up a batch file, but when I try to run "net stop smtpsvc" I get:

The Simple Mail Transfer Protocol (SMTP) service is stopping................
The Simple Mail Transfer Protocol (SMTP) service could not be stopped.

When I check the event log, I see this:

Cluster resource 'SMTP Virtual Server Instance 1 (EXCHANGE01)' in Resource Group 'Exchange Resources' failed.

I'm assuming MSCS doesn't like me manually restarting services.  Is there any way I can get around this?

0
Comment
Question by:FWeston
  • 5
  • 3
9 Comments
 
LVL 9

Expert Comment

by:PC_Rob
ID: 24798019
Try using the IISRESET command instead.  It also resets the SMTP service I believe.

Here is a detailed article of usage:

http://support.microsoft.com/kb/202013

iisreset /restart usually does it for me when I can't get the service to stop from the services manager.

Regards,

Rob
0
 
LVL 3

Author Comment

by:FWeston
ID: 24798159
That seems like it might work, but I'd really rather not take down IIS if I can help it, since that would kick people out of OWA and would temporarily break ActiveSync.
0
 
LVL 65

Expert Comment

by:Mestha
ID: 24802803
Any reason you don't want to install the hotfix for the greylisting bug?
It takes about two minutes to get and then install.

Simon.
0
Optimizing Cloud Backup for Low Bandwidth

With cloud storage prices going down a growing number of SMBs start to use it for backup storage. Unfortunately, business data volume rarely fits the average Internet speed. This article provides an overview of main Internet speed challenges and reveals backup best practices.

 
LVL 3

Author Comment

by:FWeston
ID: 24813146
Yes - we only have one user who's mentioned this problem to us, and the amount of messages it affects is miniscule.  MS recommends only installing the hotfix if the problem is seriously affecting you, so I'd rather avoid introducing any random elements into our Exchange setup if possible since that's probably the most critical service we provide.  The SMTP restart seems like it should solve the problem without requiring us to install any software.
0
 
LVL 65

Expert Comment

by:Mestha
ID: 24814067
I install the hotfix on to every server that I deploy, and haven't seen any problems with it. I actually asked Microsoft if they would push out on Automatic updates, but for some reason they declined to.

Restarting SMTP is fine, unless you happen to be receiving a message at the time.

Personally I would have no problems with deploying the patch, and I encourage everyone with Exchange 2003 to do so.

Simon.
0
 
LVL 3

Author Comment

by:FWeston
ID: 24814251
If this were a new installation, I wouldn't have any problem installing a hotfix, but since it's established and is mission critical, I'd rather not do it unless absolutely necessary.  Regarding the SMTP restart, if the message isn't completely received, I assume it would be treated as a failure and would be thrown in the retry queue.
0
 
LVL 65

Accepted Solution

by:
Mestha earned 500 total points
ID: 24814535
Not always.
It depends on how the message is NDR'd.

As for your original question, due to the way clustering works, I believe your only option is to failover to the other cluster.

I have deployed the patch on more servers than I can count, including clustered servers, with no ill effects. I haven't had an Exchange 2003 patch cause a problem since the first post SP1 update that changed the behaviour of the Full Mailbox Access permission for admin accounts.

Simon.
0
 
LVL 3

Author Comment

by:FWeston
ID: 24814754
That makes sense, and is what I was thinking regarding the SMTP restart, but wasn't sure how to confirm it.  I'll take your word for it, and we'll go ahead and install the hotfix.
0
 
LVL 3

Author Closing Comment

by:FWeston
ID: 31600791
Installed the patch with no issues
0

Featured Post

Does Powershell have you tied up in knots?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This process describes the steps required to Import and Export data from and to .pst files using Exchange 2010. We can use these steps to export data from a user to a .pst file, import data back to the same or a different user, or even import data t…
Read this checklist to learn more about the 15 things you should never include in an email signature.
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager
This video shows how to quickly and easily add an email signature for all users on Exchange 2016. The resulting signature is applied on a server level by Exchange Online. The email signature template has been downloaded from: www.mail-signatures…

777 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question