Troubleshooting Guide

A plan can fail for multiple reasons.

1. First check the ETL error files the one that ends in .log
2. If unable to figure out problem from error file, download plan complete with errors
3. If the data is not sensitive attach the zip file when emailing support@escholar.com

If data is sensitive use File Transfer Protocol (FTP) to send it to eScholar

The following can cause a batch in eDM to run for a long time.

1. Lots of data file with a large number of records (e.g. 1 million records)
2. Templates with a lot of fields (e.g. Student or Student Snapshot)
3. Data files that generate a lot of errors (e.g. bad dates in all records)
4. If you think the batch is stuck open the eDM console*, go to restart file or batch if you see the status counts on the top are changing  wait a bit
5. If the status counts are not changing you should restart services (see below)

Note: always make sure other batches or files are not running before you restart services because restarting services will stop those batches and they’ll have to be resubmitted 

eDM services may need to be restarted.

1. Open the eDM console*
2. Restart file or batch
3. If that doesn’t get the file to process, restart all services
4. If file still won’t process, fail the file or batch and resubmit the file

Note: always make sure other batches or files are not running before you restart services because restarting services will stop those batches and they’ll have to be resubmitted

File was in a data format that the system does not accept.

Check to make sure file is in an accepted format

For example we do not accept xls files but we accept csv. We also accept .txt, .tab, or .del format.  They can be in fixed length field format, or delimited. Acceptable delimiters include comma, pipe, and tab. We also accept zip files containing any of the aforementioned approved formats  

This can happen when the first line of the file does not correspond with the rest of the file.

1. The file may have a header and the box that indicates header row in File Manager was not checked

The first line in the file has quotes and the following lines do not or vice versa 

This normally indicates that the server is running out of disk space.

1. Delete the older batch folders from the Work folder on the ETL server
2. Consider taking this opportunity to also clean the unnecessary batch folders from the Work folder on the other ETL servers if available
3. Restart services via eDM Console*

Note: The Work folder is in the same directory as the eScholar folder.  In addition, always make sure other batches or files are not running before you restart services because restarting services will stop those batches and they’ll have to be resubmitted

That error message may mean that you have to restart the data flow service.

1. Open the Sagent admin tool
2. Click on the servers tab
3. Click on the status tab
4. If status says “connection lost” then restart the data flow service.

If status says anything else contact support@escholar.com

This most likely means that the analytical calculator component was installed incorrectly. 

1. Reinstall the analytical calculator component within Sagent for both the Server and Client installs.
2. If you are still encountering errors contact support@escholar.com

This could be a memory issue caused by contention for memory resources on the ETL Server due to multiple or long running load plans all running at the same time.

1. Wait 5-10 minutes and rerun plan

If the same problem happens again email support@escholar.com

This means the connection string in the command file or ESDM database is incorrect.

1. Contact your DBA to review the connection string

Examples of the database connection string –

DB2:  escdev:escdev:DB2:ESC_REP::sdbadmin:warehouse
Oracle:  escdev:escdev:Oracle:ESC_REP::sdbadmins:warehouse
SQL Server: escdev:escdev:SQL Server:CDW-ETL2:ESC_REP:sdbadmin:warehouse

Make sure the database name (ESC_REP) and the sdbadmin password matches your environment.

This often happens when you are running the default file path for the source or error file.

1. Go to the ETL configuration page and make sure the path names in the plans are valid

They should not contain “d:escholar…”

This means you need to create the Sort Directory on your ETL server.

1. Place the Sort Directory in your root directory.
2. In most cases the path will be D:ESC_SortDir.

You must name the sort directory ESC_SortDir, otherwise any plan that uses a disk sort will fail. 

This happens when the field is set for fewer characters than what you are uploading or there is a delimiter issue.

1. Check field in plan to confirm the error and make changes to file as appropriate

If field is correct, then check if the delimiter on the ETL configuration page matches your file

If you are running a load plan using a .csv file as input make sure the SOURCE_DelimiterCharacter Custom Plan Property (CPP) is set to a comma (,)  otherwise all the records in the input file will be rejected. Conversely, if you are running a load plan using a .tab file as input make sure the SOURCE_DelimiterCharacter CPP is set to a tab (%09)  otherwise all the records in the input file will be rejected.  The SOURCE_DelimiterCharacter is set on the ETL Plan Configuration Page for the plan you are attempting to run. Please refer to the examples below for guidance.

EXAMPLE:

Name of the source file : 142_CTE_ACADEMIC_ATTAINMENT_2012.csv
SOURCE_DelimiterCharacter = ,
OR
Name of the source file : 142_CTE_ACADEMIC_ATTAINMENT_2012.tab
SOURCE_DelimiterCharacter = %09

This error occurs when a load plan is missing a mandatory column, such as SCHOOL_YEAR, DISTRICT_CODE or STUDENT_ID, is blank. Please refer to the SCHOOL_YEAR example below for guidance.

EXAMPLE:

Error in source line 30, output record 29, field ‘School Year Date’: Column data is required.  None provided for field.  Error has occurred.

Sagent was installed prior to the Oracle client. Reinstall Sagent after confirming correct Oracle client install.

The issue is the database connectivity for the Delete Utility. To check the server is configure properly

1. Go to %ESCHOLAR_HOME%DeleteUtilityconfconn.properties
2. Review the database information for the Default Connection information

DeleteUtil.url=jdbc:sqlserver://DEMO-DB1:1433;databaseName=DELADMIN

DeleteUtil.driver=com.microsoft.sqlserver.jdbc.SQLServerDriver

DeleteUtil.userid=sa

DeleteUtil.password.encrypted=false

DeleteUtil.password=XXXXXXXX

DeleteUtil.initial.connections=2

DeleteUtil.maximum.connections=100

DeleteUtil.dbtype=SqlServer

The database connectivity for the Warehouse has an issue.  To check the server is configured properly

1. Go to %ESCHOLAR_HOME%DeleteUtilityconfconn.properties
2. Review the database information for the CDW Connection information

CDW.url=jdbc:sqlserver://DEMO-DB1:1433;databaseName=WAREHOUSE

CDW.driver=com.microsoft.sqlserver.jdbc.SQLServerDriver

CDW.userid=sa

CDW.password.encrypted=false

CDW.password=XXXXXXXXX

CDW.initial.connections=2

CDW.maximum.connections=100

CDW.dbtype=SqlServer

Validate the database server, user and password.  Using Microsoft Management Studio or Oracle SQL Developer connect to the database using the username and password