3:
Re: Re: Error importing into one server but not another
By: Fiona Malikoff
|
In response to 2 | 10/10/06 01:38 AM | ||
Ken,
I'm not sure I can give you an answer on this one. When you get that error, the real error is usually a little way back up the log. Its one of those unfortunate errors where the one the user gets is a side effect of the problem, not the real problem. Any chance you could try doing it again and posting the lams.log and system.log? I've tried importing the sequence myself, and found that our importer doesn't cope with an entry for a tool that isn't installed in LAMS. I've raised this as an issue (https://bugs.lamsfoundation.org/browse/LDEV-848) and this should be attended to in the next few days. I could install the behaviour composer tool, but the importer needs to be fixed so that it will cope with a "missing" tool. Once we have it skipping any activities for uninstalled tools, then we will have a look at it to see if we can find another bug. Fiona ps I assume you did double check that you had the tool installed on the problem LAMS server? Posted by Fiona Malikoff |
|
|||||||||||||||
|
|||||||||||||||
|
|||||||||||||||
|
|||||||||||||||
|
|||||||||||||||
|
Reply to first post on this page
Back to LAMS for Tech-Heads - General Forum