cancel
Showing results for 
Search instead for 
Did you mean: 

Logon problems using process agent

Hywel_Mallett
Level 6
Certified

Hi all,

I've got a Windows batch script which I'm trying to get VCS to control using the process agent.

The batch script needs to run as a particular user, but when I try to online the resource I get the following error in the event log:

Source: AgentFramework

Event ID: 6532

Process:<<resource name>> Failed to launch the program <<path to batch script>>. Error = 1385

 When I look up that error code here, it shows as:

Logon failure: the user has not been granted the requested logon type at this computer.

So the user account in question can't log on. That user account already runs some services, and has been granted the Logon as a service right. I've also added the Log on as a batch job right, but the problem persists.

So what rights do I need to assign to that account so that VCS can start a batch script as that user?

 

The operating system is Windows Server 2003, and VCS is version 5.0.
1 ACCEPTED SOLUTION

Accepted Solutions

Wally_Heim
Level 6
Employee

Hi Hywel,

The process agent should be OK for what you want to do.  The Process agent does have a User, Password and Domain attributes to run the online,offline and monitor scripts (batch file are an acceptable formate along with perl files and executable files.)

The Process agent does not run as a service so that right is not going to work correctly and the Log on as a batch job I don't think, will work either.  I think you need ensure that you can log on directly to the console with the account and run the batch file.   I think you are missing the log on locally permission/right.

After you get the log on issue resolved, it sounds like you will then have issues with the monitor script.  If you are having problems please private message me and I will dig up a sample set of process agent scripts that you can use to call your batch file from that can handle the online, offline and monitor cycles as needed.

Thanks,

Wally

View solution in original post

3 REPLIES 3

Zahid_Haseeb
Level 6
Partner    VIP    Accredited

I think you are selecting wrong resource. You try the Application Resource. IN that resource you can also mention the User.

Wally_Heim
Level 6
Employee

Hi Hywel,

The process agent should be OK for what you want to do.  The Process agent does have a User, Password and Domain attributes to run the online,offline and monitor scripts (batch file are an acceptable formate along with perl files and executable files.)

The Process agent does not run as a service so that right is not going to work correctly and the Log on as a batch job I don't think, will work either.  I think you need ensure that you can log on directly to the console with the account and run the batch file.   I think you are missing the log on locally permission/right.

After you get the log on issue resolved, it sounds like you will then have issues with the monitor script.  If you are having problems please private message me and I will dig up a sample set of process agent scripts that you can use to call your batch file from that can handle the online, offline and monitor cycles as needed.

Thanks,

Wally

View solution in original post

armorbear1
Not applicable

You should use the correct resource.Currently the resource you are using may have some bugs.