Get the error codes via OpenSDK_GetLastErrorCode and get the error code information via OpenSDK_GetLastErrorDesc. The API only returns 0 and -1 by default (except some special API). The error code of SDK is listed according to modules. Major and frequently-occurred error codes are shown below.
error code is defined in the header file of OpenNetStreamError.h.
return via information callback function, refer to header file of INS_ErrorCode.h for details.
error code format{xbbbbb}, x represents the module type of error code, bbbbb represent what the error is, the value of x is shown below:
type | definition | remark |
---|---|---|
0 | correct condition | correct |
1 | network exception | This error is the same with network or configuration information error, so CURL ErrorCode is still available, for example, DNS is not configured. |
2 | user operation error | User level error code. It is usually caused by improper usage of SDK by the users. |
3 | platform server error | The error returned by OpenApi. For details, refer to error code of server port |
4 | system resource exception | Usually caused by inadequate system resource, e.g., inadequate memory. |
5 | get stream exception | error code of streaming module |
6 | method not supported | SDK unsupported |
7 | push error | push relevant error information |
9 | undefined error | error code without specific definition |
The following table shows the definition of the detailed error code value.
Description | Value | Definition | Remark |
---|---|---|---|
Network Level | |||
OPEN_SDK_COULDNT_RESOLVE_HOST | 100006 | unable to resolve to specified remote host | Here it refers that the domain name of the platform fails to be resolved. The reason maybe that the DNS is not configured or the device is disconnected. |
OPEN_SDK_COULDNT_CONNECT | 100007 | the remote host is unavailable | Here it refers to failing to access the platform. It may be caused by incorrect platform address. |
OPEN_SDK_OPERATION_TIMEOUT | 100028 | request timed out |
The expiry time is 20s. Request timed out. Check the address configuration of the platform. |
User Operation Level | |||
OPEN_SDK_BAD_PARAMS | 200001 | Invalid incoming parameter of API | |
OPEN_SDK_SESSION_INVALID | 200002 | The current session doesn’t exist or has been released. | incoming value of SessionId error or the Session has been deleted. |
OPEN_SDK_VIDEO_RECORD_NOT_EXIST | 200003 | No video file exists in the specified period. | |
OPEN_SDK_VIDEO_RECORD_SEARCHING | 200004 | Searching video records… | |
OPEN_SDK_STOP_ALARM_REC_FAILED | 200005 | Failed to disable alarm. | |
OPEN_SDK_PERMANENT_KEY_INVALID | 200006 | Incorrect verificaiton code. | |
OPEN_SDK_PIC_DECRYPT_FAILED | 200007 | Failed to decode the picture. | |
OPEN_SDK_PIC_CONTENT_INVALID | 200008 | Invalid picture content. | |
OPEN_SDK_PIC_NO_NEED_DECRYPT | 200009 | The picture doesn’t need to be decoded. | |
OPEN_SDK_PIC_COULDNT_ALLOC_BUFFERS | 200010 | Failed to allocate memory of picture resources. |
Insufficient memory or the picture size is too large. |
EZVIZ API Level | |||
OPEN_SDK_RESPINFO_BAD | 300001 | The information requested to return. json cannot resolve it. | It may be caused by the configuration problem ofPlatformAddr. |
OPEN_SDK_RESPINFO_INVALID | 300002 | Incorrect return information format of the request. | |
OPEN_SDK_ACCESSTOKEN_INVALID | 310002 | accesstoken exception or accesstoken has been expired. | |
OPEN_SDK_SIGNATURE_ERROR | 310008 | Incoming parameter error. System displaying signature error. | |
OPEN_SDK_USERID_PHONE_UNBIND | 310014 | The third-party userId and phone under APPKEY are unbound. | |
OPEN_SDK_CHANNEL_NOT_EXIST | 320001 | The channel doesn’t exist. | The channel corresponds with a specific camera. |
OPEN_SDK_USER_NOTOWN_DEVICE | 320018 | The user doesn’t have the device. | |
System Resource Level | |||
OPEN_SDK_COULDNT_CREATE_THREAD | 400001 | Failed to create a thread. | |
OPEN_SDK_COULDNT_ALLOC_BUFFERS | 400002 | Failed to apply memory resources. | |
Streaming Function Level | |||
OPEN_SDK_NS_OPERATIONCODE_FAILED | 500045 | Failed to get operation code. | It will report this error if users enabled terminal binding. |
OPEN_SDK_NS_STREAM_LIMIT | 500410 | Limit of streaming channel number | The device connection number reaches upper limit. |
OPEN_SDK_NS_DEV_NO_ONLINE | 503121 | Device offline | |
OPEN_SDK_NS_PERMANENTKEY_EXCEPTION | 502012 | Input key again. 1. Clear-text key and MD5 key mismatched. | Verification code error. |
OPEN_SDK_NS_VTDU_TIMEOUT | 502021 | Stream media sending or receiving signal timed out. | Check the device network status. It is usually caused by network problems. |
OPEN_SDK_NS_VTDU_CLIENT_TIMEOUT | 502025 | vtduThe client receiving response timed out. |
The camera and DVR/NVR may have connection problems. |
Unsupported Level | |||
OPEN_SDK_DEV_NOT_SUPPORT | 600001 | Only support device of version 1.7. | |
OPEN_SDK_API_NO_IMPLEMENT | 600002 | The API is not realized. | |
Push message level error. | |||
OPEN_SDK_PUSH_PARAM_ERROR | 710001 | Invalid incoming parameters. | |
OPEN_SDK_PUSH_DATA_UNINIT_ERROR | 710002 | The data is uninitialized. | Initialize by calling the API Init first. |
OPEN_SDK_PUSH_NO_REGISTER_ERROR | 710003 | Unregistered on the push system. | Call register API first. |
OPEN_SDK_PUSH_NO_MQTT_CREATE_ERROR | 710004 | Push object hasn’t been created. |
You haven’t call create API. |
OPEN_SDK_PUSH_MQTT_DISCONNECTED_ERROR | 720003 | sdk disconnected with push server. | Network disconnected or unstable network. |
OPEN_SDK_PUSH_MQTT_MAX_MESSAGES_ERROR | 720004 | The number of the received push messages reaches upper limit. | |
OPEN_SDK_PUSH_MQTT_BAD_UTF8_STRING_ERROR | 720005 | Invalid UTF-8 string. | |
OPEN_SDK_PUSH_MQTT_NULL_PARAMETER_ERROR | 720006 | The incoming parameter is empty pointer. | |
OPEN_SDK_PUSH_MQTT_VERSION_INVALID_ERROR | 730001 | Connection fails. Unsupported by the protocol version. | |
OPEN_SDK_PUSH_MQTT_IDENTIFIER_ERROR | 730002 | Connection fails, the only ID is incorrect. | |
OPEN_SDK_PUSH_MQTT_SERVER_UNAVAILABLE_ERROR | 730003 | Connection fails. The service doesn’t exist. | |
OPEN_SDK_PUSH_MQTT_BAD_USERNAME_PASSWORD_ERROR | 730004 | Connection fails. Incorrect mqtt username and password. | |
OPEN_SDK_PUSH_MQTT_NOT_AUTHORIZED_ERROR | 730005 | Connection fails. Unauthorized. | |
OPEN_SDK_PUSH_PLATFORM_RESPINFO_BAD | 740001 | The information returned by the request cannot be resolved normally by json. | It may be caused by invalid configuration of PlatformAddr. |
OPEN_SDK_PUSH_PLATFORM_RESPINFO_INVALID | 740002 | The format of the informaiton returned by the request is incorrect. | |
OPEN_SDK_PUSH_PLATFORM_SESSION_INVALID_ERROR | 740003 | Invalid session. | The session might has been released. |
OPEN_SDK_PUSH_PLATFORM_UNAUTHORIZED_ERROR | 740401 | Invalid certificate. |
It may be caused by invalid configuration of PlatformAddr. |
OPEN_SDK_PUSH_COULDNT_CREATE_THREAD | 750001 | Failed to create the thread. | |
OPEN_SDK_PUSH_COULDNT_ALLOC_BUFFERS | 750002 | Failed to apply memory resources. | |
OPEN_SDK_PUSH_COULDNT_RESOLVE_HOST | 760006 | The specified remote host is not been resolved. | Here it refers that the platform domain fails to be resolved normally. It may be caused by unconfigured DNS or disconnected device. |
OPEN_SDK_PUSH_COULDNT_CONNECT | 760007 | The remote host is unavailable | Here it refers that the platform is inaccessible. It may be caused by the configuration error of the platform address. |
OPEN_SDK_PUSH_OPERATION_TIMEOUT | 760028 | Request timed out. The expiry time is 20s. |
Sending request to platform timed out. Failed to access the EZVIZ OPEN platform. Check the configured address or the network. |
Undefined Level | |||
OPEN_SDK_ALLOCSESSION_FAILED | 900001 | AllocSession failed. | |
OPEN_SDK_SEARCH_RECORD_FAILED | 900002 | Failed to search playback records. | |
OPEN_SDK_START_ALARM_REC_FAILED | 900003 | Failed to enable alarm. |
Содержание
- IVMS-4200 Error: Adding Failed(OpenSDK[305000])
- alexf40
- alexf40
- alexf40
- The complete error codes list for iVMS-4200
- Common errors on iVMS-4200
- Open sdk string error ivms 4200
IVMS-4200 Error: Adding Failed(OpenSDK[305000])
alexf40
Member
I’m currently running IVMS-4200 v3.2.0.10 on Windows 10. I’m trying to add a camera as Cloud P2P by entering the serial number and verification code, on adding I get the error «Adding Failed(OpenSDK[305000])».
5/7 cameras have successfully been added, not sure why the other two are giving this error as the settings/configuration appear identical for all of them.
Administrator
alexf40
Member
Hi Dan, thanks for the suggestion. I tried adding the cameras directly in the portal, after entering the serial number it tells me the camera has been added. But the camera is not visible in the hik connect portal.
But I now have six cameras on the Hik Connect app on iOS, and five on the portal.
I also tried adding the camera through the iOS Hik Connect app and it tells me that the camera has been added but doesn’t appear.
I’ve tried refreshing multiple times and logging out and back in.
Administrator
For the camera that says it has been added, I think you are going to have to try unbinding the device using SADP and then try adding it to the Hik-connect portal.
We always recommend people add cameras/NVRs directly to the online portal and not via the app as it is often the case that devices added via the app are only linked to the app via the local LAN connection and so when you then try and access remotely you can’t see the cameras. When you add the device to the portal you link the remote access app to Hikvision cloud server and the cloud server to the camera, doing this creates a simple but secure link for footage to leave the cameras on your local network and pass over the internet to reach the remote Hik-Connect application whatever network it is on. (e.g. Public WiFi, 3G, 4G, etc. )
alexf40
Member
Thanks Dan, I’d like to give that a try. But since I upgraded SADP I can’t get any of my cameras to show. They are all accessible through IVMS-4200 and direct via IP on the same computer.
I’ve ran sc query «npf» in the command line and it shows that it’s running, I’ve also tried uninstalling and reinstalling to no joy.
I»ve also tried installing Npcap: Windows Packet Capture Library & Driver and win10 cap but
I»m pretty sure it’s an issue with having the right NPF but haven’t been able to get it to work.
Administrator
Do you have a firewall/security software installed on your PC/Mac? default Windows/Mac firewall or 3rd-party like ESET, Norton, etc.
We have seen issues previously, not just with Hikvision’s software, where the software has to be added to the firewalls safe software list and be given permission to pass & receive data through the firewall, So I would recommend trying to add the SADP tool to that safe software list.
Источник
The complete error codes list for iVMS-4200
This is the complete list of error codes in the Hikvision iVMS-4200 camera management software. Locate the exact error code and find the meaning and the possible fix. If you’re using the phone app, check this article: Common error codes in iVMS-4500 and how to fix them.
Common errors on iVMS-4200
Error code 317″ No videos. It will be prompted when the user has no permission to playback.
HCNetSDK.dll error code
Error code 1: Invalid user name or password
Error code 2: No permission. The user in the device has not enough permission.
Error code 4: Invalid channel number.
It will be prompted in the live view of the remote screen control.
Error code5: No more devices can be connected.
Failed to connect the device. Not supported. Operation failed.
Error code 7: Failed to connect the device.
Error code 23: Not Supported.
The camera signal is not supported. Check the video settings on the unit (camera, DVR, NVR).
Error code 43: No buffer.
It will be prompted when adding a device and the device port is occupied by a web server.
Error code 91: The channel does not support the operation.
It will be prompted when failed to get the sub stream.
Error code 96: The device is not registered on the DDNS.
Error code 153: The user is locked.
Error code 250: The device is not activated.
Error code 404: Channel No. error or the device does not support the sub stream.
It will be prompted when failed to get the sub stream or the sub stream does not exist.
Error code 424: Failed to receive the data for RTSP SETUP.
It will be prompted when adding the live view for the software via the external network.
Error code 800: No more bandwidth can be used.
Playctrl.dll ERROR CODE
Error code 2: The stream is not a Video & Audio stream.
Error code 6: The playback window turns black when adopting H.265 in the 64-bit operating system.
SMS ERROR CODE
Error code 3: The connection problem between the software and the stream media server.
Error code 17: The streaming problem between the stream media server and the device.
Источник
Open sdk string error ivms 4200
Get the error codes via OpenSDK_GetLastErrorCode and get the error code information via OpenSDK_GetLastErrorDesc. The API only returns 0 and -1 by default (except some special API). The error code of SDK is listed according to modules. Major and frequently-occurred error codes are shown below.
error code is defined in the header file of OpenNetStreamError.h.
return via information callback function, refer to header file of INS_ErrorCode.h for details.
error code format, x represents the module type of error code, bbbbb represent what the error is, the value of x is shown below:
type | definition | remark |
---|---|---|
correct condition | correct | |
1 | network exception | This error is the same with network or configuration information error, so CURL ErrorCode is still available, for example, DNS is not configured. |
2 | user operation error | User level error code. It is usually caused by improper usage of SDK by the users. |
3 | platform server error | The error returned by OpenApi. For details, refer to error code of server port |
4 | system resource exception | Usually caused by inadequate system resource, e.g., inadequate memory. |
5 | get stream exception | error code of streaming module |
6 | method not supported | SDK unsupported |
7 | push error | push relevant error information |
9 | undefined error | error code without specific definition |
The following table shows the definition of the detailed error code value.
The expiry time is 20s. Request timed out. Check the address configuration of the platform.
Insufficient memory or the picture size is too large.
The camera and DVR/NVR may have connection problems.
You haven’t call create API.
It may be caused by invalid configuration of PlatformAddr.
Sending request to platform timed out. Failed to access the EZVIZ OPEN platform. Check the configured address or the network.
Источник
Adblock
detector
Description | Value | Definition | Remark |
---|---|---|---|
Network Level | |||
OPEN_SDK_COULDNT_RESOLVE_HOST | 100006 | unable to resolve to specified remote host | Here it refers that the domain name of the platform fails to be resolved. The reason maybe that the DNS is not configured or the device is disconnected. |
OPEN_SDK_COULDNT_CONNECT | 100007 | the remote host is unavailable | Here it refers to failing to access the platform. It may be caused by incorrect platform address. |
OPEN_SDK_OPERATION_TIMEOUT | 100028 | request timed out | |
User Operation Level | |||
OPEN_SDK_BAD_PARAMS | 200001 | Invalid incoming parameter of API | |
OPEN_SDK_SESSION_INVALID | 200002 | The current session doesn’t exist or has been released. | incoming value of SessionId error or the Session has been deleted. |
OPEN_SDK_VIDEO_RECORD_NOT_EXIST | 200003 | No video file exists in the specified period. | |
OPEN_SDK_VIDEO_RECORD_SEARCHING | 200004 | Searching video records. | |
OPEN_SDK_STOP_ALARM_REC_FAILED | 200005 | Failed to disable alarm. | |
OPEN_SDK_PERMANENT_KEY_INVALID | 200006 | Incorrect verificaiton code. | |
OPEN_SDK_PIC_DECRYPT_FAILED | 200007 | Failed to decode the picture. | |
OPEN_SDK_PIC_CONTENT_INVALID | 200008 | Invalid picture content. | |
OPEN_SDK_PIC_NO_NEED_DECRYPT | 200009 | The picture doesn’t need to be decoded. | |
OPEN_SDK_PIC_COULDNT_ALLOC_BUFFERS | 200010 | Failed to allocate memory of picture resources. | |
EZVIZ API Level | |||
OPEN_SDK_RESPINFO_BAD | 300001 | The information requested to return. json cannot resolve it. | It may be caused by the configuration problem ofPlatformAddr. |
OPEN_SDK_RESPINFO_INVALID | 300002 | Incorrect return information format of the request. | |
OPEN_SDK_ACCESSTOKEN_INVALID | 310002 | accesstoken exception or accesstoken has been expired. | |
OPEN_SDK_SIGNATURE_ERROR | 310008 | Incoming parameter error. System displaying signature error. | |
OPEN_SDK_USERID_PHONE_UNBIND | 310014 | The third-party userId and phone under APPKEY are unbound. | |
OPEN_SDK_CHANNEL_NOT_EXIST | 320001 | The channel doesn’t exist. | The channel corresponds with a specific camera. |
OPEN_SDK_USER_NOTOWN_DEVICE | 320018 | The user doesn’t have the device. | |
System Resource Level | |||
OPEN_SDK_COULDNT_CREATE_THREAD | 400001 | Failed to create a thread. | |
OPEN_SDK_COULDNT_ALLOC_BUFFERS | 400002 | Failed to apply memory resources. | |
Streaming Function Level | |||
OPEN_SDK_NS_OPERATIONCODE_FAILED | 500045 | Failed to get operation code. | It will report this error if users enabled terminal binding. |
OPEN_SDK_NS_STREAM_LIMIT | 500410 | Limit of streaming channel number | The device connection number reaches upper limit. |
OPEN_SDK_NS_DEV_NO_ONLINE | 503121 | Device offline | |
OPEN_SDK_NS_PERMANENTKEY_EXCEPTION | 502012 | Input key again. 1. Clear-text key and MD5 key mismatched. | Verification code error. |
OPEN_SDK_NS_VTDU_TIMEOUT | 502021 | Stream media sending or receiving signal timed out. | Check the device network status. It is usually caused by network problems. |
OPEN_SDK_NS_VTDU_CLIENT_TIMEOUT | 502025 | vtduThe client receiving response timed out. | |
Unsupported Level | |||
OPEN_SDK_DEV_NOT_SUPPORT | 600001 | Only support device of version 1.7. | |
OPEN_SDK_API_NO_IMPLEMENT | 600002 | The API is not realized. | |
Push message level error. | |||
OPEN_SDK_PUSH_PARAM_ERROR | 710001 | Invalid incoming parameters. | |
OPEN_SDK_PUSH_DATA_UNINIT_ERROR | 710002 | The data is uninitialized. | Initialize by calling the API Init first. |
OPEN_SDK_PUSH_NO_REGISTER_ERROR | 710003 | Unregistered on the push system. | Call register API first. |
OPEN_SDK_PUSH_NO_MQTT_CREATE_ERROR | 710004 | Push object hasn’t been created. | |
OPEN_SDK_PUSH_MQTT_DISCONNECTED_ERROR | 720003 | sdk disconnected with push server. | Network disconnected or unstable network. |
OPEN_SDK_PUSH_MQTT_MAX_MESSAGES_ERROR | 720004 | The number of the received push messages reaches upper limit. | |
OPEN_SDK_PUSH_MQTT_BAD_UTF8_STRING_ERROR | 720005 | Invalid UTF-8 string. | |
OPEN_SDK_PUSH_MQTT_NULL_PARAMETER_ERROR | 720006 | The incoming parameter is empty pointer. | |
OPEN_SDK_PUSH_MQTT_VERSION_INVALID_ERROR | 730001 | Connection fails. Unsupported by the protocol version. | |
OPEN_SDK_PUSH_MQTT_IDENTIFIER_ERROR | 730002 | Connection fails, the only ID is incorrect. | |
OPEN_SDK_PUSH_MQTT_SERVER_UNAVAILABLE_ERROR | 730003 | Connection fails. The service doesn’t exist. | |
OPEN_SDK_PUSH_MQTT_BAD_USERNAME_PASSWORD_ERROR | 730004 | Connection fails. Incorrect mqtt username and password. | |
OPEN_SDK_PUSH_MQTT_NOT_AUTHORIZED_ERROR | 730005 | Connection fails. Unauthorized. | |
OPEN_SDK_PUSH_PLATFORM_RESPINFO_BAD | 740001 | The information returned by the request cannot be resolved normally by json. | It may be caused by invalid configuration of PlatformAddr. |
OPEN_SDK_PUSH_PLATFORM_RESPINFO_INVALID | 740002 | The format of the informaiton returned by the request is incorrect. | |
OPEN_SDK_PUSH_PLATFORM_SESSION_INVALID_ERROR | 740003 | Invalid session. | The session might has been released. |
OPEN_SDK_PUSH_PLATFORM_UNAUTHORIZED_ERROR | 740401 | Invalid certificate. | |
OPEN_SDK_PUSH_COULDNT_CREATE_THREAD | 750001 | Failed to create the thread. | |
OPEN_SDK_PUSH_COULDNT_ALLOC_BUFFERS | 750002 | Failed to apply memory resources. | |
OPEN_SDK_PUSH_COULDNT_RESOLVE_HOST | 760006 | The specified remote host is not been resolved. | Here it refers that the platform domain fails to be resolved normally. It may be caused by unconfigured DNS or disconnected device. |
OPEN_SDK_PUSH_COULDNT_CONNECT | 760007 | The remote host is unavailable | Here it refers that the platform is inaccessible. It may be caused by the configuration error of the platform address. |
OPEN_SDK_PUSH_OPERATION_TIMEOUT | 760028 | Request timed out. The expiry time is 20s. |
-
#1
Hi, i have a Hikvision DVR 7208 HQHI, everything worked find for months, now without ! any changes, IVMS 4200 (no changes done too) tell me this, when i try to watch recorded Videofiles over the IVMS client:
Hikvision DVR Playback failed Error Code open SDK String Error 105 — Playback failed
When i go over the network straight to the DVR i can watch this recorded files, on the montior that is connected to the DVR, only IVMS 4200 on the PC tell me this error.
Nothing was changed, in one moment it dosent work anymore (the playback over IVMS)
Sorry for my English, iam from Germany.
Hope you understand whats the problem.
Regards
-
#2
Hi, I am having the same issue! I just noticed that the recorded video clips listed on the right of the screen are not in chronological order (see picture below). This seems to be causing the system to throw a string error. If you narrow your time span to include only 1 clip, it will play the recorded clip.
This is only occurring on devices that are Hik-Connect, local devices (on the same LAN as the iVMS-2400 client software) work fine.
Can anyone explain where this is coming from? It was working fine until recently.
Thanks. Brendan
-
#3
Hi Brendan, thats the same Problem over here, the files are not correct chronological, only by Hik devices, via Lan everything okay. Hikvision support is shxt ! No help.. wrote to UK,.com and Europe… no help !
-
#4
Hello? Can anyone on this forum help us? Are slot99 and myself the only ones having this bizarre behaviour of our iVMS clients?
Thanks.
-
#6
same here guys, new member, new install , in the uk, and installed last week,
remote playback over the internet via hik connect same error,
local lan playback no error
convinced its a hik connect issue somehow
-
#7
This is a known problem that will be fixed with Hikvisions next IVMS upgrade. The is a OpenNetStream.dll file that needs to be updated in the C:Program FilesiVMS-4200 StationiVMS-4200iVMS-4200 directory. If you email me at FredWentworth@NewEnglandcctv.com with your email, I can send you the file.
We have had to do this for every client using Hik-Connect for remote viewing/ playback in the past 6 weeks or so. Its a simple fix.
-
#8
This is a known problem that will be fixed with Hikvisions next IVMS upgrade. The is a OpenNetStream.dll file that needs to be updated in the C:Program FilesiVMS-4200 StationiVMS-4200iVMS-4200 directory. If you email me at FredWentworth@NewEnglandcctv.com with your email, I can send you the file.
We have had to do this for every client using Hik-Connect for remote viewing/ playback in the past 6 weeks or so. Its a simple fix.
Hi @FredWentworth, can you send me the file? I have the same problem!
Last edited: Feb 19, 2018
-
#9
This is a known problem that will be fixed with Hikvisions next IVMS upgrade. The is a OpenNetStream.dll file that needs to be updated in the C:Program FilesiVMS-4200 StationiVMS-4200iVMS-4200 directory. If you email me at FredWentworth@NewEnglandcctv.com with your email, I can send you the file.
We have had to do this for every client using Hik-Connect for remote viewing/ playback in the past 6 weeks or so. Its a simple fix.
Cant you just upload the file, so anyone can download?
-
Forums
-
Manufacturer Specific Forums
-
Hikvision
You should upgrade or use an alternative browser.
Device error, OpenSDK stringerror 510004
-
Thread starterrkg
-
Start dateJan 23, 2022
-
#1
-
#2
What model is your NVR and which firmware version is it running?
Which version of iVMS-4200 are you running?
Is this on a Windows or macOS device?
- Thread starter
-
#3
IiVMS-4200 version V3.6.0.6 build20210630 (iVMS says that is latest version)
OS: Windows 10
-
#4
- Thread starter
-
#5
-
#6
- Thread starter
-
#7
-
#8
Sorry, I’m not sure what else the issue could be I can’t find any other mention of that error code, so it may be specific to HiWatch devices.
If you can, I’d ask your supplier to ask Hikvision Support about the error code. Or, take it to them directly, as they’ll probably know what it means — support.uk@hikvision.com
- Thread starter
-
#9
-
#10
-
#11
Similar threads
-
Forums
-
Manufacturer Specific Forums
-
Hikvision
I just upgraded to Visual Studio 2017 Community Edition and I have trouble loading standard header files. I get 507 errors from various header files. Here are some snippets:
Some of the errors:
Severity Code Description Project File Line Suppression State
Error (active) E1696 cannot open source file "errno.h" RPGWorld c:Program Files (x86)Microsoft Visual Studio2017CommunityVCToolsMSVC14.10.25017includecerrno 7
Error (active) E1696 cannot open source file "float.h" RPGWorld c:Program Files (x86)Microsoft Visual Studio2017CommunityVCToolsMSVC14.10.25017includecfloat 7
Error (active) E0282 the global scope has no "acosf" RPGWorld c:Program Files (x86)Microsoft Visual Studio2017CommunityVCToolsMSVC14.10.25017includecmath 629
Error (active) E0282 the global scope has no "asinf" RPGWorld c:Program Files (x86)Microsoft Visual Studio2017CommunityVCToolsMSVC14.10.25017includecmath 629
Error (active) E0282 the global scope has no "atanf" RPGWorld c:Program Files (x86)Microsoft Visual Studio2017CommunityVCToolsMSVC14.10.25017includecmath 630
Error (active) E0282 the global scope has no "atan2f" RPGWorld c:Program Files (x86)Microsoft Visual Studio2017CommunityVCToolsMSVC14.10.25017includecmath 630
Error (active) E0282 the global scope has no "ceilf" RPGWorld c:Program Files (x86)Microsoft Visual Studio2017CommunityVCToolsMSVC14.10.25017includecmath 630
Error (active) E0282 the global scope has no "cosf" RPGWorld c:Program Files (x86)Microsoft Visual Studio2017CommunityVCToolsMSVC14.10.25017includecmath 631
Error (active) E0282 the global scope has no "coshf" RPGWorld c:Program Files (x86)Microsoft Visual Studio2017CommunityVCToolsMSVC14.10.25017includecmath 631
Error (active) E0282 the global scope has no "swprintf" RPGWorld c:Program Files (x86)Microsoft Visual Studio2017CommunityVCToolsMSVC14.10.25017includecwchar 21
Error (active) E0282 the global scope has no "swscanf" RPGWorld c:Program Files (x86)Microsoft Visual Studio2017CommunityVCToolsMSVC14.10.25017includecwchar 21
Error (active) E0282 the global scope has no "ungetwc" RPGWorld c:Program Files (x86)Microsoft Visual Studio2017CommunityVCToolsMSVC14.10.25017includecwchar 21
Error (active) E0282 the global scope has no "vfwprintf" RPGWorld c:Program Files (x86)Microsoft Visual Studio2017CommunityVCToolsMSVC14.10.25017includecwchar 22
Error (active) E0282 the global scope has no "vswprintf" RPGWorld c:Program Files (x86)Microsoft Visual Studio2017CommunityVCToolsMSVC14.10.25017includecwchar 22
Error (active) E0282 the global scope has no "vwprintf" RPGWorld c:Program Files (x86)Microsoft Visual Studio2017CommunityVCToolsMSVC14.10.25017includecwchar 22
Error (active) E0282 the global scope has no "wcrtomb" RPGWorld c:Program Files (x86)Microsoft Visual Studio2017CommunityVCToolsMSVC14.10.25017includecwchar 23
Error (active) E0282 the global scope has no "wprintf" RPGWorld c:Program Files (x86)Microsoft Visual Studio2017CommunityVCToolsMSVC14.10.25017includecwchar 23
Error (active) E0282 the global scope has no "wscanf" RPGWorld c:Program Files (x86)Microsoft Visual Studio2017CommunityVCToolsMSVC14.10.25017includecwchar 23
Error (active) E0282 the global scope has no "wcsrtombs" RPGWorld c:Program Files (x86)Microsoft Visual Studio2017CommunityVCToolsMSVC14.10.25017includecwchar 24
Error (active) E0282 the global scope has no "wcstol" RPGWorld c:Program Files (x86)Microsoft Visual Studio2017CommunityVCToolsMSVC14.10.25017includecwchar 24
Error (active) E0282 the global scope has no "wcscat" RPGWorld c:Program Files (x86)Microsoft Visual Studio2017CommunityVCToolsMSVC14.10.25017includecwchar 24
Error (active) E0282 the global scope has no "wcschr" RPGWorld c:Program Files (x86)Microsoft Visual Studio2017CommunityVCToolsMSVC14.10.25017includecwchar 25
Error (active) E0282 the global scope has no "wcscmp" RPGWorld c:Program Files (x86)Microsoft Visual Studio2017CommunityVCToolsMSVC14.10.25017includecwchar 25
Error (active) E0282 the global scope has no "wcscoll" RPGWorld c:Program Files (x86)Microsoft Visual Studio2017CommunityVCToolsMSVC14.10.25017includecwchar 25
Error (active) E0282 the global scope has no "wcscpy" RPGWorld c:Program Files (x86)Microsoft Visual Studio2017CommunityVCToolsMSVC14.10.25017includecwchar 26
Error (active) E0282 the global scope has no "wcscspn" RPGWorld c:Program Files (x86)Microsoft Visual Studio2017CommunityVCToolsMSVC14.10.25017includecwchar 26
Error (active) E0282 the global scope has no "wcslen" RPGWorld c:Program Files (x86)Microsoft Visual Studio2017CommunityVCToolsMSVC14.10.25017includecwchar 26
Error (active) E0282 the global scope has no "wcsncat" RPGWorld c:Program Files (x86)Microsoft Visual Studio2017CommunityVCToolsMSVC14.10.25017includecwchar 27
Error (active) E0282 the global scope has no "wcsncmp" RPGWorld c:Program Files (x86)Microsoft Visual Studio2017CommunityVCToolsMSVC14.10.25017includecwchar 27
Error (active) E0282 the global scope has no "wcsncpy" RPGWorld c:Program Files (x86)Microsoft Visual Studio2017CommunityVCToolsMSVC14.10.25017includecwchar 27
Error (active) E0282 the global scope has no "wcspbrk" RPGWorld c:Program Files (x86)Microsoft Visual Studio2017CommunityVCToolsMSVC14.10.25017includecwchar 28
Error (active) E0282 the global scope has no "wcsrchr" RPGWorld c:Program Files (x86)Microsoft Visual Studio2017CommunityVCTools
Error (active) E0260 explicit type is missing ('int' assumed) RPGWorld c:Program Files (x86)Microsoft Visual Studio2017CommunityVCToolsMSVC14.10.25017includextgmath.h 212
Error (active) E0757 variable "size_t" is not a type name RPGWorld c:UsersFazilDocumentsVisual Studio 2017ProjectsLocalRPGWorldpackagessfml-system.2.4.0.0buildnativeincludeSFMLGraphicsGlsl.inl 40
Error (active) E0757 variable "size_t" is not a type name RPGWorld c:UsersFazilDocumentsVisual Studio 2017ProjectsLocalRPGWorldpackagessfml-system.2.4.0.0buildnativeincludeSFMLGraphicsTexture.hpp 159
Error (active) E0757 variable "size_t" is not a type name RPGWorld c:UsersFazilDocumentsVisual Studio 2017ProjectsLocalRPGWorldpackagessfml-system.2.4.0.0buildnativeincludeSFMLGraphicsVertexArray.hpp 64
Error (active) E0757 variable "size_t" is not a type name RPGWorld c:UsersFazilDocumentsVisual Studio 2017ProjectsLocalRPGWorldpackagessfml-system.2.4.0.0buildnativeincludeSFMLGraphicsVertexArray.hpp 72
Error (active) E0757 variable "size_t" is not a type name RPGWorld c:UsersFazilDocumentsVisual Studio 2017ProjectsLocalRPGWorldpackagessfml-system.2.4.0.0buildnativeincludeSFMLGraphicsVertexArray.hpp 88
Error (active) E0757 variable "size_t" is not a type name RPGWorld c:UsersFazilDocumentsVisual Studio 2017ProjectsLocalRPGWorldpackagessfml-system.2.4.0.0buildnativeincludeSFMLGraphicsVertexArray.hpp 104
Error (active) E0757 variable "size_t" is not a type name RPGWorld c:UsersFazilDocumentsVisual Studio 2017ProjectsLocalRPGWorldpackagessfml-system.2.4.0.0buildnativeincludeSFMLGraphicsVertexArray.hpp 129
Error (active) E0757 variable "size_t" is not a type name RPGWorld c:UsersFazilDocumentsVisual Studio 2017ProjectsLocalRPGWorldpackagessfml-system.2.4.0.0buildnativeincludeSFMLSystemString.hpp 58
Error (active) E0757 variable "size_t" is not a type name RPGWorld c:UsersFazilDocumentsVisual Studio 2017ProjectsLocalRPGWorldpackagessfml-system.2.4.0.0buildnativeincludeSFMLSystemString.hpp 332
Error (active) E0757 variable "size_t" is not a type name RPGWorld c:UsersFazilDocumentsVisual Studio 2017ProjectsLocalRPGWorldpackagessfml-system.2.4.0.0buildnativeincludeSFMLSystemString.hpp 345
Error (active) E0757 variable "size_t" is not a type name RPGWorld c:UsersFazilDocumentsVisual Studio 2017ProjectsLocalRPGWorldpackagessfml-system.2.4.0.0buildnativeincludeSFMLSystemString.hpp 365
Error (active) E0757 variable "size_t" is not a type name RPGWorld c:UsersFazilDocumentsVisual Studio 2017ProjectsLocalRPGWorldpackagessfml-system.2.4.0.0buildnativeincludeSFMLSystemString.hpp 387
Error (active) E0757 variable "size_t" is not a type name RPGWorld c:UsersFazilDocumentsVisual Studio 2017ProjectsLocalRPGWorldpackagessfml-system.2.4.0.0buildnativeincludeSFMLSystemString.hpp 387
Error (active) E0757 variable "size_t" is not a type name RPGWorld c:UsersFazilDocumentsVisual Studio 2017ProjectsLocalRPGWorldpackagessfml-system.2.4.0.0buildnativeincludeSFMLSystemString.hpp 399
Error (active) E0757 variable "size_t" is not a type name RPGWorld c:UsersFazilDocumentsVisual Studio 2017ProjectsLocalRPGWorldpackagessfml-system.2.4.0.0buildnativeincludeSFMLSystemString.hpp 413
Error (active) E0757 variable "size_t" is not a type name RPGWorld c:UsersFazilDocumentsVisual Studio 2017ProjectsLocalRPGWorldpackagessfml-system.2.4.0.0buildnativeincludeSFMLSystemString.hpp 413
Error (active) E0757 variable "size_t" is not a type name RPGWorld c:UsersFazilDocumentsVisual Studio 2017ProjectsLocalRPGWorldpackagessfml-system.2.4.0.0buildnativeincludeSFMLSystemString.hpp 427
Error (active) E0757 variable "size_t" is not a type name RPGWorld c:UsersFazilDocumentsVisual Studio 2017ProjectsLocalRPGWorldpackagessfml-system.2.4.0.0buildnativeincludeSFMLSystemString.hpp 427
Error (active) E0757 variable "size_t" is not a type name RPGWorld c:UsersFazilDocumentsVisual Studio 2017ProjectsLocalRPGWorldpackagessfml-system.2.4.0.0buildnativeincludeSFMLSystemString.hpp 456
Error (active) E0757 variable "size_t" is not a type name RPGWorld c:UsersFazilDocumentsVisual Studio 2017ProjectsLocalRPGWorldpackagessfml-system.2.4.0.0buildnativeincludeSFMLSystemString.hpp 456
Error (active) E0020 identifier "rand" is undefined RPGWorld c:UsersFazilDocumentsVisual Studio 2017ProjectsLocalRPGWorldRPGWorldBlocks.cpp 23
Error C1083 Cannot open include file: 'corecrt.h': No such file or directory RPGWorld c:program files (x86)microsoft visual studio2017communityvctoolsmsvc14.10.25017includecrtdefs.h 10
Error C1083 Cannot open include file: 'corecrt.h': No such file or directory RPGWorld c:program files (x86)microsoft visual studio2017communityvctoolsmsvc14.10.25017includecrtdefs.h 10
Error C1083 Cannot open include file: 'corecrt.h': No such file or directory RPGWorld c:program files (x86)microsoft visual studio2017communityvctoolsmsvc14.10.25017includecrtdefs.h 10
Error C1083 Cannot open include file: 'corecrt.h': No such file or directory RPGWorld c:program files (x86)microsoft visual studio2017communityvctoolsmsvc14.10.25017includecrtdefs.h 10
Error C1083 Cannot open include file: 'corecrt.h': No such file or directory RPGWorld c:program files (x86)microsoft visual studio2017communityvctoolsmsvc14.10.25017includecrtdefs.h 10
Error C1083 Cannot open include file: 'corecrt.h': No such file or directory RPGWorld c:program files (x86)microsoft visual studio2017communityvctoolsmsvc14.10.25017includecrtdefs.h 10
Error C1083 Cannot open include file: 'corecrt.h': No such file or directory RPGWorld c:program files (x86)microsoft visual studio2017communityvctoolsmsvc14.10.25017includecrtdefs.h 10
Error C1083 Cannot open include file: 'corecrt.h': No such file or directory RPGWorld c:program files (x86)microsoft visual studio2017communityvctoolsmsvc14.10.25017includecrtdefs.h 10
I never had this issue with Visual Studio 2015 Community Edition. Am I missing some component from the Installer? Any help would be appreciated. Thank you!
asked Mar 14, 2017 at 3:45
I got the errors to go away by installing the Windows Universal CRT SDK
component, which adds support for legacy Windows SDKs. You can install this using the Visual Studio Installer:
If the problem still persists, you should change the Target SDK in the Visual Studio Project : check whether the Windows SDK version is 10.0.15063.0.
In : Project -> Properties -> General -> Windows SDK Version -> select 10.0.15063.0.
Then errno.h and other standard files will be found and it will compile.
answered Mar 14, 2017 at 5:03
o.oo.o
3,4798 gold badges41 silver badges69 bronze badges
5
If the problem is not solved by above answer, check whether the Windows SDK version is 10.0.15063.0.
Project -> Properties -> General -> Windows SDK Version -> select 10.0.15063.0
After this rebuild the solution.
answered Jul 27, 2017 at 13:56
2
If anyone’s still stuck on this, the easiest solution I found was to «Retarget Solution».
In my case, the project was built of SDK 8.1, upgrading to VS2017 brought with it SDK 10.0.xxx.
To retarget solution:
Project->Retarget Solution->»Select whichever SDK you have installed»->OK
From there on you can simply build/debug your solution. Hope it helps
answered Apr 16, 2019 at 17:05
Rafay KhanRafay Khan
92011 silver badges23 bronze badges
I upgraded VS2017 from version 15.2 to 15.8. With version 15.8 here’s what happened:
Project -> Properties -> General -> Windows SDK Version -> select 10.0.15063.0 no longer worked for me! I had to change it to 10.0.17134.0 and then everything built again. After the upgrade and without making this change, I was getting the same header file errors.
I would have submitted this as a comment on one of the other answers but I don’t have enough reputation yet.
answered Aug 29, 2018 at 4:02
echoecho
4507 silver badges11 bronze badges
1
This problem may also happen if you have a unit test project that has a different C++ version than the project you want to test.
Example:
- EXE with C++ 17 enabled explicitly
- Unit Test with C++ version set to «Default»
Solution: change the Unit Test to C++17 as well.
answered Oct 30, 2020 at 10:09
Thomas WellerThomas Weller
53.2k20 gold badges121 silver badges210 bronze badges
If the instalation of Windows Universal CRT SDK as described in the acceped answer did not help. Try to check this:
In case the directory «C:Program FilesWindows Kits» exists on your system ensure that it contains «10/Include» and «10/Lib» subdirectories. If not create hard links there to thoose present in your «C:Program Files (x86)Windows Kits10″
Explanation:
As you can see from C:Program Files (x86)Windows Kits10DesignTimeCommonConfigurationNeutraluCRT.props the path «C:Program FilesWindows Kits» is prefered over «C:Program Files (x86)Windows Kits» if it exists!
answered Feb 4, 2022 at 11:29
BohdanBohdan
4384 silver badges6 bronze badges
Работа с облаком и настройки удаленного доступа
Удаленный доступ на камеры и регистраторы Hikvision и HiWatch можно реализовать следующими способами.
1) Если используется белый (публичный) статический IP, то на роутере настраиваете проброс портов 80 554 и 8000 (uPnP рекомендуем отключить)
2) Если используется серый IP, то единственный способ настроить доступ — p2p сервис Hik-Connect, возможен удаленный просмотр и удаленный просмотр архива. Запись в облако не происходит.
Личный кабинет Hik-connect
Инструкция по настройке p2p сервиса Hik-connect / Guarding vision
Рекомендации по первоначальной настройке сети панелей Ax Pro
Как отвязать устройство от облачной учетной записи
Российские адреса серверов:
dev.hik-connectru.com
litedev.hik-connectru.com
Для домофонии — litedev.hik-connectru.com
IVMS 4200
Перепрошивка камер и все что с ней связано
Обновить прошивку можно через web интерфейс устройства, как обычный роутер, либо через клиентское ПО IVMS-4200.
Обновление необходимо производить последовательно. 5.1.X -> 5.2.X -> 5.3.X -> 5.4.X
C прошивок 5.3.X на 5.2.X и с 5.4.X на 5.3.X откатиться НЕ ПОЛУЧИТСЯ!!!
Инструкция по обновлению
Вы можете откатить прошивку (к примеру) с 5.3.8 на 5.3.3 с помощью TFTP, с 5.3.8 до 5.2.0 откатиться НЕЛЬЗЯ!
Перепрошивка через TFTP
Перепрошивка регистраторов все что с ней связано
Мы рекомендуем проводить обновление через клиентское ПО IVMS-4200 или утилиту BatchConfigTool
Инструкция по перепрошивке
Восстановление устройства с помощью прошивки через TFTP
IP Камеры: аудио вход и выход
IP Камеры: схема обжима
RTSP ссылки
RTSP-ссылки
Основная и универсальная ссылка для IP камер, NVR и DVR:
rtsp://admin:12345@192.168.200.11:554/ISAPI/Streaming/Channels/101
где:
rtsp — тип используемого протокола
admin — имя учетной записи
12345 – пароль используемой учетной записи
192.168.200.11 — IP-адрес камеры
554 — RTSP порт камеры (по умолчанию 554, может быть изменен в настройках)
101 — это 1 камера 1 поток
201 — это 2 камера 1 поток
102 — это 1 камера 2 поток
IP каналы HD-TVI регистраторов
7204 — 501 601;
7208 — 901 1001;
7X16 — 1701 1801 и т.д
Для вызывных панелей:
rtsp://admin:12345@192.168.200.11:554/Streaming/Channels/101
Устаревшие ссылки:
rtsp://admin:12345@IP-камеры:554/mpeg4/ch01/main/av_stream
получение потока с первого канала
rtsp://admin:12345@IP-камеры:554/mjpeg/ch1/sub/av_stream
получение потока mjpeg со второго потока. прошивка должна поддерживать mjpeg на втором
потоке.
MJPEG и фото:
Для получения MJPEG-потока по HTTP (суб-поток камеры должен быть настроен как mjpeg)
Перевести в MJPEG можно только суб-поток камеры.
IP Камеры: тревожный вход и выход
Подбор кронштейнов и монтажных коробок
Таблицу совместимости камер Hikvision с аксессуарами вы можете скачать тут
Таблицу совместимости камер HiWatch с аксессуарами вы можете скачать тут
С паспортами для аксессуаров вы можете ознакомиться по данной ссылке
Список протестированных HDD и SD карт
Как просматривать устройство в браузере
Для Windows
Для просмотра через web требуется установить плагин Web Components
- В Internet Explorer в разделе Свойства обозревателя->Дополнительно разрешите запуск сторонних плагинов.
- В Chrome и браузерах на его основе, например Yandex browser разработчиками была отключена поддержка сторонних NAPI плагинов. По данной причине потребуется установить расширение IE Tabs Инструкция по настройке просмотра в Chrome
- В Opera плагин не работает
- В Safari плагин не работает
Для MacOSX
Используйте клиент iVMS-4200 для macosx
Домофония
Перед настройкой обновите прошивки устройств до актуальных версий.
После обновления обязательно сделайте полный сброс настроек устройств.
Для работы с первым поколением устройств используйте клиент iVMS-4200 3.1.1.9
Для настройки второго поколения домофонии скачивайте актуальную версию
Настройку необходимо осуществлять на АНГЛИЙСКОМ ЯЗЫКЕ. Сменить язык на русский вы можете после.
Второе поколение устройств:
Домофоны: DS-KH6320-(W)TE1, DS-KH8350-(W)TE1, DS-KH8520-(W)TE1
Вызывные панели (V серия): DS-KV6113-(W)PE1, DS-KV8X13-WME1 и дверной звонок DS-KV6103-PE1
Модульная вызывная панель DS-KD8003-IME1
Прошивки вы можете скачать тут
Инструкция по настройке 2 поколения домофонии Intercom 2.0
Инструкция по настройке 2 поколения домофонии Intercom 1.0
Настройка терминалов доступа DS-K1T50X в качестве вызывных панелей для второго поколения домофонов
Подключение считываетелей к вызывным панелям и терминалам доступа
Если планируете подключать интерком устройства через Wi-Fi, просьба ознакомиться с данной инструкцией.
Первое поколение домофонии было представлено моделями:
Домофоны: DS-KH6210, DS-KH6310-(W,L), DS-KH8301-(WT), DS-KH8300-T
Вызывные панели (V серия): DS-KV8X02-IM, DS-KV8102-VP(IP)
Многоабонентские вызывные панели (D серия) : DS-KD3002-VM, DS-KD8002-VM, DS-KD8102-V
Актуальные прошивки на перечисленные устройства вы можете скачать тут
Инструкции по настройке вы можете найти на нашем ftp