02-18-2013 06:57 AM
I have Application error:Error merging delta files for file... (e0140005), event ID :10, on my Windows 2003 Application log server every second, we are using Netapp as Strorage location.
Here is what I have found on Symantec
http://www.symantec.com/business/support/index?page=content&id=TECH45924
I have also followed the article http://www.symantec.com/docs/TECH167400 for configuring the delegation.
The DLO client are still in version 6.1, we plan to migrate to version 7.0 too.
Thaks for your help.
BR
Ismail.
02-20-2013 09:36 PM
The error you are seeing could be a result of the following
1. The admin server is not able to resolve the hostname of the NAS device due to DNS settings
2. Anti-virus settings or a security setting could be preventing the maintenance server from accessing the storage location (NAS device)
02-21-2013 02:44 AM
Hi,
I have tested the hostename resoltion from the server and it work fine.
I have also disabled the our Antivirus on the server, but I've got same error messages:
Event Type: Error
Event Source: SymantecDLOMaintenanceSvc
Event Category: None
Event ID: 10
Date: 2013-02-21
Time: 11:34:20
User: N/A
Computer: LUNSWDLOADM01
Description:
Error merging delta files for file 鴐ȒLUNSOFILER02\lundlo_01$\GRP-sejese\.dlo\lunl2259\C_\Documents and Settings\sejese\Local Settings\Application Data\Microsoft\Outlook\My PST 2007.pst. WriteCompressionShim::Write.Compress failure. err: 2, remaining: 262144
Also:
Event Type: Error
Event Source: SymantecDLOMaintenanceSvc
Event Category: None
Event ID: 10
Date: 2013-02-21
Time: 11:19:29
User: N/A
Computer: LUNSWDLOADM01
Description:
Error merging delta files for file 㷐DŽLUNSOFILER02\lundlo_01$\GRP-sechhe\.dlo\lunl2404\C_\Users\sechhe\AppData\Local\Microsoft\Outlook\Mail2008.pst. DeltaMergeThread::_OnRecord.GetVersionsForFile failed for \\LUNSOFILER02\lundlo_01$\GRP-sechhe\.dlo\lunl2404\C_\Users\sechhe\AppData\Local\Microsoft\Outlook\Mail2008.pst (e0140005)
And
Event Type: Error
Event Source: MSSQL$DLO
Event Category: (4)
Event ID: 17806
Date: 2013-02-21
Time: 11:04:12
User: N/A
Computer: LUNSWDLOADM01
Description:
SSPI handshake failed with error code 0x8009030c while establishing a connection with integrated security; the connection has been closed. [CLIENT: <named pipe>]
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 8e 45 00 00 14 00 00 00 E......
0008: 12 00 00 00 4c 00 55 00 ....L.U.
0010: 4e 00 53 00 57 00 44 00 N.S.W.D.
0018: 4c 00 4f 00 41 00 44 00 L.O.A.D.
0020: 4d 00 30 00 31 00 5c 00 M.0.1.\.
0028: 44 00 4c 00 4f 00 00 00 D.L.O...
0030: 00 00 00 00 ....
BR
Ismail.
02-25-2013 01:12 AM
Hi Ismail
When delta files are transferred to the NUDF, a request is sent to the maintenance server for grooming. During this time, if the files are being transferred then the maintenance server cannot groom the files and this condition will result in 'Error merging delta files for file... (e0140005)' error. This is generally observed in the cases of very small files, such as those created by web browsers. The grooming will however be performed during the next backup.
You may try to exclude such files from getting backed up to prevent this error. If you are facing any significant consequences as a result of this error please let us know.
-Avinash
02-25-2013 01:42 AM
Hi Avinash,
Thanks for replying, unfortunately it accurs on all type of files, from pst to office document for instance.
I have found somthing interresting in the Article URL http://www.symantec.com/docs/TECH172824.
Ihave upgraded the DLO server 6.1 to 7.0, but the clients are not yet updated, I don't know if this have any impact on that issue ?
I have also opened a case for that last week, but at this time I'm allways waiting for a solution from Symantec support ( I'm little discouraged by the delay for fixing this).
BR
Ismail.
02-25-2013 09:26 PM
Hi Ismail
If you have reported the case to Tech Support, rest assured that they are working on it and revert to you with a solution or a fix.
-Avinash
03-27-2013 02:37 AM
Hi,
Still have the same error message on new DLO 7.0 server with DLO clients 7.0 !
Ismail.