Hikvision iVMS client not running in wine-staging

Questions about Wine on Linux
Locked
agorwadia
Level 2
Level 2
Posts: 15
Joined: Sat Dec 22, 2018 5:57 am

Hikvision iVMS client not running in wine-staging

Post by agorwadia »

I have installed iVMS-4200 Lite (v1.0.0.4) - downloaded the exe from HikVision's own website.
Installed it with wine. I have installed wine64 as default for my system.

Upon opening the desktop shortcut nothing happened. So I looked into it, came across MakeUseOff website and tried

Code: Select all

wine ivms-4200 Lite.exe &> debug.txt 
and got the following error messages. Not sure what it means. I find it strange why wine is looking for IVMS-4200.exe in system32 folder. Also, I am unsure about the NPF driver issue.

I am very new to wine. I tried testing my current wine installation with Notepad++ and worked fine.

IVMS-4200 program is mentioned on winehq as a positive - there are people using it without any issues.

for info: - I am using MX Linux 17. Installed winehq-staging from MX Package Installer as per MX Linux guidelines.

Any help would be greatly appreciated.

Ankit

-------------- debug.txt output ----------------
  • fixme:winediag:start_process Wine Staging 2.21 is a testing version containing experimental patches.
    fixme:winediag:start_process Please mention your exact version when filing bug reports on winehq.org.
    fixme:ndis:NdisRegisterProtocol (0x53e078, 0x6475e8, 0x53df00, 208): stub
    err:winedevice:async_create_driver failed to create driver L"NPF": c0000001
    wine: cannot find L"C:\\windows\\system32\\IVMS-4200.exe"
jkfloris
Level 12
Level 12
Posts: 3141
Joined: Thu Aug 14, 2014 10:10 am

Re: Hikvision iVMS client not running in wine-staging

Post by jkfloris »

wine ivms-4200 Lite.exe &> debug.txt
Put quotes around the name

Code: Select all

wine "ivms-4200 Lite.exe"
agorwadia
Level 2
Level 2
Posts: 15
Joined: Sat Dec 22, 2018 5:57 am

Re: Hikvision iVMS client not running in wine-staging

Post by agorwadia »

Not sure how your suggestion would help the matter because I do not believe the problem is regarding running the app, its the reason for not running.

Anyways, when I tried with the "" quotes, error message was:

Code: Select all

wine: cannot find 'ivms-4200 Lite.exe'
jkfloris
Level 12
Level 12
Posts: 3141
Joined: Thu Aug 14, 2014 10:10 am

Re: Hikvision iVMS client not running in wine-staging

Post by jkfloris »

wine: cannot find L"C:\\windows\\system32\\IVMS-4200.exe"
and
wine: cannot find 'ivms-4200 Lite.exe'
In both cases there is a message that there is no file named "ivms-4200" or "ivms-4200 Lite.exe"
Are you in the directory where the exe-file is when you run the wine command?
agorwadia
Level 2
Level 2
Posts: 15
Joined: Sat Dec 22, 2018 5:57 am

Re: Hikvision iVMS client not running in wine-staging

Post by agorwadia »

Dear jkfloris,

Thanks for correcting me. I was not investigating the issue correctly.

Having navigated to the appropriate directory I ran the code again and I got the below set of error messages.

It appears that there are a couple of issues: one with NPF driver and ODBC driver and other with some DLL files. What I find strange is that IVMS client programs has been tested and reported OK by other users on WineHQ so I am unsure why I am getting this issue?

The NPF driver issues appears to be more generic to my wine as I got it even when incorrect file path was specified, as seen in my last error log. The other errors should be specific to this program, I believe.

I am running wine-2.21 (Staging) which I downloaded with MX Package Installer and I am using 64 bit prefix.

Any thoughts on how to resolve these errors??

Thanks,
A

Code: Select all

$ wine --version
wine-2.21 (Staging)
ERROR LOG
fixme:winediag:start_process Wine Staging 2.21 is a testing version containing experimental patches.
fixme:winediag:start_process Please mention your exact version when filing bug reports on winehq.org.
fixme:ndis:NdisRegisterProtocol (0x53e078, 0x6475e8, 0x53df00, 208): stub
err:winedevice:async_create_driver failed to create driver L"NPF": c0000001
err:winediag:ODBC_LoadDriverManager failed to open library "libodbc.so.2": libodbc.so.2: cannot open shared object file: No such file or directory
err:module:attach_process_dlls "log4cxx.dll" failed to initialize, aborting
err:module:LdrInitializeThunk Main exe initialization for L"C:\\Program Files\\iVMS-4200 Lite\\ivms-4200 Lite.exe" failed, status e06d7363
jkfloris
Level 12
Level 12
Posts: 3141
Joined: Thu Aug 14, 2014 10:10 am

Re: Hikvision iVMS client not running in wine-staging

Post by jkfloris »

What I find strange is that IVMS client programs has been tested and reported OK by other users on WineHQ so I am unsure why I am getting this issue?
According to the Wine AppDB [1], the application gets a gold rating in a 32-bit prefix and some winetricks overrides:

Code: Select all

winetricks -q jet40 mdac28 riched30 windowscodecs wininet vcrun6 wsh56
[1] https://appdb.winehq.org/objectManager. ... &iId=35493
agorwadia
Level 2
Level 2
Posts: 15
Joined: Sat Dec 22, 2018 5:57 am

Re: Hikvision iVMS client not running in wine-staging

Post by agorwadia »

Dear jkfloris,

Thanks for the clarification. I did wonder what the line under 'Additional Comments' meant. Very new to Linux you see and especially wine so I couldn't guess it was a requirement.

Anyhow, I am have installed wine64 prefix. So should I create a separate win32 prefix and re-install IVMS? Or should it work with this installation? I would guess the latter but I am unsure.

I presume the winetricks overides have to be run every time or is it at install only?

Would you be able to provide some further guidance please?

Much appreciated.

Thanks,
AG
jkfloris
Level 12
Level 12
Posts: 3141
Joined: Thu Aug 14, 2014 10:10 am

Re: Hikvision iVMS client not running in wine-staging

Post by jkfloris »

Anyhow, I am have installed wine64 prefix. So should I create a separate win32 prefix and re-install IVMS? Or should it work with this installation?
If you have other applications installed in the default wineprefix, then I recommend to create a new wineprefix. The winetricks overrides can break the other programs.
By trial and error you can find out if the 32-bit prefix is still necessary.
I presume the winetricks overides have to be run every time or is it at install only?
Winetricks installs some dll-files, so you only have to run this command once.
agorwadia
Level 2
Level 2
Posts: 15
Joined: Sat Dec 22, 2018 5:57 am

Re: Hikvision iVMS client not running in wine-staging

Post by agorwadia »

Dear jkfloris,

Thanks for the clarification. I wiped the 64-bit prefix to be safe and installed a fresh 32-bit prefix. All went ok till then.

Then I ran the winetricks code and got the below set of failure messages. Apparently winetricks is trying to fetch files from Windows servers and unable to get all of what it asks for. Perhaps files have been moved.

Any idea how I can get around it?

Thanks,
AG

Code: Select all

winetricks -q jet40 mdac28 riched30 windowscodecs wininet vcrun6 wsh56
Using winetricks 20170101 - sha1sum: c844fda0cca25ac9ed0ed1b55cd138cab6a4af16 with wine-2.21 (Staging) and WINEARCH=win32
Executing w_do_call jet40
Executing load_jet40 
Executing w_do_call mdac27
Executing load_mdac27 
Executing mkdir -p /home/ankit/.cache/winetricks/mdac27
Executing cd /home/ankit/.cache/winetricks/mdac27
Downloading http://download.microsoft.com/download/3/b/f/3bf74b01-16ba-472d-9a8c-42b2b4fa0d76/mdac_typ.exe to /home/ankit/.cache/winetricks/mdac27
--2018-12-31 17:51:38--  http://download.microsoft.com/download/3/b/f/3bf74b01-16ba-472d-9a8c-42b2b4fa0d76/mdac_typ.exe
Resolving download.microsoft.com (download.microsoft.com)... 23.57.113.23, 2600:1411:0:1a3::e59, 2600:1411:0:182::e59
Connecting to download.microsoft.com (download.microsoft.com)|23.57.113.23|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2018-12-31 17:51:40 ERROR 404: Not Found.

Executing cd /home/ankit/.cache/winetricks/mdac27
Downloading https://web.archive.org/web/http://download.microsoft.com/download/3/b/f/3bf74b01-16ba-472d-9a8c-42b2b4fa0d76/mdac_typ.exe to /home/ankit/.cache/winetricks/mdac27
--2018-12-31 17:51:41--  https://web.archive.org/web/http://download.microsoft.com/download/3/b/f/3bf74b01-16ba-472d-9a8c-42b2b4fa0d76/mdac_typ.exe
Resolving web.archive.org (web.archive.org)... 207.241.224.26
Connecting to web.archive.org (web.archive.org)|207.241.224.26|:443... connected.
HTTP request sent, awaiting response... 302 FOUND
Location: https://web.archive.org/web/20170101154733/http://download.microsoft.com/download/3/b/f/3bf74b01-16ba-472d-9a8c-42b2b4fa0d76/mdac_typ.exe [following]
--2018-12-31 17:51:44--  https://web.archive.org/w
eb/20170101154733/http://download.microsoft.com/download/3/b/f/3bf74b01-16ba-472d-9a8c-42b2b4fa0d76/mdac_typ.exe
Reusing existing connection to web.archive.org:443.
HTTP request sent, awaiting response... 404 Not Found
2018-12-31 17:51:46 ERROR 404: Not Found.

------------------------------------------------------
Downloading https://web.archive.org/web/http://download.microsoft.com/download/3/b/f/3bf74b01-16ba-472d-9a8c-42b2b4fa0d76/mdac_typ.exe failed
------------------------------------------------------
jkfloris
Level 12
Level 12
Posts: 3141
Joined: Thu Aug 14, 2014 10:10 am

Re: Hikvision iVMS client not running in wine-staging

Post by jkfloris »

Using winetricks 20170101 - sha1sum: c844fda0cca25ac9ed0ed1b55cd138cab6a4af16 with wine-2.21 (Staging) and WINEARCH=win32
Your winetricks version is to old. Please update to a newer version
https://wiki.winehq.org/Winetricks
agorwadia
Level 2
Level 2
Posts: 15
Joined: Sat Dec 22, 2018 5:57 am

Re: Hikvision iVMS client not running in wine-staging

Post by agorwadia »

Dear jkfloris,

Updated winetricks to the latest version and was managed to run IVMS as I do in my Win10.

Thanks very much for your patience and assistance.

When I ran winetricks command a message I remember noticing was that my wine is v2.2 and it recommended using 3.0. Now, I recently moved from using Ubuntu to MX Linux and so far I have only used MX package manager to install winehq/winestaging. I would really like to update wine to v3.0 as recommended by winetricks but I would like to do it in a manner that does't steer me off the package manager of MX Linux.

Is there a stable and reliable way of upgrading wine without causing any grief?

Thanks,
Regards
jkfloris
Level 12
Level 12
Posts: 3141
Joined: Thu Aug 14, 2014 10:10 am

Re: Hikvision iVMS client not running in wine-staging

Post by jkfloris »

MX Linux is Debian Stable based. You should be able to use the Debian Stable (Stretch) WineHQ repository.
https://wiki.winehq.org/Debian
agorwadia
Level 2
Level 2
Posts: 15
Joined: Sat Dec 22, 2018 5:57 am

Re: Hikvision iVMS client not running in wine-staging

Post by agorwadia »

Dear jkfloris,

Thanks for the input, I shall give it a try.

AG
agorwadia
Level 2
Level 2
Posts: 15
Joined: Sat Dec 22, 2018 5:57 am

Re: Hikvision iVMS client not running in wine-staging

Post by agorwadia »

Hi jkfloris,

About a year ago you helped me install iVMS on my MX Linux. I had to do a clean system install while migrating from MX18 to 19. So I am trying to install iVMS again using the method you explained to me.

However, this time around I am experiencing some strange issues.

1) I installed wine from MX Package Installer
2) Created win32 prefix using the method described on the FAQ
3) Install winetricks
4) ran the winetricks code

Code: Select all

sh winetricks -q jet40 mdac28 riched30 windowscodecs wininet vcrun6 wsh56
5) the code said wsh56 as outdated so I ran wintricks with wsh57 as recommended and that was installed too.
6) when I tried installaing the .exe it shows an error - something to do with NFP service start issue - presumably some driver issue. I was getting the same issue last year from memory.
7) Also, the install script shows numerous error lines and gets stuck when reaching 'extract icon'.
8) Debug text attached for reference (although I couldn't get complete text as the installer got stuck).

What could be issue?

Can you help.

Thanks
AG

Code: Select all

000b:fixme:thread:create_user_shared_data_thread Creating user shared data update thread.
000b:fixme:winediag:start_process Wine Staging 4.18 is a testing version containing experimental patches.
000b:fixme:winediag:start_process Please mention your exact version when filing bug reports on winehq.org.
000f:fixme:thread:create_user_shared_data_thread Creating user shared data update thread.
0012:fixme:thread:create_user_shared_data_thread Creating user shared data update thread.
0016:fixme:ndis:NdisRegisterProtocol (000000000054F838, 00000000006775E8, 000000000054F6C0, 208): stub
0016:err:ntoskrnl:ZwLoadDriver failed to create driver L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\NPF": c0000001
000f:fixme:service:scmdatabase_autostart_services Auto-start service L"NPF" failed to start: 31
000d:fixme:thread:create_user_shared_data_thread Creating user shared data update thread.
0019:fixme:thread:create_user_shared_data_thread Creating user shared data update thread.
0021:fixme:thread:create_user_shared_data_thread Creating user shared data update thread.
001c:fixme:thread:create_user_shared_data_thread Creating user shared data update thread.
0027:fixme:thread:create_user_shared_data_thread Creating user shared data update thread.
0009:fixme:ole:CoInitializeSecurity (0032F818,-1,00000000,00000000,6,2,00000000,8192,00000000) - stub!
0009:fixme:gdiplus:resample_bitmap_pixel_premult Unimplemented interpolation 7
0009:fixme:ntdll:NtLockFile I/O completion on lock not implemented yet
002f:fixme:ver:GetCurrentPackageId (0x12fff2c (nil)): stub
0009:fixme:ole:NdrCorrelationInitialize (0032DBC0, 0032D74C, 1024, 0x0): semi-stub
0009:fixme:ole:NdrCorrelationFree (0032CC90): stub
0032:fixme:thread:create_user_shared_data_thread Creating user shared data update thread.
0037:fixme:thread:create_user_shared_data_thread Creating user shared data update thread.
0047:fixme:thread:create_user_shared_data_thread Creating user shared data update thread.
0047:err:ole:std_release_marshal_data could not map object ID to stub manager, oxid=47, oid=2
0047:err:ole:CoReleaseMarshalData StdMarshal ReleaseMarshalData failed with error 0x8001011d
0050:fixme:thread:create_user_shared_data_thread Creating user shared data update thread.
0050:err:ole:std_release_marshal_data could not map object ID to stub manager, oxid=50, oid=2
0050:err:ole:CoReleaseMarshalData StdMarshal ReleaseMarshalData failed with error 0x8001011d
0059:fixme:thread:create_user_shared_data_thread Creating user shared data update thread.
0059:err:ole:std_release_marshal_data could not map object ID to stub manager, oxid=59, oid=2
0059:err:ole:CoReleaseMarshalData StdMarshal ReleaseMarshalData failed with error 0x8001011d
0062:fixme:thread:create_user_shared_data_thread Creating user shared data update thread.
0062:err:ole:std_release_marshal_data could not map object ID to stub manager, oxid=62, oid=2
0062:err:ole:CoReleaseMarshalData StdMarshal ReleaseMarshalData failed with error 0x8001011d
0009:fixme:apphelp:ApphelpCheckInstallShieldPackage stub: 0032F1CC L"C:\\users\\ankit\\Temp\\{856E5E8A-8CE6-48CC-B869-78334F3FD548}\\Disk1\\data1.hdr"
006b:fixme:thread:create_user_shared_data_thread Creating user shared data update thread.
002f:fixme:explorerframe:taskbar_list_SetProgressState iface 0019E7E8, hwnd 0002007C, flags 2 stub!
002f:fixme:explorerframe:taskbar_list_SetProgressValue iface 0019E7E8, hwnd 0002007C, ullCompleted 1, ullTotal 64 stub!
0009:fixme:sfc:SRSetRestorePointW 007FDAD8 007FDBC0
0073:fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub
0073:fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub
0076:fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub
0076:fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub
0076:fixme:advapi:DecryptFileW (L"C:\\users\\ankit\\Temp\\{f65db027-aff3-4070-886a-0d87064aabb1}\\", 00000000): stub
0073:fixme:ole:CoInitializeSecurity (0032F5EC,-1,00000000,00000000,6,2,00000000,12288,00000000) - stub!
007b:fixme:shell:SHAutoComplete stub
0076:fixme:advapi:DecryptFileW (L"C:\\users\\ankit\\Temp\\{f65db027-aff3-4070-886a-0d87064aabb1}\\", 00000000): stub
0073:fixme:wuapi:automatic_updates_Pause 
0073:fixme:sfc:SRSetRestorePointW 0032F4C0 0032F6D0
0073:fixme:wuapi:automatic_updates_Resume 
007d:fixme:clusapi:GetNodeClusterState ((null),0032ECB4) stub!
007d:fixme:advapi:DecryptFileA ("c:\\8cd1ffdd165559dbece6db0355\\", 00000000): stub
0080:fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub
0080:err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution.
0080:err:winediag:load_gssapi_krb5 Failed to load libgssapi_krb5, Kerberos SSP support will not be available.
0080:fixme:security:GetWindowsAccountDomainSid (0032F304 001510CC 0032F300): semi-stub
0080:fixme:secur32:GetComputerObjectNameW NameFormat 7 not implemented
0080:fixme:ntdll:NtLockFile I/O completion on lock not implemented yet
0083:fixme:clusapi:GetNodeClusterState ((null),0032ECB4) stub!
0083:fixme:advapi:DecryptFileA ("c:\\4b871980240566372a628be5\\", 00000000): stub
0086:fixme:thread:create_user_shared_data_thread Creating user shared data update thread.
0086:fixme:heap:RtlSetHeapInformation 0x4e0000 0 0x22fce0 4 stub
0086:fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub
0086:fixme:heap:RtlSetHeapInformation 0x5f0000 0 0x22ead0 4 stub
0086:err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution.
0086:fixme:security:GetWindowsAccountDomainSid (000000000022EC10 0000000000069168 000000000022EC08): semi-stub
0086:fixme:secur32:GetComputerObjectNameW NameFormat 7 not implemented
0086:fixme:ntdll:NtLockFile I/O completion on lock not implemented yet
0089:fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub
0089:fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub
008c:fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub
008c:fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub
008c:fixme:advapi:DecryptFileW (L"C:\\users\\ankit\\Temp\\{1b103cea-f037-4504-81de-956057b442c3}\\", 00000000): stub
0089:fixme:ole:CoInitializeSecurity (0032F5EC,-1,00000000,00000000,6,2,00000000,12288,00000000) - stub!
0091:fixme:shell:SHAutoComplete stub
008c:fixme:advapi:DecryptFileW (L"C:\\users\\ankit\\Temp\\{1b103cea-f037-4504-81de-956057b442c3}\\", 00000000): stub
0089:fixme:wuapi:automatic_updates_Pause 
0089:fixme:sfc:SRSetRestorePointW 0032F4C0 0032F6D0
0089:fixme:wuapi:automatic_updates_Resume 
0093:fixme:thread:create_user_shared_data_thread Creating user shared data update thread.
0093:err:ole:std_release_marshal_data could not map object ID to stub manager, oxid=93, oid=2
0093:err:ole:CoReleaseMarshalData StdMarshal ReleaseMarshalData failed with error 0x8001011d
00a0:fixme:thread:create_user_shared_data_thread Creating user shared data update thread.
00a2:fixme:thread:create_user_shared_data_thread Creating user shared data update thread.
00b1:fixme:thread:create_user_shared_data_thread Creating user shared data update thread.
00b3:fixme:ndis:NdisRegisterProtocol (000000000054F838, 00000000006775E8, 000000000054F6C0, 208): stub
00b3:err:ntoskrnl:ZwLoadDriver failed to create driver L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\NPF": c0000001
00b9:fixme:thread:create_user_shared_data_thread Creating user shared data update thread.
00bb:fixme:ndis:NdisRegisterProtocol (000000000054F838, 00000000006775E8, 000000000054F6C0, 208): stub
00bb:err:ntoskrnl:ZwLoadDriver failed to create driver L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\NPF": c0000001
00bf:fixme:thread:create_user_shared_data_thread Creating user shared data update thread.
00c1:fixme:ndis:NdisRegisterProtocol (000000000054F838, 00000000006775E8, 000000000054F6C0, 208): stub
00c1:err:ntoskrnl:ZwLoadDriver failed to create driver L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\NPF": c0000001
00c5:fixme:thread:create_user_shared_data_thread Creating user shared data update thread.
00c7:fixme:ndis:NdisRegisterProtocol (000000000054F838, 00000000006775E8, 000000000054F6C0, 208): stub
00c7:err:ntoskrnl:ZwLoadDriver failed to create driver L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\NPF": c0000001
00c9:fixme:ver:GetCurrentPackageId (0xb4ff2c (nil)): stub
02d1:fixme:thread:create_user_shared_data_thread Creating user shared data update thread.
02d3:fixme:thread:create_user_shared_data_thread Creating user shared data update thread.
02d5:fixme:thread:create_user_shared_data_thread Creating user shared data update thread.
02d7:fixme:thread:create_user_shared_data_thread Creating user shared data update thread.
006b:err:ole:std_release_marshal_data could not map object ID to stub manager, oxid=6b, oid=2
006b:err:ole:CoReleaseMarshalData StdMarshal ReleaseMarshalData failed with error 0x8001011d
0032:err:ole:std_release_marshal_data could not map object ID to stub manager, oxid=32, oid=2
0032:err:ole:CoReleaseMarshalData StdMarshal ReleaseMarshalData failed with error 0x8001011d
jkfloris
Level 12
Level 12
Posts: 3141
Joined: Thu Aug 14, 2014 10:10 am

Re: Hikvision iVMS client not running in wine-staging

Post by jkfloris »

0080:err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution.
Does installing the winbind package help?

Code: Select all

apt install winbind
On the Hikvision website there are several installation packages. Which one do you use?
agorwadia
Level 2
Level 2
Posts: 15
Joined: Sat Dec 22, 2018 5:57 am

Re: Hikvision iVMS client not running in wine-staging

Post by agorwadia »

Dear jkfloris,

Thanks for the reply.

The file I am using is iVMS-4200(v2.6.2.7).exe.

I installed winbind but still the same error as before.

I will retry with a newer iVMS-4200 3.2.0.10 and see if there's any changes. The thing is as soon as the install beings, it beings with a series of errors...

Feels like something fundamentally is wrong with wine installation. But that's just a guess. I wouldn't know.

Code: Select all

ankit@AG-mx:~
$ wine /media/ankit/DATA/Software/iVMS-4200\(v2.6.2.7\)/iVMS-4200\(v2.6.2.7\).exe > ~/Desktop/debug.txt 
0041:err:ole:std_release_marshal_data could not map object ID to stub manager, oxid=4000000041, oid=2
0041:err:ole:CoReleaseMarshalData StdMarshal ReleaseMarshalData failed with error 0x8001011d
004a:err:ole:std_release_marshal_data could not map object ID to stub manager, oxid=490000004a, oid=2
004a:err:ole:CoReleaseMarshalData StdMarshal ReleaseMarshalData failed with error 0x8001011d
0053:err:ole:std_release_marshal_data could not map object ID to stub manager, oxid=5200000053, oid=2
Ankit
agorwadia
Level 2
Level 2
Posts: 15
Joined: Sat Dec 22, 2018 5:57 am

Re: Hikvision iVMS client not running in wine-staging

Post by agorwadia »

Tried with newer version still very similar errors.

Interesting thing is that NPF driver errors is the main error. The installation for the newer version failed at NPF driver install stage

Code: Select all

ankit@AG-mx:~
$ wine ivms/iVMS-4200\(V3.2.0.10_E\).exe > ~/Desktop/debug2.txt
001c:err:ntoskrnl:ZwLoadDriver failed to create driver L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\NPF": c0000001
0014:err:service:process_send_command service protocol error - failed to write pipe!
003f:err:richedit:ReadColorTbl malformed entry
003f:err:richedit:ReadColorTbl malformed entry
003f:err:richedit:ReadColorTbl malformed entry
.
.
.
0048:err:mscoree:LoadLibraryShim error reading registry key for installroot
0048:err:mscoree:LoadLibraryShim error reading registry key for installroot
0048:err:mscoree:LoadLibraryShim error reading registry key for installroot
0048:err:mscoree:LoadLibraryShim error reading registry key for installroot
0048:err:mscoree:LoadLibraryShim error reading registry key for installroot
0048:err:mscoree:LoadLibraryShim error reading registry key for installroot
0048:err:mscoree:LoadLibraryShim error reading registry key for installroot
0048:err:mscoree:LoadLibraryShim error reading registry key for installroot
01d6:err:ntoskrnl:ZwLoadDriver failed to create driver L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\NPF": c0000001
006c:err:service:process_send_command service protocol error - failed to write pipe!
01dd:err:ntoskrnl:ZwLoadDriver failed to create driver L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\NPF": c0000001
01d8:err:service:process_send_command service protocol error - failed to write pipe!
01e3:err:ntoskrnl:ZwLoadDriver failed to create driver L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\NPF": c0000001
006b:err:service:process_send_command service protocol error - failed to write pipe!
wine: Unhandled page fault on read access to 0x0000008c at address 0x7bc467d0 (thread 006b), starting debugger...
01eb:err:ntoskrnl:ZwLoadDriver failed to create driver L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\NPF": c0000001
01ed:err:service:process_send_command service protocol error - failed to write pipe!
01e9:fixme:dbghelp:elf_search_auxv can't find symbol in module
01e9:fixme:dbghelp:elf_search_auxv can't find symbol in module
01e9:fixme:dbghelp:elf_search_auxv can't find symbol in module
01e9:fixme:dbghelp:elf_search_auxv can't find symbol in module
01e9:fixme:dbghelp:elf_search_auxv can't find symbol in module
01e9:fixme:dbghelp:elf_search_auxv can't find symbol in module
01e9:fixme:dbghelp:elf_search_auxv can't find symbol in module
01e9:fixme:dbghelp:elf_search_auxv can't find symbol in module
02a1:err:rpc:RpcAssoc_BindConnection receive failed with error 1726
Killed
[code]
agorwadia
Level 2
Level 2
Posts: 15
Joined: Sat Dec 22, 2018 5:57 am

Re: Hikvision iVMS client not running in wine-staging

Post by agorwadia »

I just noticed some errors when I tried wiping all prefixes and creating a fresh 32-bit prefix
Does this reflect some fundamental issues with the wine install that may be affecting my install of ivms?

A

Code: Select all

ankit@AG-mx:~
$ WINEARCH=win32 WINEPREFIX=/home/ankit/.wine winecfg
wine: created the configuration directory '/home/ankit/.wine'
0012:err:ole:marshal_object couldn't get IPSFactory buffer for interface {00000131-0000-0000-c000-000000000046}
0012:err:ole:marshal_object couldn't get IPSFactory buffer for interface {6d5140c1-7436-11ce-8034-00aa006009fa}
0012:err:ole:StdMarshalImpl_MarshalInterface Failed to create ifstub, hres=0x80004002
0012:err:ole:CoMarshalInterface Failed to marshal the interface {6d5140c1-7436-11ce-8034-00aa006009fa}, 80004002
0012:err:ole:get_local_server_stream Failed: 80004002
0014:err:ole:marshal_object couldn't get IPSFactory buffer for interface {00000131-0000-0000-c000-000000000046}
0014:err:ole:marshal_object couldn't get IPSFactory buffer for interface {6d5140c1-7436-11ce-8034-00aa006009fa}
0014:err:ole:StdMarshalImpl_MarshalInterface Failed to create ifstub, hres=0x80004002
0014:err:ole:CoMarshalInterface Failed to marshal the interface {6d5140c1-7436-11ce-8034-00aa006009fa}, 80004002
0014:err:ole:get_local_server_stream Failed: 80004002
Could not load wine-gecko. HTML rendering will be disabled.
wine: configuration in '/home/ankit/.wine' has been updated.

And then when I tried installing from the new prefix...

Code: Select all

 WINEPREFIX=/home/ankit/.wine32 wine start ~/ivms/iVMS-4200\(V3.2.0.10_E\).exe > ~/Desktop/debug3.txt
wine: created the configuration directory '/home/ankit/.wine32'
0009:err:file:init_redirects cannot open L"C:\\windows" (c000000f)
0012:err:ole:marshal_object couldn't get IPSFactory buffer for interface {00000131-0000-0000-c000-000000000046}
0012:err:ole:marshal_object couldn't get IPSFactory buffer for interface {6d5140c1-7436-11ce-8034-00aa006009fa}
0012:err:ole:StdMarshalImpl_MarshalInterface Failed to create ifstub, hres=0x80004002
0012:err:ole:CoMarshalInterface Failed to marshal the interface {6d5140c1-7436-11ce-8034-00aa006009fa}, 80004002
0012:err:ole:get_local_server_stream Failed: 80004002
0014:err:ole:marshal_object couldn't get IPSFactory buffer for interface {00000131-0000-0000-c000-000000000046}
0014:err:ole:marshal_object couldn't get IPSFactory buffer for interface {6d5140c1-7436-11ce-8034-00aa006009fa}
0014:err:ole:StdMarshalImpl_MarshalInterface Failed to create ifstub, hres=0x80004002
0014:err:ole:CoMarshalInterface Failed to marshal the interface {6d5140c1-7436-11ce-8034-00aa006009fa}, 80004002
0014:err:ole:get_local_server_stream Failed: 80004002
Could not load wine-gecko. HTML rendering will be disabled.
Could not load wine-gecko. HTML rendering will be disabled.
wine: configuration in '/home/ankit/.wine32' has been updated.
0009:err:start:wmain Unknown option 'L"/home/ankit/ivms/iVMS-4200(V3.2.0.10_E).exe"'
User avatar
Bob Wya
Level 12
Level 12
Posts: 3068
Joined: Sat Oct 16, 2010 7:40 pm

Re: Hikvision iVMS client not running in wine-staging

Post by Bob Wya »

agorwadia wrote: Sun Jan 26, 2020 10:49 pm ...

And then when I tried installing from the new prefix...

Code: Select all

WINEARCH=win32 WINEPREFIX=/home/ankit/.wine winecfg
...
WINEPREFIX=/home/ankit/.wine32 wine start ~/ivms/iVMS-4200\(V3.2.0.10_E\).exe > ~/Desktop/debug3.txt
wine: created the configuration directory '/home/ankit/.wine32'
...
0009:err:start:wmain Unknown option 'L"/home/ankit/ivms/iVMS-4200(V3.2.0.10_E).exe"'
That should be written as:

Code: Select all

export WINEPREFIX=/home/ankit/.wine32
WINEARCH=win32  wineboot -u
wine start /unix "/home/ankit/ivms/iVMS-4200(V3.2.0.10_E).exe" > ~/Desktop/debug3.txt
You are using mismatched WINEPREFIX paths - so the second command actually sets up a new WINEPREFIX.
You can see this clearly, from the Wine terminal output.

Bob
agorwadia
Level 2
Level 2
Posts: 15
Joined: Sat Dec 22, 2018 5:57 am

Re: Hikvision iVMS client not running in wine-staging

Post by agorwadia »

Hi Bob,

Thanks for pointing out the issue with prefix. I reinstalled wine using MX apt repository. Created the prefix as you suggested. All went ok till that part.

Then I applied the winetricks code.

Code: Select all

winetricks -q jet40 mdac28 riched30 windowscodecs wininet vcrun6 wsh56
But there were some errors but the install did complete after sometime.

After that I installed iVMS but ran into same set of errors as before.

See the below.

The install window opened up but a number of things missing (I presume that because the errors mentioned about menubuilder bitmaps) Then the installer stucked at NFP driver stage as before.

I strongly think that the drivers required for ivms are not being installed correctly. That could be at the stage of winetricks code or perhaps at the very source of wine installation.

For ref, my current wine version is as shown below:

Code: Select all

$ wine --version
wine-4.0 (Debian 4.0-2)
Errors occurred during iVMS installation.

Code: Select all

ankit@AG-mx:~
$ wine start /unix "/home/ankit/ivms/iVMS-4200(V3.2.0.10_E).exe" > ~/Desktop/debug3.txt
000d:err:menubuilder:convert_to_native_icon error 0x88982F0C copying bitmaps
000d:err:menubuilder:convert_to_native_icon error 0x88982F04 committing encoder
000d:err:menubuilder:convert_to_native_icon error 0x88982F0C copying bitmaps
000d:err:menubuilder:convert_to_native_icon error 0x88982F04 committing encoder
000d:err:menubuilder:convert_to_native_icon error 0x88982F0C copying bitmaps
000d:err:menubuilder:convert_to_native_icon error 0x88982F04 committing encoder
000d:err:menubuilder:convert_to_native_icon error 0x88982F0C copying bitmaps
000d:err:menubuilder:convert_to_native_icon error 0x88982F04 committing encoder
000d:err:menubuilder:convert_to_native_icon error 0x88982F0C copying bitmaps
000d:err:menubuilder:convert_to_native_icon error 0x88982F04 committing encoder
000d:err:menubuilder:convert_to_native_icon error 0x88982F0C copying bitmaps
000d:err:menubuilder:convert_to_native_icon error 0x88982F04 committing encoder
000d:err:menubuilder:convert_to_native_icon error 0x88982F0C copying bitmaps
000d:err:menubuilder:convert_to_native_icon error 0x88982F04 committing encoder
000d:err:menubuilder:convert_to_native_icon error 0x88982F0C copying bitmaps
000d:err:menubuilder:convert_to_native_icon error 0x88982F04 committing encoder
000d:err:menubuilder:convert_to_native_icon error 0x88982F0C copying bitmaps
000d:err:menubuilder:convert_to_native_icon error 0x88982F04 committing encoder
000d:err:menubuilder:convert_to_native_icon error 0x88982F0C copying bitmaps
000d:err:menubuilder:convert_to_native_icon error 0x88982F04 committing encoder
000d:err:menubuilder:convert_to_native_icon error 0x88982F0C copying bitmaps
000d:err:menubuilder:convert_to_native_icon error 0x88982F04 committing encoder
000d:err:menubuilder:convert_to_native_icon error 0x88982F0C copying bitmaps
000d:err:menubuilder:convert_to_native_icon error 0x88982F04 committing encoder
ankit@AG-mx:~
$ 0042:err:winediag:load_gssapi_krb5 Failed to load libgssapi_krb5, Kerberos SSP support will not be available.
0043:err:mscoree:LoadLibraryShim error reading registry key for installroot
0043:err:mscoree:LoadLibraryShim error reading registry key for installroot
0043:err:mscoree:LoadLibraryShim error reading registry key for installroot
0043:err:mscoree:LoadLibraryShim error reading registry key for installroot
0058:err:ole:apartment_getclassobject DllGetClassObject returned error 0x80040154 for dll L"C:\\windows\\system32\\windowscodecs.dll"
0058:err:ole:CoGetClassObject no class object {3692ca39-e082-4350-9e1f-3704cb083cd5} could be created for context 0x1
0066:err:ole:apartment_getclassobject DllGetClassObject returned error 0x80040154 for dll L"C:\\windows\\system32\\windowscodecs.dll"
0066:err:ole:CoGetClassObject no class object {3692ca39-e082-4350-9e1f-3704cb083cd5} could be created for context 0x1
0081:err:ntoskrnl:ZwLoadDriver failed to create driver L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\NPF": c0000001
0083:err:service:process_send_command service protocol error - failed to write pipe!
0088:err:ntoskrnl:ZwLoadDriver failed to create driver L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\NPF": c0000001
0083:err:service:process_send_command service protocol error - failed to write pipe!
wine: Unhandled page fault on read access to 0x00000048 at address 0x7bc3d6b1 (thread 0083), starting debugger...
0090:err:ntoskrnl:ZwLoadDriver failed to create driver L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\NPF": c0000001
agorwadia
Level 2
Level 2
Posts: 15
Joined: Sat Dec 22, 2018 5:57 am

Re: Hikvision iVMS client not running in wine-staging

Post by agorwadia »

Dear Bob,

While I was waiting, I thought to try and see if the problem is more fundamental. So I removed all wine prefixes (yes, again) and tried making the 32bit as you suggested. Below is the output of just that.

Does that look ok to you because seems to be quite a few error lines there...

Code: Select all

ankit@AG-mx:~
$ rm -rf /home/ankit/.wine*
ankit@AG-mx:~
$ export WINEPREFIX=/home/ankit/.wine32 
ankit@AG-mx:~
$ WINEARCH=win32 wineboot -u
wine: created the configuration directory '/home/ankit/.wine32'
0012:err:ole:marshal_object couldn't get IPSFactory buffer for interface {00000131-0000-0000-c000-000000000046}
0012:err:ole:marshal_object couldn't get IPSFactory buffer for interface {6d5140c1-7436-11ce-8034-00aa006009fa}
0012:err:ole:StdMarshalImpl_MarshalInterface Failed to create ifstub, hres=0x80004002
0012:err:ole:CoMarshalInterface Failed to marshal the interface {6d5140c1-7436-11ce-8034-00aa006009fa}, 80004002
0012:err:ole:get_local_server_stream Failed: 80004002
0014:err:ole:marshal_object couldn't get IPSFactory buffer for interface {00000131-0000-0000-c000-000000000046}
0014:err:ole:marshal_object couldn't get IPSFactory buffer for interface {6d5140c1-7436-11ce-8034-00aa006009fa}
0014:err:ole:StdMarshalImpl_MarshalInterface Failed to create ifstub, hres=0x80004002
0014:err:ole:CoMarshalInterface Failed to marshal the interface {6d5140c1-7436-11ce-8034-00aa006009fa}, 80004002
0014:err:ole:get_local_server_stream Failed: 80004002
0019:err:mscoree:LoadLibraryShim error reading registry key for installroot
0019:err:mscoree:LoadLibraryShim error reading registry key for installroot
0019:err:mscoree:LoadLibraryShim error reading registry key for installroot
0019:err:mscoree:LoadLibraryShim error reading registry key for installroot
wine: configuration in '/home/ankit/.wine32' has been updated.
0035:err:winediag:load_gssapi_krb5 Failed to load libgssapi_krb5, Kerberos SSP support will not be available.
wine: configuration in '/home/ankit/.wine32' has been updated.
User avatar
Bob Wya
Level 12
Level 12
Posts: 3068
Joined: Sat Oct 16, 2010 7:40 pm

Re: Hikvision iVMS client not running in wine-staging

Post by Bob Wya »

agorwadia wrote: Tue Jan 28, 2020 12:26 am Hi Bob,

Then I applied the winetricks code.

Code: Select all

winetricks -q jet40 mdac28 riched30 windowscodecs wininet vcrun6 wsh56
But there were some errors but the install did complete after sometime.

After that I installed iVMS but ran into same set of errors as before.

Code: Select all

$ wine --version
wine-4.0 (Debian 4.0-2)
@agorwadia

That version of Wine is obsolete.
Please update Wine. Install Wine version 5.0 and re-test your application.

See: WineHQ Download: Debian.

Thanks
Bob
agorwadia
Level 2
Level 2
Posts: 15
Joined: Sat Dec 22, 2018 5:57 am

Re: Hikvision iVMS client not running in wine-staging

Post by agorwadia »

Dear Bob,

Updated to wine 5. Did all the prefix formalities.

Tried installing the app and then got issue at NPF driver...

See below.

The bad thing is that this error keeps on going on and I cannot even Ctrl+C this procedure in terminal. Kinda like a stuck loop of errors. Even the installation dialog box of ivms is stuck and non-responsive.

How to overcome this NPF driver issue?

Code: Select all

0376:err:ntoskrnl:ZwLoadDriver failed to create driver L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\NPF": c0000001
0405:fixme:ndis:NdisRegisterProtocol (000000000099F798, 00000000003375E8, 000000000099F620, 208): stub
0405:err:ntoskrnl:ZwLoadDriver failed to create driver L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\NPF": c0000001
0084:fixme:ver:GetCurrentPackageId (0xc4ff2c (nil)): stub
024e:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION
017c:fixme:ver:GetCurrentPackageId (0xc4ff2c (nil)): stub
038f:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION
02f5:fixme:ndis:NdisRegisterProtocol (000000000099F798, 00000000003375E8, 000000000099F620, 208): stub
02f5:err:ntoskrnl:ZwLoadDriver failed to create driver L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\NPF": c0000001
02fe:fixme:ndis:NdisRegisterProtocol (000000000099F798, 00000000003375E8, 000000000099F620, 208): stub
02fe:err:ntoskrnl:ZwLoadDriver failed to create driver L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\NPF": c0000001
0044:fixme:ndis:NdisRegisterProtocol (000000000099F798, 00000000003375E8, 000000000099F620, 208): stub
0044:err:ntoskrnl:ZwLoadDriver failed to create driver L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\NPF": c0000001
03d1:fixme:ndis:NdisRegisterProtocol (000000000099F798, 00000000003375E8, 000000000099F620, 208): stub
03d1:err:ntoskrnl:ZwLoadDriver failed to create driver L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\NPF": c0000001
03ca:fixme:ver:GetCurrentPackageId (0xc4ff2c (nil)): stub
....
agorwadia
Level 2
Level 2
Posts: 15
Joined: Sat Dec 22, 2018 5:57 am

Re: Hikvision iVMS client not running in wine-staging

Post by agorwadia »

Guys, any update?

Please help!
Locked