Frustrating Xenapp 6.5 Issue - 2 servers

ashrobbo · 19 Apr 2014 at 12:41

Hi Guys,

2 server in a 4 server farm are showing the following symptoms

- Plug and Play service does not start on boot
- Power server does not start on boot
- Lots of print spooler crashes previous to this.

Trying to manually launch the plug and play succeeds - but i shortly get 'this server must shutdown because of a dcom error'

I cannot manually launch the power services I get an access is denied 5 message. Running procmon doesnt show any access denied results. Event logs not showing anything helpful.

as a final straw I removed Xenapp and all of the services start ok.

Ive removed all print drivers from the server and even ran the microsoft fixit which removed all custom print keys etc - still to no avail - im thinking the print issues were a side effect.

Citrix patches are the same on all 4 servers - 2 of which are working fine (with the same list of printers). Im at a loss of what to do. All servers are Xenapp 6.5 Rollup 3.

sfc /scannow brings back no errors, disk check also completes ok. AV uninstalled still no joy.

Uhtred · 20 Apr 2014 at 07:27

Personally I'd just format the two servers in question, it almost sounds like malware

ashrobbo · 21 Apr 2014 at 13:06

Uhtred said:
Personally I'd just format the two servers in question, it almost sounds like malware

I built a brand new server (virtual) - didnt even patch it (only sp1) and reinstalled Xenapp and the issue reoccured!! absolutely no idea, im thinking maybe corrupt install files?

I've done a malwarebytes scan, tdskiller and all sorts just to be sure. Been tearing my hair out and wasted my whole Bank hol weekend

Baz · 23 Apr 2014 at 07:42

Firstly, is installation of in-box printer drivers checked, it is recommended to never install printer drivers on any Xenapp servers, one main culprit is the HP universal printer driver which is a pain to remove.

If you only have basic printing needs, use the Citrix universal printer driver only, if you have complex printing requirements, create a print server and use the Citrix universal print server software.

Having seen the HP universal print driver in many environments, it is a really bad piece of software, and causes so many unrelated printing issues I would start there, especially if a fresh install is knackered.

anything I don't mind · 23 Apr 2014 at 20:58

Only other thing i can think of is third party software like a virus scanner or group policy that is interfering and causing problems but if its only two of 4 and then a new server has the same symptoms. That is very strange behaviour.

Only other thing i can think of is that the other two xenapp servers have not been rebooted for a long time and thus have not displayed a problem that has occurred due to an update of .net or something like that.

ashrobbo · 27 Apr 2014 at 01:44

anything I don't mind said:
Only other thing i can think of is third party software like a virus scanner or group policy that is interfering and causing problems but if its only two of 4 and then a new server has the same symptoms. That is very strange behaviour.

Only other thing i can think of is that the other two xenapp servers have not been rebooted for a long time and thus have not displayed a problem that has occurred due to an update of .net or something like that.

My thoughts exactly, all 4 servers reside in the same OU and have the same GPO's applied. I've been through the policies to make sure but nothing has changed and nothing is disabling any services. I rebuilt the one VM again and all now appears to be OK.

Rebuilt the physical (again) and have the same issue. Removal of Xenapp the the server service starts successfully aswell as the plug and play and power services. A procmon scan of trying to start the power service gives no access denied's - a couple of name not found's but this is the same on all other servers.

I'm wondering if its the order i'm installing things, I tend to get 2008R2 installed - windows update totally then install Xenapp then HRP03 rollup then the apps. I tend to leave the AV until last to rule out any issues there.

Could be some sort of windows update interfering - but far too many to tell which one it may be.