{"id":722,"date":"2016-08-10T15:37:16","date_gmt":"2016-08-10T15:37:16","guid":{"rendered":"http:\/\/www.tiagoneves.net\/blog\/?p=722"},"modified":"2016-08-10T15:37:16","modified_gmt":"2016-08-10T15:37:16","slug":"erro-ao-salvar-relatorio-no-reporting-services-2016","status":"publish","type":"post","link":"https:\/\/www.tiagoneves.net\/blog\/erro-ao-salvar-relatorio-no-reporting-services-2016\/","title":{"rendered":"Erro ao salvar relat\u00f3rio no Reporting Services 2016"},"content":{"rendered":"<p style=\"text-align: justify;\">Ol\u00e1 pessoal, tudo certo?<\/p>\n<p style=\"text-align: justify;\">Fiquei ausente uns dias mas estamos de volta, hoje compartilharei um problema que tive na empresa que trabalho.<\/p>\n<p style=\"text-align: justify;\">O time de BI, resolveu implementar o Reporting Services 2016, na realidade o projeto inicial era instalar o Datazen, mas como a ferramenta foi integrada ao Reporting Services 2016, resolvemos iniciar o projeto com o Reporting Services, assim fizemos a instala\u00e7\u00e3o do SQL Server 2016 com o Reporting Service, fizemos a configura\u00e7\u00e3o com sucesso, por\u00e9m na hora de salvar os relat\u00f3rios estava dando o seguinte erro:<\/p>\n<p style=\"text-align: justify;\"><a href=\"https:\/\/i0.wp.com\/www.tiagoneves.net\/blog\/wp-content\/uploads\/2016\/08\/Erro-RS.png\" rel=\"lightbox[722]\"><img data-recalc-dims=\"1\" loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-726\" src=\"https:\/\/i0.wp.com\/www.tiagoneves.net\/blog\/wp-content\/uploads\/2016\/08\/Erro-RS.png?resize=678%2C173\" alt=\"Erro RS\" width=\"678\" height=\"173\" srcset=\"https:\/\/i0.wp.com\/www.tiagoneves.net\/blog\/wp-content\/uploads\/2016\/08\/Erro-RS.png?w=834&amp;ssl=1 834w, https:\/\/i0.wp.com\/www.tiagoneves.net\/blog\/wp-content\/uploads\/2016\/08\/Erro-RS.png?resize=300%2C77&amp;ssl=1 300w, https:\/\/i0.wp.com\/www.tiagoneves.net\/blog\/wp-content\/uploads\/2016\/08\/Erro-RS.png?resize=768%2C196&amp;ssl=1 768w\" sizes=\"auto, (max-width: 678px) 100vw, 678px\" \/><\/a><\/p>\n<p style=\"text-align: justify;\">&#8220;<em>System.Reflection.TargetInvocationException Exception has been thrown by the target of an invocation. &#8212; System.InvalidOperationException This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.<\/em>&#8220;<\/p>\n<p style=\"text-align: justify;\">Ap\u00f3s algumas consultas no nosso amigo Google, descobri que o problema era porque o FIPS estava habilitado no servidor, consultei o time de seguran\u00e7a da possibilidade de desabilita-lo, e fui informado que n\u00e3o \u00e9 poss\u00edvel por causa da pol\u00edtica de seguran\u00e7a da empresa.<\/p>\n<p style=\"text-align: justify;\">Diante do cen\u00e1rio, juntamente com o <a href=\"http:\/\/www.dirceuresende.com\/blog\/\" target=\"_blank\">Dirceu Resende<\/a>, come\u00e7amos a buscar uma solu\u00e7\u00e3o de contorno e encontramos um documento da <a href=\"https:\/\/blogs.msdn.microsoft.com\/dataaccesstechnologies\/2015\/07\/16\/report-manager-system-invalidoperationexception-this-implementation-is-not-part-of-the-windows-platform-fips-validated-cryptographic-algorithms\/\" target=\"_blank\">Microsoft <\/a>que diz que <em>&#8220;This is happening because FIPS is enabled on the Reporting Services server and Report Manager does not support the Local Security Policy \u201cSystem cryptograph&#8221;<\/em> ou seja o Reporting Services n\u00e3o \u00e9 suportado, e recomenda desabilitar a policy, o que n\u00e3o \u00e9 permitido no ambiente da empresa.<\/p>\n<p style=\"text-align: justify;\">Se voc\u00ea tiver esse problema, e puder desabilitar a policy do FIPS, basta alterar somente um registro.<\/p>\n<p style=\"text-align: justify;\">&#8220;<em>HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Control\\Lsa\\fipsalgorithmpolicy<\/em>&#8220;<\/p>\n<p style=\"text-align: justify;\">Setar o valor da chave &#8220;Enabled&#8221; para &#8220;0&#8221;.<\/p>\n<p style=\"text-align: justify;\">Como n\u00e3o posso desabilitar o FIPS, encontrei uma solu\u00e7\u00e3o de contorno no <a href=\"https:\/\/social.msdn.microsoft.com\/Forums\/sqlserver\/en-US\/6bca86c4-7e08-4dfb-a312-d6586ea686ad\/ssrs-2016-fips-algorithm-error?forum=sqlreportingservices\" target=\"_blank\">F\u00f3rum Technet<\/a>, nele a solu\u00e7\u00e3o proposta \u00e9 para editar o arquivo machine.config do .NetFrameWork (<em>C:\\Windows\\Microsoft.NET\\Framework64\\v4.0.30319\\Config<\/em>) e adicionar a seguinte configura\u00e7\u00e3o ao final do arquivo.<\/p>\n<pre class=\"theme:vs2012 lang:xhtml decode:true\">&lt;mscorlib&gt;\r\n    &lt;cryptographySettings&gt;\r\n        &lt;cryptoNameMapping&gt;   \r\n            &lt;cryptoClasses&gt;\r\n                &lt;cryptoClass\r\n                    SHA256CSP=\"System.Security.Cryptography.SHA256CryptoServiceProvider, System.Core, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089\" \/&gt;\r\n            &lt;\/cryptoClasses&gt;            \r\n            &lt;!-- name mappings --&gt;           \r\n            &lt;nameEntry\r\n                name=\"SHA256\"\r\n                class=\"SHA256CSP\" \/&gt;\r\n            &lt;nameEntry\r\n                name=\"SHA256CryptoServiceProvider\"\r\n                class=\"SHA256CSP\" \/&gt;\r\n            &lt;nameEntry\r\n                name=\"System.Security.Cryptography.SHA256CryptoServiceProvider\"\r\n                class=\"SHA256CSP\" \/&gt; \r\n            &lt;nameEntry\r\n                name=\"System.Security.Cryptography.SHA256\"\r\n                class=\"SHA256CSP\"\/&gt;      \r\n        &lt;\/cryptoNameMapping&gt;          \r\n    &lt;\/cryptographySettings&gt;\r\n&lt;\/mscorlib&gt;<\/pre>\n<p style=\"text-align: justify;\">Ap\u00f3s editar o arquivo machine.config, \u00e9 necess\u00e1rio reiniciar o servi\u00e7o do Reporting Service, recomendo que voc\u00ea fa\u00e7a um backup do arquivo antes de alterar.<\/p>\n<p style=\"text-align: justify;\">Feito o procedimento acima, conseguimos publicar os relat\u00f3rios com sucesso.<\/p>\n<p style=\"text-align: justify;\">Bom por hoje \u00e9 isso.<\/p>\n<p style=\"text-align: justify;\">Abra\u00e7os,<\/p>\n<p style=\"text-align: justify;\">Tiago Neves<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Ol\u00e1 pessoal, tudo certo? Fiquei ausente uns dias mas estamos de volta, hoje compartilharei um problema que tive na empresa que trabalho. O time de BI, resolveu implementar o Reporting Services 2016, na realidade o projeto inicial era instalar o Datazen, mas como a ferramenta foi integrada ao Reporting Services 2016, resolvemos iniciar o projeto [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"rop_custom_images_group":[],"rop_custom_messages_group":[],"rop_publish_now":"initial","rop_publish_now_accounts":{"twitter_91251433_91251433":""},"rop_publish_now_history":[],"rop_publish_now_status":"pending","_exactmetrics_skip_tracking":false,"_exactmetrics_sitenote_active":false,"_exactmetrics_sitenote_note":"","_exactmetrics_sitenote_category":0,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"advanced_seo_description":"","jetpack_seo_html_title":"","jetpack_seo_noindex":false,"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2},"_wpscppro_dont_share_socialmedia":false,"_wpscppro_custom_social_share_image":0,"_facebook_share_type":"","_twitter_share_type":"","_linkedin_share_type":"","_pinterest_share_type":"","_linkedin_share_type_page":"","_instagram_share_type":"","_medium_share_type":"","_threads_share_type":"","_google_business_share_type":"","_selected_social_profile":[],"_wpsp_enable_custom_social_template":false,"_wpsp_social_scheduling":{"enabled":false,"datetime":null,"platforms":[],"status":"template_only","dateOption":"today","timeOption":"now","customDays":"","customHours":"","customDate":"","customTime":"","schedulingType":"absolute"},"_wpsp_active_default_template":true},"categories":[2,26,138,5],"tags":[164,163,165,162,65,35,27],"class_list":["post-722","post","type-post","status-publish","format-standard","hentry","category-casos-do-dia-a-dia","category-sqlserver-2016","category-troubleshooting","category-virtual-pass-br","tag-bi","tag-datazen","tag-fips","tag-reporting-services","tag-seguranca","tag-sql-server","tag-sql-server-2016"],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/p6eIyh-bE","jetpack-related-posts":[{"id":2414,"url":"https:\/\/www.tiagoneves.net\/blog\/sql-server-2016-esta-chegando-ao-fim-do-suporte-o-que-isso-significa-na-pratica\/","url_meta":{"origin":722,"position":0},"title":"SQL Server 2016 est\u00e1 chegando ao fim do suporte: o que isso significa na pr\u00e1tica?","author":"tiagoneves","date":"27 de abril de 2026","format":false,"excerpt":"O SQL Server 2016 ter\u00e1 seu suporte estendido encerrado em 14 de julho de 2026, o que resultar\u00e1 na falta de atualiza\u00e7\u00f5es de seguran\u00e7a e suporte. Continuar usando essa vers\u00e3o traz riscos como vulnerabilidades e n\u00e3o conformidade regulat\u00f3ria. Planejar a migra\u00e7\u00e3o para vers\u00f5es mais recentes ou cloud deve ser prioridade\u2026","rel":"","context":"Em &quot;Seguran\u00e7a&quot;","block_context":{"text":"Seguran\u00e7a","link":"https:\/\/www.tiagoneves.net\/blog\/category\/seguranca\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/www.tiagoneves.net\/blog\/wp-content\/uploads\/2026\/04\/sql_server_2016_eos_v3.png?fit=772%2C702&ssl=1&resize=350%2C200","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/www.tiagoneves.net\/blog\/wp-content\/uploads\/2026\/04\/sql_server_2016_eos_v3.png?fit=772%2C702&ssl=1&resize=350%2C200 1x, https:\/\/i0.wp.com\/www.tiagoneves.net\/blog\/wp-content\/uploads\/2026\/04\/sql_server_2016_eos_v3.png?fit=772%2C702&ssl=1&resize=525%2C300 1.5x, https:\/\/i0.wp.com\/www.tiagoneves.net\/blog\/wp-content\/uploads\/2026\/04\/sql_server_2016_eos_v3.png?fit=772%2C702&ssl=1&resize=700%2C400 2x"},"classes":[]}],"jetpack_likes_enabled":true,"_links":{"self":[{"href":"https:\/\/www.tiagoneves.net\/blog\/wp-json\/wp\/v2\/posts\/722","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.tiagoneves.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.tiagoneves.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.tiagoneves.net\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.tiagoneves.net\/blog\/wp-json\/wp\/v2\/comments?post=722"}],"version-history":[{"count":6,"href":"https:\/\/www.tiagoneves.net\/blog\/wp-json\/wp\/v2\/posts\/722\/revisions"}],"predecessor-version":[{"id":730,"href":"https:\/\/www.tiagoneves.net\/blog\/wp-json\/wp\/v2\/posts\/722\/revisions\/730"}],"wp:attachment":[{"href":"https:\/\/www.tiagoneves.net\/blog\/wp-json\/wp\/v2\/media?parent=722"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.tiagoneves.net\/blog\/wp-json\/wp\/v2\/categories?post=722"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.tiagoneves.net\/blog\/wp-json\/wp\/v2\/tags?post=722"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}