Tech Support Forum banner
Status
Not open for further replies.
1 - 1 of 1 Posts

· Registered
Joined
·
936 Posts
Discussion Starter · #1 ·
I'm running this server and a couple Win 7 clients. Recently, the boot Launchpad (from the client) stopped connecting with an error log:

[2392] 130401.200901.7864: General: Branding colors XML parsing started
[2392] 130401.200901.7864: General: Branding colors XML parsing ended
[2392] 130401.200901.7864: General: Looking for OEM branding colors XML
[2392] 130401.200901.7864: General: No OEM informations available
[2392] 130401.200901.7864: General: Color branding complete
[4968] 130401.200901.7864: ProviderFramework: Information: [0] : Register to listen to ProviderRegistryConnectionMgmt connected event.
[4968] 130401.200901.7964: ProviderFramework: Information: [0] : ProviderRegistryProxy: Beginning connection attempt.
[4968] 130401.200901.8064: ProviderFramework: Information: [0] : ProviderRegistryProxy: Creating proxy for AutoReconnecter.
[4968] 130401.200901.8164: ProviderFramework: Information: [0] : ConnectionMgmt: _CreateChannel address generated = [net.tcp://collector-pc:6602//Microsoft.WindowsServerSolutions.Common.ProviderFramework.IProviderRegistry]
[4968] 130401.200901.8164: ProviderFramework: Information: [0] : GetDuplexChannelFactory()
[4968] 130401.200901.8164: ProviderFramework: Information: [0] : Contract: [Microsoft.WindowsServerSolutions.Common.ProviderFramework.IProviderRegistry]
[4968] 130401.200901.8164: ProviderFramework: Information: [0] : Address: [net.tcp://collector-pc:6602//Microsoft.WindowsServerSolutions.Common.ProviderFramework.IProviderRegistry]
[4968] 130401.200901.8164: ProviderFramework: Information: [0] : Binding: []
[4968] 130401.200901.8164: ProviderFramework: Information: [0] : Identifier: []
[4968] 130401.200901.8164: ProviderFramework: Information: [0] : ProviderEndpointBehavior.AllowedConnectionType: [AllowRemoteAccess]
[4968] 130401.200901.8164: ProviderFramework: Information: [0] : ProviderEndpointBehavior.EndpointCredentialType: [None]
[4968] 130401.200901.8164: ProviderFramework: Information: [0] : RequiredImpersonationLevel: [Identification]
[4968] 130401.200901.8864: WssgCertMgmt: Collection Empty
[4968] 130401.200901.8864: IDENTITY: Root cert backup not found.
[4968] 130401.200901.8864: PfBinding: Error: [0] : Valid machine certificate is not found.
[2392] 130401.200901.8964: General: Restoring window location settings
[2392] 130401.200901.8964: General: Location string: 1451|23|280|400|Normal|1591|223|{X=0,Y=0,Width=1920,Height=1200}{X=0,Y=0,Width=1920,Height=1200}True{X=1920,Y=0,Width=1680,Height=1050}{X=1920,Y=0,Width=1680,Height=1050}False
[2392] 130401.200901.8964: General: Window location settings restored successfully
[5908] 130401.200901.9064: ClientSetup: NetGetJoinInformation (server = [], ...)
[5908] 130401.200901.9664: ProviderFramework: Information: [0] : (current thread: 0x1714): PfSynchronizationContext not needed.
[5908] 130401.200901.9664: ProviderFramework: Information: [0] : (current thread: 0x1714): PfSynchronizationContext not needed.
[4968] 130401.200901.9664: ProviderFramework: Information: [0] : (current thread: 0x1368): PfSynchronizationContext not needed.
[4968] 130401.200901.9664: ProviderFramework: Information: [0] : (current thread: 0x1368): PfSynchronizationContext not needed.
[3324] 130401.200901.9764: ProviderFramework: Information: [0] : Register to listen to ProviderRegistryConnectionMgmt connected event.
[3324] 130401.200901.9764: ProviderFramework: Information: [0] : ProviderRegistryProxy: Beginning connection attempt.
[3324] 130401.200901.9764: ProviderFramework: Information: [0] : ProviderRegistryProxy: Creating proxy for AutoReconnecter.
[3324] 130401.200901.9764: ProviderFramework: Information: [0] : ConnectionMgmt: _CreateChannel address generated = [net.tcp://collector-pc:6602//Microsoft.WindowsServerSolutions.Common.ProviderFramework.IProviderRegistry]
[3324] 130401.200901.9764: ProviderFramework: Information: [0] : GetDuplexChannelFactory()
[3324] 130401.200901.9764: ProviderFramework: Information: [0] : Contract: [Microsoft.WindowsServerSolutions.Common.ProviderFramework.IProviderRegistry]
[3324] 130401.200901.9764: ProviderFramework: Information: [0] : Address: [net.tcp://collector-pc:6602//Microsoft.WindowsServerSolutions.Common.ProviderFramework.IProviderRegistry]
[3324] 130401.200901.9764: ProviderFramework: Information: [0] : Binding: []
[3324] 130401.200901.9764: ProviderFramework: Information: [0] : Identifier: []
[3324] 130401.200901.9764: ProviderFramework: Information: [0] : ProviderEndpointBehavior.AllowedConnectionType: [AllowRemoteAccess]
[3324] 130401.200901.9764: ProviderFramework: Information: [0] : ProviderEndpointBehavior.EndpointCredentialType: [None]
[3324] 130401.200901.9764: ProviderFramework: Information: [0] : RequiredImpersonationLevel: [Identification]
[3324] 130401.200901.9764: WssgCertMgmt: Collection Empty
[3324] 130401.200901.9764: IDENTITY: Root cert backup not found.
[3324] 130401.200901.9764: PfBinding: Error: [0] : Valid machine certificate is not found.
[2392] 130401.200902.0464: LaunchPad: No file matching the '*.launchpad' file spec located in 'C:\Program Files\Windows Server\Bin\Launchpad'
[2392] 130401.200902.0464: LaunchPad: Loading data from file: C:\Program Files\Windows Server\Bin\Launchpad\LaunchPadContent.dll
[2392] 130401.200902.0664: LaunchPad: Finished loading data from file: C:\Program Files\Windows Server\Bin\Launchpad\LaunchPadContent.dll
[2392] 130401.200902.0664: LaunchPad: Loading data from file: C:\Program Files\Windows Server\Bin\Launchpad\en\LaunchPadContent.resources.dll
[2392] 130401.200902.0664: LaunchPad: Skipping satellite dll: 'C:\Program Files\Windows Server\Bin\Launchpad\en\LaunchPadContent.resources.dll'
[2392] 130401.200902.0664: LaunchPad: Scanning for empty categories...
[2392] 130401.200902.0664: LaunchPad: Removing empty category: name='_Add-ins' id='Microsoft.Launchpad.AddinCategory'
[2392] 130401.200902.0664: LaunchPad: Data loaded. Categories: 0; Tasks: 4
[2392] 130401.200902.0964: ServerDiscoveryObjectModel:Backend: Provider called while not connected (Connector is null). Please call Connect before using this property
[2392] 130401.200902.1064: LaunchPad: !!!!FATAL: Launchpad shutting down due to unhandled exception: Provider called while not connected (Connector is null). Please call Connect before using this property
[2392] 130401.200902.1064: Exception:
An exception of type 'Type: Microsoft.WindowsServerSolutions.Common.ProviderFramework.ProviderNotAvailableException, ProviderFramework, Version=6.1.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' has occurred.
Timestamp: 04/01/2013 20:09:02
Message: Provider called while not connected (Connector is null). Please call Connect before using this property
Stack: at Microsoft.WindowsServerSolutions.Networking.ServerDiscovery.ServerPresenceProviderBackend.StartServerPresenceDetection()
at Microsoft.WindowsServerSolutions.LaunchPad.ServerConnectivityStatus.connectWorker_RunWorkerCompleted(Object sender, RunWorkerCompletedEventArgs e)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler)
at System.Windows.Threading.Dispatcher.WrappedInvoke(Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
at System.Windows.Threading.DispatcherOperation.InvokeImpl()
at System.Threading.ExecutionContext.runTryCode(Object userData)
at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Windows.Threading.DispatcherOperation.Invoke()
at System.Windows.Threading.Dispatcher.ProcessQueue()
at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler)
at System.Windows.Threading.Dispatcher.WrappedInvoke(Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
at System.Windows.Threading.Dispatcher.InvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs)
at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)
at MS.Win32.UnsafeNativeMethods.DispatchMessage(MSG& msg)
at System.Windows.Threading.Dispatcher.PushFrameImpl(DispatcherFrame frame)
at System.Windows.Application.RunInternal(Window window)
at System.Windows.Application.Run()
at Microsoft.WindowsServerSolutions.LaunchPad.App.Main()
I've searched and there are no clear solutions that I've found online.

Further, I came across the folder that contains the logs while looking for a solution, and realized that these logs are being created fairly often, and I would like to relocate or limit log creation on the client PC, which boots off an SSD drive. Is there a way to limit the server logs from being created on the client PC?
 
1 - 1 of 1 Posts
Status
Not open for further replies.
Top