Macola 70 errors...inherited problems 1

[MParsch]

I have inherited a Macola setup with Progression. After physically moving the server (NT 4) and logging in with the normal client workstation, I receive the error "The Pervasive Network Services Layer encountered a connection failure", then, "Error 3106 on file F:\Macola70\SCREENS\SYSPASS.BTR - Refer to online P.SQL help", then "System error - SYSPASS.BTR is not open."

Any help on this antique would be appreciated.

 

[abaldwin]

I think we might need more information.

1. What version of Macola progression
2. What version of db backend on this server.
3. Did you connect a workstation and run the install from the server?

If answer to 3 is NO then I would suggest get a workstation, connect to the net, install the pervasive client, map a drive ("F") in your case to this servers macola share, run the client installs for Macola, and then try to log in.



Andy Baldwin

"Testing is the most overlooked programming language on the books!

 

[MParsch]

The documentation is a bit lacking about this but i will give it a go.

1. I believe it is 7.5.x. I can't find a file with the exact version number.
2. Pervasive SQL
3. The client (32-bit) was previously installed on this workstation. The only change that was made was shutting down and physically moving the server and its port. It maintains the same domain info and IP addy.

I have tried disconnecting the network drive and remapping which goes fine and adding the everyone permissions to the share to avoid permission errors.

I appreciate your quick response, abaldwin. Our VP of finance is quite anxious to get this thing running!

 

[MParsch]

I found some additional information,

1. 7.5.103
2. Pervasive SQL 7

Hope this helps.

 

[abaldwin]

Further,

From Macolas AWESOME infomine (can you hear the sarcasm?)

Problem:
What may cause a status 3106 error message when trying to log into Progression, or running the Install Scout, or Function Executor utilities?

Resolution:
This error can be caused by any one or more of the following:

1. a mismatch of protocols between the workstation and the sever

2. dual NICs in the server, but multihomed is not enabled

3. PING command not able to resolve IP address

4. the Accept Remote Requests set to OFF on an NT server

5. Advance Power Management: Windows OS drops TCP/IP listen ports during a Suspend which uses the Advance Power Management features of newer computers, especially Laptops. While Windows 98 and Windows NT are able to restore the listening ports when power resumes, Windows 95 does not. This leaves the active MicroKernel engine unable to "hear" anything and thus connectivity is lost

6. The Pervasive Transactional and Relational Services are not running on the server.


I would say that by just physically moving the server and nothing else, you probably do not have the pervasive server engine running. I can not remember exactly where but on the SERVER, start programs, pervasive, start engine.

Andy

Andy Baldwin

"Testing is the most overlooked programming language on the books!

 

[abaldwin]

Also check to see that you plugged the network cable back into the same NIC that was originally in use. Some servers have more than one nic and each would have a different IP address. Your client is looking for the original ip to pass pervasive request to.


Andy Baldwin

"Testing is the most overlooked programming language on the books!

 

[MParsch]

Thanks again for your help.

I will answer the infomine questions.

1. TCP/IP is enabled on both.
2. Single NIC in the server and only one IP is present
3. Ping from any work station on the network resolves to the correct IP.
4. In troubleshooting, I came upon a program for the pervasive DB. It showed remote access to yes.
5. APM is off.
6. I had to go into services and restarted both Btrieve and SSQL services. Both restarted without errors.

I really appreciate this.

 

[abaldwin]

Now that the Btrieve services are running, can you run Macola from the test workstation?


Andy Baldwin

"Testing is the most overlooked programming language on the books!

 

[MParsch]

Yes!
We can now log on to Progression.

It said it was started, but it lied!

Now the error we are receiving is whenever we attempt to connect is the the "x" file has not been set-up. Our VP states that under the old admin, he said that it was pointed to the incorrect database/files, went away and it worked. Any ideas about that?

 

[MParsch]

Wait, I got that solved and everything is running smoothly now.

Thanks for all of your assistance!

 

[abaldwin]

Good. You may want to insure that the services for BTRIEVE and Pervasive are set to startup automatically. It would appear that the server never shutdown that often. Having the services start automatically will insure you can run them if the machine looses power etc.

Andy

Andy Baldwin

"Testing is the most overlooked programming language on the books!