locked
Connector & backup not working RRS feed

  • Question

  • On an XP Pro laptop the connector software installed normally, however:

    The computer shows as "offline" on the dashboard.
    Backups don't hapen

    When the launch pad is started first the alert service crashes witout ever starting then I get a dialog box which says "The server appears to be offline. Do you want to sign in to offline mode. YES NO". When I answer YES, the launchpad will start.
    "Backup" function yields "Cannot connect to the Windows Server Computer Backup Provider Service" after it thinks about it for a while.
    "Remote Web Access" does nothing
    Shared folders opens normally and allows access.
    "Dashboard" opens the dashboard normally.

    I've uniinstalled the connector, then .Net 4.0, then reinstalled .Net 4.0, then reinstalled the connector. No joy.

    Help!!

    drm

    Saturday, June 11, 2011 11:13 PM

All replies

  • On an XP Pro laptop the connector software installed normally, however:

    The computer shows as "offline" on the dashboard.
    Backups don't hapen

    When the launch pad is started first the alert service crashes witout ever starting then I get a dialog box which says "The server appears to be offline. Do you want to sign in to offline mode. YES NO". When I answer YES, the launchpad will start.
    "Backup" function yields "Cannot connect to the Windows Server Computer Backup Provider Service" after it thinks about it for a while.
    "Remote Web Access" does nothing
    Shared folders opens normally and allows access.
    "Dashboard" opens the dashboard normally.

    I've uniinstalled the connector, then .Net 4.0, then reinstalled .Net 4.0, then reinstalled the connector. No joy.

    Help!!

    drm


    Do you have other worstations (besides your XP box) in your LAN?  If so, can any of them see the server?  Can you successfully ping your server from your XP box (both by name and by IP address)?
    Sunday, June 12, 2011 3:09 PM
  • Yes - there are two other XP Pro machines and two Win 7 x64 machines that work properly - show as "online" get backed-up every nite, etc.

    The machine in question can see the server both using its ip address & its name.  Similarly, the server can see it.  It has access to the server shares and can open the dashboard.  I can open an RDP session on the server using the machine in question.

    Thanks for your help!!

     

    drm

    Sunday, June 12, 2011 6:44 PM
  • For my friend Fred:

    I got Launchpad to work.  After starting my laptop I went to Events and checked all Errors within the last hour.  I started with the first one and reviewed them with Microsoft using the Event Log Online Help.  It showed the following information.

    ----------------------------------------------------------------------------------

     

    Event ID 7009 — Basic Service Operations

     Updated: January 6, 2009 at http://technet.microsoft.com/en-us/library/dd349435(WS.10).aspx

     

    Applies To: Windows Server 2008 R2 

     Service Control Manager transmits control requests to running services and driver services. It also maintains status information about those services, and reports configuration changes and state changes.

     

    Event Details

     Product: Windows Operating System

     ID: 7009

     Source: Service Control Manager

     Version: 6.1

     Symbolic Name: EVENT_CONNECTION_TIMEOUT

     Message: Timeout (%1 milliseconds) waiting for the %2 service to connect.

     Resolve

     

    Increase the service timeout period

     

    The Service Control Manager will generate an event if a service does not respond within the defined timeout period (the default timeout period is 30000 milliseconds). To resolve this problem, use the Registry Editor to change the default timeout value for all services.

     

    To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority. 

     Caution: Incorrectly editing the registry may severely damage your system. Before making changes to the registry, you should back up any valued data. 

     To change the service timeout period: 

    1.Click the Start button, then click Run, type regedit, and click OK. 

    2.In the Registry Editor, click the registry subkey HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control. 

    3.In the details pane, locate the ServicesPipeTimeout entry, right-click that entry and then select Modify.

     Note: If the ServicesPipeTimeout entry does not exist, you must create it by selecting New on the Edit menu, followed by the DWORD Value, then typing ServicesPipeTimeout, and clicking Enter.

     

    4.Click Decimal, enter the new timeout value in milliseconds, and then click OK. 

    5.Restart the computer. 

      

    ----------------------------------------------------------------------------------

     So I had to create the ServicesPipeTimeout and I gave it a 100000 millisecond setting.  Shut down my laptop.  I restarted my laptop and immediately went back to my Event Viewer and selected to review all the errors for the last hour.  So there were about 12 errors cleared up with this one entry so I selected Launchpad to run.  It popped up connected in just a couple seconds.

    • Proposed as answer by wubbles Thursday, March 29, 2012 10:27 PM
    Sunday, June 12, 2011 10:26 PM
  • Thanks, kingair1,  But, alas, didn't work for me!  Tried several bigger time entries with no joy.

     

    drm

    Sunday, June 12, 2011 10:52 PM
  • I had exactly this problem.

    Check your running services and event logs.  I found that the NET.TCP Port Sharing Service was hanging with the status "starting", and so all the dependent Windows Server services were not starting.

    I fixed it by running the service using a user login with administrative rights rather than the LOCAL SERVICE default, and everything seems to work perfectly now.

    • Proposed as answer by wubbles Thursday, March 29, 2012 10:27 PM
    Monday, June 13, 2011 6:12 AM
  • Good lead, RichardM40 - but the Port Sharing Service is running.  I stopped and restarted it for good measure but still NO JOY.

     

    drm


    Monday, June 13, 2011 11:12 AM
  • I found that to get Net.TCP to start reliably, that I had to set the ServicesPipeTimeout to at least 100000.  I eventually just set it to 300000 to try and take care of the problem completely.  I also needed to switch the login, it seemed, but it may be that the login is unrelated, and I just happened to get the timing right the particular "attempt" that I had also changed the login.

    It seems that this is related to really slow/old XP machines doing many things at startup, and .NET-4 has all of these inter-related service startup timing/issues that are fragile in such cases.


    Wubs

    Thursday, March 29, 2012 10:30 PM