{"id":116,"date":"2018-05-25T03:39:56","date_gmt":"2018-05-25T03:39:56","guid":{"rendered":"http:\/\/michaelschultz.net\/tech\/?p=116"},"modified":"2018-06-28T21:47:13","modified_gmt":"2018-06-28T21:47:13","slug":"translating-error-codes-to-error-messages-in-our-configman-reports","status":"publish","type":"post","link":"https:\/\/michaelschultz.net\/tech\/translating-error-codes-to-error-messages-in-our-configman-reports\/","title":{"rendered":"Translating error codes to error messages in your ConfigMgr reports."},"content":{"rendered":"

I was recently working on a set of custom reports on the configuration baseline and configuration item compliance. I noticed some systems failed on a few configuration items so I decided to bring in the ErrorCode info in from the v_CIErrorDetails view.\u00a0 Unfortunately, as nice as error codes are to have, we don\u2019t know what all of them mean so plain text reason for an error is helpful. \u00a0I am going to show you one way to do just that.<\/p>\n

First, I am going to run a short SQL query to show some of the error codes I am talking about and what they look like.<\/p>\n

I run the following and as you can see -2147467262 doesn\u2019t tell you a lot.<\/p>\n

SELECT<\/span> DISTINCT<\/span> ResourceID,<\/span> ErrorCode
\nFROM<\/span>\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 v_CIErrorDetails
\nORDER<\/span> BY<\/span> ErrorCode<\/div><\/div>\n

\"\"<\/p>\n

Let\u2019s take that same query and use Report Builder to make a report out of it. I did alter it to just select the TOP(1).<\/p>\n

Here is what it looks like in Report Builder<\/p>\n

\"\"<\/p>\n

And here is the report<\/p>\n

\"\"<\/p>\n

We need to reference SrsResources.dll and use an expression to convert the error code to the text found in the DLL.<\/p>\n

Right click in an area outside of the report and go to Report Properties. Go to References and Add a new assembly.\u00a0 Type in the following:<\/p>\n

SrsResources, culture=neutral<\/strong><\/p><\/blockquote>\n

And click OK.<\/p>\n

\"\"<\/p>\n

Next we need to alter the value of the ErrorCode with an expression to use the assembly and convert the error code. Right click on [ErrorCode} and select Expression.\u00a0 Replace the currect expression with =SrsResources.Localization.GetErrorMessage(Fields!ErrorCode.Value,”en-US”)<\/strong> but the Field may different for your report.\u00a0 For me the column is ErrorCode. Click OK and rerun the report.<\/p>\n

\"\"<\/p>\n

The report now shows the error message text and not the error code.<\/p>\n

\"\"<\/p>\n

I took it a little further and included the error codes in two columns using the following query.<\/p>\n

SELECT<\/span> DISTINCT<\/span> ResourceID,<\/span> ErrorCode AS<\/span> 'Message'<\/span>,<\/span> ErrorCode
\nFROM<\/span>\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 v_CIErrorDetails
\nORDER<\/span> BY<\/span> ErrorCode<\/div><\/div>\n

I use this this expression on the Message field<\/p>\n

=SrsResources.Localization.GetErrorMessage(Fields!Message.Value,”en-US”)<\/strong><\/p><\/blockquote>\n

And now I have the error code and the error message.<\/p>\n

\"\"<\/p>\n

Here are a few links for further information.<\/p>\n