Arcana Development logo
Site Search:
  • Home
  • Products
    • Products Overview
    • adTempus
    • Report Commander
    • Arcana Scheduler
  • Support
    • Support Home
    • Knowledge Base
    • License Management
    • Contact Support
  • Community
  • Purchase
    • Pricing and Ordering
    • Additional Purchasing Information
  • Contact
  • About Us
  • Forum HelpHelp
  • Log In
  • Register

Community

Arcana Development Forums > Arcana Scheduler > General > Scheduled jobs in Arcana Scheduler are failing to start

General Discussion Scheduled jobs in Arcana Scheduler are failing to start RSS Feed Icon

You must be logged in to reply to this topic.

1
(Showing 1 to 2 of 2)
Avatar
Mohan
Joined: March 18, 2009
Posts: 1
Posted October 13, 2010 11:33:34 AM
 

HI,

I have few scheduled jobs run daily in Arcana Scheduler.

I have observed that sometimes these jobs do not kick off as per the scheduled time. It shows as 

 "failed to start" in status column of the scheduler. The symbol under the description column would appear with a red X mark.

Seeing this error, I have chekce dteh applicaiton log part of the event viewer. It showed me log for this program as  "Access is denied." . This is happening randomly and not to a any specific job.

When ever I get this problem, I go to task manger of the machine. I observe that there is a process called adsiumon.exe.  I used to kill this process manually and then start the job in Arcana. It then start running.

Cna you please advise me on how to fic this problem. This problem is happening intermittently and i am not able to control it. Every time, I am chekcing and killing adsiumon.exe process to prevent the jobs to go as "failed to start"

Can you pelase help me on this

Thanks

Mohan

 
Avatar
J.D.
Arcana Development Staff
Joined: September 23, 2007
Posts: 59
Posted October 19, 2010 10:44:40 AM
 

The adsiumon process is used by the Arcana Scheduler when it needs to detect and impersonate the interactive user. It's possible that the access denied error is happening when the scheduler tries to add interactive access for the logon session for the job.

If things appear to be working correctly when adsiumon is not running, you can disable adsiumon in one of two ways:

1) rename the executable so that it doesn't get launched, or

2) Look under Registry key "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run" and remove the entry for adsiumon. (This entry is what causes Windows to launch adsiumon when a user logs in. If you remove the entry, Windows will no longer start adsiumon.)


 
  Copyright 2012 Arcana Development, LLC. Use of this site signifies your agreement to the terms of use and privacy policy.