• RSS
  • Twitter
  • FaceBook

Exchange Server Forums

Forums | Register | Login | My Profile | Inbox | RSS RSS icon | My Subscription | My Forums | Address Book | Member List | Search | FAQ | Ticket List | Log Out

Migrated to 2010

Users viewing this topic: none

Logged in as: Guest
  Printable Version
All Forums >> [Microsoft Exchange 2003] >> Migration >> Migrated to 2010 Page: [1]
Login
Message << Older Topic   Newer Topic >>
Migrated to 2010 - 14.Sep.2010 10:49:53 AM   
MCornejo

 

Posts: 3
Joined: 3.Jun.2010
Status: offline
We recenlty upgraded a client of our to Exchange 2010 on a new server. The old server running Exchange 2003 is still running and is no longer running the mailstore or mailboxes as they have been migrated to the new server. The old Exhange server is still giving me errors in the event log such as MSEXhangeSA 9175. How can I get the server to stop this without removing Exchange. Not sure why we still have it going though. Thanks.
Post #: 1
RE: Migrated to 2010 - 14.Sep.2010 11:32:00 AM   
de.blackman

 

Posts: 3542
Joined: 4.Apr.2005
From: Toronto, Canada
Status: offline
Check to make sure that the information store service is running and the databases are mounted. Event ID 9175 are usually generated when the system attendant service attempts to log into the database but it cannot (service not started or database not mounted).

_____________________________

Ibrahim Benna - Microsoft Exchange MVP
Forum Moderator
Navantis
@IbrahimBenna

(in reply to MCornejo)
Post #: 2
RE: Migrated to 2010 - 14.Sep.2010 11:34:07 AM   
MCornejo

 

Posts: 3
Joined: 3.Jun.2010
Status: offline
The problem with that is that this server no longer acts as an Exchange server as we have upgraded to Exchange 2010. This server now is only running as we make sure that there is no longer a need for us to have it up. In the mean time I would like to know if there was a way of making sure these alerts do not fill my event log.

(in reply to de.blackman)
Post #: 3
RE: Migrated to 2010 - 14.Sep.2010 3:29:15 PM   
de.blackman

 

Posts: 3542
Joined: 4.Apr.2005
From: Toronto, Canada
Status: offline
I am not sure what you mean. Just because this server is not runnign any exchange roles, it still exists as an Exchange server, correct?

As I mentioned in my first post, Exchange system attendant process attempts requires to be logged into a mailbox database (the first mailbox database in an exchange server contains the system attendant mailbox). If the service cannot connect because the information store service is stopped or the database(s) are offline, then you will receive these errors.

Simply said, if you want these errors to stop, then start the information store service AND mount all mailbox databases on the server. The best way to make sure this server is no longer needed is to have it completely shutdown for a few days and make sure everything runs smoothly on Exchange 2010. Hope this clarifies things!

_____________________________

Ibrahim Benna - Microsoft Exchange MVP
Forum Moderator
Navantis
@IbrahimBenna

(in reply to MCornejo)
Post #: 4

Page:   [1] << Older Topic    Newer Topic >>
All Forums >> [Microsoft Exchange 2003] >> Migration >> Migrated to 2010 Page: [1]
Jump to:

New Messages No New Messages
Hot Topic w/ New Messages Hot Topic w/o New Messages
Locked w/ New Messages Locked w/o New Messages
 Post New Thread
 Reply to Message
 Post New Poll
 Submit Vote
 Delete My Own Post
 Delete My Own Thread
 Rate Posts


Follow TechGenix on Twitter