The Lan-Inspector will create ODBC shortcuts in the frontend. The scheduler, however, runs on the computer running the LaniMasterServer service. Therefore, if the scheduler is to export data, the ODBC shortcut must exist on the master servers’ system. To avoid this problem, start a frontend on the server and configure the links there.
Problems with access using Access: Due to the scheduler running as independent session in SYSTEM context, problems may arise when accessing Access MDB-files residing on network drives. To export via a scheduler, the MDB file must reside on the local Lan-Inspector computer.
Problems with MSSQL permissions: Since the scheduler runs in SYSTEM context, problems may arise when accessing the SQL server, in case of ODBC shortcut configuration via “Windows Authentication”. To export using scheduler, you need a SQL server account (e.g. sa, if available.)