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

We always had some error events on our Exchange 5.5: MSExchangeIS (465) Synchronous read page

Users viewing this topic: none

Logged in as: Guest
  Printable Version
All Forums >> [Microsoft Exchange 2003] >> Migration >> We always had some error events on our Exchange 5.5: MSExchangeIS (465) Synchronous read page Page: [1]
Login
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!
We always had some error events on our Exchange 5.5: ... - 20.Nov.2006 11:23:11 AM   
tomh_2006

 

Posts: 21
Joined: 1.Nov.2006
Status: offline 		We always had some error events on our Exchange 5.5:

=================================================

MSExchangeIS (465) Synchronous read page checksum error -1018 ((1:129823 1:4294967295) (4294967295-4294967295) (0-693591239)) occurred. Please restore the databases from a previous backup.



MSExchangeIS (465) Synchronous read page checksum error -1018 ((1:129823 1:4294967295) (4294967295-4294967295) (0-693591420)) occurred. Please restore the databases from a previous backup.



MSExchangeIS (465) A read of the database file E:\exchsrvr\MDBDATA\PRIV.EDB between offsets 0x000000001FB20000 and 0x000000001FB20FFF failed after 16 failed read attempts with error -1018. There is a software or hardware problem affecting the database drive that must be corrected to preserve database integrity. Contact Microsoft Product Support Services.
For more information, search the Microsoft Knowledge Base at http: Event ID number.



MSExchangeIS (465) Online defragmentation of database 'E:\exchsrvr\MDBDATA\PRIV.EDB' terminated prematurely after encountering unexpected error -1018.

=================================================


But it worked just fine.

Now we are planning Exchange 5.5 to 2003 migration, and after running g:\>eseutil /g /ispriv /v /x >e:\privchk.txt, discovered the following:


=================================================

0 10 20 30 40 50 60 70 80 90 100
|----|----|----|----|----|----|----|----|----|----|
checking SystemRoot
SystemRoot (OE)
SystemRoot (AE)
checking system table
MSysObjectsShadow
MSysObjects
Name
RootObjects
rebuilding and comparing indexes
checking table "1-1EBBE4" (26207)
checking data
checking index "?T668f+B67aa-Te06+Q674a" (38867)
checking index "MsgFolderIndexPtagDeletedOn" (26211)
checking index "RuleMsgFolderIndex" (26210)
checking index "MsgFolderIndex7" (26209)
rebuilding and comparing indexes
checking table "1-24" (52)
checking data
checking long value tree (65)
ERROR: orphaned LV (lid 49546, size 3476, refcount 0). Non-corrupting error
ERROR: node [127768:0]: leaf node check failed
ERROR: orphaned LV (lid 49547, size 1418240, refcount 0). Non-corrupting error
ERROR: node [127769:0]: leaf node check failed
ERROR: page 129823: error -1018 on read
ERROR: node [124172:1]: subtree check (page 163082) failed with err -1018
ERROR: error -1018 at line 3186 of G:\ese97\src\ese\repair.cxx
ERROR: node [2564106:0]: subtree check (page 124172) failed with err -1018
ERROR: error -1018 at line 3186 of G:\ese97\src\ese\repair.cxx
ERROR: node [161:0]: subtree check (page 2564106) failed with err -1018
ERROR: error -1018 at line 3186 of G:\ese97\src\ese\repair.cxx
ERROR: error -1018 at line 2968 of G:\ese97\src\ese\repair.cxx
ERROR: error -1018 at line 2702 of G:\ese97\src\ese\repair.cxx
ERROR: error -1018 at line 1664 of G:\ese97\src\ese\repair.cxx
Long-Value table will be rebuilt
Indexes will be rebuilt
Long-Value refcounts will be rebuilt

...............


checking table "Folders" (6)
checking data
checking long value tree (71)
ERROR: orphaned LV (lid 2031, size 80, refcount 0). Non-corrupting error
ERROR: node [582816:4]: leaf node check failed
ERROR: orphaned LV (lid 2032, size 88, refcount 0). Non-corrupting error
ERROR: node [582816:6]: leaf node check failed
ERROR: orphaned LV (lid 2033, size 92, refcount 0). Non-corrupting error
ERROR: node [582816:8]: leaf node check failed
ERROR: orphaned LV (lid 2034, size 40, refcount 0). Non-corrupting error
ERROR: node [582816:10]: leaf node check failed
ERROR: orphaned LV (lid 2035, size 64, refcount 0). Non-corrupting error
ERROR: node [582816:12]: leaf node check failed
ERROR: orphaned LV (lid 2036, size 64, refcount 0). Non-corrupting error
ERROR: node [582816:14]: leaf node check failed
ERROR: orphaned LV (lid 2037, size 64, refcount 0). Non-corrupting error
ERROR: node [582816:16]: leaf node check failed
ERROR: orphaned LV (lid 2038, size 36, refcount 0). Non-corrupting error
ERROR: node [582816:18]: leaf node check failed
ERROR: orphaned LV (lid 2039, size 76, refcount 0). Non-corrupting error
ERROR: node [582816:20]: leaf node check failed
ERROR: orphaned LV (lid 2040, size 36, refcount 0). Non-corrupting error
ERROR: node [582816:22]: leaf node check failed
ERROR: orphaned LV (lid 2041, size 76, refcount 0). Non-corrupting error
ERROR: node [582816:24]: leaf node check failed
ERROR: orphaned LV (lid 2042, size 76, refcount 0). Non-corrupting error
ERROR: node [582816:26]: leaf node check failed
ERROR: orphaned LV (lid 2043, size 76, refcount 0). Non-corrupting error
ERROR: node [582816:28]: leaf node check failed
ERROR: orphaned LV (lid 2044, size 36, refcount 0). Non-corrupting error
ERROR: node [582816:30]: leaf node check failed
ERROR: orphaned LV (lid 2045, size 76, refcount 0). Non-corrupting error
ERROR: node [582816:32]: leaf node check failed
ERROR: orphaned LV (lid 2046, size 36, refcount 0). Non-corrupting error
ERROR: node [582816:34]: leaf node check failed
ERROR: orphaned LV (lid 2047, size 36, refcount 0). Non-corrupting error
ERROR: node [582816:36]: leaf node check failed
ERROR: orphaned LV (lid 2048, size 36, refcount 0). Non-corrupting error
ERROR: node [582816:38]: leaf node check failed
checking index "*T668f+Q6749+S3001+Q6748 409" (31800)
checking index "?T668f+Q6749+S3001+Q6748 409" (31799)
checking index "FoldersIndex13" (12)
checking index "FoldersIndex10" (11)
checking index "FoldersIndex8" (10)
checking index "FoldersIndex7" (9)
checking index "FoldersIndex6" (8)
checking index "FoldersIndex5" (7)
rebuilding and comparing indexes
checking table "Global" (45)
checking data
rebuilding and comparing indexes
checking table "IndexAge" (32)
checking data
rebuilding and comparing indexes
checking table "Mailbox" (18)
checking data
checking index "MailboxIndex3" (35987)
checking index "MailboxIndex2" (19)
rebuilding and comparing indexes
checking table "Message Tombstone" (31)
checking data
rebuilding and comparing indexes
checking table "Msg" (14)
checking data
.. checking long value tree (103)
ERROR: orphaned LV (lid 43248, size 1716, refcount 0). Non-corrupting error
ERROR: node [25556:0]: leaf node check failed
ERROR: orphaned LV (lid 43576, size 4128, refcount 0). Non-corrupting error
ERROR: node [33638:0]: leaf node check failed
ERROR: orphaned LV (lid 43581, size 1715, refcount 0). Non-corrupting error
ERROR: node [20677:1]: leaf node check failed
ERROR: orphaned LV (lid 43591, size 1717, refcount 0). Non-corrupting error
ERROR: node [19933:0]: leaf node check failed
ERROR: orphaned LV (lid 43614, size 1721, refcount 0). Non-corrupting error
ERROR: node [22258:0]: leaf node check failed
ERROR: orphaned LV (lid 43629, size 10029, refcount 0). Non-corrupting error
ERROR: node [19904:0]: leaf node check failed
ERROR: orphaned LV (lid 43660, size 1576, refcount 0). Non-corrupting error
ERROR: node [21358:0]: leaf node check failed
ERROR: orphaned LV (lid 43665, size 1723, refcount 0). Non-corrupting error
ERROR: node [22751:0]: leaf node check failed
ERROR: orphaned LV (lid 43776, size 1714, refcount 0). Non-corrupting error
ERROR: node [19810:0]: leaf node check failed
ERROR: orphaned LV (lid 43786, size 1722, refcount 0). Non-corrupting error
ERROR: node [20676:0]: leaf node check failed
ERROR: orphaned LV (lid 43796, size 1724, refcount 0). Non-corrupting error
ERROR: node [20779:0]: leaf node check failed
ERROR: orphaned LV (lid 43808, size 1724, refcount 0). Non-corrupting error
ERROR: node [21110:0]: leaf node check failed
ERROR: orphaned LV (lid 43855, size 1723, refcount 0). Non-corrupting error
ERROR: node [20335:0]: leaf node check failed
ERROR: orphaned LV (lid 43860, size 1729, refcount 0). Non-corrupting error
ERROR: node [19936:0]: leaf node check failed
ERROR: orphaned LV (lid 43962, size 1728, refcount 0). Non-corrupting error
ERROR: node [17024:0]: leaf node check failed
ERROR: orphaned LV (lid 44202, size 10636, refcount 0). Non-corrupting error
ERROR: node [19809:0]: leaf node check failed
ERROR: orphaned LV (lid 87718, size 7448, refcount 0). Non-corrupting error
ERROR: node [223784:0]: leaf node check failed
ERROR: orphaned LV (lid 87771, size 1645, refcount 0). Non-corrupting error
ERROR: node [225526:0]: leaf node check failed
ERROR: orphaned LV (lid 87809, size 3013, refcount 0). Non-corrupting error
ERROR: node [226960:0]: leaf node check failed
ERROR: orphaned LV (lid 87811, size 1225, refcount 0). Non-corrupting error
ERROR: node [227937:0]: leaf node check failed
ERROR: orphaned LV (lid 87812, size 3400, refcount 0). Non-corrupting error
ERROR: node [227937:2]: leaf node check failed
ERROR: orphaned LV (lid 87957, size 1091, refcount 0). Non-corrupting error
ERROR: node [235586:0]: leaf node check failed
ERROR: orphaned LV (lid 87958, size 1445, refcount 0). Non-corrupting error
ERROR: node [235586:2]: leaf node check failed
ERROR: orphaned LV (lid 88417, size 34670, refcount 0). Non-corrupting error
ERROR: node [259990:0]: leaf node check failed
ERROR: orphaned LV (lid 88418, size 12361, refcount 0). Non-corrupting error
ERROR: node [259998:1]: leaf node check failed
ERROR: orphaned LV (lid 88419, size 1497, refcount 0). Non-corrupting error
ERROR: node [260002:1]: leaf node check failed
ERROR: orphaned LV (lid 88939, size 4979, refcount 0). Non-corrupting error
ERROR: node [286144:0]: leaf node check failed
ERROR: orphaned LV (lid 89220, size 1123, refcount 0). Non-corrupting error
ERROR: node [302151:0]: leaf node check failed
ERROR: orphaned LV (lid 165713, size 1289, refcount 0). Non-corrupting error
ERROR: node [483290:0]: leaf node check failed
ERROR: orphaned LV (lid 166163, size 1959, refcount 0). Non-corrupting error
ERROR: node [435984:0]: leaf node check failed
ERROR: orphaned LV (lid 167040, size 2281, refcount 0). Non-corrupting error
ERROR: node [450903:0]: leaf node check failed
ERROR: orphaned LV (lid 167041, size 3638, refcount 0). Non-corrupting error
ERROR: node [450903:2]: leaf node check failed
ERROR: orphaned LV (lid 174033, size 1228, refcount 0). Non-corrupting error
ERROR: node [495915:0]: leaf node check failed
ERROR: orphaned LV (lid 175784, size 17049, refcount 0). Non-corrupting error
ERROR: node [500878:0]: leaf node check failed
ERROR: orphaned LV (lid 175785, size 1672, refcount 0). Non-corrupting error
ERROR: node [495862:1]: leaf node check failed
ERROR: orphaned LV (lid 176642, size 1206, refcount 0). Non-corrupting error
ERROR: node [492320:0]: leaf node check failed
ERROR: orphaned LV (lid 176645, size 2288, refcount 0). Non-corrupting error
ERROR: node [492320:2]: leaf node check failed
ERROR: orphaned LV (lid 176847, size 2288, refcount 0). Non-corrupting error
ERROR: node [440450:0]: leaf node check failed
ERROR: orphaned LV (lid 176954, size 1520, refcount 0). Non-corrupting error
ERROR: node [436349:0]: leaf node check failed
ERROR: orphaned LV (lid 177825, size 13718, refcount 0). Non-corrupting error
ERROR: node [177846:0]: leaf node check failed
ERROR: orphaned LV (lid 177826, size 3105, refcount 0). Non-corrupting error
ERROR: node [147378:1]: leaf node check failed
ERROR: orphaned LV (lid 184949, size 1093, refcount 0). Non-corrupting error
ERROR: node [490824:0]: leaf node check failed
ERROR: orphaned LV (lid 190590, size 1401, refcount 0). Non-corrupting error
ERROR: node [455037:0]: leaf node check failed
ERROR: orphaned LV (lid 190591, size 1737, refcount 0). Non-corrupting error
ERROR: node [455037:2]: leaf node check failed
ERROR: orphaned LV (lid 190592, size 2223, refcount 0). Non-corrupting error
ERROR: node [455038:0]: leaf node check failed
ERROR: orphaned LV (lid 193708, size 2315, refcount 0). Non-corrupting error
ERROR: node [507693:0]: leaf node check failed
ERROR: orphaned LV (lid 193709, size 1288, refcount 0). Non-corrupting error
ERROR: node [507693:2]: leaf node check failed
ERROR: orphaned LV (lid 193711, size 1882, refcount 0). Non-corrupting error
ERROR: node [507691:0]: leaf node check failed
ERROR: orphaned LV (lid 193712, size 1278, refcount 0). Non-corrupting error
ERROR: node [507691:2]: leaf node check failed
ERROR: orphaned LV (lid 193713, size 1512, refcount 0). Non-corrupting error
ERROR: node [498936:1]: leaf node check failed
ERROR: orphaned LV (lid 193714, size 1278, refcount 0). Non-corrupting error
ERROR: node [498936:3]: leaf node check failed
ERROR: orphaned LV (lid 193715, size 1507, refcount 0). Non-corrupting error
ERROR: node [498674:1]: leaf node check failed
ERROR: orphaned LV (lid 193716, size 1278, refcount 0). Non-corrupting error
ERROR: node [498674:3]: leaf node check failed
ERROR: orphaned LV (lid 193717, size 1500, refcount 0). Non-corrupting error
ERROR: node [496383:1]: leaf node check failed
ERROR: orphaned LV (lid 193718, size 1278, refcount 0). Non-corrupting error
ERROR: node [496383:3]: leaf node check failed
ERROR: orphaned LV (lid 194054, size 5677, refcount 0). Non-corrupting error
ERROR: node [490946:0]: leaf node check failed
ERROR: orphaned LV (lid 195383, size 1079, refcount 0). Non-corrupting error
ERROR: node [455125:0]: leaf node check failed
ERROR: orphaned LV (lid 195384, size 1360, refcount 0). Non-corrupting error
ERROR: node [455125:2]: leaf node check failed
ERROR: orphaned LV (lid 195385, size 1073, refcount 0). Non-corrupting error
ERROR: node [455125:4]: leaf node check failed
ERROR: orphaned LV (lid 195681, size 3686, refcount 0). Non-corrupting error
ERROR: node [107729:0]: leaf node check failed
ERROR: orphaned LV (lid 195682, size 1242, refcount 0). Non-corrupting error
ERROR: node [107729:2]: leaf node check failed
ERROR: orphaned LV (lid 197674, size 11865, refcount 0). Non-corrupting error
ERROR: node [488643:0]: leaf node check failed
ERROR: orphaned LV (lid 197675, size 1559, refcount 0). Non-corrupting error
ERROR: node [483376:1]: leaf node check failed
ERROR: orphaned LV (lid 199787, size 12697, refcount 0). Non-corrupting error
ERROR: node [507683:0]: leaf node check failed
ERROR: orphaned LV (lid 199788, size 2652, refcount 0). Non-corrupting error
ERROR: node [498933:1]: leaf node check failed
ERROR: orphaned LV (lid 199789, size 1201, refcount 0). Non-corrupting error
ERROR: node [498933:3]: leaf node check failed
ERROR: orphaned LV (lid 199812, size 12697, refcount 0). Non-corrupting error
ERROR: node [497606:0]: leaf node check failed
ERROR: orphaned LV (lid 199813, size 2652, refcount 0). Non-corrupting error
ERROR: node [500873:1]: leaf node check failed
ERROR: orphaned LV (lid 199814, size 1201, refcount 0). Non-corrupting error
ERROR: node [500873:3]: leaf node check failed
ERROR: orphaned LV (lid 199849, size 12697, refcount 0). Non-corrupting error
ERROR: node [495414:0]: leaf node check failed
ERROR: orphaned LV (lid 199850, size 2652, refcount 0). Non-corrupting error
ERROR: node [495287:1]: leaf node check failed
ERROR: orphaned LV (lid 199851, size 1201, refcount 0). Non-corrupting error
ERROR: node [495287:3]: leaf node check failed
ERROR: orphaned LV (lid 205407, size 4230, refcount 0). Non-corrupting error
ERROR: node [452887:0]: leaf node check failed
ERROR: orphaned LV (lid 205408, size 1285, refcount 0). Non-corrupting error
ERROR: node [452888:1]: leaf node check failed
ERROR: orphaned LV (lid 206174, size 10569, refcount 0). Non-corrupting error
ERROR: node [483331:0]: leaf node check failed
ERROR: orphaned LV (lid 206184, size 2690, refcount 0). Non-corrupting error
ERROR: node [470051:0]: leaf node check failed
ERROR: orphaned LV (lid 206185, size 1667, refcount 0). Non-corrupting error
ERROR: node [470051:2]: leaf node check failed
ERROR: orphaned LV (lid 206186, size 1106, refcount 0). Non-corrupting error
ERROR: node [470049:1]: leaf node check failed
ERROR: orphaned LV (lid 207376, size 1057, refcount 0). Non-corrupting error
ERROR: node [431092:0]: leaf node check failed
ERROR: orphaned LV (lid 207512, size 1159, refcount 0). Non-corrupting error
ERROR: node [439450:0]: leaf node check failed
ERROR: orphaned LV (lid 207693, size 2686, refcount 0). Non-corrupting error
ERROR: node [237805:0]: leaf node check failed
ERROR: orphaned LV (lid 207698, size 3710, refcount 0). Non-corrupting error
ERROR: node [430972:0]: leaf node check failed
ERROR: orphaned LV (lid 207704, size 3419, refcount 0). Non-corrupting error
ERROR: node [442446:0]: leaf node check failed
ERROR: orphaned LV (lid 207706, size 4663, refcount 0). Non-corrupting error
ERROR: node [439899:0]: leaf node check failed
ERROR: orphaned LV (lid 207707, size 1062, refcount 0). Non-corrupting error
ERROR: node [437629:1]: leaf node check failed
ERROR: orphaned LV (lid 207708, size 1565, refcount 0). Non-corrupting error
ERROR: node [437629:3]: leaf node check failed
ERROR: orphaned LV (lid 207709, size 1024, refcount 0). Non-corrupting error
ERROR: node [437629:5]: leaf node check failed
ERROR: orphaned LV (lid 207710, size 1024, refcount 0). Non-corrupting error
ERROR: node [437630:1]: leaf node check failed
... rebuilding and comparing indexes



.............................................

ERROR: error -1206 at line 951 of G:\ese97\src\ese\repair.cxx
Operation terminated with error -1206 (JET_errDatabaseCorrupted, non-db file or corrupted db) after 1270.906 seconds.

=================================================


Is it safe to perform migration with PRIV.EDB in this condition? I would use Eseutil /P, but not sure what it will destroy.
If it’s not safe to migrate, may Eseutil /D correct the problems?
(PRIV.EDB is 14.5 GB, and "The database has 2688 megabytes of free space after online defragmentation has terminated.")

Thank you.
Post #: 1
RE: We always had some error events on our Exchange 5.5... - 20.Nov.2006 1:30:45 PM   
jchong

 

Posts: 2516
Joined: 1.Dec.2005
From: Centreville, Virginia
Status: offline 		Well, I think if you were to ask MS if it would be safe to move forward, they would prob tell you to fix first before proceding or you can compound the issue. You can perform the /p just make a backup of your databases and keep them on another server so you have a backup.

_____________________________

James Chong
MCSE | M+, S+, MCTS, Security+
msexchangetips.blogspot.com

(in reply to tomh_2006)
Post #: 2
RE: We always had some error events on our Exchange 5.5 - 20.Nov.2006 1:53:44 PM   
tomh_2006

 

Posts: 21
Joined: 1.Nov.2006
Status: offline 		Jchong,

Thanks for reply!

One of the published solutions to the problem is to move everything to another box, recreate PRIV.EDB on the old server, and then move everything back.
And I thought since we are moving to another (Exchange 2003) box anyway ... (???)

(in reply to jchong)
Post #: 3
RE: We always had some error events on our Exchange 5.5 - 20.Nov.2006 2:36:40 PM   
jchong

 

Posts: 2516
Joined: 1.Dec.2005
From: Centreville, Virginia
Status: offline 		Yup, that's much better, because a repair is what is says it's a "repair" it's still broken, you still have holes and missing pages, links etc, a repair /p doesn't fix it but just makes it so it'll work and mount. So yes a new DB is always best.



_____________________________

James Chong
MCSE | M+, S+, MCTS, Security+
msexchangetips.blogspot.com

(in reply to tomh_2006)
Post #: 4
RE: We always had some error events on our Exchange 5.5 - 20.Nov.2006 3:12:17 PM   
tomh_2006

 

Posts: 21
Joined: 1.Nov.2006
Status: offline 		So, it's ok to start migration (which will move everything to a new box anyway) to 2003 with current state of 5.5?

(in reply to jchong)
Post #: 5
RE: We always had some error events on our Exchange 5.5 - 20.Nov.2006 4:27:04 PM   
jchong

 

Posts: 2516
Joined: 1.Dec.2005
From: Centreville, Virginia
Status: offline 		Yeah, as long as things are working. I would at least try to get the mailboxes moved as soon as possible. Since you're working with a possibly corrupted db, you don't want your mailbox move stopped say when you're half way done because your db won't mount. Also keep in mind that it might not be a db corruption but hardware related with your controller. I would test moving a mailbox or 2 before doing a bunch in the first run.



_____________________________

James Chong
MCSE | M+, S+, MCTS, Security+
msexchangetips.blogspot.com

(in reply to tomh_2006)
Post #: 6
RE: We always had some error events on our Exchange 5.5 - 20.Nov.2006 6:03:17 PM   
tomh_2006

 

Posts: 21
Joined: 1.Nov.2006
Status: offline 		Great! I just want to start something on 2003 box already.
Will run:

1. ForestPrep.
2. DomainPrep.
3. Active Directory Connector Setup.
4. Active Directory Connector tools.
5. Exchange Setup.

Hopefully none of these five will trash the existing 5.5.
I guess after that will start moving mailboxes and PST corrupted users.

Thanks a lot for your help!

(in reply to jchong)
Post #: 7
RE: We always had some error events on our Exchange 5.5... - 20.Nov.2006 6:30:42 PM   
jchong

 

Posts: 2516
Joined: 1.Dec.2005
From: Centreville, Virginia
Status: offline 		Good luck! Post again if you run into any issues.

_____________________________

James Chong
MCSE | M+, S+, MCTS, Security+
msexchangetips.blogspot.com

(in reply to tomh_2006)
Post #: 8
RE: We always had some error events - 25.Nov.2006 12:31:04 PM   
tomh_2006

 

Posts: 21
Joined: 1.Nov.2006
Status: offline 		OK. Tried Eseutil /D.
TempDfrg.edb got to 748 MB (PRIV.EDB is 14,456 MB), and returned:

Operation terminate with error -1018 (JET_errReadingVerifyFailure, Read verification error) after 1179.313 seconds.

Starting migration without fixing PRIV.EDB.

Thank you.

(in reply to jchong)
Post #: 9
RE: We always had some error events - 25.Nov.2006 12:40:15 PM   
jchong

 

Posts: 2516
Joined: 1.Dec.2005
From: Centreville, Virginia
Status: offline 		Ouch sounds like it's corrupt. Yeah go ahead and try to get those mailboxes moved as soon as possible so you don't run into any further issues.

_____________________________

James Chong
MCSE | M+, S+, MCTS, Security+
msexchangetips.blogspot.com

(in reply to tomh_2006)
Post #: 10
RE: We always had some error events - 27.Nov.2006 11:23:54 AM   
tomh_2006

 

Posts: 21
Joined: 1.Nov.2006
Status: offline 		I've done everything up to the actual "Install Exchange Server 2003" part. Finished everything Sunday morning, and now checking logs to make sure that everything is ok.
Tonight will install Exchange.

Thank you.

(in reply to jchong)
Post #: 11
RE: We always had some error events - 27.Nov.2006 11:25:33 AM   
jchong

 

Posts: 2516
Joined: 1.Dec.2005
From: Centreville, Virginia
Status: offline

_____________________________

James Chong
MCSE | M+, S+, MCTS, Security+
msexchangetips.blogspot.com

(in reply to tomh_2006)
Post #: 12
RE: We always had some error events - 27.Nov.2006 11:37:55 PM   
tomh_2006

 

Posts: 21
Joined: 1.Nov.2006
Status: offline 		Installed Exchange 2003.
Flashed with SP1 and SP2.

Did:

"After setup, change your connection agreements to connect to the new server running Exchange 2003. The new server runs Site Replication Service (SRS); connecting to this server prevents problems with directory replication and Global Address List viewing."

Didn't do - Not sure if I need to (?):

"You should also assign the Exchange View Only Administrator role to all of the ADC service accounts by using Exchange Administration and Delegation Wizard in Exchange System Manager. (To start the wizard, right-click the organization or administrative group for which you want to delegate administrative permissions, and then click Delegate control)."

Used validation tools, and checked the logs - everything's ok. Amazingly enough, domain is still there
Some strange things happened though:

Our old users and email accounts didn't match exactly on Exchange 5.5 - NT logons were generic (Example: OfficeManager), and email accounts were actual names (e.g. JohnSmith@blah.com). After all this manipulations User Manager for Domains on the Exchange 5.5 (which is still a Domain Controller) shows all the old accounts as usual. But AD Users and Computers lists 'merged' versions - actual name (John Smith) is listed in the Name column, and NT user name is visible under Account tab in User logon name (pre-Windows 2000) field. Some of them are also in User logon name field, with our domain in the (unnamed) dropdown. AD Users and Computers also shows some users without usual Exchange tabs.
Additionally, a new Recipients folder was created under the standard Users folder. I found 3 Disabled Windows accounts, custom users (Exchange 5.5 forwards these to external mail accounts) and all Distribution Groups in the Recipients folder.

But so far I see no ill effects.

According to ExDeploy, it's time to move mailboxes and Public Folders. But I would like to move them gradually, and I should probably configure 2003 to send/receive first (?) Our 5.5 extracts mail from ISP's mail server (many-to-many) via eXchangePOP3. Do you think at this point I should install eXchangePOP3 on 2003, and test some mail traffic?

Thanks for sticking around!

(in reply to jchong)
Post #: 13
RE: We always had some error events - 28.Nov.2006 2:38:48 PM   
tomh_2006

 

Posts: 21
Joined: 1.Nov.2006
Status: offline 		I moved one test mailbox, and it just works: Can send mail, see Public Folders (probably pulled from the old box), and even send and receive to/from the Internet.

Looks like the old and new servers are totally in sync. Is it the way it should be? Is it time to install eXchangePOP3 on the new Exchange 2003?

Thank you.

(in reply to tomh_2006)
Post #: 14
RE: We always had some error events - 28.Nov.2006 2:58:15 PM   
jchong

 

Posts: 2516
Joined: 1.Dec.2005
From: Centreville, Virginia
Status: offline 		Sounds good. Yeah I don't see why you shouldn't move forward so far. Just make sure you start making backups once you start moving users over.

_____________________________

James Chong
MCSE | M+, S+, MCTS, Security+
msexchangetips.blogspot.com

(in reply to tomh_2006)
Post #: 15
RE: We always had some error events - 29.Nov.2006 3:31:54 AM   
tomh_2006

 

Posts: 21
Joined: 1.Nov.2006
Status: offline 		Not sure how to deal with Public Folders. Should I do:

pfMigrate.wsf /S:EMAIL /T:SNOOPY /A /N:100 /F:C: \logfile.txt

and:

pfMigrate.wsf /S:EMAIL /D:SNOOPY /D

right after they replicate. Or should I wait until all mailboxes are on the Ex2003 box before deleting PFs from 5.5?

Sorry for asking so many questions, but timing is very confusing.

Thank you.

(in reply to jchong)
Post #: 16
RE: We always had some error events - 29.Nov.2006 9:53:05 AM   
jchong

 

Posts: 2516
Joined: 1.Dec.2005
From: Centreville, Virginia
Status: offline 		I've never used the pfmigrate script, I used pfdavadmin which might be easier since it's a gui based tool. You can select the folders that you want to replicate to your new 2k3 ex server. I would do a few at a time, for example if your pf db is 10gb, start off by doing 2gb of folders to be replicated at a time. I've seen weird issues if you try to replicate too much data at once causing the mb store to stop responding during the middle of the day. You begin replication during your mailbox move process.

_____________________________

James Chong
MCSE | M+, S+, MCTS, Security+
msexchangetips.blogspot.com

(in reply to tomh_2006)
Post #: 17
RE: We always had some error events - 29.Nov.2006 12:37:37 PM   
tomh_2006

 

Posts: 21
Joined: 1.Nov.2006
Status: offline 		We only have around 300mb of data in PFs.
I was concerned about information availability to users – will the PFs remain available to the old server users if I use:

pfMigrate.wsf /S:EMAIL /T:SNOOPY /A /N:100 /F:C: \logfile.txt

and then:

pfMigrate.wsf /S:EMAIL /D:SNOOPY /D

I generally still have no idea what data is where (which server), and who can access it.

Thank you.

(in reply to jchong)
Post #: 18

Page:   [1] << Older Topic    Newer Topic >>
All Forums >> [Microsoft Exchange 2003] >> Migration >> We always had some error events on our Exchange 5.5: MSExchangeIS (465) Synchronous read page 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