[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1330
  • Last Modified:

Server sits at blank desktop screen after failed update

We installed Citrix hotfix XAE500W2K8046 on Friday night to one of our two Citrix boxes.  We are running XenApp 5.0 for Windows Server 2008 x86. Both servers are in a Hyper-V VM.

Unfortunately, something went wrong during the install and it failed. There are no errors in the event logs but it hung at Removing Backup Files. After sitting there for over an hour we terminated the install and rebooted the server.

When we rebooted, the Citrix console showed that we had the patch installed vbut we could not login to the console, deskopt or published applications, we only got a blank desktop screen.

We uninstalled the patch yesterday (it took 4+ hours and 3 tries to get it off the machine) but no joy.

Now we are at a point where we can login with one domain admin account, the local admin account and one test (non-admin) user.

Our regular users and other admins can launch explorer.exe manually from task manager and UAC is disabled so I'm not sure why this is occurring.

There are no erors in the event logs, the permissions on the files all appear to be correct and the registry shows the same winlogon info that my good server does. Both Authenticated Users and Interactive User are part of the local users group.

The VM computer is on the other side of the country so I don't have the ability to drop in a CD to repair Citrix or the OS.

As part of my troubleshooting, I have tried forcing a GPO update in case that was it, this results in a WSRM event 119 - Windows System Resource Manager encountered teh following error 0x80010117.  User Name will not be logged in the subsequent event logs.

Has anyone come across this before? If so, what do I need to do to bring this up for tomorrow morning? All tips are appreciated.

Thanks in advance
0
fuzzysneekers
Asked:
fuzzysneekers
1 Solution
 
fuzzysneekersAuthor Commented:
Resolved - The install corrupted a portion of the user profile data in the registry.
We have roaming profiles so I copied the good NTUSER.DAT file from the server copied over to the local copy on the problem server.
In testing with several accounts this allowed the desktop/applications to load properly and the data was correctly loaded back to the roaming profile on the server.
0

Featured Post

Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

Tackle projects and never again get stuck behind a technical roadblock.
Join Now