0 votes

Hello Support,

After migrating from 2017.2 to 2021.1, certain actions no longer work. If a group object is to be renamed, the message appears: The object cannot be renamed. We cannot find the reason for this. A direct renaming in the Admin Console works and the permissions in the configuration have been taken over and they look correct. Is there perhaps a useful log file?

Best regards Jo

by (170 points)
0

Hello Jo,

Sorry for the confusion, but we are not sure what exactly the issue is. Could you, please, provide all the steps you take before facing the error with screenshots (including the screenshot of the error message itself)? You can post screenshots here or send them to us at support@adaxes.com.

0

Thanks for the quick response!

I want to rename a security group of type Global

Search

image.png

Select image.png

Rename image.png

Approval image.png

Error image.png

I can not find error details

1 Answer

0 votes
by (211k points)

Hello Jo,

Thank you for the provided details. It looks like there is a business rule triggering before renaming a group that cancels the operation. To check the rule:

  1. Launch Adaxes Administration console.
  2. In the Console Tree, expand your service node.
  3. Select Logging.
  4. In the Result Pane on the right, right-click the Rename SEC-DE-ENIT_SER_COO-1235-Test_JI4 operation. image.png
  5. In the context menu, click Properties.
  6. In the Execution log section you should see the business rule that cancelled the renaming. image.png
0

The renaming is probably not logged. Other operations were logged: image.png

Earlier, I have already disabled all business rules. But that didn't change anything.

0

Hello Jo,

The renaming is probably not logged.

Are you sure that all the filters were disabled and the time period was selected to include the time when the error occurred?

To check whether the Rename object operation is logged:

  1. Launch Adaxes Administration console.
  2. In the Console Tree, expand your service node.
  3. Right-click Logging and then click Properties in the context menu.
  4. Activate the Log Settings tab.
  5. Make sure that the Rename object checkbox is cleared. image.png
  6. If the checkbox is selected, clear it, click OK, reproduce the issue and follow the instructions for checking the Execution log.

Earlier, I have already disabled all business rules. But that didn't change anything.

Does the issue occur only for the SEC-DE-ENITSERCOO-1235-Test_JI4 group or for any other group too?

0

Our Log Setting: image.png

Yes, I have already tried different groups. It always appears: The object cannot be renamed.

0

Hello Jo,

Thank you for clarifying. For further troubleshooting, please, do the following:

  1. Launch Adaxes Administration console.
  2. In the Console Tree, expand your service node.
  3. Navigate to and right-click the group.
  4. In the context menu, navigate to All Tasks and then click Export.
  5. In the dialog box that opens, select LDIF and click Next twice.
  6. On the Properties to Export step, clear the Do not export System-Only properties checkbox. image.png
  7. Click Export.
  8. Send the export file to us (support@adaxes.com).
0

Sorry for the late response. I just sent the export by email.

0

Hello Jo,

Thank you for the provided export file. The group looks fine and according to the property values there should be no issues renaming it. Could you, please, try renaming the group in Adaxes Administration console and Active Directory Users and Computers? Does it work fine?

0

That works perfectly

image.png

image.png

0

Hello Jo,

Thank you for checking. It looks like the issue occurs because the Rename operation is disabled in the Web interface settings. To remedy the issue, you need to enable the operation. For details, on how to do that, have a look at the following tutorial: https://www.adaxes.com/tutorials_WebInterfaceCustomization_DisallowCertainOperationsOnADObjects.htm.

0

Hello Serge,

Strangely, in the 2017.2 version we migrated, the check mark is not set. But here it seems to have an effect. I will keep testing it...

Related questions

0 votes
1 answer

We are attempting to use the member property in a powershell script for all groups. We get this error message on certain groups that are used as "primary". If we set another ... just shows the single member in the group in which the group is not the primary.

asked Feb 19, 2020 by mark.it.admin (1.7k points)
0 votes
1 answer

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 ... these properties are displayed for users. Has anyone else experienced this issue at all?

asked Sep 1, 2016 by Martyn (70 points)
0 votes
0 answers

Hello, When I click on a user from the web interface I get this error message at the top of the page : The search filter cannot be recognized. (Server: domainname) Before ... one for service desk). What can I do to troubleshoot and find out the cause? thanks.

asked Apr 29, 2016 by tentaal (1.1k 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

When trying to modify a user via web inerface, logged in as administrator, after selectin user, clicking on it i receive the following error: Fatal Error Length cannot be less than zero. Parameter name: length. Can you help me? Thanks, Claudio

asked Sep 3, 2012 by Claudio (20 points)
2,607 questions
2,344 answers
6,228 comments
861,160 users