error code 114 on Term server install

[mfreff]

I am running 7.5.103f on SQL 7.0, and the system is running fine on standalone workstations. I am trying to set up a terminal server for the first time and am getting an error trying to start Macola "Execution error: file 'TRIGGER' error code:114, pc=0, call=-1, seg=0 (Signal 11)" I know this is probably a Terminal Server issue, but I am not having any luck in those forums. I have a W2K3 SP1 server running TS against a W2K server running Macola/SQL. Any suggestions as to a starting point would be appreciated. Thanks.

 

[NEmacGuy]

There are a few other posts currently with almost the same issue. Check them out below.

First thing to mind is mapped drive issue. Macola has to be run from a mapped drive. Next thing to mind is Windows 2003 server - security issue settings.

 

[mfreff]

I have the drive mapped to M, as I do all the other workstations. I have set Terminal Server to run in Relaxed Security mode, and am attempting to run Macola logged in to the machine as a Domain Administrator.

 

[kscheeler]

For TS2003 it should work fine from a mapped drive. Make sure you install Macola / Flex from Add/Remove programs and are logged in as Administrator.

Do you get the same error message running PWE as Progression Explorer?

Kevin Scheeler

 

[mfreff]

I don't know what PWE is. I found a Tech Note referring to Progression SQL V7.5.103 installation on W2K TS, which referenced some changes to the macola7.ini file. (didn't help me) We have not renewed our support contract and so can't access the Exact support site. Can anyone tell me if there is a Tech Note describing post installation actions for 7.5.103f on W2K3 TS?

 

[erpgooroo]

I advise paying your maintenance, upgrading to 7.6.300a, and upgrading to SQL Server 2000. You have probably wasted more time and company resources by not paying maintence and not getting your answer directly from the Exact Customer Portal.

 

[mfreff]

Thanks for the tip, but that is a business decicion beyond my control, and doesn't ease the frustration I am feeling "in the trenches".

 

[kscheeler]

PWE stands for Progression Workflow Explorer. There are two executables to Access Macola. Macola32.exe and PWE.exe. PWE gives you some additional functions like tabs for sorting shortcuts and the ability to run the Crystal Integrated reports within Macola.

It's also possible that you can get a different error message running one vs. the other.

Kevin Scheeler

 

[AKPolarBear]

Error 114 is a bit of a catch all error from what I have learned.

One place to look is the setting in the macola7.ini file. Make sure it is pointing correctly to your drive and program locations. Make sure the drive is mapped with full access to all users.

 

[MacolaHelp]

Did you install macola on TS by using add/remove programs? Do all users have registry permissions to hkey local software macola, odbc, etc? Do the users have rights to the directory(ies) where their own macola7.ini resides? In w2k3 you have to explicitly grant these rights rather than deny as in previous versions. There has been a lot of discussion about installing the macola programs on the terminal server to correct various issues with an sql installation of macola.

 

[AKPolarBear]

In our experiences, installing Macola on our Citrix Metaframe/NT Term server would bring the whole system to its knees. We are already overloading it. We run Macola and SQL on separate (dedicated) servers and it normally runs just fine mapped to the Macola server from the Term Server. This morning was a different story for some odd reason, but that will be a different post and was an SQL issue. During a recent move from older to newer servers, error 114 was encountered. Most were resolved with changes in user permissions on the SQL server. A former VAR initially set up our SQL server with all users having a dbo permission level. No wonder it worked so well! When we rebuilt the new server, those user permissions did not get that level of permission and thus we started have 114 errors along with other issues.