Macola 7.5 103f crashes on Windows 2000 and Windows XP

[JDMiller]

I am having an issue with some of my Windows 2000 and Windows XP machines running Macola 7.5 103f. When some users attempt to open or open and close Macola throughout the day Macola will crash the system and reboot displaying the following

This system has recovered from a serious error. A log of this error has been created. Please tell Microsoft about this problem. We have created an error report that you can send to help us improve Microsoft Windows. We will treat this report as confidential & anonymous.

Then it says do you want to send this error?

Has anyone else experienced this?

 

[vbajock]

7.5 xx versions are only designed to run on Win 3.1, 95, 98 platforms. You need to upgrade to ver 7.6xx, and upgrade to Progession 2000i if your running PSQL Btrieve.

Version 7.6.100a seems to be the most stable for both MS SQL and PSQL versions.

 

[cparralesl]

Hello

I'm running 7.5.103e on W2k. and it is working fine. Before update to 103f I built and testing scenario, server and worstation on W2K, where I made so many process on Macola. All operation that I made worked just fine. So you should not have problem with Macola 7.5.103f on W2K

Maybe you need to check what you have installed on the machines.

My tests were made with W2K, Office 2K and some Patches installed only

Regards

Cesar Humberto Parrales
Application Support

 

[vbajock]

The 7.5 version was so doggy it barked when you loaded it.

 

[MacolaHelp]

I have a couple of clients still on 103f & win2k workstations. Not sure about xp. They are fine, running pervasive sql 2000i. One is on a win2k server, one a novell 4.11 server. Maybe you need to tweak your pervasive settings. I also had a site that ran on 103f sql on a win2k server, mssql 2000 for 1.5 years without the type of errors you indicate. Sounds like a machine configuration issue to me.

 

[MacolaHelp]

Forgot to ask: are you running pwe or standard progression? My sql site never ran pwe on many workstations. They had 98 & win2k workstations, converted all workstations to xp & ran that configuration with 103f mssql for 6 months or so before we upgraded to xp. Have you patched your servers & workstations & database manager to current levels? Any reason why you haven't gone to 7.6.100a yet?

 

[JDMiller]

We are in a catch 22. We can't upgrade to Macola 7.6 100 because we still have Windows 95 machines but when we upgraded some to XP they are getting this error.

 

[stravis]

JDMiller,

The problem you are experiencing is abnormal. In order to resolve your issue, you will need to respond to the postings by other members. With this information in hand, we can help you. There is no reason you should be caught in a catch 22 situation.

Regards,
Scott Travis
infoSpring, LLC.

 

[JDMiller]

We are running Pervasive 2000i. The issue has happened on some XP machines and not others. A user can have nothing else open, attempt to open Macola and get booted out.

The workstations are new and setup by the same individual. I do not set them up so I do not know what patches and versions are loaded on the OS. We do not run PWE.

Where should I look for pertinent OS configurations?

 

[stravis]

This behaviour is highly unusual. I would suggest that the mostly likely cause of this problem is either faulty hardware or another software application running on these machines that is causing these issues. The reason I say this is that if Macola itself was having problems on a XP machine it's own process would be the only one that would fail and Windows XP would continue to run without a reboot. The problem you are having has be triggering a system problem or caused by a system problem; that is the only way that a reboot would occur.

If there is a problem with hardware I would suspect that it is either your graphics adapter, memory or main board. The most likely of the two would be the graphics adapter. You could have incompatible graphics adapters installed on these machines or incompatible graphics adapter drivers installed. If the problem is with the main board you should be able to fix the problem with BIOS update. I would say that memory is a highly unlikely candidate because it would mean that you would have had to have the same memory defect on each PC, although it is also possible that you have incompatible memory installed on several machines.

If the issue is software the most likely types of sofware that can cause this behavior would be software that interacts with your systems graphics, such as screen magnification sofware or screen capture utilities. Other possibilites might be system or user monitoring applications installed on the machine. It may be software that is installed on every machine but configured slightly different on the machines causing this problem.

In addition to checking the above items I would suggest reinstalling the Pervasive and Macola Clients on the problem machines. It might be best if you try this first and solve yourself a great deal of headaches.

Regards,
Scott Travis
infoSpring, LLC.

 

[MacolaHelp]

Are the client machines crashing or is the server crashing? If you have sp4 w/hot fixes on your server & the latest service packs on the client machines, I would then check your pervasive settings on the local machine. Be sure you are sending requests to the server & you have the communication protocols set to tcp/ip only.

 

[kscheeler]

Just so you know. 7.6.100 will work with Windows95 computers. If you try to upgrade to service pack A, it will pop up a screen mentioning that SPA won't install on a Windows95 client.

Kevin Scheeler

 

[MacolaHelp]

I just checked w/2 of my other sites still on 103f. They both have some xp clients, one is win2k server, one is novell 5.11 & they are running just fine. What is your server platform?

 

[TardisInc]

I would agree that the most likely problem is the graphics card or it's drivers. You might want to check to manufacturer's website for the latest drivers.

On the error msg that pops up, you can drill down to see what info the msg is going to send to MS. Look and see if your graphics drivers are mentioned in there.

Larry Wilson
TARDIS Systems, Inc.
Dallas, TX

 

[JDMiller]

We are checking into the graphics suggestion. Our Macola(s) run on several servers all
Novell NetWare 5.1
Support Pack Revision 05

I was told today that the Macola issue exists on both Windows 2000 and Windows XP machines which are on multiple PC makes and models.

We just brought up another XP box with Macola and it crashed 3 times in a row. Macola opened once and then crashed 3 times on later attempts to open.

 

[MacolaHelp]

I have a site running 103f nw5.1 tcpip, pervasive sql200i sp4. We've been running for 2+ years & have migrated almost all the machines to win2k or xp (20 users). Everything is fine, though PWE is inconsistent on login on xp, but haven't had time to troubleshoot it. We did need to use lmhosts on the local machine to help resolve dns as they have 5 or 6 servers with all different operating systems. We do lots of inbound EDI transactions, fewer outbound. Lots of AR transactions, custom VB programs & access routines.

Do your pervasive & macola client installs go off without errors? When the new xp box crashes, are you getting the same error as in your initial post? I really have had very few issues with macola & win2k/xp.

 

[stravis]

Was this a new XP box, and are you using drive imaging? Something is fishy in this pot of stew and it ain't Macola.

 

[JDMiller]

We have tried a couple of things but we are still having issues. Some odd things that seem to have helped but not resolved the situation.

We found if there are old user files under the Macola70/user directory and the user with the crashing PC deletes these files they are able to get in. ??

We've updated the video drivers.

Question: On a Novell network how do you have your communications protocols setup on the server and XP workstations.

 

[kscheeler]

What Novell client are you running. One approach would be to use an earlier client on the computers that are giving you an issue.

I don't have alot of clients left running Novell but the few that do are running SPX as their protocol even if they are running Novell 5.1 or higher.

Kevin Scheeler

 

[JDMiller]

We are on Novell 5.x. Various clients depending on when the PC was setup and what OS is on it. The network engineer says we should use Microsoft TCP/IP for the protocol. Is this true for Pervasive?