Exchange Server Forums

Win2k + Exchange + Windows Update = Broken Exchange

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [Microsoft Exchange 2000] >> General >> Win2k + Exchange + Windows Update = Broken Exchange

Page: [1]

Message

<< Older Topic Newer Topic >>

Limited time MSExchange.org offer! -- 1.Sep.2008 1:00:00 PM

TechGenix and SolarWinds have partnered to provide free copies of SolarWinds Exchange Monitor to all visitors who join the MSExchange.org Forums. SolarWinds Exchange Monitor is a handy desktop dashboard that continuously monitors Microsoft Exchange to deliver real-time insight into Exchange services, mail queue sizes, and host server health. Learn more about Exchange Monitor and the free offer!

Win2k + Exchange + Windows Update = Broken Exchange - 28.Oct.2001 3:59:00 AM

j_h_o

Posts: 1
Joined: 28.Oct.2001
Status: offline

After a clean format and Microsoft Exchange 2000 and SP1, I visited Windows Update where it proceeded to apply a bunch of 'critical updates'.

After the requested reboot, the Microsoft Exchange Information Store no longer starts (hung on starting) , and Event Viewer reports event ID 7022.

Any ideas?

Post #: 1

Featured Links*

RE: Win2k + Exchange + Windows Update = Broken Exchange - 28.Oct.2001 4:46:00 AM

jeffj

Posts: 145
Joined: 23.Oct.2001
Status: offline

What is the Source in 7022?

(in reply to j_h_o)

Post #: 2

RE: Win2k + Exchange + Windows Update = Broken Exchange - 23.Nov.2001 2:45:00 PM

Guest

quote:
Originally posted by jeffj:
What is the Source in 7022?

Hello, I recently added SQL 2000+ SQL 2000SP1 to a Win2000 server running Win2kSP1 and Exchange 2000+Ex2kSP1.

Installing SQL2000 was ok, until i added SQL2000SP1 ! At that point, the information store service refused to start (store.exe) ... mad panic ensued !

The solution was to upgrade the server to Win2kSP2, which I had wanted to do anyway and is otherwise a good idea.

On the subject of using windowsupdate... I usually fully update any new servers being added to the domain, but I always make sure to add ALL critical updates - if you are selective, you might have problems. In much the same way as major updates such as win2ksp2 are tested before release, I think windowsupdate testing occurs assuming that ALL critical updates up to that point have been applied.

(in reply to j_h_o)

Post #: 3