在客户端系统中安装后,桌面应用程序无法打开 [英] Desktop applicaton not opening after installation in client system

查看:176
本文介绍了在客户端系统中安装后,桌面应用程序无法打开的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我目前正在使用带有4.6.1 .net框架的Visual Studio 2017。我为桌面应用程序创建了安装文件,安装程序可以在我的系统中完美安装并运行。问题是该安装程序已成功在其他计算机上安装,但未打开该应用程序。



编辑



在客户端系统中下载了.net框架,但仍然出现相同的问题。



编辑2



我使用Dependency Walker进行了依赖项扫描。它说有很多文件,系统找不到-打开文件时出错。系统找不到指定的文件。

  API-MS-WIN-APPMODEL-RUNTIME-L1-1-0.DLL 
API-MS-WIN-CORE-WINRT-ERROR-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-L1-1-0.DLL
API-MS -WIN-核心-WINRT-ROBUFFER-L1-1-0.DLL
API-MS-WIN-核心-WINRT-STRING-L1-1-0.DLL
API-MS-WIN-SHCORE -SCALING-L1-1-1.DLL
DCOMP.DLL
IESHIMS.DLL

此外,发现x86类型的模块(包括setup.exe)时出错,但是我不知道这是怎么发生的。我在列出的任何位置都选择了64。请找到屏幕截图。如果确实是问题所在,该如何解决?

解决方案


应用程序启动问题 :这是一个简短的版本:启动时WPF应用程序崩溃 Chattier版本







日志 :始终检查所有事件日志应用程序日志 MSI日志(如果有)。只是提一下。 也许尝试附加调试器按此处所述进行测试-只要应用程序完全脱离地面。然后逐步执行代码。



惯常罪犯 :您可能只是 缺少运行时 ,遇到 位问题 (32/64位)或 权限不足/特权 ,或 配置错误 ini xml 注册表等。 。)。



总结 -鱼雷,下方完整铺开-没什么好说的:-):







缺少运行时间 :首先,始终检查缺少的运行时。例如: .Net .Net Core Java Silverlight
Direct X (现在甚至用于应用程序), VC ++运行时 MS-XML (旧版), 等... 。请记住,它们有不同的版本,有些不能并存,而有些
可以并排运行。








错误代码 :查找错误代码和异常消息。










调试工具 有关调试到ols










ProcMon.exe :交易工具。一种适合所有人的
工具。蜜蜂的膝盖,最高处,量子跃迁,猫的
睡衣(是的,这是Top Gear仓鼠的典故)。有效使用它可能是一个挑战,但是它是免费的
最佳通用调试工具。









其他想法


  1. 配置设置


    • Dev-box罪过:硬编码引用?测试服务器/ UAT链接?

    • 清单 INI文件 XMLfiles

    • 注册表设置? HKLM / HKCU

    • 连接字符串。请参阅身份验证和


  2. 平台& 位数? (ARM,Intel 32/64等)。


    • 从错误的注册表配置单元读取错误( 经典时间浪费)很常见:


      • HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\MyApp\MySettings (32位)

      • HKEY_LOCAL_MACHINE\SOFTWARE\MyApp\MySettings (64位)



  3. 先决条件和依赖关系


  4. 缺少注册/丢失注册(间接依赖项)


  5. 权限和权限特权? -本地- ACL权限 NT权限


  6. 身份验证/授权-与网络相关的


    • 本地用户,域用户,Active Directory:组成员身份,组策略等...

    • 启动用户:用户配置文件有问题吗?也许尝试用另一个登录失败的用户登录?

    • 身份验证模式:Windows身份验证。 SQL Server身份验证等...


  7. 常规网络&代理问题? (代理,WINS,DNS和网络中涉及的所有复杂性。UNC路径可达吗?)

  8. 许可? (可能与硬件加密狗和驱动程序有关)

  9. 安全软件干扰? (软件/硬件防火墙,防病毒,加密工具和套件等...)

  10. 操作系统版本或版本? ( Windows 7问题

  11. 本地化?非英语系统?

  12. 驱动程序?

  13. 硬件?

  14. 编码?

  15. 系统损坏? (错误的时间,磁盘错误,文件和路径名太长,磁盘已满,错误)

  16. 目标计算机的性质?虚拟机?国企?目标机器是真实机器吗?测试机器?

  17. 锁定/阻止/使用中的文件和注册表项?

  18. 是否存在恶意软件?几乎可以导致任何问题。






链接




I am currently working with visual studio 2017 with 4.6.1 .net framework. I created setup file for my desktop application the setup installs and runs perfectly in my system. The issue is that the setup installs successfully in other computers but the application not getting opened.

edit

Downloaded .net framework in client system but still same issue occurs.

edit 2

I ran a dependency scan using Dependency walker. It said there were a bunch of files the system could not find - error opening file. The system cannot find the files specified.

  API-MS-WIN-APPMODEL-RUNTIME-L1-1-0.DLL
  API-MS-WIN-CORE-WINRT-ERROR-L1-1-0.DLL
  API-MS-WIN-CORE-WINRT-L1-1-0.DLL
  API-MS-WIN-CORE-WINRT-ROBUFFER-L1-1-0.DLL
  API-MS-WIN-CORE-WINRT-STRING-L1-1-0.DLL
  API-MS-WIN-SHCORE-SCALING-L1-1-1.DLL
  DCOMP.DLL
  IESHIMS.DLL

Also, there was an error with modules with an x86 type found - including the setup.exe - but I am unaware how this happened. I have selected 64 wherever I saw the option listed. Please find the screenshot. If this is indeed the issue, how do I solve this?

解决方案

Application Launch Problems: Here is a short version: WPF application crashes when I launch. Chattier version.


Logs: Always check all event logs, application logs and MSI logs - if available. Just to mention it. Maybe try to attach debugger for testing as described here - provided the application gets off the ground at all. Then step through code.

The Usual Culprits: You probably just lack a runtime, have a bitness problem (32/64-bit) or insufficient permissions / privileges, or configuration errors (ini, xml, registry, etc...).

To summarize - torpedos, full spread below - nothing too dumb not to mention :-):


Missing Runtimes: First, always check for missing runtimes. For example: .Net, .Net Core, Java, Silverlight, Direct X (used even for applications now), VC++ Runtime, MS-XML (legacy), etc.... Remember that they come in different versions and some can not co-exist on the box whilst others can run side-by-side.


Error Code: Looking up error codes and exception messages.


Debugging Tools: Some information on debugging tools.


ProcMon.exe: The tool of the trade. The one-size-fits-all tool. The bee's knees, the topper-most, the quantum leap, the cat's pajamas (yes, it is a Top Gear Hamster allusion). It can be a challenge to use it effectively, but it is the best general-purpose debugging tool that is free.


Other Ideas:

  1. Configuration Settings?
    • Dev-box sins: Hard coded references? Test Servers / UAT links?
    • Manifests, INI files and XMLfiles?
    • Registry settings? HKLM / HKCU
    • Connection strings. See Authentication & Authorization section below as well.
  2. Platform & Bitness? (ARM, Intel 32 / 64, etc...).
    • Very common to read from wrong registry hive (the classic time waster):
      • HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\MyApp\MySettings (32-bit)
      • HKEY_LOCAL_MACHINE\SOFTWARE\MyApp\MySettings (64-bit)
  3. Prerequisites & Dependencies?
  4. Missing / Broken Registration (indirect dependencies)
  5. Permissions & Privilege? - local - ACL permissions and NT privileges?
  6. Authentication / Authorization - network related
    • Local user, domain user, Active Directory: group membership, group policy, etc...
    • Launching User: User profile issues? Maybe try with another user logged on where it fails?
    • Authentication Mode: Windows Authentication. SQL Server Authentication, etc...
  7. General Network & Proxy issues? (proxies, WINS, DNS and all the complexities involved in networking. UNC paths reachable?)
  8. Licensing? (conceivably related to hardware dongles and drivers)
  9. Security software interference? (software / hardware firewall, anti-virus, encryption tools and suites, etc...)
  10. OS version or edition? (Windows 7 problems)
  11. Localization? Non-English systems?
  12. Drivers?
  13. Hardware?
  14. Encoding?
  15. System corruption? (wrong time, disk errors, file and path names are too long, disk full, "wrong something")
  16. Target Machine Nature? Virtuals? SOE? Are the target machines real machines? Test machines?
  17. Locking / Blocking / In-Use files and registry keys?
  18. Malware? Can cause practically anything in terms of problems.


Links:

这篇关于在客户端系统中安装后,桌面应用程序无法打开的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆