Differences

This shows you the differences between two versions of the page.

--- normal_processing_steps [2021/02/02 20:11]
dlm created
+++ normal_processing_steps [2021/02/02 20:38]
dlm [Troubleshooting]
@@ Line 1: / Line 1: @@
-=== 'Normal' Processing Steps ===
+====== 'Normal' Processing Steps ======
+\\
+====Here is a recommendation of steps to follow when a file is to be added to the NovoMotion Outbound process:====
-Here is a recommendation of steps to follow when a file is to be added to the NovoMotion outbound process:
+  - Create a new schema using either [[novo_motion_novo_gen.schema|NovoMotion NOVO.GEN.SCHEMA ]] or [[novo_motion_schema_editor|NovoMotion Schema Editor]].
+  - In the [[novo_motion_schema_editor|NovoMotion Schema Editor]], establish the connection information on the SQL Options tab and activate the schema.
+  - In the [[novo_motion_schema_editor|NovoMotion Schema Editor]], use the SQL script creation ([[Creating a SQL Script]]) process to generate a SQL script to copy and execute in the SQL database.
+  - If the ODBC datasource is new, create it by either adding a data source through the Administrative Tools (Windows) or ding the data source to the odbc.ini record (Unix).
+  - Use the [[load_bci.action|LOAD.BCI.ACTION]] process to test a load from the U2 server to the SQL server.
+  - Correct dictionaries, connections, or schema records as needed.
+  - Once there are no identified issues, use NOVO.E.T ([[novo_motion_trigger_generator|NovoMotion Trigger Generator]]) to enable an UPDATE (and usually a DELETE) trigger on the U2 file.
+  - Use the [[load_bci.action|LOAD.BCI.ACTION]] process to load all the records from the U2 environment to the SQL server.
+  - Check the SQL server to verify results.
+\\
+====Troubleshooting====
-  - Create a new schema using either [[novo_motion_novo_gen.schema|]] or [[novo_motion_schema_editor|]].
+^ Error Message                    ^ Analysis Steps ^
-#In the [[NovoMotion Schema Editor]], establish the connection information on the SQL Options tab and activates the schema.
+| No BCI.ACTION record created    | Verify the trigger is on using LIST.TRIGGER. If the trigger exists, try logging off and back on. If the file is the TM, make sure the table number has been added on the NovoMotion Interface Control Trigger Controls tab. |
-#In the [[NovoMotion Schema Editor]], use the SQL script creation ([[Creating a SQL Script]]) process to generate a SQL script to copy and execute in the SQL database. <br /><br />
+| No Schema exists for filename    | Verify the schema is flagged as Active in the [[novo_motion_schema_editor|NovoMotion Schema Editor]]|
-#If the ODBC datasource is new, create it by either adding a data source through the Administrative Tools (Windows) or ding the data source to the odbc.ini record (Unix). <br /><br />
+| Connection does not exist   | Verify the correct login and password are entered in the SQL Options tab of the [[novo_motion_schema_editor|NovoMotion Schema Editor]]. If they are, verify the datasource is set up. If it is, verify the login has permission to the database on the SQL server. |
-#Use the [[LOAD.BCI.ACTION]] process to test a load from the U2 server to the SQL server. <br /><br />
+| Invalid Object Name error    | Verify the database name on the SQL options tab of the [[novo_motion_schema_editor|NovoMotion Schema Editor]] is fully qualified i.e dbo.filename |
-#Correct dictionaries, connections, or schema records as needed.  <br /><br />
-#Once there are no identified issues, use NOVO.E.T ([[NovoMotion Trigger Generator]]) to enable an UPDATE (and usually a DELETE) trigger on the U2 file. <br /><br />
-#Use the [[LOAD.BCI.ACTION]] process to load all the records from the U2 environment to the SQL server. <br /><br />
-#Check the SQL server to verify results.<br /><br />

NovoRoi Systems DokuWiki

User Tools

Site Tools

Differences

Page Tools