Error codes
This article lists the error codes that Starcounter uses, along with their severity and descriptions of what they mean.
0- Unspecified.1000- General.2000- StartupAndShutdown.3000- IO.4000- Database.5000- Session.6000- Internal.7000- Sql.8000- TransactionAbort.10000- Management.11000- Installer.12000- Development.13000- NetworkGateway.14000- Apps.15000- MetaTypes.
Category | Code | Name | Description |
0 | 999 |
| An unspecified error caused the operation to fail. |
1000 | 1001 |
| One or more arguments was invalid. |
1000 | 1002 |
| Code not enhanced. |
1000 | 1003 |
| Operation failed because needed memory couldn't be allocated. |
1000 | 1004 |
| The operation failed because the current thread wasn't attached to the scheduler. |
1000 | 1005 |
| The requested operation is not supported on the specific object. |
1000 | 1006 |
| The operation failed because the calling thread isn't a worker thread. |
1000 | 1007 |
| The operation failed because the current thread was attached to the scheduler and detached thread was expected. |
1000 | 1008 |
| The operation failed because it required the thread to yield but yield was blocked. |
1000 | 1009 |
| Generic error code for counter mismatch. |
1000 | 1010 |
| Generic error code for counter overflow. |
1000 | 1011 |
| A stack overflow has been detected. |
1000 | 1012 |
| The wait timed out before the object was signaled. |
1000 | 1013 |
| The operation failed because the maximum number of worker threads has been reached and the operation required the scheduler to create additional worker threads. |
1000 | 1014 |
| Failed to generate an UUID. |
1000 | 1016 |
| Operation failed because of an attempt to release ownership of a mutex not owned by the current thread. |
1000 | 1017 |
| A non blocking operation failed because if would be required to block. |
1000 | 1018 |
| A cooperatively scheduled worker thread has been unresponsive for an unacceptably long period of time. |
1000 | 1019 |
| All threads available to the scheduler has been blocked for an unacceptably long period of time. |
1000 | 1020 |
| A task still held resource when terminating that should have been released before the task terminated. |
1000 | 1021 |
| A cooperatively scheduled worker thread has been unwilling to yield for an unacceptably long period of time. |
1000 | 1022 |
| Use of reattach function for manually detached threads on auto detached thread. |
1000 | 1023 |
| Use of reattach function for auto detached threads on manually detached thread. |
1000 | 1024 |
| Generic error code indicating that debug verification failed. |
1000 | 1025 |
| Operation invalid for the object's current state. |
1000 | 1026 |
| Operation failed because the target input queue was full. |
1000 | 1027 |
| The method, operation or feature is not implemented. |
1000 | 1028 |
| Access to an environment variable was not permitted due to the current security settings. |
1000 | 1029 |
| The environment variable holding the path to the Starcounter installation directory was not found. |
1000 | 1030 |
| The format of the command-line was invalid. |
1000 | 1031 |
| Command-line arguments didn't match the defined syntax. |
1000 | 1032 |
| The license key used to initialize the PostSharp library was invalid. |
1000 | 1033 |
| Parsing an error message string failed due to an incorrect message format. |
1000 | 1034 |
| The operation was cancelled. |
1000 | 1035 |
| Opening the managed segment with the segment_name failed. Invalid segment or does not exist. |
1000 | 1036 |
| Could not find the chunks shared memory object. |
1000 | 1037 |
| Could not find the shared_chunk_pool shared memory object. |
1000 | 1038 |
| Could not find the common_scheduler_interface shared memory object. |
1000 | 1039 |
| Could not find the scheduler_interfaces shared memory object. |
1000 | 1040 |
| Could not find the common_client_interface shared memory object. |
1000 | 1041 |
| Could not find the client_interfaces shared memory object. |
1000 | 1042 |
| Could not find the channels shared memory object. |
1000 | 1043 |
| Failed to open a scheduler work event. |
1000 | 1044 |
| Failed to open a client work event. |
1000 | 1045 |
| Failed to open a scheduler number pool not empty event. |
1000 | 1046 |
| Failed to open a scheduler number pool not full event. |
1000 | 1047 |
| Failed to format the active databases updated event name. |
1000 | 1048 |
| Failed to convert active databases updated event name to multi-byte string. |
1000 | 1049 |
| Failed to open the active databases updated event. |
1000 | 1050 |
| The IPC monitor failed to erase a database name. |
1000 | 1051 |
| The IPC monitor trying to open segment boost::interprocess::interprocess_exception caught. |
1000 | 1052 |
| The IPC monitor trying to open segment unknown exception caught. |
1000 | 1053 |
| The IPC monitor expected database process but got client process type. |
1000 | 1054 |
| The IPC monitor expected database process but got unknown process type. |
1000 | 1055 |
| The IPC monitor is trying to register a database process but OpenProcess() failed. |
1000 | 1056 |
| The IPC monitor failed to insert database name into active databases register. |
1000 | 1057 |
| The IPC monitor failed to insert segment name into the monitor interface. |
1000 | 1058 |
| The IPC monitor failed to notify the scheduler on the given channel. |
1000 | 1059 |
| The IPC monitor failed to open the database shared memory segment and is unable to notify the clients. |
1000 | 1060 |
| The IPC monitor caught an unknown exception while trying to open database IPC shared memory segments. |
1000 | 1061 |
| The IPC monitor got an unknown proess type exit. |
1000 | 1062 |
| The IPC monitor is trying to register a client process but OpenProcess() failed. |
1000 | 1063 |
| The IPC monitor unregistration failed. The owner ID matches but not the PID. |
1000 | 1064 |
| The IPC monitor unregistration failed. The PID matches but not the owner ID. |
1000 | 1065 |
| The IPC monitor cleanup failed. Could not open the IPC database shared memory segment. |
1000 | 1066 |
| The IPC monitor was not notified. Wait failed. |
1000 | 1067 |
| Operation failed because needed memory couldn't be allocated within dedicated address space |
1000 | 1068 |
| Operation failed because limit reached on limited memory resource. |
1000 | 1069 |
| An unhandled exception was detected. |
1000 | 1070 |
| An unexpected internal error was detected. |
1000 | 1071 |
| Assertion used in a test application failed. |
1000 | 1072 |
| Operation completion pending. |
2000 | 2001 |
| A Starcounter process with the specified name is already started. |
2000 | 2002 |
| Base directory (baseDirectory) missing from config or invalid. |
2000 | 2003 |
| Temp directory (tempDirectory) missing from config or invalid. |
2000 | 2004 |
| Image directory (imageDirectory) missing from config or invalid. |
2000 | 2005 |
| The transaction log directory (transactionLogDirectory) is missing from config or invalid. |
2000 | 2012 |
| Unable to initialize the CLR. |
2000 | 2013 |
| Unable to load host environment. |
2000 | 2014 |
| The operation failed because sccorelog.dll or one of the functions it exports couldn't be loaded. |
2000 | 2015 |
| The properties of the different disk drives used to store the image files don't have compatible configuration (do they have the same sector sizes?). |
2000 | 2016 |
| The properties of the disk drive doesn't match the database image (is the disk drive is configured for a different sector size than the image is built for?). |
2000 | 2017 |
| The database files are build for a different Starcounter version and are not compatible with the current version. |
2000 | 2018 |
| Could not acquire the privileges needed for the operation to complete successfully. |
2000 | 2022 |
| Attempt to load database files from different databases was detected. |
2000 | 2023 |
| One or more of the languages the database is configured for isn't supported by the current system. |
2000 | 2027 |
| Code loder error. |
2000 | 2029 |
| Error inspecting assembly. |
2000 | 2030 |
| At least one error has been detected during weaving of the application code. |
2000 | 2031 |
| The server name is too long (max 31 chars) or contains invalid characters. |
2000 | 2032 |
| Shutdown timed out: Stuck in user code. |
2000 | 2035 |
| Too many virtual CPUs configured. |
2000 | 2036 |
| Wrong transaction log version. |
2000 | 2037 |
| Bad unload/reload configuration. |
2000 | 2043 |
| The specified transaction log size is either smaller then the minimum size, larger then the maximum size or not aligned with the disk sector size. |
2000 | 2044 |
| The specified disk sector size is not compatible with storage. |
2000 | 2045 |
| The specified new image size is smaller then the current image size. Making the image smaller is not allowed. |
2000 | 2046 |
| The specified image size is either smaller then the minimum size, larger then the maximum size or not aligned with the database block size. |
2000 | 2047 |
| A database with the specified name already exists. |
2000 | 2048 |
| The operation failed because an expected DLL module couldn't be loaded. |
2000 | 2049 |
| When parsing the application arguments to scdbs.exe, the system routine parsing it reported an error. |
2000 | 2050 |
| The number of arguments passed to scdbs.exe did not include all arguments required. |
2000 | 2051 |
| All arguments passed to scdbs.exe did not confirm to the constraints, or some of them were found incompatible. |
2000 | 2052 |
| The -unload directive specified as a server application argument can not be used when the database is empty and not initialized. |
2000 | 2053 |
| The -reload directive specified as a server application argument can not be used when the database is allready populated. |
2000 | 2054 |
| The operation failed because an expected function export from a module dependent upon was not found. |
2000 | 2055 |
| Bad backup directory config. Either the configured directory does not exist or the directory path is to long. |
2000 | 2056 |
| Bad log directory config. Either the configuration does not exist or the configured directory isn't valid. |
2000 | 2057 |
| The server was started, instructed to execute a compare of application and core schemas, and when the database was examined, the server detected it to not being bound to any previous application, i.e. containing no schema. |
2000 | 2058 |
| An operation failed due to the transaction/redo log not being initialized. |
2000 | 2059 |
| Attempt to acquire control of the database environment timed out. |
2000 | 2060 |
| Attempt to create activity monitor shared buffer timed out. |
2000 | 2061 |
| Allocating shared memory for database state failed. Access was denied. |
2000 | 2063 |
| Checksum mismatch detected in image file when image file was loaded into memory. |
2000 | 2064 |
| Client application communication library was already loaded. |
2000 | 2065 |
| Client application communication library failed to load. |
2000 | 2066 |
| Client application communication library was loaded from the wrong path. |
2000 | 2067 |
| Problems starting shared memory monitor process. |
2000 | 2068 |
| A project file the weaver engine depends on could not be found. Either it was deleted or the program hosting the weaver did not resolve its path to the correct installation directory. |
2000 | 2069 |
| The database intends to open the database shared memory parameters, but failed when trying to concatenate the database name prefix with the database name. |
2000 | 2070 |
| The database intends to open the shared memory object with the database shared memory parameters, but failed because of an illegal char in the db_data_dir_path in the psetup parameter. |
2000 | 2071 |
| The database intends to open the shared memory object with the database shared memory parameters, but failed because a wide character that cannot be converted into a multibyte character was encountered. |
2000 | 2075 |
| Failed to construct the segment name with sequence number. |
2000 | 2076 |
| The database intends to get the sequence number and append it to the segment name, but failed because a wide character that cannot be converted into a multibyte character was encountered. |
2000 | 2077 |
| The database intends to register with the monitor, but it failed because constructing the monitor interface name would result in buffer overflow. |
2000 | 2078 |
| The database intends to register with the monitor, but failed to map the monitor interface in shared memory. |
2000 | 2080 |
| The database tried to register with the monitor, but failed to acquire an owner ID. |
2000 | 2081 |
| The client intends to open the database shared memory parameters, but failed when trying to concatenate the database name prefix with the database name. |
2000 | 2082 |
| The client intends to register with the monitor, but failed because constructing the monitor interface name would result in buffer overflow. |
2000 | 2083 |
| The client tried to register with the monitor, but failed to acquire an owner ID. |
2000 | 2084 |
| The client intends to open the database shared memory segment, but failed because it is not initialized yet. |
2000 | 2085 |
| The client intends to open the database shared memory segment, but failed because constructing the name of the database shared memory segment would result in buffer overflow. |
2000 | 2086 |
| The client failed to initialize because it could not acquire a client number. |
2000 | 2087 |
| An unknown exception was thrown by the database when trying something in the call to setup during the initialization phase. |
2000 | 2088 |
| The database intends to register with the monitor, but it failed to open the monitor interface. |
2000 | 2089 |
| The database failed to create the database shared memory parameters file. |
2000 | 2090 |
| Failed to create the database shared memory parameters file. |
2000 | 2091 |
| Failed to open the database shared memory parameters file. |
2000 | 2092 |
| Failed to map the database shared memory parameters in shared memory. |
2000 | 2094 |
| Failed to open monitor interface. |
2000 | 2095 |
| Failed to map monitor interface in shared memory. |
2000 | 2096 |
| The database failed to map the database shared memory parameters in shared memory. |
2000 | 2097 |
| The client failed to open the database shared memory parameters file. |
2000 | 2098 |
| The client failed to map the database shared memory parameters in shared memory. |
2000 | 2099 |
| The database failed to open the debug file. |
2000 | 2100 |
| The database tried to unregister with the monitor, but failed to release its owner ID. |
2000 | 2101 |
| The client tried to unregister with the monitor, but failed to release its owner ID. |
2000 | 2102 |
| The database tried to register with the monitor, but failed to acquire an owner ID because a timeout occurred. |
2000 | 2103 |
| The client tried to register with the monitor, but failed to acquire an owner ID because a timeout occurred. |
2000 | 2104 |
| The database tried to unregister with the monitor, but failed to release its owner ID because a timeout occurred. |
2000 | 2105 |
| The client tried to unregister with the monitor, but failed to release its owner ID because a timeout occurred. |
2000 | 2106 |
| Trying to queue a job on scheduler with incorrect id. |
2000 | 2107 |
| The client tried to register with the monitor, but failed to acquire an owner ID because a timeout occurred. |
2000 | 2108 |
| A Starcounter database with the specified name is already started. |
2000 | 2109 |
| Invalid configuration prevents the database from being accessible. |
2000 | 2110 |
| Problems starting network gateway process. |
2000 | 2111 |
| Shared memory chunks number is missing in database configuration file or has invalid value. |
2000 | 2112 |
| The properties of the disk drive doesn't match the transaction log (is the disk drive is configured for a different sector size than the transaction log is built for?). |
2000 | 2113 |
| Service configuration is invalid. |
2000 | 2114 |
| Process was killed by process manager. |
2000 | 2115 |
| Server configuration is invalid. |
2000 | 2116 |
| Invalid Global Segment Shared Memory Object. |
2000 | 2117 |
| Unknown exception thrown during initialization of server. |
2000 | 2118 |
| Server port initialization failed, invalid shared memory object. |
2000 | 2119 |
| Server port initialization failed, invalid mapped region. |
2000 | 2120 |
| Server port initialization failed, unknown exception caught. |
2000 | 2121 |
| IPC monitor failed to create IPC monitor directory. |
2000 | 2122 |
| IPC monitor failed to start, required arguments are missing. |
2000 | 2123 |
| IPC monitor failed to format the ipc_monitor_cleanup_event_name. |
2000 | 2124 |
| IPC monitor failed to convert the IPC monitor cleanup event name to multi-byte string. |
2000 | 2125 |
| IPC monitor failed to create the IPC monitor cleanup event. |
2000 | 2126 |
| IPC monitor failed to format the active databases updated event name. |
2000 | 2127 |
| IPC monitor failed to convert active databases updated event name to multi-byte string. |
2000 | 2128 |
| IPC monitor failed to failed to create the active databases updated event. |
2000 | 2129 |
| IPC monitor invalid monitor_interface shared memory object. |
2000 | 2130 |
| IPC monitor invalid monitor_interface mapped_region. |
2000 | 2131 |
| IPC monitor OpenProcessToken() failed. |
2000 | 2132 |
| IPC monitor LookupPrivilegeValue() failed. |
2000 | 2133 |
| IPC monitor AdjustTokenPrivileges() failed. |
2000 | 2134 |
| IPC monitor failed to set SeDebugPrivilege. |
2000 | 2135 |
| IPC monitor can't create monitor active databases directory. |
2000 | 2136 |
| IPC monitor can't delete monitor active databases file. |
2000 | 2137 |
| Boost interprocess exception thrown in client_port. |
2000 | 2138 |
| Unknown exception thrown in client_port. |
2000 | 2139 |
| Unknown exception thrown in IPC monitor. |
2000 | 2140 |
| The weaver failed to load a binary user code file. |
2000 | 2141 |
| An instance of scservice is already running in the same session. |
2000 | 2142 |
| scservice tried to create a mutex named scservice_is_running_lock but CreateMutex() returned NULL. |
2000 | 2143 |
| A locally deployed strong-named assembly was detected. |
2000 | 2144 |
| Gateway workers number is missing in configuration file or has invalid value. |
2000 | 2145 |
| Sessions default timeout is missing in configuration file or has invalid value. |
2000 | 2146 |
| Application name can only contain letters, numbers and underscores. |
2000 | 2147 |
| The weaver failed to resolve a reference to an assembly. |
2000 | 2148 |
| Internal system port is missing in configuration file or has invalid value. |
2000 | 2149 |
| The application can not start because it contains at least one database class with private data. See separate errors with ID "ScErrNonPublicFieldNotExposed". |
2000 | 2150 |
| Failed to create/invoke the application host. See IApplicationHost documentation on its constraints. |
2000 | 2151 |
| Unable to start the application host because the host is already running. |
2000 | 2152 |
| The application assembly did not contain expected resource stream with schema. |
3000 | 3001 |
| The specified handle is invalid. |
3000 | 3002 |
| Attempt to release a user reference to an adapter failed because no user references was registered. |
3000 | 3003 |
| Operation to set an option failed because the value of an option couldn't be set to the specified value. |
3000 | 3006 |
| The operation couldn't be completed because memory couldn't be locked. |
3000 | 3010 |
| Operation couldn't be completed because the channel has been closed. |
3000 | 3011 |
| Operation failed because an read has been posted and pending completion. |
3000 | 3012 |
| Connection timed out because the remote party didn't respond within an acceptable abount of time. |
3000 | 3013 |
| A connection to a remote endpoint could not be established because the target system actively refused it. |
3000 | 3014 |
| Tried to bind to an invalid endpoint |
3000 | 3015 |
| The endpoint is occupied |
3000 | 3016 |
| The endpoint couldn't be reached. |
3000 | 3018 |
| Operation couldn't be completed because the listener has been closed. |
3000 | 3019 |
| Channel read operation failed because the message received was larger than allowed. |
3000 | 3020 |
| Operation could not be completed because there the limit of references to the accessed I/O adapter has been reached. |
3000 | 3021 |
| Operation couldn't be completed because the contents of the message couldn't be sent through a channel. |
3000 | 3022 |
| Connection to log server closed. |
3000 | 3023 |
| Operation failed because no option with the specified name was availible. |
3000 | 3024 |
| Received a malformed message |
3000 | 3025 |
| An operation failed because the object that only allows access by the owning thread wasn't owned by the current thread. |
3000 | 3026 |
| The memory file used to share server information already existed and the process could therefore not claim ownership of the object. |
3000 | 3027 |
| The memory file used to share server information could not be opened. Most likely an indication that the server with the specified name isn't online. |
3000 | 3029 |
| Operation could not complete because of failure to create an I/O adapter. Occurs when the maximum number of I/O adapters has been reached. |
3000 | 3031 |
| Operation failed due to insufficient disk space. |
3000 | 3032 |
| The memory file used to share server information was of an incompatible version. |
3000 | 3033 |
| A timeout occurred because the client could not push a request message to the channels in queue, because it is full. The database have not popped any request message from the channel within the timeout period. |
3000 | 3034 |
| A timeout occurred because the client could not pop a response message from the channels out queue, because it is empty. The database have not pushed any response message to the channel within the timeout period. |
3000 | 3035 |
| Database connect failed because the database was not loaded. |
3000 | 3036 |
| Not enough free shared memory. Enough memory chunks could not be acquired to hold the whole message. |
3000 | 3037 |
| Current network protocol is not used correctly. Please consult documentation for more details. |
3000 | 3038 |
| Channel is full, can't push. |
4000 | 4002 |
| No more space in string heap. |
4000 | 4003 |
| Operation must be performed in the context of a valid transaction |
4000 | 4008 |
| The specified extension is not an extension of the specific type. |
4000 | 4009 |
| Unable to create database schema |
4000 | 4011 |
| Indicates that an relation property wasn't properly declared. |
4000 | 4012 |
| The data type is not supported. The data type of a field or property in an Entity class is not supported by the database. |
4000 | 4013 |
| A type had to many attributes. |
4000 | 4016 |
| The operation failed because a delete is pending (issued but not finalized). |
4000 | 4019 |
| Instantiation of an object failed because the object wasn't a registered type. |
4000 | 4020 |
| The database is read-only. |
4000 | 4022 |
| An attempt to release an reference that wasn't registered was intercepted. |
4000 | 4024 |
| Too many references registered by the transaction. |
4000 | 4025 |
| A change in the durability of an object was requested, but the object was in a state where the durability couldn't be changed. |
4000 | 4028 |
| One of database the image files of the database could not be opened. |
4000 | 4029 |
| An error occured when attempting to read from an image file. |
4000 | 4030 |
| An error occured when attempting to write to an image file. |
4000 | 4031 |
| Can't modify the state of the transaction. |
4000 | 4033 |
| The commit hook type is properly declared (doesn't adhere to the constraints of commit hook types). |
4000 | 4034 |
| The operation failed because an error was detected in a hook callback function. |
4000 | 4035 |
| A cursor operation failed because the cursor wasn't owned by the current thread and transaction. |
4000 | 4036 |
| A violation in plugin code was detected. |
4000 | 4037 |
| A plugin type lacks a default constructor. |
4000 | 4038 |
| An exception was not handled by a plugin callback or a plugin constructor. |
4000 | 4039 |
| The target declared foor a commit hooks is not valid hook. |
4000 | 4040 |
| The transaction is already attached to another thread. |
4000 | 4041 |
| General weaver error. |
4000 | 4042 |
| An entity class in the deployed application was not part of the previously created core database schema. |
4000 | 4043 |
| User code referenced a type, field or method decorated with the HideFromApplications attribute |
4000 | 4044 |
| The field may not be explicitly assigned. |
4000 | 4046 |
| A database class was declared as a generic, which is not allowed. |
4000 | 4047 |
| A database class contained a finalizer, something currently not supported. |
4000 | 4048 |
| A database class contained a field declaration where the field was named __typeRef. |
4000 | 4049 |
| The instance initializer was too complex. Assign values inside the instance constructor instead. |
4000 | 4050 |
| A database class declared a persistent field that has already been declared in one of the parent classes. |
4000 | 4051 |
| Extension classes may only have default constructors. |
4000 | 4052 |
| May not explicitly create instances of extension classes. |
4000 | 4053 |
| The constructor in an extension class contained user code. |
4000 | 4054 |
| An extension class that wasn't declared as "sealed" was found. |
4000 | 4055 |
| A Kind class named something other than "Kind" was found. |
4000 | 4056 |
| A Kind class missing an enclosing concept class was found. |
4000 | 4057 |
| A Kind class was derived from an inappropriate base class. |
4000 | 4058 |
| A Kind class missing a default constructor was found. |
4000 | 4059 |
| Classes named "Kind" declared within Society Object concept classes must inherit its parent Kind. |
4000 | 4060 |
| Kind classes must at least have the "protected" visibility. |
4000 | 4061 |
| Too complex field initializer in entity class. Initialize it in the constructor instead. |
4000 | 4062 |
| Starcounter can't handle the reference parameters in a certain method. |
4000 | 4066 |
| A field was declared as a synonym to a non-existent field. |
4000 | 4067 |
| Mismatch between a synonym's type and the synonym's target's type. |
4000 | 4068 |
| A synonym was found that was more visible than its target. |
4000 | 4069 |
| A non-readonly synonym to a readonly field was found. |
4000 | 4070 |
| A synonym targeted a non-persistent field. |
4000 | 4071 |
| Can't declare synonyms to private fields. |
4000 | 4077 |
| Field not found. |
4000 | 4078 |
| Two classes of the same full name were found. |
4000 | 4083 |
| A transaction tried to access an object that has been deleted (or which for some reason doesn't exist). |
4000 | 4084 |
| A transaction operation failed because the transaction wasn't owned by the current virtual processor. |
4000 | 4085 |
| An entity class in the deployed application declared a field not part of the previously created core database schema. |
4000 | 4086 |
| The unload routine failed to execute. |
4000 | 4087 |
| The database reload routine failed to execute. |
4000 | 4089 |
| Context not accessible because it's owned by a scope. |
4000 | 4090 |
| The operation failed because of an unhandled transaction conflict. |
4000 | 4091 |
| Binary data exceeds maximum size. |
4000 | 4093 |
| The transaction is readonly and cannot be changed to write-mode. |
4000 | 4099 |
| A renamed token (class/field) specifies a previous name not part of the old schema. |
4000 | 4101 |
| The memory manager has terminated unexpectedly. |
4000 | 4103 |
| When reloading the database; the memory manager has detected that the image files represents another database the the one in memory, or another generation of it. |
4000 | 4104 |
| An error occured when writing to the redo log. |
4000 | 4105 |
| Reload failed because the process was unable to open the dump file. |
4000 | 4106 |
| Unable to open transaction log. |
4000 | 4107 |
| Could not expand image file. |
4000 | 4108 |
| Could not create image file. |
4000 | 4109 |
| Could not create transaction log. |
4000 | 4111 |
| The unload routine failed to execute because a dump with the specified name already exists. |
4000 | 4112 |
| When initializing the reload, the reload instruction set unexpectedly was proved invalid. |
4000 | 4113 |
| When rebuilding (dump ver 1), a known and un-recoverable error was detected. Please contact Starcounter for guidance. |
4000 | 4114 |
| Unsupported field conversion during rebuild. |
4000 | 4115 |
| Conversion overflow during rebuild. |
4000 | 4116 |
| When rebuilding, a version of the dump was not supported. |
4000 | 4117 |
| One or both of the image files are missing. |
4000 | 4118 |
| One or both of the image files aren't accessible by the process. |
4000 | 4119 |
| One or both of the image files are locked by another process. |
4000 | 4120 |
| The transaction log is missing. |
4000 | 4121 |
| The transaction log isn't accessible by the process. |
4000 | 4122 |
| The transaction log is locked by another process. |
4000 | 4123 |
| Reload failed because the dump file weren't accessible by the process. |
4000 | 4124 |
| Reload failed because the dump file was locked by another process. |
4000 | 4125 |
| The reload completed successfully but reload data violated one or more constraints. |
4000 | 4126 |
| File transactions cannot be used on this platform version. |
4000 | 4127 |
| An entity type declared a base class that did not match the base class previously bound to the core database schema. |
4000 | 4128 |
| A database type declared a persistent field that did not match the signature of the attribute in the core schema. |
4000 | 4129 |
| Schema deviations were found when comparing the deployed application to the core schema in the database. Individual deviations detected have been logged. To find these logs, use the activity ID property of this message as a reference. |
4000 | 4130 |
| An extension class in the deployed application declared a field not part of the previously created core database schema. This is caused by addition of fields, inproper renaming of fields or if the extended class of the extension was altered. |
4000 | 4131 |
| An index was declared but either not part of the core database schema or the signature of that index did not match the signature of the index in the core. |
4000 | 4132 |
| A database definition in the current core database schema have no corresponding entity class in the deployed application. |
4000 | 4133 |
| A database attribute in the current core database schema have no corresponding persistent field in the deployed application. |
4000 | 4134 |
| In the core database schema, an entity class was extended by an extension class that have no corresponding class in the deployed application. |
4000 | 4135 |
| An index was defined in the core database schema but it has no corresponding index declaration in the deployed application. |
4000 | 4136 |
| At least one commit hook part of the deployed application defined a callback that was not previously bound to the core database definition of the target being hooked. |
4000 | 4137 |
| At least one hook part of the deployed application was missing. The core keeps track of what hooks and callbacks are installed and when a core definition was inspected, a callback was previously bound but no longer part of the deployed application. |
4000 | 4139 |
| A interator operation failed because the iterator was closed. |
4000 | 4141 |
| The checkpoint image file could not be backed up because of failure to allocate needed resources. |
4000 | 4142 |
| The checkpoint image file could not be backed up because a backup with the same timestamp already existed. |
4000 | 4143 |
| The checkpoint image file could not be backed up because there wasn't enough room om the target disk. |
4000 | 4144 |
| The checkpoint image file could not be backed up as a result of an OS error. |
4000 | 4145 |
| Backup file could not be verified. |
4000 | 4146 |
| Backup file could not be found. |
4000 | 4147 |
| Backup file isn't accessible by the process. |
4000 | 4148 |
| Verification of image file against magic number failed. The file could not be identified as an image file. |
4000 | 4149 |
| Verification of backup file against magic number failed. The file could not be identified as a backup file. |
4000 | 4150 |
| When inspecting a set of physical redo log files in a multi-file transaction log setup, the server was not able to find the main redo log, indexed 0 (zero). The reason for this indicates that the main redo log file have been tampered with on the server, either it has been deleted or moved. |
4000 | 4151 |
| When inspecting a set of physical redo log files in a multi-file transaction log setup, the server found that the count expected did not match the number of redo logs found. The reason for this indicates that physical files have been tampered with on the server, usually that one of more files have been deleted or moved. |
4000 | 4152 |
| The physical redo log file referenced by the image opened was not part of the set of file identified as logs. This is most likely caused by the file being renamed or possibly deleted. |
4000 | 4153 |
| Large binary data exceeds maximum size. |
4000 | 4154 |
| String data exceeds maximum size. |
4000 | 4155 |
| An error occured when converting string to or from native format. |
4000 | 4156 |
| Search key data exceeds maximum allowed size. |
4000 | 4157 |
| Operation is only supported during schema update. |
4000 | 4158 |
| A thread detached during database operation and failed to reattach leaving the server process in an inconsistent state. |
4000 | 4159 |
| Checkpoint process could not be initialized because of failure to allocated needed resources from OS. |
4000 | 4160 |
| Checkpoint process could not be initialized because of an unexpected OS error. |
4000 | 4161 |
| Operation is not supported during schema update. |
4000 | 4162 |
| The operation failed because a transaction commit is pending (issued but not finalized). |
4000 | 4163 |
| The operation failed because the maximum size of the thread buffer was exceeded. |
4000 | 4164 |
| Code generation failed. |
4000 | 4166 |
| Index on type of specified attribute not supported. |
4000 | 4167 |
| The number of attributes specified exceeds the maximum number of attributes supported in a combined index. |
4000 | 4168 |
| No attributes specified on index creation. |
4000 | 4169 |
| Invalid sort mask specified on index creation. |
4000 | 4170 |
| The size of the defintion exceeded the maximum definition size. |
4000 | 4173 |
| String conversion failed during rebuild. |
4000 | 4174 |
| The operation failed because of an invalid object access. |
4000 | 4177 |
| Operation failed because input does not match schema. |
4000 | 4178 |
| Failed to setup dynamic code environment. |
4000 | 4179 |
| Failed to load a dynamically generated library. |
4000 | 4180 |
| An error occured when reading from the redo log. |
4000 | 4181 |
| A PersistentProperty declaration referenced a field in the core that was not found. |
4000 | 4182 |
| Too many open iterators registered with the current scheduler. |
4000 | 4183 |
| Unable to generate a name for dynamically generated library. |
4000 | 4184 |
| Operation is only allowed by a REP transaction. |
4000 | 4185 |
| Operation is not allowed by a REP transaction. |
4000 | 4186 |
| The memory manager was unable to create a memory file to store database memory. |
4000 | 4187 |
| An index with the specified name already exists. |
4000 | 4188 |
| Metadata objects cannot be deleted. |
4000 | 4189 |
| Flush process could not be initialized because of failure to allocated needed resources from OS. |
4000 | 4190 |
| Flush process could not be initialized because of an unexpected OS error. |
4000 | 4191 |
| Checksum mismatch detected in database memory on checkpoint. |
4000 | 4192 |
| Checksum mismatch detected in image file on checkpoint. |
4000 | 4193 |
| Checksum mismatch detected in image file on backup. |
4000 | 4194 |
| A new image file could not be created because a file with the specific name already exists. |
4000 | 4195 |
| The image page size does not match the page size of the executable. |
4000 | 4196 |
| The backup page size does not match the page size of the executable. |
4000 | 4197 |
| Operation failed because the output buffer was to small for the output. |
4000 | 4198 |
| Index creation failed because the specified index name was too long. |
4000 | 4199 |
| Operation failed because a transaction was attached to the thread and the operation was not allowed whtin a transaction. |
4000 | 4200 |
| Index creation failed because the specified index name was of an invalid format. |
4000 | 4201 |
| Connect failed because it was called from code running inside a database. |
4000 | 4202 |
| The SQL statement referenced a class/table whose code type was not found on the client. Missing type: "{0}". Please add the assembly defining this type using Db.Current.EnableClientAssembly(Assembly), for example using Db.Current.EnableClientAssembly(typeof({0}).Assembly).{1}SQL: "{2}". |
4000 | 4203 |
| A method call failed because the client backend was not yet established. |
4000 | 4204 |
| The assembly was not compiled/weaved for access from a client application. |
4000 | 4205 |
| The database connection string is incorrect. |
4000 | 4206 |
| The type- or extenstion binding "{0}" can not be instantiated because the code type is not known. Make sure the code type is assigned using the CodeType property. |
4000 | 4207 |
| The type- or extenstion binding "{0}" can not be instantiated because it represents a type that is declared abstract. |
4000 | 4208 |
| Unable to create a new table because the maximum number of tables would be exceeded. |
4000 | 4209 |
| Create or alter table failed because the specified table name was too long. |
4000 | 4210 |
| Create or alter table failed because the specified table name was of an invalid format. |
4000 | 4211 |
| Create or alter table failed because the specified column name was too long. |
4000 | 4212 |
| Create or alter table failed because the specified column name was of an invalid format. |
4000 | 4213 |
| Create or alter table failed because a column of a type that requires it to be nullable was not specified as nullable. |
4000 | 4214 |
| Create table failed because a table with the specified name already exists. |
4000 | 4215 |
| Connecting failed because another database is already connected. |
4000 | 4216 |
| Failed to drop a table because it has already been dropped. |
4000 | 4217 |
| The database process terminated gracefully. |
4000 | 4218 |
| The database process terminated unexpectedly. |
4000 | 4219 |
| Unknown database state. |
4000 | 4220 |
| The class is not public. Entity classes must be declared with public visibility. |
4000 | 4221 |
| The operation failed because a transaction commit is not pending. |
4000 | 4222 |
| Transaction abort could not be reset. |
4000 | 4224 |
| Wait for log writer to write log entries to disk before completing checkpoint was aborted. |
4000 | 4225 |
| Unable to write to image file because the write would expand the file and there is no space available on disk. |
4000 | 4226 |
| An unknown column type was specified when creating a table. |
4000 | 4227 |
| The operation failed because the transaction was bound to a thread. |
4000 | 4228 |
| Failed alter table because it has been dropped. |
4000 | 4229 |
| Index requested not found. |
4000 | 4230 |
| Table with specified name not found. |
4000 | 4232 |
| Table can't be altered or dropped because it is a system table. |
4000 | 4233 |
| Index can't be altered or dropped because it is a system index. |
4000 | 4234 |
| Checkpoint was aborted. |
4000 | 4239 |
| Wait for disk space to become available before completing checkpoint was aborted. |
4000 | 4240 |
| The assembly specification type was not found in the given assembly. |
4000 | 4241 |
| Unable to retrieve well-known metadata from a transformed binary. Check inner exceptions and/or logs to find more information. |
4000 | 4242 |
| The database class index backing type was not found in the given assembly. |
4000 | 4243 |
| The given .NET type was not considered a valid type specification type. |
4000 | 4244 |
| A type specification construct was missing or had an illegal signature. |
4000 | 4245 |
| Unable to drop index because at least one (not inherited) index is required on a table. |
4000 | 4246 |
| The CLR Decimal cannot be converted to a Starcounter X6 decimal without data loss. Range error. |
4000 | 4247 |
| A property in a database class can not have the same name as a public/protected field in the same class, or in a base class, not even if they differ in casing. |
4000 | 4248 |
| An error occured when attempting to expand transaction log. |
4000 | 4249 |
| Transaction log could not be expanded because a faulty log element file was found in the log directory. |
4000 | 4250 |
| Transaction log could not be expanded because of a failure to allocate disk space. |
4000 | 4251 |
| ransaction log could not be expanded because of a failure to allocate disk memory. |
4000 | 4252 |
| An error occured when initializing transaction log writer. |
4000 | 4254 |
| Transaction could not be committed because of a lack of available log space. |
4000 | 4255 |
| Transaction could not be committed because of a lack of available log space and log space can't be expanded. |
4000 | 4256 |
| Transaction log writer is not available. |
4000 | 4257 |
| Transaction log writer client library could not be loaded. |
4000 | 4258 |
| The Transient attribute is not applicable to the target code construct. |
4000 | 4259 |
| The user code entrypoint method raised an exception. |
4000 | 4260 |
| An operation failed because transaction has been closed. |
4000 | 4261 |
| A field in a database class can not have the same name as a another field in the same class, or in a base class, not even if they differ in casing. |
4000 | 4262 |
| A property in a database class can not have the same name as a another property in the same class, or in a base class, not even if they differ in casing. |
4000 | 4263 |
| Initializing fields in database classes must be done inside a constructor. Field initializers are not supported. |
4000 | 4264 |
| The application could not be resolved based on the given arguments or context. |
4000 | 4265 |
| The name of a database class field or property clashed with a name reserved by Starcounter. |
4000 | 4266 |
| Failed to execute DDL statement, since a transaction cannot be created for the execution. This can happen if the statement was called in a user-specified transaction scope. |
4000 | 4267 |
| Transaction size limit reached. |
4000 | 4268 |
| System index can't be added to a regular table. |
4000 | 4269 |
| Operation is only allowed within the context of a system transaction. |
4000 | 4270 |
| Operation is not allowed within the context of a system transaction. |
4000 | 4271 |
| Attempt to detach thread when not allowed to detach thread. |
4000 | 4272 |
| Value is undefined. |
4000 | 4273 |
| Record with specified id not found. |
4000 | 4274 |
| A type with the same name was already loaded, from a different assembly. |
4000 | 4275 |
| Unloading a table fails, since its class is not loaded. An application, where the class is declared, needs to be loaded before unload is called. |
4000 | 4276 |
| Maximum index count for table exceeded when creating index. |
4000 | 4277 |
| Create table failed because one or more columns shared the same name token as another column. |
4000 | 4278 |
| Ambiguous implicit transaction. Please put code inside a transaction scope. |
4000 | 4279 |
| Internal error: token for the given name is not found. |
4000 | 4280 |
| The [Type] attribute is not valid on the given target. |
4000 | 4281 |
| The [Inherits] attribute is not valid on the given target. |
4000 | 4282 |
| The [TypeName] attribute is not valid on the given target. |
4000 | 4283 |
| Fields/properties of this type must be declared public. |
4000 | 4284 |
| Object cannot be used as a type. |
4000 | 4285 |
| The database field was not public and no public property exist that expose it. |
4000 | 4286 |
| The transaction is already owned by someone else and cannot be claimed. |
4000 | 4287 |
| Data in the transaction is created or updated, but the transaction is not referenced and will be discarded. |
4000 | 4293 |
| Failed to connect to data manager is unavailable. Occurs when data manager is not started or not yet properly initialized. |
4000 | 4294 |
| Failed to connect to data manager because designated channel is in use. Occurs if a previous client is still connected or not yet properly disconnected. |
4000 | 4295 |
| Communication with data manager failed because data manager is unresponsive. |
4000 | 4296 |
| Communication with data manager failed because client was disconnected by data manager. |
4000 | 4297 |
| Communication with data manager failed because client is unable to understand the data manager. |
4000 | 4298 |
| Could not proceed because log writer is still running and won't shut down. |
4000 | 4299 |
| Record ID limit is reached. No more records can be inserted in the database. |
4000 | 4300 |
| Column with specified name not found. |
4000 | 4301 |
| Specified position not found in the transaction log. |
4000 | 4302 |
| Unable to allocate a handle table since the maximum number of handles tables are reached. |
4000 | 4303 |
| Illegal element for the SynonymousTo attribute. |
4000 | 4304 |
| Invalid database name. |
4000 | 4305 |
| Illegal attempt to run the shared app code host. |
4000 | 4306 |
| Only public code properties in database classes are allowed. |
4000 | 4307 |
| Database types can not declare instance fields. |
4000 | 4308 |
| The class is not abstract. Entity classes must be declared abstract. |
4000 | 4309 |
| The property is not abstract. Auto-implemented properties in entity classes must be declared abstract. |
4000 | 4310 |
| The property is not supported. Consult Starcounter documentation on declaring properties in database classes. |
4000 | 4311 |
| An attempt was made to initialize a new transaction within the scope of an active transaction. Creating such nested transactions is not supported. Consider reusing the already active transaction or running a new transaction outside the already active transaction's scope. |
4000 | 4312 |
| Invalid database class definition. Consult Starcounter documentation on declaring database classes. |
5000 | 5002 |
| Specified session id not valid. |
5000 | 5003 |
| The specific transaction is not registered with the session. |
5000 | 5004 |
| Unable to register transaction with session because the maximum number of transactions per session has already been reached. |
5000 | 5005 |
| Operations on sessions are only available from clients, not code running inside a database. |
5000 | 5006 |
| Scheduler session manager has died. |
5000 | 5007 |
| Another session for this thread is already active. |
5000 | 5008 |
| Exclusive access to the session could not be obtained. |
6000 | 6002 |
| A call to an operating system level disk access API failed to execute. |
6000 | 6003 |
| A call (other than read/write) to an operating system level file access API failed to execute. |
6000 | 6005 |
| Recovery detected the transaction log to be corrupt, recovery can't be completed. |
6000 | 6006 |
| An unexpected file I/O error occurred when writing to or reading from the image file. |
6000 | 6007 |
| An unexpected error was detected when allocating memory for the database image. |
6000 | 6008 |
| An unexpected error was detected when waiting for a waitable object. |
6000 | 6009 |
| An unexpected file I/O error occurred when attempting to open an image file. |
6000 | 6010 |
| An unexpected file I/O error occurred when attempting to read from an image file. |
6000 | 6011 |
| An unexpected file I/O error occurred when attempting to write to an image file. |
6000 | 6012 |
| An unexpected error occured when attempting to initialize a shared object. |
6000 | 6013 |
| An unexpected file I/O error occurred when attempting to create the redo log. |
6000 | 6014 |
| An unexpected file I/O error occurred when attempting to open the redo log. |
6000 | 6015 |
| An unexpected file I/O error occurred when attempting to read from the redo log. |
6000 | 6016 |
| An unexpected file I/O error occurred when attempting to write to the redo log. |
6000 | 6017 |
| An unexpected file I/O error occurred when attempting to open a dump file (SCD or SCDX). |
6000 | 6018 |
| An unexpected file I/O error occurred when attempting to read a dump file (SCD or SCDX). |
6000 | 6019 |
| An unexpected file I/O error occurred when attempting to write to dump file (SCD or SCDX). |
6000 | 6020 |
| An unexpected file I/O error occurred when attempting to expand an image file. |
6000 | 6021 |
| An unexpected file I/O error occurred when attempting to copy an image file. |
6000 | 6022 |
| An unexpected file I/O error occurred when attempting to create an image file. |
6000 | 6024 |
| The image file is corrupt. |
6000 | 6026 |
| An unexpected error occured when attempting to create a child process. |
6000 | 6027 |
| An unexpected file I/O error occurred when attempting to rename dump file from temporary to final name. |
6000 | 6028 |
| When rebuilding, verifying the dump against the magic number failed. |
6000 | 6029 |
| An unexpected error occured when creating a temporary file name for dump. |
6000 | 6030 |
| An unexpected file I/O error occurred when attempting to create dump file (SCD or SCDX). |
6000 | 6031 |
| The server can't understand the memory manager. |
6000 | 6032 |
| An unexpected error was detected when initiating or completing a channel read. |
6000 | 6033 |
| An unexpected error was detected when initiating or completing a channel write. |
6000 | 6034 |
| An unexpected error was detected when initiating or completing a channel accept. |
6000 | 6035 |
| An unexpected error was detected when initiating or completing a channel connect. |
6000 | 6036 |
| An unexpected error was detected when initiating or completing a channel close. |
6000 | 6037 |
| An unexpected error was detected when creating a listener. |
6000 | 6038 |
| An unexpected error was detected when initiating or completing a listener close. |
6000 | 6039 |
| An unexpected error was detected when opening the server file/trace log. |
6000 | 6041 |
| An unexpected OS error occurred when attempting to initialize backup process. |
6000 | 6042 |
| An unexpected file I/O error occurred when attempting to backup an image file. |
6000 | 6043 |
| An unexpected file I/O error occurred when attempting to open a backup file. |
6000 | 6044 |
| An unexpected error occurred when attempting to find the redo log(s). |
6000 | 6045 |
| An unexpected error occurred when reading the internal COUNT property of the physical main redo log. The value was 0 (zero). |
6000 | 6046 |
| The reference to the place where the next transaction should be written in the redo log, fetched from the image when loaded, was out of bounds with respect to the sector count of the given file. |
6000 | 6047 |
| An unexpected OS error occurred when attempting to initialize checkpoint process. |
6000 | 6048 |
| An unexpected file I/O error occurred when attempting to copy code generation base file. |
6000 | 6049 |
| An unexpected file I/O error occurred when attempting to open code generation file. |
6000 | 6050 |
| An unexpected file I/O error occurred when attempting to write to code generation file. |
6000 | 6051 |
| An unexpected error occurred when attempting to compile code generation output. |
6000 | 6052 |
| An unexpected error occurred was returned by the compiler when attempting to compile code generation output. |
6000 | 6053 |
| An unexpected error occurred when attempting to create directory for dynamically generated code. |
6000 | 6054 |
| An unexpected error occurred when attempting to load dynamically generated code. |
6000 | 6055 |
| An unexpected error occured when attempting to allocate a OS resource. |
6000 | 6056 |
| An unexpected error occured when attempting to release a OS resource. |
6000 | 6057 |
| An unexpected error occured when attempting set, reset or wait for an OS event. |
6000 | 6058 |
| An unexpected error was detected when creating a memory file for database data. |
6000 | 6059 |
| Checksum mismatch detected in database memory on checkpoint. |
6000 | 6060 |
| Checksum mismatch detected in image file on load. |
6000 | 6061 |
| Checksum mismatch detected in image file on checkpoint. |
6000 | 6062 |
| Checksum mismatch detected in image file on backup. |
6000 | 6063 |
| An unexpected OS error occurred when attempting to initialize image write process. |
6000 | 6064 |
| An unexpected OS error occurred when attempting to initialize image write process. |
6000 | 6065 |
| Exception occurred inside URI matcher code generator. |
6000 | 6066 |
| An unhandled, unidentified (non-Starcounter) exception occurred in the weaver. |
6000 | 6067 |
| An unexpected error occured calling a platform API function. |
6000 | 6068 |
| TupleWriter cannot write tuple, since it is too big. |
6000 | 6069 |
| An unexpected error occured in FasterThanJson library. |
6000 | 6070 |
| TupleWriter cannot safely write tuple. |
6000 | 6071 |
| Input value cannot fit the given tuple lenght. |
6000 | 6072 |
| Value is out of range of the tuple. |
6000 | 6073 |
| Unexpected error during enumerator dispose. |
6000 | 6074 |
| Unexpected error during mapping different meta-data, which represent database classes and properties. |
6000 | 6075 |
| Current network protocol is unknown. |
6000 | 6076 |
| TupleWriter cannot safely seal tuple, since not all values were written. |
6000 | 6077 |
| The weaver was unable to weave the application because of an internal problem with the weaver cache. Run the weaver with the --nocache option to remedy. |
6000 | 6078 |
| Maximum number of handlers reached. |
6000 | 6079 |
| Handler info exceeds size limits. |
6000 | 6080 |
| An internal node call returned an unexpected response. |
6000 | 6081 |
| The column is not exposed with a property, it can not be accessed. |
6000 | 6082 |
| Unexpected connect timeout. |
7000 | 7000 |
| Unexpected internal error in SQL module. |
7000 | 7001 |
| SQL module was unable to write a schema file to the current temp directory. |
7000 | 7002 |
| SQL module was unable to start external process scsqlparser.exe. |
7000 | 7003 |
| SQL module was unable to verify external process scsqlparser.exe. |
7000 | 7004 |
| External process scsqlparser.exe was unable to process the current SQL query. |
7000 | 7006 |
| Unexpected internal error in query optimization module. |
7000 | 7007 |
| Unexpected internal error in query execution module. |
7000 | 7008 |
| More than one public identifier (class name, property name etc.) with the same case insensitive representation. |
7000 | 7009 |
| Can't establish connection to specified database. |
7000 | 7010 |
| Error fetching unique SQL query identifier. |
7000 | 7011 |
| Error fetching SQL query results. |
7000 | 7013 |
| Error fetching SQL query results next page. |
7000 | 7014 |
| Error closing open SQL enumerator. |
7000 | 7015 |
| Error initializing managed SQL function pointers. |
7000 | 7016 |
| Only single object projection is allowed for SQL queries on the client. |
7000 | 7017 |
| The length of the query string exceeds the maximal length allowed. |
7000 | 7019 |
| In out of database execution offset key can be obtained only for queries with FETCH statement. |
7000 | 7020 |
| Incorrect SQL parameter/variable type. |
7000 | 7021 |
| Incorrect SQL syntax. |
7000 | 7022 |
| Not implemented SQL feature. |
7000 | 7023 |
| Not supported SQL feature. |
7000 | 7024 |
| An unexpected error occurred in unmanaged SQL parser when attempting to format message for SQL syntax error. |
7000 | 7025 |
| An unexpected error occurred in SQL Parser. |
7000 | 7026 |
| Specified name of class, property or other object name does not exist in the database. |
7000 | 7027 |
| An unexpected error occurred in scanner of SQL Parser. |
7000 | 7028 |
| Offset key is invalid for given query. |
7000 | 7029 |
| Literals are not supported in the query. |
7000 | 7030 |
| Aggregates are not supported in the query. |
7000 | 7031 |
| Expected generic result type does not match with query result type. |
7000 | 7032 |
| Too many columns for compound index. |
7000 | 7033 |
| Calling current is invalid, since enumerator has not started or has already finished. |
7000 | 7034 |
| Internal error in SQL Processor. Error cannot be retrieved. |
7000 | 7035 |
| Internal error in unmanaged meta-data population. |
7000 | 7036 |
| Internal error in native SQL processor that allocated buffer is too small. |
7000 | 7037 |
| The type is unknown. The name of the table or database class specified in the query is unknown and cannot be matched to a database type. |
7000 | 7038 |
| The column is unknown. The name of the column or property specified in the query is unknown and cannot be matched to a database column. |
7000 | 7039 |
| The type is ambiguous. The name of the table or database class specified in the query matches several database types. |
7000 | 7040 |
| Type of column value does not match actual column type. |
7000 | 7041 |
| Range error: value cannot be converted without loss. |
7000 | 7042 |
| Given SQL statement is of unexpected type. Another API function should be called. |
7000 | 7043 |
| Meta-data hasn't been created or created incompletely for this database. |
7000 | 7044 |
| Given Query ID wasn't found in cache. |
8000 | 8001 |
| A transaction was aborted because a constraint was violated. |
8000 | 8002 |
| A transaction was aborted because it was in conflict with another transaction. |
8000 | 8005 |
| The transaction was aborted because of a failure to allocate memory. |
8000 | 8006 |
| The transaction was aborted because of an invalid object access. |
8000 | 8007 |
| The transaction was aborted because pending writes didn't match the schema. |
8000 | 8008 |
| The transaction was aborted because code is inconsistent. |
8000 | 8009 |
| The transaction was aborted because of an attempt to delete a prototype. |
8000 | 8010 |
| The transaction was aborted because of a failure to allocate file storage space. |
8000 | 8012 |
| The transaction was aborted because of a failure to allocate shared storage memory. |
8000 | 8013 |
| The transaction was aborted because of an unexpected internal error. |
8000 | 8014 |
| The transaction was aborted because code constraint violation. That is, the calling code did something is wasn't supposed to. |
8000 | 8016 |
| The transaction was aborted because space could not be allocated for the transaction log entry. |
8000 | 8017 |
| The transaction was aborted because of a failure to allocate transaction log buffer space. |
8000 | 8034 |
| The transaction has been aborted by the framework because of an external event that suggested that the transaction should be considered invalid. |
8000 | 8035 |
| Transaction was aborted because of an attempt by a non-system transaction to update a system table. |
8000 | 8036 |
| The transaction was aborted because limit reached on limited memory resource. |
8000 | 8037 |
| The transaction was aborted because an invalid operation attempted left the transaction in an inconsistent state. |
8000 | 8038 |
| The transaction was aborted after being merged into another transaction. |
8000 | 8039 |
| The transaction was aborted because record generated exeeded the maximum allowed record size. |
8000 | 8040 |
| The transaction was aborted because of an attempt to create a new record layout while the limit of the number of record layouts had been reached. |
8000 | 8041 |
| The transaction was aborted because of an attempt to create a new index while the limit of the number of indexes had been reached. |
8000 | 8048 |
| The transaction was aborted because of an attempt to create a new index while the limit of the number of indexes on the specific set had been reached. |
8000 | 8049 |
| The transaction was aborted because the snapshot the transaction was referencing couldn't be maintained. |
10000 | 10001 |
| A server with the specified identity was not found. |
10000 | 10002 |
| A database with the specified name was not found. |
10000 | 10003 |
| The administrator server is not running. |
10000 | 10004 |
| Attempting to start the database failed. |