Access to Data

Problem 1: RAM Commander user can’t access network drive with projects sometimes ("Fatal error"), when other user(s) are already working with it. If nobody else is working with drive user may access it.

Additional symptoms: Network drive is shared with full access rights. If user is first on the drive he enters successfully. May appear sporadically (depending on the first user who access the network drive). For some user combinations may work, for some user combinations may not work.

Reason:

Second user connecting to the network drive will try to use Pervasive Database Engine of the first user connected to the drive. It will search second user PC and try to access Pervasive Database Engine network service. If second user can’t find other user PC (DNS, sub-net, VPN etc.) or can’t access other user's Pervasive Engine (Firewall) then the connection attempt will fail.

Solution:

1.	Check and ensure that all RAM Commander users may "ping" each other computers by computer name.

2.	Check and ensure that Pervasive Database Engine is included into the list of exceptions on all RAM Commander user computers and that Firewall exceptions are not disabled.

Pervasive Database Engine is usually added to the Firewall exceptions list when RAM Commander is installed. Setup procedure gives Windows Firewall Unblock question:

Install_WinXPFirewall

Install_Win7Firewall

If user answers yes (or Unblock, or Allow Access), Pervasive Engine is added to the exceptions list.

For all RAM Commander user computers, perform steps described below:

To check that the Pervasive Database Engine is allowed by Windows Firewall:

i.	Open Control Panel from Start menu, Settings section.

ii.	Open "Windows Firewall"

iii.	If Firewall is off, no need to continue, you may close the Firewall dialog.

iv.	If Firewall is on, make sure that "Don't allow exceptions" check box is empty:

Troubleshooting_WinXPFirewallSettings1

v.	Switch to "Exceptions" tab of the dialog.

vi.	Make sure that there is "Database Service Manager" program in the list:

Install_WinXPFirewall_Exceptions

vii.	If there is no "Database Service Manager", click "Add program" button, then click "Browse" and select W3dbsmngr.exe program in RAM Commander working folder (usually RAMC32\BIN). Then press Ok. "Database Service Manager" should now appear in the list of exceptions.

viii.

You may need to provide also access for "Database Service Manager" to TCP ports 3351, 137-139, and 2441.

ix.	Press Ok on the Firewall dialog to close it and store changes.

Problem 2: All RAM Commander users can’t access network drive with projects, users unable to open projects list on a network drive

Additional symptoms: Initially network drive works fine, and then this problem could suddenly appear. Could be accompanied with error message "OPERR=<116> in X:\RAMC32\BIN\DRIVE.DRV". The drive.drv file exists, project folders exist, access to the network shared folder is available with full access rights to all users.

Reason:

Users connecting to the network drive try to use Pervasive Database Engine of the first user connected to the drive. If the first user's Pervasive Database Engine on PC in general is stuck, the described problem will appear. This stuck user's PC should be restarted.

Solution:

1.	Try to restart the Pervasive Database Engine which is stuck.

a.	Open the folder where the projects you can't access are located, for example X:\RAMC3\PRJ.

b.	Try to open the X:\RAMC3\PRJ\~PVSW~.LOC file using Notepad (Windows Explorer, locate file, right click – open).

c.	You will see a computer name of a PC which acts as Pervasive Gateway and which has problem with Pervasive Database Engine.

d.	Restart this computer.

e.	Delete the X:\RAMC3\PRJ\~PVSW~.LOC file.

f.	Try opening the list of projects again.

2.	If the previous recommendation did not help, please restart the RAM Commander database server and try again.

3.	If the previous recommendation did not help, please ask all the engineers working with RAM Commander to restart their computers.

In addition, it is recommended that the PC where the network drive with shared projects is physically located to have RAM Commander server installed (see Server Installation ) or to have RAM Commander's Projects Network Service installed (see Standalone Installation + Common Network Database ).

Problem 3: RAM Commander installed, but user login name and password were not defined during the installation.

Solution:

1. Run UserMngr utility from Start->Programs->ALD Engineering menu group.

2. Choose "New manager" button. Manager password dialog will appear – just press Ok.

3. "Edit user parameters" dialog will appear:

Install_NewUserDialog

4. Enter desired user name (password and group fields are optional) and press Ok.

5. Close "User manager" utility

6. Start RAM Commander and enter the user name you've just defined.

Problem 4: Error message with code “3105” after starting RAM Commander. Does not happen when starting RAMC with administrative privileges.

Reason 1: Pervasive Database Engine network protocols are set to support not only TCP/IP (but also SPXII and NETBIOS).

Solution: Manually change Pervasive Database Engine network protocol settings to contain only TCP/IP protocol, without SPXII and NETBIOS, using Windows Registry Editor, as shown below. Open the key HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software\MicroKernel Workstation Engine\Version 7\Settings , value name Supported Protocols, and change value data to TCP/IP:

Pervasive_SupportedProtocols

Do it also for key HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software\Communications Requester\Version 7\Settings, value name "Supported protocols" (if key exists).

Do it on all RAM Commander workstations, servers or standalone PCs.

Reason 2: No write permissions for Pervasive Database Engine service and log files.

Solution:

We can suggest two options to solve this issue:

1. Give write permissions to C:\Windows\MKDE folder for RAMC users on the RAMC Server (in client/server configuration ) and on PC which makes the problem.

2. Change settings in registry for each RAMC workstation.

Find Key HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software\MicroKernel Workstation Engine\Version 7\Settings, then change value names:

DBNamesDirectory - <RAM Commander installation folder> (for example C:\RAMC32)

Home Directory - <RAM Commander installation folder>\BIN (for example C:\RAMC32\BIN)

Trace File - <RAM Commander installation folder>\BIN\MKDE.TRA (for example C:\RAMC32\BIN\MKDE.TRA)

Transaction Log Directory - <RAM Commander installation folder>\BIN\MKDE\LOG (for example C:\RAMC32\BIN\MKDE\LOG)

Problem 5: Error message with code “OPER=100” while working with large project

Solution: Problem with Pervasive database engine settings - allocated cache size is too small - increase it to 4000000.

Perform the following changes:

1.	Press Start button

2.	Choose Run

3.	Type regedit and press ok

4.	Open HKEY_LOCAL_MACHINE group, then Software, Pervasive Software, Microkernel Router, Version 7, Settings (key HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software\MicroKernel Workstation Engine\Version 7\Settings)

5.	Double click on “Cache Size” key in the right part of the window.

6.	Change key value to “4000000” (hex)

Press Ok.

8.	Restart the PC and continue working.

If this does not help - try increasing the value up to 40000000.

Problem 6: Error message with code “1022” or “1032” after starting RAM Commander

Solution: Problem could appear on Windows 95/98 on RAM Commander workstation. Do the following:

9.	Press Start button

10.	Choose Run

11.	Type regedit and press ok

12.	Open HKEY_LOCAL_MACHINE group, then Software, Pervasive Software, Microkernel Router, Version 7, Settings

13.	Double click on “Target Engine” key in the right part of the window.

14.	Change key value to “0”

15.

Press Ok.

Problem 7: Error message with code “8020” after starting RAM Commander

Solution:

In client-server configuration, can appear on client if connection with the server was terminated.

User should ensure the server is on, the connection is established (network drive etc.), and reboot the workstation.

Problem 8: Error message “W3DBSMGR: Error 8509: Timeout occurred during the initialization of MKDE” or error message with code “3012” inside it

Solution:

The most common reason of the problem – absence or old version of Microsoft dll files \WINDOWS\SYSTEM\MSVCP60.DLL and \WINDOWS\SYSTEM\MSVCRT.DLL. Both files must be present and their creation year must be later then 1998. If you need the files – contact our support service or take them from other computer with the same operating system.

Problem 9: Error 1021

Sometimes happen because there is not enough free space on the system disk (disk where Windows installed) or insufficient access rights to RAM Commander folders with database files.

Solution:

1. Check free disk space, if low - free some disk space and try once again.

2. Make sure that user has full access rights to RAM Commander installation folder (by default C:\RAMC32\) and all it’s sub-folders and files on all levels. Just Read/Write permissions are not enough - file creation/deletion, folder creation/deletion should be also allowed, so "Full Control" permissions are required.

3. If previous advices do not help, grant "Full Control" access rights to Windows folder and try again.

Problem 10: Error message “The setup routines for the Microsoft Access Driver {*.mdb} could not be loaded due to system error code 126.”

Solution:

See Microsoft KB article:

https://support.microsoft.com/default.aspx?scid=kb;EN-US;q260558

There are two possible causes for this problem:

•	Incorrect registry settings for MDAC components.
•	Incompatible .dll files.

These problems may have arisen because of an installation of older software that changed the registry settings of the ODBC drivers or replaced some .dll files with incompatible versions.

Resolution for incorrect registry settings problem:

Start Registry Editor (Regedt32.exe).

Locate the following key in the registry:

HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI

Installation information for ODBC drivers is stored in this key. Make sure that all the required ODBC driver files are in the correct folder as described by the registry keys. For example, assume that you have the following information in your registry for the Microsoft Access ODBC driver:

HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\Microsoft Access Driver (*.mdb)
Driver = C:\WINNT\System\Odbcjt32.dll
Setup = C:\WINNT\System\Odbcjt32.dll

This will cause an error if the Odbcjt32.dll file is in the C:\WINNT\System32 folder. You can modify the registry key values to C:\WINNT\System32\odbcjt32.dll to solve this problem. Also verify that the Odbcinst.ini file has the correct entries in the same way.

Any wrong value in HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI under the Setup key will cause this error.

Resolution for incompatible .dll files problem:

Reinstall your current version of MDAC, or install the latest version. See the "References" section of this article for more information on reconfiguring an MDAC installation. The latest version of MDAC can be downloaded from the following Microsoft Web site:

https://msdn.microsoft.com/dataaccess

Problem 11: RAM Commander works fine for user with PC administrator access rights, but does not work for another user.

Solution:

The reason is insufficient user rights to access system resources required for RAM Commander.

Grant full access rights to the user for the following resources:

Folders:

RAM Commander installation folder (usually C:\RAMC32)

Project folders on all local and network drives where user wishes to store his projects

Registry branches:

HKEY_LOCAL_MACHINE\SOFTWARE\Advanced Logistics Developments

HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software

Problem 12: RAM Commander workstation can’t start (error 94) or can't access network drive. Also, server alias is used (FQDN or CNAME), server OS is Windows Server 2003 SP1.

Solution:

Do not use FQDN/CNAME from workstations, but use full not-aliased server name instead. If you still wish to see alias - see the next paragraph.

This problem occurs because Windows Server 2003 SP1 includes a new security feature named loopback check functionality. By default, loopback check functionality is turned on in Windows Server 2003 SP1, and the value of the DisableLoopbackCheck registry entry is set to 0 (zero).

The loopback check functionality is stored in the following registry subkey:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\DisableLoopbackCheck.

Set this key value to 0 in the registry on the server.

Then reboot the server.