有没有办法处理 MSI 安装向导中的捕获异常?
我面临一些奇怪的情况,当我在功能自定义向导中选择/取消选择功能时,有时会导致窗口崩溃。它根本没有给出任何线索。它也不是始终如一地发生。
您有任何想法或遇到过此类问题吗?我什至可以使用安装日志追踪根本原因。
I am facing some odd situation that when I select/deselect the features in the feature customization wizard, it sometimes crashes the window. It does not give any clue at all. It also not happens consistently.
Do you have any idea or faced such kind of issue? I am able to even trace the root cause using install log.
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(2)
如果打开“调试”策略,您可能能够更接近地隔离问题。为此,请按照以下说明将
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer
的Debug
值设置为 (dword)7
Windows Installer 团队博客。然后,您需要使用 DebugView 等工具来查看额外的内容Windows Installer 将生成的输出。请注意,您可能需要重新启动“msiserver”服务才能使策略生效。祝你好运,理解它所显示的内容;通常只是大量 SQL 查询转储。You may be able to get closer to isolating the problem if you turn on the Debug policy. Do this by setting
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer
'sDebug
value to (dword)7
in as described on the Windows Installer team blog. You will then need to use a tool like DebugView to view the extra output that Windows Installer will generate. Note you may have to restart the "msiserver" service for the policy to take effect. Best luck making sense of what it shows; often it's just a lot of SQL query dumps.有时您可以从事件日志中获取 MSI 异常,但它们并不总是能告诉您太多信息。
相反,您可以打开 MSI 日志记录,这可以通过注册表或命令行来完成。要了解有关注册表选项的信息,请访问这篇 MS 支持文章。要从命令行执行此操作,您可以使用相同的开关,但它们显然只能持续一次安装。这是从 msiexec 收集的快照:
要利用这些选项,请直接使用 msiexec:
You can sometimes grab MSI exceptions from out of the event log, but they won't always tell you much.
Instead what you can do is turn on logging of the MSI, this can be done either via the registry, or via the command line. To find out about the registry option, visit this MS Support article. To do it from the command line you can use the same switches, but they obviously will only last for that one install. This is a snapshot as gathered from msiexec:
To take advantage of these options, use msiexec directly: