An Error Occurred That Prevented The Windows Home Server Connector
Contents |
(Nederlands)Polska (Polski)România (Română)Singapore (English)Türkiye (Türkçe)Россия (Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語)香港特別行政區 (中文) Microsoft Home Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: How do you repair a cannot connect the computer to the server broken WHS connector? Windows Home Server > Windows Home Server Software Question 0 cannot connect the computer to the server because either another software installation Sign in to vote My Windows Home Server connector software was recently infected with the tenga.a worm. The files
Cannot Connect To Windows Server Windows 10
in question were: setup.exe & WHSConnectorInstall.exe WindowsInstaller-KB893803-v2-x86.exe dotnetchk.exe & dotnetfx.exe I replaced the infected files with versions from C:\WHS. This worked fine for three of my computers (XP home SP3 & XP
The Server Is Not Available. Try Connecting This Computer Again
Pro SP3). They connect and backup just fine. One machine (XP Home SP3) would no longer back up. I have attempted to reinstall the connector software numerous times. The installer tells me that "Windows Home Server Connector is already installed on this computer. Setup will uninstall and then reinstall the Windows Home Server Connector software. Do you want to proceed?" After clicking "Yes" it goes cannot connect this computer to the network the server is not available through the motions of installing but fails. "Installation did not finish. An error occurred that prevented the Windows Home Server Connector from completing successfully. Run this wizard again to install the Windows Home Server Connector. To close this wizard click OK." Running the wizard again does not help. Add and Remove Programs does not list WHS Connector. How can I COMPLETELY remove the old version so it will reinstall and work? Thursday, June 03, 2010 5:37 PM Reply | Quote Answers 0 Sign in to vote A compromised (formerly infected) system is still compromised and not trustworthy any more, so I would not really recommend to deal too long with that attempt. (What about restoring a preinfection version of that machine from your home server?) It may be enough to úse the Windows Installer Cleanup Utility to remove the Installer information for the Connector software on the client, or you may have to uninstall the software and remove the folder Program Files\Windows Home Server and the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Home Server. Best greetings from Germany Olaf Proposed as answer by Ken WarrenModerator Friday, June 04, 2010 12:02 AM Marked as answer by
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business
Windows Server Essentials Connector The Server Is Not Available
Learn more about hiring developers or posting ads with us Super User Questions Tags Users cannot connect to server mac Badges Unanswered Ask Question _ Super User is a question and answer site for computer enthusiasts and power users. Join them; it only cannot connect to server android takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Windows Home Server Connector Failing to Install up vote 6 https://social.microsoft.com/Forums/en-US/dada6d43-bc4b-4be1-8ea7-e7f682ae553f/how-do-you-repair-a-broken-whs-connector?forum=whssoftware down vote favorite I'm having some difficulty getting the Windows Home Server Connector to work on multiple machines. My Home Server server is up and running and working perfectly with my main PC (which has the Connector installed). Now I'm trying to install the Connector on subsequent PCs with no luck. On the client PCs, I run the Connector installer. An error occurs after being prompted to enter my WHS password: This operation cannot be completed at http://superuser.com/questions/159138/windows-home-server-connector-failing-to-install this time. Please try again later. If the problem persists, please contact Product Support. At this point, my only option is to back out of the Connector installer. This is the details of the event in the Event Log: Server ID is not set yet. On the client it means that the server discovery (discovery.exe) was not run or was not run successfully. I have tried getting the Connector working of a variety of machines now, so I don't believe that the error exists on the client end. Any solutions or suggestions? installation windows-home-server share|improve this question asked May 2 '09 at 15:27 Matt Hanson 64511428 migrated from serverfault.com Jul 1 '10 at 20:01 This question came from our site for system and network administrators. How are you installing the client? from the server share? or from a local copy of the connector software? –Omar Shahine May 2 '09 at 15:33 I've tried both server:55000 and \\server\Software. –Matt Hanson May 2 '09 at 15:39 add a comment| 6 Answers 6 active oldest votes up vote 4 down vote accepted I would copy the entire Home Server Connector software to your local drive and run it from there. In a few cases I've had failures where running directly from the home server failed but running the exe from the local machine worked fine. share|impro
Sign Up All Content All Content This Topic This Forum Advanced Search Browse Forums Downloads Guidelines Staff Online Users More Activity All Activity My Activity Streams Unread Content Content I Started Search More Store Orders Manage Purchases http://forum.wegotserved.com/index.php?/topic/10929-unable-to-install-x64-connector-on-windows-7/ My Details Personal Information Addresses Account Credit Alternative Contacts More Support Support More We Got Served More More All Activity Home Home Servers & NAS Windows Home Server & Windows Server Windows Home Server v1 Installation Unable To Install X64 Connector On Windows 7 Sign in to follow this Followers 0 Unable To Install X64 Connector On Windows 7 Started by cheyne, November 11, 2009 4 posts in this topic cheyne 0 Newbie Members 0 2 cannot connect posts Posted November 11, 2009 I have Windows 7 x64 on the client, and WHS 32bit on the server. The server has updated itself to PP2, and includes the x64 Connector installer. I am trying to run the installer on the Win7 box thus: msiexec /i "\\SERVER\Software\Home Server Connector Software\whsconnector_x64.msi" WHSMSI="RUNSETUP" The connector MSI installer fails at about the time it appears to be starting services: "An error occurred that prevented the Windows Home Server Connector from completing computer to the successfully". Interestingly, this is the second time installing the Connector on this Win7 box. The first time worked. At the time, the server had not yet updated itself to PP2. Though the Connector install worked at that time, the software didn't work right - the server failed to see the client PC, it never showed up in the Console's list of computers. I have since reinstalled Win7 on the client and am trying to install the Connector again, but now I get this error. I've checked the server registry HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Home Server\Transport\Clients and it only lists my second (XP 32bit) client PC that successfully installed the Connector. I've checked the Win7 PC's event viewer and two errors appear at the time of install - 1) From HomeServer: Server ID is not set yet. On the client it means that the server discovery (discovery.exe) was not run or was not run successfully. 2) From Kernel-EventTracing: Session "" failed to start with the following error: 0xC000000D Thanks, Mark Share this post Link to post Share on other sites Upgrade to a WGS Supporter Account to remove this ad. Drashna Jaelre (WGS) 314 Tinkerer Lead Moderator 314 11633 posts Gender:Male Location:San Diego, CA, USA Interests:Computers, Home Server (obviously), math, science, good books, friends Posted November 12, 2009 Make sure the windows install service is enabled and started, I believe it was. Share