Macola error function: 00920 pf-display bitmapstatus:

[JDMiller]

We are running Macola Progression on Pervasive SQL windows server. We have not had any issues for a couple years now.
Today however our users happened to begin getting an error when trying to open Macola that we have never seen before.

function: 00920 pf-display bitmapstatus:
00006 No more memory

We thought a server reboot resolved the issue but we have since found that if users wait and then retry they can then open Macola.

We don't believe it is workstation related because the error will occur with multiple users randomly and then stop.

 

[dgillz]

There is nothing on this anywhere as near as I can determine. What does Exact say? What version of Progression and Pervasive are you using?

Software Sales, Training, Implementation and Support for Macola, Synergy, and Crystal Reports. Check out our Macola tools:

http://www.gainfocus.biz/exceladdin.html

 

[JDMiller]

We have not spoken to Exact. Our VAR has documentation on this occuring on workstations but it does not seem to apply.

We are running Macola Progression 7.6 400a on Pervasive SQL v9 SP2 for Windows.

I have not seen any errors in the Pervasive log file.

 

[dgillz]

I would bump this up to Exact. This one is real strange to me and I thought I had heard them all.

Software Sales, Training, Implementation and Support for Macola, Synergy, and Crystal Reports. Check out our Macola tools:

http://www.gainfocus.biz/exceladdin.html

 

[JDMiller]

Another odd bit of information:

If you click OK to the errors Macola will come up and allow you to login but then the entire left menu panel is blank.

 

[NEmacGuy]

Any customizations ? I hit something just like this, drove me nuts, in the end could only determine is it the server, workstations, Macola Programs, or the Data. I went with the easiest thing to rule out first, the Macola Programs, your said your btrieve 9 which makes life easy at one level. I would install Macola 7.6.400 in a non-productions enviroment, update it to service pack A. I would rename the Macola Root directory. Now you would need to figure out if you have any customizations and then go about splicing together the fresh install and my live environment <Data, Screens, PWE, Rpts...>. Note: I still have everything in my renamed Macola Root directory, should things go bad, switch the directory names around and you are where you started. It also a dam good idea to have a backup before you start this process.
Issue went away. Eventually traces issue, not to missing files, but an extra DLL file in their Macola Root directory.

One other possible idea to share. Query Macola Font issues, or Panels. Perhaps you installed some new software recently and have corrupt font.

 

[NEmacGuy]

Today is your luck day. Sometimes you hit an issue that rack your brain. Dug out the cobol source code and tried to figure out how to read the stuff.

Net thing points to you have an issue with the following file : Mbitmp32.dll.

The old installing a fresh copy would work, but you should be able to just get the right version of this file and you will be back in business. If you rename this file you get you exact problem.

Hope this helps.