Re: Exchange SP1 stopped all smtp traffic

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

P.S. Ran it against servername:80 and received the following message:

Cannot upgrade virtual server http://stargate:80. Windows SharePoint
Services do
es not support in-place upgrading of SharePoint Team Services v. 1.0 from
Micros
oft or FrontPage Server Extensions. You must migrate the content from this
virtu
al server to a new virtual server extended with Windows SharePoint Services.



"Dave Nickason [SBS MVP]" wrote:

This looks like the solution:

Installation fails and mail flow stops when you install Exchange Server 2003
Service Pack 1 (SP1)
http://support.microsoft.com/kb/919076


"Daveinfla" <Daveinfla@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:517EAC3C-EBDB-454D-BCFB-039098961BBA@xxxxxxxxxxxxxxxx
This was a fresh install of SBS 2003 Standard on a new server, I just
forgot
to install the service patches and decided to do them last night.

I've rebooted several times.

I've re-run CEICW and rebooted.

I've removed GFI Mail Essentials, rebooted.

The SMTP service is running, I wouldn't be able to telnet to it and send
e-mail if it wasn't.

No additional info. is listed under the queues in ESM, the local queue IS
receiving messages, not up to 64 messages and the "Messages awaiting
directory lookup" queue has 19 waiting.

I did locate the following errors in the application log, in addition upon
reboot I get a crash recovery type popup box after each bootup that IIS
has
faild to run:

"Initialization of external interface SMTP failed; Error
ecVersionMismatch-MAPI_E_VERSION."

"#50070: Unable to connect to the database STS_Config on
SERVERNAME\SharePoint."

No client side errors have been observed, Outlook connects, sends receives
messages leave but never get to the destination and nothing shows up on
inbound as they are stuck in the queue.

I re-ran the SP install and still nothing, however it did remind me that
during the step it "Messaging and Colaboration..." it finishes with an
error
about not restarting in a timely fasion, it occured both times.

Re-loading isn't really a big deal, only a few users on it, but I'd sure
like to know what I did wrong to prevent this from happening in the
future.

Should I have removed GFI before the SP upgrade? Or was this a fluke?

If someone comes up with a quick fix for this I'm all ears and will wait
an
hour or so, but will probably start on a reinstall later tonight.

Thanks,

Dave




"Dave Nickason [SBS MVP]" wrote:

You've rebooted the server since all of this, right? If not, please try
that first. If it's still not working, I would try re-running the CEICW
and, for any page not related to e-mail, choose the "do not change"
option.
For the e-mail pages, just verify that the information is correct. You
don't mention ISA, but in particular if you upgraded to ISA 2004 as part
of
the SP install, you definitely need to re-run the CEICW.

When you view the queues in ESM, is there anything insightful at the
bottom
of the screen under "additional queue information?" Is Outlook giving an
error when messages fail to send, or logging anything in the app log on
the
client PC? When you say you can telnet in, can you do that from outside
your network as opposed to just from your desktop PC?

I wouldn't even consider formatting and reinstalling at this point.
Whatever this is is fixable, and at worst, you should be able to get free
support for a failed SP install.



"Daveinfla" <Daveinfla@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:6ABBDAF9-0CC9-4238-A2D5-7E52DBF3C4FD@xxxxxxxxxxxxxxxx

Last night I upgraded SBS 2003 to SP1 following the step by step
instructions which included the following steps:

Install Windows Server 2003 Service Pack 1
Install Windows SharePoint Services 2.0 Service Pack 1
Install Exchange Server 2003 Service Pack 1
Install Windows XP SP2 for Client Deployment
Install Windows Small Business Server 2003 Service Pack 1

Immediately following I lost all smtp traffic, the local queue is just
filling up.

I have no event log errors except for the fact that SharePoint will not
start and IIS produces and error upon boot, stating it had to close.
The
company web is also broken.

I was running GFI mail filter and removed it to see if the upgrades
botched
it, this had no affect.

Any ideas? I'm about the re-format and start from scratch, what a pain.









.

Relevant Pages

  • Defect in installer for Antivirus Corp Ed 9.0.1.1000 when upgrading from 9.0.0.x
    ... antivirus solution and have Windows XP desktops you'd like to upgrade to XP ... SP2 and wish to have the most recent build of SAV 9 that is XP SP2 compatible. ... to install to servers & PCs to provide XP SP 2 compatibility. ... Once you upgrade your Primary Server to 9.0.1.1000 and attempt to ...
    (NT-Bugtraq)
  • Re: 2008 or 2003
    ... To install a 2008 DC in a 2003 domain the schema has to be upgraded to version 44. ... The schema is the same in your complete domain, the schema upgrade will add additional AD objects which are needed for 2008. ... 2008 ad schema instead of setting it up as a 2003 AD server I need all ...
    (microsoft.public.windows.server.setup)
  • RE: DNS Question on NT4 to AD upgrade
    ... With the dell you can install NT4.0 it is just is not supported by dell. ... Then perform your upgrade on the NT 4.0 Machine although this ... pointing to the new WINS server on the first dhcp scope. ...
    (microsoft.public.win2000.active_directory)
  • Re: SBS2003/NT4 migration - Trust issue?
    ... Introduced SBS into the existing AD. ... I am having a problem with an SBS 2003 upgrade. ... Install temporary NT4 server on spare hardware, ...
    (microsoft.public.windows.server.sbs)
  • RE: Possible to install Excel 2003 and InfoPath additionaly to a B
    ... I assume WSS is Windows SharePoint? ... setup the server. ... So I will install InfoPath additionaly. ...
    (microsoft.public.biztalk.general)