5.6 SR1 Prof: can't find "s7wmedbx.dll"

Hello,

I have the same problem. I recently installed again the version 5.6 SR1 Prof and I can't find the mentioned file "s7wmedbx.dll" in any directory. Where is possbile to find it if the installation don't put that file as expected?

------------------------------------------------------------------------------------------
Split from Diganostic Buffer.

Towome

Hi,

why do you install SP1? Install newst Step 7 V5.6 with SP2 and HF3 and check behaviour again.

Regards,

Towome

 The newest hotfix is HF5

Hi all,

I installed as update the version 2017 SR2 (5.6) over the 5.6 SR1 and I found the file ("s7wmedbx.dll" file version 506.200.101.1) in the path: "C:\Program Files (x86)\Common Files\Siemens\s7wmedb\", however I still can't read the error text description from the diagnostic buffer. When I open the CPU buffer data, I got an "Unexpected file format" error warning box. Here are the details of the error:

Problem Event Name: APPCRASH
Application Name: S7WMEDAX.EXE
Application Version: 506.200.101.1
Application timestamp: 5d4a8a8a
Failed module name: ntdll.dll
Module version with errors: 6.1.7601.24545
Failed module timestamp: 5e0eb751
Exception code: c015000f
Exception offset: 0008442b
OS version: 6.1.7601.2.1.0.256.48
Locale ID: 1040
Additional information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Further information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

Hi all,

I installed the HF3 and nothing is changed, except some values in the details of the error:

Problem Event Name: APPCRASH
Application Name: S7WMEDAX.EXE
Application Version: 506.201.201.1
Application timestamp: 5e6786db
Failed module name: ntdll.dll
Module version with errors: 6.1.7601.24545
Failed module timestamp: 5e0eb751
Exception code: c015000f
Exception offset: 0008442b
OS version: 6.1.7601.2.1.0.256.48
Locale ID: 1040
Additional information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Further information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

I checked Windows (7 x64) integrity with command "sfc /scannow" (all good) and fixed registry error with Wisecleaner.

Regards.