Accessing execution agent failed

Hi!
I'm using Oracle 10g XE on linux. When I want execute any scheduler jobs get everytime the following error message:
ORA-27370: job slave failed to launch a job of type EXECUTABLE
ORA-27300: OS system dependent operation:accessing execution agent failed with status: 2
ORA-27301: OS failure message: No such file or directory
ORA-27302: failure occurred at: sjsec 3
The user privileges and owner of the extjob is set correctly.
The script runs on other servers without errors (on LINUX and WINDOWS too, but on 10g Enterprise Ed.).
This error seems to be the 'OracleJobScheduler service not runnig' in case of Windows, but here is no service. I could generate this problem by hand with renaming the extjob file in a goodworking system.
Could anyone help me in this problem? Why can't the oracle process see the extjob file?
Thanks for help
nmsAkos

Hi,
What schema are you running the jobs in ?
In the SYS schema, the Scheduler uses the extjobo executable to execute jobs but I think on XE this executable might be missing so jobs in the SYS schema would be expected to throw this error.
You could fix this by simply doing something like
cp extjob extjobo
chmod 0755 extjobo
Or you could grant create job (and possibly create external job) to a regular user and have the user create the external job. I believe that in XE by default extjob is not setuid so all jobs would run as the oracle user. This may have security implications.
If this doesn't help could you say what schema you are running the jobs in and give the output of "ls -l extjob*" in the oracle bin directory.
Hope this helps,
Ravi.

Similar Messages

  • Sqlserver agent fails to execute the job

    Hi Team,
    Usually i am getting error with sqlserver agent job schedule with different errors for ssis package execution but manual execution of job getting fine for execution.
    Regards,
    Sarath

    Executed as user: CITRITE\svcacct_sqlappsprod. Started:  4:01:12 AM  Finished: 4:32:51 AM  Elapsed:  1899.48 seconds.  The package execution failed.  The step failed.
     Description: Failed to decrypt protected XML node "ServerPassword" with error 0x8009000B "Key not valid for use in specified state.". You may not be authorized to access this information. This error occurs when there is a cryptographic
    error. Verify that the correct key is available
    after getting error when we run the job with just right click on job and select run job st step 1 and then it is fine running.
    Regards,
    Kumar
    That's something related to Protection Level of SSIS Packages.
    Please refer similar thread and check reply by Wendy Fu. Hope that helps.
    https://social.msdn.microsoft.com/Forums/sqlserver/en-US/8df90455-19ea-449e-b80d-5590deb4fecb/sql-server-agent-failed-to-decrypt-protected-xml-node?forum=sqlintegrationservices
    Cheers,
    Vaibhav Chaudhari
    [MCP],
    [MCTS], [MCSA-SQL2012]

  • How to access different Agent from differnt schema in ODI?

    Hi,
    I am new in ODI and doing some practical assignment related to ODI agent.
    here on one system i.e. 198.168.100.22 my colleague install ODI and  another system 198.168.100.21 I also have installed ODI this is my system with different schema of each.
    We also have created standalone agent of each system and Test successfully. We run so many session with this standalone agent.
    Now we have to configure his agent in my system and vice-a-verse, he also configure my agent to his system.
    we try tried it but for my agent , the Test is SUCCESSFUL but when I created another agent with the same name & his hostname the Test is fail.
    Please anybody suggest us how would I access his agent in my system & test successfully(Work Successfully).
    Thanks

    ODI-1424: Agent host or port cannot be reached using http://192.168.100.29:20910/oraclediagent.
    Here, the IP(100.29) in URL looks different than 2 IPs' that you have specified above. 
    Also, In topology, the ODI agent should be configured with hostname where ODI Standalone Agent is installed.
    will create only one Master Repository and under that will create the 2 work repository
      Yes, this sounds good.
    Regards,
    Santy

  • The distribution agent failed to create temporary files in 'C:\Program Files\Microsoft SQL Server\110\COM' directory. System returned errorcode 5.

    One of my replication job failed with below error, which means job failed because of permission issue on the folder. To resolve that, I have granted the permission and it started working fine. Now the question is as my job was running fine since long time
    without any issue then how suddenly the permission of the folder got omitted automatically? I am sure that no one deleted the permission from the folder and as the server is part of SQL cluster no failover occurs.
    Error:-The distribution agent failed to create temporary files in 'C:\Program Files\Microsoft SQL Server\110\COM' directory. System returned errorcode 5.
    Rahul

    Hi Rahul,
    Error code 5 indicates that the error is "access is denied."  Please make sure that the COM folder is excluded from any antivirus scan that occurs on the system.
    If the issue still persists, I recommend you use
    Process Monitor to find out a bit more about the accounts and access requests involved. Then grant write permission to the exact COM folder for the account that is running the SQL Server Agent service. For more details, please review the following similar
    thread.
    http://www.sqlservercentral.com/Forums/Topic1364832-1550-1.aspx
    Thanks,
    Lydia Zhang
    If you have any feedback on our support, please click
    here.

  • Distribution agent failed to create temporary files in

    Hello,
    we are configured transnational replication in sql server 2005 location, all replication jobs are running fine,
    while we checking sql server errorlog showing below error :
    Distribution agent failed to create temporary files in  'C:\Program Files\Microsoft SQL Server\100\COM' directory. System returned errorcode 5.
    NOte: normally we are configured replication 2005 [90] , but while see the above error it shows [100] comparability level . 

    Hi,
    If the account that is running SQL Server Agent does not have write access to the COM folder, the Distribution Agent will fail
    when it is running as a job. If you run the Distribution Agent from a command line by using an account that does not have write access to the COM folder, the same failure will occur.
    To work around this
    issue, grant write permissions to the COM folder for the account that is running the SQL Server Agent service. If you run the Distribution Agent from a command line, grant write permissions to the COM folder for the account that you use to run the Distribution
    Agent.
    For more information, please go through the below URL:
    http://support.microsoft.com/kb/956032/en-us  

  • PeopleTools 8.22.19 Upgrade : Distribution Agent fails to distribute

    After we upgraded our People Tools from 8.20.13 to 8.22.19, the distribution agent fails to distribute reports. Does anyone have similar experiences before or any know solutions? Please share here.

    Elvis,
    Did you change the hardware ? If so, then did you checked the existence of the report repository and write access ?
    Did you (re)checked the report node definition ? Is it still valid ?
    What error did you got from the process scheduler log file ?
    Nicolas.

  • Exchange 2010 MP : Some Client Access test cmdlets failed to run

    Hi all,
    This error is triggered in SCOM 2012 R2 about a single Exchange 2010 SP3 server :
    Exchange 2010 MP : Some Client Access test cmdlets failed to run.
    When I dig into the error context, I can see it's about the cmdlet "Test-CalendarConnectivity -TestType:External".
    The TechNet
    https://technet.microsoft.com/en-us/library/hh377605(v=exchg.140).aspx proposes to verify that the URL for the external virtual directory can be accessed by running the Test-OwaConnectivity.
    OK.
    But what sould I specify for the parameter -MailBoxCredential required for Test-OwaConnectivity -URL my_url -MailBoxCredential ?
    Thank you.
    Have a good day.
    FXE

    Hi,
    Under Administration, run as configuration, profiles, you can check Default action account.
    Local system is the account account for agents by default, you can change to use another account.
    Regards,
    Yan Li
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

  • Too  Slow - Domino 6.5.4  with access manager agent 2.2 ?

    I don't know how to tune Domino 6.5.4 with access manager agent 2.2?
    I think AMAgent.properties is not good for SSO.
    Please help me to tune it.
    # $Id: AMAgent.properties,v 1.103 2005/09/19 22:08:34 madan Exp $
    # Copyright ? 2002 Sun Microsystems, Inc. All rights reserved.
    # U.S. Government Rights - Commercial software. Government users are
    # subject to the Sun Microsystems, Inc. standard license agreement and
    # applicable provisions of the FAR and its supplements. Use is subject to
    # license terms. Sun, Sun Microsystems, the Sun logo and Sun ONE are
    # trademarks or registered trademarks of Sun Microsystems, Inc. in the
    # U.S. and other countries.
    # Copyright ? 2002 Sun Microsystems, Inc. Tous droits r閟erv閟.
    # Droits du gouvernement am閞icain, utlisateurs gouvernmentaux - logiciel
    # commercial. Les utilisateurs gouvernmentaux sont soumis au contrat de
    # licence standard de Sun Microsystems, Inc., ainsi qu aux dispositions en
    # vigueur de la FAR [ (Federal Acquisition Regulations) et des suppl閙ents
    # ? celles-ci.
    # Distribu? par des licences qui en restreignent l'utilisation. Sun, Sun
    # Microsystems, le logo Sun et Sun ONE sont des marques de fabrique ou des
    # marques d閜os閑s de Sun Microsystems, Inc. aux Etats-Unis et dans
    # d'autres pays.
    # The syntax of this file is that of a standard Java properties file,
    # see the documentation for the java.util.Properties.load method for a
    # complete description. (CAVEAT: The SDK in the parser does not currently
    # support any backslash escapes except for wrapping long lines.)
    # All property names in this file are case-sensitive.
    # NOTE: The value of a property that is specified multiple times is not
    # defined.
    # WARNING: The contents of this file are classified as an UNSTABLE
    # interface by Sun Microsystems, Inc. As such, they are subject to
    # significant, incompatible changes in any future release of the
    # software.
    # The name of the cookie passed between the Access Manager
    # and the SDK.
    # WARNING: Changing this property without making the corresponding change
    # to the Access Manager will disable the SDK.
    com.sun.am.cookie.name = iPlanetDirectoryPro
    # The URL for the Access Manager Naming service.
    com.sun.am.naming.url = http://sportal.yjy.dqyt.petrochina:80/amserver/namingservice
    # The URL of the login page on the Access Manager.
    com.sun.am.policy.am.login.url = http://sportal.yjy.dqyt.petrochina:80/amserver/UI/Login
    # Name of the file to use for logging messages.
    com.sun.am.policy.agents.config.local.log.file = c:/Sun/Access_Manager/Agents/2.2/debug/C__Lotus_Domino/amAgent
    # This property is used for Log Rotation. The value of the property specifies
    # whether the agent deployed on the server supports the feature of not. If set
    # to false all log messages are written to the same file.
    com.sun.am.policy.agents.config.local.log.rotate = true
    # Name of the Access Manager log file to use for logging messages to
    # Access Manager.
    # Just the name of the file is needed. The directory of the file
    # is determined by settings configured on the Access Manager.
    com.sun.am.policy.agents.config.remote.log = amAuthLog.Dominoad.yjy.dqyt.petrochina.80
    # Set the logging level for the specified logging categories.
    # The format of the values is
    #     <ModuleName>[:<Level>][,<ModuleName>[:<Level>]]*
    # The currently used module names are: AuthService, NamingService,
    # PolicyService, SessionService, PolicyEngine, ServiceEngine,
    # Notification, PolicyAgent, RemoteLog and all.
    # The all module can be used to set the logging level for all currently
    # none logging modules. This will also establish the default level for
    # all subsequently created modules.
    # The meaning of the 'Level' value is described below:
    #     0     Disable logging from specified module*
    #     1     Log error messages
    #     2     Log warning and error messages
    #     3     Log info, warning, and error messages
    #     4     Log debug, info, warning, and error messages
    #     5     Like level 4, but with even more debugging messages
    # 128     log url access to log file on AM server.
    # 256     log url access to log file on local machine.
    # If level is omitted, then the logging module will be created with
    # the default logging level, which is the logging level associated with
    # the 'all' module.
    # for level of 128 and 256, you must also specify a logAccessType.
    # *Even if the level is set to zero, some messages may be produced for
    # a module if they are logged with the special level value of 'always'.
    com.sun.am.log.level =
    # The org, username and password for Agent to login to AM.
    com.sun.am.policy.am.username = UrlAccessAgent
    com.sun.am.policy.am.password = LYnKyOIgdWt404ivWY6HPQ==
    # Name of the directory containing the certificate databases for SSL.
    com.sun.am.sslcert.dir = c:/Sun/Access_Manager/Agents/2.2/domino/cert
    # Set this property if the certificate databases in the directory specified
    # by the previous property have a prefix.
    com.sun.am.certdb.prefix =
    # Should agent trust all server certificates when Access Manager
    # is running SSL?
    # Possible values are true or false.
    com.sun.am.trust_server_certs = true
    # Should the policy SDK use the Access Manager notification
    # mechanism to maintain the consistency of its internal cache? If the value
    # is false, then a polling mechanism is used to maintain cache consistency.
    # Possible values are true or false.
    com.sun.am.notification.enable = true
    # URL to which notification messages should be sent if notification is
    # enabled, see previous property.
    com.sun.am.notification.url = http://Dominoad.yjy.dqyt.petrochina:80/amagent/UpdateAgentCacheServlet?shortcircuit=false
    # This property determines whether URL string case sensitivity is
    # obeyed during policy evaluation
    com.sun.am.policy.am.url_comparison.case_ignore = true
    # This property determines the amount of time (in minutes) an entry
    # remains valid after it has been added to the cache. The default
    # value for this property is 3 minutes.
    com.sun.am.policy.am.polling.interval=3
    # This property allows the user to configure the User Id parameter passed
    # by the session information from the access manager. The value of User
    # Id will be used by the agent to set the value of REMOTE_USER server
    # variable. By default this parameter is set to "UserToken"
    com.sun.am.policy.am.userid.param=UserToken
    # Profile attributes fetch mode
    # String attribute mode to specify if additional user profile attributes should
    # be introduced into the request. Possible values are:
    # NONE - no additional user profile attributes will be introduced.
    # HTTP_HEADER - additional user profile attributes will be introduced into
    # HTTP header.
    # HTTP_COOKIE - additional user profile attributes will be introduced through
    # cookies.
    # If not within these values, it will be considered as NONE.
    com.sun.am.policy.agents.config.profile.attribute.fetch.mode=NONE
    # The user profile attributes to be added to the HTTP header. The
    # specification is of the format ldap_attribute_name|http_header_name[,...].
    # ldap_attribute_name is the attribute in data store to be fetched and
    # http_header_name is the name of the header to which the value needs
    # to be assigned.
    # NOTE: In most cases, in a destination application where a "http_header_name"
    # shows up as a request header, it will be prefixed by HTTP_, and all
    # lower case letters will become upper case, and any - will become _;
    # For example, "common-name" would become "HTTP_COMMON_NAME"
    com.sun.am.policy.agents.config.profile.attribute.map=cn|common-name,ou|organizational-unit,o|organization,mail|email,employeenumber|employee-
    number,c|country
    # Session attributes mode
    # String attribute mode to specify if additional user session attributes should
    # be introduced into the request. Possible values are:
    # NONE - no additional user session attributes will be introduced.
    # HTTP_HEADER - additional user session attributes will be introduced into HTTP header.
    # HTTP_COOKIE - additional user session attributes will be introduced through cookies.
    # If not within these values, it will be considered as NONE.
    com.sun.am.policy.agents.config.session.attribute.fetch.mode=NONE
    # The session attributes to be added to the HTTP header. The specification is
    # of the format session_attribute_name|http_header_name[,...].
    # session_attribute_name is the attribute in session to be fetched and
    # http_header_name is the name of the header to which the value needs to be
    # assigned.
    # NOTE: In most cases, in a destination application where a "http_header_name"
    # shows up as a request header, it will be prefixed by HTTP_, and all
    # lower case letters will become upper case, and any - will become _;
    # For example, "common-name" would become "HTTP_COMMON_NAME"
    com.sun.am.policy.agents.config.session.attribute.map=
    # Response Attribute Fetch Mode
    # String attribute mode to specify if additional user response attributes should
    # be introduced into the request. Possible values are:
    # NONE - no additional user response attributes will be introduced.
    # HTTP_HEADER - additional user response attributes will be introduced into
    # HTTP header.
    # HTTP_COOKIE - additional user response attributes will be introduced through
    # cookies.
    # If not within these values, it will be considered as NONE.
    com.sun.am.policy.agents.config.response.attribute.fetch.mode=NONE
    # The response attributes to be added to the HTTP header. The specification is
    # of the format response_attribute_name|http_header_name[,...].
    # response_attribute_name is the attribute in policy response to be fetched and
    # http_header_name is the name of the header to which the value needs to be
    # assigned.
    # NOTE: In most cases, in a destination application where a "http_header_name"
    # shows up as a request header, it will be prefixed by HTTP_, and all
    # lower case letters will become upper case, and any - will become _;
    # For example, "common-name" would become "HTTP_COMMON_NAME"
    com.sun.am.policy.agents.config.response.attribute.map=
    # The cookie name used in iAS for sticky load balancing
    com.sun.am.policy.am.lb.cookie.name = GX_jst
    # indicate where a load balancer is used for Access Manager
    # services.
    # true | false
    com.sun.am.load_balancer.enable = false
    ####Agent Configuration####
    # this is for product versioning, please do not modify it
    com.sun.am.policy.agents.config.version=2.2
    # Set the url access logging level. the choices are
    # LOG_NONE - do not log user access to url
    # LOG_DENY - log url access that was denied.
    # LOG_ALLOW - log url access that was allowed.
    # LOG_BOTH - log url access that was allowed or denied.
    com.sun.am.policy.agents.config.audit.accesstype = LOG_DENY
    # Agent prefix
    com.sun.am.policy.agents.config.agenturi.prefix = http://Dominoad.yjy.dqyt.petrochina:80/amagent
    # Locale setting.
    com.sun.am.policy.agents.config.locale = en_US
    # The unique identifier for this agent instance.
    com.sun.am.policy.agents.config.instance.name = unused
    # Do SSO only
    # Boolean attribute to indicate whether the agent will just enforce user
    # authentication (SSO) without enforcing policies (authorization)
    com.sun.am.policy.agents.config.do_sso_only = true
    # The URL of the access denied page. If no value is specified, then
    # the agent will return an HTTP status of 403 (Forbidden).
    com.sun.am.policy.agents.config.accessdenied.url =
    # This property indicates if FQDN checking is enabled or not.
    com.sun.am.policy.agents.config.fqdn.check.enable = true
    # Default FQDN is the fully qualified hostname that the users should use
    # in order to access resources on this web server instance. This is a
    # required configuration value without which the Web server may not
    # startup correctly.
    # The primary purpose of specifying this property is to ensure that if
    # the users try to access protected resources on this web server
    # instance without specifying the FQDN in the browser URL, the Agent
    # can take corrective action and redirect the user to the URL that
    # contains the correct FQDN.
    # This property is set during the agent installation and need not be
    # modified unless absolutely necessary to accommodate deployment
    # requirements.
    # WARNING: Invalid value for this property can result in the Web Server
    # becoming unusable or the resources becoming inaccessible.
    # See also: com.sun.am.policy.agents.config.fqdn.check.enable,
    # com.sun.am.policy.agents.config.fqdn.map
    com.sun.am.policy.agents.config.fqdn.default = Dominoad.yjy.dqyt.petrochina
    # The FQDN Map is a simple map that enables the Agent to take corrective
    # action in the case where the users may have typed in an incorrect URL
    # such as by specifying partial hostname or using an IP address to
    # access protected resources. It redirects the browser to the URL
    # with fully qualified domain name so that cookies related to the domain
    # are received by the agents.
    # The format for this property is:
    # com.sun.am.policy.agents.config.fqdn.map = [invalid_hostname|valid_hostname][,...]
    # This property can also be used so that the agents use the name specified
    # in this map instead of the web server's actual name. This can be
    # accomplished by doing the following.
    # Say you want your server to be addressed as xyz.hostname.com whereas the
    # actual name of the server is abc.hostname.com. The browsers only knows
    # xyz.hostname.com and you have specified polices using xyz.hostname.com at
    # the Access Manager policy console, in this file set the mapping as
    # com.sun.am.policy.agents.fqdn.map = valid|xyz.hostname.com
    # Another example is if you have multiple virtual servers say rst.hostname.com,
    # uvw.hostname.com and xyz.hostname.com pointing to the same actual server
    # abc.hostname.com and each of the virtual servers have their own policies
    # defined, then the fqdnMap should be defined as follows:
    # com.sun.am.policy.agents.fqdn.map = valid1|rst.hostname.com,valid2|uvw.hostname.com,valid3|xyz.hostname.com
    # WARNING: Invalid value for this property can result in the Web Server
    # becoming unusable or the resources becoming inaccessible.
    com.sun.am.policy.agents.config.fqdn.map =
    # Cookie Reset
    # This property must be set to true, if this agent needs to
    # reset cookies in the response before redirecting to
    # Access Manager for Authentication.
    # By default this is set to false.
    # Example : com.sun.am.policy.agents.config.cookie.reset.enable=true
    com.sun.am.policy.agents.config.cookie.reset.enable=false
    # This property gives the comma separated list of Cookies, that
    # need to be included in the Redirect Response to Access Manager.
    # This property is used only if the Cookie Reset feature is enabled.
    # The Cookie details need to be specified in the following Format
    # name[=value][;Domain=value]
    # If "Domain" is not specified, then the default agent domain is
    # used to set the Cookie.
    # Example : com.sun.am.policy.agents.config.cookie.reset.list=LtpaToken,
    # token=value;Domain=subdomain.domain.com
    com.sun.am.policy.agents.config.cookie.reset.list=
    # This property gives the space separated list of domains in
    # which cookies have to be set in a CDSSO scenario. This property
    # is used only if CDSSO is enabled.
    # If this property is left blank then the fully qualified cookie
    # domain for the agent server will be used for setting the cookie
    # domain. In such case it is a host cookie instead of a domain cookie.
    # Example : com.sun.am.policy.agents.config.cookie.domain.list=.sun.com .iplanet.com
    com.sun.am.policy.agents.config.cookie.domain.list=
    # user id returned if accessing global allow page and not authenticated
    com.sun.am.policy.agents.config.anonymous_user=anonymous
    # Enable/Disable REMOTE_USER processing for anonymous users
    # true | false
    com.sun.am.policy.agents.config.anonymous_user.enable=false
    # Not enforced list is the list of URLs for which no authentication is
    # required. Wildcards can be used to define a pattern of URLs.
    # The URLs specified may not contain any query parameters.
    # Each service have their own not enforced list. The service name is suffixed
    # after "# com.sun.am.policy.agents.notenforcedList." to specify a list
    # for a particular service. SPACE is the separator between the URL.
    com.sun.am.policy.agents.config.notenforced_list = http://dominoad.yjy.dqyt.petrochina/*.nsf http://dominoad.yjy.dqyt.petrochina/teamroom.nsf/TROutline.gif?
    OpenImageResource http://dominoad.yjy.dqyt.petrochina/icons/*.gif
    # Boolean attribute to indicate whether the above list is a not enforced list
    # or an enforced list; When the value is true, the list means enforced list,
    # or in other words, the whole web site is open/accessible without
    # authentication except for those URLs in the list.
    com.sun.am.policy.agents.config.notenforced_list.invert = false
    # Not enforced client IP address list is a list of client IP addresses.
    # No authentication and authorization are required for the requests coming
    # from these client IP addresses. The IP address must be in the form of
    # eg: 192.168.12.2 1.1.1.1
    com.sun.am.policy.agents.config.notenforced_client_ip_list =
    # Enable POST data preservation; By default it is set to false
    com.sun.am.policy.agents.config.postdata.preserve.enable = false
    # POST data preservation : POST cache entry lifetime in minutes,
    # After the specified interval, the entry will be dropped
    com.sun.am.policy.agents.config.postcache.entry.lifetime = 10
    # Cross-Domain Single Sign On URL
    # Is CDSSO enabled.
    com.sun.am.policy.agents.config.cdsso.enable=false
    # This is the URL the user will be redirected to for authentication
    # in a CDSSO Scenario.
    com.sun.am.policy.agents.config.cdcservlet.url =
    # Enable/Disable client IP address validation. This validate
    # will check if the subsequent browser requests come from the
    # same ip address that the SSO token is initially issued against
    com.sun.am.policy.agents.config.client_ip_validation.enable = false
    # Below properties are used to define cookie prefix and cookie max age
    com.sun.am.policy.agents.config.profile.attribute.cookie.prefix = HTTP_
    com.sun.am.policy.agents.config.profile.attribute.cookie.maxage = 300
    # Logout URL - application's Logout URL.
    # This URL is not enforced by policy.
    # if set, agent will intercept this URL and destroy the user's session,
    # if any. The application's logout URL will be allowed whether or not
    # the session destroy is successful.
    com.sun.am.policy.agents.config.logout.url=
    #http://sportal.yjy.dqyt.petrochina/amserver/UI/Logout
    # Any cookies to be reset upon logout in the same format as cookie_reset_list
    com.sun.am.policy.agents.config.logout.cookie.reset.list =
    # By default, when a policy decision for a resource is needed,
    # agent gets and caches the policy decision of the resource and
    # all resource from the root of the resource down, from the Access Manager.
    # For example, if the resource is http://host/a/b/c, the the root of the
    # resource is http://host/. This is because more resources from the
    # same path are likely to be accessed subsequently.
    # However this may take a long time the first time if there
    # are many many policies defined under the root resource.
    # To have agent get and cache the policy decision for the resource only,
    # set the following property to false.
    com.sun.am.policy.am.fetch_from_root_resource = true
    # Whether to get the client's hostname through DNS reverse lookup for use
    # in policy evaluation.
    # It is true by default, if the property does not exist or if it is
    # any value other than false.
    com.sun.am.policy.agents.config.get_client_host_name = false
    # The following property is to enable native encoding of
    # ldap header attributes forwarded by agents. If set to true
    # agent will encode the ldap header value in the default
    # encoding of OS locale. If set to false ldap header values
    # will be encoded in UTF-8
    com.sun.am.policy.agents.config.convert_mbyte.enable = false
    #When the not enforced list or policy has a wildcard '*' character, agent
    #strips the path info from the request URI and uses the resulting request
    #URI to check against the not enforced list or policy instead of the entire
    #request URI, in order to prevent someone from getting access to any URI by
    #simply appending the matching pattern in the policy or not enforced list.
    #For example, if the not enforced list has the value http://host/*.gif,
    #stripping the path info from the request URI will prevent someone from
    #getting access to http://host/index.html by using the URL http://host/index.html?hack.gif.
    #However when a web server (for exmample apache) is configured to be a reverse
    #proxy server for a J2EE application server, path info is interpreted in a different
    #manner since it maps to a resource on the proxy instead of the app server.
    #This prevents the not enforced list or policy from being applied to part of
    #the URI below the app serverpath if there is a wildcard character. For example,
    #if the not enforced list has value http://host/webapp/servcontext/* and the
    #request URL is http://host/webapp/servcontext/example.jsp the path info
    #is /servcontext/example.jsp and the resulting request URL with path info stripped
    #is http://host/webapp, which will not match the not enforced list. By setting the
    #following property to true, the path info will not be stripped from the request URL
    #even if there is a wild character in the not enforced list or policy.
    #Be aware though that if this is set to true there should be nothing following the
    #wildcard character '*' in the not enforced list or policy, or the
    #security loophole described above may occur.
    com.sun.am.policy.agents.config.ignore_path_info = false
    # Override the request url given by the web server with
    # the protocol, host or port of the agent's uri specified in
    # the com.sun.am.policy.agents.agenturiprefix property.
    # These may be needed if the agent is sitting behind a ssl off-loader,
    # load balancer, or proxy, and either the protocol (HTTP scheme),
    # hostname, or port of the machine in front of agent which users go through
    # is different from the agent's protocol, host or port.
    com.sun.am.policy.agents.config.override_protocol =
    com.sun.am.policy.agents.config.override_host =
    com.sun.am.policy.agents.config.override_port =
    # Override the notification url in the same way as other request urls.
    # Set this to true if any one of the override properties above is true,
    # and if the notification url is coming through the proxy or load balancer
    # in the same way as other request url's.
    com.sun.am.policy.agents.config.override_notification.url =
    # The following property defines how long to wait in attempting
    # to connect to an Access Manager AUTH server.
    # The default value is 2 seconds. This value needs to be increased
    # when receiving the error "unable to find active Access Manager Auth server"
    com.sun.am.policy.agents.config.connection_timeout =
    # Time in milliseconds the agent will wait to receive the
    # response from Access Manager. After the timeout, the connection
    # will be drop.
    # A value of 0 means that the agent will wait until receiving the response.
    # WARNING: Invalid value for this property can result in
    # the resources becoming inaccessible.
    com.sun.am.receive_timeout = 0
    # The three following properties are for IIS6 agent only.
    # The two first properties allow to set a username and password that will be
    # used by the authentication filter to pass the Windows challenge when the Basic
    # Authentication option is selected in Microsoft IIS 6.0. The authentication
    # filter is named amiis6auth.dll and is located in
    # Agent_installation_directory/iis6/bin. It must be installed manually on
    # the web site ("ISAPI Filters" tab in the properties of the web site).
    # It must also be uninstalled manually when unintalling the agent.
    # The last property defines the full path for the authentication filter log file.
    com.sun.am.policy.agents.config.iis6.basicAuthentication.username =
    com.sun.am.policy.agents.config.iis6.basicAuthentication.password =
    com.sun.am.policy.agents.config.iis6.basicAuthentication.logFile = c:/Sun/Access_Manager/Agents/2.2/debug/C__Lotus_Domino/amAuthFilter

    Hi,
    I installed opensso (so Sun Java(TM) System Access Manager 7.5) and the agent for Domino 6.5.4 and I have the message in logs "amAgent"
    2007-07-11 18:40:16.119 Error 1708:3dbcf768 PolicyAgent: render_response(): Entered.
    I have the box to identify but it doesnot connect me on my opensso server.
    It still identify with Domino's server
    Thanks for your response
    Thomas

  • Generation of access report CNRCRMPRCUST999 failed.

    Dear Gurus,
             I’ve createe one pricing condition table in Dev environment and now I’m trying to transport it in Quality environment. This table is for CRM only.
    In development every thing working fine but while transporting in Quality I got the error "Generation of access report CNRCRMPRCUST999 failed." And I am Unable to maintain records for the respective condition type I got the error "There are no maximum generated tables for condition type ZXXX".
    Please help....
    Regards,
    Biplab

    Hello Singa,
    For the error;." there is no entry in the object directory (TADIR) for R3TR TTYP /1CR/RCBSAP017_T"
    This mean that Table 017 in R3 is for Application 'M' (Purchasing for Pricing 'A') which is not revelant for download to CRM. If you see the download object DNL_CUST_CNDALL, filters for T681 are on Application V, TX (KAPPL). In the R3 side in T681, have 2 entries for KAPPL= V, and the usage's are E (Rebate) and N (Free Goods). So this might be the reason why it has come to CRM. The relevant tables in CRM for the above are /1CN/CCBSAP017 and /1CN/CCFSAP017. If you see /SAPCND/T681
    table for these 2 entries, GESTA field has '5', meaning the tables are downloaded. However, these tables are not used in any free goods condition types or rebate condition types/access sequences in CRM and R3. So I think this table is not being used for rebates and free goods, you can also check the corresponding tables in R3, KOTE017 and KOTN017, which have 0 entries
    which indicate that they are not in use, so we can ignore this error.
    IPlease also check note 1003793. and restart the customizing download DNL_CUST_CNDALL.
    thanks
    willie

  • Agents failing when sent as attachments (pdf or excel) in OBIEE 11g

    Hello,
    We have issue agents failing with following error when set up with attachment (pdf or excel only) either as Dashboard or Report. If the same agent is run as inline then the agent is working fine. OBIEE version is 11.1.1.6.0 unclustered.
    [nQSError: 77006] Oracle BI Presentation Server Error: A fatal error occurred while processing the request. The server responded with: A fatal error occurred while processing the request. The server responded with: java.io.IOException: The system cannot find the path specified.
    Error Codes: AGEGTYVF
    Location: saw.rpc.mis.read, saw.subsystem.portal.pdf, saw.delivers.rpc.getDeviceContent, saw.rpc.server.responder, saw.rpc.server, saw.rpc.server.handleConnection, saw.rpc.server.dispatch, saw.threadpool.socketrpcserver, saw.threads
    We tried logging in as user/Administrator and running the report from catalog without any error. Also strangely this is evident in only a specific environment. Not sure what is causing the issue.
    Please advise.
    Thanks

    What is the size of the attachments of reports you are trying to send thru Agents .? either PDF or EXCEL ?
    What does you JavaHost log .?
    I think this is a same Bug 14680611 : ERROR CODES: AGEGTYVF RUNNING AGENTS WITH LARGE REPORT AS EXCEL ATTACHMENT
    If your are not able to download even smaller attachments/reports then, I would raise an SR with Oracle.
    Let us know. Hope this Helps.!
    Thanks,
    SVS

  • Why call between WebClient agents fails?

    Hi,
    I have just recently installed the mySAP CRM 4.0 IC WebClient (CRM40 SP00).
    I have been testing the installation with CCS (Contact Center Simulator) and for a basic CCS supported tests (Inbound Phone call, Outbound Phone call, Chat) everything seems to be ok, but a call between WebClient agents fails due to an java error. The Phone Call between WebClients which should work according the CCS webpage.
    What should I do to get WebClient agents to call each others? Any configuration or customization tips? Note that I do not have CC integration in place, just the IC WebClients.
    Here is the test done in details and the error reported by WebClient:
    0) I restarted SAP CRM to be sure no pending sessions exists
    1) Open the CCS to see that no agents are logged in with WebClient
    2) Login as java_ic with WebClient
    3) CCS shows java_ic Workmode (=status) as 'Not Ready'
    4) Switch java_ic to ready by from the WebClient
    5) CCS shows java_ic Workmode (=status) as 'Ready'
    Then I do the same for agent 'sap*' with another MSIE browser window. At this point, the CCS shows Workmode for both agents as 'Ready' and I have two WebClient browsers opened. I also verify that both has Phone selected from the channel selector in the WebClient.
    6) With java_ic agent, I press the Dial Pad, enter the sap* agent phone
    number (Phone: +15550002; shown in the CCS for both agents logged in) and then I press the Dial button on Dial Pad to call to +15550002.
    6.1) After pressing the Dial button, the WebClient displays a pop-up in
    the middle of the screen with info: "Your request is being processed." After this there is an Info message under the buttons in the WebClient for java_ic saying: "No account information found".
    7) Java_ic WebClient shows that it's doing an outbound call and is 'Dialing' state.
    8) sap* WebClient window has blinking button with labels 'Accept' and 'Reject'. So, it clearly got an notification of the Inbound Phone call coming from java_ic. But there is also an error message under the buttons in the same WebClient webbrowser screen (not in the JavaConsole, not in separate alert message this time) for sap*:
    "Java error: type= APPLICATION ERROR, ID= GETIAD_FAILED, description=".
    9) With sap* WebClient I cannot answer or reject the call. Nothing happens. The browser Status Bar says: javascript:void(0) when I press the Accept button.
    10) At this situation, the CCS shows that the agents's sap* Workmode is
    switched from the previous 'Ready' state to 'Not Ready' automatically (while the sap* WebClient status is still in Ready). So, the sap* automatically, due to the error, changed the status to 'Not Ready'.
    11) java_ic remain on 'Dialing' status for all the time trying to get connected with sap*.
    I got informed that the call between WebClient COULD BE seen as a "call transfer" between clients by the CRM system. This might be something to do with the problem in calling between WebClients.
    Because the java_ic reports: "No account information found" when placing the Outbound Phone call, one could assume that account details should be passed along with the call transfer. Possibly sap* cannot receive the
    inbound phone call due to a missing account information thus reporting java error: "Java error: type= APPLICATION ERROR, ID= GETIAD_FAILED, description=".
    Best Regards,
    Jani

    [loaded]  com.genieo.completer.download.plist Adware! [Remove]
      [loaded]  com.genieo.completer.ltvbit.plist [Support]
      [running]  com.genieo.completer.update.plist Adware! [Remove]
      [not loaded]  com.macpaw.CleanMyMac.helperTool.plist [Support]
      [not loaded]  com.macpaw.CleanMyMac.trashSizeWatcher.plist [Support]
      [not loaded]  com.macpaw.CleanMyMac.volumeWatcher.plist [Support]
      [loaded]  com.macpaw.CleanMyMac2Helper.diskSpaceWatcher.plist [Support]
      [loaded]  com.macpaw.CleanMyMac2Helper.scheduledScan.plist [Support]
      [loaded]  com.macpaw.CleanMyMac2Helper.trashWatcher.plist [Support]
    Your machine is slow because you loaded a bunch of third party junk on it.

  • Cannot access external data , Failed to get the document information.

    Hi All,
    In my dashboard there are live office connections which has optional prompts defined in SAP BI. I have bound the cells to these prompts in live office object properties.
    There are no errors while refreshing the LO connections from excel sheet.
    But when i run that dashboard and give BLANK value for that prompt then it throws the error :
    Cannot access external data , Failed to get the document information. (LO 26315).
    Reply highly appreciated.
    Thanks & Regards,
    DJ

    Hi Hardik,
    I am building a similar solution as yours connecting webi reports to Bex queries and reading the webi data through live office into the dashboards. I am using almost similar versions as yours - BW 7.1 SP5, BO 4.1 SP4, Dashboards and Live Office SP4 versions. I am facing issues setting up the live office connections itself. I create the Live office connections within an excel and when I try to import this excel spreadsheet into my dashboard designer, it runs forever and crashes.
    Could you please list out the steps you performed to get the Dashboard to preview live office data? Do you have OLAP connections for BW cubes and created WebI reports using these connections or You created a Universe on top of the Bex Queries?
    It would be great if you could share the steps performed.
    With respect to your issue, check if the report engine service is running. Do you have any error message details apart from this error?
    Thanks.
    Regards,
    Rohini.

  • Calendaring agent failed with error code 0x8000ffff Event id 8206 and 8207

    Hi to all
    We have an Exchange 2007 SP3 with Update Rollup 11 and all the user use Outlook 2003 with SP3.
    Suddenly in our Exchange Server we have start to receive a lot of 8206 and 8207 EXCDO errors in the Application.
    Event Type: Error
    Event Source: EXCDO
    Event Category: General
    Event ID: 8206
    Date:  5/2/2015
    Time:  11:17:41 πμ
    User:  N/A
    Computer: EXCHANGESRV1
    Description:
    Calendaring agent failed with error code 0x8000ffff while saving appointment.
    For more information, see Help and Support Center at
    http://go.microsoft.com/fwlink/events.asp.
    Data:
    0000: 48 72 53 61 76 69 6e 67   HrSaving
    0008: 41 70 70 74 3a 3a 48 72   Appt::Hr
    0010: 43 68 65 63 6b 50 61 74   CheckPat
    0018: 74 65 72 6e 20 66 61 69   tern fai
    0020: 6c 65 64 2e 20 4d 61 69   led. Mai
    0028: 6c 62 6f 78 3a 56 61 73   lbox:x
    0030: 73 69 6c 69 73 2e 4b 6f   xxxx.xxx
    0038: 6e 74 6f 67 69 61 6e 6e   xxxxxxx
    0040: 69 73 40 45 55 52 4f 43   xx@xxxx
    0048: 48 41 52 54 49 4b 49 2e   xxxxxxx.
    0050: 47 52                     GR     
    Event Type: Error
    Event Source: EXCDO
    Event Category: General
    Event ID: 8207
    Date:  5/2/2015
    Time:  11:19:41 πμ
    User:  N/A
    Computer: EXCHANGESRV1
    Description:
    Calendaring agent failed with error code 0x8000ffff while deleting appointment.
    For more information, see Help and Support Center at
    http://go.microsoft.com/fwlink/events.asp.
    Data:
    0000: 48 72 44 65 6c 65 74 69   HrDeleti
    0008: 6e 67 41 70 70 74 3a 3a   ngAppt::
    0010: 5f 48 72 47 65 74 42 75   _HrGetBu
    0018: 73 79 49 6e 66 6f 20 66   syInfo f
    0020: 61 69 6c 65 64 2e 20 4d   ailed. M
    0028: 61 69 6c 62 6f 78 3a 56   ailbox:x
    0030: 61 73 73 69 6c 69 73 2e   xxxx.xxx
    0038: 4b 6f 6e 74 6f 67 69 61   xxxxxxxxx
    0040: 6e 6e 69 73 40 45 55 52   xxx@xxx
    0048: 4f 43 48 41 52 54 49 4b   xxxxxxxx
    0050: 49 2e 47 52               I.GR   
    All the errors come ONLY FROM 1 USER. 
    How can i fix this errors?
    If you require any further information do not
    hesitate to let me know
    Thanks and regards.

    You must ask in Exchange forum
    https://social.technet.microsoft.com/Forums/office/en-US/home?category=exchangeserver

  • Web Part Error: Sandboxed code execution request failed - office 365

    If i am trying to edit the webpart, i am getting this error "Web Part Error: Sandboxed code execution request failed"
    But the same code worked properly before two months, i didnt done any deployment activities from last 6 months..i dont know how it is possible ? 
    and the same issue happening during the javascript post back also
    1) I cant able to restart the sandbox service because i am using office 365
    2) it worked properly before march month, after the patch upgrade which is released by microsoft, i am facing this kind of issue..
    can any one help to resolve this issue ?

    Hi,
    Please post your question on online community for sharepoint 

  • Automatic windows agent fail over in SCOM 2012 / 2012 R2

    Hi All,
    I have a question with respect to SCOM 2012 / 2012 R2 windows agent fail over.
    For example i have only 400 windows agents and i have 2 MS in my environment. So 200 windows agents are managed by MS1 and the rest 200 are managed by the MS2.
    What i want to know is if either of the MS (MS1 or MS2) Shutdown / restart or any thing happens to them, Do the agents automatically fail over to the other MS ? As i have not configured ant thing for this as i don't know.
    So is there any configuration to be done for the above to happen after the deployment of both the management servers is done before discovering the agents or does it automatically understand take the rest 200 agents thinking that the other MS is down ?
    Gautam.75801

    Hi All,
    I have a question with respect to SCOM 2012 / 2012 R2 windows agent fail over.
    For example i have only 400 windows agents and i have 2 MS in my environment. So 200 windows agents are managed by MS1 and the rest 200 are managed by the MS2.
    What i want to know is if either of the MS (MS1 or MS2) Shutdown / restart or any thing happens to them, Do the agents automatically fail over to the other MS ? As i have not configured ant thing for this as i don't know.
    So is there any configuration to be done for the above to happen after the deployment of both the management servers is done before discovering the agents or does it automatically understand take the rest 200 agents thinking that the other MS is down ?
    Gautam.75801
    This happens automagically for Windows agents within a domain that are assigned to a Management Server.  For other scenarios, such as Gateways, the Gateways should be configured for failover between Management Servers, and the agents attached to those
    Gateways should be configured to failover between the Gateways.  Cross platform agents report to a resource pool, so that happens automagically as well.
    To confirm your scenario, simply run the Get-SCOMAgent cmdlet.
    To test you can do the following, assuming first agent in the array isn't a Management Server/Gateway :)
    $SCOMAgents = get-scomagent
    $SCOMAgents[0].PrimaryManagementServerName
    $SCOMAgents[0].GetFailoverManagementServers()
    Supporting article:
    http://blogs.technet.com/b/jimmyharper/archive/2010/07/23/powershell-commands-to-configure-gateway-server-agent-failover.aspx

Maybe you are looking for

  • C9058A-002 Duplexer - Looking for another model of printer to use it on

    Now that my OfficeJet J6450 is no longer operational, I was wondering if anyone knows of any other current models of all-in-one type printers that the C9058A-002 Duplexer (that came with the J6450) could be used on. I've tried researching it with no

  • About Tomact's Web.xml file

    Starting service Tomcat-Standalone Apache Tomcat/4.0.1 PARSE error at line 38 column 11 org.xml.sax.SAXParseException: The content of element type "web-app" must match "(icon?,display-name?,description?, distributable?,context-param*,servlet*,servlet

  • Programmatically retrieving the DeviceNet "Connection" object in LabVIEW (like SimpleWho can)

    I can already get all of the "Identity" object attributes, but how does one get the "Connection" object attributes? Specifically, I would like to get the poll input/output lengths so I can set up an I/O connection.  It looks like SimpleWho can get th

  • Where is an opacity/scale/speed LINE on CC?

    I have got Adobe After Effects CC from few minutes. And I noticed that line for keyfreming is missing. How can I see a timeline of for example OPACITY? It's gone in CC version.

  • NetConnection Failed - AIR app

    Hi, I am having a NETConnection Failed Error, when i am calling remote objects functions.. My air app successfully received results from remote object call when the SQL execution time takes less than about 10 seconds, however a NETConnection Failed E