Progression 7.5.102e Error on Windows 2003 Server 1

[norrisar]

I currently have the following setup:

Machine A - Windows 2000 Server (Application Server)
Machine B - Windows 2000 Server (Terminal Server)
Machine C - Windows 2003 Server (Print Server)

Machine A hosts Progression 7.5.102e and PervasiveSQL 2000i SP3, serving approximately 14 local users. Machine B serves approximately 11 remote users running Progression from Machine A. Machine C is used solely to run custom MS Access reports for branch managers at 5 remote locations.

In an effort to alleviate 1) the load on Machine B and, 2) confusion on the part of the branch managers, I am attempting to run Progression from Machine C. When I run Progression on Machine C, either locally or in a Terminal Server session, I get the following error message:

Execution error : file 'TRIGGER'
error code: 114, pc=0, call=-1, seg=0
(Signal 11).

Does anyone know what causes this error? Could it be an incompatibility with Windows 2003 server?

 

[dgillz]

If machine A hosts Progression, how can you be attempting to run Progression from machine C? Please explain in detail.

Software Sales, Training, Implementation and Support for Macola, eSynergy, and Crystal Reports

http://www.gainfocus.biz

 

[norrisar]

dgillz

Machine A is the Application Server on which Macola, as well as the Pervasive database are installed. Machine C has a maped drive to the Macola directory, from which I ran the Macola Setup program for clients. This essentially sets up the data connections to the server and provides a shortcut to the Macola executible which resides on the Application Server, Machine A; a typical client/server environment.

This solution works on all the local XP clients as well as on the Windows 2000 Server Terminal Server, Machine B, which remote clients use to execute Macola.

I installed Macola on Machine C in the same manner as the local clients and the Terminal Server, Machine B. I only have problems running Macola on Machine C, Windows 2003 Server configured as a Terminal Server.

Anthony Norris
CFO/CIO
Desert Gem Trading/Noble Tile Supply

http://WWW.NOBLETILE.COM

 

[keain]

The Trigger error is most likely because of Pervasive. To run on Windows 2003, either in server or client mode, Pervasive has to be P.SQL 2000 sp4 with all post sp4 hot fixes applied.

That's were I'd start. Both sp4 and all post sp4 hot fixes can be found on Pervasive's website.

 

[dgillz]

Macola has dropped support on Pervasive 2000 as of June 30th. You need to be running Pervasive v8.5.

Software Sales, Training, Implementation and Support for Macola, eSynergy, and Crystal Reports

http://www.gainfocus.biz

 

[keain]

The thing is, that he can't run 8.5 with 7.5.102c. So, if he wants to get this running on W2K3, he'll need to update Pervasive 2000 as far as it'll go.

 

[norrisar]

First off, thank you for your responses. I have downloaded SPK4 as well as the follow up hot fixes and will apply ASAP.

As for the versions of Macola and Pervasive, I would love to move to the latest version of Macola and migrate to SQL Server; however, my hands are tied. The owner, President, and CEO(one in the same) does not see the business need to upgrade at this time.

Again, thank you for your responses. I will post results once implemented.

Anthony Norris
CFO/CIO
Desert Gem Trading/Noble Tile Supply

http://WWW.NOBLETILE.COM

 

[keain]

Good luck. Hopefully that will cure your issues.

 

[MacolaHelp]

I have a client running 7.6.100a on a 2003 server with pervasive 2000i sp3 successfully using primarily win2k workstations. I wouldn't think that you could run a macola client from a 2003 server, though, in your description of machine C. You should be able to update your macola to 7.6.300a, since pervasive 2000i was still supported when it was released. Do you have custom mods or something that are keeping you on 102? There have been lots of fixes and corrections since 102.

 

[norrisar]

I have found this issue is not related to Macola or 2000i but rather Windows 2003 server. See MS article regarding Data Execution Prevention by following this link

http://support.microsoft.com/kb/875352.

The following excerpt details the solution:

1. Click Start, click Run, type sysdm.cpl, and then click OK.
2. On the Advanced tab, under Performance, click Settings.
3. On the Data Execution Prevention tab, use one of the following procedures:
• Click Turn on DEP for essential Windows programs and services only to select the OptIn policy.
• Click Turn on DEP for all programs and services except those I select to select the OptOut policy, and then click
"Add" to add the programs that you do not want to use the DEP feature.
4. Click OK two times.

After modifying the DEP settings Macola was able to execute without installing 2000i SP 4 and all post SP 4 hot fixes.


Anthony Norris
CFO/CIO
Desert Gem Trading/Noble Tile Supply

http://WWW.NOBLETILE.COM

 

[jake29]

How about popping over to this thread and giving stravis a bump for his solution to this problem.

http://www.tek-tips.com/viewthread.cfm?qid=1134722