# DBAmp error referencing 'xp\_cmdshell'

**URL:** <https://community.cdata.com/t/dbamp-error-referencing-xp-cmdshell/277>\
**Category:** Editions\
**Tags:** article, salesforce, dbamp\
**Created:** [July 20, 2023, 7:05pm UTC](https://community.cdata.com/t/dbamp-error-referencing-xp-cmdshell/277 "2023-07-20T19:05:38Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Dani\_Moran](https://avatars.discourse-cdn.com/v4/letter/d/2acd7d/32.png) [@Dani\_Moran](https://community.cdata.com/u/Dani_Moran)\
**Post date:** [July 20, 2023, 7:05pm UTC](https://community.cdata.com/t/dbamp-error-referencing-xp-cmdshell/277/1 "2023-07-20T19:05:38Z")

</div>

The error: “Error: SQL Server blocked access to procedure ‘sys.xp\_cmdshell’ of component ‘xp\_cmdshell’ because this component is turned off as part of the security configuration for this server.”, shows up because xp\_cmdshell is not enabled for the user you have running the stored procedure. Most of the DBAmp stored procedures require xp\_cmdshell, so you’ll need to enable it for the user in question. That is an option in SQL Server, and you can find configuration instructions here: [Server Configuration: xp\_cmdshell - SQL Server | Microsoft Learn](https://docs.microsoft.com/en-us/sql/database-engine/configure-windows/xp-cmdshell-server-configuration-option?view=sql-server-ver15)