RE: Repairing / modyfing Exchange
- From: v-natliu@xxxxxxxxxxxxxxxxxxxx ("Nathan Liu [MSFT]")
- Date: Tue, 09 Aug 2005 08:34:39 GMT
Hi Georgek,
Thank you for your kind update.
Please note that we are happy to work with you on this issues here,
however, if this response time does not meet your needs, please contact
Customer Service and Support (CSS) for more immediate assistance. For more
information on available CSS services, please click here:
http://support.microsoft.com/default.aspx?scid=fh;EN-US;OfferProPhone#faq607
In escalated customer situations, Business-Critical Phone Support provides
you with technical phone support at no charge during critical LAN outages
or "business down" situations. This benefit is available 24 hours a day, 7
days a week to all Microsoft technology partners in the United States and
Canada.
This service gives you access to Microsoft technical support engineers who
can help you solve critical technical issues for non-developer products
that affect a function critical to your customers' business. Outside the
United States and Canada, hours of availability for business-critical
support may differ.
This and other support options are available here:
https://partner.microsoft.com/US/technicalsupport/supportoverview/.
If you are outside the United States, please visit our International
Support page: http://support.microsoft.com/common/international.aspx.
Alternatively, I'm glad to provide the below suggestion for your reference:
1. As you mentioned, you have reinstalled the Exchange, and overwrote the
database by using the old Server's database files, but the Exchange cannot
correctly work now. If you have backup the appropriate Exchange database
before you overwrote the database by using the old Server's database files,
please restore it back and try again.
2. If you don't have backup the appropriate Exchange database before you
overwrote the database by using the old Server's database files, please
refer to the KB article 313184 to recover the Exchange databases:
313184 How to recover the information store on Exchange 2000 in a single
site
http://support.microsoft.com/?id=313184
893083 Top support issues for the Exchange information store
http://support.microsoft.com/?id=893083
I am appreciated your time and cooperation. If anything is unclear, please
feel free to let me know. I am looking forward to hearing from you.
Best regards,
Nathan Liu (MSFT)
Microsoft CSS Online Newsgroup Support
Get Secure! - www.microsoft.com/security
======================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.
Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.
For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.
Any input or comments in this thread are highly appreciated.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
>Thread-Topic: Repairing / modyfing Exchange
>thread-index: AcWcRuiwYcyjs7w5SKetQ8sa4v1jGA==
>X-WBNR-Posting-Host: 62.38.216.83
>From: "=?Utf-8?B?R2VvcmdlSw==?=" <GeorgeK@xxxxxxxxxxxxxxxxxxxxxxxxx>
>References: <E6068E70-842A-4C4E-9216-DDB46D66A00E@xxxxxxxxxxxxx>
<1sTvD0WmFHA.588@xxxxxxxxxxxxxxxxxxxxx>
<657C581F-9AB3-4BFD-89C2-D37C638664D3@xxxxxxxxxxxxx>
<5AM8Nw7mFHA.3120@xxxxxxxxxxxxxxxxxxxxx>
>Subject: RE: Repairing / modyfing Exchange
>Date: Mon, 8 Aug 2005 11:28:01 -0700
>Lines: 314
>Message-ID: <60AD82CE-21CA-4698-A14B-08A1E523E530@xxxxxxxxxxxxx>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Newsgroups: microsoft.public.windows.server.sbs
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:142449
>X-Tomcat-NG: microsoft.public.windows.server.sbs
>
>Thank you Nathan for your quick response.
>By error I overwrote the database files with the older ones. I tried to
move
>the old server's database files to an other disk and I overwrote the
database
>of my current working exchange. Unfortunetly the exchange services were
>stopped and the move was completed. I know, pretty stupid but I was awake
for
>over 52 hours.
>Since I have only about 10 users I don't care if I 'll have to recreate
>them from the begining, but I don't want to reinstall the server because
of a
>very srtange extranet running on IIS ( It took me 28 hours to set it
up!!!).
>
>Thank you in advance!
>
>""Nathan Liu [MSFT]"" wrote:
>
>> Hi Georgek,
>>
>> Thank you for your kind reply.
>>
>> According to your description, I understand that you have messed
something
>> up with the First Storage Group, so you would like to delete it and then
>> re-create it without destroying everything. If I have misunderstood your
>> concern, please don't hesitate to let me know.
>>
>> First of all, please kindly describe what changes you had been made to
the
>> First Storage Group. We don't simply delete the First Storage Group and
>> re-create it, since it contains one or more stores, and only empty
storage
>> groups can be deleted. So I suggest you create a Recovery Storage Group
and
>> manually copy database files to the Recovery Storage Group, and then
>> Extract or Merge mailbox data from the Recovery Storage Group to the
First
>> Storage Group.
>>
>> For the detailed steps, please refer to the KB article 824126:
>>
>> 824126 How to use Recovery Storage Groups in Exchange Server 2003
>> http://support.microsoft.com/?id=824126
>>
>> I am appreciated your time and cooperation. If anything is unclear,
please
>> feel free to let me know. I am looking forward to hearing from you.
>>
>> Best regards,
>>
>> Nathan Liu (MSFT)
>> Microsoft CSS Online Newsgroup Support
>>
>> Get Secure! - www.microsoft.com/security
>> ======================================================
>> This newsgroup only focuses on SBS technical issues. If you have issues
>> regarding other Microsoft products, you'd better post in the
corresponding
>> newsgroups so that they can be resolved in an efficient and timely
manner.
>> You can locate the newsgroup here:
>> http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
>>
>> When opening a new thread via the web interface, we recommend you check
the
>> "Notify me of replies" box to receive e-mail notifications when there
are
>> any updates in your thread. When responding to posts via your
newsreader,
>> please "Reply to Group" so that others may learn and benefit from your
>> issue.
>>
>> Microsoft engineers can only focus on one issue per thread. Although we
>> provide other information for your reference, we recommend you post
>> different incidents in different threads to keep the thread clean. In
doing
>> so, it will ensure your issues are resolved in a timely manner.
>>
>> For urgent issues, you may want to contact Microsoft CSS directly.
Please
>> check http://support.microsoft.com for regional support phone numbers.
>>
>> Any input or comments in this thread are highly appreciated.
>> ======================================================
>> This posting is provided "AS IS" with no warranties, and confers no
rights.
>>
>> --------------------
>> >Thread-Topic: Repairing / modyfing Exchange
>> >thread-index: AcWZtKnHpog4rdDkTuWzQesZanY4TA==
>> >X-WBNR-Posting-Host: 62.38.216.83
>> >From: "=?Utf-8?B?R2VvcmdlSw==?=" <GeorgeK@xxxxxxxxxxxxxxxxxxxxxxxxx>
>> >References: <E6068E70-842A-4C4E-9216-DDB46D66A00E@xxxxxxxxxxxxx>
>> <1sTvD0WmFHA.588@xxxxxxxxxxxxxxxxxxxxx>
>> >Subject: RE: Repairing / modyfing Exchange
>> >Date: Fri, 5 Aug 2005 04:56:07 -0700
>> >Lines: 222
>> >Message-ID: <657C581F-9AB3-4BFD-89C2-D37C638664D3@xxxxxxxxxxxxx>
>> >MIME-Version: 1.0
>> >Content-Type: text/plain;
>> > charset="Utf-8"
>> >Content-Transfer-Encoding: 7bit
>> >X-Newsreader: Microsoft CDO for Windows 2000
>> >Content-Class: urn:content-classes:message
>> >Importance: normal
>> >Priority: normal
>> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>> >Newsgroups: microsoft.public.windows.server.sbs
>> >NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>> >Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
>> >Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:141804
>> >X-Tomcat-NG: microsoft.public.windows.server.sbs
>> >
>> >Thank you Nathan Liu for your qiuck answer,
>> >I haven't tried your solution yet. I'll setup a new server today to try
it.
>> >
>> >Also, because I have messed something up with the First Storage Group,
if
>> I
>> >delete it and recreate it will I destroy everything? Is there a way to
>> create
>> >a new one without destroying everything?
>> >
>> >""Nathan Liu [MSFT]"" wrote:
>> >
>> >> Hello Georgek,
>> >>
>> >> Thank you for posting in the SBS newsgroup.
>> >>
>> >> Also, many thanks for Axel's great input.
>> >>
>> >> According to your description, I understand that you would like to
move
>> the
>> >> Exchange Database to another disk, and restore the mailbox store. If
I
>> have
>> >> misunderstood your concern, please don't hesitate to let me know.
>> >>
>> >> Question: Is there a way to move it to the D: partition which is
about
>> 40GB
>> >> without destroying everething (including outlook web access)?
>> >>
>> >> Answer: Axel is right, please refer to the KB article 821915 to move
the
>> >> Exchange Database. For detailed information, you may refer to the
below
>> >> document:
>> >>
>> >> 821915 How to move Exchange databases and logs in Exchange Server 2003
>> >> http://support.microsoft.com/?id=821915
>> >>
>> >> Moving Data Folders for Windows Small Business Server 2003
>> >> http://go.microsoft.com/fwlink/?LinkId=49931
>> >>
>> >> Additionally, if you have a good backup of the original Exchange
>> >> information store in case the original server is totally damaged, to
>> >> restore the data back or mount the edb file on a newly installed
>> Exchange
>> >> server, the following essential naming scheme elements in your
original
>> >> organization must be the same as your new one.
>> >>
>> >> * The Exchange organization name.
>> >>
>> >> * The name of the administrative group to which the database belongs.
>> >>
>> >> * The name of the storage group to which the database belongs.
>> >>
>> >> * The logical database name itself.
>> >>
>> >> * The legacyExchangeDN value for the administrative group object that
>> the
>> >> database currently belongs to.
>> >>
>> >> For more information, please refer to the following link:
>> >>
>>
http://www.microsoft.com/technet/prodtechnol/exchange/2000/support/dbrecovr.
>> >> mspx
>> >>
>> >> However, in case there is some differentiation, Legacydn.exe could
help
>> you
>> >> some.
>> >>
>> >> Legacydn.exe is a tool that you can use to perform the following
tasks:
>> >>
>> >> - Change the Microsoft Exchange 2000 Server or Microsoft Exchange
Server
>> >> 2003 organization name.
>> >>
>> >> - Change the administrative group names.
>> >>
>> >> - View the legacyExchangeDN values.
>> >>
>> >> - Change the legacyExchangeDN values.
>> >>
>> >> Note We only support the use of the Legacydn tool in a lab
environment.
>> The
>> >> tool works only in a single domain controller environment.
>> >>
>> >> For more information, please refer to:
>> >>
>> >> 324606 XADM: How to Use Legacydn.exe to Correct Exchange Organization
or
>> >> Administrative Group Names
>> >> http://support.microsoft.com/?kbid=324606
>> >>
>> >> 293324 XADM: "C104173A" Error Message Occurs After You Restore the
>> Database
>> >> http://support.microsoft.com/?id=293324
>> >>
>> >> Furthermore, in case you have a good backup and meet the above
>> >> requirements, when you recover the database in the RSG, you could
still
>> not
>> >> recover the mailbox since the Exmerge file may not find the original
>> user
>> >> referenced in the original mail store. Following error will occur:
>> >>
>> >> Error! Cannot identify the user with the msExchMailboxGuid
>> >> \3C\C8\7D\D7\99\C3\FCL\B5\E3\FEUWa\D6F. The legacyExchangeDN is
>> >> /O=DOMAIN/OU=FIRST ADMINISTRATIVE GROUP/CN=RECIPIENTS/CN=USER.
>> >>
>> >> This is because the exmerge utility cannot find referenced user in
the
>> AD.
>> >>
>> >> In normal mail store, we could create a non-mail enabled user and
>> connect
>> >> the orphan mailbox in storage via Mailbox Wizard. However, in the
RSG,
>> it
>> >> is not possible. We need to manually create new user and replace the
>> >> msExchMailboxGuid via ADSI.
>> >>
>> >> In the Exmerge log, we may find filtered msExchMailboxGuid as
>> >> \3C\C8\7D\D7\99\C3\FCL\B5\E3\FEUWa\D6F
>> >>
>> >> We may need to manually translate it to valid form via following rule
>> >>
>> >> \3C\C8\7D\D7\99\C3\FCL\B5\E3\FEUWa\D6F -> will become separated with
>> spaces
>> >> like this:
>> >>
>> >> 3C C8 7D D7 99 C3 FC L B5 E3 FE U W a D6 F -> we have to convert
letters
>> >> L,U,W,a and F back to Hex using ASCII table (attached as below)
>> >>
>> >> 3C C8 7D D7 99 C3 FC 4C B5 E3 FE 55 57 61 D6 46 -> this is our
recovered
>> >> msExchMailboxGuid
>> >>
>> >> Then, the whole steps on the SBS server will be:
>> >>
>> >> 1. Logon SBS server as built-in administrator
>> >>
>> >> 2. Restore the exchange database file (*.edb, *.stm) to the SBS server
>> >>
>> >> 3. Run Exchange utility and make sure it is in the Clean state
>> >>
>> >> 4. Create a new Recover Storage Group
>> >>
>> >> 5. Add database to Recover and select the only database you find
>> >>
>> >> 6. Delete all files created in the new Recover storage Group folder.
>> Copy
>> >> the backup edb and stm file to this folder and rename it as mentioned
in
>> >> the recovery storage group database settings.
>> >>
>> >> 7. On the Database tab of the Mailbox Store Properties dialog box,
>> verify
>> >> that the "This database can be overwritten by a restore" check box is
>> >> selected.
>> >>
>> >> 8. Mount the store.
>> >>
>> >> 9. Create new users
>> >>
>> >> 10. Modify the msExchMailboxGuid properties mentioned above via ADSI.
>> >>
>> >> 11. Run the Exmerge program and export it to a PST file
>> >>
>> >> To get additional information, you may refer to the following
document:
>> >>
>> >> Exchange 2000 Server Database Recovery
>> >>
>>
http://www.microsoft.com/technet/prodtechnol/exchange/2000/support/dbrecovr.
>> >> mspx#XSLTsection128121120120
>> >>
>> >> I am appreciated your time and cooperation. If anything is unclear,
>> please
>> >> feel free to let me know. I am looking forward to hearing from you.
>> >>
>> >> Best regards,
>> >>
>> >> Nathan Liu (MSFT)
>> >> Microsoft CSS Online Newsgroup Support
>> >>
>> >> Get Secure! - www.microsoft.com/security
>> >> ======================================================
>> >> This newsgroup only focuses on SBS technical issues. If you have
issues
>> >> regarding other Microsoft products, you'd better post in the
>> corresponding
>> >> newsgroups so that they can be resolved in an efficient and timely
>> manner.
>> >> You can locate the newsgroup here:
>> >> http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
>> >>
>> >> When opening a new thread via the web interface, we recommend you
check
>> the
>> >> "Notify me of replies" box to receive e-mail notifications when there
>> are
>> >> any updates in your thread. When responding to posts via your
>> newsreader,
>> >> please "Reply to Group" so that others may learn and benefit from
your
>> >> issue.
>> >>
>> >> Microsoft engineers can only focus on one issue per thread. Although
we
>> >> provide other information for your reference, we recommend you post
>> >> different incidents in different threads to keep the thread clean. In
>> doing
>> >> so, it will ensure your issues are resolved in a timely manner.
>> >>
>> >> For urgent issues, you may want to contact Microsoft CSS directly.
>> Please
>> >> check http://support.microsoft.com for regional support phone numbers.
>> >>
>> >> Any input or comments in this thread are highly appreciated.
>> >> ======================================================
>> >> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> >>
>> >> --------------------
>> >> >Thread-Topic: Repairing / modyfing Exchange
>> >> >thread-index: AcWZO60uqBvsilGfRqK1aRaVFfNJEg==
>> >> >X-WBNR-Posting-Host: 62.38.216.83
>> >> >From: "=?Utf-8?B?R2VvcmdlSw==?=" <GeorgeK@xxxxxxxxxxxxxxxxxxxxxxxxx>
>> >> >Subject: Repairing / modyfing Exchange
>> >> >Date: Thu, 4 Aug 2005 14:30:03 -0700
>> >> >Lines: 14
>> >> >Message-ID: <E6068E70-842A-4C4E-9216-DDB46D66A00E@xxxxxxxxxxxxx>
>> >> >MIME-Version: 1.0
>> >> >Content-Type: text/plain;
>> >> > charset="Utf-8"
>
.
- Follow-Ups:
- RE: Repairing / modyfing Exchange
- From: GeorgeK
- RE: Repairing / modyfing Exchange
- References:
- Repairing / modyfing Exchange
- From: GeorgeK
- RE: Repairing / modyfing Exchange
- From: "Nathan Liu [MSFT]"
- RE: Repairing / modyfing Exchange
- From: GeorgeK
- RE: Repairing / modyfing Exchange
- From: "Nathan Liu [MSFT]"
- RE: Repairing / modyfing Exchange
- From: GeorgeK
- Repairing / modyfing Exchange
- Prev by Date: RE: Need help setting up VPN access
- Next by Date: Re: Problem installing SBS2003 on MSI 915P motherboard with SATA R
- Previous by thread: RE: Repairing / modyfing Exchange
- Next by thread: RE: Repairing / modyfing Exchange
- Index(es):
Relevant Pages
|