38.9.6.3 SAAA Errors

Error Code	Error Message	Cause and Troubleshooting
0xC0B00001 SAAA001 -1062207487 3232759809	System error	Please restart your computer. If the issue still occurs, install again.
0xC0B00002 SAAA002 -1062207486 3232759810	Cannot process due to shortage of OS resources or memory.
0xC0B00003 SAAA003 -1062207485 3232759811	Cannot execute any new process until the server returns a processing result.
0xC0B00004 SAAA004 -1062207484 3232759812	The process was interrupted because Pro-Server EX was terminated.	A fatal error occurred. Restart WinGP and WinGP SDK after executing a forced transfer in GP-Pro EX.
0xC0B00005 SAAA005 -1062207483 3232759813	The process was suspended because Pro-Server EX was terminated during the process.
0xC0B00006 SAAA006 -1062207482 3232759814	Cannot process because Pro-Server EX has already been terminated.
0xC0B00007 SAAA007 -1062207481 3232759815	The specified connector has already been registered. The application is already in execution.	Please restart your computer. If the issue still occurs, install again.
0xC0B00008 SAAA008 -1062207480 3232759816	An error occurred in an OLE function. Cannot convert the data.
0xC0B0000A SAAA010 -1062207478 3232759818	Cannot refer to the resource because Pro-Server EX has not yet been started.
0xC0B0000B SAAA011 -1062207477 3232759819	Cannot request the system to execute processing because Pro-Server EX has not yet been started.
0xC0B0000C SAAA012 -1062207476 3232759820	The system is broken. Cannot process.
0xC0B00011 SAAA017 -1062207471 3232759825	An error occurred when accessing the XX file. File lock (shared) or corrupted. (XX: File name)	Please restart your computer. If the issue still occurs, install again.
0xC0B00012 SAAA018 -1062207470 3232759826	Too many connectors to register.
0xC0B00029 SAAA041 -1062207447 3232759849	Failed to get device information from the PRX file.	The screen project file may be damaged. Restart WinGP and WinGP SDK after executing a forced transfer in GP-Pro EX.
0xC0B0002A SAAA042 -1062207446 3232759850	Failed to get symbol info from the PRX file.
0xC0B0002B SAAA043 -1062207445 3232759851	Failed to get the device address from the PRX file.
0xC0B0002C SAAA044 -1062207444 3232759852	Failed to get setting information from the PRX file.
0xC0B0002D SAAA045 -1062207443 3232759853	Failed to create temporary file.	A temporary file creation folder may not have sufficient free space. Please check whether the drive has enough free space, and increase it if it is insufficient.
0xC0B0002E SAAA046 -1062207442 3232759854	Cannot open the PRX file.	The screen project file may be damaged. Restart WinGP and WinGP SDK after executing a forced transfer in GP-Pro EX.
0xC0B0002F SAAA047 -1062207441 3232759855	Failed to delete temporary file.	Please run again.
0xC0B00030 SAAA048 -1062207440 3232759856	The specified PRX file has an error.	The screen project file may be damaged. Restart WinGP and WinGP SDK after executing a forced transfer in GP-Pro EX.
0xC0B00031 SAAA049 -1062207439 3232759857	The PRX file does not have necessary data.
0xC0B00032 SAAA050 -1062207438 3232759858	The specified file is not a PRX file.
0xC0B00062 SAAA098 -1062207390 3232759906	The network project file is broken. Cannot read. Please confirm whether the file you specified is a real network project file.	A fatal error occurred. Restart WinGP and WinGP SDK after executing a forced transfer in GP-Pro EX.
0xC0B00063 SAAA099 -1062207389 3232759907	Cannot write to the network project file.	Please check whether the disk space is sufficient, and the hard disk has any problem.
0xC0B00064 SAAA100 -1062207388 3232759908	The file is not a network project file, or its version is old. Cannot read the data.	A fatal error occurred. Restart WinGP and WinGP SDK after executing a forced transfer in GP-Pro EX.
0xC0B00065 SAAA101 -1062207387 3232759909	The specified device was not found in (XX). It may have been deleted or renamed. Please review the settings. (XX: NODE name)
0xC0B00066 SAAA102 -1062207386 3232759910	The specified NODE (XX) has not been registered. There is a conflict. Please review the settings. (XX: NODE name)
0xC0B00067 SAAA103 -1062207385 3232759911	The specified NODE info is incorrect. No NODE info exists.
0xC0B00068 SAAA104 -1062207384 3232759912	The device setting in the system area of the specified NODE (XX) has an error. Please check the device you set. (XX: NODE name)
0xC0B00069 SAAA105 -1062207383 3232759913	(XX: XX) is invalid as a device or symbol. Cannot analyze. (XX: Device/Symbol name)	A nonexisting device/symbol name has been specified. Please confirm the symbol, following the direction of the message. If it does not solve the problem, the screen project file may be damaged. Restart WinGP and WinGP SDK after executing a forced transfer in GP-Pro EX.
0xC0B0006C SAAA108 -1062207380 3232759916	The network setting is broken.	Please review the network settings.
0xC0B00078 SAAA120 -1062207368 3232759928	(Symbol Sheet: XX Symbol: XX Address: XX) is invalid as a device address. (XX: Symbol Sheet name, XX: Symbol name, XX: Address)	The screen project file may be damaged. Restart WinGP and WinGP SDK after executing a forced transfer in GP-Pro EX.
0xC0B0007C SAAA124 -1062207364 3232759932	(Symbol Sheet: %s Symbol: %s Address: %s) is beyond the valid device range. (XX: Symbol Sheet name, XX: Symbol name, XX: Address)
0xC0B00082 SAAA130 -1062207358 3232759938	The specified node has not been registered in the network project. (XX:) NODE name	A fatal error occurred. Restart WinGP and WinGP SDK after executing a forced transfer in GP-Pro EX.
0xC0B00083 SAAA131 -1062207357 3232759939	The specified node (XX) is not a GP series node. (XX:) NODE name
0xC0B00084 SAAA132 -1062207356 3232759940	The device of the specified node (XX) is not supported. (XX:) NODE name
0xC0B00095 SAAA149 -1062207339 3232759957	(Symbol Sheet: XX Symbol: XX Number of Devices:XX) is beyond the range of the number of devices. (Valid Range: xx...xx)	Decrease the number of symbols registered on the GP-Pro EX Symbol screen.
0xC0B00096 SAAA150 -1062207338 3232759958	(Symbol Sheet: XX Group: XX) has the number of rows beyond the limit. Please reduce it. (XX rows or less)
0xC0B0009C SAAA156 -1062207332 3232759964	In a symbol sheet, 2 symbol/group names are redundant. (Symbol Sheet: XX Name1: XX Name2: XX)	Change the name of the symbol registered on the GP-Pro EX Symbol screen.
0xC0B0009D SAAA157 -1062207331 3232759965	The device driver of (Node: XX) is not supported. (Necessary driver has not been installed.) (XX: NODE name)	Please install according to Device/PLC differences.
0xC0B000A9 SAAA169 -1062207319 3232759977	(XX:XX) The specified Device or Symbol is beyond the valid device range. (xx: Device, xx: Number))	A device beyond the valid device range was accessed.
0xC0B000E0 SAAA224 -1062207264 3232760032	Warning: In different symbol sheets, 2 symbol/group names are the same. To use the same name, please specify the sheet name to which this symbol/group belongs. (xx: Existing symbol sheet name, xx: Symbol sheet name to which the same symbol name belongs, xx: Same symbol name)	In the GP-Pro EX Symbol setting screen, please change the name to avoid name duplication.
0xC0B000E1 SAAA225 -1062207263 3232760033	Warning: The symbol/group name is the same as a symbol sheet name. To use the same name, please specify the sheet name to which this symbol/group belongs. (xx: Symbol Sheet name to which Same Symbol name belongs, XX: Same Symbol name)
0xC0B000E4 SAAA228 -1062207260 3232760036	Warning: The array variable (XX) has too many elements for API Communication for WinGP to access the whole array.In API Communication for WinGP, only XX elements from the head are accessible. (XX: Symbol name, XX: Array Element number)	1. Consider registering the array by splitting it into multiple parts in GP-Pro EX. 2. If the array cannot be split, when importing the GP-Pro EX project file to the network project in Pro-Server EX, there is a function that automatically splits array variables that exceed the number that can be accessed simultaneously, and registers them as multiple symbols. Consider using Pro-Server EX instead of WinGP SDK.

Error Code

Error Message

Cause and Troubleshooting

0xC0B00001

SAAA001

-1062207487

3232759809

System error

Please restart your computer. If the issue still occurs, install again.

0xC0B00002

SAAA002

-1062207486

3232759810

Cannot process due to shortage of OS resources or memory.

0xC0B00003

SAAA003

-1062207485

3232759811

Cannot execute any new process until the server returns a processing result.

0xC0B00004

SAAA004

-1062207484

3232759812

The process was interrupted because Pro-Server EX was terminated.

A fatal error occurred.

Restart WinGP and WinGP SDK after executing a forced transfer in GP-Pro EX.

0xC0B00005

SAAA005

-1062207483

3232759813

The process was suspended because Pro-Server EX was terminated during the process.

0xC0B00006

SAAA006

-1062207482

3232759814

Cannot process because Pro-Server EX has already been terminated.

0xC0B00007

SAAA007

-1062207481

3232759815

The specified connector has already been registered. The application is already in execution.

Please restart your computer. If the issue still occurs, install again.

0xC0B00008

SAAA008

-1062207480

3232759816

An error occurred in an OLE function. Cannot convert the data.

0xC0B0000A

SAAA010

-1062207478

3232759818

Cannot refer to the resource because Pro-Server EX has not yet been started.

0xC0B0000B

SAAA011

-1062207477

3232759819

Cannot request the system to execute processing because Pro-Server EX has not yet been started.

0xC0B0000C

SAAA012

-1062207476

3232759820

The system is broken. Cannot process.

0xC0B00011

SAAA017

-1062207471

3232759825

An error occurred when accessing the XX file. File lock
(shared) or corrupted.

(XX: File name)

Please restart your computer. If the issue still occurs, install again.

0xC0B00012

SAAA018

-1062207470

3232759826

Too many connectors to register.

0xC0B00029

SAAA041

-1062207447

3232759849

Failed to get device information from the PRX file.

The screen project file may be damaged.

Restart WinGP and WinGP SDK after executing a forced transfer in GP-Pro EX.

0xC0B0002A

SAAA042

-1062207446

3232759850

Failed to get symbol info from the PRX file.

0xC0B0002B

SAAA043

-1062207445

3232759851

Failed to get the device address from the PRX file.

0xC0B0002C

SAAA044

-1062207444

3232759852

Failed to get setting information from the PRX file.

0xC0B0002D

SAAA045

-1062207443

3232759853

Failed to create temporary file.

A temporary file creation folder may not have sufficient free space. Please check whether the drive has enough free space, and increase it if it is insufficient.

0xC0B0002E

SAAA046

-1062207442

3232759854

Cannot open the PRX file.

The screen project file may be damaged.

Restart WinGP and WinGP SDK after executing a forced transfer in GP-Pro EX.

0xC0B0002F

SAAA047

-1062207441

3232759855

Failed to delete temporary file.

Please run again.

0xC0B00030

SAAA048

-1062207440

3232759856

The specified PRX file has an error.

The screen project file may be damaged.

Restart WinGP and WinGP SDK after executing a forced transfer in GP-Pro EX.

0xC0B00031

SAAA049

-1062207439

3232759857

The PRX file does not have necessary data.

0xC0B00032

SAAA050

-1062207438

3232759858

The specified file is not a PRX file.

0xC0B00062

SAAA098

-1062207390

3232759906

The network project file is broken. Cannot read. Please confirm whether the file you specified is a real network project file.

A fatal error occurred.

Restart WinGP and WinGP SDK after executing a forced transfer in GP-Pro EX.

0xC0B00063

SAAA099

-1062207389

3232759907

Cannot write to the network project file.

Please check whether the disk space is sufficient, and the hard disk has any problem.

0xC0B00064

SAAA100

-1062207388

3232759908

The file is not a network project file, or its version is old. Cannot read the data.

A fatal error occurred.

Restart WinGP and WinGP SDK after executing a forced transfer in GP-Pro EX.

0xC0B00065

SAAA101

-1062207387

3232759909

The specified device was not found in (XX). It may have been deleted or renamed. Please review the settings.

(XX: NODE name)

0xC0B00066

SAAA102

-1062207386

3232759910

The specified NODE (XX) has not been registered. There is a conflict. Please review the settings.

(XX: NODE name)

0xC0B00067

SAAA103

-1062207385

3232759911

The specified NODE info is incorrect. No NODE info exists.

0xC0B00068

SAAA104

-1062207384

3232759912

The device setting in the system area of the specified NODE (XX) has an error. Please check the device you set.

(XX: NODE name)

0xC0B00069

SAAA105

-1062207383

3232759913

(XX: XX) is invalid as a device or symbol. Cannot analyze.

(XX: Device/Symbol name)

A nonexisting device/symbol name has been specified. Please confirm the symbol, following the direction of the message. If it does not solve the problem, the screen project file may be damaged. Restart WinGP and WinGP SDK after executing a forced transfer in GP-Pro EX.

0xC0B0006C

SAAA108

-1062207380

3232759916

The network setting is broken.

Please review the network settings.

0xC0B00078

SAAA120

-1062207368

3232759928

(Symbol Sheet: XX Symbol: XX Address: XX) is invalid as a device address. (XX: Symbol Sheet name, XX: Symbol name, XX: Address)

The screen project file may be damaged.

Restart WinGP and WinGP SDK after executing a forced transfer in GP-Pro EX.

0xC0B0007C

SAAA124

-1062207364

3232759932

(Symbol Sheet: %s Symbol: %s Address: %s) is beyond the valid device range. (XX: Symbol Sheet name, XX: Symbol name, XX: Address)

0xC0B00082

SAAA130

-1062207358

3232759938

The specified node has not been registered in the network project.

(XX:) NODE name

A fatal error occurred.

Restart WinGP and WinGP SDK after executing a forced transfer in GP-Pro EX.

0xC0B00083

SAAA131

-1062207357

3232759939

The specified node (XX) is not a GP series node.

(XX:) NODE name

0xC0B00084

SAAA132

-1062207356

3232759940

The device of the specified node (XX) is not supported.

(XX:) NODE name

0xC0B00095

SAAA149

-1062207339

3232759957

(Symbol Sheet: XX Symbol: XX Number of Devices:XX) is beyond the range of the number of devices. (Valid Range: xx...xx)

Decrease the number of symbols registered on the GP-Pro EX Symbol screen.

0xC0B00096

SAAA150

-1062207338

3232759958

(Symbol Sheet: XX Group: XX) has the number of rows beyond the limit. Please reduce it. (XX rows or less)

0xC0B0009C

SAAA156

-1062207332

3232759964

In a symbol sheet, 2 symbol/group names are redundant. (Symbol Sheet: XX Name1: XX Name2: XX)

Change the name of the symbol registered on the GP-Pro EX Symbol screen.

0xC0B0009D

SAAA157

-1062207331

3232759965

The device driver of (Node: XX) is not supported. (Necessary driver has not been installed.)

(XX: NODE name)

Please install according to Device/PLC differences.

0xC0B000A9

SAAA169

-1062207319

3232759977

(XX:XX) The specified Device or Symbol is beyond the valid device range.

(xx: Device, xx: Number))

A device beyond the valid device range was accessed.

0xC0B000E0

SAAA224

-1062207264

3232760032

Warning: In different symbol sheets, 2 symbol/group names are the same. To use the same name, please specify the sheet name to which this symbol/group belongs.

(xx: Existing symbol sheet name, xx: Symbol sheet name to which the same symbol name belongs, xx: Same symbol name)

In the GP-Pro EX Symbol setting screen, please change the name to avoid name duplication.

0xC0B000E1

SAAA225

-1062207263

3232760033

Warning: The symbol/group name is the same as a symbol sheet name. To use the same name, please specify the sheet name to which this symbol/group belongs.
(xx: Symbol Sheet name to which Same Symbol name belongs, XX: Same Symbol name)

0xC0B000E4

SAAA228

-1062207260

3232760036

Warning: The array variable (XX) has too many elements for API Communication for WinGP to access the whole array.In API Communication for WinGP, only XX elements from the head are accessible.

(XX: Symbol name, XX: Array Element number)

1. Consider registering the array by splitting it into multiple parts in GP-Pro EX.

2. If the array cannot be split, when importing the GP-Pro EX project file to the network project in Pro-Server EX, there is a function that automatically splits array variables that exceed the number that can be accessed simultaneously, and registers them as multiple symbols.
Consider using Pro-Server EX instead of WinGP SDK.

Line 1: error code
Line 2: Integrated error code
Line 3: Base10 signed error code
Line 4: Base10 unsigned error code