Ошибка в таблице аналитики btrieve 3012

  • Remove From My Forums

  • Question

  • User1088344998 posted
    I need some help connecting to a flat file. I need to force the path of the flat file and then verify the database before running the report. I’m receiving the following error:Data Object cannot be opened/accessed. Details: cannot open file DTWDATA Query
    Engine Error: 'Btrieve error status: 3012' Data Object cannot be opened/accessed. Failed to open a rowset. Error in File C:WINDOWSTEMP{2F435A92-34E8-4C81-A273-5EA5EDAEF3C7}.rpt: The table could not be found.    When I connect to my Btrieve 2000i DDF,
    it works fine. If I type in new parameters, I receive this message. I have to repoint to the DDF and then reverify the DB for it to work again within Crystal. This is why I think I need to do this. ;-) Any assistance is appreciated.

Источник

Tim Keating

Senior Member
****


DBA CLASSIC WIN 2000
C/S

Posts: 298



Re: Btrieve error 3012 and CR 8.5
Reply #1 — 12/09/04 at 10:08:57

 

Quote from aricon   on 06/01/04 at 21:10:14:

From the Pervasive Documentation:

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 (for clients and workstations only):
1. Click Start | Programs | Pervasive | Pervasive Control Center.
2. Expand Pervasive.SQL 2000i Engines and expand the desired database.
3. Expand Configuration, then expand Client, and click on Access.
4. In the right hand frame, double-click on Local, change the Current value to Off, and click OK.
5. In the right-hand frame, double-click on Requester, change the Current value to Off, and click OK.
6. In the right-hand frame, double-click Target Engine, change Current to Server only, and click OK.
7. In the left-hand frame, expand Client-16 bit and click on Access.
8. In the right-hand frame, double-click Use Local MicroKernel Engine, change Current value to Off, and click OK.
9. Make sure the Use Remote MicroKernel Engine value is set to on and that the remote engine is set to accept remote requests.
10. Exit the configuration utility and restart the engines for the new settings to take effect.

Crystal is trying to access the peer server without the MK engine being available.

Источник

This error refers to:

Unable to open PracticeWorks on one or more machines.  

Cause:

Pervasive services are not running on the server, or simply need to be restarted (even if the issue only happens on one machine and all others function fine)

Displayed message: 

«Local engine not accessible. Btrieve last code 3012 op = 0»

Most Common Solution:

1. Restart the Pervasive services by:

  1. From the server, click Start
  2. Click Run
  3. Type services.msc in the window and hit enter
  4. Right click on Pervasive PSQL Relational Engine and click Stop
  5. Right click on Pervasive PSQL Transactional Engine and click Stop
  6. Right click on Pervasive PSQL Relational Engine and click Start
  7. Right click on Pervasive PSQL Transactional Engine and click Start
  8. Close this window
  9. Open PracticeWorks

NOTE: Pervasive SQL «listens» through Port 3351 on the Server’s IP address. A static IP address is not required here, but it is helpful. If the IP on the server changes without Pervasive Services being restarted, they will still be listening on the original IP address, and workstations will not be able to find it. This is what often times causes 3012 errors, and it is why we begin troubleshooting by restarting the Pervasive Engines.

If the server is still not able to launch PracticeWorks without issue:

2. Ensure the mapped network drives are connected on all workstations (no red x’s).

  1. Open File Explorer from the taskbar or the Start  menu, or press the Windows logo key  + E.
  2. Select This PC from the left pane. Confirm the existence of a drive that points to the shared Pworks folder on the server.
  3. If the drive is not present, then on the Computer tab, select Map Network drive. 
  4. In the Drive list, select a drive letter. (Any available letter will do.)
    • Letter should match what’s expected from the current installation.
  5. In the Folder box, type the path of the folder or computer, or select Browse to find the folder or computer. To connect every time you log on to your PC, select the Reconnect at sign-in check box.
    • If manually typing the path, use the computer name, not the IP address.
  6. Select Finish.

If the issue persists, you can also check the following:

3. Check to make sure that Telnet connects.

  1. From the Workstation, go to Start > Control Panel > Programs and Features.

  2. On top left click Turn  Windows features on or off

  3. On the list check the box for Telnet Client > click OK to install.

  4. Once installation is complete, open command prompt window.

  5. Type in «Telnet  <servername> 3351». Where <servername> = the name of the Pervasive server.

  6. Press Enter.

  7. If CMD goes blank with blinking curser then it successfully connected.  otherwise it will give a message that failed. Will need to resolve for communication on port 3351.

  8. This can be caused by the Firewall, or communication issue between workstation(s) and server.

  9. Office tech needs to find why 3351 will not connect, as this is considered a networking issue.

4. Make sure server has the network location set to private/Domain.

  1. Go to Start > control panel > Network and Sharing center.

  2. Under View your active networks check to see if the network is set to public, private, or domain.

  3. If set to public, this needs to be changed to private or domain depending on the network.

  4. The steps to change the network type depends on the version of Windows.

5. Network — Group Policy Update

In chronic cases if error persists — look at error.log file for the workstation with the errors. Record the date and time stamp and then compare it to Windows System Event logs to see if there was a Group Policy Update information entry showing as successfully completed at the same time. This process has been known to reset the network connection on completion. This can be resolved by having whomever maintains their network set the Group Policy Update to happen after hours instead of during the day. This is something outside scope of support and should be done by whomever maintains their network.

Источник
Topic T1144 Applies to All NEO Products

Problem

NEO reports a Database Error 3012 and will not start. Pervasive refers to this as encountering a ‘Status 3012’.

Description

This is an uncommon problem that confronts new users trying to start NEO for the first time and is related to a Pervasive conflict, setup or configuration problem.

Resolution 1, from the Pervasive Knowledge Base

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

Problem Description:
Status 3012: Local engine is not accessible to the MicroKernel router

Problem Environment:
Pervasive.SQL 2000

Status Codes and Messages

Cause of this problem:
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.

Solution:
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’ (for clients and workstations only):

  1. Click Start, point to Programs, then to Pervasive, and then Pervasive.SQL Control Center.
  2. Expand Pervasive.SQL 2000 Engines and expand the desired database.
  3. Expand Configuration, then expand Client, and click on Access.
  4. In the right hand frame, double-click on Local, change the Current value to Off, and click OK.
  5. In the right-hand frame, double-click on Requester, change the Current value to Off, and click OK.
  6. In the right-hand frame, double-click Target Engine, change Current to Server only, and click OK.
  7. In the left-hand frame, expand Client-16 bit and click on Access.
  8. In the right-hand frame, double-click Use Local MicroKernel Engine, change Current value to Off, and click OK.
  9. Make sure the Use Remote MicroKernel Engine value is set to on and that the remote engine is set to accept remote requests.

Resolution 2, from the Pervasive Knowledge Base

Multithreaded app fails to restart MKDE

Problem Description:
Multithreaded app fails to restart MKDE

Problem reproduced with test program which has two threads running. One thread opens a Btrieve file. WGE auto loads and open is successful. Thread issues reset. The WGE auto unloads. Sometime later, the second thread tries to open a file. It gets status 95.

Status 3012: ‘Local engine is not accessible to MicroKernel router.’

Problem Environment:
Pervasive.SQL 2000 WG

Service Pack 2a, Defect: 27603

Solution:
This issue was addressed by Service Pack 3.

[e486], [e491]

Last updated: 15 Feb 2005

Источник

Понравилась статья? Поделить с друзьями:
  • Ошибка в табеле учета рабочего после начисления как исправить
  • Ошибка в табеле учета рабочего времени объяснительная
  • Ошибка в сяоми в приложении google
  • Ошибка в стиральной машине самсунг пена
  • Ошибка в стиральной машине самсунг не1 что это