Why Experts Exchange?

Experts Exchange always has the answer, or at the least points me in the correct direction! It is like having another employee that is extremely experienced.

Jim Murphy
Programmer at Smart IT Solutions

When asked, what has been your best career decision?

Deciding to stick with EE.

Mohamed Asif
Technical Department Head

Being involved with EE helped me to grow personally and professionally.

Carl Webster
CTP, Sr Infrastructure Consultant
Ask ANY Question

Connect with Certified Experts to gain insight and support on specific technology challenges including:

Troubleshooting
Research
Professional Opinions
Ask a Question
Did You Know?

We've partnered with two important charities to provide clean water and computer science education to those who need it most. READ MORE

troubleshooting Question

Error using Microsoft Transport Suite

Avatar of ACECORP
ACECORPFlag for United States of America asked on
Exchange
6 Comments1 Solution1134 ViewsLast Modified:
I am having a problem creating a new Directory Connector using the Exchange Transport.

We have the Microsoft Exchange Transporter Suite installed on a CAS server and we are trying to set up the transporter suite. One of the first steps in that set-up process is to create a new domino connector.

We enabled detailed logging within the Exchange Transport tool and the error details show below is what appears when we try to create a new domino connector.

We already have Notes 8 installed on the box, so I don't understand why the line "Microsoft.Exchange.Transporter.Provider.Domino.NsfDataReaderException: Notes client is not installed !" would appear.

Unhandled Exception: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> Microsoft.Exchange.Transporter.Provider.Domino.NsfDataReaderException: Notes client is not installed !
   at Microsoft.Exchange.Transporter.Provider.Domino.NotesDataAccess.GetNotesClientPath()
   at Microsoft.Exchange.Transporter.Provider.Domino.NotesDataAccess.AddNotesClientToPath()
   --- End of inner exception stack trace ---
   at System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)
   at System.RuntimeMethodHandle.InvokeMethodFast(Object target, Object[] arguments, Signature sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at Microsoft.Exchange.Transporter.DominoConnector.Configuration.NotesDataAccess.AddNotesClientToPath()
   at AddNotesClientToPath()
   at _mainCRTStartup()

We also made sure that the path to nlnotes.exe is present in the path variable section of Windows.

We were able to successfully create a new “Free/Busy Connector” so I don’t understand why we keep getting an error when trying to create a new-dominodirectoryconnector.

Any help resolving this error would be greatly appreciated.


TransportSuiteIssue.pdf
ASKER CERTIFIED SOLUTION
Avatar of Sjef Bosman
Sjef BosmanFlag of France imageGroupware Consultant

Our community of experts have been thoroughly vetted for their expertise and industry experience.

Commented:
This problem has been solved!
Unlock 1 Answer and 6 Comments.
See Answers