Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
"Windows Home Server Connector is being upgraded" in System Tray RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote
    I am running WHS on an HP Mediasmart EX470 server from a networked Dell laptop. Since this morning, the Mediasmart icon in the System Tray is grayed out with a "lightning bolt" and the tooltip says "Windows Home Server Connector is being upgraded." It's been sitting like that for 3-4 hours now, with no obvious activity on the computer. How long is this "upgrade" supposed to take?
    Wednesday, March 25, 2009 4:41 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    Most likely until MS fixes Power Pack 2. Anybody know how to roll back to Power Pack 1?
    mathijs
    Wednesday, March 25, 2009 4:50 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    mathijs kok said:

    Most likely until MS fixes Power Pack 2. Anybody know how to roll back to Power Pack 1?

    mathijs



    RDP into your server and go control panel>ADD/REMOVE PROGRAMS>SHOW UPDATES> Windows Home Server Power Pack 2 (KB956587) [REMOVE]

    However, if you are having trouble, you should submit a bug to connect so we can investigate.

    Thank you
    Lara Jones [MSFT] | Program Manager
    Community Support and Beta | Windows Home Server Team
    Windows Home Server Team Blog
    Connect Windows Home Server
    Windows Home Server
    Wednesday, March 25, 2009 6:34 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    ajfisher said:

    I am running WHS on an HP Mediasmart EX470 server from a networked Dell laptop. Since this morning, the Mediasmart icon in the System Tray is grayed out with a "lightning bolt" and the tooltip says "Windows Home Server Connector is being upgraded." It's been sitting like that for 3-4 hours now, with no obvious activity on the computer. How long is this "upgrade" supposed to take?



    Hi,

    Did you have a beta version of Snoqualmie installed? The workaround is to uninstall the connector and then browse to your software directory and reinstall the connector.

    Thanks
    Lara Jones [MSFT] | Program Manager
    Community Support and Beta | Windows Home Server Team
    Windows Home Server Team Blog
    Connect Windows Home Server
    Windows Home Server
    Wednesday, March 25, 2009 6:35 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    No, no Snoqualmie. I'll have to try the RDP solution and will re-post later.
    Wednesday, March 25, 2009 7:13 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    AJ, nobody suggested that you RDP into your server.
    Rather, what was suggested you need to do on the problematic clients.
    On the client PC:
    Browse (across your network) to "\\servername\software\Windows Home Server Connector Software", and run Setup.exe (for a 64-bgit client, run WHSConnector_x64.msi.)
    This will uninstall the existing Connector on that client, and install the latest version.

    HTH,
    Chris
    [If this post helps to resolve your issue, please click the "Mark as Answer" or "Helpful" button at the top of this message. By marking a post as Answered, or Helpful you help others find the answer faster.]
    Thursday, March 26, 2009 12:05 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hmm, OK, well I already RPD'd into the server and uninstalled Power Pack 2, for whatever that's worth. Server rebooted, rebooted laptop. I'm currently re-installing the Home Server Connector as you suggested. Question is, should I then try to install Power Pack 2 again? Are people having problems with Power Pack 2?
    Thursday, March 26, 2009 12:39 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Installed yesterday; so far, no issues.
    The Win7 and Vista machines automagically updated the Connector on their own; the XP boxen might have got there on their own, but, I updated them manually after the server rebooted (and, after the Win7 and Vista boxen took care of themselves.)
    [If this post helps to resolve your issue, please click the "Mark as Answer" or "Helpful" button at the top of this message. By marking a post as Answered, or Helpful you help others find the answer faster.]
    Thursday, March 26, 2009 2:53 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    ajfisher said:

    Hmm, OK, well I already RPD'd into the server and uninstalled Power Pack 2, for whatever that's worth. Server rebooted, rebooted laptop. I'm currently re-installing the Home Server Connector as you suggested. Question is, should I then try to install Power Pack 2 again? Are people having problems with Power Pack 2?


    I would.  My guess (considering the icon was a lightning bolt which is for backups) is that your server was backing up at the same time PP2 got installed and rebooted your server.  I would install it again (except this time do it through the Console yourself, don't wait for AU to do it.)
    Thursday, March 26, 2009 4:08 AM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    I have the same problem ""Windows Home Server Connector is being upgraded" on two laptops, under Visa Business and Vista Ultimate.
    Showed after the HWS auto-upgraded to SP2. Can't believe this passed QA.

    Wednesday, May 27, 2009 8:44 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I have the same problem ""Windows Home Server Connector is being upgraded" on two laptops, under Visa Business and Vista Ultimate.
    Showed after the HWS auto-upgraded to SP2. Can't believe this passed QA.


    It sounds to me like it's updating automatically, just as designed.  If you have a specific problem, please start a new thread and post as many details as possible.
    Wednesday, May 27, 2009 11:54 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    I have had the same problem now for few days with all the 3 computers in network. All of them shows "Windows Home Server Connector is being upgraded". Notting happens even if I have keept them on over the night and days. Backup is not working with any of the computer nor any of them connect to homeserver. Shared folders are available for all the computers in the network. When no updates available for homeserver nor XP with Windows Update, I suppose all the computer are updated.

    Today I tried reinstall Homeserver Connector for 2 different XP PC. Upgrade goes otherwise ok but can't configure backup. Therefore it removes the whole WHS Connector installation in end of installation.

    Then I started to study what could be wrong with home server.
    I notticed the Backup Service in homeserver is not running at all. It, as well as Drive Extender Migrator Service were stopped and disabled. Waiting or rebooting didn't help. In the event log there was one event ID: 7022 from each restart for Drive Extender Migration Service.  I changed both to be with automatic start and started them. Then WHS Console finally started when earlier it just reported backup is not running and didn't start.

    Now both those services are starting after reboot of the homeserver, but still one event ID: 7022 from each restart for Drive Extender Migration Service comes to System log. However both services are on.

    What coud I check next?

    WHS Archiver and Drive Letter Service are disabled. WHS Computer Backup, Port Forwarding, Storage Manager and Transport Service are "Started". Now my WHS Console starts well in the homeserver which is now having screen, mouse and keyboard for trouble shooting, but just complanes none of the computers are backed up in last 5 or 6 days. From that I could guess something happend 5-6 days ago.  

    What coud I check next and how to fix this?


    Sunday, May 31, 2009 8:11 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I noticed the same thing on my HP 9200 Dual Core Entertainment Series Notebook machine the other day.  It's running Vista Ultimate 64 Bit and the Server is an EX475.  The Tray Icon turned Blue mid day like it was backing up.  It was doing the same thing yours is.  It only lasted 45 seconds or so though.  Here are the specs of the server:

    Bios Version of Media Server: R02     Friday, July 13, 2007

    Software Version: 1.3.8.25155

    Serial Number: CN67510FAN

    Windows Home Server With Power Pack 2

    Product ID: 78495-OEM-4211965-00077

    AMD Sempron™ Processor 3400+

    1.97 GB of RAM 

    Version Information on everything: 6.0.2030.2

    IT Genius
    Monday, June 1, 2009 1:09 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi
    I experience a similar problem.

    I upgraded to PP2 some weeks ago and no issues. Recently the system automatically updated to NET 3.5 sp1.
    Since then the connector on my VISTA (ultimate) machine try to upgrade and then abort with the error " the operation can not be completed at this time" .

    I tried to uninstall the connector and even the upgrade to net 3.5 sp1 but no results.

    Strange enough my othe PC Vista HOme seems to be OK.

    I have no problem accessing  in  RDC
    Monday, June 1, 2009 3:56 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Anybody been able to solve this problem?

    It seems to be so that all my home computers are asking update for Connector. When the update goes well up to the point where it is doing backup configuration, it takes long time and finally fails for unable to configure backup.

    The only error messages I have found from the folder: C:\Documents and Settings\All Users\Application Data\Microsoft\Windows Home Server\logs

    is in Connector_date_.log  like this:

    [2009/06/10 21:03:32  54c]   CClientConnection::Run ERROR: Wrong transport protocol version: partner version is 133038082, current version is 133038080, client software needs an upgrade.

    And in HomeServerClientSetup.log like this:
    21.30.59 6/10/2009 MSI returned 1602
    21.30.59 6/10/2009 MSI installer returned 1602
    21.30.59 6/10/2009 MSI returned cancellation code 1602 - rolling back via uninstall
    21.30.59 6/10/2009 Uninstalling old Q client
    21.30.59 6/10/2009 LOCATION_LOG: "C:\Documents and Settings\All Users\Application Data\Microsoft\Windows Home Server\logs\HomeServerClientMsi.log"
    21.30.59 6/10/2009 LOCATION_MSIEXEC: C:\WINDOWS\system32\msiexec.exe
    21.31.14 6/10/2009 MSI returned 0 for uninstallation
    21.31.14 6/10/2009 MSI un-installer returned 0
    21.31.14 6/10/2009 END: got to the end

    Are these telling anything for anyone?

    Wednesday, June 10, 2009 6:50 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi
    I experience a similar problem.

    I upgraded to PP2 some weeks ago and no issues. Recently the system automatically updated to NET 3.5 sp1.
    Since then the connector on my VISTA (ultimate) machine try to upgrade and then abort with the error " the operation can not be completed at this time" .

    I tried to uninstall the connector and even the upgrade to net 3.5 sp1 but no results.

    Strange enough my othe PC Vista HOme seems to be OK.

    I have no problem accessing  in  RDC

    What are the regional settings on the PC?
    Lara Jones [MSFT] | Program Manager
    Community Support and Beta | Windows Home Server Team
    Windows Home Server Team Blog
    Connect Windows Home Server
    Windows Home Server
    Wednesday, June 10, 2009 7:35 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    Anybody been able to solve this problem?

    It seems to be so that all my home computers are asking update for Connector. When the update goes well up to the point where it is doing backup configuration, it takes long time and finally fails for unable to configure backup.

    The only error messages I have found from the folder: C:\Documents and Settings\All Users\Application Data\Microsoft\Windows Home Server\logs

    is in Connector_date_.log  like this:

    [2009/06/10 21:03:32  54c]   CClientConnection::Run ERROR: Wrong transport protocol version: partner version is 133038082, current version is 133038080, client software needs an upgrade.

    And in HomeServerClientSetup.log like this:
    21.30.59 6/10/2009 MSI returned 1602
    21.30.59 6/10/2009 MSI installer returned 1602
    21.30.59 6/10/2009 MSI returned cancellation code 1602 - rolling back via uninstall
    21.30.59 6/10/2009 Uninstalling old Q client
    21.30.59 6/10/2009 LOCATION_LOG: "C:\Documents and Settings\All Users\Application Data\Microsoft\Windows Home Server\logs\HomeServerClientMsi.log"
    21.30.59 6/10/2009 LOCATION_MSIEXEC: C:\WINDOWS\system32\msiexec.exe
    21.31.14 6/10/2009 MSI returned 0 for uninstallation
    21.31.14 6/10/2009 MSI un-installer returned 0
    21.31.14 6/10/2009 END: got to the end

    Are these telling anything for anyone?


    Hi,

    What is the OS for the clients?
    Lara Jones [MSFT] | Program Manager
    Community Support and Beta | Windows Home Server Team
    Windows Home Server Team Blog
    Connect Windows Home Server
    Windows Home Server
    Wednesday, June 10, 2009 7:36 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi I solved my problem  as indicated in this thread
    http://social.microsoft.com/Forums/en-US/whssoftware/thread/ed82d28c-0936-4782-8414-29c6a434b205

    Baiscally I had to replace the ASP.NET to 2.0 in the ISS propriety.

    I suspect it was the installation of teh updated to .NET 3.1 sp1 that created the problem on the server.

    Regards

    Alfio
    Wednesday, June 10, 2009 8:59 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I noticed that you referenced the .NET 3.1 SP1 update. What are the regional settings on the machine and was the language pack installed?

    Thanks
    Lara Jones [MSFT] | Program Manager
    Community Support and Beta | Windows Home Server Team
    Windows Home Server Team Blog
    Connect Windows Home Server
    Windows Home Server
    Wednesday, June 10, 2009 9:04 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi 

    Th eserver is set up in ENGLISH  (US) with Keyboard in Italian

    Two Client are in ENGLISH US one with Italian Keyboard and teh other with German Keyboard

    and one client is in German with German Keyboard

    Regards

    Thursday, June 11, 2009 8:18 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi,

    All the Clients I have been working with this are on Windows XP Pro. Two english and one Finnish versions. All of them with Finnish keyboard. I also have one Chinese XP Home laptop with Chinese/English keyboard, which is also asking update for Connector, but I haven't been trying yet to update connector in that one when it is bit more challencing to read error messages in Chinese if something goes wrong. However, the Connector in that one is not able to connect to homeserver eighter.

    The Homeserver is english version with Finnish keyboard. Homeserver and all of the computers are having "Standards and formats" = Finnish and "Location" = Finland.

    Regards,

    Terola
    Friday, June 12, 2009 9:19 PM