Clientes

Btrieve Errores

Btrieve Error

Pervasive Error 3000 al 3099


3001: Local access is unavailable to the MicroKernel router.


A call to the MicroKernel failed. This is most likely the result of an incorrect configuration. For example, if the MicroKernel is unavailable because of configuration settings and the file to be opened is local, then the MicroKernel router returns this status code.

3002: The MicroKernel router resource DLL is unavailable.

The MicroKernel router returns this status code when its resource DLL is either missing or incompatible with the current version of the router. If this happens, the MicroKernel reverts to its default settings and continues to run.
Check the Pervasive Event Log (PVSW.LOG) for more information.

3003: The MicroKernel router detected an incompatible network component.


The networking services component is not compatible with this version of the MicroKernel router. The most likely cause is that the Networking services DLL has been replaced by an older version.
Check the Pervasive Event Log (PVSW.LOG) for more information.

3004: The MicroKernel is not responding to the MicroKernel router.

The MicroKernel is not responding to requests from the MicroKernel router. Verify that the MicroKernel is running.

3005: The MicroKernel router encountered an operating system error.

The MicroKernel router encountered an unexpected error from the operating system, such as a shared memory failure.
Check the Pervasive Event Log (PVSW.LOG) for more information.

3006: The MicroKernel router detected an invalid session.

The session information contained in a position block is invalid. This status code occurs for one of the following reasons:

•    The application is trying to use a position block for a file that resides on an engine and for which the connection has been previously terminated via a B_STOP (25) or B_RESET (28) operation.

•    The application is trying to use a position block for a file that resides on a remote server and that encountered an abnormal network error on a previous operation.

3008: Invalid configuration for MicroKernel router.

This status code results from an invalid configuration. For example, if the Local, Remote, and Thunk options have all been set to No, the router has no valid path to take. If this happens, set one of these options to Yes, depending on your setup.

3009: NETinterface.DLL is not loaded.

The MicroKernel router could not find NETAPI.DLL.

3010: NetWare API DLLs are not loaded.

The MicroKernel router could not find the NetWare API DLLs.

3011: Thunk not possible - the Win32 MicroKernel router could not be found or is incompatible.

This status code is only relevant to the Win16 MicroKernel router. You receive this status code when the Use Thunk option is set to Yes and the thunk path is not accessible. Possible causes include:

•    The Win32 MicroKernel Router DLL does not exist or is not compatible.

•    The Win32s routines failed to initialize.

Check the Pervasive Event Log (PVSW.LOG) for more information.

3012: Local engine is not accessible to the MicroKernel router.

Access to the local engine is not possible because it is not loaded or could not be launched. You can receive this status code if you try to access a local file on a client and you do not have a MicroKernel workstation engine installed or if you try to access a local file on a server and the MicroKernel server engine is not running.

If you have only a server engine installed and your Pervasive Event Log (PVSW.LOG) contains Status Code 3012 warning entries, perform the following steps:

To Turn Off Local Engine support:

1.     Click Start, point to Programs, then to the Pervasive folder.

2.     Select Setup (Win32 or Win16).

3.     Select the MicroKernel router component.

4.     Select the Local setting and change it to Off.

5.     Select the MKDE Requester component.

6.     Select the Local Usage setting and change it to Off.

7.     Click Save and then Exit.

3013: The remote engine is inaccessible to the MicroKernel router because the networking component is not loaded.

Access to the remote engine is not possible because the MicroKernel router could not initialize the networking component. Possible causes include:

•    The Remote option is incorrectly set to No.

•    The required networking component could not be found or is not compatible.

3014: The MicroKernel router cannot find an engine.

The MicroKernel router could not complete the operation because it did not find an engine (local or remote) that could process the operation. Possible causes include:

•    The target network operating system is not available.

•    The target engine is not available.

•    In a Windows 3.x environment, you are using a shared drive name that contains a space. To resolve the condition, remove the space from the shared drive name. For example, if you connect to a server named "D Drive", change the share name to "D_Drive".

3015: The MicroKernel router encountered an initialization error.

An unexpected error occurred during the initialization of the MicroKernel router. Check the Pervasive Event Log (PVSW.LOG) for more information.

3016: The MicroKernel router encountered an internal error.

The MicroKernel router encountered an internal error. Check the Pervasive Event Log (PVSW.LOG) for more information.

3017: Data buffer of the local engine is too small.

You receive this status code when the requester has more data to send the MicroKernel than the MicroKernel’s buffers can handle. This status code is only relevant to an engine running locally; it does not apply to client/server environments. Some possible solutions include:

•    Specify a higher value for the Communications buffer size parameter in the Setup utility.

•    Use smaller buffers in Btrieve operations.

3018: The file is already closed.

You receive this status code when the MicroKernel router is shut down and is not accepting any more requests.

3019: The MicroKernel router encountered a semaphore error.

A semaphore error occurred while trying to establish contact with the local engine. Check the Pervasive Event Log (PVSW.LOG) for more information.

3020: An error occurred while loading the MicroKernel.

You receive this status code when an error occurs while loading the MicroKernel or when access to the server and client machine’s shared memory objects are unavailable.

Check the Pervasive Event Log (PVSW.LOG) for more information.

3021: The MicroKernel router received a badly formatted data packet.

The MicroKernel router rejected the response from the engine because it was badly formatted.

Check the Pervasive Event Log (PVSW.LOG) for more information.

3022: The MicroKernel router could not send the request to the remote engine because the specified data buffer length resulted in a data packet object that is too large.

A request to the MicroKernel router specified a data buffer length that resulted in a data packet size greater than 64 KB, which is the maximum. This can occur even if the data buffer length for the request is smaller than 64 KB because the MicroKernel router adds some packet overhead as it forms the data packet.

Check the Pervasive Event Log (PVSW.LOG) for more information.

3023: The task table of the MicroKernel router is full.

An internal table used by the MicroKernel router to manage tasks is full. This error should only occur in Win16 environments and indicates that a large number of applications are using the Win16 MicroKernel router at the same time.

3025 : Cannot load IDS client requester.


The MicroKernel router could not load the IDS client requester.

The IDS client requester is W3ICRxxx.DLL, where xxx is a revision number (100, 101, etc.).  The IDS client requester needs to be located in a directory listed in your PERVASIVE_PATH or PATH environment variable.

3026 : Incompatible IDS client requester.

The MicroKernel router found an incompatible IDS client requester.

The IDS client requester was found, but is a version that cannot be used by the MicroKernel router, or the file is corrupt.

3027 : Connection failure to IDS target server.

The MicroKernel router could not connect to the IDS target server.

Be sure that IDS is running on the target server.  If you are connecting to the IDS target by a host name, ensure that the name is spelled correctly and can be resolved to a TCP/IP address.  If you are connecting by a TCP/IP dotted notation address, be sure that the address is correct and accessible from the client.You can use SmartScout as a diagnostic tool.

3028 : Login failure to IDS target server.

The MicroKernel router could not login to the IDS target server.

Be sure that the user name, password, and database set name used are correct.  Some applications may prompt for this information; others may require MicroKernel Router configuration parameters to be set. See the Pervasive.SQL User's Guide or the Getting Started with I*net Data Server for more information regarding MicroKernel Router configuration parameters.

3029 : IDS Not Allowed.

This code will be returned if the path indicates an IDS request and either:

1.     the key number on the open request indicates 'local only'; OR

2.     the config setting for 'Allow IDS' == 'No'.

3030 : Remote access not allowed.


This code is returned if the path is remote, the config setting for 'Local' == 'No', and either:

1.     the key number on the open request indicates 'local only'; OR

2.     the config setting for 'Requestor' == 'No'.

Btrieve Error 116 El archivo fue tomado por otro controlador Microkernel que actúa como un Puerta de Enlace y no puede ser localizado.

Este mensaje de error indica una condición temporal en la cual no están disponibles actualmente los bloqueos de sistema. Los siguientes son casos de ejemplo:

  •     Un solo cliente esta ejecutando una transacción muy larga, en la cual miles de registros están siendo modificados.
  •     Un controlador esta configurado como una puerta de enlace permanente y el controlador no esta activado.
  •     Demasiados clientes están ejecutando largas transacciones concurrentemente.

Un cliente puede recibir este código de mensaje de error si esta o no esta en una transacción. En algunos casos, un cliente puede simplemente reintentar la operación que falló. Si otros clientes han liberado bloqueos de sistema en el intervalo, la operación reintentada puede que finalice con éxito. Si un cliente en una transacción recibe este código como resultado, finalice o aborte la transacción. Si la transacción es muy grande considere dividirla en varias transacciones. Usted también puede usar la utilidad de configurar a un número menor de bloqueos de sistema asignados a bloqueos explícitos. Para hacer eso, baje los valores asignados al Número de Bloqueos y / o opciones de configuración de Número de Sesiones.
Btrieve Error 116: The file is owned by another Microkernel engine acting as a Gateway



El MicroKernel no puede puede ponerse en contacto con el motor en la PC que esta como Gateway o puede ser localizado el archivo. Esto puede ocurrir por las siguientes razones:
  •     El nombre de la puerta de entrada de la PC no pueden ser resueltos. Para resolver este problema, pruebe uno de los siguientes: 
    • Asegúrese de que la PC puerta de enlace está registrado con su servicio de resolución de nombres, como DNS.
    • Si usted no está usando un servicio de resolución de nombres, debe proporcionar la resolución de nombres manualmente. Localizar el archivo HOSTS en su actual equipo. Añadir una línea en este archivo asociar la dirección TCP / IP de la puerta de entrada de PC con el nombre de la red de dicho equipo. Por ejemplo, si la PC puerta de entrada se llama "mycomp" y su dirección IP es 125.1.4.245, entonces usted debe agregar la siguiente línea en el Archivo C:\Windows\System32\drivers\etc\HOSTS:
            125.1.4.245 mycomp






  •     When the two computers are separated by a router so they can both see the server, but cannot see one another. Try the following:
         1. Use the Gateway Locator utility to identify the owner of the gateway.
         2. Use Pervasive System Analyser (PSA) to test the network connection to that computer.
  •     You may have attempted to open a file with two different Workgroup engines that are mapped to the files using different share names. The MicroKernel attempts to correct this, but cannot do so in all cases. Make sure each computer is mapping to the same share name.

    * fuente: http://www.pervasive.com/library/docs/psql/870/code_msg/code_msg-2-460.html

MicroKernel Status Codes for Windows and DOS Workstations

The workstation MicroKernel engine returns the following status codes in Windows and DOS environments.

1001: The lock parameter is out of range.


This status code is obsolete in MicroKernel versions 7.0 and later.
Version 6.x MicroKernels return this status code when the value specified for the Number of Locks configuration option is out of range. Pre-v6.0 MicroKernels return this status code when the value specified for the Multiple Locks configuration option is out of range.

1002: A memory allocation error occurred.

Make sure that the workstation has enough memory to load all the programs it requires. For workstation versions of the MicroKernel, or client requesters, the insufficient memory may apply to conventional memory, expanded memory, or both.

1003: An invalid memory size parameter was specified.

Ensure that the value for the Cache Allocation configuration option is large enough to accommodate the required cache size. See the Pervasive.SQL User’s Guide for more information.

1004: A page size error occurred.

This status code is obsolete in MicroKernel versions 7.0 and later.
The value of the Page Size configuration option must be an even multiple of 512, and it must be between 512 and 4096, inclusive.

1005: The pre-image or lock file drive parameter is invalid.

You must specify a valid drive letter for the Pre-Image/Lock File Drive configuration option.

Note : Pre-image files are used only for pre-v6.0 files. Lock files are used only for v6.0 and later files opened in MEFS mode.

1006: The pre-image buffer parameter is out of range.

The Extended Operation Buffer Size configuration option must be between 0 and 64,000, inclusive. Both the v6.15 and v7.0 MicroKernel return Status 1006 for this reason
The Pre-Image Buffer Size configuration option must be between 1 and 64, inclusive. The pre-image file is used in pre-v6.0 files and by v6.0 and later MicroKernels that are loaded with the Create Files in Pre-v6.x Format configuration option set to Yes.

1007: The files parameter is out of range.

For pre-v6.0 engines, the Open Files configuration option must be between 1 and 250, inclusive. For v6.0 and later engines, refer to the Pervasive.SQL User’s Guide for valid range information.

1008: The initialization parameter is invalid.

The specified configuration options contain invalid or unidentifiable values.

1009: The transaction filename parameter is invalid.

This status code is obsolete in MicroKernel versions 7.0 and later.
The filename specified for the Transaction filename configuration option is not valid. Ensure that the transaction filename is correct.

1010: An error occurred during the access of the transaction control file.

This status code is obsolete in MicroKernel versions 7.0 and later.
The MicroKernel is unable to create, open, read, or write to BTRIEVE.TRN or MKDE.TRN. Set the TRNFILE setting in the BTI.INI file to C:\.

1011: The compression buffer parameter is out of range.

The Compression Buffer Size configuration option is out of range. Refer to the Pervasive.SQL User’s Guide for valid range information.

1012: Invalid /n: option.

This status code is obsolete in MicroKernel versions 6.0 and later.
The Maximum Number Of Files In A Transaction configuration option is invalid. Valid values are 0 to 18; the default is 12.

1013: The task list is full.

In the Windows environment, this status code is returned if the task entry table is full. You can change the value for the Number of Tasks option using the Setup utility. For more information, refer to the Pervasive.SQL User’s Guide.
In the DOS environment, this status code is returned if the BREQUEST or BREQNT requesters are used without the /t parameter when BTRVID calls are present in the application. Reload the requester with a non-zero value for the /t parameter. For more information on the DOS Requester parameters, refer to Getting Started With Pervasive.SQL .

1015: One of the pointer parameters passed to the MicroKernel is invalid.

One of the pointer parameters passed into the MicroKernel is invalid. The MicroKernel checks for invalid pointers (and therefore only returns this status code) if you put the following line under the [BTRIEVE] heading in your initialization file: CHKPARMS=YES. By default, the MicroKernel performs no pointer checking.

1016: The MicroKernel is already initialized.

This status code is obsolete in MicroKernel versions 6.0 and later.
The MicroKernel returns this status code if you attempt to initialize the MicroKernel when it is already initialized. To reinitialize the MicroKernel, close all files, end/abort all transactions, and issue Btrieve operation 25, using the BTRV interface before calling the initialization function.

1017: The Btrieve Requester is unable to find the resource file WBTRVRES.DLL.


WBTRCALL.DLL returns this status code when it cannot find the resource file WBTRVRES.DLL. Place the WBTRVRES.DLL file in the same directory as the WBTRCALL.DLL file.

1018: The application attempted to call the MicroKernel from a Btrieve callback function.

The Windows MicroKernel does not allow a task to call the MicroKernel from a Btrieve callback function. You can only use the callback function with Btrieve for Windows.

1019: The MicroKernel cancelled the current Btrieve operation at the request of the application’s Btrieve callback function.


The application’s MicroKernel callback function returned a nonzero value, indicating that the application wants to terminate the current operation immediately. When the MicroKernel receives such a cancellation request, it attempts to terminate the currently executing operation and ceases to call the callback function for the duration of that operation. The MicroKernel may be unable to cancel the operation. However, if successful in doing so, the MicroKernel returns this status code.

1020: Btrieve Requester Interface communications error.

The MicroKernel loader and requester Interface returns this status code when it cannot send a message to the MicroKernel. This occurs when Windows is shutting down or when you terminate the MicroKernel using Ctrl+Alt+Delete. This is an informational status code only. No action is required. Your application continues the shutdown process. You also receive this status code when running an application that prevents Windows from processing messages.

1021: The MicroKernel failed to initialize.

The MicroKernel could not complete its initialization tasks. Check the MicroKernel’s console or error log for a message that specifies the problem that prevented the MicroKernel from initializing. The NetWare MicroKernel displays the message on the server’s system console, and it also writes the message to the Pervasive Event Log (PVSW.LOG), which is located at SYS:SYSTEM. The Win32 workstation MicroKernel displays the message in the console message window and writes the message to the Pervasive Event Log (PVSW.LOG), which is located in the C:\WINDOWS directory. The Windows NT server MicroKernel does not display a message, but writes the message in the Pervasive Event Log (PVSW.LOG), which is located in the C:\WINNT directory.

Correct the problem, using the Setup utility if necessary, then retry the operation. If you are using a NetWare MicroKernel, you must first correct the problem, then unload and reload the MicroKernel before you can retry the operation.

1022: The MicroKernel is shutting down.

The operation cannot be completed because the MicroKernel is shutting down. To correct this problem, allow the engine to completely shut down, and then restart.

Copyright © 1999 Pervasive Software, Inc..  All rights reserved. 

Btrieve Error 94 Error de Permisos


DacEasy no fue capaz de ejecutar satisfactoriamente la función debido a un error de permisos.

1. Verificar que todos los usuarios tengan acceso total a los datos y a los directorios del programa. Algunos entornos de redes le permiten garantizar o denegar ciertos tipos de accesos a directorios seleccionados. Para usar DacEasy apropiadamente, todos los usuarios de DacEasy deben tener acceso total a los datos y los directorios del programa.
2. Reiniciar el programa y ejecute otra vez la operación.
3. Pulse Reestablecer Atributos desde la caja de diálogo Respaldar/Restaurar Datos para reestablecer los atributos de los archivos.

4. Haga clic-derecho al archivo en el Explorador de Windows, y entonces, pulse Propiedades. Si está seleccionado Sólo-lectura, pulse está opción para remover este atributo.
5. Reinicie el computador que tiene residente los datos y los archivos del programa

 

Nota:

si esta usando Daceasy version 15, entonces debe

1. ir a servicio de windows menu Inicio/ejecutar/services.msc

2. seleccion el servicion "Pervasive SQL ..."

3. hacer clic en propiedad de este servicio y poner "Manual"y luego detenerlo para que no se ejectute otra al iniciar la pc.

4. fin

 



 

Dirección

Av. 27 de Febrero No. 421, Local No. 4-C-3
Plaza Dominica, El Millón
Santo Domingo, DN, RD.
809-563-3232 Tel
809-547-3967 Fax
Esta dirección de correo electrónico está siendo protegida contra los robots de spam. Necesita tener JavaScript habilitado para poder verlo.