Download Error Resolution (Query Analyser) for On Demand Imports New

1
On Demand Import Error Resolution for CHESS/Cases Schools
Common reasons for import errors are:






The file is not saved in comma delimited (CSV) format,
There are fields missing,
There are fields in the wrong order,
Field lengths are wrong,
Data formats of fields are wrong,
Columns still have their headings.
Two other possible reasons for the import to fail are detailed in the following Table:
PROBLEM
SOLUTION
Unable to save to database
 The problem is that the field stdnt_extrnl_xid does not match the stdnt_xid
If the import fails with the
field in the database and is causing errors. This can be fixed fairly quickly
message of:
but will require someone with administration access to the On Demand
server, e.g., a school technician.
Import failed: Unable to save to
database ['You have entered a
record that already exists or 1. Log into the On Demand server.
On Demand VM, Start > All Programs > Microsoft SQL Server 2005 >
has been used.' (-2147220991)]
SQL
Server Management Studio (see Figure 1)
Followed by a series of
failures with message:
Import failed: Unable to save to
database ['Method '~' of object
'~' failed' (-2147220991)]
Figure 1 – Finding the SQL Server Management Studio.
D:\769855392.doc
2
Figure 2 – The Connect to SQL Server.
2.
Click “Connect”
Figure 3 – Open an New Query
3.
Enter the following as the SQL command in the Query window EXACTLY as it
appears below.
USE AIM
UPDATE student
SET stdnt_extrnl_xid = stdnt_xid
WHERE stdnt_extrnl_xid IS NULL
D:\769855392.doc
3
Figure 4 – the new Query exactly as written.
4.
5.
Duplicate student external
XID
The import fails with the
message:
Import failed: Duplicate
Student External Number XID
D:\769855392.doc
Once you have entered this click on the “Execute” button to execute the query.
You will see a confirmation along the lines of “(16 row(s) affected)”.
Once you have done this exit from the SQL Query and try the import again.
 The students name and/or date of birth has been changed in CASES and
no longer matches what is recorded in On Demand. On Demand then
thinks that you are trying to create a new student with the same ID as an
existing student. Unfortunately students with this error will have to be
updated manually. Once their name and date of birth match in both On
Demand and CASES then future imports will work without issue.
 The most common cause of this problem is that a middle name has been
recorded for students where previously it was blank.
 As with all import error messages the import has only failed for the
records shown in the error log, all other students will have been imported
successfully.