Suddenly having several job failures. When I attempt to run as a manual start, getting "Object reference not set to an instance of an object." as an error. Started to get these yesterday working with loop lists and log components then today, several scheduled jobs fail.
Seems to be related to export component in this instance as all processing tables were generated... just not being able to export. This is perplexing as no changes to scripts or environment were made.
Export seems to begin as partial output occurs then fails.
FOUND TO BE ENVIRONMENTAL
Windows 10 (1909)
Toad Data Point 5.1.2.166 32 bit
Dave
This is now affecting export to file components as well. Below is basic log:
-- 4/28/2020 9:21:09 AM: PSON_AUTO.log: Setting up environment
-- 4/28/2020 9:21:09 AM: PSON_AUTO.log: Script run by Toad Data Point 5.1.2.166 as daburns on CNCVDA1946
-- 4/28/2020 9:21:09 AM: PSON_AUTO.log: AppDataDir = C:\Users\daburns\AppData\Roaming\Quest Software\Toad Data Point 5.1
-- 4/28/2020 9:21:09 AM: PSON_AUTO.log: Temp Dir = C:\Users\daburns\AppData\Local\Temp\3
-- 4/28/2020 9:21:09 AM: PSON_AUTO.log: Build started
-- 4/28/2020 9:21:09 AM: PSON_AUTO.log: Compiling script
-- 4/28/2020 9:21:09 AM: PSON_AUTO.log: Start CompileWorkflow
-- 4/28/2020 9:21:09 AM: PSON_AUTO.log: Before Compile
-- 4/28/2020 9:21:12 AM: PSON_AUTO.log: Return from CompileWorkflow
-- 4/28/2020 9:21:12 AM: PSON_AUTO.log: Workflow Compiled without Errors
-- 4/28/2020 9:21:12 AM: PSON_AUTO.log: Build completed
-- 4/28/2020 9:21:12 AM: PSON_AUTO.log: Create Workflow instance
-- 4/28/2020 9:21:12 AM: PSON_AUTO.log: Started workflow instance
-- 4/28/2020 9:21:12 AM: PSON_AUTO.log: Begin execution script activities
-- 4/28/2020 9:21:12 AM: PSON_AUTO.log: Variable "ROOT_PATH" set to
-- 4/28/2020 9:21:12 AM: PSON_AUTO.log: Variable "RUN_MODE" set to Production
-- 4/28/2020 9:21:12 AM: PSON_AUTO.log: Scanning the script for prompt bind variables
-- 4/28/2020 9:21:12 AM: PSON_AUTO.log: Executing Grouping_1 group
-- 4/28/2020 9:21:13 AM: PSON_AUTO.log: Copied file \centene.com\SHARED\AUS\Texas_Reports\Data_Analytic_Recurring_Rpt\PSON\3_Automation\PSON_TEMPLATE.xlsx to \centene.com\SHARED\AUS\Texas_Reports\Data_Analytic_Recurring_Rpt\PSON\3_Automation\PSON_.xlsx
-- 4/28/2020 9:21:13 AM: PSON_AUTO.log: Copy File finished, click PSON_.xlsx to view file.
-- 4/28/2020 9:21:13 AM: PSON_AUTO.log: Begin Export of EXPORT_STATUS
-- 4/28/2020 9:21:13 AM: PSON_AUTO.log: Connection description = TX_ANALYTICS_ETL_USER@EDWP (ETL_ACCESS_OWN)
-- 4/28/2020 9:21:13 AM: PSON_AUTO.log: Connection node found
-- 4/28/2020 9:21:13 AM: PSON_AUTO.log: Connection to: TX_ANALYTICS_ETL_USER@EDWP (ETL_ACCESS_OWN)
-- 4/28/2020 9:21:13 AM: PSON_AUTO.log: Begin Export
-- 4/28/2020 9:21:13 AM: PSON_AUTO.log: SQL to execute: SELECT * FROM HP_TX_OWN_TABLES.DLY_PSON_STATUS_FINAL ORDER BY 1
-- 4/28/2020 9:21:13 AM: PSON_AUTO.log: Beginning export
-- 4/28/2020 9:21:54 AM: PSON_AUTO.log: EXPORT_STATUS - Object reference not set to an instance of an object.
-- 4/28/2020 9:21:54 AM: PSON_AUTO.log: Object reference not set to an instance of an object.
-- 4/28/2020 9:21:54 AM: PSON_AUTO.log: Start error email
-- 4/28/2020 9:21:55 AM: PSON_AUTO.log: Exception Email successfully sent
-- 4/28/2020 9:21:55 AM: PSON_AUTO.log: Failed
I am getting the same error when exporting through automation only. When I export the same result set to CSV manually it works just fine. Any updates on this?
Update: Rolled back to Toad Data Point 5.0.7.106 (32 bit) and everything is working normally again.
Hey John... my issue, we're pretty sure, was due to the server being mirrored. Some tables were still locked I guess when trying to export.
I can't say if that helps either way for me. The CSV is on a network resource where I am the only user and I got the exception even immediately after a reboot. I was able to get the error to come and go. It appeared that the magic number for me was 2500 rows of data.