Troubleshooting FAQ

1. The loadadmin and loadsupport creation is failing because SQL Server is unable to create the DBs due to lack of privileges to write files in the default (C:\sql_db\) directory.
   If the relevant users have privileges to create files in the directory, then most likely the SQL Server is not in mixed authentication mode, if this is a fresh installation. Check to make sure SQL Server is in mixed auth mode.
2. The loading seems to be stuck but there is no error or warning message in the task log.
   Look at the LOAD (if the loading is in the task db stage) or PUB (of it is in the publish/finish stage) job history in the SQL Server Agent jobs to see if the job ended with an error. The history entry will show an error corresponding to the problem.
3. The SQL Server Agent is running and LOAD/PUB jobs are active, but the tasks are not getting beyond the detach (DTC) stage.
   Click on the Servers page in the load monitor and make sure that the PUB server state is "running" (arrow).
4. The BLD is throwing an error because it is unable to create a task DB because some files could not be created due to lack of permissions.
   The Windows domain user that the loadagent SQL Server user is mapped to does not have permissions to create files in the directory that the taskdatapath entry in the Constants table is pointing to. The loadagent user needs to be mapped to a domain admin Windows user.
5. The CSV check step does not find any files so the task finishes without loading any files.
   The csv_ready file at the top level should be empty or have valid file names in it. Make sure that if it is supposed to be empty it is actually 0 bytes in size.

Miscellaneous FAQ

1. How do I add a new export type to the loader?
   You need to perform the following steps to add a new export type (e.g. GALSPEC):
   1. Add the export type to admin\newtask.asp and admin\add.asp.
   2. Add a case for the new export type to x_upload.js.
   3. Add a regexp pattern for the CSV fles for this export type to vbs\csvrobot.vbs under the appropriate export subdirectory (e.g., spCSV\galspec\).
   4. Add validation tests if applicable to schema\sql\spValidate.sql (e.g. unique key tests) - create a new stored procedure for this export type.
   5. If necessary, add a case to schema\sql\spSetValues.sql for the files in this export type.
   6. Add the commands to copy the tables for this export from the task db to the publish db in schema\sql\spPublish.sql.
   7. Add indices for the tables in this export to IndexMap (schema\sql\IndexMap.sql).
   8. Finally, add any code necessary to merge this data into the publish DB during the FINISH processing, in schema\sql\spFinish.sql.