You could also check the "Timeout" setting in the tps.config file for the ServiceDesk.Framework application. The default is fairly low and if you have large numbers of devices, it could just be timing out.
Change that setting to something like 12000000. I've had this happen before and it was a matter of getting the timeout setting correct.
Jamie, i've made the change but the result was the same... an empty list in Test Results
What does the import log file say when you test it? Also, can you create a query on the data connection object OK? I often find that if there is a problem with the connection I am more likely to see a meaningful error message when running a query than running an import.
I'm having the exact same problem. As a new user can I ask for some more details?
Where do you find the Import log file? How do you run a query on a data connection object?
You configure the location for the import log file on the same screen that you design your import mapping. The field is towards the bottom right of the page.
To run a query against a data connection object simply create a query as you would for any other object. You can do this either in Console within "Query and Report Designer" or in Web Access by right-clicking in your shortcuts panel and select "Create query". Then you'll find your Data Connection listed as a Module and your Data Connection Type listed as an Object.
My log file says; "There are no objects in the database to Import or the datasource could not be accessed. Make sure the datasource is not locked by another application or another user."
When I run a query I get an unhandled exception. It states that the COM class factory failed due to the following error. The server process could not be started because the configured identity is incorrect. Check the username and password.
I have changed the COM+ LANDesk Indentity properties to Interactive User, Local Service, Network Service and even the specific service account on the LDSD application server without any success. I get the same unhandled exception everytime.
Having the same problem. Has anyone made any progress on this?
Is the LDMS Remote console installed on the application server where you are running this import? That is a requirement and is often missed.
Your problem is the criteria on the query in SD.. Go into the query and edit it or create a new one