During an Exchange 2007 restore I was attempting to do a merge from the RSG into my target mailbox and ran into an error. The error occurs in the Application Event Log after the Exchange Wizard reports that the operation was successful. The error text is the following:
Source: Exchange Migration
Event ID: 1008
Category: Restore Mailbox
Description:
The restore-mailbox task for mailbox 'XXXX' failed.
Error: Failed to copy messages to the destination mailbox store with error:
The operation was cancelled.
As odd as this sounds the fix is to skip the wizard and run the same commands in the EMS (Exchange Management Shell) directly. Here is the syntax:
Restore-Mailbox -identity "Target Mailbox" -RSGDatabase "Recovery Storage Group\RSG Datastore" -RSGMailbox "Mailbox to be restored" -TargetFolder "Folder in -Identity to place data in" -BadItemLimit "Int32"
Friday, May 29, 2009
Wednesday, May 27, 2009
Serv-U FTP Server 8.0 Windows Authentication Changes
It appears that there is a change in the new version of Serv-U FTP Server that affects Windows Authentication. This change is that the Windows AD user must be a member of the "Domain Users" AD Group or Serv-U FTP Server will give you an Access Denied error upon connection. In the past you just needed an AD User account and could assign it to a "No Permissions" group so that it could only be used for FTP, however that is no longer the case.
Wednesday, May 20, 2009
Thursday, May 14, 2009
The Internet is broken...
It looks like there was a rather serious issue with the Internet earlier this morning. The most obvious symptom was that all the Google Apps as well as www.google.com were unavailable from 8:53am MST to 11:15am. At this point it appears that it might have been an issue with the pipe going to Google. Here is a tracert of what we were seeing:
C:\Users\xxxx>tracert www.google.com
Tracing route to www.l.google.com [74.125.93.104]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms xxxxxx.xxxxx.xxxx[xx.xx.0.1]
2 <1 ms <1 ms <1 ms xx.xx.0.1
3 <1 ms <1 ms <1 ms xx.xx.0.9
4 4 ms 4 ms 4 ms xxx.xxx-1-0.xxxx-cust1.dnvr.uswest.net [xx.224.x
x.17]
5 4 ms 4 ms 4 ms cls-core-02.inet.qwest.net [205.171.152.94]
6 30 ms 32 ms 31 ms dap-brdr-03.inet.qwest.net [67.14.2.85]
7 30 ms 30 ms 30 ms 192.205.36.45
8 49 ms 48 ms 49 ms cr2.dlstx.ip.att.net [12.122.87.54]
9 48 ms 48 ms 49 ms cr1.attga.ip.att.net [12.122.28.173]
10 48 ms 48 ms 48 ms 12.123.22.5
11 * * * Request timed out.
12 * * 293 ms 72.14.233.54
13 * * * Request timed out.
14 287 ms * * 209.85.254.239
15 * * * Request timed out.
16 * * * Request timed out.
17 287 ms * 288 ms qw-in-f104.google.com [74.125.93.104]
Trace complete.
Everything looks good at this point, but it really makes you appreciate having Google.
Also, here are some tools to help out when taking a look at outages like this:
1. http://www.internettrafficreport.com/
2. http://isc.sans.org/
3. http://www.internetpulse.net/
C:\Users\xxxx>tracert www.google.com
Tracing route to www.l.google.com [74.125.93.104]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms xxxxxx.xxxxx.xxxx[xx.xx.0.1]
2 <1 ms <1 ms <1 ms xx.xx.0.1
3 <1 ms <1 ms <1 ms xx.xx.0.9
4 4 ms 4 ms 4 ms xxx.xxx-1-0.xxxx-cust1.dnvr.uswest.net [xx.224.x
x.17]
5 4 ms 4 ms 4 ms cls-core-02.inet.qwest.net [205.171.152.94]
6 30 ms 32 ms 31 ms dap-brdr-03.inet.qwest.net [67.14.2.85]
7 30 ms 30 ms 30 ms 192.205.36.45
8 49 ms 48 ms 49 ms cr2.dlstx.ip.att.net [12.122.87.54]
9 48 ms 48 ms 49 ms cr1.attga.ip.att.net [12.122.28.173]
10 48 ms 48 ms 48 ms 12.123.22.5
11 * * * Request timed out.
12 * * 293 ms 72.14.233.54
13 * * * Request timed out.
14 287 ms * * 209.85.254.239
15 * * * Request timed out.
16 * * * Request timed out.
17 287 ms * 288 ms qw-in-f104.google.com [74.125.93.104]
Trace complete.
Everything looks good at this point, but it really makes you appreciate having Google.
Also, here are some tools to help out when taking a look at outages like this:
1. http://www.internettrafficreport.com/
2. http://isc.sans.org/
3. http://www.internetpulse.net/
Subscribe to:
Posts (Atom)