Exchange Explorer Error

[digitlman]

I need some help from Gostev et al.

I have opened a case with support - 00528758.

The crux of the issue - I can use the Exchange Explorer just fine once, but the second time I launch the program and try a restore, I get the error: "The process cannot access the file 'C:\ProgramData\Veeam\Backup\ExchangeExplorer\ESE\V14\ese.dll' because it is being used by another process."

Once I reboot the server, then everything works fine for one time.

As I said, I am working with Support, and I have run Process Monitor and sent those logs. However, they have me disabling Windows Event Log, TCP/IP NetBIOS Helper, Windows Audio, and Security Center....which is akin to throwing spaghetti at the wall and seeing if it sticks.

Some input from Veeam board members would be appreciated. I don't know if I need to talk to a programmer or what.

[NightBird]

Same problem here.

Veeam B&R v7 patch3a

[digitlman]

UPDATE: Ok, now a higher-level engineer will be contacting me.

I was just irritated because it felt like I was dealing with Symantec support all over again. And anybody who has used Symantec knows that the first line support always asks you do to the dumbest shit that you know has absolutely no bearing on the problem at hand.

I am still keen to see if anybody on the Forums has seen or heard of this issue.

[digitlman]

NightBird: do you have a case open with Support?

[foggy]

R&D is aware of this issue, however there is currently no ETA on the fix or whatever. Every new support case will help to nail the problem down, so please work directly with higher tier support on that.

[Kostya]

Hi,

We are investigating this problem, so far it looks like that issue is related to Windows Event Log and Event Log Viewer. The ese.dll library is writing internal messages to the event log which leads to the observed behavior.

...but the second time I launch the program and try a restore, I get the error: "The process cannot access the file...

BTW, can you please tell me if you're targeting the same version of Exchange server during the second restore attempt?

[digitlman]

Version? Of?

I only have one instance of Veeam & Exchange Explorer, and one Exchange server. I have 2 backups - A full and an incr. I have tried different combos of order for restoring and they all have the same result.

[Kostya]

I meant to say the version of Exchange server that you're trying to restore items from. But now I see that you have only one server, so it was the same version on both runs. Thanks!

[digitlman]

The issue was ID'd and patched. Good work, Veeam!

It took about a week, all told.

With Symantec, it would have been at least a month.

[fons]

What do you mean by "the issue was ID'd" ? How did you solved this problem ?

[foggy]

IDentified. Please contact support to address the issue.

[Didi7]

Ok, I can confirm that the ESE.DLL error is happening under Veeam B&R v8.0.0.817 as well.

I have 2 backup jobs on the same Veeam B&R server for 2 different companies. When I try to do a restore from the first successful Job, I can work with the Veeam Explorer for Exchange, I can close the session and if I try to do a restore from the second job from a different Exchange server, the ESE.DLL (being used by another process) error is displayed.

The behaviour doesn't change, when I close Veeam B&R. Stopping Veeam B&R Backup Service does not solve the problem either.

I have no other idea, other than restarting the Veeam B&R Server.

Annoying.

Regards,
Didi7

[foggy]

Have you contacted support already?

[Didi7]

No, I have not. How is that done. Would be the first time for me. Is it complicated?

[foggy]

Not, at all: https://cp.veeam.com

[Didi7]

Case #00701877

Veeam B&R 8.0.0.817 reports ESE.dll in use by another process using Veeam Explorer for Microsoft Exchange on different Exchange disk backup jobs.

Regards,
Didi7

[veremin]

Hi,

Kindly, avoid creating multiple thread regarding the same problem. It's recommended to speak about the same issue within one discussion.

Thanks.

[Didi7]

Hello v.Eremin,

can you please tell me, where I did create multiple threads regarding the same problem?

Thanks

[Gostev]

This thread. Please search the forum for the error you are experiencing before creating a new topic, to avoid duplicate discussions. Thanks!

[Didi7]

I searched the forum for the error I am experiencing and found this thread, which I did not create!

Sorry to say that, but I still don't understand the problem?

Am I not allowed to post here, when I am exactly experiencing the same error, just in a new version of B&R ?

Thanks.

[veremin]

As you can see, one of your messages' header starts with "Merged" (8:41 pm), which means it was a separate topic that was created by you and meanwhile it was talking about the same issue. Due to that reason it's been merged here where you can keep posting.

Thanks.

[Didi7]

Ok, that must have been a mistake. My original intention was to post in a thread I found here. I have absolutely no explanation for what has happened here

Is it possible that a new thread is automatically created, when I include a support case number?

Otherwise, I have no clue, what happened.

Thanks

[foggy]

Nothing that worth talking about so much, instead of discussing the issue itself. Please continue working with your engineer and post your findings here, that would be much appreciated.