Changing OU of a user fails logon attempt to PRTG on first try

Modified on 2025-06-10 14:34:58 +0200

Hi,

We have recently had a user that has changed departments within the company and subsequently has changed OU.

Since then, the first log on attempt fails, but subsequent login works ok.

Error in log shows....

20/12/2012 08:35:52 Webserver: ADsOpenObject1(LDAP:company.com/CN=User Name,OU=Department,OU=Sub Department,OU=Employees,OU=Company,DC=company,DC=com): 80072030: There is no such object on the server

It appears to have cached the location on the user, OU=Department is wrong in the log.

Any thoughts?

Phil....

Article Comments

Attention: This article is a record of a conversation with the Paessler support team. The information in this conversation is not updated to preserve the historical record. As a result, some of the information or recommendations in this conversation might be out of date.

Hello,

this unfortunately is an issue that should be fixed in one of the next stable builds. Please bear with us.

best regards.

Dec, 2012 - Permalink

Disclaimer:
The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.

Changing OU of a user fails logon attempt to PRTG on first try

Article CommentsAttention: This article is a record of a conversation with the Paessler support team. The information in this conversation is not updated to preserve the historical record. As a result, some of the information or recommendations in this conversation might be out of date.

Search

Attention

Related Articles

Article Comments

Attention: This article is a record of a conversation with the Paessler support team. The information in this conversation is not updated to preserve the historical record. As a result, some of the information or recommendations in this conversation might be out of date.