Verified on production.
Company: CVHP For HSPL
Verified all attached test cases.Import done successfully.
Working as expected.

Thanks,
Sanjana Jadhav

CC: Prasad Pise Hrishikesh Deshpande Rakesh Roy Ganesh Sadawarte Jayshree Nagpure Suraj Sokasane

Verified on stage.
Getting notification when scheduler was unexpectedly stopped.
Please refer attachment for same:

Error occurred while import.
Filezilla credentials:
Username: WT17
Password: @CCe$$_1007
Refer below error log:
============================================================
Company Level Import : Austin For HSPL

Template Name : test_imp
DateTime : 2/5/2018 10:23:54 PM
Status : Error occured while import.
Error Source : ExecuteImportDTS.AutomatedImportFile->ExecuteImportDTS.UploadFileOnFTPServer
Error Message : 530 User WT17 cannot log in.

============================================================

As discussed with Ganesh Sadawarte marked this jira as ready for production. If same issue will occur on production, we will take action accordingly.

Thanks,
Sanjana Jadhav

CC: Hrishikesh Deshpande Prasad Pise Rakesh Roy Jayshree Nagpure Suraj Sokasane Ganesh Sadawarte Jaideep Vinchurkar

Verified on LB.
Getting notification when scheduler was unexpectedly stopped.
PFA,

Ready for stage.

Thanks,
Sanjana Jadhav

CC: Prasad Pise Jayshree Nagpure Rakesh Roy

HI Satya,

As per jaideep comment scheduler was stopped by system exception not due to any code issue and previously we don't get any notification when scheduler was unexpectedly stopped.

Now We have added schedule task Import Export Scheduler Status on 75 server. This will run in every 15 minutes and checked import export scheduler service status, if service is stopped or pause it will send email notification to users which are added for this job notification. Please find below snap.

This utility is place into N:\Harbinger\ExportScheduledTasks on 75 server.

CC-Vinayak Kulkarni,Suraj Sokasane

Thanks,
Ganesh

Reopening this to find exact root cause.

As of now, we are resolving this by marking can not reproduce, because scheduler has picked the file for this week.

Concern: Import files are not seen in calendar.

Cause: Scheduler service was stopped (by system exception) for a day.

Correction: As of now, we do not have logs for this. We are checking with our technical team if we can increase log size of windows to find out the root cause

Hi Damion M Velasquez,

We found that scheduler service was stopped on 11/01/2017 at 10.30 AM PST to 11/2/2017 12 AM PST. This is system failure. Since the failure we have 8 days and we do not have any system logs about exception.
Today, schedule picked all files. Please refer

Hi Damion M Velasquez,

The Import feed was skipped and not executed on 01/11/2017. So it's not showing in the calendar. We are looking into possible cause. We'll update you soon on same.

Hi Jaideep, Please check this, Let me know if you have any questions. Thanks.