RE: legacyexchangedn

2003-07-16 Thread John Parker
This was the only thing I could find from www.eventid.net Look for the following key in the registry: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\VirusScan and set Enabled to a value of 0. Stop and restart the exchange services. If the information store comes up after the

Re: legacyexchangedn

2003-07-16 Thread Tony Hlabse
I have run into this before. IIRC it has to do with a setting in the registry. Search the Local on the Server itself for the Restore in progress It has to be set to one then try starting the IS. Something about SP patch level differences. There is a Q article on this too. Do not remember the

RE: legacyexchangedn

2003-07-16 Thread Woodruff, Michael
Restore in progress would be a registry key to look for and set to 1... Just to clarify. Thanks for the help BTW. -Original Message- From: Tony Hlabse [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 16, 2003 11:07 AM To: Exchange Discussions Subject: Re: legacyexchangedn I have run

RE: legacyexchangedn

2003-07-16 Thread Tony Hlabse
] Subject: RE: legacyexchangedn Date: Wed, 16 Jul 2003 11:24:25 -0400 Restore in progress would be a registry key to look for and set to 1... Just to clarify. Thanks for the help BTW. -Original Message- From: Tony Hlabse [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 16, 2003 11:07 AM

RE: legacyexchangedn

2003-07-16 Thread Woodruff, Michael
. ESEUTIL now shows the database as clean now. This is where the stated error comes in? -Original Message- From: Tony Hlabse [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 16, 2003 11:30 AM To: Exchange Discussions Subject: RE: legacyexchangedn Yes I found one article hopefully it will help

RE: legacyexchangedn

2003-07-16 Thread Tony Hlabse
-To: Exchange Discussions [EMAIL PROTECTED] To: Exchange Discussions [EMAIL PROTECTED] Subject: RE: legacyexchangedn Date: Wed, 16 Jul 2003 11:41:24 -0400 Here's the deal.. I only had a priv.edb from a corrupted database backup. I ran eseutil /P and created a new .stm file as well. It ran fine

RE: legacyexchangedn

2003-07-16 Thread Couch, Nate
I don't believe there is a Restore in Progress key entry for Exchange 2000. Nate Couch EDS Messaging -Original Message- From: Woodruff, Michael [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 16, 2003 10:24 AM To: Exchange Discussions Subject: RE: legacyexchangedn Restore in progress

RE: legacyexchangedn

2003-07-16 Thread Tony Hlabse
] Subject: RE: legacyexchangedn Date: Wed, 16 Jul 2003 10:50:35 -0500 I don't believe there is a Restore in Progress key entry for Exchange 2000. Nate Couch EDS Messaging -Original Message- From: Woodruff, Michael [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 16, 2003 10:24 AM To: Exchange

RE: LegacyExchangeDN

2002-02-05 Thread Michel, David
ADSI EDIT from Microsoft is probably the easiest to learn but any other ldap query program will work. -Original Message- From: Sabo, Eric [mailto:[EMAIL PROTECTED]] Sent: Tuesday, February 05, 2002 1:58 PM To: Exchange Discussions Subject: LegacyExchangeDN I'm trying to recover my

RE: LegacyExchangeDN

2002-02-05 Thread Ronald Mazzotta
What I did was on my recovery server I ran forest prep then installed ONLY the exchange sys admin. You can then go into it and install your appropriate admin group that matches you prod net. It's easier than changing all those exchangelegacydn's Director of IT, Ronald Mazzotta -Original

RE: LegacyExchangeDN

2002-02-05 Thread Sabo, Eric
To: Exchange Discussions Subject: RE: LegacyExchangeDN What I did was on my recovery server I ran forest prep then installed ONLY the exchange sys admin. You can then go into it and install your appropriate admin group that matches you prod net. It's easier than changing all those exchangelegacydn's