Acronis Recovery for Microsoft Exchange: Member invoke failed

Are there no acronis support engineers reading this support forum?

Hello Site Woondiensten,

Thank you for using [[http://www.acronis.com/enterprise/ | Acronis Corporate Products]]

This error message can be ignored, it doesn't influence the backup file integrity. In the next released build we will get rid of this error message.

Thank you.

Hello. I know, but the logging we get emailed only is mentioning the error. That way we cannot see if the backup

is successful, is giving an error, and how long the backup time was.

In old posts I see that acronis is familiar with this error for a while now, and the build 220 is released a month ago.

So I do not know why you haven't fixed this problem already, and really would like to know when we can expect a new release which will fix this error.

Michiel

Hello Michiel,

Thank you for your response.

The exact date is unknown. We release a new build when the appropriate team creates a stable build of the program.

Thank you.

Is there any news regarding a newer version of this software?
It’s over a month ago since my last question, and still there is no newer build.
So I’m a little concerned about the priority of this build, because it’s should
take that long to fix this bug.

I have been getting these messages when backing up our exchange server and sql servers. I am really not comfortable with the backup images of knowing and seeing the error messages. I am sure there are a lot of bugs that needed to to be fixed for the next build. Please keep up posted.

"This error message can be ignored, it doesn't influence the backup file integrity."

Oleg,
Please do understand, that nobody can sustain a backup policy only with this argument. From a managing perspective, a backup report indicating errors = no backup. (no matter what a sys admin says)

After all this time without fixing this, i am really not sure this is only an output misplaced message error as you said.

I confirm these last posts...

Another thing is that I have problems with paying for software and support
when bugs are not fixed in a few weeks, and certainly not 5 months...
I do not understand that acronis is not sharing this feeling...

I always liked acronis products and we use a lot of their software, but some
support and the speed of bug fixing are some points of improvement to keep
me exited !

I am glad to see others have the same opinion as mine on this issue. I have purchased MANY Acronis products and have always had the same experience. Paying for priority support gives me nothing. I get the same results as far as taking a LARGE amount of time. I was a beta tester on the exchange product and purchased it as soon as it came out. It hasn't worked since. That was....oh....Feb 2009!! And yes, I have opened numerous cases on issues and never a fix. It still will not create info store backups and I am forced to create brick levels with all the same including some more errors. I have never really had a successful backup as I agree with the above post that errors=no backup!! And, for such a new product and for the price, there better be fixes in a shorter timeframe than 5 months!!

This STILL hasnt been fixed.

I am using acronis for exchange (the latest version) and the message keeps coming up.

Dear customers,

First of all, I'd like to apologize for the inconvenience you experienced waiting for a fix to this issue. The cause of this delay is that we were not able to reproduce this issue on 32-bit operating systems, that's why it took such a long time to create the correct environment and escalate this issue to Development Team. For now, we have enough information to fix this situation. The process is not stalled and we're working on it.

Now, regarding the issue itself: since the new build with the fix is not compiled, we have requested a workaround for the current builds. I will share it here as soon as we get it.

Once again, I'm very sorry for this situation...

Regards,

Has there been any forward movement on a workaround for this issue? I am also receiving the following error message:

Backup task [XXX] [IS backup] on computer XXX completed with errors.
Member invoke failed, Failed to create incremental backup of storage group 'First Storage Group' from Microsoft Exchange Server 'XXX'., ESE adapter server raised error: The database missed a previous full backup before the incremental backup. , The system returned error: ` (3,355,443,760)`.

hello,

can this be fixed please.

Over a month now, and still nothing fixed or workaround available.
Over 3 months old when I first posted this problem.

Can only conclude that acronis is delivering very bad service/support
concerning this product. It should never have been released like this.

Hello all,

I'm sorry for the delayed response.

I have tracked the task for this time and want to let you know that the issue with "Member invoke failed, Unable to access operation system directories" error message has been fixed. It will be available in next release of Acronis Recovery for MS Exchange.

I'm sorry for the inconvenience.

Regards,

And when should this new release be available?

Rg
Michiel

Hello Michiel,

Unfortunately, we are not aware of the exact release date.

However, I have sent you the workaround solution via PM.

Thank you!

hi,

i need this workaround please. i am getting tired of "failed" errors.

Thanks Alexander. Applied it, and have to reboot the server this evening anyway. I will know tomorrow if this workaround is working.

Do I have to restore the original dll before updateing to the new release when it's available?

Alexander,

Can you please provide me with the work around for the member invoke failure error.

Thanks,
Nick

Error message is gone, and finally we have a normal report email..

I too am having the "member invoke failed" error when trying to back up information stores. I have tried a reinstall of the agent, restarting the services and rebooting the server. Can someone please advise how to solve this problem? I have not had one hassle free back up since I bought this product.

hi,

im getting tired of this now!

i want to know the workaround please, we purchased premium support, and the software cost over £450!

" .Site Woondiensten
Offline
Beginner
Joined: 2009-09-24
Posts: 11 Error message is gone, and finally we have a normal report email.. "

if this person has it, why not post the workaround online, before everyone moves to backup exec.

Could you sent me a fix too.
Mine shows the failed error, but gives no option to proceed anyway. It just kills the backup.

Thanks,
B.

Add me to the list i need this work around i don't understand the secrecy why not just post it here in the forums.

Thank you

Hello all,

Let me clarify the situation regarding the fix.

The possible fix is available only for the error "Member invoke failed, Unable to access operation system directories" in the product, with the following steps to reproduce:

Create task to full Information Store backup with
Acronis Recovery for Microsoft Exchange and Operation fails with
"Unable to access operation system directories." line_tag="0xDCDAF24D3C1CC7E0" in log, but backup is created.

1. Actual solution is in dynamic library file replacement, and we haven't published it yet because we must confirm that it works in all cases. This fix is very custom, and we won't be able to publish it for the common access until its 100% confirmed. I'm sorry for the inconvenience.

2. The same issue can be caused by IPv6 protocol is not enabled, for example. When we connected to console by user member of Administrators, and trying to create Disaster Recovery Plan, after pressing Finish we receive the same error.

In this case, we should try to resolve computer name. Ping your PC with its domain name. If it shows address ::1 - you should enable (or install) IPv6 on your Windows system. The description is available here.

Please let me know if you need any further assistance.

Regards,

I am a paying customer, with "PREMIUM SUPPORT"

i want this dll, and instructions please.

this is completely unacceptable.

Our issue was the IPv6 issue a vendor disabled it while we were migrating our exchange box re-enabling it fixed the issue.

Thank you,

this is a known issue with the software, which "everyone" is having.

why cant you just release a patch....

Hello all!

First of all thank you for your comments and finding time to post into this thread.

Dear Gary, I entirely share your concern and I wish we could assist you with it, but currently this "dll solution" is still being tested as well as the next build currently is in process of testing - we need to make sure that all was fixed in the newer build and you will not face any issues with it.

I will forward your comment to the Experts and Development team - this will speed up the process. I will keep the thread posted regarding the process of releasing the solution.

Todd, thank you for letting us know that the issue got resolved - it is really very pleasant to hear.

Should you have any further questions or concerns - please, feel free to share them with us, we will be happy to help you!

Thank you.

the full product "doesnt work", so i dont really care about testing some beta code.

how long have we been waiting for this to be fixed.

Hello Gary,

I'm sorry for the inconvenience.

I have sent you the information via PM, but as we stated several times before: it's not guaranteed that it will fix the situation you experience.

Anyway, please share the results here so we can proceed with the investigation.

Thank you.

hi,

thanks for sending it on.

please post it on here for the other people to use. why be so secretive?

also, dont you have any technical people testing this? why do you need our help to "investigate" this issue. its a known issue, which you claim to fix in the "next release", which is due in 2020 i believe....

Oleg said the following:

This error message can be ignored, it doesn't influence the backup file integrity. In the next released build we will get rid of this error message.

1. Your DLL change doesnt work.
2. if its an error message that can be ignored, why not just create a patch to change the error reporting?!?!
3. this "service" is completely unacceptable.

how can we be expected to backup an exchange infrastructure using software this buggy???

There are 2 months gone again, and still no new release.
Besides that we need exchange 2010 support soon, and there is no news when this support
will get available. Software with this support should be a lot cheaper than it is...

Hello Gary and Site.

Thank you for being sincere in your feedback.

Gary, as it was already mentioned - this *dll doesn't guarantee to fix the situation, that's why we still do not have it available for all the customers. Also you have mentioned

I am a paying customer, with "PREMIUM SUPPORT"

I regret you had to wait for a solution on Forum for a long time and be sure we will keep tracking it so that you could receive a reply on time. In addition I'd like to mention that in case of emergency you can contact support directly - they will definitely provide you with immediate assistance.

if its an error message that can be ignored, why not just create a patch to change the error reporting?!?!

Thank you for the reasonable suggestion! I have forwarded it to the Development team, so I believe that currently they are working on it.

Site, I completely understand your concern and wish I could do anything, but release date depends on our Development team. We've forwarded the speed-up request to them, but still weren't provided with any timeframes.

Nevertheless if you would like to share your concerns with us and the management team you can also send your comments to the e-mail address specified here. Be sure all your suggestions and feedback will be taken under consideration and properly addresses.

Meanwhile we will continue tracking the update process and keep you posted.

Thank you for understanding.

"I regret you had to wait for a solution on Forum for a long time and be sure we will keep tracking it so that you could receive a reply on time. In addition I'd like to mention that in case of emergency you can contact support directly - they will definitely provide you with immediate assistance."

No they won't......

I called them, and they said it was a "known issue".

How can you sell a backup solution that doesnt report if its working or not?
How did this pass through "testing" ?

Surely someone would have noticed that every backup "fails", yet you still released this product, knowing full well that it doesnt work as it is marketed!

Hello Gary,

I understand that this is not convenient for you.

Once again i specially marked the part of my response that .dll solution may not help with this issue. That answers the question why we haven't released it officially. It's still on work with Development Team.

Also, we have informed you several times that this issue is known and we're working to get an absolute fix for it. Support department is not able to get all issues fixed at one time. We just gather the common opinion and forward them to the responsible departments.

Yana told me that you have asked to escalate your case. We can do so easily, but I was not able to find any case in our database. Please provide me with its number so we can work with facts in our hands.

We are looking forward to hearing back from you at your earliest convenience.

Thank you.

how bout i tell you i have the Backup task failed. Reason: Unable invoke this member. Parent is not interface on the SQL recovery too