Getlasterror,windows API Call Error when you use this function to view errors

〖0〗-operation completed successfully.
〖1〗-function error.
The 〖2〗-system cannot find the file specified.
The 〖3〗-system could not find the path specified.
The 〖4〗-system cannot open the file.
〖5〗-denied access.
The 〖6〗-handle is not valid.
The 〖7〗-Storage control block is corrupted.
〖8〗-There is not enough storage space to process this command.
〖9〗-Storage Control block address is invalid.
〖10〗-environment error.
〖11〗-attempted to load a malformed program.
The 〖12〗-access code is invalid.
〖13〗-data is invalid.
There is not enough 〖14〗-memory to complete this operation.
The 〖15〗-system could not find the specified drive.
〖16〗-cannot delete the directory.
The 〖17〗-system cannot move files to a different drive.
〖18〗-no more files.
〖19〗-Media is protected by write.
The 〖20〗-system could not find the specified device.
The 〖21〗-device is not ready.
The 〖22〗-device does not recognize this command.
〖23〗-Data error (cyclic redundancy check).
The 〖24〗-program issues commands, but the command length is incorrect.
The 〖25〗-drive cannot find the location of a specific area or track on the disk.
〖26〗-cannot access the specified disk or diskette.
The 〖27〗-drive could not find the requested sector.
〖28〗-printer is missing paper.
The 〖29〗-system cannot write to the specified device.
The 〖30〗-system cannot read from the specified device.
〖31〗-devices connected to the system are not functioning.
The 〖32〗-process cannot access the file because the file is being used by another program.
The 〖33〗-process cannot access the file because another program has locked part of the file.
〖36〗-is used to share too many open files.
〖38〗-reaches the end of the file.
〖39〗-disk is full.
〖50〗-does not support network requests.
〖51〗-The remote computer is not available.
The 〖52〗-already has duplicate names on the network.
〖53〗-the network path could not be found.
〖54〗-network Busy.
〖55〗-the specified network resource or device is no longer available.
〖56〗-has reached the network BIOS command limit.
〖57〗-network adapter hardware error.
〖58〗-The specified server cannot run the requested operation.
〖59〗-An unexpected network error occurred.
〖60〗-remote adapter is not compatible.
The 〖61〗-printer queue is full.
〖62〗-cannot get the space on the server to save the file to be printed.
〖63〗-Delete files waiting to be printed.
The network name specified by 〖64〗-is no longer available.
〖65〗-Deny network access.
〖66〗-network resource type error.
〖67〗-the network name could not be found.
〖68〗-exceeds the name limit for local computer networks cards.
〖69〗-exceeded the network BIOS session limit.
〖70〗-The remote server has been paused or is in the process of being started.
〖71〗-is currently no longer connected to this remote computer because it has reached the limit of the number of connections to the computer.
〖72〗-the specified printer or disk device has been paused.
The 〖80〗-file exists.
〖82〗-cannot create a directory or file.
〖83〗-int 24 failed.
〖84〗-cannot get the storage space to handle this request.
〖85〗-The local device name is already in use.
〖86〗-The specified network password error.
〖87〗-parameter error.
A write error occurred on the 〖88〗-network.
The 〖89〗-system cannot start another process at this time.
〖100〗-cannot create another system semaphore.
〖101〗-another process has an exclusive semaphore.
〖102〗-The semaphore has been set and cannot be turned off.
〖103〗-can no longer set the semaphore.
〖104〗-cannot request an exclusive semaphore at interrupt time.
〖105〗-the previous ownership of this semaphore has ended.
The 〖107〗-program stops because the replacement floppy disk is not plugged in.
The 〖108〗-disk is in use or locked by another process.
The 〖109〗-pipeline has ended.
The 〖110〗-system cannot open the specified device or file.
〖111〗-file name is too long.
〖112〗-disk space is low.
〖113〗-can no longer obtain the identity of the internal file.
The 〖114〗-target internal file is not identified correctly.
The 〖117〗-application made an IOCTL call error.
〖118〗-Verify that the switching parameter value of the write is incorrect.
The 〖119〗-system does not support the requested command.
〖120〗-This feature is only supported by this system.
〖121〗-semaphore time-out time has arrived.
〖122〗-The data area passed to the system call is too small.
〖123〗-file name, directory name, or volume label method is incorrect.
〖124〗-system call level error.
〖125〗-disk does not have a volume label.
〖126〗-the specified module could not be found.
〖127〗-the specified program could not be found.
〖128〗-There are no waiting child processes.
〖130〗-a file handle to an open disk partition that attempts to use an operation instead of raw disk I/O.
〖131〗-tries to move the file pointer to the beginning of the file.
〖132〗-cannot set the file pointer on the specified device or file.
〖133〗-contains a drive that was previously joined to a drive that cannot use the join or SUBST command.
〖134〗-attempted to use the JOIN or SUBST command on a drive that has been merged.
〖135〗-attempted to use the JOIN or SUBST command on a drive that has been merged.
The 〖136〗-system attempted to unblock a JOIN of an unincorporated drive.
The 〖137〗-system attempted to release the SUBST of the non-replacement drive.
The 〖138〗-system attempted to merge drives into a directory on a merged drive.
The 〖139〗-system attempted to replace the drive with a directory on a replacement drive.
The 〖140〗-system attempted to merge drives into a directory on an alternate drive.
The 〖141〗-system tries to replace the drive as a directory on the merged drive.
The 〖142〗-system cannot run JOIN or SUBST at this time.
The 〖143〗-system cannot merge drives into or replace directories on the same drive.
The 〖144〗-directory is not a subdirectory under the root directory.
〖145〗-directory is not empty.
〖146〗-the specified path is already in use in the override.
〖147〗-insufficient resources to process this command.
The path specified by 〖148〗-cannot be used at this time.
〖149〗-attempts to merge or replace a drive with a drive on a drive where the directory is the target of the previous override.
〖150〗-system trace information is not in CONFIG. SYS file, or do not allow tracing.
〖151〗-the number of semaphore events specified for dosmuxsemwait is incorrect.
The 〖152〗-dosmuxsemwait is not operational. Too many semaphores have been set.
〖153〗-dosmuxsemwait list error.
〖154〗-the volume label entered exceeds the length limit of the target file system
〖155〗-cannot create another thread.
The 〖156〗-receive process has rejected this signal.
The 〖157〗-segment has been discarded and cannot be locked.
The 〖158〗-segment has been unlocked.
〖159〗-the address of the thread identity is incorrect.
〖160〗-passed to DOSEXECPGM parameter string error.
The path specified by 〖161〗-is not valid.
The 〖162〗-signal is paused.
〖164〗-cannot create more threads in the system.
〖167〗-cannot lock the file area.
〖170〗-the requested resource is in use.
〖173〗-requests to provide a cancellation zone for locking are not obvious.
The 〖174〗-file system does not support the minimum unit change for a locked type.
The 〖180〗-system detects the wrong segment number.
〖183〗-The file cannot be created when the file already exists.
〖186〗-passed a flag error.
〖187〗-the specified system semaphore name was not found.
The 〖196〗-operating system cannot run this application.
The current configuration of the 〖197〗-operating system cannot run this application.
The 〖199〗-operating system cannot run this application.
The 〖200〗-code snippet must not be greater than or equal to 64K.
The 〖203〗-operating system could not find the environment option that was entered.
The process in the 〖205〗-command subtree does not have a signal handler.
〖206〗-file name or extension is too long.
〖207〗-2nd Ring Stack is already occupied.
〖208〗-does not correctly enter the filename wildcard * or?, or specifies too many file name wildcard characters.
〖209〗-is sending a bad signal.
〖210〗-cannot set the signal handler.
The 〖212〗-segment is locked and cannot be reassigned.
〖214〗-There are too many dynamic link modules attached to the program or dynamic link module.
〖215〗-cannot nest calls to LoadModule.
〖230〗-pipeline status is invalid.
〖231〗-all pipeline instances are in use.
The 〖232〗-pipeline is shutting down.
There is no process on the other end of the 〖233〗-pipe.
〖234〗-more data is available.
〖240〗-Cancel the session.
〖254〗-the specified extended property name is not valid.
〖255〗-extended properties are inconsistent.
〖258〗-the pending operation is obsolete.
There is no data available for the 〖259〗-.
〖266〗-cannot use the copy function.
〖267〗-directory name is invalid.
The 〖275〗-extension property does not apply in the buffer.
〖276〗-the extended Properties file installed on the file system is corrupted.
〖277〗-extended Attribute table file is full.
〖278〗-the specified extended property handle is invalid.
〖282〗-mounted file systems do not support extended properties.
〖288〗-attempts to release a multi-user terminal run program that is not owned by the caller.
The 〖298〗-sent too many requests to the semaphore.
〖299〗-only partial readprocessmemoty or writeprocessmemory requests are completed.
The 〖300〗-operation lockout request was denied.
The 〖301〗-system received an invalid operation lock acknowledgement.
〖487〗-attempted to access an invalid address.
〖534〗-arithmetic results exceed 32 digits.
The other end of the 〖535〗-pipeline has a process.
〖536〗-waits for a process to open the other end of the pipe.
〖994〗-denied access to extended properties.
〖995〗-I/O operations have been discarded due to thread exits or application requests.
〖996〗-overlapped I/O events are not in the signal state.
〖997〗-overlapped I/O operations are in progress.
〖998〗-memory allocation access is not valid.
〖999〗-error running in-page operation.
〖1001〗-recursion too deep; stack overflow.
The 〖1002〗-window cannot operate on a message that has been sent.
〖1003〗-cannot complete this function.
〖1004〗-invalid flag.
〖1005〗-This volume does not contain a recognizable file system. Make sure that all requested file system drivers are loaded and that the volume is not corrupted.
The volume on which the 〖1006〗-file resides has been externally altered, so the opened file is no longer valid.
〖1007〗-cannot run the requested operation in full screen mode.
〖1008〗-attempted to reference a token that does not exist.
〖1009〗-Configuration Registry database corruption.
The 〖1010〗-configuration registry key is invalid.
〖1011〗-cannot open the configuration registry key.
〖1012〗-cannot read the configuration registry key.
〖1013〗-cannot write to the configuration registry key.
〖1014〗-a file in the registry database must be recovered using a record or alternate replication. Recovery completed successfully.
〖1015〗-the registry is corrupted. A file structure that contains registry data is corrupted, or the file memory image of the system is corrupted, or the file cannot be recovered because of an alternate copy, missing or corrupted log.
〖1016〗-Recovery of I/O operations initiated by the registry failed. The registry cannot read in, write out, or clear any file that contains a registry system image.
The 〖1017〗-system attempted to load or restore a file to the registry, but the specified file is not in the registry file format.
〖1018〗-attempted to run an illegal operation on a registry key that is marked for deletion.
The 〖1019〗-system cannot configure the requested space in the registry log.
〖1020〗-cannot create a symbolic link in a registry key that already has subkeys or values.
〖1021〗-cannot create a stable subkey under the variable parent.
〖1022〗-notifies the change request that it is completing and that the information is not returned to the caller's buffer. The current caller must enumerate the files to find the changes.
〖1051〗-has sent stop control to the service, which is dependent on other running services.
〖1052〗-requested control is not valid for this service
The 〖1053〗-service does not respond to a start or control request in a timely manner.
〖1054〗-cannot create a thread for this service.
〖1055〗-locks the service database.
An instance of the 〖1056〗-service is already running.
The 〖1057〗-account name is invalid or does not exist, or the password is not valid for the specified account name.
〖1058〗-cannot start the service because it may be disabled or the device associated with it is not started.
〖1059〗-Specifies the cyclic service dependency.
〖1060〗-The specified service does not exist with the installed service.
The 〖1061〗-service was unable to receive control information at this time.
The 〖1062〗-service is not started.
The 〖1063〗-service process could not connect to the service controller.
〖1064〗-An exception occurred in the service when the control request was processed.
〖1065〗-The specified database does not exist.
The 〖1066〗-service has returned a specific service error code.
The 〖1067〗-process terminated unexpectedly.
〖1068〗-Dependency Service or group failed to start.
〖1069〗-failed to start the service because of a logon failure.
After the 〖1070〗-is started, the service stays in the start-pause state.
〖1071〗-The specified service database lock is invalid.
〖1072〗-The specified service has been marked for deletion.
〖1073〗-The specified service already exists.
The 〖1074〗-system is currently running with the most recent and valid configuration.
The 〖1075〗-dependency service does not exist or has been marked for deletion.
〖1076〗-has accepted the use of the current boot as the last valid control setting.
〖1077〗-The boot service has not been attempted since the last boot.
The 〖1078〗-name is already used as the service name or service display name.
〖1079〗-the account for this service differs from the account that is running on other services on the same process.
〖1080〗-can only set failed actions for the WIN32 service and cannot be set for the driver.
〖1081〗-This service runs the same processing and service Control Manager. Therefore, the Service Control Manager cannot do anything if the service handler is aborted unexpectedly.
〖1082〗-The recovery program has not been set up for this service.
The service 〖1083〗-configured to run in the executable program cannot execute the service.
The 〖1100〗-has reached the actual end of the tape.
〖1101〗-tape access has reached the file tag.
The 〖1102〗-has reached the beginning of a tape or disk partition.
〖1103〗-tape access has reached the end of a set of files.
There is no more data on the 〖1104〗-tape.
〖1105〗-tape cannot be partitioned.
〖1106〗-the current block size is incorrect when accessing a new tape for a multi-volume partition.
〖1107〗-the partition information was not found when loading the tape.
〖1108〗-cannot lock the media eject feature.
〖1109〗-cannot unload media.
The media in the 〖1110〗-drive may have changed.
〖1111〗-resets the I/O bus.
There is no media in the 〖1112〗-drive.
〖1113〗-in a multi-byte target code page, there are no characters that this Unicode character can map to.
〖1114〗-Dynamic link library (DLL) initialization routines failed.
〖1115〗-system shutdown is in progress.
〖1116〗-cannot interrupt the system shutdown because there is no ongoing shutdown process.
〖1117〗-cannot run this request because of an I/O device error.
〖1118〗-No serial device was initialized successfully. The serial driver will be uninstalled.
〖1119〗-cannot open a device that is sharing an interrupt request (IRQ) with another device. At least one other device that uses the IRQ is turned on.
The 〖1120〗-sequence I/O operation has been completed by writing another serial port. (Ioctl_serial_xoff_counter has reached 0.) )
〖1121〗-the serial I/O operation is complete because the timeout period has expired. (Ioctl_serial_xoff_counter not up to 0.) )
〖1122〗-the ID address tag was not found on the floppy disk.
〖1123〗-floppy disk sector ID Word value field does not match the floppy disk controller track address.
The 〖1124〗-floppy controller reports errors that the floppy driver does not recognize.
The 〖1125〗-floppy controller returns inconsistent results with its registers.
〖1126〗-when the hard drive is accessed, the recalibration operation fails and the retry still fails.
〖1127〗-the disk operation failed while accessing the hard disk, and the retry still failed.
〖1128〗-when accessing the hard drive, the disk controller must be reset even if it fails.
The 〖1129〗-has reached the end of the tape.
〖1130〗-server does not have enough storage space to handle this command.
The 〖1131〗-detects a potential deadlock state.
〖1132〗-the specified base address or file offset is not properly aligned.
〖1140〗-attempts to change the system power state are deprecated by another application or driver.
The 〖1141〗-system BIOS has failed to change the system power state.
〖1142〗-attempts to create a link on a file that exceeds the allowable amount of the system.
〖1150〗-Specifies the version of Windows that the program requires to update.
〖1151〗-Specifies that the program is not a Windows or MS-DOS program.
〖1152〗-only one instance of the specified program can be started.
〖1153〗-The specified program applies to older versions of Windows.
〖1154〗-One of the library files required to execute the application is corrupted.
〖1155〗-no application is associated with the specified file for this operation.
〖1156〗-An error occurred during the delivery of the instruction to the application.
〖1157〗-One of the library files required to execute the application could not be found.
〖1158〗-the current program has used all the handles allowed by the Window Manager object's system.
〖1159〗-messages can only be used with synchronization operations.
〖1160〗-indicates that the source element does not have media.
〖1161〗-indicates that the target element already contains media.
The element indicated by 〖1162〗-does not exist.
The element indicated by 〖1163〗-is part of the storage resource that is not displayed.
The 〖1164〗-display device needs to be reinitialized because of hardware errors.
The 〖1165〗-device shows that it needs to be cleared before attempting further operation.
The 〖1166〗-device shows that its door is still open.
The 〖1167〗-device is not connected.
〖1168〗-the element was not found.
There are no items in the 〖1169〗-index that match the specified item.
〖1170〗-the specified set of properties does not exist on the object.
〖1171〗-the point passed to GetMouseMovePoints is not in the buffer.
The 〖1172〗-Tracking (workstation) service is not running.
〖1173〗-the volume ID could not be found.
〖1175〗-cannot delete the file to be replaced.
〖1176〗-cannot move the replacement file to the file to be replaced. The file to be replaced remains the original name.
〖1177〗-cannot move the replacement file to the file to be replaced. The file to be replaced has been renamed back to the backup name.
〖1178〗-volume change record is deleted.
The 〖1179〗-volume change logging service is not active.
〖1180〗-found a file, but it may not be the correct one.
〖1181〗-log entries are removed from the log.
〖1200〗-The specified device name is invalid.
The 〖1201〗-device is not currently connected, but it is a record connection.
〖1202〗-attempts to record devices that have previously been recorded.
〖1203〗-No network provider accepts the specified network path.
〖1204〗-The specified network provider name is invalid.
〖1205〗-Unable to open the network connection configuration file.
〖1206〗-Network connection profile is corrupted.
〖1207〗-cannot enumerate empty vectors.
〖1208〗-an extended error occurred.
〖1209〗-the specified group name format is invalid.
〖1210〗-the specified computer name format is invalid.
〖1211〗-the specified event name format is invalid.
〖1212〗-the specified domain name format is invalid.
〖1213〗-the specified service name format is invalid.
〖1214〗-the specified network name format is invalid.
〖1215〗-the specified share name format is invalid.
〖1216〗-The specified password format is invalid.
〖1217〗-the specified message name format is invalid.
〖1218〗-the specified message destination format is invalid.
The credentials provided by 〖1219〗-conflict with the set of credentials that already exist.
〖1220〗-attempted to create a session for a network server, but too many sessions have been created for that server.
〖1221〗-workgroup or domain name has been used by another computer on the network.
The 〖1222〗-network is not connected or started.
The 〖1223〗-operation has been canceled by the user.
〖1224〗-requested operation cannot be performed on a file opened using the user mapping area.
〖1225〗-the remote system denies the network connection.
The 〖1226〗-network connection has been properly shut down.
The 〖1227〗-network transport endpoint already has an address associated with it.
The 〖1228〗-address is still not associated with the network endpoint.
〖1229〗-attempts to operate on a network connection that does not exist.
〖1230〗-an attempt to perform an invalid operation on a network connection that is in use.
〖1231〗-cannot access network locations. For information about network troubleshooting, see Windows Help.
〖1232〗-cannot access network locations. For information about network troubleshooting, see Windows Help.
〖1233〗-cannot access network locations. For information about network troubleshooting, see Windows Help.
〖1234〗-No service is operating on the destination network endpoint on the remote system.
The 〖1235〗-request was terminated.
〖1236〗-The network connection is terminated by the local system.
The 〖1237〗-operation could not be completed. Should try again.
〖1238〗-cannot connect to the server because it has reached the maximum simultaneous connection limit for this account.
〖1239〗-attempted to log in within a time when the account was not authorized.
〖1240〗-This account does not have authorization to log on from this workstation.
The 〖1241〗-requested operation cannot use this network address.
The 〖1242〗-server is already registered.
〖1243〗-The specified service does not exist.
〖1244〗-The requested action cannot be performed because the user has not been authenticated.
〖1245〗-The requested action cannot be performed because the user is not logged on to the network. The specified service does not exist.
〖1246〗-is continuing to work.
〖1247〗-attempted an initial operation, but initialization is complete.
〖1248〗-no more local devices.
〖1249〗-The specified site does not exist.
〖1250〗-a domain controller with the specified name already exists.
〖1251〗-This operation is supported only if you are connected to the server.
〖1252〗-The Group Policy framework should call the extension even if there are no changes.
〖1253〗-The specified user does not have a valid configuration file.
〖1254〗-microsoft Small Business Server does not support this operation.
〖1300〗-not all the referenced privileges are assigned to the calling party.
Some mappings between the 〖1301〗-account name and the security ID were not completed.
〖1302〗-does not specifically set system quota limits for this account.
The 〖1303〗-does not have an encryption key available. A known encryption key was returned.
The 〖1304〗-password is too complex to be converted to the LAN Manager password. The LAN Manager password returned is an empty string.
〖1305〗-revision level is unknown.
〖1306〗-indicates that the two revision levels are incompatible.
〖1307〗-This security ID cannot be assigned to the owner of this object.
〖1308〗-This security ID cannot be assigned as the primary group of the object.
〖1309〗-currently does not impersonate the customer's thread attempting to manipulate the impersonation token.
The 〖1310〗-group may not be disabled.
〖1311〗-currently does not have a logon server available to service logon requests.
〖1312〗-the specified logon session does not exist. may have been terminated.
〖1313〗-The specified privilege does not exist.
The 〖1314〗-customer does not have the required privileges.
The name provided by 〖1315〗-is not the correct account name form.
〖1316〗-The specified user already exists.
〖1317〗-The specified user does not exist.
〖1318〗-The specified group already exists.
〖1319〗-The specified group does not exist.
〖1320〗-The specified user account is already a member of the specified group, or the specified group cannot be deleted because the group contains members.
〖1321〗-The specified user account is not a member of the specified group account.
〖1322〗-cannot disable or remove the last remaining system administration accounts.
〖1323〗-cannot update password. The value provided as the current password is incorrect.
〖1324〗-cannot update password. The value provided to the new password contains a value that is not allowed in the password.
〖1325〗-cannot update password. The value provided for the new password does not conform to the length, complexity, or historical requirements of the word value field.
〖1326〗-Logon failure: Unknown user name or bad password.
〖1327〗-Logon Failure: User account limit.
〖1328〗-Logon Failure: Violation of account logon time limit.
〖1329〗-Logon Failure: The user is not allowed to log on to this computer.
〖1330〗-Logon Failure: The specified account password has expired.
〖1331〗-Logon Failure: Disables the current account.
There is no mapping between the 〖1332〗-account name and the security ID.
〖1333〗-a request for too many local user identifiers (LUIDs) at a time.
〖1334〗-There are no more local user identifiers (LUIDs) available.
〖1335〗-for this particular usage, the secondary authorization portion of the security ID is invalid.
The 〖1336〗-access Control List (ACL) structure is invalid.
The 〖1337〗-security ID structure is invalid.
The 〖1338〗-security descriptor structure is invalid.
〖1340〗-cannot create an intrinsic access control List (ACL) or access control entry (ACE).
The 〖1341〗-server is currently disabled.
The 〖1342〗-server is currently enabled.
The value that 〖1343〗-provides to the identification designator authority is an invalid value.
〖1344〗-no more memory available to update security information.
〖1345〗-The specified property is invalid or incompatible with the properties of the entire group.
The impersonation level specified by 〖1346〗-is invalid, or the provided impersonation level is invalid.
〖1347〗-cannot open an anonymous level security token.
The validation information category for the 〖1348〗-request is invalid.
The type of the 〖1349〗-token is inappropriate for the method it is trying to use.
〖1350〗-cannot run security operations on objects that are not associated with security.
〖1351〗-failed to read configuration information from the domain controller, either because the machine is not available or the access is denied.
The 〖1352〗-Security Account Manager (SAM) or local Security Authority (LSA) server is in an error state that is running a security operation.
The 〖1353〗-domain is in an error state that is running a security operation.
〖1354〗-This operation is only feasible for the domain's primary domain controller.
〖1355〗-The specified domain does not exist or cannot be contacted.
〖1356〗-The specified domain already exists.
〖1357〗-attempts to exceed the limit of the number of domains per server.
〖1358〗-cannot complete the request operation because of a critical media failure on disk or a corrupted data structure.
〖1359〗-An internal error has occurred.
The 〖1360〗-generic access type is contained in an access mask that is mapped to a non-generic type.
The 〖1361〗-security descriptor is malformed (absolute or self-related).
The 〖1362〗-request operation is restricted to use in the logon process only. The calling process is not registered as a logon process.
〖1363〗-cannot start a new session with an identity that is already in use.
〖1364〗-The specified authentication packet that is unknown.
The 〖1365〗-logon session is not in a state that is consistent with the requested operation.
The 〖1366〗-logon session ID is already in use.
The 〖1367〗-login request contains an invalid login type value.
〖1368〗-cannot be emulated through this pipeline until it is read with a named pipe.
The transaction state of the 〖1369〗-registry subtree is inconsistent with the request state.
There was a corruption inside the 〖1370〗-security database.
〖1371〗-cannot run this operation on a built-in account.
〖1372〗-cannot run this operation on a built-in special group.
〖1373〗-cannot run this operation on a built-in special user.
〖1374〗-cannot remove a user from a group because the current group is the primary group for the user.
The 〖1375〗-token is used as the primary token.
〖1376〗-The specified local group does not exist.
〖1377〗-The specified account name is not a member of the local group.
〖1378〗-The account name specified is already a member of the local group.
〖1379〗-the specified local group already exists.
〖1380〗-Logon Failure: The user is not granted the requested logon type on this computer.
〖1381〗-has exceeded the maximum number of secrets that can be saved in a single system.
The length of the 〖1382〗-secret exceeds the maximum allowable length.
〖1383〗-The local Security Authority database contains inconsistencies internally.
〖1384〗-in the process of attempting to log in, the user's security context accumulates excessive security identities.
〖1385〗-Logon Failure: The user is not granted the requested logon type on this computer.
〖1386〗-requires a cross-encrypted password when changing a user's password.
〖1387〗-a member cannot be added to a local group because the member does not exist, nor can it be deleted from a local group.
〖1388〗-cannot join a new member to a local group because the member's account type is incorrect.
〖1389〗-has specified too many security identities.
〖1390〗-requires a cross-encrypted password when changing this user password.
〖1391〗-indicates that the ACL does not contain any inheritable components.
〖1392〗-file or directory is corrupt and cannot be read.
〖1393〗-the disk structure is corrupt and unreadable.
〖1394〗-no user session entry for any specified logon session.
〖1395〗-the service being accessed has a connection number target authorization limit. It is no longer possible to connect at this time because the maximum acceptable number of connections has been reached.
〖1396〗-Logon failure: The target account name is incorrect.
〖1397〗-Mutual authentication failed. The server's password on the domain controller expires.
〖1398〗-There is a time difference between the client and the server.

Getlasterror,windows API Call Error when you use this function to view errors