escutler
asked on
When I run the Presentation Server Console, it kills the IMA service on that farm member. I need to find a fix for this. Thanks.
I can restart the IMA service, but as soon as I try to connect to a given farm member with the Presentation Server Console, it kills the IMA Service on that server. Any help on how to fix this would be greatly appreciated. It gives a Event ID of 7301 from the Service Control Manager when it kills it.
We are running XenApp 4.5 on Windows Server 2008 32-bit.
Thanks.
We are running XenApp 4.5 on Windows Server 2008 32-bit.
Thanks.
What Rollup are you using? I know there was an issue in 4.5 and IMA crashing, but it was related to Installation Manager. Can you duplicate this on another server with the console?
XenApp 4.5 will not run on Server 2008 so you must be running XenApp 5 for Server 2008 which is a different product than XenApp 5 for Server 2003.
You could have either local host cashe corruption or data store curruption.
dsmaint /recreatelhc and try again. Then try dscheck.
You could have either local host cashe corruption or data store curruption.
dsmaint /recreatelhc and try again. Then try dscheck.
ASKER
Sorry about the mistake folks, but we're actually running XenApp 4.5 on Windows Server 2003 (64-bit). I'm getting my builds confused. We are on Roll-up 3. I've tried recreating the local host cache, and that didn't solve my problem. When I ran the dscheck without any switches, I get this:
C:\>dscheck
Data Store Validation Utility. Version: 6.23
Installation Job Information for Unknown Servers
-------------------------- ---------- ---------- --
No Installation Job Records Found
MSI Installation Job Information for Unknown Servers
-------------------------- ---------- ---------- ------
No MSI Installation Job Records Found
ADF Installation Job Information for Unknown Servers
-------------------------- ---------- ---------- ------
No ADF Installation Job Records Found
Finished data store validation.
C:\>dscheck
Data Store Validation Utility. Version: 6.23
Installation Job Information for Unknown Servers
--------------------------
No Installation Job Records Found
MSI Installation Job Information for Unknown Servers
--------------------------
No MSI Installation Job Records Found
ADF Installation Job Information for Unknown Servers
--------------------------
No ADF Installation Job Records Found
Finished data store validation.
Is the IMA Service being killed on the target server or the server running the PS Console?
ASKER
We have 5 farm members, four for production (serving out apps) and one as the Data Collectpr and License Manager. The behavior is the same for all servers. When I run the PSC against a given server, it kills the IMA service on the server that is running the PSC. I normally target the PSC on the same server that I'm running it from. I've tried recreateing the lhc on each server and that didn't seem to make any difference. I've had another SA tell me that it's probably an Installation manager issue with a corrupted job, but how do I find which one is corrupted, & how do I get rid of it? Thanks.
How many thousands of users do you have? How many hundreds of applications or desktops are you publishing? Just curious why in such a small farm you have a dedicated Data Collector?
ASKER
Thanks Carl. I've looked at the link and it didn't seem like our issue. We only have approx. 50 concurrent users, but that is going to go up to about 150-200 soon. We have approx. 35 apps, some of which are fairly resource intensive (ArcGIS, Adobe prods, & some dev tools for the Arc prods). I've been looking for something to resolve the IM jobs issue, but I can't use the PSC to even look at the IM jobs. I've ran each of the dscheck /Full on each of the targets with the clean option (after backing up the datastore), and they didn't come up with any significant errors or fixes. Any way to look at the IM apps and jobs without using the PSC? Thanks.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
The problem will need to be resolved with Citrix Support. Carl gave me some good suggestions to try, but they did not resolve the issue. Good effort though. Thanks.