none
Trouble Installing Launchpad, Logs Included, Update:Solved!!!

    Question

  • I really need some help with this problem. I've tried everything I could think of to get launchpad to install on an xp pro laptop with no success yet. Other people on this forum are having this problem as well with out a real solid solution. I'm including the clientdeploy.log from the last attempt if this can help anyone see what the problem is. If other logs are needed for help I have them to.

    Desperately seeking help

    Steve

     


    [1740] 110802.131835.9234: ClientSetup: Start of ClientDeploy
    [1740] 110802.131836.3923: General: Initializing...C:\WINDOWS\Temp\Client Deployment Files\ClientDeploy.exe
    [1740] 110802.131836.4079: ClientSetup: Loading Wizard Data
    [1740] 110802.131837.0018: ClientSetup: Current DeploymentStatus=Failed
    [1740] 110802.131838.5334: ClientSetup: Showing the Client Deployment Wizard
    [1740] 110802.131838.7834: ClientSetup: Adding Server Info data in the Product Registry
    [1740] 110802.131838.8303: ClientSetup: Set the Deployment Sync Event
    [644] 110802.131857.1154: ClientSetup: Running ValidateUser Tasks at WizardPage DomainUserCred
    [644] 110802.131857.1154: ClientSetup: Entering ConnectorWizardForm.RunTasks
    [644] 110802.131857.1154: ClientSetup: Running Task with Id=ClientDeploy.ValidateUser
    [644] 110802.131857.2248: ClientSetup: Entering ValidateUserTask.Run
    [644] 110802.131857.2404: ClientSetup: Install root cert to local trusted store
    [644] 110802.131857.2717: ClientSetup: Validating User
    [644] 110802.131857.2717: ClientSetup: Call MachineIdentityManager.GetMachineStatus
    [644] 110802.131900.8349: ClientSetup: Current Machine Join Status: ActiveWithCert
    [644] 110802.131900.8349: ClientSetup: Exiting ValidateUserTask.Run
    [644] 110802.131900.8349: ClientSetup: Task with Id=ClientDeploy.ValidateUser has TaskStatus=Success
    [644] 110802.131900.8349: ClientSetup: Task with Id=ClientDeploy.ValidateUser has RebootStatus=NoReboot
    [644] 110802.131900.8349: ClientSetup: Exting ConnectorWizardForm.RunTasks
    [644] 110802.131900.8349: ClientSetup: Running JoinNetwork Tasks at WizardPage DomainUserCred
    [644] 110802.131900.8349: ClientSetup: Entering ConnectorWizardForm.RunTasks
    [644] 110802.131900.8349: ClientSetup: Running Task with Id=ClientDeploy.JoinDomain
    [644] 110802.131900.8349: ClientSetup: Entering JoinDomainTask.Run
    [644] 110802.131900.8349: ClientSetup: Domain Join Client to Server Domain: ClientComputerName=VOSTROLAP ServerDomainNetBiosName=430-Server
    [644] 110802.131900.8349: ClientSetup: Trying to set Local Nic Dns address as the Server IP.
    [644] 110802.131900.8349: ClientSetup: Configure DNS settings on local NIC
    [644] 110802.131900.8349: ClientSetup: Got Server Ip=[192.168.0.115]
    [644] 110802.131901.5382: ClientSetup: Exception in CheckNetworkAdapter: System.Management.ManagementException: Invalid query
       at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
       at System.Management.ManagementObjectCollection.ManagementObjectEnumerator.MoveNext()
       at System.Management.ManagementObjectCollection.get_Count()
       at Microsoft.WindowsServerSolutions.ClientSetup.ClientDeploy.JoinDomainTask.IsNicHardwareLoopback(String nicGuid)
    [644] 110802.131901.6164: ClientSetup: Exception in CheckNetworkAdapter: System.Management.ManagementException: Invalid query
       at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
       at System.Management.ManagementObjectCollection.ManagementObjectEnumerator.MoveNext()
       at System.Management.ManagementObjectCollection.get_Count()
       at Microsoft.WindowsServerSolutions.ClientSetup.ClientDeploy.JoinDomainTask.IsNicHardwareLoopback(String nicGuid)
    [644] 110802.131901.6320: ClientSetup: NetGetJoinInformation (server = [], ...)
    [644] 110802.131901.6476: ClientSetup: Client is already joined to a Domain: ClientDomainNetBiosName = 430-SERVER
    [644] 110802.131901.6476: ClientSetup: Client has been manually joined to the Server Domain...Moving to Next Task
    [644] 110802.131901.6476: ClientSetup: Join Domain will not be Run
    [644] 110802.131901.6476: ClientSetup: Exiting JoinDomainTask.Run
    [644] 110802.131901.6476: ClientSetup: Task with Id=ClientDeploy.JoinDomain has TaskStatus=Success
    [644] 110802.131901.6476: ClientSetup: Task with Id=ClientDeploy.JoinDomain has RebootStatus=NoReboot
    [644] 110802.131901.6476: ClientSetup: Running Task with Id=ClientDeploy.JoinNetwork
    [644] 110802.131901.6476: ClientSetup: Entering JoinNetworkTask.Run
    [644] 110802.131901.6476: ClientSetup: Network Join Client to Server: ClientComputerName=VOSTROLAP ServerName=430SERVER
    [644] 110802.131901.6476: ClientSetup: Maximum amount of joined machines: 30
    [644] 110802.131901.6476: ClientSetup: Current amount of joined machines: 3
    [644] 110802.131901.6476: ClientSetup: Server already contains a computer joined with Client Machine Name
    [644] 110802.131901.6476: ClientSetup: Network Join has been forced
    [644] 110802.131901.6476: ClientSetup: Running Network Join
    [644] 110802.131901.6476: ClientSetup: Call MachineIdentity.GetCert
    [644] 110802.131906.6018: ClientSetup: Exiting JoinNetworkTask.Run
    [644] 110802.131906.6018: ClientSetup: Task with Id=ClientDeploy.JoinNetwork has TaskStatus=Success
    [644] 110802.131906.6018: ClientSetup: Task with Id=ClientDeploy.JoinNetwork has RebootStatus=NoReboot
    [644] 110802.131906.6018: ClientSetup: Running Task with Id=ClientDeploy.AllowProfileMigration
    [644] 110802.131906.6643: ClientSetup: Entering AllowProfileMigrationTask.Run
    [644] 110802.131906.6799: ClientSetup: NetQueryUsers (Server = [VOSTROLAP] )
    [644] 110802.131911.2434: ClientSetup: Completed getting list of users
    [644] 110802.131911.2434: ClientSetup: Logon User Details: VOSTROLAP\Chris
    [644] 110802.131911.2434: ClientSetup: Checking if UserProfile exist: UserSid=S-1-5-21-3432249030-1244345151-632040562-1005
    [644] 110802.131911.2434: ClientSetup: ProfileMgmt on Windows XP
    [644] 110802.131911.2434: ClientSetup: LogonUser has a local profile
    [644] 110802.131911.7591: ClientSetup: Domain User Details: 430-Server\Chris
    [644] 110802.131911.7591: ClientSetup: Checking if UserProfile exist: UserSid=S-1-5-21-680553190-2987454500-3742871648-1119
    [644] 110802.131911.7591: ClientSetup: Domain User has a local profile on the client machine
    [644] 110802.131911.7591: ClientSetup: Logon User Profile Migration wil be Not Allowed
    [644] 110802.131911.7591: ClientSetup: Exiting AllowProfileMigrationTask.Run
    [644] 110802.131911.7591: ClientSetup: Task with Id=ClientDeploy.AllowProfileMigration has TaskStatus=Success
    [644] 110802.131911.7591: ClientSetup: Task with Id=ClientDeploy.AllowProfileMigration has RebootStatus=NoReboot
    [644] 110802.131911.7591: ClientSetup: Exting ConnectorWizardForm.RunTasks
    [1740] 110802.131911.7748: ClientSetup: JoinNetwork Tasks returned TaskStatus=Success
    [644] 110802.131922.9959: ClientSetup: Running Tasks for Wizard Page ConfiguringComputer
    [644] 110802.131922.9959: ClientSetup: Entering ConnectorWizardForm.RunTasks
    [644] 110802.131922.9959: ClientSetup: Running Task with Id=ClientDeploy.PrepareClient
    [644] 110802.131923.0740: ClientSetup: Entering PrepareClientTask.Run
    [644] 110802.131923.0740: ClientSetup: Ensuring that ServiceName=NetTcpPortSharing is Running
    [644] 110802.131923.2616: ClientSetup: Ensuring that ServiceName=SSDPSRV is Running
    [644] 110802.131923.2616: ClientSetup: NetGetJoinInformation (server = [], ...)
    [644] 110802.131923.4491: ClientSetup: Adding domain user [Chris] to local Administrators group
    [644] 110802.131923.4491: ClientSetup: LookupAccountSid (computerName = [], sid = [S-1-5-32-544])
    [644] 110802.131923.4491: ClientSetup: NetLocalGroupAddMember (server = [], groupName = [Administrators], sidMember = [S-1-5-21-680553190-2987454500-3742871648-1119])
    [644] 110802.131923.4491: ClientSetup: Enabling Compression on the Log Directory.
    [644] 110802.131923.4803: ClientSetup: Exiting PrepareClientTask.Run
    [644] 110802.131923.4803: ClientSetup: Task with Id=ClientDeploy.PrepareClient has TaskStatus=Success
    [644] 110802.131923.4803: ClientSetup: Task with Id=ClientDeploy.PrepareClient has RebootStatus=NoReboot
    [644] 110802.131923.4803: ClientSetup: Running Task with Id=ClientDeploy.DownloadSoftware
    [644] 110802.131923.5585: ClientSetup: Entering DownloadSoftwareTask.Run
    [644] 110802.131923.5585: ClientSetup: Download client package ClientCore.cab
    [644] 110802.131923.5585: ClientSetup: Download file ClientCore.cab from server
    [644] 110802.131923.5585: ClientSetup: Making web request: System.Net.HttpWebRequest
    [644] 110802.131926.4497: ClientSetup: Downloaded file C:\WINDOWS\Temp\Client Deployment Files\ClientCore.cab
    [644] 110802.131926.7310: ClientSetup: Found MSI file within cab: ClientCoreX86.msi
    [644] 110802.131926.7310: ClientSetup: Exiting DownloadSoftwareTask.Run
    [644] 110802.131926.7310: ClientSetup: Task with Id=ClientDeploy.DownloadSoftware has TaskStatus=Success
    [644] 110802.131926.7310: ClientSetup: Task with Id=ClientDeploy.DownloadSoftware has RebootStatus=NoReboot
    [644] 110802.131926.7310: ClientSetup: Running Task with Id=ClientDeploy.InstallSoftware
    [644] 110802.131926.7310: ClientSetup: Entering InstallSoftwareTask.Run
    [644] 110802.131926.7310: ClientSetup: Install package C:\WINDOWS\Temp\Client Deployment Files\ClientCoreX86.msi
    [644] 110802.131926.8092: ClientSetup: Running MSI: C:\WINDOWS\Temp\Client Deployment Files\ClientCoreX86.msi  SOFTWARE_NAME="Windows Small Business Server 2011" REBOOT=ReallySuppress
    [644] 110802.132447.3678: ClientSetup: Running MSI threw an exception:Microsoft.Deployment.WindowsInstaller.InstallerException: Fatal error during installation.
       at Microsoft.Deployment.WindowsInstaller.Installer.CheckInstallResult(UInt32 ret)
       at Microsoft.WindowsServerSolutions.ClientSetup.ClientDeploy.Helper.RunMsi(String msiPathOrProductCode, String logFilePath, Dictionary`2 msiProperties, Boolean install, ProgressChangedEventHandler progressHandler)
    [644] 110802.132447.3678: ClientSetup: RunMsi returned error: RetCode=1603
    [644] 110802.132447.3678: ClientSetup: Failed to install C:\WINDOWS\Temp\Client Deployment Files\ClientCoreX86.msi
    [644] 110802.132447.3678: ClientSetup: Exting InstallSoftwareTask.Run
    [644] 110802.132447.3678: ClientSetup: Task with Id=ClientDeploy.InstallSoftware has TaskStatus=Failed
    [644] 110802.132447.3678: ClientSetup: Task with Id=ClientDeploy.InstallSoftware has RebootStatus=NoReboot
    [644] 110802.132447.3678: ClientSetup: Exting ConnectorWizardForm.RunTasks
    [1740] 110802.132503.2127: ClientSetup: Back from the Client Deployment Wizard
    [1740] 110802.132503.2127: ClientSetup: Saving Wizard Data
    [1740] 110802.132503.2284: ClientSetup: End of ClientDeploy: ErrorCode=1603
    salt4502




    • Edited by salt4502 Tuesday, August 09, 2011 3:03 AM
    Wednesday, August 03, 2011 12:45 AM

Answers

  • Solved!!!

    First off I would like to thank sbs_sdet_w  and Xioafeng for helping me with this. I give them credit for steering me in the right direction but I'm marking this as answer because it explains how to fix it.

    I don't know if this fix will work for everyone, but I sure hope it does because it'll make you pull your hair out if you can't figure it out. This fix should work for SBS Essentials 2011 and WHS 2011. They are both about the same and considering the logs on here are from SBS Essentials 2011 and it worked, it should also work on WHS 2011

    The main problem with this was caused by the security permissions for task scheduler being corrupted. If you see these lines at the bottom of your clientdeploy.log:

     

    "[644] 110802.131926.8092: ClientSetup: Running MSI: C:\WINDOWS\Temp\Client Deployment Files\ClientCoreX86.msi  SOFTWARE_NAME="Windows Small Business Server 2011" REBOOT=ReallySuppress
    [644] 110802.132447.3678: ClientSetup: Running MSI threw an exception:Microsoft.Deployment.WindowsInstaller.InstallerException: Fatal error during installation.
       at Microsoft.Deployment.WindowsInstaller.Installer.CheckInstallResult(UInt32 ret)
       at Microsoft.WindowsServerSolutions.ClientSetup.ClientDeploy.Helper.RunMsi(String msiPathOrProductCode, String logFilePath, Dictionary`2 msiProperties, Boolean install, ProgressChangedEventHandler progressHandler)
    [644] 110802.132447.3678: ClientSetup: RunMsi returned error: RetCode=1603
    [644] 110802.132447.3678: ClientSetup: Failed to install C:\WINDOWS\Temp\Client Deployment Files\ClientCoreX86.msi
    [644] 110802.132447.3678: ClientSetup: Exting InstallSoftwareTask.Run
    [644] 110802.132447.3678: ClientSetup: Task with Id=ClientDeploy.InstallSoftware has TaskStatus=Failed

    [644] 110802.132447.3678: ClientSetup: Task with Id=ClientDeploy.InstallSoftware has RebootStatus=NoReboot
    [644] 110802.132447.3678: ClientSetup: Exting ConnectorWizardForm.RunTasks
    [1740] 110802.132503.2127: ClientSetup: Back from the Client Deployment Wizard
    [1740] 110802.132503.2127: ClientSetup: Saving Wizard Data
    [1740] 110802.132503.2284: ClientSetup: End of ClientDeploy: ErrorCode=1603"

     

    This is what prevented Launchpad from installing. None of the other errors I posted on here were related to the problem as they were still present in the logs after I had a successful install of Launchpad.

    To fix this do the following.

    First you need to see if task scheduler is running properly. Use this link provided by sbs_sdet_w to set it up if you don't know how  http://support.microsoft.com/kb/308569
    Just pick any old task to run. I used disk cleanup and set it to run once. When you run it if you get the error "Task Scheduler error,0x80090016,Keyset does not exist" you just do this next.

    1. Stop the Task Scheduler Service  (run => services.msc)
    2. Delete or Move ( I created a new folder and dumped them in there) the file(s) from the
      "C:Documents and Settings\All Users\Application Data\Microsoft\Crypto\RSA-S-1-5-18" folder.
    3. Start the Task Scheduler Service.
    4. Edit each previously scheduled task and provide security credentials( It'll as you for your login) for the task to run under.
    5. Right click a task and choose run.

    The task should run correctly and it should also run as scheduled.

    If task scheduler works you should be able to reinstall Launchpad with no problems now. If you haven't cleaned out your old installation of Launched do it before you reinstall.
    If you haven't done that before do the following.

         1.  Remove the clients computer from the Server and restart it.
         2.  On the clients computer itself, go to Control Panel- System- Computer Name and click Change.
         3.  On this tab change the computers name to anything you want to name it as long as it's different from the one that is already there.
         4.  Change Domain to Workgroup and use the name of the Workgroup you belonged to before. If not, just put Anything.
         5.  Click OK, You're Login screen should appear, Type in your login for the computer and then follow the on screen instructions to finish.
         6.  After the computer finishes rebooting run a good cleaner like CCleaner. Run the file cleaner and the registry cleaner. This gets enough of
              the old files out to reinstall Launchpad.

    After that, reinstall the Launchpad software and you should be good to go. I didn't have to uninstall .net 4.0 or turn off my antivirus software. But if you don't want to take any chances of it screwing up again, shut off anything running in the background just to be sure.

    This is all I did and it worked well for me. Some of your experiences may be different. If I missed anything please feel free to post here and correct it. If you are having this problem, I hope this works for you.

    Thanks

     


    salt
    • Marked as answer by salt4502 Tuesday, August 09, 2011 2:44 AM
    Tuesday, August 09, 2011 2:08 AM

All replies

  • Hi

    From the log the client installation failed in installing ClientCoreX86.msi

    [644] 110802.132447.3678: ClientSetup: Running MSI threw an exception:Microsoft.Deployment.WindowsInstaller.InstallerException: Fatal error during installation.
    at Microsoft.Deployment.WindowsInstaller.Installer.CheckInstallResult(UInt32 ret)
    at Microsoft.WindowsServerSolutions.ClientSetup.ClientDeploy.Helper.RunMsi(String msiPathOrProductCode, String logFilePath, Dictionary`2 msiProperties, Boolean install, ProgressChangedEventHandler progressHandler)
    [644] 110802.132447.3678: ClientSetup: RunMsi returned error: RetCode=1603

    Could you paste the ClientCoreX86.log?

    It's better you could open a connect bug http://connect.microsoft.com/ and attach the logs for futher investigation

    Thanks.

    Thursday, August 04, 2011 3:18 AM
  •  

     

    Thanks for answering Xiaofeng

    Here are just the error lines from the log. ( to large to post it all ) As far as I can tell these are all the errors I could find. If you would like it all I'll have to email it I guess. Hope you can find something.

     

    Action start 13:20:24: RegisterProduct.
    MSI (s) (90:EC) [13:20:24:133]: Note: 1: 2205 2:  3: Error
    MSI (s) (90:EC) [13:20:24:211]: Note: 1: 2228 2:  3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1302
    MSI (s) (90:EC) [13:20:24:290]: PROPERTY CHANGE: Adding ProductToBeRegistered property. Its value is '1'.
    Action ended 13:20:24: RegisterProduct. Return value 1.

     

    MSI (s) (90:00) [13:23:46:284]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSICB.tmp, Entrypoint: CAQuietExec
    CAQuietExec:  System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Runtime.InteropServices.COMException: Keyset does not exist (Exception from HRESULT: 0x80090016)
    CAQuietExec:     at System.Runtime.InteropServices.ComTypes.IPersistFile.Save(String pszFileName, Boolean fRemember)
    CAQuietExec:     at Microsoft.WindowsServerSolutions.Common.ProviderFramework.SchedulerVersion1._saveTask(ITask task)
    CAQuietExec:     at Microsoft.WindowsServerSolutions.Common.ProviderFramework.SchedulerVersion1._registerTask(TaskInformation taskInfo, TaskAction action, TriggerCollection triggers, TaskSettings settings)
    CAQuietExec:     at Microsoft.WindowsServerSolutions.Common.ProviderFramework.SchedulerVersion1.RegisterTask(TaskDefinition definition)
    CAQuietExec:     at Microsoft.WindowsServerSolutions.Common.ProviderFramework.Scheduler.RegisterTask(TaskDefinition definition, Boolean overwrite)
    CAQuietExec:     at Microsoft.WindowsServerSolutions.ClientSetup.ScheduledTasks.ClientTasks.AddScheduledTasks()
    CAQuietExec:     --- End of inner exception stack trace ---
    CAQuietExec:     at System.RuntimeMethodHandle._InvokeMethodFast(IRuntimeMethodInfo method, Object target, Object arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeType typeOwner)
    CAQuietExec:     at System.RuntimeMethodHandle.InvokeMethodFast(IRuntimeMethodInfo method, Object target, Object arguments, Signature sig, MethodAttributes methodAttributes, RuntimeType typeOwner)
    CAQuietExec:     at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object parameters, CultureInfo culture, Boolean skipVisibilityChecks)
    CAQuietExec:     at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object parameters, CultureInfo culture)
    CAQuietExec:     at Microsoft.WindowsServerSolutions.Common.ProviderFramework.Program._invokeMethod(Type classType, MethodInfo mi)
    CAQuietExec:     at Microsoft.WindowsServerSolutions.Common.ProviderFramework.Program.Main(String args)
    CAQuietExec:  Error 0x80131604: Command line returned an error.
    CAQuietExec:  Error 0x80131604: CAQuietExec Failed
    Action ended 13:23:48: InstallFinalize. Return value 3.Action ended 13:24:46: INSTALL. Return value 3.



    === Logging stopped: 8/2/2011  13:24:46 ===
    MSI (s) (90:EC) [13:24:46:180]: Note: 1: 1708
    MSI (s) (90:EC) [13:24:46:273]: Note: 1: 2205 2:  3: Error
    MSI (s) (90:EC) [13:24:46:336]: Note: 1: 2228 2:  3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1708
    MSI (s) (90:EC) [13:24:46:414]: Note: 1: 2205 2:  3: Error
    MSI (s) (90:EC) [13:24:46:461]: Note: 1: 2228 2:  3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1709
    MSI (s) (90:EC) [13:24:46:555]: Product: Windows Small Business Server 2011 Connector -- Installation failed.

    MSI (s) (90:EC) [13:24:46:649]: Cleaning up uninstalled install packages, if any exist
    MSI (s) (90:EC) [13:24:46:727]: MainEngineThread is returning 1603
    MSI (s) (90:D8) [13:24:46:930]: Destroying RemoteAPI object.
    MSI (s) (90:2C) [13:24:46:992]: Custom Action Manager thread ending.
    MSI (c) (78:D4) [13:24:47:102]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
    MSI (c) (78:D4) [13:24:47:164]: MainEngineThread is returning 1603
    === Verbose logging stopped: 8/2/2011  13:24:47 ===

     

     


    salt4502
    Thursday, August 04, 2011 5:17 AM
  • Hi,

    Look like there is something wrong with the task scheduler, could you check the following FAQ

    http://social.technet.microsoft.com/wiki/contents/articles/3941.aspx

    this section to see whether it would help

    You receive the error “The installation is cancelled. The Windows Server Connector has encountered an unexpected error”

    Thanks.

    Thursday, August 04, 2011 5:30 AM
  • Thanks for the quick response Xiaofeng

    I had found this page before but was in a rush and only tried the first one. Guess I should of scrolled down farther.

    When I was checking the services on the client I was working on I seem to remember seeing that service not running, but I'm not sure. I'll try it tomorrow and post back here to let you know how it went. Here's to hoping this one works.

    Thanks


    salt4502
    Thursday, August 04, 2011 6:28 AM
  • Hi again Xiaofeng

    I just noticed this applies to vista & windows 7. Also I checked services on my xp pro system and did not see WMCS listed.
    Are you saying to check and see if task schedular is turned on?

    Thanks


    salt4502
    Thursday, August 04, 2011 6:56 AM
  • Hi again

    Tried it again today. still same errors. Still need Help. Anyone?


    salt4502
    Thursday, August 04, 2011 7:45 PM
  • Hi,

    Have you checked the whether Task Scheduler Service is running on your client?

    Thanks

    Friday, August 05, 2011 6:56 AM
  • Hi Xiaofeng

    Yes, it was. I compared all the services between two of the laptops that were identical and they were pretty much the same. The ones that were different wouldn't affect the outcome. The launchpad installation gets about halfway and then reverses itself. It's been doing that since the first time. The only thing that I wonder about is the first time I tried it I didn't know that the network cable was unplugged from the laptop and on wireless. This left the launchpad only half installed with no way of removing the remnants except by removing it manually. Would this cause the problem even though the logs were all the same since the beginning of my nightmare.


    salt4502
    • Proposed as answer by vdibbert Sunday, March 10, 2013 12:53 PM
    Friday, August 05, 2011 7:34 AM
  • Does anybody have any idea what is causing this problem? My only option right now is to do full reinstall of the OS and I really don't want to do that. This glitch is probably the result of just one little thing and I can't find it.
    salt4502
    Sunday, August 07, 2011 8:33 AM
  • I noticed there is an exception in clientdeploy.log "644] 110802.131901.5382: ClientSetup: Exception in CheckNetworkAdapter: System" .In that point what will do is set your client computer's primary DNS to server. So you can try to set your client computer's DNS manually, and try again.  But I can't figure out the exception in MSI log has anything to do with DNS not configured correctly.

     

    Sunday, August 07, 2011 9:19 AM
  • I try to search " task scheduler 0x80090016" , and found some topics. You can identify if your Task Scheduler Service is good on your computer. Follow http://support.microsoft.com/kb/308569 and schedule a task yourself.  
    Sunday, August 07, 2011 10:35 AM
  • Thanks for answering sbs

    I can't access the laptop till Monday, Chicago time.

    If it is the task scheduler would its corruption affect the system. I did an error check of the C drive and found nothing wrong but the system runs kind of sluggish. When I type it takes a second or two for characters to appear on the screen. I found a fix for task scheduler but that might only fix a symptom, not the cause. Would a system repair fix system corruption verses a full reinstall of the OS?

    Thanks


    salt4502
    Sunday, August 07, 2011 6:54 PM
  • Please try to fix task scheduler first if it really not work and to see whether you can install connector afterwards. I really want to know If that fix works for you because it may be helpful to other users.  Do you use System repair before? I didn't have chance to use it and other people say it s not very easy to use....  And I think WHS's backup functionality can restore a PC from system corruption, thought it's not helpful to your case.
    Monday, August 08, 2011 1:10 AM
  • Hi sbs

    I'll see whats up with task scheduler tomorrow plus try a couple of other things if that doesn't work.

    As far as a system repair goes I only use it as a last resort if a os is really messed up and there is no backup available. All it does is restore windows to it's original condition without reformating the disk. It leaves all the programs, files and settings intact. The only downside is you have to reinstall all the windows updates. But if you have a slipstreamed xp cd with all the updates on it, it doesn't take long to get it done. It sure beats a complete os reinstall.


    salt4502
    Monday, August 08, 2011 2:59 AM
  • Hi,

    Have you workaround this issue? I have used bing translate to view these two threads, which specific steps you have done to fix the issue?

    Thanks.

    Tuesday, August 09, 2011 1:28 AM
  • Solved!!!

    First off I would like to thank sbs_sdet_w  and Xioafeng for helping me with this. I give them credit for steering me in the right direction but I'm marking this as answer because it explains how to fix it.

    I don't know if this fix will work for everyone, but I sure hope it does because it'll make you pull your hair out if you can't figure it out. This fix should work for SBS Essentials 2011 and WHS 2011. They are both about the same and considering the logs on here are from SBS Essentials 2011 and it worked, it should also work on WHS 2011

    The main problem with this was caused by the security permissions for task scheduler being corrupted. If you see these lines at the bottom of your clientdeploy.log:

     

    "[644] 110802.131926.8092: ClientSetup: Running MSI: C:\WINDOWS\Temp\Client Deployment Files\ClientCoreX86.msi  SOFTWARE_NAME="Windows Small Business Server 2011" REBOOT=ReallySuppress
    [644] 110802.132447.3678: ClientSetup: Running MSI threw an exception:Microsoft.Deployment.WindowsInstaller.InstallerException: Fatal error during installation.
       at Microsoft.Deployment.WindowsInstaller.Installer.CheckInstallResult(UInt32 ret)
       at Microsoft.WindowsServerSolutions.ClientSetup.ClientDeploy.Helper.RunMsi(String msiPathOrProductCode, String logFilePath, Dictionary`2 msiProperties, Boolean install, ProgressChangedEventHandler progressHandler)
    [644] 110802.132447.3678: ClientSetup: RunMsi returned error: RetCode=1603
    [644] 110802.132447.3678: ClientSetup: Failed to install C:\WINDOWS\Temp\Client Deployment Files\ClientCoreX86.msi
    [644] 110802.132447.3678: ClientSetup: Exting InstallSoftwareTask.Run
    [644] 110802.132447.3678: ClientSetup: Task with Id=ClientDeploy.InstallSoftware has TaskStatus=Failed

    [644] 110802.132447.3678: ClientSetup: Task with Id=ClientDeploy.InstallSoftware has RebootStatus=NoReboot
    [644] 110802.132447.3678: ClientSetup: Exting ConnectorWizardForm.RunTasks
    [1740] 110802.132503.2127: ClientSetup: Back from the Client Deployment Wizard
    [1740] 110802.132503.2127: ClientSetup: Saving Wizard Data
    [1740] 110802.132503.2284: ClientSetup: End of ClientDeploy: ErrorCode=1603"

     

    This is what prevented Launchpad from installing. None of the other errors I posted on here were related to the problem as they were still present in the logs after I had a successful install of Launchpad.

    To fix this do the following.

    First you need to see if task scheduler is running properly. Use this link provided by sbs_sdet_w to set it up if you don't know how  http://support.microsoft.com/kb/308569
    Just pick any old task to run. I used disk cleanup and set it to run once. When you run it if you get the error "Task Scheduler error,0x80090016,Keyset does not exist" you just do this next.

    1. Stop the Task Scheduler Service  (run => services.msc)
    2. Delete or Move ( I created a new folder and dumped them in there) the file(s) from the
      "C:Documents and Settings\All Users\Application Data\Microsoft\Crypto\RSA-S-1-5-18" folder.
    3. Start the Task Scheduler Service.
    4. Edit each previously scheduled task and provide security credentials( It'll as you for your login) for the task to run under.
    5. Right click a task and choose run.

    The task should run correctly and it should also run as scheduled.

    If task scheduler works you should be able to reinstall Launchpad with no problems now. If you haven't cleaned out your old installation of Launched do it before you reinstall.
    If you haven't done that before do the following.

         1.  Remove the clients computer from the Server and restart it.
         2.  On the clients computer itself, go to Control Panel- System- Computer Name and click Change.
         3.  On this tab change the computers name to anything you want to name it as long as it's different from the one that is already there.
         4.  Change Domain to Workgroup and use the name of the Workgroup you belonged to before. If not, just put Anything.
         5.  Click OK, You're Login screen should appear, Type in your login for the computer and then follow the on screen instructions to finish.
         6.  After the computer finishes rebooting run a good cleaner like CCleaner. Run the file cleaner and the registry cleaner. This gets enough of
              the old files out to reinstall Launchpad.

    After that, reinstall the Launchpad software and you should be good to go. I didn't have to uninstall .net 4.0 or turn off my antivirus software. But if you don't want to take any chances of it screwing up again, shut off anything running in the background just to be sure.

    This is all I did and it worked well for me. Some of your experiences may be different. If I missed anything please feel free to post here and correct it. If you are having this problem, I hope this works for you.

    Thanks

     


    salt
    • Marked as answer by salt4502 Tuesday, August 09, 2011 2:44 AM
    Tuesday, August 09, 2011 2:08 AM
  • Very nice. I'm sure your success will benefit a lot of people and our customers, own you a lot of thanks.

    Wednesday, August 10, 2011 1:08 AM
  • sbs_sdet_w

    Thanks for your help, it was much appreciated. We're just a small group and I'm the only one that knows what to do and I'm a newb at this.

     


    salt
    Wednesday, August 10, 2011 3:19 AM
  • Thanks for the fix, I had the same error today on my new laptop.   (and couldnt reinstall the connector software)  I have the same errors in my logs.

    My Scheduled Tasks were fine on both the server and client laptop.   The deleting computer name off the server, then changing client computer name to something else, & cleaning files/registry with CCleaner did the trick.    Re-install success, launch pad/connector working

    I'm now back up and running !   I just hope the problem doesnt come back.   My original problem is DashBoard times out trying to connect.

    http://experts.windows.com/frms/windows_entertainment_and_connected_home/f/68/p/102115/545465.aspx

    What would cause things to stop connecting the next day?  (no changes introduced)  See detail in link above)

    Tuesday, October 04, 2011 11:45 PM

  • Thanks for the fix, I had the same error today on my new laptop.   (and couldnt reinstall the connector software)  I have the same errors in my logs.

    My Scheduled Tasks were fine on both the server and client laptop.   The deleting computer name off the server, then changing client computer name to something else, & cleaning files/registry with CCleaner did the trick.    Re-install success, launch pad/connector working

    I'm now back up and running !   I just hope the problem doesnt come back.   My original problem is DashBoard times out trying to connect.

    http://experts.windows.com/frms/windows_entertainment_and_connected_home/f/68/p/102115/545465.aspx

    What would cause things to stop connecting the next day?  (no changes introduced)  See detail in link above)

    I spoke too soon!   I let my laptop go to sleep when I went to the post office.   I can back, unlocked the computer, and I saw LaunchPad having trouble connecting again!
    I'm having the same problem as in the link above again.   What the heck makes everything work smoothly after the install, and then bomb out permanently after the first time locking/unlocking or rebooting the client? 

     

     

    Popup =

    "Alert Viewer Error

    Alert notices are not available in the Alert Viewer due to an error, or incomplete action, or a service has stopped working. If the problem persists, contact the person who administr"

     

    LaunchPad asks for the username & password.  I enter it, it tries awhile then:

    "The Server appears to be offline.  Do you want to sign in to offline mode"

    I'm going to be forced to uninstall and reinstall the connector yet again, but it won't last.  What the heck?

    [6500] 111004.162703.3377: ClientSetup: Running Task with Id=ClientDeploy.DownloadSoftware
    [6500] 111004.162703.3533: ClientSetup: Entering DownloadSoftwareTask.Run
    [6500] 111004.162703.3533: ClientSetup: Download client package ClientCore.cab
    [6500] 111004.162703.3689: ClientSetup: Download file ClientCore.cab from server
    [6500] 111004.162703.3689: ClientSetup: Making web request: System.Net.HttpWebRequest
    [6500] 111004.162708.3921: ClientSetup: Downloaded file C:\Windows\Temp\Client Deployment Files\ClientCore.cab
    [6500] 111004.162708.8601: ClientSetup: Found MSI file within cab: ClientCore.msi
    [6500] 111004.162708.8601: ClientSetup: Found MSP file within cab: KB2554637-amd64.msp
    [6500] 111004.162708.8601: ClientSetup: Exiting DownloadSoftwareTask.Run
    [6500] 111004.162708.8601: ClientSetup: Task with Id=ClientDeploy.DownloadSoftware has TaskStatus=Success
    [6500] 111004.162708.8757: ClientSetup: Task with Id=ClientDeploy.DownloadSoftware has RebootStatus=NoReboot
    [6500] 111004.162708.8757: ClientSetup: Running Task with Id=ClientDeploy.InstallSoftware
    [6500] 111004.162708.8757: ClientSetup: Entering InstallSoftwareTask.Run
    [6500] 111004.162708.8757: ClientSetup: Install package C:\Windows\Temp\Client Deployment Files\ClientCore.msi
    [6500] 111004.162708.9069: ClientSetup: Running MSI: C:\Windows\Temp\Client Deployment Files\ClientCore.msi  SOFTWARE_NAME="Windows Home Server 2011" ADMIN_USERNAME="Administrator" ADMIN_PASSWORD=******* PATCH="C:\Windows\Temp\Client Deployment Files\KB2554637-amd64.msp" REBOOT=ReallySuppress
    [6500] 111004.162758.8114: ClientSetup: Exting InstallSoftwareTask.Run
    [6500] 111004.162758.8114: ClientSetup: Task with Id=ClientDeploy.InstallSoftware has TaskStatus=Success
    [6500] 111004.162758.8114: ClientSetup: Task with Id=ClientDeploy.InstallSoftware has RebootStatus=NoReboot
    [6500] 111004.162758.8114: ClientSetup: Running Task with Id=ClientDeploy.EnableAndReportSqmData
    [6500] 111004.162758.8270: ClientSetup: Entering EnableAndReportSqmDataTask.Run
    [6500] 111004.162758.8738: ClientSetup: Trying to Start SqmProviderSvc
    [6500] 111004.162758.8894: SqmProvider: SqmProviderUtilities.TryStartSqmProviderService: Sqm service is set to AutoStart.
    [6500] 111004.162800.8862: SqmProvider: SqmProviderUtilities.TryStartSqmProviderService: Sqm service is started.
    [6500] 111004.162800.8862: ClientSetup: User selected to opt-in for SQM
    [6500] 111004.162800.9798: ProviderFramework: Information: [0] : Register to listen to ProviderRegistryConnectionMgmt connected event.
    [6500] 111004.162800.9954: ProviderFramework: Information: [0] : ProviderRegistryProxy: Beginning connection attempt.
    [6500] 111004.162801.0266: ProviderFramework: Information: [0] : ProviderRegistryProxy: Creating proxy for AutoReconnecter.
    [6500] 111004.162801.0578: ProviderFramework: Information: [0] : ConnectionMgmt: _CreateChannel address generated = [net.tcp://jazpad:6602//Microsoft.WindowsServerSolutions.Common.ProviderFramework.IProviderRegistry]
    [6500] 111004.162801.0734: ProviderFramework: Information: [0] : GetDuplexChannelFactory()
    [6500] 111004.162801.0890: ProviderFramework: Information: [0] : Contract: [Microsoft.WindowsServerSolutions.Common.ProviderFramework.IProviderRegistry]
    [6500] 111004.162801.0890: ProviderFramework: Information: [0] : Address: [net.tcp://jazpad:6602//Microsoft.WindowsServerSolutions.Common.ProviderFramework.IProviderRegistry]
    [6500] 111004.162801.0890: ProviderFramework: Information: [0] : Binding: []
    [6500] 111004.162801.0890: ProviderFramework: Information: [0] : Identifier: []
    [6500] 111004.162801.0890: ProviderFramework: Information: [0] : ProviderEndpointBehavior.AllowedConnectionType: [AllowRemoteAccess]
    [6500] 111004.162801.0890: ProviderFramework: Information: [0] : ProviderEndpointBehavior.EndpointCredentialType: [None]
    [6500] 111004.162801.0890: ProviderFramework: Information: [0] : RequiredImpersonationLevel: [Identification]
    [6500] 111004.162801.1670: PfBinding: Information: [0] : Adding service dns identity [JAZPAD] in proxy endpoint.
    [6500] 111004.162801.1982: ProviderFramework: Information: [0] : factory impersonation level is: [Identification]
    [6500] 111004.162801.3074: ProviderFramework: Information: [0] : ConnectAsync was NOT able to synchronously connect to the provider registry.
    [6500] 111004.162801.3386: ProviderFramework: Information: [0] : (current thread: 0x1964): PfSynchronizationContext not needed.
    [6500] 111004.162801.3386: ProviderFramework: Information: [0] : ProviderConnector: Querying for provider info: Microsoft.WindowsServerSolutions.Common.SqmProvider.Services.ISqmProviderService, False, Microsoft.WindowsServerSolutions.SqmProvider
    [7568] 111004.162801.4478: ProviderFramework: Information: [0] : _OnConnected called.
    [7568] 111004.162801.4634: ProviderFramework: Information: [0] : _CoreConnected is called.
    [7560] 111004.162801.5882: ProviderFramework: Information: [0] : ProviderConnector: received ProviderInfo Microsoft.WindowsServerSolutions.Common.SqmProvider.Services.ISqmProviderService net.tcp://127.0.0.1:65532/Microsoft.WindowsServerSolutions.SqmProvider/Microsoft.WindowsServerSolutions.Common.SqmProvider.Services.ISqmProviderService
    [7560] 111004.162801.6038: ProviderFramework: Information: [0] : ProviderConnector: Beginning connection attempt for Microsoft.WindowsServerSolutions.Common.SqmProvider.Services.ISqmProviderService
    [7560] 111004.162801.6350: ProviderFramework: Information: [0] : GetChannelFactory ()
    [7560] 111004.162801.6350: ProviderFramework: Information: [0] : Contract: [Microsoft.WindowsServerSolutions.Common.SqmProvider.Services.ISqmProviderService]
    [7560] 111004.162801.6350: ProviderFramework: Information: [0] : Address: [net.tcp://127.0.0.1:65532/Microsoft.WindowsServerSolutions.SqmProvider/Microsoft.WindowsServerSolutions.Common.SqmProvider.Services.ISqmProviderService]
    [7560] 111004.162801.6350: ProviderFramework: Information: [0] : Binding: [net.tcp]
    [7560] 111004.162801.6350: ProviderFramework: Information: [0] : Identifier: [Microsoft.WindowsServerSolutions.SqmProvider]
    [7560] 111004.162801.6350: ProviderFramework: Information: [0] : ProviderEndpointBehavior.AllowedConnectionType: [AllowLocalAccessOnly]
    [7560] 111004.162801.6350: ProviderFramework: Information: [0] : ProviderEndpointBehavior.EndpointCredentialType: [User]
    [7560] 111004.162801.6350: ProviderFramework: Information: [0] : RequiredImpersonationLevel: [Identification]
    [7560] 111004.162801.6350: ProviderFramework: Information: [0] : Creating service/proxy endpoint for Contract [ISqmProviderService], binding = [CustomBinding], EndpointAddress = [net.tcp://127.0.0.1:65532/Microsoft.WindowsServerSolutions.SqmProvider/Microsoft.WindowsServerSolutions.Common.SqmProvider.Services.ISqmProviderService], AllowedConnectionType = [AllowLocalAccessOnly], EndpointCredentialType = [User]
    [7560] 111004.162801.6506: ProviderFramework: Information: [0] : factory impersonation level is: [Identification]
    [7560] 111004.162801.7910: ProviderFramework: Information: [0] : ProviderConnector: Received connection
    [7560] 111004.162801.7910: ProviderFramework: Information: [0] : ProviderConnector: Successfully connected for Microsoft.WindowsServerSolutions.Common.SqmProvider.Services.ISqmProviderService
    [6500] 111004.162801.8222: ClientSetup: Exting EnableAndReportSqmDataTask.Run
    [6500] 111004.162801.8222: ClientSetup: Task with Id=ClientDeploy.EnableAndReportSqmData has TaskStatus=Success
    [6500] 111004.162801.8222: ClientSetup: Task with Id=ClientDeploy.EnableAndReportSqmData has RebootStatus=NoReboot
    [6500] 111004.162801.8222: ClientSetup: Exting ConnectorWizardForm.RunTasks
    [6364] 111004.162806.0186: ClientSetup: Back from the Client Deployment Wizard
    [6364] 111004.162806.0186: ClientSetup: Saving Wizard Data
    [6364] 111004.162806.0498: ClientSetup: End of ClientDeploy: ErrorCode=0
    • Edited by JazJon Wednesday, October 05, 2011 12:59 AM
    Wednesday, October 05, 2011 12:50 AM
  •  

    I found another fix for the LaunchPad staying offline problem in my last post.

    http://social.microsoft.com/Forums/is/whs2011/thread/3875d337-c264-4c33-abfc-079de07634b7

     

    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 100000 

    (then click OK


    5.Restart the computer. 


    Works! Connecting great again.

     

     

    Wednesday, October 05, 2011 1:37 AM