on 06-18-2012 9:02 AM
While running managed system setup we found that Our SAPhost agents fail to connect reason being.
"The diagnostics agent os user domain\daaadm is not authorized to establish
a trusted connection to SAP host agent, check the service/admin_users
property of SAP host agent profile. (cause java.io.FileNotFoundException:
C:\Program Files\SAP\hostctrl\work\sapcontrol_logon\logon54 (Access is
denied))
<SAPHostAgentTrustedConnectionConfigurator.java:364:setupTrustedConnection()>"
Parameter service/admin_users in the host_profile as recommended.
service/admin_users = domain\SapServiceDAA domain\daaadm domain\sapadm
even then this fails to work.
Regards
Hi Marvan/Abhishek
Have to checked the file permissions as suggested by Ratnajit?
Are you not able to connect only managed system host agents or Solution Manager host agent also?
I know you would have already check this note but just in case you have not please refer:
Note 1611483 - SolutionManager7.1 - Outside Discovery common error messages.
If this does not help. Let us know how you host_profile file looks.
Best Regards
Saurabh
FCI
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Saurabh,
Thanks for your information, I already have checked the permission and compare in another system that it work, but I'm still received the same error.
I've checked the sap note as well.
Are you not able to connect only managed system host agents or Solution Manager host agent also?
In this case both doens't work.
Here own host agent profile Path 99 Version720
SAPSYSTEMNAME = SAP
SAPSYSTEM = 99
service/porttypes = SAPHostControl SAPOscol SAPCCMS
service/admin_users = server\SAPServiceDAA
DIR_LIBRARY = C:\Program Files\SAP\hostctrl\exe
DIR_EXECUTABLE = C:\Program Files\SAP\hostctrl\exe
DIR_PROFILE = C:\Program Files\SAP\hostctrl\exe
DIR_GLOBAL = C:\Program Files\SAP\hostctrl\exe
DIR_INSTANCE = C:\Program Files\SAP\hostctrl\exe
DIR_HOME = C:\Program Files\SAP\hostctrl\work
Hello All,
This solution does not work for all environments, the property 'smdagent.os.user' should be used only in especial cases. Do not use this property unless you know exactly what you are doing.
The property smdagent.os.user forces the SMDAgent applications to use the OS user specified in its value. The SMDAgent OS user must not be changed, the SMDAgent needs to use the default <sid>adm and/or SAPService<sid> (in case of Windows) to run.
Kind Regards,
Allam Drebes
Thanks forall the answers thatIhave given, I have applied but I still have the same situation.
Have your other suggestion?
Thanks
Erika
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Sorry guys but I'm still facing the same problem .
Does anyone has another idea?
Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Check the file logon54 exists under C:\Program Files\SAP\hostctrl\work\sapcontrol_logon\ .
Provide full permission to the file.
Regards
Ratnajit
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
78 | |
10 | |
9 | |
7 | |
6 | |
6 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.