SYSPASS.BTR Error

[ddamm]

We had a reboot of our server yesterday while a user was logged in and using Macola.

Today, no one can login to Macola. We get the splash screen and then a Progression error "The Pervasive Network Services Layer encountered a connection failure." Then "Error 3106 on file M:\MACOLA75\SCREENS\SYSPASS.BTR - refer to online P.SQL Help." Then, "System Error: File SYSPASS.BTR is not open."

We have an NT4 server running Pervasive SQL. The Server is multihomed, running TCP/IP (as are the clients). I believe that we are running Macola version 7.5.103f. The clients with the problem are Win98. We are able to resolve names to addresses. The PING command works.

We have stopped and restarted service for Btrieve and the Pervasive SQL. We even rebooted the server. We have gone through and confirmed the original configuration for the server installation of Macola.

 

[dgillz]

Check the M;\maola75\usres directory for ghost users. Delete anything you find in that directory without a date of today.

Let me know where you stand on this issue. Software Sales, Training and Support for Macola, Crystal Reports and Goldmine
dgilsdorf@mchsi.com

 

[vbajock]

What version of PSql are you using? 2000 has a diagnostic tool called System Analyzer that will perform a series of protocol tests that can help you pinpoint the problem.

There is also a possibility what you have is a operating system problem on your NT server, not a Macola problem. Can you ping another computer using the target computers Netbios name instead of the IP address ? Have you done any recent work on network cards or protocols on the server ? Why are you using a multihomed server ?

 

[ddamm]

dgillz,
I saw a message on tek-tips from another user with a similar problem with the SYSPASS.BTR file, and removed the users last week. So, there are no entries at this point in the M:\maola75\users directory.

vbajock,
We are using PSQL 7 on an NT4 SBS 4.5 Server. Upon installation of the server (before my time), the owner decided it was in his best financial interest to purchase only one box. Therefore, this box also houses all the network apps, Exchange, etc. So, it is also our gateway to the Internet, which is why it is multihomed.

We were doing some work on it to enable VPN. But have backed out all of the settings at this point. Now, we will probably enable VPN using a router capable of issuing certificate keys.

I can ping other computers, and have name resolution.

I have uninstalled the client on one computer. Now, when I try to reinstall the client software, we seem to be pointed at the external (WAN) NIC.

 

[vbajock]

Here is a quick solution - enable IPX on the server and the clients, and reinstall the clients using the IPX protocol. It will slow your network down, but it will take tcpip out of the picture.

 

[dgillz]

If you send me an email I will give you 2 documents I downloaded from Macola on this error. Software Sales, Training and Support for Macola, Crystal Reports and Goldmine
dgilsdorf@mchsi.com

 

[ddamm]

Thank you for your suggestions. It turns out that the WINS server had been applied to both the LAN and WAN NICs. When the server rebooted, the clients started to receive the wrong gateway even though I thought that the clients should have received the correct gateway from the DHCP server. Mind you, all these are running on one box.

The odd thing is that after I resolved the problem, I was installing a new client. In the process of testing the connection, which is part of the installation process, the address of the server is listed. This address is that of the WAN NIC. But, it all works.

Thank you for your suggestions.