EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB18737: Unable to execute report against Microsoft SQL Server Warehouse due to error ''Execution of user code in the .NET Framework is disabled'


Community Admin

• Strategy


Unable to execute report against Microsoft SQL Server Warehouse due to error ''Execution of user code in the .NET Framework is disabled'

SYMPTOM:
The following error is obtained when running a report against a Microsoft SQL Server Warehouse:
 

ka04W000000OdqPQAS_0EM440000002Eqf.jpeg

 
Error in report results
Your request could not be processed. Please try again. If the problem persists, contact the Administrator.
(QueryEngine encountered error: Execute Query failed. Error type: Odbc error. Odbc operation attempted: SQLExecDirect. Execution of user code in the .NET Framework is disabled. Enable "clr enabled" configuration option. Error in Process method of Component: QueryEngineServer, XXX, job xxx, Error Code= -2147212544)
CAUSE:
In order to execute user code on SQL server, the option 'clr enabled' has to be enabled on the Microsoft SQL Server.
 
For more information on the 'clr enabled' option, refer to the following page:
 
http://msdn2.microsoft.com/en-us/library/ms175193.aspx
 
ACTION:
On the Microsoft SQL Server, follow the steps below to resolve this issue:
 

  • Explore 'SQL Server 2005/Configuration Tools/Surface Area Configuration' in the Start menu, as shown below:
ka04W000000OdqPQAS_0EM440000002Eqh.jpeg
  • Select 'Surface Area Configuration for Features.'
  • There will be a 'CLR Integration' option. Activate it and save, as shown below:
ka04W000000OdqPQAS_0EM440000002Eqc.jpeg
  • Restart Strategy Intelligence Server and try to execute the report again.

Comment

0 comments

Details

Knowledge Article

Published:

June 15, 2017

Last Updated:

June 15, 2017