Hi Van Nguyen,

We were aware of all the failures above. We receive emails as well as we weekly monitor the failures to see if there's any error.
We are bit struggling with our error logging and not able to judge the cause of failure. Also, from the incomplete error message we received, we tried to reproduce the issue but could not. We are also working on improving the logs under WT-4723. There are few more options like database logging we will try out.

Thanks for your patience. We'll keep updating about our progress.

Hi Suraj,

Can you please share details on this Import failure & our mitigation plan?

Regards,
Satya Prakash

Cc: Jaideep Vinchurkar Vijay Siddha

Satya Vijay Siddha Please check this on priority.

Hello Vinayak Kulkarni, I am escalating this issue to you since the client, Groendyke, is upset and wants an explanation right away.

Hello Suraj Sokasane and Jaideep Vinchurkar,

Groendyke would like to know once this import failure issue has been resolved and have asked for it to be expedited. I don't know if you need to get our third party vendor Clare Computers or even Verizon involved to see what is going on.

Another Import was failed on JE Dunn on 05/22/2017 with same error. We are planning to deploy logs on production for this issue.

Hi Jaideep Vinchurkar ,

We have scanned error log with reported error, with initial analysis we found error log as

"Import FailureExecuteImportDTS.AutomatedImportFile -> ExecuteImportDTS.ImportNotificationThroughEmail ->ExecuteImportDTS.GetSenderMailAddress Object reference not set to an instance of an object.##1. Import Failure."

Its shows, Error raised on while sending Import success notification after successful import, this error was not reproduced locally or on production.

CC : Satya Vijay Siddha Rakesh Roy Suraj Sokasane