Here is an example of what I am seeing in the log: The scheduled import is not failing, however no records are being pulled in. (the last successful import was on 6/9 - see 766 records below)
6/9/2010 9:00:36 AM : There was an Object Type Missmatch. System.Analyst != System.EndUser (White, Craig)
6/9/2010 9:00:38 AM : ProcessMappings: Record = 766
6/9/2010 9:00:38 AM : Import Ended
6/9/2010 9:00:38 AM : This import took 00:00:37
6/11/2010 9:00:00 AM : Import Started
6/11/2010 9:00:07 AM : ProcessMappings: Record = 0
6/11/2010 9:00:07 AM : Import Ended
6/11/2010 9:00:07 AM : This import took 00:00:07
We have made the following changes, but I am unsure on how I can identify how the import is setup (other than what is showing under Administration/Data Import/Import Mappings).
1. started a new buildout of a new Exchange Mail infrastructure
2. upgraded our Domain Controller from Server 2003 R2 to Server 2008 R2
3. made changes to the domain controller so if LANDesk is looking for a certain Domain Controller by name and it is tied to Montana, it is no longer around
It's often useful to build a query based on the connection object.
Then you can see what the source data is.
If the query is empty then the problem is with the connection rather than the import.
If the query is full then the import is the issue.
In query builder:
Module = Your Connection
Business Object = Your Connection Type.
You can find it in the "Data Connections" component.
This will usually be in the administration or designer shortcut bar.
If you can't see it there you can add it using the Shortcut Manager.
The Data Connections tree will have an "Active Directory" branch.
The connections will be listed on this branch.
Under those will be your various Connection Types.
If you check the import you're having trouble with the Source box shows the Data Connection & Types.
They are the Module & Business Object respectively.
You can use query builder to build a query on these.