{"id":153811,"date":"2023-11-08T06:13:33","date_gmt":"2023-11-08T06:13:33","guid":{"rendered":"https:\/\/www.stellarinfo.com\/blog\/?p=153811"},"modified":"2023-12-11T03:07:35","modified_gmt":"2023-12-11T03:07:35","slug":"fix-failed-to-notify-source-server-about-the-local-truncation-point-hresult-0xc8000713","status":"publish","type":"post","link":"https:\/\/www.stellarinfo.com\/blog\/fix-failed-to-notify-source-server-about-the-local-truncation-point-hresult-0xc8000713\/","title":{"rendered":"How to Fix Error &#8220;Failed to Notify Source Server about the Local Truncation Point. Hresult 0xc8000713&#8221;?"},"content":{"rendered":"<?xml encoding=\"utf-8\" ?><?xml encoding=\"utf-8\" ?><p>In a <a href=\"https:\/\/www.stellarinfo.com\/article\/exchange-database-availability-groups.php\" target=\"_blank\" rel=\"noreferrer noopener\">Database Availability Group (DAG)<\/a> setup in Exchange Server, you have the main database on the first server. Now, you want to add it to the DAG so that the database will replicate and failover to another server when something happens. However, when you try to add the database to the DAG, the process fails and displays the below message.<\/p><p><code>The seeding operation failed. Error: An error occurred while performing the seed operation. Error: Failed to notify source server &lt;fqdn of the server&gt; about the local truncation point. Hresult: 0xc8000713. Error: Unable to find the file.<\/code><\/p><p>The error message above doesn&rsquo;t provide much information on how to fix the problem or at least where the problem is.<\/p><h2 class=\"wp-block-heading\" id=\"why-this-issue-appears?\">Why this Issue Appears?<\/h2><p>The error may occur if there is a problem with the source server where all your primary databases are or the storage device is full where the mailbox databases are stored. The storage might get full due to large size of the databases or if the transaction logs are not purged after successful daily backup. The size of the database increases if there are empty spaces in it. This can be easily cleared with a PowerShell procedure.<\/p><p>Transaction logs are deleted automatically during a backup after the data is committed to the databases. However, if there is an issue with the backup, the transaction logs will never shrink and continue to accumulate. If this is the case, you should never manually delete the transaction logs as these hold temporary data before committing to the database. If these are deleted manually or by a third-party application, this may cause inconsistency of the data and the databases will fail to mount. It&rsquo;s also not recommended to <a href=\"https:\/\/www.stellarinfo.com\/blog\/how-to-enable-circular-logging-in-exchange-server-2010\/\" target=\"_blank\" rel=\"noreferrer noopener\">enable circular logging<\/a>.<\/p><h2 class=\"wp-block-heading\" id=\"possible-solutions-to-fix-&ldquo;failed-to-notify-source-server-about-the-local-truncation-point&rdquo;-error\">Possible Solutions to Fix &ldquo;Failed to Notify Source Server about the Local Truncation Point&rdquo; Error<\/h2><p>Here are some solutions you can try to resolve the &ldquo;<strong>Failed to notify source server about the local truncation point. Hresult: 0xc8000713. Error: Unable to find the file&rdquo; in Exchange Server<\/strong>.<\/p><p>First, check if there is an issue with the database. For this, you can <a href=\"https:\/\/www.stellarinfo.com\/blog\/mount-dismount-mailbox-databases-in-exchange-2019-2016-2013-via-powershell\/\" target=\"_blank\" rel=\"noreferrer noopener\">dismount the database and then mount it back<\/a>. You can use the <strong>Exchange Admin Center (EAC<\/strong>) or the <strong>Exchange Management Shell (EMS)<\/strong>.<\/p><p>To use <strong>EAC<\/strong>, follow these steps:<\/p><ul class=\"wp-block-list\">\n<li>Open the <strong>EAC<\/strong>. Click on <strong>Server <\/strong>and <strong>Databases<\/strong>.<\/li>\n<\/ul><figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"407\" height=\"449\" src=\"https:\/\/www.stellarinfo.com\/blog\/wp-content\/uploads\/2023\/11\/dismount-the-database-and-then-mount-it-back.png\" alt=\"dismount the database and then mount it back\" class=\"wp-image-153812 apply-gradient-on-post-images\" srcset=\"https:\/\/www.stellarinfo.com\/blog\/wp-content\/uploads\/2023\/11\/dismount-the-database-and-then-mount-it-back.png 407w, https:\/\/www.stellarinfo.com\/blog\/wp-content\/uploads\/2023\/11\/dismount-the-database-and-then-mount-it-back-272x300.png 272w, https:\/\/www.stellarinfo.com\/blog\/wp-content\/uploads\/2023\/11\/dismount-the-database-and-then-mount-it-back-150x165.png 150w\" sizes=\"auto, (max-width: 407px) 100vw, 407px\" \/><\/figure><ul class=\"wp-block-list\">\n<li>Highlight the database and click on the More Options (&hellip;) button.<\/li>\n\n\n\n<li>Click <strong>Dismount.<\/strong><\/li>\n<\/ul><figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"282\" height=\"94\" src=\"https:\/\/www.stellarinfo.com\/blog\/wp-content\/uploads\/2023\/11\/Click-Dismount.png\" alt=\"Click Dismount\" class=\"wp-image-153813 apply-gradient-on-post-images\" srcset=\"https:\/\/www.stellarinfo.com\/blog\/wp-content\/uploads\/2023\/11\/Click-Dismount.png 282w, https:\/\/www.stellarinfo.com\/blog\/wp-content\/uploads\/2023\/11\/Click-Dismount-150x50.png 150w\" sizes=\"auto, (max-width: 282px) 100vw, 282px\" \/><\/figure><ul class=\"wp-block-list\">\n<li>To mount the database, follow the same steps but instead of <strong>Dismount<\/strong>, select the <strong>Mount <\/strong>option.<\/li>\n<\/ul><p>To dismount the database using the EMS, run the below PowerShell cmdlet:<\/p><p><code>Dismount-Database -Identity &lt;database name&gt;<\/code><\/p><figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"815\" height=\"160\" src=\"https:\/\/www.stellarinfo.com\/blog\/wp-content\/uploads\/2023\/11\/Dismount-Database-using-the-EMS.png\" alt=\"Dismount Database using the EMS\" class=\"wp-image-153814 apply-gradient-on-post-images\" srcset=\"https:\/\/www.stellarinfo.com\/blog\/wp-content\/uploads\/2023\/11\/Dismount-Database-using-the-EMS.png 815w, https:\/\/www.stellarinfo.com\/blog\/wp-content\/uploads\/2023\/11\/Dismount-Database-using-the-EMS-300x59.png 300w, https:\/\/www.stellarinfo.com\/blog\/wp-content\/uploads\/2023\/11\/Dismount-Database-using-the-EMS-768x151.png 768w, https:\/\/www.stellarinfo.com\/blog\/wp-content\/uploads\/2023\/11\/Dismount-Database-using-the-EMS-150x29.png 150w\" sizes=\"auto, (max-width: 815px) 100vw, 815px\" \/><\/figure><p>To mount the database, run this PowerShell cmdlet:<\/p><p><code>Mount-Database -Identity &lt;database name&gt;<\/code><\/p><figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"389\" height=\"88\" src=\"https:\/\/www.stellarinfo.com\/blog\/wp-content\/uploads\/2023\/11\/mount-the-database.png\" alt=\"mount the database\" class=\"wp-image-153815 apply-gradient-on-post-images\" srcset=\"https:\/\/www.stellarinfo.com\/blog\/wp-content\/uploads\/2023\/11\/mount-the-database.png 389w, https:\/\/www.stellarinfo.com\/blog\/wp-content\/uploads\/2023\/11\/mount-the-database-300x68.png 300w, https:\/\/www.stellarinfo.com\/blog\/wp-content\/uploads\/2023\/11\/mount-the-database-150x34.png 150w\" sizes=\"auto, (max-width: 389px) 100vw, 389px\" \/><\/figure><p>After this, check if the database is healthy or not. For this, run the following EseUtil command:<\/p><p><code>Eseutil \/mh &lt;path to the edb file name&gt;<\/code><\/p><figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"764\" height=\"486\" src=\"https:\/\/www.stellarinfo.com\/blog\/wp-content\/uploads\/2023\/11\/run-the-following-EseUtil-command-to-check-database-health.png\" alt=\"run the following EseUtil command to check database health\" class=\"wp-image-153816 apply-gradient-on-post-images\" srcset=\"https:\/\/www.stellarinfo.com\/blog\/wp-content\/uploads\/2023\/11\/run-the-following-EseUtil-command-to-check-database-health.png 764w, https:\/\/www.stellarinfo.com\/blog\/wp-content\/uploads\/2023\/11\/run-the-following-EseUtil-command-to-check-database-health-300x191.png 300w, https:\/\/www.stellarinfo.com\/blog\/wp-content\/uploads\/2023\/11\/run-the-following-EseUtil-command-to-check-database-health-150x95.png 150w\" sizes=\"auto, (max-width: 764px) 100vw, 764px\" \/><\/figure><p>If the state of the database is Clean Shutdown, then it is suggested to create a new database in the Exchange Server and migrate all the mailboxes to the new database as there might be an issue with the database. This can only be done if the server has enough space or the server can be provisioned with a new temporary drive (in case of a virtual machine).<\/p><p>However, if the problem is lack of storage space, then you can expand the storage by adding a drive and then execute a backup of the database. This will purge the transaction logs. If, after the backup, the transaction logs are not purged, then this means that the backup solution is not application aware or the feature is not enabled. In this case, you can enable the <strong><a href=\"https:\/\/learn.microsoft.com\/en-us\/troubleshoot\/windows-server\/backup-and-storage\/use-backup-feature-back-up-restore-data\" target=\"_blank\" rel=\"noreferrer noopener nofollow\">Windows Server Backup<\/a> <\/strong>from the <strong>Server Manager<\/strong> and run an application-aware backup using the <strong>Windows Server Backup<\/strong>.<\/p><p>Another option is to manually purge the transaction logs with <strong><a href=\"https:\/\/learn.microsoft.com\/en-us\/windows-server\/administration\/windows-commands\/diskshadow\" target=\"_blank\" rel=\"noreferrer noopener nofollow\">DiskShadow<\/a><\/strong>. This should be used as a final solution (if you cannot add more storage or move data to free storage). To purge the transaction logs manually, open <strong>Command<\/strong> <strong>Prompt<\/strong> as <strong>Administrator<\/strong> and type the following:<\/p><p><merlin-component id=\"merlin-code-summarizer\" class=\"merlin-code-summarizer\"><\/merlin-component><code>DiskShadow<br>Add Volume &lt;drive of the mailbox databases&gt;<br>Begin Backup<br>Create<\/code><\/p><p>When the process is complete, run the below command.<\/p><p><code>End backup<\/code><\/p><p>This will clear the space.<\/p><h2 class=\"wp-block-heading\" id=\"to-conclude\">To Conclude<\/h2><p>Issues with storage can cause corruption in the database or hinder the operations of the server. Above, we have discussed some possible solutions to resolve the issue. However, if the database is corrupt or not able to mount for any reason, then you can move it to a temporary drive or server share, thus freeing the space on the server. After that, create a new database. Then, you can use <strong>Stellar Repair for Exchange<\/strong> to recover the data from corrupt database. This <a href=\"https:\/\/www.stellarinfo.com\/edb-exchange-server-recovery.htm\" target=\"_blank\" rel=\"noreferrer noopener\">Exchange Server Recovery<\/a> software can open multiple Exchange Server databases from any version of Exchange Server, with or without a working server. You can do a quick or deep scan of the databases and granularly export the data directly to the newly created database, with automatic mailbox matching, and parallel and priority exports. You can use this software to export user archives, shared mailboxes, disabled mailboxes, and public folders. You can also export the data to Office 365 and file formats, like PST, EML, HTML, and PDF.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>In a Database Availability Group (DAG) setup in Exchange Server, you have&hellip; <a class=\"more-link\" href=\"https:\/\/www.stellarinfo.com\/blog\/fix-failed-to-notify-source-server-about-the-local-truncation-point-hresult-0xc8000713\/\">Continue reading <span class=\"screen-reader-text\">How to Fix Error &#8220;Failed to Notify Source Server about the Local Truncation Point. Hresult 0xc8000713&#8221;?<\/span><\/a><\/p>\n","protected":false},"author":17,"featured_media":156136,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[25],"tags":[5539,5537],"class_list":["post-153811","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-exchange-server","tag-failed-to-notify-source-server-about-the-local-truncation-point","tag-hresult-0xc8000713","entry"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v26.9 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Failed to Notify Source Server about the Local Truncation Point. Hresult 0xc8000713<\/title>\n<meta name=\"description\" content=\"In his blog, we have provided detailed steps to Troubleshoot the Error &quot;Failed to Notify Source Server about the Local Truncation Point. Hresult 0xc8000713&quot;\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.stellarinfo.com\/blog\/fix-failed-to-notify-source-server-about-the-local-truncation-point-hresult-0xc8000713\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Failed to Notify Source Server about the Local Truncation Point. Hresult 0xc8000713\" \/>\n<meta property=\"og:description\" content=\"In his blog, we have provided detailed steps to Troubleshoot the Error &quot;Failed to Notify Source Server about the Local Truncation Point. Hresult 0xc8000713&quot;\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.stellarinfo.com\/blog\/fix-failed-to-notify-source-server-about-the-local-truncation-point-hresult-0xc8000713\/\" \/>\n<meta property=\"og:site_name\" content=\"Stellar Data Recovery Blog\" \/>\n<meta property=\"article:published_time\" content=\"2023-11-08T06:13:33+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2023-12-11T03:07:35+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.stellarinfo.com\/blog\/wp-content\/uploads\/2023\/11\/Notify-Source-Server-about-the-Local-Truncation-Point.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"1000\" \/>\n\t<meta property=\"og:image:height\" content=\"600\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"Shelly Bhardwaj\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Shelly Bhardwaj\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"5 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/www.stellarinfo.com\/blog\/fix-failed-to-notify-source-server-about-the-local-truncation-point-hresult-0xc8000713\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.stellarinfo.com\/blog\/fix-failed-to-notify-source-server-about-the-local-truncation-point-hresult-0xc8000713\/\"},\"author\":{\"name\":\"Shelly Bhardwaj\",\"@id\":\"https:\/\/www.stellarinfo.com\/blog\/#\/schema\/person\/560294d29c29906f1a494397d89ac5b5\"},\"headline\":\"How to Fix Error &#8220;Failed to Notify Source Server about the Local Truncation Point. Hresult 0xc8000713&#8221;?\",\"datePublished\":\"2023-11-08T06:13:33+00:00\",\"dateModified\":\"2023-12-11T03:07:35+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.stellarinfo.com\/blog\/fix-failed-to-notify-source-server-about-the-local-truncation-point-hresult-0xc8000713\/\"},\"wordCount\":814,\"commentCount\":0,\"image\":{\"@id\":\"https:\/\/www.stellarinfo.com\/blog\/fix-failed-to-notify-source-server-about-the-local-truncation-point-hresult-0xc8000713\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.stellarinfo.com\/blog\/wp-content\/uploads\/2023\/11\/Notify-Source-Server-about-the-Local-Truncation-Point.jpg\",\"keywords\":[\"Failed to notify source server about the local truncation point\",\"Hresult 0xc8000713\"],\"articleSection\":[\"Exchange Server Recovery\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.stellarinfo.com\/blog\/fix-failed-to-notify-source-server-about-the-local-truncation-point-hresult-0xc8000713\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.stellarinfo.com\/blog\/fix-failed-to-notify-source-server-about-the-local-truncation-point-hresult-0xc8000713\/\",\"url\":\"https:\/\/www.stellarinfo.com\/blog\/fix-failed-to-notify-source-server-about-the-local-truncation-point-hresult-0xc8000713\/\",\"name\":\"Failed to Notify Source Server about the Local Truncation Point. Hresult 0xc8000713\",\"isPartOf\":{\"@id\":\"https:\/\/www.stellarinfo.com\/blog\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/www.stellarinfo.com\/blog\/fix-failed-to-notify-source-server-about-the-local-truncation-point-hresult-0xc8000713\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/www.stellarinfo.com\/blog\/fix-failed-to-notify-source-server-about-the-local-truncation-point-hresult-0xc8000713\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.stellarinfo.com\/blog\/wp-content\/uploads\/2023\/11\/Notify-Source-Server-about-the-Local-Truncation-Point.jpg\",\"datePublished\":\"2023-11-08T06:13:33+00:00\",\"dateModified\":\"2023-12-11T03:07:35+00:00\",\"author\":{\"@id\":\"https:\/\/www.stellarinfo.com\/blog\/#\/schema\/person\/560294d29c29906f1a494397d89ac5b5\"},\"description\":\"In his blog, we have provided detailed steps to Troubleshoot the Error \\\"Failed to Notify Source Server about the Local Truncation Point. Hresult 0xc8000713\\\"\",\"breadcrumb\":{\"@id\":\"https:\/\/www.stellarinfo.com\/blog\/fix-failed-to-notify-source-server-about-the-local-truncation-point-hresult-0xc8000713\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.stellarinfo.com\/blog\/fix-failed-to-notify-source-server-about-the-local-truncation-point-hresult-0xc8000713\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.stellarinfo.com\/blog\/fix-failed-to-notify-source-server-about-the-local-truncation-point-hresult-0xc8000713\/#primaryimage\",\"url\":\"https:\/\/www.stellarinfo.com\/blog\/wp-content\/uploads\/2023\/11\/Notify-Source-Server-about-the-Local-Truncation-Point.jpg\",\"contentUrl\":\"https:\/\/www.stellarinfo.com\/blog\/wp-content\/uploads\/2023\/11\/Notify-Source-Server-about-the-Local-Truncation-Point.jpg\",\"width\":1000,\"height\":600,\"caption\":\"Notify Source Server about the Local Truncation Point\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.stellarinfo.com\/blog\/fix-failed-to-notify-source-server-about-the-local-truncation-point-hresult-0xc8000713\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/www.stellarinfo.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"How to Fix Error &#8220;Failed to Notify Source Server about the Local Truncation Point. Hresult 0xc8000713&#8221;?\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.stellarinfo.com\/blog\/#website\",\"url\":\"https:\/\/www.stellarinfo.com\/blog\/\",\"name\":\"Stellar Data Recovery Blog\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.stellarinfo.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.stellarinfo.com\/blog\/#\/schema\/person\/560294d29c29906f1a494397d89ac5b5\",\"name\":\"Shelly Bhardwaj\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.stellarinfo.com\/blog\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/55b79705325614a5202bfcbe257c51b4bfd3229f8c27cd88856c412e9d171b8d?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/55b79705325614a5202bfcbe257c51b4bfd3229f8c27cd88856c412e9d171b8d?s=96&d=mm&r=g\",\"caption\":\"Shelly Bhardwaj\"},\"description\":\"I am a Product Consultant and is associated with Stellar Data Recovery from last 8 years. I write about the latest technology tips and provide custom solutions related to Exchange Server, Office 365, MS Outlook, and many other Email Clients &amp; different flavors of OS Servers. Read More\",\"sameAs\":[\"https:\/\/www.linkedin.com\/in\/shelly-bhardwaj\/\"],\"url\":\"https:\/\/www.stellarinfo.com\/blog\/author\/shelly\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Failed to Notify Source Server about the Local Truncation Point. Hresult 0xc8000713","description":"In his blog, we have provided detailed steps to Troubleshoot the Error \"Failed to Notify Source Server about the Local Truncation Point. Hresult 0xc8000713\"","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:\/\/www.stellarinfo.com\/blog\/fix-failed-to-notify-source-server-about-the-local-truncation-point-hresult-0xc8000713\/","og_locale":"en_US","og_type":"article","og_title":"Failed to Notify Source Server about the Local Truncation Point. Hresult 0xc8000713","og_description":"In his blog, we have provided detailed steps to Troubleshoot the Error \"Failed to Notify Source Server about the Local Truncation Point. Hresult 0xc8000713\"","og_url":"https:\/\/www.stellarinfo.com\/blog\/fix-failed-to-notify-source-server-about-the-local-truncation-point-hresult-0xc8000713\/","og_site_name":"Stellar Data Recovery Blog","article_published_time":"2023-11-08T06:13:33+00:00","article_modified_time":"2023-12-11T03:07:35+00:00","og_image":[{"width":1000,"height":600,"url":"https:\/\/www.stellarinfo.com\/blog\/wp-content\/uploads\/2023\/11\/Notify-Source-Server-about-the-Local-Truncation-Point.jpg","type":"image\/jpeg"}],"author":"Shelly Bhardwaj","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Shelly Bhardwaj","Est. reading time":"5 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.stellarinfo.com\/blog\/fix-failed-to-notify-source-server-about-the-local-truncation-point-hresult-0xc8000713\/#article","isPartOf":{"@id":"https:\/\/www.stellarinfo.com\/blog\/fix-failed-to-notify-source-server-about-the-local-truncation-point-hresult-0xc8000713\/"},"author":{"name":"Shelly Bhardwaj","@id":"https:\/\/www.stellarinfo.com\/blog\/#\/schema\/person\/560294d29c29906f1a494397d89ac5b5"},"headline":"How to Fix Error &#8220;Failed to Notify Source Server about the Local Truncation Point. Hresult 0xc8000713&#8221;?","datePublished":"2023-11-08T06:13:33+00:00","dateModified":"2023-12-11T03:07:35+00:00","mainEntityOfPage":{"@id":"https:\/\/www.stellarinfo.com\/blog\/fix-failed-to-notify-source-server-about-the-local-truncation-point-hresult-0xc8000713\/"},"wordCount":814,"commentCount":0,"image":{"@id":"https:\/\/www.stellarinfo.com\/blog\/fix-failed-to-notify-source-server-about-the-local-truncation-point-hresult-0xc8000713\/#primaryimage"},"thumbnailUrl":"https:\/\/www.stellarinfo.com\/blog\/wp-content\/uploads\/2023\/11\/Notify-Source-Server-about-the-Local-Truncation-Point.jpg","keywords":["Failed to notify source server about the local truncation point","Hresult 0xc8000713"],"articleSection":["Exchange Server Recovery"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.stellarinfo.com\/blog\/fix-failed-to-notify-source-server-about-the-local-truncation-point-hresult-0xc8000713\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.stellarinfo.com\/blog\/fix-failed-to-notify-source-server-about-the-local-truncation-point-hresult-0xc8000713\/","url":"https:\/\/www.stellarinfo.com\/blog\/fix-failed-to-notify-source-server-about-the-local-truncation-point-hresult-0xc8000713\/","name":"Failed to Notify Source Server about the Local Truncation Point. Hresult 0xc8000713","isPartOf":{"@id":"https:\/\/www.stellarinfo.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.stellarinfo.com\/blog\/fix-failed-to-notify-source-server-about-the-local-truncation-point-hresult-0xc8000713\/#primaryimage"},"image":{"@id":"https:\/\/www.stellarinfo.com\/blog\/fix-failed-to-notify-source-server-about-the-local-truncation-point-hresult-0xc8000713\/#primaryimage"},"thumbnailUrl":"https:\/\/www.stellarinfo.com\/blog\/wp-content\/uploads\/2023\/11\/Notify-Source-Server-about-the-Local-Truncation-Point.jpg","datePublished":"2023-11-08T06:13:33+00:00","dateModified":"2023-12-11T03:07:35+00:00","author":{"@id":"https:\/\/www.stellarinfo.com\/blog\/#\/schema\/person\/560294d29c29906f1a494397d89ac5b5"},"description":"In his blog, we have provided detailed steps to Troubleshoot the Error \"Failed to Notify Source Server about the Local Truncation Point. Hresult 0xc8000713\"","breadcrumb":{"@id":"https:\/\/www.stellarinfo.com\/blog\/fix-failed-to-notify-source-server-about-the-local-truncation-point-hresult-0xc8000713\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.stellarinfo.com\/blog\/fix-failed-to-notify-source-server-about-the-local-truncation-point-hresult-0xc8000713\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.stellarinfo.com\/blog\/fix-failed-to-notify-source-server-about-the-local-truncation-point-hresult-0xc8000713\/#primaryimage","url":"https:\/\/www.stellarinfo.com\/blog\/wp-content\/uploads\/2023\/11\/Notify-Source-Server-about-the-Local-Truncation-Point.jpg","contentUrl":"https:\/\/www.stellarinfo.com\/blog\/wp-content\/uploads\/2023\/11\/Notify-Source-Server-about-the-Local-Truncation-Point.jpg","width":1000,"height":600,"caption":"Notify Source Server about the Local Truncation Point"},{"@type":"BreadcrumbList","@id":"https:\/\/www.stellarinfo.com\/blog\/fix-failed-to-notify-source-server-about-the-local-truncation-point-hresult-0xc8000713\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.stellarinfo.com\/blog\/"},{"@type":"ListItem","position":2,"name":"How to Fix Error &#8220;Failed to Notify Source Server about the Local Truncation Point. Hresult 0xc8000713&#8221;?"}]},{"@type":"WebSite","@id":"https:\/\/www.stellarinfo.com\/blog\/#website","url":"https:\/\/www.stellarinfo.com\/blog\/","name":"Stellar Data Recovery Blog","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.stellarinfo.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.stellarinfo.com\/blog\/#\/schema\/person\/560294d29c29906f1a494397d89ac5b5","name":"Shelly Bhardwaj","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.stellarinfo.com\/blog\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/55b79705325614a5202bfcbe257c51b4bfd3229f8c27cd88856c412e9d171b8d?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/55b79705325614a5202bfcbe257c51b4bfd3229f8c27cd88856c412e9d171b8d?s=96&d=mm&r=g","caption":"Shelly Bhardwaj"},"description":"I am a Product Consultant and is associated with Stellar Data Recovery from last 8 years. I write about the latest technology tips and provide custom solutions related to Exchange Server, Office 365, MS Outlook, and many other Email Clients &amp; different flavors of OS Servers. Read More","sameAs":["https:\/\/www.linkedin.com\/in\/shelly-bhardwaj\/"],"url":"https:\/\/www.stellarinfo.com\/blog\/author\/shelly\/"}]}},"_links":{"self":[{"href":"https:\/\/www.stellarinfo.com\/blog\/wp-json\/wp\/v2\/posts\/153811","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.stellarinfo.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.stellarinfo.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.stellarinfo.com\/blog\/wp-json\/wp\/v2\/users\/17"}],"replies":[{"embeddable":true,"href":"https:\/\/www.stellarinfo.com\/blog\/wp-json\/wp\/v2\/comments?post=153811"}],"version-history":[{"count":6,"href":"https:\/\/www.stellarinfo.com\/blog\/wp-json\/wp\/v2\/posts\/153811\/revisions"}],"predecessor-version":[{"id":156137,"href":"https:\/\/www.stellarinfo.com\/blog\/wp-json\/wp\/v2\/posts\/153811\/revisions\/156137"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.stellarinfo.com\/blog\/wp-json\/wp\/v2\/media\/156136"}],"wp:attachment":[{"href":"https:\/\/www.stellarinfo.com\/blog\/wp-json\/wp\/v2\/media?parent=153811"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.stellarinfo.com\/blog\/wp-json\/wp\/v2\/categories?post=153811"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.stellarinfo.com\/blog\/wp-json\/wp\/v2\/tags?post=153811"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}