DLO failures

[Andy_Choi]

Using Backup Exec 11d, I can't seem to get any DLO installations to work properly.
I always get this:

Information V-139-52224-100

Unable to connect to Media Server.

Failed to load configuration settings.

Either you are not connected to the network or the Server is not responding. DLO needs to be able to contact the Server to perform this action.

The information link came up with no hits. The backup exec server is running propertly with the DLO configured correctly.

[shweta_rege]

Hello,


Could you please go through the links mentioned below and try the steps mentioned.

1. Error "Unable to connect to Media Server" is displayed after clicking "Configure Desktop and Laptop Option" from the Tools menu.

http://support.veritas.com/docs/273308


2. to perform a push install of the Desktop and Laptop Option agent in Backup Exec 10.0
http://support.veritas.com/docs/270174


Do get back to us if you face any issues with the above mentioned steps.



Thank You,

Shweta

[Andy_Choi]

I have checked both. I already installed the DLO and I re-installed without success.

Also I already have MS SQL 2005 so I created another DB instead of a new SQL instance. I do not wish to have two seperate SQL installations (even if one is SQL and the other express) on a single machine.

[Dipesh_Mistry]

this is exactly the problem i'm now getting

link:
http://forums.symantec.com/discussions/thread.jspa?threadID=69289&tstart=0

[shweta_rege]

Hello,


-- How many clients are affected with this Problem?

-- What versions of DLO on the clients affected?

-- What operating systems are on these clients?



Thank You,

Shweta

[Andy_Choi]

All of them. None of the clients have been able to connect.

Good thing I installed 11d in a test environment!!

I have reason to believe this is the issue:

http://forums.symantec.com/discussions/click.jspa?searchID=538162&messageID=4466028


packagename = Symantec Backup Exec Desktop Agent.msi
cmdline =/qf DEFAULTMEDIASERVER="NETBIOSNAME" DLODBINSTANCENAME="MSSQLSERVER" LAUNCHCLIENT="1" /l*v "%TEMP%\DLOAgentInstall.log"

Using SQL 2005. On another note, Symantec needs to release a fix that causes the DLO wizard to populate this ini file!!

[Dipesh_Mistry]

after reading the link i checked my setup.ini and it was correct, but the when installing on the client it still doesn't have the DEFAULTMEDIASERVER string set.
i set that string to the correct value but still get the V-139-52224-100 error message