Skip to Content
avatar image
Former Member

WPF Agentryclient 70.14 crashing on Windows 7

Hi experts,

I'm working with a Windows 7 Enterprise Notebook, on which the WPF AgentryClient was running without problems until version 70.12.

The installation of version 70.14 worked also without problems, but when starting it, is just crashes. In the event viewer the following error is shown:

Problemereignisname: CLR20r3
Problemsignatur 01: AgentryClient.exe
Problemsignatur 02: 7.14.0.999
Problemsignatur 03: 58d04a35
Problemsignatur 04: PresentationFramework
Problemsignatur 05: 4.6.1055.0
Problemsignatur 06: 563c1d45
Problemsignatur 07: 2f3
Problemsignatur 08: f
Problemsignatur 09: System.IO.FileNotFoundException
Betriebsystemversion: 6.1.7601.2.1.0.256.4
Gebietsschema-ID: 1031
Zusatzinformation 1: 0a9e
Zusatzinformation 2: 0a9e372d3b4ad19135b953a78882e789
Zusatzinformation 3: 0a9e
Zusatzinformation 4: 0a9e372d3b4ad19135b953a78882e789

So the issue has obviously something to do with the .Net Framework.

The current version 4.6.2 is installed and also all available Microsoft Visual C++ redistributable packs (x86 & x64).

Even reinstallation of .NET didn't fix the issue.

Only when I installed the Visual Studio 2017 community edition, the AgentryClient suddenly worked.

Has someone made the same experience and knows which addtional dependencies the 70.14 version has compared to version 70.12 ?

Regards,

Christian


Add comment
10|10000 characters needed characters exceeded

  • Hello Christian,

    Were you able to find solution for your query? If so, you may share it with community, it will help others.

    If not yet, i would suggest you to reach out to SAP support team by raising an OSS ticket.

    Regards,

    JK (Moderator)

  • Get RSS Feed

1 Answer

  • avatar image
    Former Member
    Jul 12, 2017 at 08:43 AM

    Hi,

    it seems this was related to the implemented OpenScan-interface. I had to update the reference to the AgentryClientSDK.dll.

    The Agentry client is suppressing any error message and there is also no log file which made it hard to figure out the root cause.

    Regards,

    Christian

    Add comment
    10|10000 characters needed characters exceeded