0 votes

On rare occasions, I get the following message when viewing the exchange properties;

'The operation cannot be executed by any available API.'

This only happens to a few users, but happens all the time for them and therefore unable to manage exchange properties via Adaxes. The users concerned have either a full mailbox or a contact object. On the most part however, these properties are displayed for users.

Has anyone else experienced this issue at all?

by (70 points)

I am receiving the same error with Adaxes 2018.2 and Exchange 2013. Same thing, only happens on about 10 percent of objects. Did you ever get a resolution on this?

Seems like this post has been viewed quite a bit...hopefully someone has had luck.



Could you, please, specify whether you have a hybrid environment or only Exchange Online/on-premise?

For troubleshooting purposes, enable tracing of requests sent to Exchange Servers, reproduce the error and send us (support[at]adaxes.com) the log file. For information on how to enable the tracing, see: http://www.adaxes.com/help/?HowDoI.Perf ... uests.html.

Also, could you specify for which types of objects the issue occurs? Does it happen only for users/groups or for multiple types of objects?


Thanks for the quick response!

I enabled tracing per the link provided and was able to view activity when the command to view exchange properties ran successfully.

However, when I come across an object that receives the error, no log activity is observed.

The issue seems to only occur on groups.....I checked about 30 users and everything went as expected along with good log activity. I couldn't get more than a few groups before hitting the error....I would have to say it affects more than 50 percent of groups at this point.

Additionally, I have Adaxes servers in 3 other locations and they all error on the same groups.

We are running Exchange on-premise in an isolated network....due to the nature of our business, I will not be able to provide logs.

Thanks again for your help.

1 Answer

0 votes
by (257k points)
selected by
Best answer


Thank you for the provided details.

It looks like the issue occurs because Exchange version is not specified for the groups that have the error. We recommend you to try executing the following command in Exchange management shell for one of the groups and then check whether the issue still persists. If everything works fine after executing the command, execute it for other groups that have the error.

Set-DistributionGroup –ForceUpgrade

For more details about the cmdlet, see https://docs.microsoft.com/en-us/powers ... xchange-ps.


That worked!


Thanks for your help!

Related questions

0 votes
1 answer

what its trying to do? GET, POST..etc...?

asked Apr 6 by scotthoffman (20 points)
0 votes
1 answer

I'm looking to find any Python examples of using the REST API. An Internet search didn't turn anything up.

asked Nov 25, 2021 by swengr59 (60 points)
0 votes
1 answer

Can you clarify the answer as it's a bit confusing? Will there be new major release available this month?

asked Nov 17, 2022 by ColinB (180 points)
0 votes
0 answers

Hi, Not worked with Adaxes before and just as I joined company we've had domain migration in place. After migration, whenever we want to access Exchange properties of a user ... works fine across domain..? Any ideas, however basic they may be?? regards Robert

asked Oct 16, 2019 by roberttryba (70 points)
0 votes
1 answer

Error occurs when trying to use SSPR from self-service web interface and from the Windows login screen. Has anyone seen this before? I haven't been able to ... configured exactly how it is laid out here: https://adaxes.com/help/ConfigurePasswordSelfService/

asked Apr 19 by dhodgin (20 points)
3,175 questions
2,878 answers
507,609 users