Can't connect WHS

All replies

• 

  

  0

  Sign in to vote

  i have had WHS (on my HP EX485 MediaSmart Server) since Nov. 2009 and i still cannot install it to connect to or back up my Gateway 500S+ (Win XP Home/SP3) computer.  HP has spent hours on the phone with me working on this problem but since their server is working and is installed properly on my 2 other computers, they say the problem is a Microsoft software issue and they cannot fix it.  I recently ran the Microsoft Live Safety Center scan which fixed > 800 registry issues on my Gateway computer, but when I tried again to run the WHS connector, it would not install/connect with the server.  The error message displayed has always been: Unable to Install Windows Home Server Connector; Unable to register remote desktop control.  I have run the MS Home server connector troubleshooter, but it has not identified or fixed the problem.  I am hoping that Microsoft will provide support to fix this software problem since the conflict appears to be between 2 different Microsoft operating systems.

  You might try looking at this thread or this one and see if it helps...

  Tuesday, February 16, 2010 1:35 AM

  Moderator
• 

  

  0

  Sign in to vote

  I tried the first thread but had no manage PC access problem.  Tried second unsucessful thread and had no issues except for step 3 of the WHS Troubleshooting article where I had a certificate error but continued on to the specified address and saw <ID>1</ID> instead of
   <ID>2</ID>.  So I tried MS article 939218 even though it didn't seem applicable to my error messages.  I modified the registry key as specified but WHS connector would still not install. I can ping the WH server so I may have the Win XP SP3 bug that Olaf described.  Then tried regsvr.exe mstscax.dll and got the same error as Dans_M - "DllRegisterServer in mstscax.dll failed.  Return code was: 0x80020009"  So all I can see left from the thread is to try to do a repair Win XP installation with Slipstreamed SP3 per Olaf.  But I don't know what "slipstreamed SP3" is or even if it is available.  So I'm about to give up and just manually backup this older computer with Retrospect.  If anyone sees anything else that I can do, I would appreciate the advice.

  Thursday, February 18, 2010 2:49 AM
• 

  

  0

  Sign in to vote

  I tried the first thread but had no manage PC access problem.  Tried second unsucessful thread and had no issues except for step 3 of the WHS Troubleshooting article where I had a certificate error but continued on to the specified address and saw <ID>1</ID> instead of
   <ID>2</ID>.  So I tried MS article 939218 even though it didn't seem applicable to my error messages.  I modified the registry key as specified but WHS connector would still not install. I can ping the WH server so I may have the Win XP SP3 bug that Olaf described.  Then tried regsvr.exe mstscax.dll and got the same error as Dans_M - "DllRegisterServer in mstscax.dll failed.  Return code was: 0x80020009"  So all I can see left from the thread is to try to do a repair Win XP installation with Slipstreamed SP3 per Olaf.  But I don't know what "slipstreamed SP3" is or even if it is available.
  
  

  It means an XP image with Service Pack 3 already added into it (so that when you install, SP3 is already there).  As for availability, you would probably have to create your own slipstreamed image.  A quick internet search for "XP slipstream" should point you in the right direction.
  
  

  So I'm about to give up and just manually backup this older computer with Retrospect.  If anyone sees anything else that I can do, I would appreciate the advice.

  You could always do a fresh install of XP on a different hard drive, then copy your data over from the original drive (not the most elegant solution, but it should work).

  Thursday, February 18, 2010 3:13 AM

  Moderator
• 

  

  0

  Sign in to vote

  I can access/control the MediaSmart server from another computer.  So the only reason I wanted to connect to the server with this older unit was for the automatic backups.  But it looks like my remaining options are much more burdensome than the manual backup/restore process that I have already set up on the old unit.  So that will be my approach.  But thanks to all for the help that was offered.

  Thursday, February 18, 2010 11:53 PM
• 

  

  0

  Sign in to vote

  Have you tried searching for the error message you've been seeing? Here's a Google search , and here's one from Bing . The solutions I see in the top few hits are a possible fix for your problem.
  
  Failing that, you may have some sort of subtle OS misconfiguration on your client. Unfortunately, as a practical matter it's often faster to back up your data, then wipe and restore the computer from the manufacturer's original recovery disks, rather than trying to find and fix the actual problem.

  ---

  I'm not on the WHS team, I just post a lot. :)

  Friday, February 19, 2010 12:23 AM

  Moderator