Hello,

I have been trying to setup a VB.NET (.net 1.1) console application to run as an hourly job with version 3.4.26 of the 24x7 scheduler and keep running into the following error left in the job log:
"Logon failed. Return code: 1385 - Logon failure: the user has not been granted the requested logon type at this computer"

I have looked through these support forums and been unable to find information about this situation. After checking a search in Google, it looks like problems with Windows side. I've tried the Run As User option with both my local Administrator account for the machine that the scheduler runs on, as well as using my windows ID and entering the intranet domain (and my windows ID is in the Aministrators role on the machine). I've also tried leaving it as {Current User}. In all situations, the job errors out and will not run.

If you have any ideas of what I should look into, I would greatly appreciate advice or direction.

Thanks,
Seth

After more searching of the Forums, I found http://www.softtreetech.com/cgi_bin/sconfig.cgi?read=6409
Which had me setup the user that I put in the Run As setting as a "Log on as a batch job" user. Now I'm running into a different error:

"Create process failed. Return code: 1314 - A required priviledge is not held by the client."

My console application outputs logs statements to a text file. I'm assuming this means that my user logon, when logged on "as a batch job," does not have write permissions to allow the application to make that log text file.

Is this correct, or is it a different issue that I'm facing now? Thanks for any help or direction anyone can provide! I'll keep searching the forums...

: Hello,

: I have been trying to setup a VB.NET (.net 1.1) console application to run as
: an hourly job with version 3.4.26 of the 24x7 scheduler and keep running
: into the following error left in the job log: "Logon failed. Return
: code: 1385 - Logon failure: the user has not been granted the requested
: logon type at this computer"

: I have looked through these support forums and been unable to find
: information about this situation. After checking a search in Google, it
: looks like problems with Windows side. I've tried the Run As User option
: with both my local Administrator account for the machine that the
: scheduler runs on, as well as using my windows ID and entering the
: intranet domain (and my windows ID is in the Aministrators role on the
: machine). I've also tried leaving it as {Current User}. In all situations,
: the job errors out and will not run.

: If you have any ideas of what I should look into, I would greatly appreciate
: advice or direction.

: Thanks,
: Seth

You almost made it. Error 1385 indicated that the user for the process had not been granted "logon as a batch job". Now the user has this privilege.

Current error 1314 indicates that the either
1. The scheduler is able to logon the user, but then it is unable to start the specified process using that user's account. My guess is the specified process and files/directories are owned by you, not by the user whom you want to run the process.
2. The scheduler is still unable to logon the user because the scheduler account has not been granted "act as part of the operation system" privilege. My guess in this case you granted the required privileges but didn't restart (or logoff/logon) the computer after the change.

: After more searching of the Forums, I found
: http://www.softtreetech.com/cgi_bin/sconfig.cgi?read=6409
: Which had me setup the user that I put in the Run As setting as a "Log
: on as a batch job" user. Now I'm running into a different error:
: "Create process failed. Return code: 1314 - A required priviledge is
: not held by the client."

: My console application outputs logs statements to a text file. I'm assuming
: this means that my user logon, when logged on "as a batch job,"
: does not have write permissions to allow the application to make that log
: text file.

: Is this correct, or is it a different issue that I'm facing now? Thanks for
: any help or direction anyone can provide! I'll keep searching the
: forums...

Thanks for the Reply.

I've been working on the application again and have been running into a problem actually launching the application. The job executes and I no longer receive a return code error, which I was receiving yesterday. I moved from the 1385 error to the 1314 error. I receive neither of these now. I've added all the users I could think of to both the Logon as batch job and the Act as operating system security policies. I added my own username, the Local Service, the SERVICE, and SYSTEM.

Now I am receiving the following information once the job is run:

"Process finished with exit code 3762507597"

A quick search of the forums for the this code shows now one has had it before. A search of Google shows that it comes up with someone trying to do some work in Exchange 2003 with C#. This is not the case for me. I have commented ALL of the code out of my application at this point except for a very basic call to write out a string to a text file. The job executes, sends me an email that is has started, and then sends and email that it has finished.

When I check the job log, I find that statement about the exit code. Does anyone have ideas of what I should look into?

Thanks very much for the help,
Seth

: You almost made it. Error 1385 indicated that the user for the process had
: not been granted "logon as a batch job". Now the user has this
: privilege.

: Current error 1314 indicates that the either
: 1. The scheduler is able to logon the user, but then it is unable to start
: the specified process using that user's account. My guess is the specified
: process and files/directories are owned by you, not by the user whom you
: want to run the process.
: 2. The scheduler is still unable to logon the user because the scheduler
: account has not been granted "act as part of the operation
: system" privilege. My guess in this case you granted the required
: privileges but didn't restart (or logoff/logon) the computer after the
: change.

This is just a warning that your process complets with non-zero exit code. If you think everything is working you can ignore it. If you want to suppress the warning place the command line into an bat file and at the end of bat file add "exit(0)"

: Thanks for the Reply.

: I've been working on the application again and have been running into a
: problem actually launching the application. The job executes and I no
: longer receive a return code error, which I was receiving yesterday. I
: moved from the 1385 error to the 1314 error. I receive neither of these
: now. I've added all the users I could think of to both the Logon as batch
: job and the Act as operating system security policies. I added my own
: username, the Local Service, the SERVICE, and SYSTEM.

: Now I am receiving the following information once the job is run:
: "Process finished with exit code 3762507597"

: A quick search of the forums for the this code shows now one has had it
: before. A search of Google shows that it comes up with someone trying to
: do some work in Exchange 2003 with C#. This is not the case for me. I have
: commented ALL of the code out of my application at this point except for a
: very basic call to write out a string to a text file. The job executes,
: sends me an email that is has started, and then sends and email that it
: has finished.

: When I check the job log, I find that statement about the exit code. Does
: anyone have ideas of what I should look into?

: Thanks very much for the help,
: Seth

Thanks for the help. I don't know exactly what fixed everything... I started over and recoded the application in a new project and it worked with all the same job settings just pointing at the newly created project. I guess the project was corrupted in some way. Glad to have it working now! Thanks

: This is just a warning that your process complets with non-zero exit code. If
: you think everything is working you can ignore it. If you want to suppress
: the warning place the command line into an bat file and at the end of bat
: file add "exit(0)"