How To Fix SLDW016 - Whitelist &1 is locked by a different user

SLDW016 - Overview

• Message type: E = Error

• Message class: SLDW - Messages for Central Whitelist Administration

• Message number: 016

• Message text: Whitelist &1 is locked by a different user

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

SLDW016 - Details

• The SAP error message SLDW016 indicates that a specific whitelist entry (denoted by &1) is currently locked by another user. This typically occurs in the context of managing whitelists in the SAP Landscape Directory (SLD) or when working with the SAP Data Services.
  
  Cause:
  The error occurs when:
  
  A user is currently editing or has locked the whitelist entry, preventing other users from making changes to it.
  The system may not have released the lock due to a session timeout or an unexpected termination of the previous session.
  
  
  Solution:
  To resolve the issue, you can take the following steps:
  
  
  Check for Active Sessions:
  
  Verify if the user who has locked the whitelist is still active. If possible, ask that user to log out or release the lock.
  
  
  
  Wait and Retry:
  
  Sometimes, simply waiting for a few minutes and then retrying the operation can resolve the issue if the lock is temporary.
  
  
  
  Use Transaction Codes:
  
  If you have the necessary authorizations, you can