[THIN] Re: IMA Service Failure

Is that available for XenApp 4.5? from the downloads ive only found an R04 for Presentation Server 4.0?
 
Meanwhile a reinstall of the R03 has fixed things so far . . :-)
 
The newly built machine is now working again, with the IMA service changed BACK (by the hotfix) to run as network service. Sweet!
It may be the order in which the MDT install calls the tasks or the MDT not giving the RO3 install enough time to exit...
 
Applying R02/3/4/5/1000's are always so frustrating!
 
Cheers
James

---

From: joe.shonk@gmail.com
To: thin@freelists.org
Subject: [THIN] Re: IMA Service Failure
Date: Sun, 24 May 2009 21:41:02 -0700

Have you tried R04?

 

Joe

 

From: thin-bounce@freelists.org [mailto:thin-bounce@freelists.org] On Behalf Of James Scanlon
Sent: Sunday, May 24, 2009 8:37 PM
To: Thin
Subject: [THIN] IMA Service Failure

 

Greetings list legends of the universe:
 
This one is driving me nuts. We are using MDT to build a Citrix XenApp server, FP1, W2K3 R2 SP2
 
If we add the R03 update as a build task, the server joins the farm, with errors, then on the second reboot (or restart of the IMS service) the IMA Service fails.
 
We get the following errors:
Popup: Windows could not start the Citrix Independent Management Architecture on Local COmputer...... service-specific error code
-2147483647
 
Event Viewer: The Citrix Independent Management Architecture service terminated with service-specific error 2147483649
 
Failures
Recreating the LHC, and radecache is successful but doesnt fix
Changing access permissions to TEMP directory doesnt fix a thing
Running CHFARM Fails: An Error occured while attempting to start the IMA service to the same farm or any other database (even local access farm)
 
Success
Changing the service to run as Local Service is the only thing that seems to work, but im reluctant to do that as all the other servers run as Network Service, but I Am concerned the service will not get all the required permissiosn it needs if running as local service?!?! I am however able to connect to a published desktop on ths trouble server/s
 
Removing R03 from the build process and applying manually after the full system build is the only thing that seems to work, which is not a solution as the systems need to build themselves with all latest updates....
 
Can we leave the IMA as local system?
Any advice appreciated!
 
 
 
James
 

---

Check out the new Windows Live Messenger Looking for a fresh way to share your photos?

---

Check out the new Windows Live Messenger Looking for a fresh way to share your photos?