Not a geek Leftnot a geek Right

Houston Computer Specialists Since 1984

About Customer Home Novell Microsoft Support Internet Virus Links Contact

Houston, Texas 77055

Installing Client side Pervasive 2000

run install from server /win

Install Scout seems to hang on the diagnostic tests. Failed the comm test.  Tested ping to server ok.

THERE qre 2 dhcp servers, disable the xo comm dhcpr

no dhcp - add router (gateway) to scope

changed liste4n address on server from 0000 to 192.168.1.50

failed to contact server on first client install, reinstall

ODBC only seems to be setup for demo data

no sql icon is on server or workstation.

rfms versions --> btrieve ver 7.94N, RFMS ver 8.4

is this a transactional or relational database?

only the demodata has *mkd files

RFMS - Resource and Financial Management System

Btrieve - relational database

Server Engine - Btrieve or ODBC requests

An engine icon should be in the startup folder: c:\pvsw\bin\W#dbsmgr.exe -BTRV but it is not in the server or client pvsw dir

Pervasive manual: Pervasive sql 2000i combines a transactional interface designed for high performance data handling and improved programming productivity with embeddable and scalable relational interface.

on the server, both the pervasive transactional and relational database servers are started. Pervasive System Analyzer passed all the transactional tests: the relational tests on DEMODATA all failed

Failed to connect to the database. The server name or the server DSN specified may not exist.

Make sure that the Pervasive SQL 2000i Server Engine on the machine specified is started and the usercount is valid. (The server user count administrator says there are 10 licenses.)

[Pervasive][ODBC Client Interrface][Client LNA][SHM]Connecton to the server could not be established. Please check if server is running.

testing at the server of the ODBC data sources failed with the above error.

Wednesday

The Client has no services: Pervasive.SQL 2000 (relational) or Pervasice.SQL 2000 (transactional)

The server system log was cleared yesterday but has a number of errors overnight.

Type Date Time Source Category Event User Computer
Information 9/15/2010 11:24:03 AM DHCPServer None 1039 N/A SERVER
Information 9/15/2010 11:24:03 AM DHCPServer None 1038 N/A SERVER
Information 9/15/2010 11:24:03 AM DHCPServer None 1037 N/A SERVER
Error 9/15/2010 5:27:03 AM DHCPServer None 1016 N/A SERVER
Error 9/15/2010 5:27:03 AM DHCPServer None 1014 N/A SERVER
Error 9/15/2010 3:26:54 AM DHCPServer None 1016 N/A SERVER
Error 9/15/2010 3:26:54 AM DHCPServer None 1014 N/A SERVER
Error 9/15/2010 1:26:43 AM DHCPServer None 1016 N/A SERVER
Error 9/15/2010 1:26:43 AM DHCPServer None 1014 N/A SERVER
Error 9/15/2010 12:03:22 AM DHCPServer None 1010 N/A SERVER
Error 9/15/2010 12:03:22 AM DHCPServer None 1016 N/A SERVER
Error 9/15/2010 12:03:22 AM DHCPServer None 1014 N/A SERVER
Information 9/15/2010 12:03:14 AM DHCPServer None 1039 N/A SERVER
Information 9/15/2010 12:03:14 AM DHCPServer None 1038 N/A SERVER
Information 9/15/2010 12:03:14 AM DHCPServer None 1037 N/A SERVER
Error 9/14/2010 11:26:42 PM DHCPServer None 1016 N/A SERVER
Error 9/14/2010 11:26:42 PM DHCPServer None 1014 N/A SERVER
 

Event ID 1010, 1014, 1016 DHCPServer Error

You may receive the following Event ID:
Question: I have been receiving the following errors:

Event Type: Error
Event Source: DhcpServer
Event Category: None
Event ID: 1010
Description:
The DHCP service encountered the following error while cleaning up the database: 
An error occurred while accessing the DHCP database. Look at the
DHCP server event log for more information on this error.

Event Type: Error
Event Source: DhcpServer
Event Category: None
Event ID: 1014
Description:
The following problem occurred with the Jet database -1032: Jet database read or write operations failed. If the computer or database has just been upgraded, then this message can be safely ignored. If this message appears frequently, either there is not enough disk space to complete the operation or the database or backup database may be corrupt. To correct this problem, either free additional space on your hard disk or restore the database. After you restore the database, ensure that conflict detection is enabled in DHCP server properties. For information about restoring the database, see Help and Support Center. Additional Debug Information: JetBackup.

Event Type: Error
Event Source: DhcpServer
Event Category: None
Event ID: 1016
Description:
The DHCP service encountered the following error when backing up the database: 
An error occurred while accessing the DHCP database. Look at the
DHCP server event log for more information on this error.

Resolution: 
1. Disable Allow Indexing Service to index this disk for fast file searching. To do that, open the properties of the C. Select General. Uncheck the Allow Indexing Service to index this disk for fast file searching.
2. It could a software issue, for example Anti-virus and security software. You may try to Windows clean boot to test it.
3. Copy the original Windows system.md_ file from the Windows compact disc to your hard drive. Then, run the <Systemroot>\\System32\\Expand.exe program to expand System.md_ to System.mdb. Next, copy System.mdb to the new database location. 
4. Or refer to the following links:
Event Viewer Displays DHCP Events 1010, 1016, and 1014 
... The DHCP server encountered the following error when cleaning up the user database -or- DHCP Event 1016 ... Article ID : 129730: Last Review : November 1, 2006: Revision : 4.1
http://support.microsoft.com/kb/129730

This event happens when you move the Dynamic Host Configuration Protocol (DHCP) database and its backup directories from the default location. When the DHCP server is initially installed, its database is stored in %SystemRoot%\SYSTEM32\DHCP and the backup directory is set to %SystemRoot%\SYSTEM32\DHCP\BACKUP\JET. The DHCP database remembers all attached database directories and files in the SYSTEM.MDB file. If the database and backup directories are moved, the backup fails because it tries to backup the database from the old and new locations, but cannot find the database file in the old location.

However, I found NO files in %systemroot%\system32\dhcp; there is NO system.mdb file on drive c.

DHCP server stops leasing addresses if a sharing violation occurs 
Event ID: 1016 Source: DHCP Server Description: The DHCP Server encountered the following error when backing up the user database: Data: 2d 4e 00 00. Back to the top
http://support.microsoft.com/kb/216793 
 
The DHCP server encountered the following error when backing up the ... 
... Event Log Event ID Event Type; DHCP: System: 1016: Error ... 
http://msdn.microsoft.com/library/en-us/w2kmsgs/3440.asp 
 
Errors When Using Directory Replicator to Backup DHCP Database 
Article ID : 193819: Last Review : October 31, 2006: Revision : 1.1 ... Event 1016 Source: DhcpServer Description: The DHCP server encountered the following error when backing ... 
http://support.microsoft.com/kb/193819
 
The DHCP service encountered the following error when backing up the ... 
The DHCP service encountered the following error when backing up the database ... Event Log Event ID Event Type; DhcpServer: System: 1016: Error ... 
http://msdn2.microsoft.com/en-us/library/ms847700.aspx 

The DHCP service encountered the following error when backing up the ... 
Event Message: The DHCP service encountered the following error when backing up the database ... Event Log Event ID Event Type; DhcpServer: System: 1016: Error ... 
http://msdn.microsoft.com/library/en-us/w2kmsgs/5149.asp 
 

Related Topics

Event ID Troubleshooting

Event ID: 1000 - The safe mode service of Windows SharePoint Services has failed to initialize because of an unknown error. ...
http://www.chicagotech.net/wineventid.htm

 

Disk Check

Event Type: Information
Event Source: Winlogon
Event Category: None
Event ID: 1001
Date: 9/15/2010
Time: 1:56:41 PM
User: N/A
Computer: SERVER
Description:
Checking file system on C:
The type of the file system is NTFS.
Volume label is LOCAL DISK.

A disk check has been scheduled.
Windows will now check the disk.
Cleaning up minor inconsistencies on the drive.
Cleaning up 170 unused index entries from index $SII of file 0x9.
Cleaning up 170 unused index entries from index $SDH of file 0x9.
Cleaning up 170 unused security descriptors.
CHKDSK is verifying Usn Journal...
Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
Free space verification is complete.
CHKDSK discovered free space marked as allocated in the volume bitmap.
Windows has made corrections to the file system.

39078080 KB total disk space.
24960195 KB in 50692 files.
15800 KB in 6789 indexes.
0 KB in bad sectors.
156645 KB in use by the system.
65536 KB occupied by the log file.
13945439 KB available on disk.

512 bytes in each allocation unit.
78156161 total allocation units on disk.
27890879 allocation units available on disk.

Windows has finished checking your disk.
Please wait while your computer restarts.

Sysvol

Event Type: Error
Event Source: Ci
Event Category: CI Service
Event ID: 4124
Date: 9/15/2010
Time: 2:02:45 PM
User: N/A
Computer: SERVER
Description:
Content index on c:\system volume information\catalog.wci is corrupt. Please shutdown and restart the Indexing Service (cisvc).
 

Note: The Pervasive.SQL product provides two categories of maintenance utilities: Btrieve and SQL.  The SQL Maintenance Utility supports data source named (DSNs), which are used for relational access through ODBC.  See "Backing Up a Database with SQLUTIL" on page 8-18 for a discussion of the SQL Maintenance Utility.

9/21/10

On the Windows 2K server, the Pervasive ODBC Data Sources are a, b, c,

a --> Pervasive ODBC Engine Interface

b --> Microsoft dbase Driver (*.dbf)

c --> Driver do Microsoft Escel(*.xls)

DeluxeCD --> Microsoft Access Driver (*.mdb)

Working RFMS data files in the server c:\RFMS dir include: Receipt.dat, Comments,dat, Roll-hst.dat, Ap.dat, Roll-inv.dat, KG266180.tmp, Item-inv.dat, PRICECHG.DAT, iTEM-HST.DAT,password.dat, Wolne.dat, Jobcost.dat, Line.dat, Salesman.dat, posconfi.dat, WPASSPAT.DAT, USERCNT.DAT, Customer.dat, Header.dat

The SQL control center installed on Server 2003 is version 7.20.230.036

Task manager on W2k has more processes than the S2003

Note that when installing RFMS on Server 2003, first the Pervasive disk, then the 8.4 update, but data not connected, then the 8.4 & Payroll update, now data is connected. This also happened after installing 64 Microsoft updates.

Now the Server2003 is online and R mapped to RFMS and F mapped to PVSW.  Reinstalled Pervasive from the client on Server2003. Pervasive test says it cannot connect to database.  Cannot verify that relational access to Pervasive.SQL 2000 is functioning properly.

Failed to connect to the database.  The Server Name of the Server DSN specified may not exist.  Make sure that the Pervasive.SQL 2000 Server Engine is running on the machine specified and the user count is valid.

[Pervasive][ODBC Client Interfase][Client LNA] Connection attempt time out.  The SQL Connection Manager may be inactive or using a diffenent transport protocol from the client.

I will now follow the communications troubleshooting as found in the Pervasive book

Checklist for Problems

Did you see any error messages displayed during installation?  - yes see above.

Does the Network function correctly? - yes

Is the Engine running? There are no Pervasive services running on the client. On the Server, Pervasive.SQL 2000 (relatiolnal) and Pervasive.SQL 2000(transactional) services are both running

Is the Client software correctly functioning?

Are there errors in your PVSW.LOG file? No listings on the workstation, on the server, information only ntdbsmgr.exe NTMKDE. I guess these were created when I ran Navigator on the server.

There is no "Pervasive System Analyzer" but there is InstallScout which I think is the upgraded version.

The server you chose appears to have the TCP/IP protocol but Btrieve did not respond. --> Ensure Btrieve engine is started and rerun test.

Userguide.pdf, page 5-3; 6. Note: If your application used pure Btrieve access only, without ODBC, then skip this step. (This is probably what RFMS uses)

IN PCC, Supported protocols: Microsoft SPXII; Microsoft TCP/IP

On the workstation, the PCC shows Pervasive.SQL 2000 Engines --> PCS (x) SERVER ();  PCS is the name of the workstation and has been changed to GX280-RFMS, SERVER is the name of the OLD server.

Therefore, reinstall Pervasive on workstation, uninstall, remove PVSW di

It worked before! Install 8.4 update and 8.4 payroll on the workstation. RFMS does not have an add/remove item, del the RFMS dir. Del PVSWarch dir. tuneup utilities for super clean

1.  Install RFMS 8.4 update. The installation disk in the 8.4 update jacket said it was installing 8.3. It would not start because wbtrv32.dllwas not found, therefore start with Pervasive. delete RFMS and its shortcut.

1. install Pervasive.SQL SP4 using typical install.  Logged into F and R by entering the password. Installed 10 licenses. Would not accept testing the transactional engine on F. but it would test on f:\samples but failed create, read, update, insert; passed all on c:\pvsw\samples; relational tests passed as well.

2, give everyone all rights to RFMS and PVSW on server.

3. Install RFMS from "Installation CD"

4. Install RFMS 8.4 and Paroll update, the RFMS directory is missing. Reinstall with "installation CD" Only one sub dir "Practice" was installed

5. The file c:\RFMS\RFMSvers.txt could not be opened. Copied it from the server, now installation completed. Now RFMS error (In harmony with your contract, your system is access code protected and has EXPIRED.  Please contact te RFMS Sales Office.  I think what got me this message is that I installed from the CD and not the server win client. But now I have the Pervasive System Analyzer Wizard.

PSV says: the server you chose appears to havfe the SPX and TCP/IP protocols but the network address returned does not look like a valid address and therefore failed, Connect to Server, Access Engine, Stress Test. usrguide.pdf says 3. check the client access requester, make sure the setting is set to on.  There is no client access requester on either the server or workstation. See sgs.pdf, 15-9 Installing the Pervasive.SQL 2000i Client Components.

Run Pervasive setup from server. chose network installation, remove pervasive with add/remove, del psvw dir, installscout not found on the server; PCC on workstation shows server GX280(x).

Uninstall pervasive del pvsw and ffms, reinstall pv from server.

Forum provided new documentation followed sgs.pdf Client network configuration 17-17 to make server ip 192.168.1.51 and set up in hosts file. But it seems mostly like what I already have.  Now following 15-9, Installing the Pervasive.SQL 200i Client Components. Setup is removing the existing copy. Selecting network install to c:\pvsw. Install Scout was not fiund on the Server.  Database connectivity tests will not be performed but it continues on to copy files and utilities.

Had to install from CD to get the Pervasive System Analyzerv

Forum link: http://cs.pervasive.com/forums/p/13234/45307.aspx#45307

server ip:  67.105.91.86

 

9/30/10

sql test passed when the server firewall was turned off.  Reinstalled the Pervasive 2000 on server and on client, then the RFMS. Before this error 3012, and then passlvl.dat could not be opened.  Still getting file c:\RFMS\Passlevl.dat could not be opened.  Error: Unknown Error *3012)  Press ok to end application. Runnig a fuller Pervasive System Analyzer.  Copied Nadia RFMS backup from server 1 to c:

10/7/10

Client RFMS has File Access Error

File C:\RFMS\Passlevl.dat could not bve opened.  Error: Unknown Error (3012). Press OK to end this.

Change the security of this file to full control for everyone. Add full control to Users (PC2\Users) But still says it cannot access. On the server, the owner of this file is Administrators (SERVER1\Administrators).  Will copy this file which was last modified in 2002, to the client. The file on the Client was dated 4/20/2001 and the server file was dated 10/29/2002.  Since now we still have file access error, this must be caused by something else.

Server1 Environment

C:\Documents and Settings\Administrator>set
ALLUSERSPROFILE=C:\Documents and Settings\All Users
APPDATA=C:\Documents and Settings\Administrator\Application
Data
CLASSPATH=C:\PVSW\BIN\PVJDBC2X.JAR;C:\PVSW\BIN\PVJDBC2.JAR
CLIENTNAME=GX280-RFMS
ClusterLog=C:\WINDOWS\Cluster\cluster.log
CommonProgramFiles=C:\Program Files\Common Files
COMPUTERNAME=SERVER1
ComSpec=C:\WINDOWS\system32\cmd.exe
FP_NO_HOST_CHECK=NO
HOMEDRIVE=C:
HOMEPATH=\Documents and Settings\Administrator
LOGONSERVER=\\SERVER1
NUMBER_OF_PROCESSORS=1
OS=Windows_NT
Path=C:\PVSW\BIN;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\Syste
PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH
PROCESSOR_ARCHITECTURE=x86
PROCESSOR_IDENTIFIER=x86 Family 15 Model 4 Stepping 1,
GenuineIn
PROCESSOR_LEVEL=15
PROCESSOR_REVISION=0401
ProgramFiles=C:\Program Files
PROMPT=$P$G
SESSIONNAME=RDP-Tcp#2
SystemDrive=C:
SystemRoot=C:\WINDOWS
TEMP=C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\2
TMP=C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\2
USERDOMAIN=SERVER1
USERNAME=Administrator
USERPROFILE=C:\Documents and Settings\Administrator
VSL=C:\PVSW\BIN
windir=C:\WINDOWS
 
 

Client Environment
C:\Documents and Settings\User>set
ALLUSERSPROFILE=C:\Documents and Settings\All Users
APPDATA=C:\Documents and Settings\User\Application Data
CLASSPATH=C:\PVSW\BIN\PVJDBC2X.JAR;C:\PVSW\BIN\PVJDBC2.JAR
CLIENTNAME=Console
CommonProgramFiles=C:\Program Files\Common Files
COMPUTERNAME=PC2
ComSpec=C:\WINDOWS\system32\cmd.exe
FP_NO_HOST_CHECK=NO
HOMEDRIVE=C:
HOMEPATH=\Documents and Settings\User
LOGONSERVER=\\PC2
NUMBER_OF_PROCESSORS=1
OS=Windows_NT
Path=C:\PVSW\BIN;F:\BIN;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH
PERVASIVE_PATH=F:\BIN;C:\PVSW\BIN
PROCESSOR_ARCHITECTURE=x86
PROCESSOR_IDENTIFIER=x86 Family 15 Model 4 Stepping 1, GenuineIntel
PROCESSOR_LEVEL=15
PROCESSOR_REVISION=0401
ProgramFiles=C:\Program Files
PROMPT=$P$G
SESSIONNAME=Console
SystemDrive=C:
SystemRoot=C:\WINDOWS
TEMP=C:\DOCUME~1\User\LOCALS~1\Temp
TMP=C:\DOCUME~1\User\LOCALS~1\Temp
USERDOMAIN=PC2
USERNAME=User
USERPROFILE=C:\Documents and Settings\User
VSL=C:\PVSW\BIN
windir=C:\WINDOWS

 
There appears to be no significant differences.

 

 

 

Primary Computer Service, Inc.
Copyright 2016 [Primary Computer Service, Inc]. All rights reserved.
 
 
Revised: 08/13/16