Error 179

[AKPolarBear]

Following thread639-568428, I am also having this issue as we move to 2 new TS servers that are currently W2K. These will go to W23K once the rest of the application servers are upgraded.

We are starting to get these errors now. Does anybody have an update?

One of the suggested fixes is installing the Macola software on each TS. Has this proven to be effective? Does violate any Macola license agreements (not that it would really matter at this point.)

 

[abaldwin]

No real updates here. Been dealing with this forever it seems. The only thing that seems to make a definite difference for us is the number of users on a TS running macola. Once you breech a meesly 9 user this error seems to be more prevelant. Under 9 and the problem does not surface for us.

Now that is:
1. Very low useage for a TS server today.
2. Does not rule out that a few of the users were doing something that caused it. (I believe I posted in the prior thread about using the X to close Macola applications).
3. The installation of Macola should be done as a normal client software. The macola infomine says to move the actuall application to the server and have it become the app server. This is directly disputed in one of their other fixes. Fact is they do not know how to fix this. I still think it is a memory leak issue with closing forms using the "X".



Andy Baldwin

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

 

[kscheeler]

As I wrote in the thread you referenced, on all of the sites that I've had to implement installing Macola on the TS locally, it's corrected the issue.

To answer your other question on licensing, download and read Macola's support document 01.559.508 which is their answer to the 198 / 179 errors on Citrix and Terminal Server.

And as well in your situation, it's a temporary fix until you can upgrade them to 2003.

Kevin Scheeler

 

[AKPolarBear]

Thanks for the update. I have that Macola article under my elbow. I should have known there would be a Macola issue of some sort during this TS upgrade.

Installing the Macola apps on the TS's makes sense for the problem but does not make sense for the TS's operation. We are using 2X Load Balancer program so each server will end up handling more than 9 users, maybe 15 - 20 each. I do have W23kRC2 in hand destined for those terminal servers. Any issues in upgrading to that with Macola version 7.6.100a?

One observation is that this issue has come up twice this week, both in the late afternoon. Yesterdays came as I was adding 5 users to the new network and they were logging on and off and in and out of Macola for the first time. This was on top of normal Macola load from the users still accessing through the NT TS. The first issue came up with only 4 users on the new network, now I have 9 or 10.

Doing nothing but waiting a few minutes allowed at least one of the users to log back on. The others had already switched back to the NT version and had no issues. This points to some sort of timing issue within the Macola application itself and the TS's and maybe SQL (all of which use the same W2K version).

The Red X issue has been long known and its use is discouraged here when users are first Macola trained. Some appear to have forgotten that.

Also my SQL and Application server are on W2K Advanced. Any problem leaving those alone for now and still working with W23K?

Finally, we still have some NT servers in the mix. This is the big reason we did not upgrade straight to W23K for all servers -incompatibility. We have created a mixed NT/W2K network that has become AD controlled for the most part. We are still in the testing mode and finding little surprises like the Macola issue.

 

[abaldwin]

Even more evidence of memory leaks in Macola. The "X" that I am speaking of is not the Red X on the menu bar but the normal Windows "X" or close window button found in the upper right corner of most windows programs.

Andy Baldwin

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

 

[AKPolarBear]

As I add more users to the new network and TS's, we are now experiencing more than just 179 errors. Printer issues, messages that say a .lbr version is not compatible, error messages when creating shortcut icons, general errors during a process, etc. All these go away when the user exits Macola and goes back in and it works the next time.
Except for the icon issue. I watched a user create them a couple of days ago and each one produced an error but placed the short cut anyway. They worked for the next 2 days and then this morning they were all gone. I first suspected that the user logged on to a different TS and it is an issue with the profile but that appears unlikely to not have happened by now. Besides, with the load balancer in use, all users have to use roaming profiles so all the user information is in one place on the AD server and not on the terminal servers. Maybe this is an issue with Macola although we use roaming profiles now on the single NT TS.
Just more quirks we are finding as the user load went up. Others report no issues at all and they are heavy users of the Macola apps.

I also discovered that some users are using the esc button to close screens and have advised them to stop doing that.

Are these issues related to the same general reason that caused the 179 problem?

 

[AKPolarBear]

Does the above W2K problem also affect individual user settings? Users are saying that some of the screen preferences are not being saved. However, shortcuts are being saved. Do some things get stored in the roaming profile or local profile and others in the TS registry? This could explain issues with multiple Term Servers.