Agree with John here. Remove WSUS and start up again On Thu, Nov 19, 2015 at 3:44 PM, Marcum, John <[email protected]> wrote:
> Easiest answer here is take this chance to upgrade all that old crap. J > > > > Second easiest is… Anytime I see WSUS break I find it quicker to uninstall > and reinstall it than to troubleshoot it. > > > * ------------------------------ * > > * John Marcum* > > MCITP, MCTS, MCSA > * Desktop Architect* > > * Bradley Arant Boult Cummings LLP* > * ------------------------------ * > > > > [image: H_Logo] > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Haritwal, Dhiraj > *Sent:* Thursday, November 19, 2015 9:24 AM > *To:* [email protected] > *Subject:* [mssms] WSUS stopped working > > > > Hi, > > > > We are using SCCM 2007 SP2 on Windows server 2003 SP2 with WSUS > 3.2.7600.226 which is stopped working from couple of weeks & getting below > errors. > > > > Appreciate any help to resolve this issue. > > > > > > *WSUS Software Distribution Log* > > > > The assembly or AppDomain that failed was: > > mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 > > 2015-11-19 14:56:37.353 UTC Warning > w3wp.6 SoapExceptionProcessor.SerializeAndThrow > Discarding stack trace for user , IP Address , exception > System.Security.SecurityException: Request for principal permission failed. > > at > System.Security.Permissions.PrincipalPermission.ThrowSecurityException() > > at System.Security.Permissions.PrincipalPermission.Demand() > > at System.Security.PermissionSet.DemandNonCAS() > > at > Microsoft.UpdateServices.Internal.DatabaseAccess.AdminDataAccess.GetServerVersion() > > at Microsoft.UpdateServices.Internal.ApiRemoting.GetServerVersion() > > The action that failed was: > > Demand > > The type of the first permission that failed was: > > System.Security.Permissions.PrincipalPermission > > The first permission that failed was: > > <IPermission class="System.Security.Permissions.PrincipalPermission, > mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" > > version="1"> > > <Identity Authenticated="true" > > Role="ViewServerSetting"/> > > </IPermission> > > > > > > > > *SMS_WSUS_SYNC_MANAGER Logs* > > > > Event Type: Error > > Event Source: SMS Server > > Event Category: SMS_WSUS_SYNC_MANAGER > > Event ID: 6703 > > Date: 11/19/2015 > > Time: 8:14:55 PM > > User: N/A > > > > Description: > > On 11/19/15 20:14:55, component SMS_WSUS_SYNC_MANAGER on computer > SCCMServer reported: SMS WSUS Synchronization failed. > > Message: WSUS server not configured. > > Source: CWSyncMgr::DoSync. > > The operating system reported error 2147500037: Unspecified error > > > > Regards, > > > > Dhiraj > > > > > > > ------------------------------ > > > This email is confidential and intended only for the use of the individual > or entity named above and may contain information that is privileged. If > you are not the intended recipient, you are notified that any > dissemination, distribution or copying of this email is strictly > prohibited. If you have received this email in error, please notify us > immediately by return email or telephone and destroy the original message. > - This mail is sent via Sony Asia Pacific Mail Gateway.. > > ------------------------------ > > > Confidentiality Notice: This e-mail is from a law firm and may be > protected by the attorney-client or work product privileges. If you have > received this message in error, please notify the sender by replying to > this e-mail and then delete it from your computer. > >
