MSIR.0197 Error opening (file or group) (name): Difference between revisions
Jump to navigation
Jump to search
m (1 revision) |
(Automatically generated page update) |
||
| Line 1: | Line 1: | ||
This message indicates that Janus could not open a file or group associated with a ''[[Janus Specialty Data Store]]'' table. This message can be issued either by the SDSUSER (the SDAEMON that holds file enqueues and loads the in-core/in-CCATEMP SDS tables) when reloading tables or starting a port (for files associated with enqueued tables) or a server thread (for unenqueued tables). In the former case, the associated table is marked as invalid and cannot be referenced in subsequent requests. In the latter case, the request fails and an error message is sent back to the client. The <var class="product">Model 204</var> audit trail immediately preceding this error should have more information as to the exact nature of the problem. | This message indicates that Janus could not open a file or group associated with a ''[[Janus Specialty Data Store]]'' table. This message can be issued either by the SDSUSER (the SDAEMON that holds file enqueues and loads the in-core/in-CCATEMP SDS tables) when reloading tables or starting a port (for files associated with enqueued tables) or a server thread (for unenqueued tables). In the former case, the associated table is marked as invalid and cannot be referenced in subsequent requests. In the latter case, the request fails and an error message is sent back to the client. The <var class="product">Model 204</var> audit trail immediately preceding this error should have more information as to the exact nature of the problem. | ||
[[Category:Sirius Mods | [[Category:Sirius Mods messages]] | ||
Revision as of 17:35, 19 April 2013
This message indicates that Janus could not open a file or group associated with a Janus Specialty Data Store table. This message can be issued either by the SDSUSER (the SDAEMON that holds file enqueues and loads the in-core/in-CCATEMP SDS tables) when reloading tables or starting a port (for files associated with enqueued tables) or a server thread (for unenqueued tables). In the former case, the associated table is marked as invalid and cannot be referenced in subsequent requests. In the latter case, the request fails and an error message is sent back to the client. The Model 204 audit trail immediately preceding this error should have more information as to the exact nature of the problem.