By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
428,899 Members | 1,230 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 428,899 IT Pros & Developers. It's quick & easy.

Scheduled Task odd behavior

P: 2
I have 2 .NET 4 console apps that I want to run as a scheduled tasks, but set up so that it does not need user logged in.

Both apps are nearly identical, and are reading Exchange inboxes via IMAP.

#1 copies attachments to a folder
#2 saves the body to a database, based on the subject line.

#1 is working perfectly, no problems.
#2 works fine when run manually, or when the task is set up to use the current user, and show the running window, but it does not do the work when it is set up as a task that can run when no user is logged in. I am using integrated security on the SQL connection. Could this be the problem?
Jun 6 '12 #1
Share this Question
Share on Google+
1 Reply


P: 2
To answer my own question:

DO NOT USE INTEGRATED SECURITY ON SCHEDULED TASK APPS.

You may want to create a special SQL user that has permission to update / insert / whatever you are doing in your app. But you will need to specify a user in the connection string.
Jun 6 '12 #2

Post your reply

Sign in to post your reply or Sign up for a free account.