BE 2010 R2 DLO Admin Console Hangs

[UrbanLegendPA]

When I open the DLO Admin Console it just hangs "Not Responding". Just started happening in the last week. I have all the latest patches applied. DLO is functioning and can be used to backup and restore from the desktops, just can not administer.

I am accessing the Media Server via Remote Desktop and opening the DLO Console remotely.

Once the DLO Admin Console is openned, the task cannot be terminated. To remove the process a reboot is required.

Any ideas on how to solve this?

[CraigV]

Hi there,

Have you run a repair of your installation? If not, do that, and report back.

You can also check the Event Viewer (Application Log) to see if there are any specific errors generated.

Laters!

[UrbanLegendPA]

I did a repair, that didn't fix it. It uninstalled BE 2010, CPS, and DLO and reinstalled all 3. Did all Live updates. Still same problem. There are no events in the App log indicating a problem.

Thanks

[RahulG]

Hello,

Please check if any anti-virus software is scanning the C:\program files\Symantec directory, if yes, add it to exceptions. Ensure that you do not have any DOT NET events in the application log. run a SGMON debug against "StoreX" and try launching the admin console. Attach the log if possible.

Lemme know how that goes!

[Takeshima]

Hello,
I also have exactly the same problem.

No response from DLO Admin Console.
Cannot stop the process.

However, and then install the DLO Admin Console to another PC
I was able to connect to media server without problems.
Problem occurs only on the local media server.

Including all components such as MSSQL and Visual C++ run-time I uninstalled BE2010 R2.
I rebooted the server.
And I reinstalled BE2010 R2 and all HotFix but still problem occurs.

I have set exception 'C:\Program Files\Symantec' directory in Symantec Endpoint Protection.
I make sure that no DOT NET events in the application log.

Attachment file is logging enabled 'DLO' and 'StoreX' in SGMON. 

[Takeshima · Accepted solution]

According to the analysis of Symantec technical support,
the cause was BackupExec 2010 R2 CPS Server installed in the same machine.

It solved it by having upgraded BackupExec 2010 R2 and CPS R2 to R3.