Error codes

This article lists the error codes that Starcounter uses, along with their severity and descriptions of what they mean.
Categories
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.
Error Codes
Category
Code
Name
Description
0
999
ScErrUnspecified
An unspecified error caused the operation to fail.
1000
1001
ScErrBadArguments
One or more arguments was invalid.
1000
1002
ScErrCodeNotEnhanced
Code not enhanced.
1000
1003
ScErrOutOfMemory
Operation failed because needed memory couldn't be allocated.
1000
1004
ScErrThreadNotAttached
The operation failed because the current thread wasn't attached to the scheduler.
1000
1005
ScErrNotSupported
The requested operation is not supported on the specific object.
1000
1006
ScErrNotAWorkerThread
The operation failed because the calling thread isn't a worker thread.
1000
1007
ScErrThreadNotDetached
The operation failed because the current thread was attached to the scheduler and detached thread was expected.
1000
1008
ScErrThreadYieldBlocked
The operation failed because it required the thread to yield but yield was blocked.
1000
1009
ScErrCounterMismatch
Generic error code for counter mismatch.
1000
1010
ScErrCounterOverflow
Generic error code for counter overflow.
1000
1011
ScErrStackOverflow
A stack overflow has been detected.
1000
1012
ScErrWaitTimeout
The wait timed out before the object was signaled.
1000
1013
ScErrMaxThreadsReached
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
ScErrCantCreateUuid
Failed to generate an UUID.
1000
1016
ScErrMutexNotOwned
Operation failed because of an attempt to release ownership of a mutex not owned by the current thread.
1000
1017
ScErrWouldBlock
A non blocking operation failed because if would be required to block.
1000
1018
ScErrUnresposiveThreadStall
A cooperatively scheduled worker thread has been unresponsive for an unacceptably long period of time.
1000
1019
ScErrThreadsBlockedStall
All threads available to the scheduler has been blocked for an unacceptably long period of time.
ScErrCodeNotEnhanced, 1002
Runtime error occuring when accessing code that needs to be enhanced in order to work, but for some reason hasn't.
ScErrThreadNotAttached, 1004
This can either indicate that the thread is temporarily detached from the scheduler or that it isn't a worker thread. Only certain operations differs between the two.
ScErrMaxThreadsReached, 1013
This error can occur when a large number of worker threads are blocked.
ScErrUnresposiveThreadStall, 1018
A cooperatively scheduled worker thread is considered unresponsive when it hasn't yielded for more then a minute but this error isn't generated unless the thread has been unresponsive for a user configured period of time (2 minutes by default). If a thread is detected to be unresponsive but not long enough for the error to be generated, a warning is generated instead. The error is likely caused by an infinite loop or a deadlock but could also be caused by the thread doing something that doesn't give it the opportunity to yield for a very long period of time (which also is a real problem since the stall timeout is configured in minutes).
ScErrThreadsBlockedStall, 1019
The error is likely an indication of a deadlock or a highly contested lock held for a very long period of time.
ScErrTaskCleanupIncomplete, 1020
Error currently only raised when exclusive environment ownership hasn't been released when task terminated. This should not occur.
ScErrOperationCancelled, 1034
General error code representing a cancelled operation.
ScErrBadBaseDirectoryConfig, 2002
Applies if the specified directory doesn't exists or is invalid (for example if the specified path indicates a file), or if a base directory isn't specified when one is required.
ScErrBadTempDirectoryConfig, 2003
Applies if the specified directory doesn't exists or is invalid (for example if the specified path indicates a file).
ScErrBadImageDirectoryConfig, 2004
Applies if the specified directory doesn't exists or is invalid (for example if the specified path indicates a file), or if a image directory isn't specified when one is required.
ScErrBadTLogDirectoryConfig, 2005
Applies if the specified directory doesn't exists or is invalid (for example if the specified path indicates a file), or if a transaction log directory isn't specified when one is required.
ScErrLogModuleNotFound, 2014
Most likely caused by a faulty installation.
ScErrCantGetPrivilegesNeeded, 2018
This error code is obsolete in current version.
ScErrDatabaseFileMismatch, 2022
This means that one of the image files, the transaction log or all three files were created for different databases.
ScErrCodeLoaderError, 2027
General error produced by the code loader component. This error indicates that an operation during startup requiered some code to be accessed via the .NET reflection engine and that the loader cound not satisfy the request because of an error fetching the needed data. This usually indicates version mismatches or missing pe-files in the runtime library. The error lines up with one (or several) more specific errors. The later contains more detailed information about what specific code that couldnt load and can be found in the error log. This error ends up in the critical log (causing the database to fail startup). A corresponding and more specific error at the same time is written to the error log, describing what assembly failed and how to get even more error information.
ScErrTypesLoadError, 2029
The code loader requested to iterate types in a given (loaded) assembly, but this operation resulted in an error. This usually indicates some kind of reference error where one assembly or module references (direct or indirect) a type that was implied for the former to load properly. Results in a code loader error in the critical error log. See about this above. In companion with this error, Starcounter writes out what assembly failed to load. This might be enough for the developer, but if it isn't, even more information is availible. To get this additional and extended error information, the error in the error log comes equipped with a reference number (in the form of a GUID). This reference number can be used to find the information lining up with the given exception. To search for this information by reference, consult the Starcounter.Notice log. In the complementary log the following can be found:
Number of types declared in the failing assembly, and how many of these that wheren't possible to load.
Which of the above types that was possible to load (and from that, it should be clear which ones could not)
The full set of assemblies currently loaded into the database.
Exception messages (including file name of the target) for each type in the faulty assembly, indicating the broken link.
Fusion log for each exception message above.
ScErrWeavingError, 2030
All specific weaver related errors use this general weaving error as an umbrella to communicate their existence to the user. That is, this general weaving error will be found in the critical logging branch of errors and all specific errors will be found in the extended error logging system (the error log). When this error is found in the critical error log, consult the error log for a corresponding ScErrWeavingFailed error. That error will head a list of more specific errors that are the real source for this error.
ScErrInvalidServerName, 2031
Indicates that the specified server name is to long (a server name is currently limited to 31 characters) or contains invalid characters.
ScErrShutdownTimedOut, 2032
The shutdown thread got stuck in user code and was aborted.
ScErrBadSchedCountConfig, 2035
Indicates that the configured number of virtual CPUs wasn't supported. Currently no more than 4 virtual CPUs is supported in the x64 version and no more then a 1 virtual CPU is supported in the x86 version.
ScErrWrongTLogVersion, 2036
The transaction log file is versioned and must match the version of the loading transaction logging runtime library when the database is started. If versions differ, this error will be in the error log and the database will fail to load.
ScErrBadRebuildConfig, 2037
Configuration given for either an unload operation or a reload counterpart violated some constraint. What type of operation (unload/reload) the error originated from will be indicated by the context, a parachute error for respective routine. In current version, all configuration is done internally so this error should not occur. In previous versions it could occur because of bad settings in configuration for unload/reload.
ScErrModuleNotFound, 2048
Most likely caused by a faulty installation.
ScErrParsingAppArgs, 2049
Consult the system error code to find out more about what failed.
ScErrTooFewAppArgs, 2050
Consult the documentation to see what arguments Starcounter encforces, accepts and what constraints apply.
ScErrAppArgsSemanticViolation, 2051
Consult the documentation to see what arguments Starcounter encforces, accepts and what constraints apply.
ScErrFuncExportNotFound, 2054
Most likely caused by a faulty installation.
ScErrBadBackupDirectoryConfig, 2055
Backup directory is currently the same as output directory.
ScErrTLogNotInitialized, 2058
The transaction/redo log is considered uninitialized after it has been created and before it has successfully been started at least once.
ScErrAcquireDbControlTimeOut, 2059
Error occurs if unable to acquire the shared object used to control ownership of the database environment on startup. Could indicate that the memory manager is unresponsive (scdata.exe). Try again after terminating this process.
ScErrCreateActMonBufTimeOut, 2060
Error occurs if unable create activity monitor shared buffer timed out. Could indicate that the activity monitor is unresponsive (scactmon.exe) and has therefore not released the buffer. Try again after terminating the process.
ScErrDbStateAccessDenied, 2061
Check so that the user that runs the database or server has the priviledge to create/open globally named objects, "SeCreateGlobalPrivilege". Corresponds to windows error ERROR_ACCESS_DENIED.
ScErrClientBackendAlreadyLoaded, 2064
When the client runtime was trying to load the library that communicates with Starcounter databases, a library with the same name ("sccoredb") was found already loaded.
ScErrClientBackendNotLoaded, 2065
When the client runtime was trying to load the library that communicates with Starcounter databases, the library was not found loaded after initialization.
ScErrClientBackendWrongPath, 2066
When the client runtime was trying to load the library that communicates with Starcounter databases, the library was found loaded from the wrong path.
ScErrStartSharedMemoryMonitor, 2067
Shared memory monitor process is started by each Starcounter server and is used to correctly free clients' shared memory resources.
ScErrDbOpenMonitorInterface, 2088
If there is no monitor (scipcmonitor.exe) running in the same terminal server session as the database process, this is likely the cause of the error. If the database is to be started in session 0, it may help to start the Starcounter System Server service. If the database is to be started in session 1, it may help to start the Starcounter Administrator.
ScErrBadSchedIdSupplied, 2106
You can queue a job on scheduler with id from 0 to n-1, where n is a number of logical processors in the system.
ScErrBadDatabaseConfig, 2109
Generic error indicating that the configuration of a database is invalid preventing the database from being accessible.
ScErrStartNetworkGateway, 2110
Network gateway process is started by each Starcounter server and is used to provide communication for Starcounter with outside world.
ScErrBadServiceConfig, 2113
The service configuration file doesn't exist, isn't accessible or isn't formatted correctly.
ScErrBadServerConfig, 2115
The server configuration file doesn't exist, isn't accessible or isn't formatted correctly.
ScErrApplicationAlreadyHosted, 2151
This error usually indicate an app tries to start a host when the app is is either already running in the shared host, or has already started the host previously.
ScErrInvalidHandle, 3001
Usually implies that the object referenced by the handle has been freed.
ScErrBadChannelOptionValue, 3003
Error is raised when configuring a channel. This is usually done using values from named port configuration (I/O handler configuration) but if so, configuration should already have been validated and this error should not occur.
ScErrChannelReading, 3011
A new read operation can not be posted and certain options can not be set until the operation has completed.
ScErrConnectionRefused, 3013
This is usually the result when communication could be established with the remote system but the current system wasn't excepted as a client. An example is when trying to connect to a specific port and address and the addressed system was found but no one was accepting connection requests on that port.
ScErrEndPointInvalid, 3014
Operation failed because the channel couldn't be bound to the specified end point since it wasn't a valid end point.
ScErrEndPointOccupied, 3015
Operation failed because the a channel couldn't be bound to the specified end point since it already was occupied.
ScErrEndPointUnreachable, 3016
A connection couldn't be established because the specified end point couldn't be reached. When this error occurs it's probably because the current machine isn't connected to a network or only connected to a local network.
ScErrUnwritableMessage, 3021
This error occurs when trying to write a message containing 0 value bytes when 0 bytes is used as message terminator.
ScErrUnreadableMessage, 3024
Operation couldn't be completed because the contents of a message being read from by a channel couldn't be interpreted by the channel. Indicates that a message of an invalid format was passed to the process. The channel is closed when this error is detected since the input stream must be considered corrupted.
ScErrCantCreateProcessShare, 3026
Another process holds the memory file open. Could be a conflict with a client application reading server statistics although if the client application is properly implemented this is highly unlikely. In this case the issues should be resolved by trying again to start the server.
ScErrStringHeapOutOfSpace, 4002
String heap is used to store type and field names in the kernel. The maximum string heap size if fixed so the only way to resolve this is reduce the number of types and fields store in the database.
ScErrNoTransactionAttached, 4003
Operation failed because no transaction was attached to the thread when the operation only could be executed within the context of a transaction (this applies to most database operations). Note that this error can occur even if the transaction isn't activly detached from the running thread, should another thread force-claim the ownership of the transaction (by for example committing or rolling back the transaction).
ScErrCantCreateSchema, 4009
Indicates that schema creation failed. The reason why schema creation failed is logged before the error is raised.
ScErrDeletePending, 4016
If this error occurs it indicates a bug in the managed binding.
ScErrNoTransRefToRelease, 4022
Probably indicates that the reference counter is out of sync.
ScErrToManyTransactionRefs, 4024
Only a limited number of references can be registered (the reference counter is a 16-bit integer).
ScErrCantOpenImageFile, 4028
The most likely case of this error is that the image file does not exists in the configured director or is locked by another process. The reason for why the image file couldn't be opened is logged seperatly.
ScErrCantReadImageFile, 4029
The reason for the failure is logged seperatly."
ScErrCantWriteImageFile, 4030
The reason for the failure is logged seperatly."
ScErrTransactionLockedOnThread, 4031
Transaction failed because the current transaction was locked on the thread. This error occures if trying to change the current transaction of modify the state of the current transaction in a context where this isn't allowed (for example when executing a trigger).
ScErrErrorInHookCallback, 4034
This error code is for example set when there is an error in a commit hook which in turn causes the commit to fail.
ScErrPluginCodeViolation, 4036
This could either be a declarative violation or one what was caused during runtime due to a callback function that let an exception slip loose. Individual codes for plugin violations are logged separatly; this is the common error that is propagated to user code.
ScErrPluginInvocationException, 4038
Note that errors occuring due to the runtime (code access for ex) should be treated separatly if possible.
ScErrInvalidHookTarget, 4039
Hooks that implements custom filtering of targets must obey the constraints of targets as specified by the hooking documentation.
ScErrTransactionAlreadyBound, 4040
Indicates an attempt to attach a transaction to a thread when the transaction is already attached to another thread.
ScErrWeavingFailed, 4041
Information error connecting a sample of errors (always at least one) that is the cause of a general weaver error. Weaving errors use a reference approach, meaning that this error will inform the user about a unique reference that can be used to connect all errors and notices that are the underlying source for this error. With that reference it will be easy to find out more specific error information, assisting in correcting the problems that was discovered.
ScErrMissingDefinition, 4042
During schema deviation detection, a violation was found, indicating that the deployed database application code structure was different than the metadata found in the core. To remedy this symptom, a database rebuild must be performed.
ScErrRefForbiddenUserCode, 4043
Maps to ATV01
ScErrIllegalAttributeAssign, 4044
Illegal field assignment. This error will be the result of user code assigning a construct in Starcounter that doesnt allow explicit assignment. Examples includes reference lists and sequence number fields. (Maps to ATV03)
ScErrDbClassCantBeGeneric, 4046
Maps to DCV01.
ScErrIllegalFinalizer, 4047
Maps to DCV02.
ScErrIllegalTypeRefDecl, 4048
This name has been reserved by Starcounter. (Maps to DCV03)
ScErrToComplexCtor, 4049
The "initialization" part of the constructor (i.e., the part before the base constructor is called) should be simple enough:
May not declare lexical scopes (impossible in C#)
May not declare exception handlers (impossible in C#)
May not contain branching instructions (like constructs <condition>? <true> : <false> in C#).
Maps to DCV04.
ScErrFieldRedeclaration, 4050
Maps to DCV06.
ScErrIllegalExtCtor, 4051
An extension class was discovered and that class declared a constructor other than the default contructor. Extension classes are not allowed to declare any other constructors than the default contructor. (Maps to ECV01)
ScErrIllegalExtCreation, 4052
Code that explicitly instantiated a Starcounter extension class was discovered. This is not allowed. (Maps to ECV02)
ScErrIllegalExtCtorBody, 4053
This is currently not allowed. Note: I can't really remember why we have this limitation? We should remove it if it's there for no particular reason. (Maps to ECV03)
ScErrExtNotSealed, 4054
Maps to ECV04.
ScErrKindWrongName, 4055
A Society Object class was discovered as a kind (by extending Something.Kind) but it was named something other than "Kind". Note: As long as we provide a tight integration with Society Objects and we validate their code constrains in modules that targets their framework, I guess it is fair to have a set of error codes for those violations as well. However, these might be considered to be removed/moved in the future. (Maps to KCV02)
ScErrKindMissingConcept, 4056
All kind classes must be declared inside a Society Object concept class. A kind was found that wasn't. (Maps to KCV03)
ScErrKindIllegalParent, 4057
A kind class belonging to concept A must be derived from the closest declared kind class of A's base concept. A class that violated this was found. (Maps to KCV04)
ScErrKindMissingCtor, 4058
A kind class must have a default constructor, either an explicit one or the one provided by the compiler. (Maps to KCV05)
ScErrKindMissingParent, 4059
Maps to KCV06.
ScErrKindWrongVisibility, 4060
Maps to KCV09.
ScErrFieldComplexInit, 4061
A persistent field was equipped with an initialization statement (for example "public int = 0;"), but the statement was to complex for the current version of the code weaver to interpret. Consult weaver documentation about what initialization constructs are supported, and watch out for later versions of Starcounter, being able to support more complex initializations. (Maps to PFV02)
ScErrFieldRefMethod, 4062
A few restrictions regarding methods with reference parameters of persistent fields currently applies. When this error occurs, look at the method signature of the target method (part of the error message) and see if it can be implemented differently until there is support for more complex field-by-reference cases in later versions of the database. For more information about this, contact Starcounter. (Maps to PFV21)
ScErrSynNoTarget, 4066
A field was declared as a synonym, but the field it was declared as a synonym for could not be located by the loader. Make sure your synonym targets are accessible as fields in the current class (or a baseclass) and that they are also persistent. (Maps to PFV06)
ScErrSynTypeMismatch, 4067
There was a mismatch between a synonym and the target it specified. A synonym target must always be assignable for the synonym field and if and of the fields are instrict fields, the type must be a perfect match. (Maps to PFV07)
ScErrSynVisibilityMismatch, 4068
When a synonym references a target in another type that its own, the synonym is not allowed to have a wider visibility than the target. (Maps to PFV08)
ScErrSynReadOnlyMismatch, 4069
When a synonym references a target in another type that its own, the synonym must be readonly if the target is readonly. (Maps to PFV09)
ScErrSynTargetNotPersistent, 4070
When a synonym references a target, the target must be a persistent field and nothing else. (Maps to PFV12)
ScErrSynPrivateTarget, 4071
When a synonym references a target, and the target is in another type, the target must never have the private visibility. (Maps to PFV20)
ScErrPersPropNoTarget, 4077
A persistent property (in a known assembly) was declared. It supplied a reference to a target database field, but that field was not found when queried for by the loader. (Maps to PPV02)
ScErrTypeNameDuplicate, 4078
A class was being discovered by the analyzer and while analyzing, the analyzer detected that a type with the same name (full name) was allready discovered. (Maps to DCV07)
ScErrObjectDoesntExist, 4083
Indicates an attempt to access an object that for some reason doesn't exist. This error is raised if accessing or attempting to modify an object that has been deleted in another transaction before the start of the current transaction. This error is also used when attempting to access removed objects that exist outside the scope of transactions (like an index) or when accessing removed entity object without any notion of transactions (applies to certain metadata functions).
ScErrAttrNoKernelField, 4085
During schema deviation detection, a violation was found, indicating that the deployed database application code structure was different than the metadata found in the core. To remedy this symptom, a database rebuild must be performed.
ScErrUnhandledTransactConflict, 4090
This error is raised by transaction scopes if they are unable to restart a conflicted transaction.
ScErrBinaryValueExceedsMaxSize, 4091
Maximum size allowed for binary data is 4080 bytes (4096 - 16).
ScErrRenameMissingSource, 4099
When specifying renaming instructions for classes and fields, Starcounter forces them to be part of the legacy schema, the one the renaming applies to. There are several probable causes for this error, all of them relating to bad specification of the previous name, and they will be listed on the documentation, helping developers understand what might have caused the error to be raised.
ScErrCantAccessImageFile, 4118
Check so that the user that runs the server has read and write access to the file and that the file isn't read-only. Corresponds to windows error ERROR_ACCESS_DENIED.
ScErrImageFileLocked, 4119
Corresponds to windows error ERROR_SHARING_VIOLATION.
ScErrCantAccessTransactionLog, 4121
Check so that the user that runs the server has read and write access to the file and that the file isn't read-only. Corresponds to windows error ERROR_ACCESS_DENIED.
ScErrTransactionLogLocked, 4122
Corresponds to windows error ERROR_SHARING_VIOLATION.
ScErrCantAccessDumpFile, 4123
Check so that the user that runs the server has read and write access to the file and that the file isn't read-only. Corresponds to windows error ERROR_ACCESS_DENIED.
ScErrDumpFileLocked, 4124
Corresponds to windows error ERROR_SHARING_VIOLATION.
ScErrReloadConstraintViolation, 4125
The log will also contain which constraint or constraints that was violated.
ScErrFileTransNotSupported, 4126
Minimum version for File transactions is 6 (Windows Vista/Server 2008).
ScErrTypeBaseDeviation, 4127
During schema deviation detection, a violation was found, indicating that the deployed database application code structure was different than the metadata found in the core. To remedy this symptom, a database rebuild must be performed.
ScErrFieldSignatureDeviation, 4128
During schema deviation detection, a violation was found, indicating that the deployed database application code structure was different than the metadata found in the core. To remedy this symptom, a database rebuild must be performed. This error code is used for deviating signatures on persistent fields declared in regular entity classes as well as in Starcounter extension classes.
ScErrSchemaDeviation, 4129
During schema deviation detection, at least one violation was found, indicating that the deployed database application code structure was different than the metadata found in the core. To remedy this symptom, a database rebuild must be performed.
ScErrExtFieldMissingCore, 4130
During schema deviation detection, a violation was found, indicating that the deployed database application code structure was different than the metadata found in the core. To remedy this symptom, a database rebuild must be performed.
ScErrIndexDeclarationDeviation, 4131
During schema deviation detection, a violation was found, indicating that the deployed database application code structure was different than the metadata found in the core. To remedy this symptom, a database rebuild must be performed.
ScErrMissingEntityClass, 4132
During schema deviation detection, a violation was found, indicating that the deployed database application code structure was different than the metadata found in the core. The reason for this error is that a class was either removed or improperly renamed. To remedy the symptom, a database rebuild must be performed.
ScErrMissingPersistentField, 4133
During schema deviation detection, a violation was found, indicating that the deployed database application code structure was different than the metadata found in the core. The reason for this error is that a field was either removed or improperly renamed. To remedy the symptom, a database rebuild must be performed.
ScErrMissingExtensionClass, 4134
During schema deviation detection, a violation was found, indicating that the deployed database application code structure was different than the metadata found in the core. The reason for this error is that an extension class was either removed, improperly renamed or was redefined to extend another class than it extended originally. To remedy the symptom, a database rebuild must be performed.
ScErrIndexDeclarationMissing, 4135
During schema deviation detection, a violation was found, indicating that the deployed database application code structure was different than the metadata found in the core. The reason for this error is that an index previously defined have been removed/renamed. To remedy this symptom, a database rebuild must be performed.
ScErrHookCallbackNotBound, 4136
During schema deviation detection, a violation was found, indicating that the deployed database application code structure was different than the metadata found in the core. The reason for this error is that either a new hook was added or that a callback on an existing hook was added. To remedy this symptom, a database rebuild must be performed.
ScErrHookCallbackNotInstalled, 4137
During schema deviation detection, a violation was found, indicating that the deployed database application code structure was different than the metadata found in the core. The reason for this error is that a hook either was removed completly, referenced another target than it was originally, or that a particular callback of such a hook was removed. To remedy this symptom, a database rebuild must be performed.
ScErrCantBackupUnexpError, 4144
The reason for why the image file couldn't be backed up is logged seperatly.
ScErrStringValueExceedsMaxSize, 4154
The maximum size is set so that it's unlikely to be exceeded. If storing a larger string is needed then it will have to be stored as a large binary. The maximum size of a string in characters is affected by contents of the string and varies between different collations. This since it's the size of the string packed that is restricted.
ScErrStringConversionFailed, 4155
This error may indicate a bug in the string formatter or data corruption.
ScErrReattachFailedBadDbState, 4158
Can occur either when processing commit hooks or a delete hook. Caused either by the thread ending the hook operation manually detached (which should not occur) or if an out of memory or similar occurs while attempting to reattach an auto detached thread.
ScErrCantInitCheckpUnexpError, 4160
The reason for why the checkpoint process could not be initialized is logged seperatly.
ScErrCommitPending, 4162
If this error occurs it indicates a bug in the managed binding.
ScErrCodeGenerationFailed, 4164
The error is usually due to a previous I/O error. If so that error will have been written to log.
ScErrDefinitionToLarge, 4170
The size of a definition depends on the number and type of attributes and the number and type indexes. Reducing the number of attributes and/or indexes might help resolve this problem.
ScErrInvalidObjectAccess, 4174
Occurs when transaction attempts to access an object that isn't accessible from the specific transaction. This could mean that the object either didn't exist when the transaction started, was deleted within the scope of the transaction or was created within the scope of another transaction not yet committed. It could also mean that the referenced object isn't accessible to the current transaction because it belongs to another container. Only simple reads generates this error. If the error is detected in a write the transaction is aborted. See ScErrInvalidObjectAccessAbort.
ScErrSchemaCodeMismatch, 4177
Occurs when, for example, a string attribute is accessed as an integer.
ScErrLoadDynamicCodeFailed, 4179
The error is usually due to a previous I/O error. If so that error will have been written to log.
ScErrPersPropWrongCoreRef, 4181
A persistent property (in a known assembly) was declared. It specified a mapping to a database field in the core, but that field was not found when the class and it's ancestors where analyzed.
ScErrToManyOpenIterators, 4182
Only a limited number of open iterators is allowed at any given time. To avoid this error be sure to close iterators (releasing the result set) when done with them and don't keep too many iterators referenced at any given time.
ScErrCantCreateDbMemoryFile, 4186
This error occurs when the memory manager was unable to create a memory file for storing database data either when loading image or expanding database memory. If the failure is caused by an OS error code is logged seperatly. The error could also occur because the maximum number of memory files kept by the memory manager has been reached. If the memory manager fails to create a memory file because it was unable to allocate sufficient memory from the OS then a ScErrOutOfMemory will be raised.
ScErrCantInitFlushUnexpError, 4190
The reason for why the checkpoint process could not be initialized is logged seperatly.
ScErrConnectInsideDatabase, 4201
Connecting to databases using Db.Connect is currently only supported from client applications. When executing inside a database, a connect is not needed since the code is implicitly connected to the running database.
ScErrClientEntityTypeUnknown, 4202
To use entity types in a client application, the client runtime must be aware of their code types. All the entity types in a given assembly is instantly known the first type one of them is referenced, as they are implicitly registering themself with the runtime. However, if a type is used in an SQL statement and has not previously been referenced by it's code type, the query will fail with this error. To remedy this, you can explicitly add the entity types in a given assembly by issuing Db.Current.EnableClientAssembly(Assembly).
ScErrClientBackendNotInitialized, 4203
This error usually indicates that a client has not successfully called Db.Connect before it used a Starcounter method that needed to access something in the database. Example of methods that can cause this error if they are called without the client first have successfully called Db.Connect is: Db.SQL, SqlResult.GetEnumerator, new T where T is an entity type.
ScErrAssemblyNotPreparedForClient, 4204
To use Starcounter binaries in a client application, the build system must prepare the code for client access during compilation. This is normally done in Visual Studio, under the project property page "Starcounter" in a Starcounter Library project. Make sure you set the "Enable access from external process" to TRUE.
ScErrBackingRetreivalFailed, 4241
A general backing retreival error, used when no more specific backing error applies. Exceptions with this error will carry more detailed information (such as postfixes describing the case, and inner exceptions) and we are strict when logging this when it occurs in a real (i.e. non-testing) context.
ScErrCantExpandTransLog, 4248
The reason for the failure is logged seperatly."
ScErrToManyIndexes, 4276
Keep in mind that this is evaluated using the total amount of indexes on a table, including inherited indexes. Create table where base table because of failure to add default index for this reason.
ScErrColumnNameNotUnique, 4277
Note that in case the table definition inherits another table definition the name of a defined column must not share the name of a inherited column.
ScErrLogWriterStillRunning, 4298
Database load can not proceed while log writer is still running and for some reason it won't shut down within an expected time frame. This could be because is stalled or because flushing pending log writes takes longer then expected.
ScErrRecordIDLimitReached, 4299
Database preconfigured maximum record ID has been reached. No more records can be inserted in the database.
ScErrTransactionLogPositionNotFound, 4301
Position passed is not found in the transaction log. Most likely appropriate transaction log files has been removed due to retention policy.
ScErrForbiddenDatabaseName, 4304
The database name must follow this [a-z,A-Z,0-9] naming scheme.
ScErrCantRunSharedAppHost, 4305
The shared app code host is managed by Starcounter and can not be explicitly executed by user code.
ScErrInvalidSessionId, 5002
The session with the id has either expired or never existed.
ScErrUnexpErrorGetDumpTmpName, 6029
Name is created using API function GetTempFileName.
ScErrUnexpErrorExecuteCompile, 6051
This error is probably due to a faulty installation. Likely the used compiler is not properly installed.
ScErrUnexpectedCompilerError, 6052
This error should not occur. Please contact Starcounter support.
ScErrSqlExportSchemaFailed, 7001
The schema file is used by external process scsqlparser.exe.
ScErrSqlDuplicatedIdentifier, 7008
Since the SQL is case insensitive such case insensitive ambiguity can not be allowed.
ScErrConstraintViolationAbort, 8001
A constraint violation is most likely caused by a bug, restarting a transaction that's aborted for this reason is therefore not advisable since it's very likely that the same error will occur again and again each time the transaction commits.
ScErrTransactionConflictAbort, 8002
Accessing an object that has been deleted before the transaction started could also cause the current transaction to abort because of a perceived conflict. This can happen if an object is accessed within another transaction then the transaction the object was fetched in and the object at that time has been deleted. The reason for this is that the database engine can't determine when the object was deleted and therefore assumes that the object existed when the transaction started because of the assumption that the reference was fetched within the current transaction. To avoid this one should only access objects fetched within the context of the current transaction is possible.
ScErrInvalidObjectAccessAbort, 8006
Occurs when transaction attempts to access an object that isn't accessible from the specific transaction. This could mean that the object either didn't exist when the transaction started, was deleted within the scope of the transaction or was created within the scope of another transaction not yet committed. It could also mean that the referenced object isn't accessible to the current transaction because it belongs to another container. Simple read operations that fails because of an invalid object access does not abort the transaction but instead generates a ScErrInvalidObjectAccess error. error.
ScErrSchemaCodeMismatchAbort, 8007
Occurs when for example a string attribute was written to as an integer. Should not occur unless there is a problem with the binding.
ScErrInconsistentCodeAbort, 8008
Occurs when for example an attribute is written as an attribute of a certain type and later read or written as an attribute of a different type.
ScErrCodeConstrViolationAbort, 8014
This is most likely due to a bug in database binding, not in user code.
ScErrServerNotRunning, 10003
This error is used when a management client, such as star.exe, can not communicate properly with the admin server and decide it is because the admin server process is not running. See also: ScErrServerNotAvailable
ScErrServerCommandFailed, 10011
This error is used as a general error for all server commands that don't provide a custom, more specific one. Example message when expanded: "The operation "Starting database 'MyDatabase'" failed.".
ScErrUnexpectedCommandException, 10016
The server detected that a command failed with an exception that was not an exception based on a Starcounter error code (and hence unexpected). The exception details are logged along with this error. Example message when expanded: "Starting database 'MyDatabase' failed due to an unexpected problem".
ScErrExecutableNotFound, 10019
Error used mainly by the server library when asked to run an executable and the executable file could not be found where specified. The error message should include the full path used (if possible).
ScErrServerNotAvailable, 10020
This error is used when a management client, such as star.exe, can not communicate properly with the admin server and the exact reason why doesn't map one to one to any other, more specific Starcounter error (such as ScErrServerNotRunning). When constructing and logging/showing an error message based on this code, make sure to supply more low-level, detailed info such as socket level error codes, etc, to make support for this easier. See also: ScErrServerNotRunning
ScErrCommandPreconditionFailed, 10023
This error allows server command processors to report about a condition failing to be met based on a given fingerprint. The server design for fingerprint matching is closely related and largely influenced by the HTTP Etag- and conditional invocation concepts and hence, this error can be considered the equivivalent to HTTP status 412.
ScErrDatabaseEngineNotRunning, 10024
Indicates a management operation was attempted but could not succeed because the database engine was not running, as expected too.
ScErrExecutableAlreadyRunning, 10025
Indicates an executable is already loaded in a certain database engine and that state was considered worth reporting as an error.
ScErrDatabaseRunning, 10031
Indicates a management operation was attempted but could not succeed because the database was running. The operation might succeed if the database is first stopped, and the operation is issued again.
ScErrWeaverFileNotFound, 12008
Occurs when the weaver executable is given a file that can not be found.
ScErrWeaverFileNotSupported, 12009
Occurs when the weaver executable is given a file with an extension that is not supported.
ScErrDebugFailedConnectToServer, 12010
Occurs when the Visual Studio extension runs the debugging sequence, in order to debug a Starcounter module, and the server (i.e. Starcounter Administrator) does not answer to the request being sent over the pipe. Usually indicates that the server is not running.
ScErrDebugFailedServerErrorStarting, 12011
Occurs when the Visual Studio extension runs the debugging sequence, in order to debug a Starcounter module, and the server (i.e. Starcounter Administrator) reports an error in response to the request to weave and host the module inside the user code process.
ScErrDebugFailedReported, 12012
Used internally to communicate the failure of the debug sequence using an exception. Indicates the debug sequence has failed, but that the raising component has logged detailed error messages to the error list and hence, no such action must be taken by the catching party.
ScErrDebuggerAlreadyAttached, 12013
Indicates the debugging of a Starcounter application failed b/c attaching the debugger was not possible, since a debugger was already attached to the database code host process the about-to-be-debugged application targets.
ScErrDebugDbHigherPrivilege, 12014
To resolve this, either restart Visual Studio and run it as an administrator, or make sure the database runs in non-elevated mode.
ScErrDebugNoDbProcess, 12015
This indicate the database process terminated in between it was started and when Visual Studio tried attaching a debugger to it.
ScErrBadGatewayConfig, 13005
The gateway configuration file doesn't exist, isn't accessible or isn't formatted correctly.
ScErrJsonPropertyNotFound, 14003
Error code used when parsing a Json document against a well-defined template and a given property name is not found in the template.
ScErrJsonValueWrongType, 14004
Error code used when parsing a Json document against a well-defined template and a given property value is not valid according to the type of the property. For example, when doing "Name":false and "Name" is a string.
ScErrJsonUnexpectedEndOfContent, 14005
Error code used when populating a typed json object using plain json as input and the end of the content is reached before the end of the json.
Failover cluster
star tool
Last modified 2yr ago
Copy link
Contents