Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Cannot install Connector software on Win7 x64 - error - This operation cannot be completed at this time RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello,

    I've a Windows 7 x64 client and Acer Aspire EasyStore H340 HomeServer with PP3.
    I usually do not connect to my home server (terminal services or connector) though from a few weeks (may be months) back when I try to connect via the connector, it will not be able to connect to the WHS.

    I installed the Connector troubleshooter kit and got several issues:

    The version of the Connector software does not match the version of Windows Home Server
    Cannot connect to the server backup
    Cannot connect to the server internal Web site (ASPX page)
    Cannot connect to the server internal Web site (password hint page)
    Cannot connect to the server secure internal Web site
    Cannot connect to the server internal Web site (simple page)
    Cannot connect to the server internal Web services
    Cannot connect to the server internal secure Web services
    Name resolution failed
    Windows Home Server Beacon discovery failed

    I uninstall the connector software, rebooted my client computer and tried to reinstall the connector software from \\servername\Software\Home Server Connector Software

    Now I get this error immediately after entering the Admin password on Connector install.

    "This operation cannot be completed at this time. Please try again later. If the problem persists, please contact product support."

    I would note that I am able to connect to WHS via terminal services.

    Here's what my folder "\\servername\Software\Home Server Connector Software" looks like

    Most of the file version are 6.0.2423.0

    12/17/2009  12:38 PM    <DIR>          DOTNETFX20
    10/07/2009  02:48 PM           224,104 setup.exe
    10/07/2009  02:16 PM        15,460,352 WHSConnector.msi
    10/07/2009  02:48 PM         1,103,720 WHSConnectorInstall.exe
    10/07/2009  04:45 PM        16,396,800 WHSConnector_x64.msi
    10/07/2009  02:48 PM            41,320 WHSVersionUpgrade.dll
    10/07/2009  04:11 PM            43,880 WHSVersionUpgrade_x64.dll
    02/20/2009  05:28 PM            43,283 WHS_ConnectorHelp.chm
    12/17/2009  12:38 PM    <DIR>          WindowsInstaller31

    The version information when looking through the console via terminal service is as follows

    Windows Home Server Console: 6.0.2423.0
    Windows Home Server Backup & Restore: 6.0.2423.0
    Windows Home Server Drive Extender: 6.0.2423.0
    Windows Home Server Remote Access: 6.0.2423.0
    Windows Home Server Storage Manager: 6.0.3039.0


    I've spent too much time now on this... sifting through the articles on net and trying to fix it by myself but no luck.

    I am hoping that there are folks out there who can help me get this working.

    Thanks
    imdurgi

    • Edited by durgi-msdn Thursday, October 21, 2010 4:13 AM
    Thursday, October 21, 2010 3:04 AM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    Finally resolved this issue myself.... posting here for others benefits.

    I noticed that I had some event log like this.

    Event Type: Error
    Event Source: IIS Config
    Event Category: Catalog
    Event ID: 4275
    Date:  10/20/2010
    Time:  7:10:24 PM
    User:  N/A
    Computer: XXXXX
    Description:
    Error parsing XML file. Reason: An invalid character was found in text content.
     Incorrect XML: ystem verion(Tue Sep 07 08:01:11 2010.1065391890) : GetUserDefaultLCID failed, restorting to system verion(Tue Sep 07 08:01:11 2010.1065391906) : GetUserDefaultLCID failed, restorting to system verion(Tue Sep 07 08:01:11 2010.1065391937) : GetUserDefaultLCID failed, restorting to system verion(Tue Sep 07 08:01:13 2010.1065393140) : GetUserDefaultLCID failed, restorting to system verion(Tue Sep 07 08:01:18 2010.1065398156) : GetUserDefaultLCID failed, restorting to system verion(Tue Sep 07 08:01:21 2010.1065401828) : GetUserDefaultLCID failed, restorting to system verion(Tue Sep 07 08:01:23 2010.1065403156) : GetUserDefaultLCID failed, restorting to system verion(Tue Sep 07 08:01:28 2010.1065408156) : GetUserDefaultLCID failed, restorting to system verion(Tue Sep 07 08:01:33 2010.1065413156) : GetUserDefaultLCID failed, restorting to system verion(Tue Sep 07 08:01:38 2010.1065418156) : GetUserDefaultLCID failed, restorting to system verion(Tue Sep 07 08:01:43 2010.1065423156) : GetUserDefaultLCID failed, rest
    ErrorCode           : 0xC00CE508
    Interceptor         : 14
    OperationType       : Populate
    Table               : MBProperty
    ConfigurationSource : file:///C:/WINDOWS/system32/inetsrv/MetaBase.xml
    Row                 : 1
    Column              : 4101

     

    After searching a bit on net, found this msdn blog entry which led to resolution for this issue.

    http://blogs.msdn.com/b/rakkimk/archive/2006/12/11/iis-services-down-quot-error-parsing-xml-file-reason-an-invalid-character-was-found-in-text-content-quot-4275-event-from-iis-config-in-the-system-event-log.aspx

     

    After the IIS was working, the connector software installed successfully.

    ~ happy camper ~

    • Marked as answer by durgi-msdn Thursday, October 21, 2010 5:17 AM
    Thursday, October 21, 2010 5:17 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Few more things I want to add

    I used to be able to connect via the connector... not exactly when this problem started.

    Also, since this issue has started, I am logging on to WHS via terminal service and ensuring that windows update happens.

    I've alot of data ~3TB spread over 2x2TB  + 2x1TB drives, so rebuilding is not really an option :(

    Thursday, October 21, 2010 3:27 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Finally resolved this issue myself.... posting here for others benefits.

    I noticed that I had some event log like this.

    Event Type: Error
    Event Source: IIS Config
    Event Category: Catalog
    Event ID: 4275
    Date:  10/20/2010
    Time:  7:10:24 PM
    User:  N/A
    Computer: XXXXX
    Description:
    Error parsing XML file. Reason: An invalid character was found in text content.
     Incorrect XML: ystem verion(Tue Sep 07 08:01:11 2010.1065391890) : GetUserDefaultLCID failed, restorting to system verion(Tue Sep 07 08:01:11 2010.1065391906) : GetUserDefaultLCID failed, restorting to system verion(Tue Sep 07 08:01:11 2010.1065391937) : GetUserDefaultLCID failed, restorting to system verion(Tue Sep 07 08:01:13 2010.1065393140) : GetUserDefaultLCID failed, restorting to system verion(Tue Sep 07 08:01:18 2010.1065398156) : GetUserDefaultLCID failed, restorting to system verion(Tue Sep 07 08:01:21 2010.1065401828) : GetUserDefaultLCID failed, restorting to system verion(Tue Sep 07 08:01:23 2010.1065403156) : GetUserDefaultLCID failed, restorting to system verion(Tue Sep 07 08:01:28 2010.1065408156) : GetUserDefaultLCID failed, restorting to system verion(Tue Sep 07 08:01:33 2010.1065413156) : GetUserDefaultLCID failed, restorting to system verion(Tue Sep 07 08:01:38 2010.1065418156) : GetUserDefaultLCID failed, restorting to system verion(Tue Sep 07 08:01:43 2010.1065423156) : GetUserDefaultLCID failed, rest
    ErrorCode           : 0xC00CE508
    Interceptor         : 14
    OperationType       : Populate
    Table               : MBProperty
    ConfigurationSource : file:///C:/WINDOWS/system32/inetsrv/MetaBase.xml
    Row                 : 1
    Column              : 4101

     

    After searching a bit on net, found this msdn blog entry which led to resolution for this issue.

    http://blogs.msdn.com/b/rakkimk/archive/2006/12/11/iis-services-down-quot-error-parsing-xml-file-reason-an-invalid-character-was-found-in-text-content-quot-4275-event-from-iis-config-in-the-system-event-log.aspx

     

    After the IIS was working, the connector software installed successfully.

    ~ happy camper ~

    • Marked as answer by durgi-msdn Thursday, October 21, 2010 5:17 AM
    Thursday, October 21, 2010 5:17 AM