Error Code |
Error Message |
Cause and Troubleshooting |
---|---|---|
0xC0B00201 SAAF001 -1062206975 3232760321 |
Cannot initialize TCP/IP. |
From the Windows [Control Panel]-[Network Connection], confirm that connection settings are enabled and confirm in the connection setting properties that the TCP/IP protocol has been installed. 'WinGP SDK' does not work without TCP/IP. |
0xC0B00203 SAAF003 -1062206973 3232760323 |
This PC does not have a valid IP address allocated. Please check the TCP/IP environment of this PC. |
Please confirm that the LAN card works properly. Please check the LAN cable, too. |
0xC0B00204 SAAF004 -1062206972 3232760324 |
Cannot load the PLCInfo.xml file. |
Please update the protocol driver. If it does not solve the problem, please install 'WinGP SDK' again. |
0xC0B00205 SAAF005 -1062206971 3232760325 |
Cannot load the Editor Driver. |
|
0xC0B00206 SAAF006 -1062206970 3232760326 |
An error occurred on the Active-X I/F. |
Please confirm that the OS version is appropriate. If the phenomenon still reoccurs despite the restart, please install 'WinGP SDK' again. |
0xC0B00207 SAAF007 -1062206969 3232760327 |
Cannot execute because of the version inconsistency of DLL and EXE for Pro-Server EX.xxThis program will be shut down. (xx: program name) |
Please confirm that there are not multiple different versions of 'Pro-Server EX' or DLLs of 'WinGP SDK' are installed in one PC. Only 1 version of 'Pro-Server EX' or 'WinGP SDK' can be installed in a PC. |
0xC0B00209 SAAF009 -1062206967 3232760329 |
The file Core.ID was not found. |
Please restart your PC. If it does not solve the problem, please install 'WinGP SDK' again. |
0xC0B0020B SAAF011 -1062206965 3232760331 |
ProNet.dll has not been installed properly. |
|
0xC0B0020C SAAF012 -1062206964 3232760332 |
Cannot start Pro-Server EX. Please close all the applications that use WinGP node EX or Pro-Server EX, and try again. |
Cannot start 'WinGP SDK' because 'WinGP SDK' or an application using 'WinGP SDK' may not have stopped normally. Please close 'WinGP SDK' and all the applications running on it, and then try again. |
0xC0B00211 SAAF017 -1062206959 3232760337 |
This API is not supported. |
The API you use is unavailable. Please consider another method. |
0xC0B00212 SAAF018 -1062206958 3232760338 |
The specified text is invalid as a device address. |
Please reconfirm the address specification method. Please confirm that no change has been made to devices and nodes. Please confirm that the necessary device driver has been installed. |
0xC0B00213 SAAF019 -1062206957 3232760339 |
The specified device supports bit access only. |
Please confirm the device to access and the access method. |
0xC0B00214 SAAF020 -1062206956 3232760340 |
The specified device driver is not supported (The necessary device driver has not been installed). |
Please install according to Device/PLC differences. |
0xC0B00215 SAAF021 -1062206955 3232760341 |
The parameter value is invalid. |
Please review the API parameters. |
0xC0B00216 SAAF022 -1062206954 3232760342 |
The device no. is out of range. |
Please check the device number. |
0xC0B00217 SAAF023 -1062206953 3232760343 |
The specified device does not exist. |
Please check that the Device/PLC settings or System Area Start Address settings are correct. |
0xC0B00218 SAAF024 -1062206952 3232760344 |
The specified group symbol does not exist. |
Please check the group symbol specification. |
0xC0B0021A SAAF026 -1062206950 3232760346 |
In Queuing Access, read-access and write-access, or cache access and direct access, cannot be mixed. |
Please confirm that no different access method exists between the start of queuing and the actual access. If there is the necessity of using a different access method, please use another queuing access. |
0xC0B0021D SAAF029 -1062206947 3232760349 |
The specified node has not been registered in the network project. |
Please check the node specification. |
0xC0B0021F SAAF031 -1062206945 3232760351 |
The API was double called. The specified access handle for Pro-Server EX is already running. |
Consider using EasySetWaitType() to avoid calling the API simultaneously. |
0xC0B00220 SAAF032 -1062206944 3232760352 |
In data-type conversion, the data type of the conversion source/destination is unsupported. |
Please check the contents of the Variant type. |
0xC0B00221 SAAF033 -1062206943 3232760353 |
Backup data type specified is not supported. |
Please check the data type specification. |
0xC0B00222 SAAF034 -1062206942 3232760354 |
Failed to open the SRAM backup data file or to create its copy in the PC. |
Please check the specifications of the destination file/folder in the PC, disk space, and the access rights to the file, etc. |
0xC0B00223 SAAF035 -1062206941 3232760355 |
In Read/Write Backup Data, failed to access the file. |
In reading or writing SRAM Backup Data, an error occurred in accessing the specified file. Please check the free space of the PC and the file access right, and then execute it again. |
0xC0B00224 SAAF036 -1062206940 3232760356 |
In Write SRAM Backup Data, the specified file size is too large. It must be 96 KB or less. |
Please confirm that the file specified in Write SRAM Backup Data is correct. Also, please specify a file of the size of 96Kbytes or less. |
0xC0B00225 SAAF037 -1062206939 3232760357 |
Numeric value error. Please set a correct value. |
Please confirm that the string is valid as a numeric value. |
0xC0B00226 SAAF038 -1062206938 3232760358 |
The specified data count is 0 or out of range. |
Please check the data count. |
0xC0B00227 SAAF039 -1062206937 3232760359 |
The max number of access destinations is too high (It must be 1500 or less). |
Please consider dividing it for successful access. |
0xC0B00228 SAAF040 -1062206936 3232760360 |
The total buffer size of the data to access is too high. (It must be 1 MB or less.) |
|
0xC0B00230 SAAF048 -1062206928 3232760368 |
Cannot start Pro-Server EX. |
Please restart your computer. If the problem is not solved, please install 'WinGP SDK' again. |
0xC0B00238 SAAF056 -1062206920 3232760376 |
Reading out logging data from a GP3000 Series / WinGP NODE is not allowed. |
Please change the setting to not execute Read Logging Data when the target is a 'WinGP' Node. |
0xC0B00239 SAAF057 -1062206919 3232760377 |
Reading out trend data from a GP3000 Series / WinGP NODE is not allowed. |
Please change the setting to not execute Read Trend Data when the target is a 'WinGP' Node. |
0xC0B00240 SAAF064 -1062206912 3232760384 |
The specified access handle for Pro-Server EX is invalid. |
Please restart your PC. It must be other than 0, correctly created, and not discarded. |
0xC0B00241 SAAF065 -1062206911 3232760385 |
Cannot continue because this command is unsupported. |
Please restart your computer. If the problem is not solved, please install 'WinGP SDK' again. |
0xC0B00242 SAAF066 -1062206910 3232760386 |
Cannot process because Pro-Server EX has stopped. |
Please exit all applications before you close 'WinGP SDK'. |
0xC0B00243 SAAF067 -1062206909 3232760387 |
While waiting for processing results from the server, the API received the application quitting message. |
If you do not want to receive WM_QUIT, please use a multihandle system API in EasySetWaitTypeM(2). |
0xC0B00244 SAAF068 -1062206908 3232760388 |
The file name consists of more than 256 characters. Supposed to be within 256 characters. |
Please check the file name specification. |
0xC0B00245 SAAF069 -1062206907 3232760389 |
Queuing access registration has not started. |
Please check the sequence of the program. |
0xC0B00246 SAAF070 -1062206906 3232760390 |
Actual queuing access has not been made. |
|
0xC0B00247 SAAF071 -1062206905 3232760391 |
The device access to the specified number has failed. |
Please check the cable or device operating environment. |
0xC0B00248 SAAF072 -1062206904 3232760392 |
The device access with the specified number has not been registered. Please check the preregistered access count and number. |
Please check the sequence of the program. |
0xC0B0024C SAAF076 -1062206900 3232760396 |
The specified group number is not within the range of the sampling data group number. |
Please review the API parameters. |
0xC0B0024D SAAF077 -1062206899 3232760397 |
In Queuing Access, Read and Write cannot be mixed. |
Please check the sequence of the program. |
0xC0B00250 SAAF080 -1062206896 3232760400 |
No word exists. |
Please review the API parameters. |
0xC0B00251 SAAF081 -1062206895 3232760401 |
Invalid name/word. Illegal characters are included. |
|
0xC0B00252 SAAF082 -1062206894 3232760402 |
The specified node has not been registered in the network project. |
Please review the API parameters. |
0xC0B00253 SAAF083 -1062206893 3232760403 |
The specified device has not been registered. |
|
0xC0B00254 SAAF084 -1062206892 3232760404 |
Array Index Specification Error. |
Please check the array specification method. |
0xC0B00255 SAAF085 -1062206891 3232760405 |
The specified device is an undefined symbol or an invalid address. |
Please check the device address specification method. |
0xC0B00256 SAAF086 -1062206890 3232760406 |
The symbol name is invalid, or the group specification is too deeply nested. |
|
0xC0B00257 SAAF087 -1062206889 3232760407 |
Index specification is unavailable for a string-type symbol. |
|
0xC0B00258 SAAF088 -1062206888 3232760408 |
The specified index value is too high. |
|
0xC0B00259 SAAF089 -1062206887 3232760409 |
Group symbol specification is unavailable for this device specification. |
|
0xC0B0025A SAAF090 -1062206886 3232760410 |
Please specify a group symbol to specify a device. |
|
0xC0B0025B SAAF091 -1062206885 3232760411 |
The symbol sheet name is invalid, or unavailable for the specified device. |
Please check the device address specification method. |
0xC0B0025C SAAF092 -1062206884 3232760412 |
The connecting device names are redundantly specified. |
A fatal error occurred. Restart 'WinGP' and 'WinGP SDK' after executing a forced transfer in 'GP-Pro EX'. |
0xC0B0025D SAAF093 -1062206883 3232760413 |
Cannot use the specified symbol because its data type is different from the one required here. |
The symbol data type and the specified data type are different and cannot be used. Check the Symbol name or data type. |
0xC0B0025E SAAF094 -1062206882 3232760414 |
Failed to analyze the option-specifying text. |
Please review the API parameters. |
0xC0B00262 SAAF098 -1062206878 3232760418 |
Failed to read the file. |
Please confirm that the specified file exists in the CF Card folder. If exists, please confirm the right of access to the file. |
0xC0B00263 SAAF099 -1062206877 3232760419 |
Failed to writing to the file. |
Please check the access rights to the write destination. If there is no problem with the access right, please check whether the CF Card has enough free space. |
0xC0B00264 SAAF100 -1062206876 3232760420 |
The specified file was not found. |
Please confirm that the specified file exists. |
0xC0B00265 SAAF101 -1062206875 3232760421 |
Failed to delete the file. |
Please confirm that the specified file exists in the CF Card folder. If it exists, please confirm the access rights to the file. |
0xC0B00266 SAAF102 -1062206874 3232760422 |
Failed to rename the file. |
Please confirm that the specified file exists in the CF Card folder. If it does, please check the access right to the file and whether the new file name does not contain any forbidden characters. |
0xC0B00267 SAAF103 -1062206873 3232760423 |
Cannot open the file list retention file. |
Please check the access rights to the destination folder. If there is no problem with the access right, please check whether the drive has enough free space. |
0xC0B00269 SAAF105 -1062206871 3232760425 |
No file name has been inputted. |
Please input a file name. |
0xC0B0026A SAAF106 -1062206870 3232760426 |
Too long file path. |
Please shorten the file path. |
0xC0B0026C SAAF108 -1062206868 3232760428 |
Connection to GP3000 Series NODE was reset. |
After confirming the GP3000 Series NODE/'WinGP' Node is still on and the cable is properly connected, please execute it again |
0xC0B0026D SAAF109 -1062206867 3232760429 |
The destination NODE does not respond. |
|
0xC0B0026E SAAF110 -1062206866 3232760430 |
Could not complete the operation because connection was broken during the process. |
|
0xC0B0026F SAAF111 -1062206865 3232760431 |
Cannot connect to the specified node because it does not exist. |
Please use the #WinGP node name. |
0xC0B00272 SAAF114 -1062206862 3232760434 |
The parameter value is invalid. |
Please review the inputted parameter, and set a correct value. |
0xC0B00273 SAAF115 -1062206861 3232760435 |
Failed to get a file list from the CF/SD Card. |
Please confirm that the specified file type is correct. Also, please check the access right to the destination folder. If there is no problem with the access right, please check whether the drive has enough free space. |
0xC0B00274 SAAF116 -1062206860 3232760448 |
Could not connect to GP3000 Series NODE / WinGP NODE. |
'WinGP' NODE may be busy. Please execute it again after a brief interval. Or, if the connection with 'WinGP' NODE is established using the transfer tool, please exit the tool and then execute it again. |
0xC0B002A6 SAAF166 -1062206810 3232760486 |
Read SRAM Backup Data is now being used. |
Please execute Read SRAM Backup Data again. |
0xC0B002A7 SAAF167 -1062206809 3232760487 |
Parameter Error in Read SRAM Backup Data |
Please execute Read SRAM Backup Data using a correct parameter. |
0xC0B002A8 SAAF168 -1062206808 3232760488 |
Failed to write to a saved file. |
If the hard-disk capacity of the PC is insufficient, please increase it and execute the operation again. Or please restart the PC and execute again. |
Line 1: error code
Line 2: Integrated error code
Line 3: Base10 signed error code
Line 4: Base10 unsigned error code