Attach agent for a server in a workgroup

I have SCDPM 2012 on a 2012 server trying to attach to a 2008r2 workgroup server I receive the following error:
Attach protected computer elmscadawhist failed:
Error 32685: This server does not match the DPM server setting on server elmscadawhist.
Error details: The parameter is incorrect (0x80070057)
Recommended action: 1) Ensure that you have specified the correct protected computer.
2) In case you have specified the correct protected computer, run the SetDpmServer utility on elmscadawhist with the correct DPM server name, and then retry the operation.

Hi
Did you manually install the agent and use the DPM server name at the end?

Similar Messages

SQL query to get the without SCCM agent for a Server

Hello every one,
Can I get the SQL query for a server without a SCCM agent .

Here you go!!
Add the version for windows 2012 server if you have them as well in your environment
v_R_System.Netbios_Name0
,v_R_System.Full_Domain_Name0
,v_R_System.User_Name0
,case
When v_R_System.Operating_System_Name_and0 LIKE N'%Server 6.1'THEN 'Windows Server 2008 R2'
When v_R_System.Operating_System_Name_and0 LIKE N'%Server 6.0'THEN 'Windows Server 2008'
When v_R_System.Operating_System_Name_and0 LIKE N'%Server 5.2'THEN 'Windows Server 2003 R2'
ELSE 'Unknown Version' END AS 'OS version'
FROM
v_R_System
WHERE
v_R_System.Operating_System_Name_and0 LIKE N'%server%' and v_R_System.Client0 is null
Kindly mark as answer/Vote as helpful if a reply from anybody helped you in this forum. Delphin

SUN cluster 3.1 Agent for Siebel Server

Hi All
I dont have the CD for the Sun Cluster 3.1 agent . Please suggest me a link from where i can download the agent for Sun HA For Siebel Server,
Thanks/Regards

Hi,
the agent should be part of the latest JAS release, which is SC3.1 8/05.
Mark the Java Availability Suite checkbox on
www.sun.comhttp://www.sun.com/software/swportfolio/get.jsp
and hit "Get downloads". That should lead you to the download section.
Regards
Hartmut

Can't install DPM agent for Windows Server 2003

Hi,
We have DPM 2012 backup server.i try to install DPM Agent on Windows server 2003 PC. but installation failed.below error are Occured.
Install protection agent on (serverName.domain name) failed:
Error 347: An error occurred when the agent operation attempted to create the DPM Agent Coordinator service on (serverName.domain name).
Error details: %1 is not a valid Win32 application
Recommended action: Verify that the Agent Coordinator service on(serverName.domain name) is responding, if it is present. Review the error details, take the appropriate action, and then retry the agent operation.
HOW CAN SORTED OUT FOLLOWING ISSURE
Thanks,
Gayan

Hi,
The below blog outlines the needed steps for protecting
Windows Server 2003 computers using Data Protection Manager 2012 R2.
http://blogs.technet.com/b/dpm/archive/2014/06/11/details-on-protecting-windows-server-2003-computers-using-data-protection-manager-2012-r2.aspx
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually
answer your question. This can be beneficial to other community members reading the thread. Regards, Dwayne Jackson II. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights."

The Server Intelligence Agent for this server is unavailable

Folks,
Issue surfaces after clustering,above mentioned error appears in properties of each server irrespective of servers running(pretend) and not running.
Here,we tried to cluster 4 nodes,first 2 nodes are good no issues,but 3 and 4 nodes have issue.
I also noticed below message under properties
" The server is not managed by Server Intelligence Agent. Current command line arguments could not be retrieved. Server restart would be required if the command line arguments are modified. Current command line arguments could not be retrieved. Server restart is required if the command line arguments are modified".
Environment
=========
BOXI3.1 SP5
Win 2008

Hi,
Check attached sap notes.
1432354 - Error "The server is not managed by Server Intelligent Agent" in a clustered environment
1498863 - Error: "The server is not managed by Server Intelligence Agent." in all Business Objects Server's properties in Central Management Console.
Regards,
Amit

AM 7.1 agent for Web Server 7.0 not working

Hello,
I've performed a clean installation of Java ES 5 Access Manager 7.1 installation on one box, a clean installation of Jave ES 5 Web Server 7.0 on another and installed Policy Agent 2.2 on the Web Server box. It has modified obj.conf and magnus.conf as proposed, but I still can access all resources with no AM authentication. The agent is being initialized as per /root/web_agents/sjsws_agent/Agent_001/logs/debug/amAgent log file.
I would swear it did work before (in previous WS70/PA installation with no special configuration, but I cannot get it working now.
What to look at first?
Thanks :-/

Appeared to be RTFM issue with WS70 admin console creating new instance-specific obj.conf and not copying AMAgent configuration blocks.
Sorry :/

AM policy agents for Weblogic help

I installed a Policy Agent for Weblogic Server 8.1 When I try to start the Weblogic server after modifications, the portal server throws an exception....
com.sun.identity.agents.AmAgentFilter not found
When u enter the URL for that application running on Weblogic , it is supposed to be forwarded to the Identity Management page ...but this does not happen..
It is apparently able to read the web.xml file in the Weblogic application but is not able to find the particular class above....nor is it able to contact the IDM.
Any suggestions?
Anand

I am trying to install a PA with a Weblogic server. The installation works fine and I have also configured the necessary config files...and the concerned Weblogic server starts up successfully.
But when I enter the URL , I see the following error in the Logs....
<Jan 3, 2006 3:54:12 PM CST> <Error> <HTTP> <BEA-101020> <[ServletContext(id=20772999,name=sbm,context-path=/sbm)] Servlet failed with Exception
java.lang.ExceptionInInitializerError
     at com.sun.identity.agents.filter.AmFilter.<init>(Unknown Source)
     at com.sun.identity.agents.filter.AmFilterManager.getAmFilter(Unknown Source)
     at com.sun.identity.agents.filter.AmFilterManager.getAmFilter(Unknown Source)
     at com.sun.identity.agents.filter.AmFilterManager.getAmFilterInstanceForModeConfigured(Unknown Source)
     at com.sun.identity.agents.filter.AmAgentFilter.doFilter(Unknown Source)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6724)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
     at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3764)
     at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2644)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
Caused by: java.lang.RuntimeException: Exception caught in AmAgentLogManager initializer: Unable to initialize Local Log Handler
     at com.sun.identity.agents.log.AmAgentLogManager.<clinit>(Unknown Source)
Can someone help me taclke this problem??
Thanks!
anand

Using the SQL Server Agent for the first time

I have set up several jobs to run automatically throughout the day. Each job just does one thing: executes an SSIS package.
The packages themselves run perfect when I test them in Visual Studio 2005, but when the SQL Server Agent tries to run the job I am getting failed jobs.
Is there any tutorials or walkthroughs that can teach my about using the SQL Server Agent? If I wanted extensive help troubleshooting my SQL Server Agent problems which part of the message boards would I post that too?
Thanks for the info!

Anyone?
I really need some resources for SQL Server Agent 2005.
Refer these links,
http://technet.microsoft.com/en-us/library/ms141701(v=sql.90).aspx
http://stackoverflow.com/questions/10489392/permissions-issue-running-ssis-package-from-sql-job
Regards, RSingh

Logs for sql server agent restart

Hi,
Can I get log on the sql server agent restart history of week. I mean the sql server agent has been restarted several times in last week I want to know the date and time when the sql server agent restarted in that week. Is it possible to get
the info?
Thanks in advance,
Pavan
Pavan

In addition to Uri's post, here is some more information that might help you:
SQLAGENT.OUT, the log file for SQL Agent. SQL Server Agent can maintain up to 10 Error Logs files. The currently used SQL Server Agent Error Log will be named SQLAGENT.OUT
where is the SQLAGENT.OUT file?
C:\Program Files\Microsoft SQL Server\MSSQL11.SQL2012\MSSQL\Log\
What will be when a new file create?
The old file should get a name like SQLAGENT.X and the new file get the name SQLAGENT.OUT (X is numbers 1-9)
This can help you to get more information on sql agent properties (like the location of the log file, the user that start the service and more):
EXEC msdb..sp_get_sqlagent_properties
[Personal Site] [Blog] [Facebook]

Service Account for SQL Server Agent on SQL Server 2008 R2

This SQL Server instance is SQL Server 2008 R2 (10.50.4000). We had Active Domain Service accounts created to run the service accounts for SQL Server and SQL Server Agent.
It has become company policy to alter the service accounts that run SQL Server and SQL Server Agent. Currently, both were running under the Local System Accounts. We have altered the SQL Server but we are having issues with the SQL Server Agent.
I am told by another DBA that
"The agent is requiring elevated rights. It will startup if it has local admin rights, but not with domain accounts without admin rights."
So I was wondering if anyone has come across this issue and how did they resolve it.
lcerni

"The agent is requiring elevated rights. It will startup if it has local admin rights, but not with domain accounts without admin rights."
This is completely not true. It is indeed possible to run agent as a domain account without giving it local admin. Chances are you'll need to update the local acls by adding the account to the local security groups. Please see this article for more information:
http://technet.microsoft.com/en-us/library/ms143504(v=sql.105).aspx
Edit: In addition, it'll need rights to SQL server for that account to connect and do its work. It will need to be given sysadmin:
http://technet.microsoft.com/en-us/library/ms191543.aspx
Sean Gallardy | Blog |
Twitter

What would be the reason for sql server agent [MSSQLSERVER] service terminated unexpectedly?

What would be the reason for sql server agent [MSSQLSERVER] service terminated unexpectedly?
only below details found in error log
07:26:44.170 spid60
FILESTREAM: effective level = 3, configured level = 3, file system access share name = 'MSSQLSERVER'.
07:26:45.720 spid51
Configuration option 'Agent XPs' changed from 0 to 1. Run the RECONFIGURE statement to install.
07:26:45.730 spid51
FILESTREAM: effective level = 3, configured level = 3, file system access share name = 'MSSQLSERVER'.
07:28:57.840 spid64
Configuration option 'Agent XPs' changed from 1 to 0. Run the RECONFIGURE statement to install.
07:28:57.840 spid64
FILESTREAM: effective level = 3, configured level = 3, file system access share name = 'MSSQLSERVER'.
and below error on agent log
2014-01-01 07:26:28 - ? [131] SQLSERVERAGENT service stopping due to a stop request from a user, process, or the OS...
2014-01-01 07:26:43 - + [188] Scheduler engine timed out (after 15 seconds) waiting for 1 jobs(s) to stop
2014-01-01 07:26:44 - + [098] SQLServerAgent terminated (forcefully)
Rahul

What would be the reason for sql server agent [MSSQLSERVER] service terminated unexpectedly?
only below details found in error log
07:26:44.170 spid60
FILESTREAM: effective level = 3, configured level = 3, file system access share name = 'MSSQLSERVER'.
07:26:45.720 spid51
Configuration option 'Agent XPs' changed from 0 to 1. Run the RECONFIGURE statement to install.
07:26:45.730 spid51
FILESTREAM: effective level = 3, configured level = 3, file system access share name = 'MSSQLSERVER'.
07:28:57.840 spid64
Configuration option 'Agent XPs' changed from 1 to 0. Run the RECONFIGURE statement to install.
07:28:57.840 spid64
FILESTREAM: effective level = 3, configured level = 3, file system access share name = 'MSSQLSERVER'.
and below error on agent log
2014-01-01 07:26:28 - ? [131] SQLSERVERAGENT service stopping due to a stop request from a user, process, or the OS...
2014-01-01 07:26:43 - + [188] Scheduler engine timed out (after 15 seconds) waiting for 1 jobs(s) to stop
2014-01-01 07:26:44 - + [098] SQLServerAgent terminated (forcefully)
Rahul
Can you post the output of below query
select @@version.
If you are using SQl server express edition ,SQL server agent feature is not available.It seems from errorlog that you can start it but actually you cannot.But first confirm what is version and edition of your SQL server
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

ID Server and Policy Agent for AS .. is secure?

Hello there,
I have a question. Quite critical question, concerning iPlanetDirectoryPro cookie. If I've got it right, this cookie contains SSO Token. And the SSO token can be used with identity server to obtain any SSO assetion. I've experimentaly confirmed this.
Now, can anyone tell me why this cookie is sent to any host in my domain? The default after instalation is "bgs.sk". This default value enables any host in my domain to impersonate me. Well, I still can change this, but it is now good to have insecure default values anyway, is it?
Second, and more critical problem: I have Policy Agent installed on my Application Server. It looks like the agent requires access to the iPlanetDirectoryPro cookie to work correctly. But, if my application server has my SSO token, it can impersonate me anywhere. Not a good situation at all. That would mean security hole as big as hangar doors.
Are my assumptions correct? Am I overlooking something?
(All valid for ID server 6.0 and Liberty protocols)
Thanks for any help.

Although Sun promote Identity Server by emphasizing its Liberty/SAML feature, the product itself use a proprietary protocol for SSO and CDSSO.
As all we know, this product could be totally useless without Sun's Policy/J2EE Agent deployed. But ironically these agents communicate with Identity Server in its own way, nothing to do with SAML, XACML, or even SOAP.
The agent approach is usually not a good idea. We saw more and more problem raised from fields related to agent stability and scalability. We never see any performance benchmark data from Sun. Since the communication between agt and Identity Server are proprietary, no ISV can make agent for this product. You have to wait for Sun for agent support if you have new system not on the support matrix.
In addition to agent, another big issue of Identity Server is its complex DIT structure. In fact, we prefer to have RDBMS as Identity Server's repository. Sun abuse ldap just because this company doesn't have any database product but still want to provide a pure Sun platform (JES) to customer. So they compromise the architecture for business reason, I'd like to tell you, I don't like the way Identity Server store data in DIT, I don't like the console UI (its for technical geek), and on one in our company dare to do any configuration change.
Now Sun put Identity Server as the core of its JES product stack. If you have time to take a look at how the SJS Portal use Identity Server and how SSO between Portal channel and Email/Calendar Server are achieved, you'll find that you just buy a "framework" (I mean Identity server), not a product, because you have to do every integration work by intensively coding.
I predict that Identity Server will be significantly rearchitctured in the near future, otherwise we don't see any benefit this product can bring to me. It is a headache for deployment as well as maintenance. If you just need Single Sign-On, there are lots alternative to achieve, Sun's Identity Server is really overkill. It's authentication feature is ok, but authorization feature (policy, role) is very limited. If you have lots of Windows/IIS web app need to do SSO with Identity Server, god bless you... you better have a sharp programmer to wrap up the C API so as your ASP programmer can leverage Identity Server SDK, and you got to pray for IIS agent behave well. In addition, don't forget to learn more about JATO if you want to do some fancy customization on the default login page.

BE 9.2 agent support for Win Server 2008

Greetings, all...
I have a client with an OES 2 NetWare cluster running BE 9.2. We will soon be deploying Blackberry Enterprise Server 5 on a new box running Windows Server 2008 R2 64-bit (the only app on the box). I'm wondering whether BE 9.2 will support the Backup Exec 2010 Agent for Windows Systems, so that I may add this machine to the standard backup routine. Any experiences?
TIA

Rachelsdad,
It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.
Has your problem been resolved? If not, you might try one of the following options:
- Visit http://support.novell.com and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)
Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.novell.com/faq.php
If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.
Good luck!
Your Novell Product Support Forums Team
http://forums.novell.com/

Installing policy agent 2.1.1 for app server 7

Hi,
I've been trying to install the policy agent on app server7. I read that the policy agent had to be installed on a different instance of the app server than the one where the portal is running (portal runs on instance server1). How can you make sure of that?
I'd like to use the agent to only control the access to a webapp that is deployed on server1 instance. I don't want it to interfere with the portal but at the moment it does.
Now I can't use the webapp (access forbidden) and the portal ("Authentication Service is not initialized").
all the components of JES but the gateway are installed on a single machine called crpbioweb.crp-sante.healthnet.lu
here is the statefile of the installation
[STATE_BEGIN Sun ONE Identity Server Policy Agent a15672cb9a086c93b865dd58c4e72641d908cc91]
OS_NAME = SunOS
PACKAGE_ZIP_FILE = am_as70_agent.zip
PACKAGE_ID = SUNWamas
PACKAGE_VERSION = 2.1
COMPONENT_NAME = Sun ONE Identity Server Policy Agent for Sun ONE Application Server 7.0
AGENT_TYPE = as70
defaultInstallDirectory = /opt
currentInstallDirectory = /opt/agent
SERVER_HOST = crpbioweb.crp-sante.healthnet.lu
SERVER_PORT = 58080
SERVER_PROTO = http
SERVER_DEPLOY_URI = /amserver
CONSOLE_HOST = crpbioweb.crp-sante.healthnet.lu
CONSOLE_PORT = 58080
CONSOLE_PROTO = http
CONSOLE_DEPLOY_URI = /amconsole
ENCADMINPASSWD = password
LDAPUSERPASSWD = amldapuser
DIRECTORY_HOST = crpbioweb.crp-sante.healthnet.lu
DIRECTORY_PORT = 389
DIRECTORY_SSL_ENABLED = false
ROOT_SUFFIX = dc=crp-sante,dc=healthnet,dc=lu
ORG_BASE = dc=crp-sante,dc=healthnet,dc=lu
CONFIG_LOAD_INTEREVAL = 10
ENABLE_NEL_CACHE = false
NEL_CACHE_SIZE = 1000
NEL_CACHE_TIME = 60
PREF_PROTOCOL = http
PREF_PORT = 80
PRIMARY_CTX_PATH = /mailtracker
AGENT_HOST = crpbioweb.crp-sante.healthnet.lu
FILTER_MODE = ALL
ACCESS_DENIED_URI =
LOGIN_ATTEMPT_LIMIT = 5
JAVA_HOME = /usr/jdk/entsys-j2se
JSSE_INSTALLED = true
JCE_INSTALLED = true
AS70_BIN_DIR = /opt/SUNWappserver7/bin
AS70_ADMIN_USER = admin
AS70_ADMIN_PASSWD = password
AS70_ADMIN_PORT = 4848
AS70_INSTANCE_CONFIG_DIR = /var/opt/SUNWappserver7/domains/domain1/server1/config
[STATE_DONE Sun ONE Identity Server Policy Agent a15672cb9a086c93b865dd58c4e72641d908cc91]
There are 2 things I'd like to know:
How can I make sure the agent is installed on server2 instance and not on server1?
How do you choose to install the agent on server2?
If I correctly installed the agent on server2, then why does it block the webapp and the portal on server1?

Before installing the agent I already manually created a second instance of the app server on port 81. the problem is that I don't know how to install the agent on server2 instance. the only parameter that has something to do with port or instance is the "PREF_PORT". but according to the doc http://docs.sun.com/source/816-6884-10/chapter2.html#wp20595
it says that the Preferred protocol listening port is the preferred port number on which the application server provides its services.
I'm not quite sure what this means. Do I have to enter the port of the instance where I want to install the agent or the port I want to protect with the agent?
Another way to check if I installed it at the right place would be to check in the app server admin console. the installation created a new item in App server instance > server 1 > security > Realms. Do you know if this is the correct place to appear? or should it be in server2?
thanks

Database Mail Fails For SQL Server Agent Jobs / Maintenace plans - Why ?

Database Mail Fails For SQL Server Agent Jobs / Maintenace plans - Why ?
This has been a very common question I have seen relatedt to Database mail and I thought will post here so if you run into this issue, it could be due to one of the following and also have mentioned below how to get around them. Bottom line is datbase mail works fine with SQL Agent jobs and maintenace plans in SP1 on all platforms.
1. If you see this on 64 bit platform and on RTM build, this is a bug that is addressed in SP1.
2. If you see the below error message, it is known issue and this is because of design that requires SQL Agent to restart, if SQL Agent was started before enabling databasemail and setting a new profile. We are evaluating to change this design of not requiring to restart agent for our future release.
Re: 264] An attempt was made to send an email when no email session has been established
This problem will go away after restarting SQL Server Agent in this case. Thanks,
Gops Dwarak, MSFT

This may be related to the fact that DBMail, by default, shuts itself down after 10 minutes of inactivty. If the mail service isn't running, you won't be able to queue up any mail messages.
There may be a built-in mechanism for addressing this problem, but I found that I can detect this situation and start the mail listener before sending db mail. I use the following in stored procs that need to send email.
You could increase the inactivity period for db mail shutdown from 600 seconds to some larger value.  It might not make sense to do so, since shutting it down releases its resources back to teh system; if your SQL server only sneds mail infrequently, it might be better to start the mail listener on demand. Someone with more experience than I might want to add their two cents' worth. :-)
/* Check the mail engine. Start the service if is is stopped         */
/* -- the DB Mail engine shuts down after 10 minutes (of inactivity) */
/* -- this setting can be changed, but we probably don't need to.    */
DECLARE @rc INT
IF NOT EXISTS (SELECT * FROM msdb.sys.service_queues
               WHERE name = N'ExternalMailQueue' AND is_receive_enabled = 1)
    EXEC @rc = msdb.dbo.sysmail_start_sp
    -- TODO: add handling and logging for any engine start issues

Attach agent for a server in a workgroup

Similar Messages

Maybe you are looking for