MSP 安装 - 错误 2920:未指定文件的源目录

发布于 2024-11-02 07:24:17 字数 1142 浏览 4 评论 0原文

我有一个基本安装,其中包含一个文件,然后是两个更新该文件的补丁。已经部署了一个补丁,但我发现为时已晚我应该设置 SequenceStart< /a> 位于补丁声明中的 元素上。现在,当我查看 Orca 中的补丁时,新文件的序列为 2,这与某些现有文件相同。

现在我想应用另一个补丁,但即使我正确设置了新的 SequenceStart,它也会失败并显示以下消息:

MSI (s) (D8:EC) [15:46:34:054]: Transforming table Error.
MSI (s) (D8:EC) [15:46:34:054]: Transforming table Error.
MSI (s) (D8:EC) [15:46:34:054]: Note: 1: 2262 2: Error 3: -2147287038 MSI (s) (D8:EC) [15:46:34:054]: Transforming table Error.
MSI (s) (D8:EC) [15:46:34:054]: Note: 1: 2262 2: Error 3: -2147287038 MSI (s) (D8:EC) [15:46:34:054]: Transforming table Error.
MSI (s) (D8:EC) [15:46:34:054]: Note: 1: 2262 2: Error 3: -2147287038
DEBUG: Error 2920:  Source directory not specified for file <file ID>.

我有一种感觉,第一个补丁上的无效序列号将这里的事情弄乱了。虽然该错误仅发生在 Windows Server 2003 中。但在 Server 2008 中第二个补丁安装成功。

我是否被困在这里?全新安装是唯一的出路吗?或者可能还有其他原因导致错误?

(编辑)即使使用正确的中间序列号也对其进行了测试,但它仍然因相同的错误而失败。所以一定是别的东西。有人有任何线索吗?

(edit2) 使用 Windows Installer 3.1 时会引发错误,但使用 Windows Installer 4.5 时一切正常。

I have a base install which includes a file, then two patches after that which update that file. One patch has already been deployed, but I found out too late that I should have set the SequenceStart on the <Family> element in the patch declaration. Now when I look at the patch in Orca the new file has a Sequence of 2, which is the same as some existing file.

Now I've got another patch that I want to apply over this, but even when I set the new SequenceStart correctly, it will fail with this message:

MSI (s) (D8:EC) [15:46:34:054]: Transforming table Error.
MSI (s) (D8:EC) [15:46:34:054]: Transforming table Error.
MSI (s) (D8:EC) [15:46:34:054]: Note: 1: 2262 2: Error 3: -2147287038 MSI (s) (D8:EC) [15:46:34:054]: Transforming table Error.
MSI (s) (D8:EC) [15:46:34:054]: Note: 1: 2262 2: Error 3: -2147287038 MSI (s) (D8:EC) [15:46:34:054]: Transforming table Error.
MSI (s) (D8:EC) [15:46:34:054]: Note: 1: 2262 2: Error 3: -2147287038
DEBUG: Error 2920:  Source directory not specified for file <file ID>.

I have a feeling that the invalid sequence number on the first patch is messing things up here. Though the error only happens in Windows Server 2003. The second patch install succeeds in Server 2008.

Am I stuck here? Is the only way out to do a fresh install? Or could there be something else that's causing the error?

(edit) Tested it even with a correct intermediary Sequence number and it's still failing with the same error. So it must be something else. Does anyone have any clue?

(edit2) The error is thrown when using Windows Installer 3.1 but everything works when using Windows Installer 4.5.

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

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

发布评论

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

评论(1

违心° 2024-11-09 07:24:17

既然你已经停止调查,我不会发表太多评论,只是提到我将测试所有不同场景的卸载:

1:卸载没有补丁的原始设置
2:卸载补丁1
3:卸载补丁2
4:用补丁1打补丁后卸载整个产品
5:使用补丁 2 打补丁后卸载整个产品

打补丁是一个痛苦的世界......

Since you have stopped investigating I won't comment much, just mention that I would test uninstall of all the different scenarios:

1: uninstall of original setup without patches
2: uninstall of patch 1
3: uninstall of patch 2
4: uninstall of whole product after patching with patch 1
5: uninstall of whole product after patching with patch 2

Patching is a world of pain...

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