Delta Import on ILM MA causes app-store error
Every time I runDelta import onILM MA it causes app-store-import-exception error. It never runs all the way through.If I run Full Import, it doesn't cause the error.Does somebody know how to avoid it?
August 7th, 2009 1:41am

I don't know the way how to avoid it - probably it is another RC0 oddity - I've never looked on connect database if it is reported there or not and I will wait for newer build to see if it was fixed. However ... from my experience You need to restart ILM service to get rid of this error. After service restart delta imports start to work again. Restarting synch engine might also be a good idea if you will do ILM service restart. I know - this isn't solution for production environment, it isn't solution at all ... more workaround ... bad one ... but I'm just sharing my experience.
Free Windows Admin Tool Kit Click here and download it now
August 9th, 2009 11:51pm

When I've hit this I've found a service restart, followed by a full import and full synchronisation has fixed it. Note. When you [full] sync your ILM MA be sure to check that the sync rules have synchronised and haven't errored.
August 11th, 2009 6:02pm

Thank you for your replies.I imported some more user accounts to ILM portal, now even full import on ILM MA gets the same error. When I reset ILM agent password and restart the service, it starts working. It imports about 5000 accounts and stops with app-store-import-exception error. Total number of accounts in ILM Portal right now is about 60000. The ILM instance is running on a HyperV with 4 GB RAM, 60 GB (30 GB is free) C drive and 30GB (15 GB is free) E drive. E drive stores ILM database files. The other problem I encountered is that during ILM operations the memory usage grows to the maximum and never clears up. I see that most of the memory is used up by sqlserver process. I am not sure if it might be related.
Free Windows Admin Tool Kit Click here and download it now
August 11th, 2009 8:40pm

SQL Server memory usage does grow as it gets used and doesn't usually relinquish it without a stop and start of the SQL Service. You can set a limit to the maximum memory for SQL Server -- single box with everything on it and only 4 GB of RAM I would set it at the SQL Server Maximum RAM at 3 GB or maybe 3.25. I have seen the ILM Web Service behave funny when SQL doesn't have enough RAM, but SQL can also choke out other apps and services.David Lundell www.ilmBestPractices.com
August 16th, 2009 3:43am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics