Windows 卷影复制错误:2155348129

发布于 2024-09-10 07:48:40 字数 423 浏览 11 评论 0原文

开发 VSS 编写器应用程序:
在由 Windows 备份工具启动的备份过程中看到此错误, Microsoft 是否有为 2155348129 定义的错误代码?

从“2010‎-‎07‎-‎20T02:54:19.354000000Z”开始的备份操作失败,因为用于创建正在备份的卷的卷影副本的卷影复制服务操作失败,并出现以下错误代码“2155348129”

VSSwriter 服务(我的应用程序)停止时,不会发生这种情况。

任何帮助表示赞赏。 TechNet 上没有发现任何有用的信息。

黑客解决方法: 有趣的是,备份工作是在“Windows 分区处于活动状态”时进行的。当然,这会使系统在重新启动时无法启动

Developing a VSS writer app:
see this error during backup, initiated by windows backup tool,
is there defined error codes for 2155348129 from Microsoft?

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'

This does not happen when VSSwriter service (my application) is stopped.

Any help is appreciated. Nothing useful found on 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

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(6

风吹过旳痕迹 2024-09-17 07:48:40

TechNet 博客

十进制 21553481290x807800A1十六进制

在 Internet 上快速搜索此值将我带到此博客:

这是一个 HRESULT

此错误代码属于特殊的 < a href="https://en.wikipedia.org/wiki/HRESULT" rel="nofollow noreferrer">称为 HRESULT 的类型。

即它是与 VSS 相关的 HRESULT

,TechNet 有一个表格列出了我们的特定 HRESULT 值:

注意: VSS卷影复制服务的缩写>。 SPP 是共享保护点的缩写。他们登录常规 Windows 应用程序 事件日志。他们使用 VSSSPP 作为其事件标识符。

TechNet Blog

Decimal 2155348129 is 0x807800A1 in hex.

Quickly searching the Internet for this value takes me to this blog:

It's an HRESULT

This error code is of a special type called an HRESULT.

Namely it's a VSS related HRESULT

And TechNet has a table that lists our specific HRESULT value:

Note: VSS is short for Volume Shadow Copy Service. SPP is short for Shared Protection Point. They log into the regular Windows application event log. And they use VSS and SPP as their event-Source-identifier.

情仇皆在手 2024-09-17 07:48:40

Sharepoint Foundation 导致了该问题。通过运行“Sharepoint 2010 产品配置向导”,它将修复备份问题。

Sharepoint Foundation is causing the issue. By running the "Sharepoint 2010 Products Configuration Wizard", it will fix the backup issue.

牵你的手,一向走下去 2024-09-17 07:48:40

我遇到了类似的 VSS 错误与 SBS 备份问题。

在我的情况下,磁盘空间并不低,

戴尔专业支持(非常好)对这个问题进行了折扣,该问题与硬盘配置有关,该问题在 www. 上都有提及。他们确实说过要注意空间非常低的 HDD,从而导致服务器备份出现 VSS 问题,但事实并非如此。

检查 VSS 编写器状态

我的修复:
运行 vssadmin list writers 并查看它们是否在备份过程中停止。重新启动一两次应该可以使这些恢复正常。立即尝试备份。
检查是否有任何 SharePoint 更新导致了该问题。从开始菜单(下一步、下一步、完成)运行 SharePoint 配置向导,重新启动并重新运行备份。

希望这对其他人有帮助 - 如果您需要更多信息,请告诉我。

www.mtechnical.co.uk

I had a similar problem with VSS errors vs a SBS backup.

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.

Check VSS writer status

My Fix:
Run vssadmin list writers and 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 Wizard from the start menu (Next, Next, Finish), reboot and rerun the backup.

Hope this helps someone else out there - let me know if you need any more info.

www.mtechnical.co.uk

記柔刀 2024-09-17 07:48:40

我在 W Server 2008 R2 上遇到了这个问题。
我终于发现一个虚拟服务器实例正在我的 hyper-v 服务器上运行。
显然存在一个错误,无法处理虚拟服务器和真实服务器备份的并行性。

我相信我在知识库中读到了此问题的修复程序:

关闭 (不重要)虚拟机正在运行,问题已解决

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.

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

擦肩而过的背影 2024-09-17 07:48:40

我安装了 SQL 服务器。数据库太多。当我删除一些数据库时,错误消失了,备份可以正常继续。

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.

青衫儰鉨ミ守葔 2024-09-17 07:48:40

mtechnical 的回答让我走上了正轨,抱歉没有足够的代表来投票给你。

原因是 SharePoint VSS writer

基本上,vssadmin list writers 让我看到 SPSearch4 VSS Writer不一致的卷影副本错误而阻碍了一切,并且经过几次快速的谷歌搜索后我一切都很好。

希望这可以帮助您到达您需要到达的地方。

根本原因是 SharePoint Service Pack

如果其他人由于 SBS 2011 备份失败(即使是使用所有补丁进行全新安装)而出现此情况,则原因是 SharePoint Server Service Pack 造成的。要解决此问题,请运行 Sharepoint 2010 产品配置向导。之后,您应该能够重新运行 vssadmin list writers 并看到所有错误均已清除。

干杯
仙人掌

The answer by mtechnical put me on the right track, sorry don't have enough rep to vote you up.

Cause was SharePoint VSS writer

Basically vssadmin list writers allowed me me to see that SPSearch4 VSS Writer was holding everything up with an inconsistent shadow copy error and a few quick Google searches later I was all good.

Hopefully that helps you get to where you need to be.

Underlying cause was 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 writers and see all errors are cleared.

Cheers
Kactus

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文