Access Denied: Wily Bytecode agent Installation in SolMan 7.1

[Former Member]

Hello Experts,

We recently installed a Solution Manager 7.1 SP04 and are performing the managed system setup for one of our Netweaver 7.0 EP systems. During the Wily Bytecode agent installation, the managed system setup fails. In the SMD Agent application log I could find the below error:

Feb 8, 2012 6:48:30 PM [Thread[SAP GC|AL0_JC00_server0,5,WILYHOST_...]

Error com.sap.smd.wily.hostagent.action.GcScannerAction - doRun():

Action temporarily stopped: SAP GC|AL0_JC00_server0

[EXCEPTION]

com.sap.smd.wily.hostagent.TransientException:

java.io.FileNotFoundException:

G:\usr\sap\AL0\JC00\j2ee\..\work\std_server0.out (Access is denied) at

com.sap.smd.wily.hostagent.action.AbstractAction.handleError(AbstractAction.java:382)

at

com.sap.smd.wily.hostagent.action.GcScannerAction.scanInitial(GcScannerAction.java:395)

at

com.sap.smd.wily.hostagent.action.GcScannerAction.doRun(GcScannerAction.java:142)

at

com.sap.smd.wily.hostagent.action.AbstractAction.run(AbstractAction.java:85)

at

com.sap.smd.wily.hostagent.Scheduler$RunnerAdapter.run(Scheduler.java:163)

at com.sap.smd.server.exec.TaskRunner.run(TaskRunner.java:46)

at

com.sap.smd.server.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:785)

at java.lang.Thread.run(Thread.java:679)

Caused by: java.io.FileNotFoundException:

G:\usr\sap\AL0\JC00\j2ee\..\work\std_server0.out (Access is denied)

I already checked the Diagnostics agent OS user DAAADM user is a part of Administrators group. And the file std_server0.out is accessible to the Administrators group.

Also found few thread dealing with same issue:

http://forums.sdn.sap.com/thread.jspa?threadID=1530597

Here OS roles were updated but unsure which addtional roles are required

http://forums.sdn.sap.com/thread.jspa?threadID=1914602

Similar issue, but in our case the path to the file is a valid one - hence unsure if this applied to us.

Perhaps someone else too faced a similar error and resolved it.

Thanks and Regards,

Srikishan

[guilherme_balbinot · Accepted solution]

Check if the user belongs to group SAP_LocalAdmin

[Former Member · Accepted solution]

Hi Guilherme,

Thanks for the suggestion. I had added the user to the SAP_LocalAdmin group.

Just wondering if we need a server reboot too.

Regards,

Srikishan

[guilherme_balbinot · Accepted solution]

Hi Srikishan,

It shouldn't be necessary. Stop the Agent. Make sure the process is stopped before restarting the agent. Start it again.

Best regards,

Guilherme

[Former Member · Accepted solution]

Hi Guilherme,

Thanks again for your help. I already restarted the DAA SMD agent and even the Portal system on host - but still the same error in the logs

Regards,

Srikishan

[guilherme_balbinot · Accepted solution]

Hi,

Did you check note 1163751?

[guilherme_balbinot · Accepted solution]

Try to restart the server then, I have seen issues get solved after restart, specially windows OS.

[Former Member · Accepted solution]

Thank you Guilherme!! Yes I checked the Note 1163751, I could find the umask more relevant for the SMD agents on UNIX systems. However for Windows, no specific symptoms/solution were mentioned. Hence was not sure if it could help us.

But - we have planned for a server reboot for either tomorrow late evening or over the weekend. Will update the thread after bouncing the server. Keeping fingers crossed until then

Regards,

Srikishan

[guilherme_balbinot · Accepted solution]

Hello Srikishan,

Please share the result with us if possible.

Best regards,

Guilherme

[Former Member · Accepted solution]

Hi Guilherme,

Sorry, had got caught up with CHARM in SolMan 7.1.

We tried a reboot of the server, but the 'access denied' error still shows up. In the meantime we also opened a message with SAP Support. The recommendation was same from their end too.

We also noticed that the group SAP_LocalAdmin did not have access to the managed system folder ..\usr\sap\<SID>

We are now adding the group to the managed system's <SID> folder. Will perform a reboot afterwards and hopefully the issue is solved. Will update the thread here.

Regards,

Srikishan

[Former Member · Accepted solution]

Hi,

The issue is now resolved. Maybe ours is a freakish case, but the SAP_LocalAdmin group should be ideally in the permissions group for ..\usr\sap\<SID> where SID is the managed system for which Wily bytecode agent is being setup.

Regards,

Srikishan

[guilherme_balbinot · Accepted solution]

Hello Srikishan,

Thank you for the feedback.

I'm not sure why the group doesn't have the permission. I'm not familiar with SAPINST internals but I guess that the it should grant this permissions, perhaps a bug or a overwrite on those directories.

Best regards,

Guilherme

[Former Member · Accepted solution]

Hi Guilherme,

Yes, it was an issue due to the group getting dropped off the permission list. I also enquired regarding the setup prcedure of the managed system and found that the system is residing on a virtual host which was converted from a physical host. Perhaps this conversion is responsible for the group getting dropped off. However, yes this would be a one-off case due to the non-standard way of setting up the system.

Regards,

Srikishan

[guilherme_balbinot]

Hello,

Please check this SAP Note [1163751|https://css.wdf.sap.corp/sap/support/notes/1163751].

Best regards,

Guilherme