NSOutlookSynchronizationHandler not designed for a NAS?

Henry@columbus

I’m trying to run a outlook synchronization from a NAS, but I keep getting a message “The Outlook handler cannot be started.”.

This is due to the following code: (codeunit 5072, function Logon)

IF NOT CREATE(OLHandler) THEN BEGIN
  MESSAGE(CannotStartOutlookHandler);

Here is my code from codeunit 1

// - Outlook syncronisation
  IF (COPYSTR(Parameter,1,4) = 'OUTL') THEN 
    BEGIN
      IF (USERID <> '') AND (Salesperson.READPERMISSION) THEN BEGIN
        Salesperson.SETRANGE("Navision User ID",USERID);
        Salesperson.SETRANGE("Enable Synchronization",TRUE);
        IF Salesperson.FIND('-') THEN
          BEGIN
            StartOutlookSyncronization;
            CGNASStartedinLoop := TRUE;
          END;
      END;
    END;
// + Outlook syncronisation

If I run the code with a standard client, everything is working fine. It looks like Navision has protected the olHandler automation control from being executed from within a NAS.

Does anybody has any experience or a solution for this problem?

Thanks

kine

Under which account you are running the NAS???

DenSter

Is Outlook installed on the NAS machine?

Henry@columbus

Outlook is installed on the NAS machine.

The NAS is running under a salesperson account, witch has been set up in Navision under Salesperson->Outlook intergration

DenSter

<deleted text because of double posting>

DenSter

So if you log on to the NAS machine with the salesperson account and run the outlook integration manually from a Navision client, it runs fine?

Henry@columbus

Exactly.

Even when I create a codeunit witch only creates the OLHandler, it runs fine in a client but not in the NAS.

DenSter

And on the logon tab of your NAS service, you specify the salesperson account?

Are you using NAS-CLASSIC or SQL?

One other thing that keeps screwing things up for me is the nettype. NAS is installed with TCPS by default, and somehow that just doesn't work with Navision. All your Navision services (database server as well as NAS) must be installed with nettype TCP.

You can't change the nettype on NAS-SQL (it's a bug that they say they fixed in SP1), so you'll have to change that using the command line. Let me know if you need help with that.

kine

May be that the automation need GUI from some reason but NAS is W/O GUI... it is question for MS. Did you sent it as service incident on partnersource?

Henry@columbus

I’ve tested the NAS (NAS-classic, TCP) and it is working fine.

I think Kine is right about the NAS needing a GUI, or MS has designed the DLL only to work with a Navision client. Never the less it will not work with a NAS, and that’s a same…

Thanks for your help.

Henry

DenSter

Yes it sounds like you need to get some MS support. Let us know what the result is please .

navisi0ne

Did you take a look at:
Technical White Paper: Microsoft Business Solutions - Navision Relationship Management 3.60 and 3.70

this is the Content:
Content
Relationship Management–Navision Technical White Paper 1
Navision Integration with Outlook 1
E-Mail Logging for MS Exchange Server 2
Installation & Setup 3
General Requirements 3
A. Setting Up the Exchange Server 3
B. Setting Up Navision 3
C1. Using the Navision Application Server 4
C2. Using the Navision Client 4
Troubleshooting 6
Outlook Client Integration 7
Setup Issues 7
Technical Issues 8
Limitation Issues 9
User Impact Issues 11



you can download it from partnersource.

Dmitry_Chadaev

I heard that the problem is fixed in one of the latest updates of Navision 4.0. The dll should be available for NAS now.