Load Error 179 and Citrix

[Clundey]

I am currently suffering the load error 179 on my Citrix XPa farm after upgrading Win2k to sp3. Have tried all the reg hacks etc. to minimize the errors, but they still appear. Re-booting nightly seemed to really minimize the frequency, but still a problem.
Rolling back to sp2 is not an option for me. The next step seems to be to copy the apps folder and re-install the client to the citrix servers. I have been reluctant to do so as yet.

Does anyone have a similar setup/problem?
What, if anything are you doing? Is that a viable option? What about 7.6.100a?

I'm still on 7.5.103f due to vba customizations.

Thanks in advance for any assistance!

Chris

 

[vbajock]

If your vba custmonizations were done through Flex going to next version should not be a problem.

 

[jdavissrusa]

I had the same problem at my old employer, we tried to resolve it many different ways and SP2 is not the answer no matter what Macola says. In my opinion Macola hides behind the "SP3 blame game too much".

We did roll our servers back to SP2 and it did not solve the problem.

Before I left the company we were down to one solution and you already know it...load Macola directly to the Citrix servers.

Now at my present job I was "lucky" enough to land a job where I am dealing with Macola again (Actually the reason I was hired on) in a much smaller enjoinment.

The company was using Term Server to propagate Macola to remote users and in BTR and we received 179 codes daily, I brought up and new server and converted Macola to SQL and running SP3 have not experienced a single 179 error.

The difference is Macola is loaded locally on the term server.
I knwo this is not the answer you were looking for and it didn't help the situation one bit, but it shows your not alone in your problem.

 

[chadt]

I had to deal with this problem for over 6 months. There are only 2 solutions that will get rid of the error. Its a connection issue when going through Citrix. Either put your Citrix box on NT4 (sounds dumb...but it works) or install macola directly on to your SQL box.

 

[Clundey]

We are running a 2-server XPa farm, so unfortunately downgrading to NT4 is out.

How did you handle the Macola drive mappings for multiple Citrix Servers?

The Citrix users have roaming profiles, so won't that mess up the drive mapping when they logon?
Citrix and non-citrix Macola users have "net use s: \\macolaserver\apps" currently in their logon script.

How did you differientiate now between say, "net use s: \\citrixserver1\apps" and
"net use s: \\citrixserver2\apps" ??

I've still got a NT4 domain.