DLO7 agent installation - push or local - errors and rollback
We just upgraded our DLO server to 7, and I am trying to upgrade our agents to the new version, as well. Upon either a push installation from the server, or a local installation on the client(s), we run into an error 1325 "Documents is not a valid short file path", and the installers rolls back all changes (including the version of the agent that was previously there). The clients are Win7 SP1 x64, the server is 2008R2. Is this a known issue with DLO 7? How can I get around this and restore our DLO backups? The event logs from a sample client are attached. (PS: I realize DLO isn't part of BE2012, but that was the closest option available in the drop down)3.4KViews1like18CommentsDLO 7.0 tries to connect only before VPN connection is established
We recently upgraded from Backup Exec DLO 2010 R3 to Symantec DLO 7.0. Now, ca. 70 % of our users don't take backups anymore. I found that the DLO client tries to connect to the DLO SQL server on startup - which fails of course because the VPN is not yet established - and then never retries. Is there any configuration setting for retry attempts? Or is there anything else we can do? After all, it worked fine with the old version. This is the log from one of the affected clients (note that ALL entries are from before the VPN was established and the server name is correct): Executable:dloclientu.exe Machine: ... User: ... Domain: ... Principle user: \... Principle domain: Process domain: ... Interactive User Name: \ Debug Mask: 0 Windows: 6.1.7601 Service Pack 1 Current directory: C:\Program Files (x86)\Symantec\Symantec DLO\DLO Windows directory: C:\Windows System directory: C:\Windows\system32 Path: C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Common Files\Roxio Shared\DLLShared\;C:\Program Files (x86)\Common Files\Roxio Shared\10.0\DLLShared\;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files\WIDCOMM\Bluetooth Software\;C:\Program Files\WIDCOMM\Bluetooth Software\syswow64;C:\Program Files (x86)\Enterprise Vault\EVClient\ 11/16/12 09:15:56 dloclientu.exe 3596: > client.cpp( 1571 ) -- LANGID == DEU -- 11/16/12 09:15:56 dloclientu.exe 3596: > client.cpp( 1803 ) BUILD INFO: Build 70049a 11/16/2012 09:15:56.910AM 11/16/12 09:15:56 dloclientu.exe 3596: E> client.cpp( 9020 ) Performing 'TechRefresh' for user . from staging area C:\.dlostaging\. 11/16/12 09:15:56 dloclientu.exe 3596: E> client.cpp( 1889 ) CClientApp::InitInstance : TechRefresh() FAILED, res = e0140007 11/16/12 09:15:57 dloclientu.exe 3216: E> xmlpersist.cpp( 104 ) Fix for MP3 to MP4 export 11/16/12 09:15:57 dloclientu.exe 3216: E> xmlpersist.cpp( 111 ) failed reading XML attribute for field GSServerLowDiskWarningPercentage: E0140007 11/16/12 09:15:57 dloclientu.exe 3216: W> shebang.cpp( 485 ) Shebang::Load failed loading DB failed loading cached settings 11/16/12 09:15:57 dloclientu.exe 3216: E> xmlpersist.cpp( 104 ) Fix for MP3 to MP4 export 11/16/12 09:15:57 dloclientu.exe 3216: E> xmlpersist.cpp( 111 ) failed reading XML attribute for field GSServerLowDiskWarningPercentage: E0140007 11/16/12 09:16:20 dloclientu.exe 3216: > adoutil.h( 70 ) Connection error: 80004005( 00000011 ) : [DBNETLIB][ConnectionOpen (Connect()).]SQL Server existiert nicht oder Zugriff verweigert. 11/16/12 09:16:20 dloclientu.exe 3216: E> adodb.cpp( 608 ) failed opening connection: ADODBError-_com_error: foundationerror=cc000064, comerr=80004005, nativeerror=17, conn=Provider=SQLOLEDB;Initial Catalog=DLO;Integrated Security=SSPI;Net=dbnmpntw;Address=\\SERVER\pipe\MSSQL$DLO\sql\query;Connect Timeout=20, query=, msg=Unbekannter Fehler, src=Microsoft OLE DB Provider for SQL Server, desc=[DBNETLIB][ConnectionOpen (Connect()).]SQL Server existiert nicht oder Zugriff verweigert. 11/16/12 09:16:20 dloclientu.exe 3216: E> adodb.cpp( 1232 ) ADODB::ExecuteQuery failed, caught ADODBError: ADODBError-_com_error: foundationerror=cc000064, comerr=80004005, nativeerror=17, conn=Provider=SQLOLEDB;Initial Catalog=DLO;Integrated Security=SSPI;Net=dbnmpntw;Address=\\SERVER\pipe\MSSQL$DLO\sql\query;Connect Timeout=20, query=, msg=Unbekannter Fehler, src=Microsoft OLE DB Provider for SQL Server, desc=[DBNETLIB][ConnectionOpen (Connect()).]SQL Server existiert nicht oder Zugriff verweigert. 11/16/12 09:16:20 dloclientu.exe 3216: E> xmlpersist.cpp( 104 ) Fix for MP3 to MP4 export 11/16/12 09:16:20 dloclientu.exe 3216: E> xmlpersist.cpp( 111 ) failed reading XML attribute for field GSServerLowDiskWarningPercentage: E0140007 11/16/12 09:16:20 dloclientu.exe 3216: W> shebang.cpp( 485 ) Shebang::Load failed loading DB SQL load failure - probably no user 11/16/12 09:16:41 dloclientu.exe 3216: > adoutil.h( 70 ) Connection error: 80004005( 00000011 ) : [DBNETLIB][ConnectionOpen (Connect()).]SQL Server existiert nicht oder Zugriff verweigert. 11/16/12 09:16:41 dloclientu.exe 3216: E> adodb.cpp( 608 ) failed opening connection: ADODBError-_com_error: foundationerror=cc000064, comerr=80004005, nativeerror=17, conn=Provider=SQLOLEDB;Initial Catalog=DLO;Integrated Security=SSPI;Net=dbnmpntw;Address=\\SERVER\pipe\MSSQL$DLO\sql\query;Connect Timeout=20, query=, msg=Unbekannter Fehler, src=Microsoft OLE DB Provider for SQL Server, desc=[DBNETLIB][ConnectionOpen (Connect()).]SQL Server existiert nicht oder Zugriff verweigert. 11/16/12 09:16:41 dloclientu.exe 3216: E> client.cpp( 3846 ) error loading database ADODBError-_com_error: foundationerror=cc000064, comerr=80004005, nativeerror=17, conn=Provider=SQLOLEDB;Initial Catalog=DLO;Integrated Security=SSPI;Net=dbnmpntw;Address=\\SERVER\pipe\MSSQL$DLO\sql\query;Connect Timeout=20, query=, msg=Unbekannter Fehler, src=Microsoft OLE DB Provider for SQL Server, desc=[DBNETLIB][ConnectionOpen (Connect()).]SQL Server existiert nicht oder Zugriff verweigert. - Verbindung mit DLO-Administrationsserver kann nicht hergestellt werden. 11/16/12 09:16:41 dloclientu.exe 3216: E> Client.h( 1076 ) CClientApp::_HandleError() : displaying error message: Die Konfigurationseinstellungen konnten nicht geladen werden. Sie sind entweder nicht mit dem Netzwerk verbunden, oder der Server reagiert nicht. DLO muss eine Verbindung mit dem Server herstellen k÷nnen, um diesen Vorgang auszuf³hren. 11/16/12 09:16:41 dloclientu.exe 3216: E> Client.h( 1089 ) CClientApp::_HandleError() : no UI or UI is hidden. returning... 11/16/12 09:16:41 dloclientu.exe 3216: E> Client.h( 1109 ) CClientApp::_HandleError() : error shown. returning. 11/16/12 09:16:41 dloclientu.exe 3216: E> client.cpp( 2340 ) CClinetApp::StartupThread : InitializeDB FAILED result=CC000064 - THROWING res. 11/16/12 09:16:41 dloclientu.exe 3216: W> client.cpp( 2509 ) CClientApp::StartupThread : Caught param error exception, m_id=CC000064, ClientApp::StartupThread.InitializeDB - Verbindung mit DLO-Administrationsserver kann nicht hergestellt werden. 11/16/12 09:16:41 dloclientu.exe 3596: E> client.cpp( 1899 ) CClientApp::InitInstance : Initialize FAILED, res=34225521643KViews0likes3CommentsHow can change credentials for services in my symantec dlo server?
Hi, I wish to know if there are a way to change the credentials (user/password) that I used to install my symantec dlo server, When I installed, I used the default domain administrator, I want to change to an user like dloadmin with admin privilegies because the default domain administrator account is going to be disabled. I have the symantec dloconsole on a windows server 2012 std and I running the version of DLOSymantec_Desktop_and_Laptop_Option_80075a_64-bit I don't want to reinstall the clients one by one, I dont want to reinstall my windowsserver. Thanks for your supportSolved2.6KViews0likes9CommentsError when I try to install the client version 7.0 of the DLO: error V-138-52224-100.
I received the following error when I try to install the client version 7.0 of the DLO: V-138-52224-100. - I have already migrated to the BE 2010 BE 2012 - Installed updates - Migration Manual DLO.mdf and DLO_log.ldf (successful tech article 186484) - Execution of the following support to solve the problem: tech article 75773 (unsuccessfully) tech article 185776 (unsuccessfully) THE OS is Windows 2008 64-bit and 64-bit clients are Windows Sever Professional Can you help with any other suggestions? thank you very much2.3KViews0likes8Comments- 2.3KViews0likes12Comments
DLO Upgrade 7.0 to 7.6
We are planning an upgrade from 7.0 to 7.6 very soon. Once the server has been upgraded, are the 7.0 desktop agents still able to perform backups before they receive the updated 7.6 Agent, or are they essentially disabled until then? Also, am I correctly interpreting the 7.6 Admin Guide to say that publishing the update via DLOcommandu.exe will not work for Windows 7 x64 systems? Further, if we were migrating the DLO SQL database from one MS SQL database server to another, would we be able to just update the setup.iniin the Agent install folder, and simultaneously update both the desktop agent and its pointer to the correct SQL database? Thanks, -JeffSolved1.5KViews2likes7CommentsMigrating DLO server from Windows 2003 to Windows 2008
Hi, I must migrate our DLO servers 6.1 (windows 2003+SQL 2005) to a new platform that will be Windows 2008 R2 with SQL 2008R2 and DLO 7.0. We have near 1000 users on one DLO server, and 500 users on the second server. Is where a best practice for this operation ? My idea was to install two new 2008 servers with SQL 2008 R2 first. Update the old DLO 6.1 servers to 7.0 in order to have the same version. Import the database of the old servers with: > DLODBUtils -backup Remove the old server, insert the new server in AD, change the servername (in order two have the same name as before). use >DLODBUtils -restore, in order to restore all the configuration of DLO in the new server. Please give me your point of view about this process. Thanks. Ismail.Solved1.5KViews1like9CommentsHow to migrate the Symantec DLO 7.5 SP1 to a new server with different IP and Host Name.
Hi, Actually i have migrated the Symantec DLO 7.5 SP1 to a new server with different IP and Host Name, by restoring the DLO.mdf and DLO.ldf data files but after migration, the clients are not able to communicate with the new server. And after troubleshooting I found the DBServer name on clients in the registry was remain same(Old Server Host Name). If we change the DBServer Name then the Backup runs on Windows XP, but On Windows 7 machine its not working thereafter client get disabled after changing the DBServer Name in registry. So Please help me to get out of it. Is there any other way to migrate the SDLO 7.5 SP1. Thanks, Ashish Agrawal ACPL Systems Pvt. Ltd.1.5KViews2likes7Comments