Error while running a project in em console

Question

It was running fine all these days.server was restarted and i am facing problems shown below.
I am not able run any project(ex.Project1) in em console.I am getting 2 errors like.
1)DBLocker caught exception while retrieving locked messages.Will retry retrieval after 2 seconds
2)Error while invoking endpoint "http://<server name>:7001/soa-infra/services/default/Project1/StdService" from client; Security Subject: Administrators
Even if i unlock the account,its getting locked automatically.
Notifications:1)The DocumentChange is not configured to be allowed for the component: RichTable[org.apache.myfaces.trinidad.component.UIXTable$RowKeyFacesBeanWrapper@7ae15fc6, id=messagesResult]
2)Invalid Remote Targets: [Target Name: /Farm_soa_domain/soa_domain/AdminServer/OracleBamServer, Target Type: oracle_bam_server, Display Name: OracleBamServer (AdminServer) => com.bea:Name=oracle-bam#11.1.1,Location=AdminServer,Type=AppDeployment], [Target Name: /Farm_soa_domain/soa_domain/AdminServer/OracleBamWeb, Target Type: oracle_bam_web, Display Name: OracleBamWeb (AdminServer) => com.bea:Name=oracle-bam#11.1.1,Location=AdminServer,Type=AppDeployment]
3)Calling ClearCacheCanonical Path=oracle.dms:JDBC_DataSource=SOADataSource,Location=AdminServer,name=/JDBC/SOADataSource/CONNECTION_4106,type=JDBC_Connection :::: matched=false
Thanks in advance

Answer 1

ALV Grid control is based on the custom controls on the screen. When the program is scheduled in background, it tries to create GUI related front-end objects and hence the error u201CFatal Error u2013 GUI cannot be reachedu201D. This type of problem is common with all the programs that use the ALV grid control to display the output.
Solution:
Whenever we execute this type of programs in background, we should be passing a blank docking container instead of the custom container as parent to our grid control. 
The docking container doesnu2019t need any of the custom controls on the screen; instead it attaches an area to any or all of the four edges of the screen (top, left, right or bottom). The behavior of the areas in the container is determined by the sequence in which they are initialized. Docking Containers are attached to the screen from the inside out. This means that when you create a second container, it is attached to the edge of the screen, and the container that was already there is pushed outwards. 
Let us modify the standard program (by taking a copy of it) to enable it to execute it in background.
Following modifications have to be made:
·        Define a docking container in the program
data: or_doc  type ref to cl_gui_docking_container .
·        At the time of creating a custom container, check if the program is being executed in background or foreground. If the program is scheduled in background, then create a docking container instead of custom container.
if cl_gui_alv_grid=>offline( ) is initial.
    create object or_custom_container
           exporting container_name = c_container.
  create object or_grid
         exporting i_parent = or_custom_container.
else .
create object or_grid
         exporting i_parent = or_doc .
endif . 
Now test executing the program in background. The report would be generated.