Unable to access Autosys Job log files from WCC

[Anon Anon]

Hi,
Wondered if anyone else has come across this one before after installing an agent on Windows 2008 R2.

I have installed the Autosys Agent (11.3.0.138) under a user who is part of the Administrators group on the server and is also a Domain User. I can schedule jobs on the server and all the usual autoping -M <primary server> with the -S option and all work perfectly fine.

However when I access the Job Runs log via WCC (QVEIW) and select Standard Output I am unable to see the output.

Any ideas?

Brian

[RAMON FERRERIS]

How is your system defined, is the AE server/App Server unix or windows.
The user needs to exist on the AE server machine for it to use the
Qview/Qedit, plus you must have to have policies on the EEM side.

Also, if is that you can not see or you are getting an error message.


Thanks
Ramon




From: "CA Workload Automation (Distributed) Global User Community"
<[e-mail]>
To: "[e-mail]"
<[e-mail]>
Date: 09/10/2013 07:34 AM
Subject: [CA AutoSys Workload Automation General Discussion] Unable
to access Autosys Job log files from WCC



Hi,
Wondered if anyone else has come across this one before after installing
an agent on Windows 2008 R2.

I have installed the Autosys Agent (11.3.0.138) under a user who is part
of the Administrators group on the server and is also a Domain User. I can
schedule jobs on the server and all the usual autoping -M <primary server>
with the -S option and all work perfectly fine.

However when I access the Job Runs log via WCC (QVEIW) and select Standard
Output I am unable to see the output.

Any ideas?

Brian
Posted by:johnb546408
--
CA Communities Message Boards
101742777

[e-mail]
http://communities.ca.com


*************************** IMPORTANT
NOTE*****************************-- The opinions expressed in this
message and/or any attachments are those of the author and not
necessarily those of Brown Brothers Harriman & Co., its
subsidiaries and affiliates ("BBH"). There is no guarantee that
this message is either private or confidential, and it may have
been altered by unauthorized sources without your or our knowledge.
Nothing in the message is capable or intended to create any legally
binding obligations on either party and it is not intended to
provide legal advice. BBH accepts no responsibility for loss or
damage from its use, including damage from virus.
*******************************************************************************

[Anon Anon]

Hi Ramon,
The whole estate is a Windows Environment, AE runs on Windows. All the agents and the Scheduling server sofware is installed under a user that is a Domain Admin user and therefore has excess to do anything. Also I know EMM is not blocking access as it to is installed under the same user, the same user is also used to run batch jobs on the servers.

I was maybe thinkingthat it was a permissions issue on Windows 2008 R2 but I have disabled UAC so I know that is not causing it. I will have to have a dig round the logs see if I can see anything related.

Regards
Brian

[RAMON FERRERIS]

Ok, so are you using Active Directory or native security

For Ad the user needs to be able to use the same user id and password to
log into the machine, if using native, is the user defined in autosys
secure. Also, Under EEM make the user part of the commander group and see
if is working that way



Thanks
Ramon




From: "CA Workload Automation (Distributed) Global User Community"
<[e-mail]>
To: "[e-mail]"
<[e-mail]>
Date: 09/10/2013 08:11 AM
Subject: RE: Re: [CA AutoSys Workload Automation General
Discussion] Unable to acces



Hi Ramon,
The whole estate is a Windows Environment, AE runs on Windows. All the
agents and the Scheduling server sofware is installed under a user that is
a Domain Admin user and therefore has excess to do anything. Also I know
EMM is not blocking access as it to is installed under the same user, the
same user is also used to run batch jobs on the servers.

I was maybe thinkingthat it was a permissions issue on Windows 2008 R2 but
I have disabled UAC so I know that is not causing it. I will have to have
a dig round the logs see if I can see anything related.

Regards
Brian
Posted by:johnb546408
--
CA Communities Message Boards
101743732

[e-mail]
https://communities.ca.com


*************************** IMPORTANT
NOTE*****************************-- The opinions expressed in this
message and/or any attachments are those of the author and not
necessarily those of Brown Brothers Harriman & Co., its
subsidiaries and affiliates ("BBH"). There is no guarantee that
this message is either private or confidential, and it may have
been altered by unauthorized sources without your or our knowledge.
Nothing in the message is capable or intended to create any legally
binding obligations on either party and it is not intended to
provide legal advice. BBH accepts no responsibility for loss or
damage from its use, including damage from virus.
*******************************************************************************

[Daniel Shannon]

Another possible problem could be if the output is stored on a mapped drive or UNC share. It that's the case the agent may not have access to the output.