Entrar
Microsoft.com
 
Microsoft
 
 
 
Microsoft >
> 
> 
Cannot access Dashboard from any computer in the Network [WHS 2011 RTM]

Locked Cannot access Dashboard from any computer in the Network [WHS 2011 RTM]

  • quinta-feira, 21 de abril de 2011 17:39
     
     
    Entrar para Votar
    0

    Hey.

    I'm having an issue with Windows Home Server 2011 RTM.
    The server has been working fantastically well for the last 2 weeks but yesterday it started with a problem.

    When I open the Dashboard on one of the computers in the network, I enter the password and it shows me the following error:

    Photobucket

     

    I can access the Dashboard if I Remote Desktop directly into the server and then open the Dashboard from the server's desktop.

    I can also access it if I go to my remote access site and then click connect to my server. This provides the same interface as the standard Dashboard link.

     

    I have tried reinstalling the connector software but I get the following error:

    1. Does not find the server - I have to manually enter the name or IP address of the server:

      Server Not Found

    2. Asks for the password to the server, if I enter the incorrect it shows me an error, meaning it IS connecting to the server:

      Asking for password.

      Incorrect Password

    3. Once I enter the correct password it produces the following error:

      Cannot Connect to Server

     

    So yesterday I was doing a little bit of fiddling, and enabled Aero for the Remote Desktop connection. (I followed this post: http://sunmaiblog.wordpress.com/2010/11/28/configure-remote-desktop-service-for-windows-server-2008-r2/). The Dashboard worked (as it was still connected) and it was only later that the connection dropped (think my router rebooted) and it would not connect.

    All that was changed is the 'Allow Desktop Compositing' group policy and Audio and Video playback in tsconfig.msc were enabled. I can'ts see how that would've messed it up.
    I have now disabled all of those options but it has not helped.

    Some assistances would be GREATLY appreciated. This is the time I wish there was System Restore for the server :(

     

    • Movido kariya21MVP, Moderator domingo, 24 de abril de 2011 18:55 not a WHS v1 question (From:Windows Home Server Software)
    •  
       

    Todas as Respostas

    • sexta-feira, 22 de abril de 2011 14:34
       
       
      Entrar para Votar
      0

      Today the connector installation finds the server but still gives me an error once I enter the password.

      Would there be any logs that would have more info on this?

         
      • sexta-feira, 22 de abril de 2011 14:44
         
         
        Entrar para Votar
        0

        I also found this in the logs:

        (Had to delete the existing logs before anything showed up)


        [5824] 110422.164332.5845: ClientSetup: Call MachineIdentityManager.GetMachineStatus
        [5824] 110422.164333.2920: ClientSetup: MachineIdentityManager.GetMachineStatus had errors: ErrorCatalog:ProviderNotAvailable ErrorCode:-1
        BaseException: Microsoft.WindowsServerSolutions.Devices.Identity.MachineIdentityException: MachineIdentityManager.GetMachineStatus
           at Microsoft.WindowsServerSolutions.Devices.Identity.MachineIdentityManager.GetMachineStatus(String serverName, String userName, String password, String machineName, Boolean& isAdmin)
           at Microsoft.WindowsServerSolutions.ClientSetup.ClientDeploy.ValidateUserTask.Run(WizData data)
        [5824] 110422.164333.2925: ClientSetup: Exiting ValidateUserTask.Run
        [5824] 110422.164333.2925: ClientSetup: Task with Id=ClientDeploy.ValidateUser has TaskStatus=Failed
        [5824] 110422.164333.2925: ClientSetup: Task with Id=ClientDeploy.ValidateUser has RebootStatus=NoReboot
        [5824] 110422.164333.2925: ClientSetup: Exting ConnectorWizardForm.RunTasks
        [2128] 110422.164333.2995: ClientSetup: JoinNetwork Tasks returned TaskStatus=Failed
        [2128] 110422.164339.7705: ClientSetup: Back from the Client Deployment Wizard
        [2128] 110422.164339.7740: ClientSetup: Saving Wizard Data
        [2128] 110422.164339.7785: ClientSetup: End of ClientDeploy: ErrorCode=1603

         

        EDIT:

        In the supportedOS file I see the following:

        <SupportedConfigurations>

          <SupportedOS>
            <!-- Name is not used by the code but might be helpful in identifying the OS that is described by these parameters -->
            <!-- ExcludedSuite, RequiredSuite, and RequiredProductType are the numbers as specified in the OSVERSIONINFOEX structure -->
            <!-- Architecture is the number as specified in the SYSTEM_INFO structure -->
            <OS id="1" Name="Windows XP SP3, x86" Major="5" Minor="1" Build="2600" SPMajor="3" SPMinor="" ExcludedSuite="" RequiredSuite="" RequiredProductType="1" Architecture="0"/>   
            <OS id="2" Name="Windows Vista SP2, x86" Major="6" Minor="0" Build="6002" SPMajor="2" SPMinor="" ExcludedSuite="" RequiredSuite="" RequiredProductType="1" Architecture="0"/>
            <OS id="3" Name="Windows Vista SP2, AMD64" Major="6" Minor="0" Build="6002" SPMajor="2" SPMinor="" ExcludedSuite="" RequiredSuite="" RequiredProductType="1" Architecture="9"/>
            <OS id="4" Name="Windows 7, x86" Major="6" Minor="1" Build="7600" SPMajor="0" SPMinor="" ExcludedSuite="" RequiredSuite="" RequiredProductType="1" Architecture="0"/>
            <OS id="5" Name="Windows 7, AMD64" Major="6" Minor="1" Build="7600" SPMajor="0" SPMinor="" ExcludedSuite="" RequiredSuite="" RequiredProductType="1" Architecture="9"/>      
            <OS id="6" Name="Windows Server 2008 R2, AMD64" Major="6" Minor="1" Build="7600" SPMajor="1" SPMinor="" ExcludedSuite="" RequiredSuite="" RequiredProductType="3" Architecture="9"/>
          </SupportedOS>
          <SupportedFX>
            <!-- Name is not used by the code but might be helpful in identifying the Framework that is described by these parameters -->
            <!-- Frameworks versions have format of a.b.c.d, a = major, b = minor, c = build, d = servicepack -->
            <FX id="1" Name=".Net Framework 4.0" Major="4" Minor="0" Build="" SPMajor="0" InstallPath="SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full" InstallKey="Install" SPKey="Servicing"/>
          </SupportedFX>
          <SupportedPS>
            <!-- Name is not used by the code but might be helpful in identifying the PowerShell version that is described by these parameters -->
            <!-- PowerShell versions have format of a.b.c.d, a = major, b = minor, c = build d = servicepack -->
            <PS id="1" Name="PowerShell v2.0" Major="2" Minor="0" Build="" SPMajor=""/>
          </SupportedPS>
        </SupportedConfigurations>

        Under Windows 7, there is now service pack. Could this be a reason for it not working?


           
        • domingo, 24 de abril de 2011 21:17
          Moderador
           
           
          Entrar para Votar
          0

          Not sure...

           

          Check the client and server date/time and make sure they match.

          Restart the server. Through RDP start the Dashboard and check for any error events.
          Any "Windows Server ..." not running?

          - Theo.

           

          No home server like Home Server
             
          • domingo, 24 de abril de 2011 21:21
             
             
            Entrar para Votar
            0

            Hey Theo,

            Thanks for the response.

            Date and Time are correct - this issue is also on all of the computers that are in the network (5).

            The only error is 6GB left available on C drive.

            The only service not running is the Windows Server Initialization Service (I assume is only for initial setup?)

             

            Backups are still working on the clients that have the connector installed.

               
            • domingo, 24 de abril de 2011 21:36
               
               
              Entrar para Votar
              0

              Ok, just managed to extract an error log from one of the other clients.

              This is the DashboardClient.log after a failed attempt at logging in:

              4156] 110424.232755.5703: General: DashboardClient trying to sign in and launch the RAIL application.
              [4156] 110424.232807.1367: General: Unable to signin the user. Exception:
              [4156] 110424.232807.1376: General: Native error code: -1
              [4156] 110424.232807.3710: Exception:
              ---------------------------------------
              An exception of type 'Type: Microsoft.WindowsServerSolutions.Devices.Identity.MachineIdentityException, MachineIdentityObjectModel, Version=6.1.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' has occurred.
              Timestamp: 04/24/2011 23:28:07
              Message: MachineIdentityManager.GetMachineStatus
              Stack:    at Microsoft.WindowsServerSolutions.Devices.Identity.MachineIdentityManager.GetMachineStatus(String serverName, String userName, String password, String machineName, Boolean& isAdmin)
                  at Microsoft.WindowsServerSolutions.DashboardClient.SignInCustomCtrl.CheckUserCredentials(String username, String password)

                 
              • domingo, 24 de abril de 2011 21:44
                Moderador
                 
                 
                Entrar para Votar
                0

                Some assistances would be GREATLY appreciated. This is the time I wish there was System Restore for the server :( 

                FYI: Actually, For WHS 2011 there is (provided you have server backup configured)!
                (Not really helpfull - I guess...)


                - Theo.

                 

                No home server like Home Server
                   
                • domingo, 24 de abril de 2011 21:51
                  Moderador
                   
                   
                  Entrar para Votar
                  0

                  (On 6 GB? On a clean install I would expect at least 40GB free. Any special software installed that could cause problems?)

                  To rule out any router/DHCP problems: you can still ping the server by name from all clients?

                  Weird problem possibly not easy to find. Could be network related or just something on the server not behaving.
                  I personally would try a "quick" new server install on a spare drive to see if this solves the problem?
                  - Theo,

                   

                  No home server like Home Server
                     
                  • domingo, 24 de abril de 2011 22:03
                     
                     
                    Entrar para Votar
                    0

                    Hmm.. Good idea.

                    Just found a 'certsrv.log' file under C:\Windows using up 35GB O.o ??

                    Guess it's something to do with the SSL certificates?


                       
                    • domingo, 24 de abril de 2011 23:42
                       
                       
                      Entrar para Votar
                      0
                      My "certsrv.log" is 23.0 KB, just thought I would reference that.
                       

                      --
                      Don
                         
                      • segunda-feira, 25 de abril de 2011 08:03
                         
                         
                        Entrar para Votar
                        0
                        My "certsrv.log" is 23.0 KB, just thought I would reference that.
                         

                        --
                        Don


                        Haha, yeah. I somehow doubt my file is correct :)

                        The problem is I can't even open it to see what it's saying.

                           
                        • segunda-feira, 25 de abril de 2011 11:52
                           
                           
                          Entrar para Votar
                          0

                          It's up at 40GB this morning.

                          Anyone have an idea - this must be indicative of the original problems.

                             
                          • segunda-feira, 25 de abril de 2011 11:52
                             
                             
                            Entrar para Votar
                            0
                            Yeah, no extra HDD space for that yet :/
                               
                            • segunda-feira, 25 de abril de 2011 21:00
                               
                               
                              Entrar para Votar
                              0

                              Anyone??

                              I stopped the Active Directory Certificate Service and deleted the file and then restarted the service.

                              Surely this must be an easy fix now.


                              This is what the log contains now:


                              515.1670.0:<2011/4/25, 22:57:13>: 0xc80003fb (ESE: -1019)
                              513.15881.0:<2011/4/25, 22:57:14>: 0x80090011 (-2146893807): Exception at d:\w7rtm\ds\security\services\ca\fs\crypto\cngcryptofactory.cpp(421): NCryptOpenKey(hProv, &hKey, pwszKeyName, nLegacyKeySpec, acquireToOpenKeyFlags(fAcquire))
                              HRESULT = 0x80090011
                              513.16160.0:<2011/4/25, 22:57:14>: 0x80090011 (-2146893807): Microsoft Software Key Storage Provider
                              513.15881.0:<2011/4/25, 22:57:14>: 0x80090016 (-2146893802): Exception at d:\w7rtm\ds\security\services\ca\fs\crypto\capicryptofactory.cpp(520): CryptAcquireContext( &hProv, pszContainer, pszProvider, nProviderType, fAcquire)
                              HRESULT = 0x80090016
                              513.16160.0:<2011/4/25, 22:57:14>: 0x80090016 (-2146893802)
                              513.16219.0:<2011/4/25, 22:57:14>: 0x80090016 (-2146893802)
                              513.9488.0:<2011/4/25, 22:57:14>: 0x80090016 (-2146893802): Exception at d:\w7rtm\ds\security\services\ca\fs\crypto\capicryptofactory.cpp(348): CryptAcquireContext( &hProv, pszContainer, pszProvider, nProviderType, fAcquire | CRYPT_DELETEKEYSET)
                              HRESULT = 0x80090016

                                 
                              • quinta-feira, 28 de abril de 2011 14:52
                                 
                                 
                                Entrar para Votar
                                0
                                No more help / advice? Still having this issue.
                                   
                                • quinta-feira, 28 de abril de 2011 20:16
                                  Moderador
                                   
                                   
                                  Entrar para Votar
                                  0

                                  Hi Jonno,
                                  To be honest, I have no idea how to solve this ...

                                  Are you sure the the client originally worked witout problems?
                                  - Try uninstalling the connector software, then the .NET Framework 4.0, reboot the client.
                                  - Retry installing the connector software (download the installer to the clients desktop first and run it from there)

                                  The best advise I have is to report this to Connect (please do?) first.
                                  You will probably be asked to include your client+server logfiles. This will enable the technical team to find out what might be wrong.

                                  - Theo.

                                  No home server like Home Server
                                     
                                  • quinta-feira, 28 de abril de 2011 20:54
                                     
                                     
                                    Entrar para Votar
                                    0

                                    Thanks Theo, will submit to Connect. I thought that it'd be offer since it went RTM.

                                    Clients all worked 100% before.

                                    Have tried reinstalling in a number of ways on a number of clients - same error each time.

                                       
                                    • quinta-feira, 28 de abril de 2011 21:33
                                       
                                       
                                      Entrar para Votar
                                      0

                                      Ok, posted on https://connect.microsoft.com/WindowsHomeServer/feedback/details/665543/cannot-access-dashboard-from-any-pc-in-network-nor-install-software-on-new-clients

                                       

                                         
                                      • sexta-feira, 29 de abril de 2011 21:06
                                        Moderador
                                         
                                         
                                        Entrar para Votar
                                        0

                                        Hi,
                                        Just a question: could you please check if any of the following services are started?

                                        1. Windows Server Addins Infrastructure Service
                                        2. Windows Server Identity Management Service
                                        3. Windows Server Server Backup Service

                                        - Theo.

                                        No home server like Home Server
                                           
                                        • sexta-feira, 29 de abril de 2011 21:29
                                           
                                           
                                          Entrar para Votar
                                          0
                                          Yep, all 3 are running.
                                             
                                          • segunda-feira, 2 de maio de 2011 22:26
                                            Moderador
                                             
                                             
                                            Entrar para Votar
                                            0

                                            OK,
                                            (Was just wondering if your problem might be related to some other problem but that does not seem the case)
                                            Thanks!

                                            - Theo.

                                            No home server like Home Server
                                               
                                            • sexta-feira, 6 de maio de 2011 08:01
                                               
                                               
                                              Entrar para Votar
                                              0
                                              FYI, I'm seeing similar symptoms except no inflation of certsrv.log file (running RC). I wasn't planning to switch over to RTM just yet, but this problem stops my client backups and with no workaround in sight I might as well switch over to RTM now.