Windows 卷影复制错误：2155348129
声明：本页面是StackOverFlow热门问题的中英对照翻译，遵循CC BY-SA 4.0协议，如果您需要使用它，必须同样遵循CC BY-SA许可，注明原文地址和作者信息，同时你必须将它归于原作者（不是我）：StackOverFlow
原文地址: http://stackoverflow.com/questions/3290913/
Warning: these are provided under cc-by-sa 4.0 license. You are free to use/share it, But you must attribute it to the original authors (not me):
StackOverFlow
Windows Volume shadow copy error: 2155348129
提问by maruti
Developing a VSS writer app:
see this error during backup, initiated by windows backup tool,
is there defined error codes for 2155348129from Microsoft?
开发 VSS 编写器应用程序：
在备份期间看到此错误，由 Windows 备份工具启动，是否有2155348129Microsoft定义的错误代码？
The backup operation that started at '?2010?-?07?-?20T02:54:19.354000000Z' has failed because the Volume Shadow Copy Service operation to create a shadow copy of the volumes being backed up failed with following error code '2155348129'
在 '?2010?-?07?-?20T02:54:19.354000000Z' 开始的备份操作失败，因为创建正在备份的卷的卷影副本的卷影复制服务操作失败，错误代码为 '2155348129 '
This does not happen when VSSwriterservice (my application) is stopped.
当VSSwriter服务（我的应用程序）停止时，这不会发生。
Any help is appreciated. Nothing useful found on TechNet.
任何帮助表示赞赏。在 TechNet 上找不到任何有用的信息。
Hackish workaround: Interestingly the back up works is when "windows partition is made active". Of course this leaves the system non-boot-able upon restart
骇人听闻的解决方法：有趣的是，备份工作是在“Windows 分区处于活动状态”时进行的。当然，这会使系统在重新启动时无法启动
采纳答案by Roger Lipscombe
TechNet Blog
TechNet 博客
Decimal 2155348129is 0x807800A1in hex.
Quickly searching the Internet for this value takes me to this blog:
在 Internet 上快速搜索此值将我带到此博客：
- Microsoft TechNet "filecab" blog, Jose Barreto, 2009-09-16, Diagnosing Failures in Windows Server Backup – Part 1 (VSS/SPP Errors)(Archived here.)
- Microsoft TechNet“filecab”博客，Jose Barreto，2009 年 9 月 16 日，诊断 Windows Server 备份中的故障 – 第 1 部分（VSS/SPP 错误）（存档于此处。）
It's an HRESULT
这是一个 HRESULT
This error code is of a special type called an HRESULT.
此错误代码属于特殊类型，称为HRESULT.
Namely it's a VSS related HRESULT
即它是一个与 VSS 相关的 HRESULT
And TechNet has a table that lists our specific HRESULT value:
TechNet 有一个表格，列出了我们特定的 HRESULT 值：
- HRESULT:
2155348129 - HRESULT (in hex):
0x807800A1 - Error Message:
A Volume Shadow Copy Service operation failed. Please check "VSS" and "SPP" application event logs for more information.
- HRESULT:
TechNet：对 Windows Server 2008 和 Windows Server 2008 R2 中的 Windows Server Backup (WBADMIN) 出现的 VSS 问题进行故障排除：
- 结果：
2155348129 - HRESULT（十六进制）：
0x807800A1 - 错误信息：
A Volume Shadow Copy Service operation failed. Please check "VSS" and "SPP" application event logs for more information.
- 结果：
Note:VSSis short for Volume Shadow Copy Service. SPP is short for Shared Protection Point. They log into the regular Windows applicationevent log. And they use VSSand SPPas their event-Source-identifier.
注意：VSS是Volume Shadow Copy Service. SPP 是Shared Protection Point. 他们登录到常规的 Windowsapplication事件日志。他们使用VSS和SPP作为他们的事件Source标识符。
回答by mtechnical
I had a similar problem with VSS errors vs a SBS backup.
我在 VSS 错误和 SBS 备份方面遇到了类似的问题。
Wasn't low disk space in my case
在我的情况下，磁盘空间不低
Dell Pro Support (very good) discounted the issue being with the HDD configuration which is referred to all over the www. They did say to watch out for HDDs that are very low on space causing VSS issues for Server backup but this was not the case.
戴尔专业支持（非常好）忽略了硬盘配置的问题，该问题在 www. 他们确实说过要注意空间非常低的硬盘驱动器会导致服务器备份的 VSS 问题，但事实并非如此。
Check VSS writer status
检查 VSS 编写器状态
My Fix:
Run vssadmin list writersand see if they have stalled as part of the backup. A reboot or two should set these back to normal. Try a backup now.
Check to see if any SharePoint updates are causing the issue. Run the SharePoint Configuration Wizardfrom the start menu (Next, Next, Finish), reboot and rerun the backup.
我的修复：
运行vssadmin list writers并查看它们是否作为备份的一部分停止。重新启动或两次应将这些设置恢复正常。立即尝试备份。
检查是否有任何 SharePoint 更新导致了该问题。SharePoint Configuration Wizard从开始菜单运行（下一步、下一步、完成），重新启动并重新运行备份。
Hope this helps someone else out there - let me know if you need any more info.
希望这可以帮助其他人 - 如果您需要更多信息，请告诉我。
www.mtechnical.co.uk
www.mtechnical.co.uk
回答by Dinnabeh
Sharepoint Foundation is causing the issue. By running the "Sharepoint 2010 Products Configuration Wizard", it will fix the backup issue.
Sharepoint Foundation 导致了这个问题。通过运行“Sharepoint 2010 产品配置向导”，它将修复备份问题。
回答by iAbl
I had this problem on my W Server 2008 R2. I finaly found that a virtual server instance was running on my hyper-v server. Apparently there is a bug that cannot handle parallellism of backups of the v-server and the real server.
我在 W Server 2008 R2 上遇到了这个问题。我最终发现在我的 hyper-v 服务器上运行了一个虚拟服务器实例。显然存在一个无法处理虚拟服务器和真实服务器备份的并行性的错误。
I believe I read that there is a fix for this in the knowledge base:
我相信我读到知识库中有一个解决方法：
When shutting down the (not important) virtual machine that was running, the issue was resolved
关闭正在运行的（不重要的）虚拟机时，问题已解决
回答by Kactus
The answer by mtechnicalput me on the right track, sorry don't have enough rep to vote you up.
mtechnical的回答让我走上正轨，抱歉没有足够的代表来投票给你。
Cause was SharePoint VSS writer
原因是 SharePoint VSS 编写器
Basically vssadmin list writersallowed me me to see that SPSearch4 VSS Writerwas holding everything up with an inconsistent shadow copyerror and a few quick Google searches later I was all good.
基本上vssadmin list writers让我看到这SPSearch4 VSS Writer一切都因为inconsistent shadow copy错误而停滞不前，后来我进行了几次快速的 Google 搜索，一切都很好。
Hopefully that helps you get to where you need to be.
希望这能帮助你到达你需要去的地方。
Underlying cause was SharePoint Service Pack
根本原因是 SharePoint Service Pack
In case anyone else gets here due to backup failing with SBS 2011 even on a clean install with all patches, the cause is due to the SharePoint Server service pack. To resolve run the Sharepoint 2010 Products Configuration Wizard. And after that you should be able to re-run vssadmin list writersand see all errors are cleared.
万一其他人因为 SBS 2011 的备份失败而到达这里，即使是在带有所有补丁的全新安装中，原因是SharePoint Server service pack. 要解决运行Sharepoint 2010 Products Configuration Wizard. 之后，您应该能够重新运行vssadmin list writers并看到所有错误都已清除。
Cheers Kactus
干杯仙人掌
回答by Ole
I had a SQL server installed. With too many databases. When I deleted some databases the error went away and the backup could continue as normal.
我安装了 SQL 服务器。数据库太多。当我删除一些数据库时，错误消失了，备份可以继续正常进行。
