{"id":6900,"date":"2021-11-09T21:35:32","date_gmt":"2021-11-10T01:35:32","guid":{"rendered":"https:\/\/kevinjustin.com\/blog\/?p=6900"},"modified":"2021-11-09T21:36:10","modified_gmt":"2021-11-10T01:36:10","slug":"fixsql2017plus-netassemblyerror","status":"publish","type":"post","link":"https:\/\/kevinjustin.com\/blog\/2021\/11\/09\/fixsql2017plus-netassemblyerror\/","title":{"rendered":"Weird SQL issue from SCOM DB move"},"content":{"rendered":"
\"Fix<\/a>
BillMurry-ThatsWeird<\/figcaption><\/figure>\n

This post is courtesy of Andres Naranjo<\/a><\/p>\n

 <\/p>\n

Fix SQL2017+ .NET assembly error<\/strong><\/h3>\n

Weird SQL issue from SCOM DB move to new SQL servers<\/strong><\/h4>\n

Fix SQL2017+ .NET assembly errors after moving DB’s to new SQL servers.<\/p>\n

 <\/p>\n

Scenario:<\/strong> Moved the SCOM 2019 databases from a SQL 2014 database engine to a SQL 2019 database engine.\u00a0 SQL ApplicationThe following error occurred when opening the SCOM admin console:<\/p>\n

 <\/p>\n

Operations Manager Event Log, Event ID 26317<\/strong><\/p>\n

Date: 10\/22\/2021 11:17:27 AM<\/p>\n

Application: Operations Manager<\/p>\n

Application Version: 10.19.10505.0<\/p>\n

Severity: Error<\/p>\n

Message:<\/p>\n

 <\/p>\n

An error occurred in the Microsoft .NET Framework while trying to load assembly id 65537<\/span>. The server may be running out of resources, or the<\/span> assembly may not be trusted<\/span>. Run the query again, or check documentation to see how to solve the assembly trust issues. For more information about this error:<\/span><\/p>\n

System.IO.FileLoadException: Could not load file or assembly ‘microsoft.enterprisemanagement.sql.userdefineddatatype, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null’ or one of its dependencies. An error relating to security occurred. (Exception<\/span> from HRESULT: 0x8013150A)<\/span><\/p>\n

System.IO.FileLoadException:<\/span><\/p>\n

at System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)<\/span><\/p>\n

at System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity,<\/span> RuntimeAssembly reqAssembly, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)<\/span><\/p>\n

at System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean forIntrospection)<\/span><\/p>\n

at System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)<\/span><\/p>\n

at System.Reflection.Assembly.Load(String assemblyString)<\/span><\/p>\n

 <\/p>\n

Fix SQL2017+ .NET assembly<\/strong><\/p>\n

In addition, Operations Manager event ID’s 26317 events document the error (also check SQL Application log, see Holman’s blog<\/a>).\u00a0 Here is an example from the Operations Manager event log:<\/p>\n

\"Screenshot<\/a>
Operations Manager event log, EventID 26319<\/figcaption><\/figure>\n

 <\/p>\n

 <\/p>\n

Weird SQL issue from SCOM DB move to new SQL servers<\/strong><\/h3>\n

Cause:<\/strong><\/p>\n

Starting with SQL 2017, SQL restricts trusted managed assemblies.<\/p>\n

See more details in Microsoft TechNet article here<\/a><\/p>\n

First, ensure that SQL CLR execution is enabled with the following SQL query:<\/p>\n

 <\/p>\n

sp_configure @configname=clr_enabled, @configvalue=1<\/span>
\nGO<\/span>
\nRECONFIGURE<\/span>
\nGO<\/span><\/p>\n

 <\/p>\n

NOTE: It is important to make sure the SQL Server Service is re-started after the query above.<\/strong><\/span><\/p>\n

 <\/p>\n

Second, execute ‘add trusted’ stored procedure queries to mark both as trusted:<\/p>\n

 <\/p>\n

EXEC sp_add_trusted_assembly 0xFAC2A8ECA2BE6AD46FBB6EDFB53321240F4D98D199A5A28B4EB3BAD412BEC849B99018D9207CEA045D186CF67B8D06507EA33BFBF9A7A132DC0BB1D756F4F491<\/span><\/p>\n

EXEC sp_add_trusted_assembly 0xEC312664052DE020D0F9631110AFB4DCDF14F477293E1C5DE8C42D3265F543C92FCF8BC1648FC28E9A0731B3E491BCF1D4A8EB838ED9F0B24AE19057BDDBF6EC<\/span><\/p>\n

 <\/p>\n

 <\/p>\n

Verify assemblies are successfully registered as trusted run:<\/p>\n

Select * from sys.trusted_assemblies<\/span><\/p>\n

 <\/p>\n

The output should look like this:<\/p>\n

\"SQLTrustedAssemblies<\/a><\/p>\n

 <\/p>\n

At this point, re-start the SCOM services System Center Data Access, and System Center Management Configuration, on all management servers, and re-launch the SCOM admin console to make sure everything is working properly.<\/p>\n

 <\/p>\n

Quicker ways to start SCOM services<\/strong><\/h3>\n

From PowerShell<\/strong> (as Admin)<\/p>\n

restart-service healthservice; restart-service omsdk; restart-service cshost<\/span><\/p>\n

 <\/p>\n

Leverage Invoke-Command<\/strong><\/p>\n

# Invoke-Command syntax is PoSH remoting is enabled<\/p>\n

#<\/p>\n

# Run on multiple servers<\/p>\n

# From PowerShell on SCOM Mgmt server, where you have same credential\/access<\/p>\n

# Example 1<\/strong><\/p>\n

“server1”,”server2″| % {invoke-command $_ -scriptblock {$env:ComputerName; restart-service healthservice; restart-service omsdk; restart-service cshost; get-service healthservice; get-service omsdk; get-service cshost }}<\/span><\/p>\n

 <\/p>\n

# Example 2<\/strong><\/p>\n

# Restart healthservice on MS\/Agent<\/p>\n

“server1”,”server2″| % {invoke-command $_ -scriptblock {$env:ComputerName; restart-service healthservice; restart-service omsdk; restart-service cshost; get-service healthservice; get-service omsdk; get-service cshost\u00a0}}<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"

This post is courtesy of Andres Naranjo   Fix SQL2017+ .NET assembly error Weird SQL issue from SCOM DB move to new SQL servers Fix SQL2017+ .NET assembly errors after moving DB’s to new SQL servers.   Scenario: Moved the SCOM 2019 databases from a SQL 2014 database engine to a SQL 2019 database engine.\u00a0 … Continue reading “Weird SQL issue from SCOM DB move”<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[556,11],"tags":[561,559,511,505,560,410,562,557,558],"class_list":["post-6900","post","type-post","status-publish","format-standard","hentry","category-sql","category-troubleshooting","tag-561","tag-move-scom-databases","tag-mssql","tag-scom2019","tag-scom2022","tag-sql","tag-sql-application-log","tag-sql2014","tag-sql2017"],"yoast_head":"\nFix SQL2017+ .NET assembly<\/title>\n<meta name=\"description\" content=\"Check SQL .NET assemblies to see if trusted for SQL2017+. Use this to resolve Operations Manager Event ID 26319 events\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/kevinjustin.com\/blog\/2021\/11\/09\/fixsql2017plus-netassemblyerror\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Fix SQL2017+ .NET assembly\" \/>\n<meta property=\"og:description\" content=\"Check SQL .NET assemblies to see if trusted for SQL2017+. Use this to resolve Operations Manager Event ID 26319 events\" \/>\n<meta property=\"og:url\" content=\"https:\/\/kevinjustin.com\/blog\/2021\/11\/09\/fixsql2017plus-netassemblyerror\/\" \/>\n<meta property=\"og:site_name\" content=\"Kevin Justin's Blog\" \/>\n<meta property=\"article:published_time\" content=\"2021-11-10T01:35:32+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2021-11-10T01:36:10+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/kevinjustin.com\/blog\/wp-content\/uploads\/2021\/11\/BillMurry-ThatsWeird.jpg\" \/>\n<meta name=\"author\" content=\"WordPress Administrator\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"WordPress Administrator\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"3 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/kevinjustin.com\\\/blog\\\/2021\\\/11\\\/09\\\/fixsql2017plus-netassemblyerror\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/kevinjustin.com\\\/blog\\\/2021\\\/11\\\/09\\\/fixsql2017plus-netassemblyerror\\\/\"},\"author\":{\"name\":\"WordPress Administrator\",\"@id\":\"https:\\\/\\\/kevinjustin.com\\\/blog\\\/#\\\/schema\\\/person\\\/3d7a90f4430bef43134eaa0a7e2cd508\"},\"headline\":\"Weird SQL issue from SCOM DB move\",\"datePublished\":\"2021-11-10T01:35:32+00:00\",\"dateModified\":\"2021-11-10T01:36:10+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/kevinjustin.com\\\/blog\\\/2021\\\/11\\\/09\\\/fixsql2017plus-netassemblyerror\\\/\"},\"wordCount\":616,\"commentCount\":5,\"image\":{\"@id\":\"https:\\\/\\\/kevinjustin.com\\\/blog\\\/2021\\\/11\\\/09\\\/fixsql2017plus-netassemblyerror\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/kevinjustin.com\\\/blog\\\/wp-content\\\/uploads\\\/2021\\\/11\\\/BillMurry-ThatsWeird.jpg\",\"keywords\":[\"26317\",\"Move SCOM Databases\",\"MSSQL\",\"scom2019\",\"SCOM2022\",\"sql\",\"sql application log\",\"SQL2014\",\"SQL2017\"],\"articleSection\":[\"SQL\",\"Troubleshooting\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/kevinjustin.com\\\/blog\\\/2021\\\/11\\\/09\\\/fixsql2017plus-netassemblyerror\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/kevinjustin.com\\\/blog\\\/2021\\\/11\\\/09\\\/fixsql2017plus-netassemblyerror\\\/\",\"url\":\"https:\\\/\\\/kevinjustin.com\\\/blog\\\/2021\\\/11\\\/09\\\/fixsql2017plus-netassemblyerror\\\/\",\"name\":\"Fix SQL2017+ .NET assembly\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/kevinjustin.com\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/kevinjustin.com\\\/blog\\\/2021\\\/11\\\/09\\\/fixsql2017plus-netassemblyerror\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/kevinjustin.com\\\/blog\\\/2021\\\/11\\\/09\\\/fixsql2017plus-netassemblyerror\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/kevinjustin.com\\\/blog\\\/wp-content\\\/uploads\\\/2021\\\/11\\\/BillMurry-ThatsWeird.jpg\",\"datePublished\":\"2021-11-10T01:35:32+00:00\",\"dateModified\":\"2021-11-10T01:36:10+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/kevinjustin.com\\\/blog\\\/#\\\/schema\\\/person\\\/3d7a90f4430bef43134eaa0a7e2cd508\"},\"description\":\"Check SQL .NET assemblies to see if trusted for SQL2017+. Use this to resolve Operations Manager Event ID 26319 events\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/kevinjustin.com\\\/blog\\\/2021\\\/11\\\/09\\\/fixsql2017plus-netassemblyerror\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/kevinjustin.com\\\/blog\\\/2021\\\/11\\\/09\\\/fixsql2017plus-netassemblyerror\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/kevinjustin.com\\\/blog\\\/2021\\\/11\\\/09\\\/fixsql2017plus-netassemblyerror\\\/#primaryimage\",\"url\":\"https:\\\/\\\/kevinjustin.com\\\/blog\\\/wp-content\\\/uploads\\\/2021\\\/11\\\/BillMurry-ThatsWeird.jpg\",\"contentUrl\":\"https:\\\/\\\/kevinjustin.com\\\/blog\\\/wp-content\\\/uploads\\\/2021\\\/11\\\/BillMurry-ThatsWeird.jpg\",\"width\":261,\"height\":261,\"caption\":\"BillMurry-ThatsWeird\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/kevinjustin.com\\\/blog\\\/2021\\\/11\\\/09\\\/fixsql2017plus-netassemblyerror\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/kevinjustin.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Weird SQL issue from SCOM DB move\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/kevinjustin.com\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/kevinjustin.com\\\/blog\\\/\",\"name\":\"Kevin Justin's Blog\",\"description\":\"Operational monitoring tools including System Center, Azure Monitor\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/kevinjustin.com\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/kevinjustin.com\\\/blog\\\/#\\\/schema\\\/person\\\/3d7a90f4430bef43134eaa0a7e2cd508\",\"name\":\"WordPress Administrator\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/fca865cc5df90a25ae9533b1d9dea567a78c7469dc3202a376c8d117a0eaea11?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/fca865cc5df90a25ae9533b1d9dea567a78c7469dc3202a376c8d117a0eaea11?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/fca865cc5df90a25ae9533b1d9dea567a78c7469dc3202a376c8d117a0eaea11?s=96&d=mm&r=g\",\"caption\":\"WordPress Administrator\"},\"sameAs\":[\"https:\\\/\\\/kevinjustin.com\"],\"url\":\"https:\\\/\\\/kevinjustin.com\\\/blog\\\/author\\\/wordpress_admin\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Fix SQL2017+ .NET assembly","description":"Check SQL .NET assemblies to see if trusted for SQL2017+. Use this to resolve Operations Manager Event ID 26319 events","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/kevinjustin.com\/blog\/2021\/11\/09\/fixsql2017plus-netassemblyerror\/","og_locale":"en_US","og_type":"article","og_title":"Fix SQL2017+ .NET assembly","og_description":"Check SQL .NET assemblies to see if trusted for SQL2017+. Use this to resolve Operations Manager Event ID 26319 events","og_url":"https:\/\/kevinjustin.com\/blog\/2021\/11\/09\/fixsql2017plus-netassemblyerror\/","og_site_name":"Kevin Justin's Blog","article_published_time":"2021-11-10T01:35:32+00:00","article_modified_time":"2021-11-10T01:36:10+00:00","og_image":[{"url":"https:\/\/kevinjustin.com\/blog\/wp-content\/uploads\/2021\/11\/BillMurry-ThatsWeird.jpg","type":"","width":"","height":""}],"author":"WordPress Administrator","twitter_card":"summary_large_image","twitter_misc":{"Written by":"WordPress Administrator","Est. reading time":"3 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/kevinjustin.com\/blog\/2021\/11\/09\/fixsql2017plus-netassemblyerror\/#article","isPartOf":{"@id":"https:\/\/kevinjustin.com\/blog\/2021\/11\/09\/fixsql2017plus-netassemblyerror\/"},"author":{"name":"WordPress Administrator","@id":"https:\/\/kevinjustin.com\/blog\/#\/schema\/person\/3d7a90f4430bef43134eaa0a7e2cd508"},"headline":"Weird SQL issue from SCOM DB move","datePublished":"2021-11-10T01:35:32+00:00","dateModified":"2021-11-10T01:36:10+00:00","mainEntityOfPage":{"@id":"https:\/\/kevinjustin.com\/blog\/2021\/11\/09\/fixsql2017plus-netassemblyerror\/"},"wordCount":616,"commentCount":5,"image":{"@id":"https:\/\/kevinjustin.com\/blog\/2021\/11\/09\/fixsql2017plus-netassemblyerror\/#primaryimage"},"thumbnailUrl":"https:\/\/kevinjustin.com\/blog\/wp-content\/uploads\/2021\/11\/BillMurry-ThatsWeird.jpg","keywords":["26317","Move SCOM Databases","MSSQL","scom2019","SCOM2022","sql","sql application log","SQL2014","SQL2017"],"articleSection":["SQL","Troubleshooting"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/kevinjustin.com\/blog\/2021\/11\/09\/fixsql2017plus-netassemblyerror\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/kevinjustin.com\/blog\/2021\/11\/09\/fixsql2017plus-netassemblyerror\/","url":"https:\/\/kevinjustin.com\/blog\/2021\/11\/09\/fixsql2017plus-netassemblyerror\/","name":"Fix SQL2017+ .NET assembly","isPartOf":{"@id":"https:\/\/kevinjustin.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/kevinjustin.com\/blog\/2021\/11\/09\/fixsql2017plus-netassemblyerror\/#primaryimage"},"image":{"@id":"https:\/\/kevinjustin.com\/blog\/2021\/11\/09\/fixsql2017plus-netassemblyerror\/#primaryimage"},"thumbnailUrl":"https:\/\/kevinjustin.com\/blog\/wp-content\/uploads\/2021\/11\/BillMurry-ThatsWeird.jpg","datePublished":"2021-11-10T01:35:32+00:00","dateModified":"2021-11-10T01:36:10+00:00","author":{"@id":"https:\/\/kevinjustin.com\/blog\/#\/schema\/person\/3d7a90f4430bef43134eaa0a7e2cd508"},"description":"Check SQL .NET assemblies to see if trusted for SQL2017+. Use this to resolve Operations Manager Event ID 26319 events","breadcrumb":{"@id":"https:\/\/kevinjustin.com\/blog\/2021\/11\/09\/fixsql2017plus-netassemblyerror\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/kevinjustin.com\/blog\/2021\/11\/09\/fixsql2017plus-netassemblyerror\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/kevinjustin.com\/blog\/2021\/11\/09\/fixsql2017plus-netassemblyerror\/#primaryimage","url":"https:\/\/kevinjustin.com\/blog\/wp-content\/uploads\/2021\/11\/BillMurry-ThatsWeird.jpg","contentUrl":"https:\/\/kevinjustin.com\/blog\/wp-content\/uploads\/2021\/11\/BillMurry-ThatsWeird.jpg","width":261,"height":261,"caption":"BillMurry-ThatsWeird"},{"@type":"BreadcrumbList","@id":"https:\/\/kevinjustin.com\/blog\/2021\/11\/09\/fixsql2017plus-netassemblyerror\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/kevinjustin.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Weird SQL issue from SCOM DB move"}]},{"@type":"WebSite","@id":"https:\/\/kevinjustin.com\/blog\/#website","url":"https:\/\/kevinjustin.com\/blog\/","name":"Kevin Justin's Blog","description":"Operational monitoring tools including System Center, Azure Monitor","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/kevinjustin.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/kevinjustin.com\/blog\/#\/schema\/person\/3d7a90f4430bef43134eaa0a7e2cd508","name":"WordPress Administrator","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/fca865cc5df90a25ae9533b1d9dea567a78c7469dc3202a376c8d117a0eaea11?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/fca865cc5df90a25ae9533b1d9dea567a78c7469dc3202a376c8d117a0eaea11?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/fca865cc5df90a25ae9533b1d9dea567a78c7469dc3202a376c8d117a0eaea11?s=96&d=mm&r=g","caption":"WordPress Administrator"},"sameAs":["https:\/\/kevinjustin.com"],"url":"https:\/\/kevinjustin.com\/blog\/author\/wordpress_admin\/"}]}},"_links":{"self":[{"href":"https:\/\/kevinjustin.com\/blog\/wp-json\/wp\/v2\/posts\/6900","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/kevinjustin.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/kevinjustin.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/kevinjustin.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/kevinjustin.com\/blog\/wp-json\/wp\/v2\/comments?post=6900"}],"version-history":[{"count":9,"href":"https:\/\/kevinjustin.com\/blog\/wp-json\/wp\/v2\/posts\/6900\/revisions"}],"predecessor-version":[{"id":6912,"href":"https:\/\/kevinjustin.com\/blog\/wp-json\/wp\/v2\/posts\/6900\/revisions\/6912"}],"wp:attachment":[{"href":"https:\/\/kevinjustin.com\/blog\/wp-json\/wp\/v2\/media?parent=6900"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/kevinjustin.com\/blog\/wp-json\/wp\/v2\/categories?post=6900"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/kevinjustin.com\/blog\/wp-json\/wp\/v2\/tags?post=6900"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}