Job ran, but there is no schedule for the job (2 replies)
FYI: DB Version 5.06
Arline,
Is there another version of Iman running? Email properties will display which server is sending the audit reports
FYI: DB Version 5.06
Arline,
Is there another version of Iman running? Email properties will display which server is sending the audit reports
Realisable Software Ltd provides code-free, cost-effective applications integration solutions for SMEs. Our core IMan product is designed to integrate almost any application with a number of Sage solutions and online payment processors.
Looking to purchase IMan, please see our resellers here.
Realisable Software
Ph: +44 (0) 208 123 1017
Copyright © Realisable. All rights reserved.
Realisable is a registered trademark
Realisable Software Ltd provides code-free, cost-effective applications integration solutions for SMEs. Our core IMan product is designed to integrate almost any application with a number of Sage solutions and online payment processors.
Looking to purchase IMan, please see our resellers here.
Realisable Software
Ph: +44 (0) 208 123 1017
Copyright © Realisable. All rights reserved.
Realisable is a registered trademark
Realisable Software Ltd provides code-free, cost-effective applications integration solutions for SMEs. Our core IMan product is designed to integrate almost any application with a number of Sage solutions and online payment processors.
Looking to purchase IMan, please see our resellers here.
Realisable Software
Ph: +44 (0) 208 123 1017
Copyright © Realisable. All rights reserved.
Realisable is a registered trademark
Trying to understand why a job ran early in the morning, without a user triggering it, and without it having any schedule defined.
The job is not attached to a schedule in the user interface.
The job is not triggered via File Event.
Nor does it have a record in IMAN.dbo.SCHEDULES
Yet if I query the IMAN.dbo.AUDITLOG table for recent results for the job, I see clearly that the job was invoked today at 6:50:00 AM and a user received an email with results.
Since no user manually triggered the job, what could explain the job running spontaneously? Is there a server- or services-related explanation? Curious how to troubleshoot this.
There's nothing in Errors.txt for today, not that I would necessarily expect that.