Hi mate, I definitely owe you a beer for this one. I've had a rather
frustrating few days over this and with the help of (primarily) this email
I've finally got it all working.
FYI my setup was:
DOMAIN1
- NT 4.0sp6a Domain Controller, Exchange 5.5sp3, Backup Exec 8.6 build 3878
- Win2k member server, Backup Exec 8.6 build 3878 - could see and backup
Directory & Information Stores but not mailboxes
DOMAIN2
- Win2k Active Directory server, Backup Exec 8.6 build 3878, HP Ultrium 1/9
- could see and backup Directory & Information Stores but not mailboxes
2-Way Trust Relationship working fine for filesharing and Exchange (though I
had to set the DOMAIN2\User account as the mailbox owner)
There are a few Veritas support articles I used (go to
http://support.veritas.com>http://support.veritas.com and search for the
number):
190937 Exchange 5.5 setup
242606 Exchange 5.5 troubleshooting
240934 Exchange 5.5 in another domain
236744 Configuring the service account
These got me nowhere fast until I tried the instructions from this email,
and later found these articles:
251041 Persistent unique mailbox name error messages
* Although the Exchange server was sp3, the Exchange Administrator installed
on the backup server wasn't patched (doh!), that's basically what this
article is about. Oh, and I got the cdo.dll from the \winnt\system32
directory, not the location as per the email
238618 Enabling support for 'Restrict Anonymous'
Even then it didn't work until I logged on to the Backup Exec server as the
(DOMAIN2) service account. I could setup/modify the backup jobs (including
the mailboxes!) fine here, then log back in as Administrator and was able to
run the jobs and restore messages no problem, though I couldn't get back
into the mailboxes to create a new backup selection (but who cares as long
as I know the workaround). On the Win2k server in DOMAIN1 I didn't have to
log on as the service account so I presume at some level the Trust
Relationship isn't really doing what it says on the box or am I missing
something? If anyone reading this knows a solution to having to logon as
the service account I'd appreciate some info.
I've included all this in the hope that it will help someone else with
similar problems. We're halfway through a 12-month WinNT->Win2000 and
Exchange 5.5->2000 migration and having the old NT domain and the new 2000
Active Directory tree running smoothly side by side was essential to the
rollout plan.
Thanks again,
Daren
-----Original Message-----
From: Justin Edhouse
Sent: 02 May 2003 12:20
To: 'Daren Freckleton'
Subject: RE: Reason(s) I called...
Delete, then recreate the mailbox for the BE service account. Once you do,
recreate the Outlook profile on BE server and test send/receive email to
that mbox.
-Put BE Job Engine service in debug to see if a mapi session is even being
made. Double-click the Job Engine service in Services. Click the Stop button
to stop the service (it may ask to bring down BE Agent Browser service, that
is ok). Once stopped, type -debug in Start Parameters. Now click Start
button to start the BE Job Engine service and don't forget to start the BE
Agent Browser service. Now run a test backup of 1 mailbox or if you can't
even select mailboxes w/o the repeated prompt, just try selecting mailboxes
several times. Now reverse what you did to put the Job Engine service in
debug and find the debug00.txt file in \Program Files\Veritas\Backup
Exec\NT\Data folder.
If there is no mention anywhere in the file about "mapi" then the problem
may lie in the mapi subsytem on the BE server.
-w/o mapi mentioned in the above debug, I would close BE, stop all BE
services. Uninstall Outlook completely and reboot. Next, with the Backup
Exec services stopped, copy the cdo.dll file from \Program
Files\Exchsrvr\Bin folder on the Exchange server to same directory on the BE
server. Now go to Start|Run and type the following command with the quotes:
regsvr32 "c:\program files\exchsrvr\bin\cdo.dll"
you may need to replace the path w/the path to your cdo.dll file.
-Now start BE services and try attaching to mailboxes and backup 1 mbox as
a test.
Finally, try the following:
-On the Backup Exec server running:
1. Close Backup Exec(BE) and stop all BE services.
2. Open registry, HKLM/Software/Veritas/Backup Exec/Engine/NTFS, doubleclick
Restrict Anonymous Support and change the value from 0-->1.
3. Create a new DWORD in the NTFS key called useAdSSCheck with value of 0.
4. Close registry editor and start BE services.
-On the Exchange server running:
1. Stop and start the Backup Exec Agents etc
------- End of forwarded message -------
---
* Origin: [adminz] tech, security, support (192.168.0.2)
generated by msg2page 0.06 on Jul 21, 2006 at 19:04:28
search: