TOPIC: Scheduled RRD failing randomly

Scheduled RRD failing randomly 20 Apr 2016 15:30 #2235

  • CorLiving-IT
  • CorLiving-IT's Avatar
  • Offline
Hi,

We have a scheduled RRD run every day, and some days it just fails for some unknown reason. If I run it again, it usually runs successfully.
The history in task scheduler shows:
Task Scheduler successfully completed task "\Crystal Sales Forecast E-mail" , instance "{d9159d63-89c7-4853-b02c-ede7a69b3e2c}" , action "C:\Program Files (x86)\SaberLogic\Logicity\Logicity Desktop.exe" with return code 3762507597.

When it's actually successful, the return code is 0.
This report usually takes about an hour to run when successful, but when it fails with the return code above, it's after only 3-5 minutes.

Is there any way to know why this happens? The logging doesn't seem to be much help. Is there any more verbose logging?

Thanks.
The administrator has disabled public write access.

Scheduled RRD failing randomly 20 Apr 2016 15:36 #2236

  • mholbrook
  • mholbrook's Avatar
  • Offline
Hello,

Is it possible this report sits on a public drive and someone else has it open at that time? Thanks!

Matt
The administrator has disabled public write access.

Scheduled RRD failing randomly 20 Apr 2016 15:38 #2237

  • CorLiving-IT
  • CorLiving-IT's Avatar
  • Offline
Matt,

Yes the report and the RRD sit on a public network location, but nobody other than the user that executes the scheduled task have access to it.

Thanks in advance for your help.

-Aaron

EDIT: I should have added that the RRD runs in the middle of the night, so it's very unlikely that anyone else would access it, even if they had permission to the folder.
Last Edit: 20 Apr 2016 15:41 by CorLiving-IT.
The administrator has disabled public write access.

Scheduled RRD failing randomly 20 Apr 2016 15:42 #2238

  • mholbrook
  • mholbrook's Avatar
  • Offline
Hi Aaron,

If you are watching it execute you don't see Logicity pop up with any error messages? How long does it take take to run in crystal, because i noticed you said it takes an hour to run. Does this only happen with one particular report and you have others that are successful all the time? if so, could it be that maybe the report has an error in it from time to time like a division by 0 or something that would occasionally cause it to fail depending on the particular data? Thanks!

Matt
The administrator has disabled public write access.

Scheduled RRD failing randomly 20 Apr 2016 15:51 #2239

  • CorLiving-IT
  • CorLiving-IT's Avatar
  • Offline
The task runs in the middle of the night, so I don't see it while it executes. I haven't seen it pop up any error message when I run it manually in the morning after it fails though.

Yes, it normally does take an hour to run even in Crystal. So far I have not had any other RRD encounter this issue, just this one.

It's certainly possible that there's an error in the report. But if that were to happen, wouldn't the task stay active until the "stop the task if it runs longer than" threshold is reached? Which it hadn't by the time I checked on it (set to 12 hours).
Would it report as being successful but with that exit code?

-Aaron
The administrator has disabled public write access.

Scheduled RRD failing randomly 20 Apr 2016 16:32 #2240

  • CorLiving-IT
  • CorLiving-IT's Avatar
  • Offline
So not sure why I didn't think to check the Windows event log until now. Here is the information when the task fails.
See the Wndows Error Report attached.

File Attachment:

File Name: Report.wer.txt
File Size:54 KB



Log Name: Application
Source: Windows Error Reporting
Date: 4/19/2016 8:03:59 PM
Event ID: 1001
Description:
Fault bucket , type 0
Event Name: CLR20r3
Response: Not available
Cab Id: 0

Problem signature:
P1: logicity desktop.exe
P2: 1.8.9.0
P3: 56f2f060
P4: System.Windows.Forms
P5: 2.0.0.0
P6: 54d46ec6
P7: 48bb
P8: 96
P9: System.InvalidOperationException
P10:

Attached files:
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_logicity desktop_bc8d318a76921ac60bb60bb772accc65c27c20_66d80303

Analysis symbol:
Rechecking for solution: 0
Report Id: 8694757d-06a4-11e6-9413-000e0c6f8e62
Report Status: 4
Event Xml:
<Event xmlns="schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Windows Error Reporting" />
<EventID Qualifiers="0">1001</EventID>
<Level>4</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2016-04-20T03:03:59.000000000Z" />
<EventRecordID>947</EventRecordID>
<Channel>Application</Channel>
<Computer>AUTOMATION1</Computer>
<Security />
</System>
<EventData>
<Data>
</Data>
<Data>0</Data>
<Data>CLR20r3</Data>
<Data>Not available</Data>
<Data>0</Data>
<Data>logicity desktop.exe</Data>
<Data>1.8.9.0</Data>
<Data>56f2f060</Data>
<Data>System.Windows.Forms</Data>
<Data>2.0.0.0</Data>
<Data>54d46ec6</Data>
<Data>48bb</Data>
<Data>96</Data>
<Data>System.InvalidOperationException</Data>
<Data>
</Data>
<Data>
</Data>
<Data>C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_logicity desktop_bc8d318a76921ac60bb60bb772accc65c27c20_66d80303</Data>
<Data>
</Data>
<Data>0</Data>
<Data>8694757d-06a4-11e6-9413-000e0c6f8e62</Data>
<Data>4</Data>
</EventData>
</Event>
Last Edit: 20 Apr 2016 16:40 by CorLiving-IT. Reason: Attachment didn't attach
The administrator has disabled public write access.