Section import and export messages have one of three levels, depending on their severity. When viewed in LYNX, all messages for a single section are displayed together and the icon for the most severe level is shown.
A section completely failed to import (or export). No details in 25Live (or the SIS) were updated.
Errors are usually caused by underlying issues in SIS data (such as an incomplete meeting pattern) or in the 25Live framework (such as an event type or folder not being configured correctly).
A section was partially updated, but some details were not carried over. Alternately, everything updated correctly but something unexpected happened.
A typical example is when a location is not available in 25Live. The rest of the section details will be updated, but the location is not assigned.
A section was updated with no problems.
Info messages include successfully assigned locations and newly generated event reference numbers.
How LYNX Interprets Errors and Warnings
It’s important to understand the difference between errors and warnings as LYNX interprets them. For example, you might consider a case where a section with a pre-assigned location couldn’t be assigned that location in 25Live on import as an error. LYNX, on the other hand, would give that situation a Warning severity level, because it was able to import the section, even though it was unable to update the assigned location part of the section data.
Common Import Messages
Cannot route event using Default rule, no unique match
LYNX is unable to determine which folder is most appropriate to save the event in 25Live.
You may need to readjust your Data Translation rules for organizations, event types, or categories, especially if this section also has an "ignored unknown XXXX" error. You may also want to review CollegeNET's Best Practices for cabinets and folders.
Error saving to the Series25 database
Database issues have prevented the section from being saved. Contact CollegeNET support.
Event locked, please try again later
The section is currently in use in 25Live and cannot be imported at this time. Locks usually disappear when another user closes an event, but an administrator can manually remove them in 25Live.
Space-bound event <related UID> of event <UID> locked, please try again later
|This error means the same as the previous one, except that it applies to sections in bound relationships.|
|Event which is marked to be cancelled/deleted, does not exist|
LYNX is expecting to delete an event in 25Live or mark it as cancelled, but it has already been deleted.
Event which is marked to be cancelled/deleted, is already cancelled
|LYNX is expecting to delete an event in 25Live or mark it as cancelled, but it has already been cancelled.|
Cannot assign location for any date
The location LYNX is trying to assign is already reserved in 25Live.
Location available for #/# dates
The location LYNX is trying to assign is already reserved in 25Live, but only on some of the section's dates.
|Location removed from academic priority <term code> by <section> (<term code>)|
When Academic Priority is enabled, LYNX can remove a location assignment on a conflicting event in order to make room for an imported class.
|LYNX is attempting to import something using a name that 25Live doesn't expect. Check your Data Translation tables to ensure terminology is aligned between 25Live and your SIS.|
Event is related to another event that has not imported yet
Two events in 25Live have a relationship but only one of them was updated from the SIS.
Not all binding events can be edited, location information cannot be changed
Sections that are bound to the imported section have been cancelled or denied, so the location of the imported section cannot be changed.
|Cannot change event type from <current event type> to <new event type> due to event type incompatibility with the event's parent folder||If your Data Translation rules dictate that a section should have a new event type, it may not be able to change if your cabinet structure does not allow it. Try deleting the event in 25Live and reimporting so that it is created fresh.|
Common Export Messages
The following messages may appear when exporting data from 25Live to your SIS.
|Assignment of multiple locations not allowed||25Live allows you to assign different locations to different dates, but most SIS types only allow one location per meeting pattern. Unassign all but one in 25Live before importing.|
|Room XXXX cannot be found in SIS||There is a mismatch between the name of a location in 25Live and what is expected by the SIS. You may need to check your Data Translations.|
|Extra location assignments in 25Live not exported to SIS||Additional location assignments have been made to a section in 25Live that already had a pre-assigned location in the SIS.|
|Room XXXX assigned in SIS (but not assigned to all occurrences in 25Live)|
25Live allows you to assign a location to some dates and not others, but most SIS types do not break it out by date. If a location is only partially assigned to dates in 25Live in this way, LYNX will export it to the SIS as if it were assigned on all days.
|Warning||Data sync conflict occurred. Room assignments in SIS are retained.||The location was updated in the SIS at the same time the location was changed in 25Live. The SIS location assignment is retained.|
On This Page: