MS Transporter Suite for Notes
I am currently battling two major issues in testing the Transporter Suite in a virtual testing environment...
My setup is as follows:
-
(1)Server 2003 SP1 Domain Controller
-
Windows 2000 Native Domain
-
FSMO roles master (all roles)
-
GC
-
-
(1)Server 2003 R2 x64 Standard Ed Exchange Server
-
Transporter Suite installed here
-
-
(1)Server 2003 Domino Server
-
Transporter Calendar connector installed here
-
Issue number one is this: When I go to synchronize directories between AD and Domino, only a fraction of our Domino contacts are synchronized into AD. Only 236 (and the same 236....I've recreated the environment several times with the same results) contacts are created in AD from the Domino Directory. I have turned on logging for the connector and the following multiple errors are listed (from earliest to latest order) in the application log:
Error opening Notes document with id = 2caa
Notes Package ID: Notes Index Facility (NIF). Extended Reason String: The object store that is used by this note was not found or is not a Notes database
Error opening Notes document with id = 2cb6Notes Package ID: Notes Index Facility (NIF). Extended Reason String: The object store that is used by this note was not found or is not a Notes database
Error opening Notes document with id = 2cba
Notes Package ID: Notes Index Facility (NIF). Extended Reason String: The object store that is used by this note was not found or is not a Notes database
Error {GRC:f} detected when processing names.nsf
Error {GRC:808}: Failure reading transaction 237
Directory Synchronization Import is complete. dxa.exchange successfully imported 236 entries, and had problems importing 0 entries.
Error {GRC:808}: The application failed while processing.
The errors in the log after the above errors then go to show that the dxa service receives an abnormal shutdown request, and eventually the directory connector service terminates itself. I don't understand why only certain entries are being transferred? If I click on "Directory" in the Transporter Management Console, I can see all 960 of our users. Any thoughts as to what the root cause could be?
My second issue is that I cannot create a Free/Busy lookup connector on the Exchange Server. When I go to create a local connector in the Transport Suite, I receive a error saying : "Could not find any Exchange 2007 servers in the directory". I'm not sure what this error means... I can send mail within Exchange and between Domino and Exchange, which indicates that AD is storing the necessary Exchange information. Thoughts or ideas???
-
Answers
- This issue was caused by a corrupted Names.nsf file. Using a different names.nsf file worked like a champ!
Trevor- Marked As Answer byrovert506 Friday, November 06, 2009 5:05 PM
All Replies
Hi Trevor,
I haven't seen the error you are experiencing with the DirSync before but have seen many others. It may be a corruption in the Domino Names.nsf for those entries or more likely would be an error in the Transporter tool itself. Can you revert to a different version of the tool? I had to switch between a fair few versions of Transporter in my last migration when some bugs were introduced and different features worked in different versions.
If it is not the Transporter suite, can you manually register new users in the Domino directory individually just in case any automated creations are introducing errors that trip up the migration tool and then perform a sync to see if they come across or also fail.
With your Free/Busy connector issue I would first confirm that you have the public folder created. Are you creating the connector in the Transporter Management Console or Command Shell? If you use the Command Shell you may be able to add switches to receive more diagnostic information.
Cheers,
Rhys
- This issue was caused by a corrupted Names.nsf file. Using a different names.nsf file worked like a champ!
Trevor- Marked As Answer byrovert506 Friday, November 06, 2009 5:05 PM
