Home > Btrieve Error > Btrieve Error 91

Btrieve Error 91


You may have a Status 12 returned and see X$FILE.DDF for the file name in your DDFs. Instead, it returns this status code, and the server-based application must retry later. 078: The MicroKernel detected a deadlock condition The application should clear all resources by aborting, ending the transaction, One possible cause of this status code is an application that continues to open additional files without closing the data files that it has already opened. The "Number of Duplicate Pointers to Reserve" field exceeds the limit for maximum number of keys. this content

This status code usually means that the MicroKernel was unable to save or restore the memory mapping register context, indicating an incompatibility with another application that uses expanded memory. 058: The The external network number must be the same for all servers on the same network. Posting Guidelines Promoting, selling, recruiting, coursework and thesis posting is forbidden.Tek-Tips Posting Policies Jobs Jobs from Indeed What: Where: jobs by Link To This Forum! If task 2 reads the record and then task 1 aborts the transaction, task 2 receives this status code when issuing the Update operation.

Pervasive Error 91

An example is shown in Figure 4. These parameters are shown below with their default values: SPX VERIFY TIMEOUT=54 SPX LISTEN TIMEOUT=108 SPX ABORT TIMEOUT=540 These three parameters (in the order listed above) have values in a 1:2:10 It was later ported to NetWare 3.0, released in 1989, as a NetWare Loadable Module (NLM).

If the solutions above do not solve the problem, contact Scala Support. Btrieve for DOS returns this status code if it receives an error from the Expanded Memory Manager. For the Create, Stat, and Create Index operations, the data buffer is not long enough to contain all the file specifications, the key specifications, and (if specified) the Alternate Collating Sequence Btrieve Error 11 The network number for each frame type must be the same on network devices connected to the same segment.

Check the validity of the filename. 035: The application encountered a directory error Either a Get Directory operation specified a drive that does not exist, or a Set Directory operation specified Btrieve Error 161 NOTE: this does not effect network rights. If the values are changed from the default settings, they should be kept in this ratio. Recover the damaged file as described in Pervasive PSQL User's Guide. 055: The application specified an invalid attribute for an AUTOINCREMENT key The data field indexed by an AUTOINCREMENT key can

Check the key buffer parameter to make sure the pathname is terminated with a blank or a binary zero. Btrieve Error 35 BSETUP.NLM Btrieve setup utility BTRMON.NLM Btrieve monitoring utility ABSTART.NCF NCF file to start Btrieve BSTOP.NCF NCF file to stop Btrieve You can view the versions of the Btrieve core components currently Register now while it's still free! Crear una cuenta Clientes DacFlex InicioProductosContabilidadLibro MayorComprobante Fiscal ( NCF )FacturaciónControl InventarioCuentas por CobrarActivos FijosBanco / ConciliaciónCuentas por PagarGenerador de reporte Query / ConsultaEstados FinancierosCotización / PedidosComprasEnsamblePresupuestoDerecho Acceso UsuarioPunto de VentasNóminaServiciosPlanes

Btrieve Error 161

An example would be: LOAD NSSMOUNT ALLSYS:ETC\INITSYS.NCF MGRSTART or BSTART Embedded spaces configuration setting is "on." "On" is the default starting with Pervasive PSQL v9. Pre-v6.x files do not support these key types. Pervasive Error 91 They indicate the length of each of the lines which follows. Btrieve Error 3006 Status code 86 is for files and status code 87 is for handles.

The reason for this behavior is the 32-bit Btrieve Requester uses the NetWare Runtime Support. news When running the DOS requester see to it that BREQNT or BREQUEST is run with the /D:4096 switch. When reading a file in ascending order according to an index path, the MicroKernel has already returned the last record in that index path. The names and functions of each of the Btrieve components can be seen in the following table. Btrieve Error 2301

Also, ensure that FILE.DDF and RELATE.DDF (if the file has RI definitions) are in the locations specified by the Working Directory option in the server configuration settings. 068: The MicroKernel cannot Change the setting to "off" if your applications do not allow embedded spaces in file names. Check the file= setting in CONFIG.NT. have a peek at these guys It is therefore necessary to use external Dictionary Definition Files (DDFs) if you want to access the data from an application using, for example, Open DataBase Connectivity (ODBC).

This error indicates that the communication session is no longer valid. Btrieve Error 2 With Btrieve for Windows NT Server Edition v6.15.445, 32 bit Windows application may return Status 2 or "MKDE Terminated with Service Specific Error 0" after running an application for an extended Note Please see our Pervasive PSQL Knowledge Base for new and updated articles on troubleshooting this status code.

So, if the intent is to move the dictionaries to another server on the same network, one way would be to delete the named database on the old server before creating

If a key has multiple segments, the duplicate, modifiable, and null attributes should be the same for each segment in the key. If doubling these timeouts does not resolve or at least reduce the frequency of the problem, there is probably a communications problem on the network causing the SPX sessions to be This status code indicates that the application attempted to expand a data file beyond the amount of disk space allocated to the file owner. Btrieve Error 20 The handle table is managed dynamically by the engine.

You attempted to include a file in continuous operation, but the file is already in continuous operation. For more information about calculating the physical record length, see Pervasive PSQL Programmer's Guide. 029: The key length is invalid The MicroKernel returns this status code for the following situations pertaining The file may be corrupt, and you must recover it. http://hammerofcode.com/btrieve-error/btrieve-error-73.php For Windows 32-bit platform users: open a command prompt and run a DOS Btrieve application.

The position block parameter must be exactly 128 bytes long. 024: The page size or data buffer size is invalid The MicroKernel returns this status code in one of the following