Skip to Content
0
Former Member
Feb 09, 2012 at 02:23 PM

Access Denied: Wily Bytecode agent Installation in SolMan 7.1

87 Views

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