http://blogs.technet.com/b/gborger/archive/2009/02/27/exploring-the-wsus-windows-internal-database.aspx
  
 

    On Tuesday, January 12, 2016 2:10 PM, David McSpadden <[email protected]> 
wrote:
 

  <!--#yiv9375205618 _filtered #yiv9375205618 {font-family:Helvetica;panose-1:2 
11 6 4 2 2 2 2 2 4;} _filtered #yiv9375205618 {font-family:"Cambria 
Math";panose-1:2 4 5 3 5 4 6 3 2 4;} _filtered #yiv9375205618 
{font-family:Calibri;panose-1:2 15 5 2 2 2 4 3 2 4;} _filtered #yiv9375205618 
{font-family:Montserrat;} _filtered #yiv9375205618 
{font-family:Verdana;panose-1:2 11 6 4 3 5 4 4 2 4;}#yiv9375205618 
#yiv9375205618 p.yiv9375205618MsoNormal, #yiv9375205618 
li.yiv9375205618MsoNormal, #yiv9375205618 div.yiv9375205618MsoNormal 
{margin:0in;margin-bottom:.0001pt;font-size:12.0pt;font-family:"Times New 
Roman", serif;}#yiv9375205618 a:link, #yiv9375205618 
span.yiv9375205618MsoHyperlink 
{color:blue;text-decoration:underline;}#yiv9375205618 a:visited, #yiv9375205618 
span.yiv9375205618MsoHyperlinkFollowed 
{color:purple;text-decoration:underline;}#yiv9375205618 p 
{margin-right:0in;margin-left:0in;font-size:12.0pt;font-family:"Times New 
Roman", serif;}#yiv9375205618 p.yiv9375205618msonormal0, #yiv9375205618 
li.yiv9375205618msonormal0, #yiv9375205618 div.yiv9375205618msonormal0 
{margin-right:0in;margin-left:0in;font-size:12.0pt;font-family:"Times New 
Roman", serif;}#yiv9375205618 p.yiv9375205618msonormal, #yiv9375205618 
li.yiv9375205618msonormal, #yiv9375205618 div.yiv9375205618msonormal 
{margin-right:0in;margin-left:0in;font-size:12.0pt;font-family:"Times New 
Roman", serif;}#yiv9375205618 p.yiv9375205618msochpdefault, #yiv9375205618 
li.yiv9375205618msochpdefault, #yiv9375205618 div.yiv9375205618msochpdefault 
{margin-right:0in;margin-left:0in;font-size:12.0pt;font-family:"Times New 
Roman", serif;}#yiv9375205618 p.yiv9375205618msonormal1, #yiv9375205618 
li.yiv9375205618msonormal1, #yiv9375205618 div.yiv9375205618msonormal1 
{margin:0in;margin-bottom:.0001pt;font-size:12.0pt;font-family:"Times New 
Roman", serif;}#yiv9375205618 p.yiv9375205618msochpdefault1, #yiv9375205618 
li.yiv9375205618msochpdefault1, #yiv9375205618 div.yiv9375205618msochpdefault1 
{margin-right:0in;margin-left:0in;font-size:10.0pt;font-family:"Times New 
Roman", serif;}#yiv9375205618 span.yiv9375205618msohyperlink {}#yiv9375205618 
span.yiv9375205618msohyperlinkfollowed {}#yiv9375205618 
span.yiv9375205618emailstyle18 {}#yiv9375205618 span.yiv9375205618emailstyle19 
{}#yiv9375205618 span.yiv9375205618msohyperlink1 
{color:blue;text-decoration:underline;}#yiv9375205618 
span.yiv9375205618msohyperlinkfollowed1 
{color:purple;text-decoration:underline;}#yiv9375205618 
span.yiv9375205618emailstyle181 {font-family:"Calibri", 
sans-serif;color:#1F497D;}#yiv9375205618 span.yiv9375205618emailstyle191 
{font-family:"Calibri", sans-serif;color:#1F497D;}#yiv9375205618 
span.yiv9375205618EmailStyle31 {font-family:"Calibri", 
sans-serif;color:#1F497D;}#yiv9375205618 span.yiv9375205618EmailStyle32 
{font-family:"Calibri", sans-serif;color:#1F497D;}#yiv9375205618 
span.yiv9375205618EmailStyle33 {font-family:"Calibri", 
sans-serif;color:#1F497D;}#yiv9375205618 .yiv9375205618MsoChpDefault 
{font-size:10.0pt;} _filtered #yiv9375205618 {margin:1.0in 1.0in 1.0in 
1.0in;}#yiv9375205618 div.yiv9375205618WordSection1 {}-->Server 2012 R2 Local 
machine Sql 2012 installed.       From: [email protected] 
[mailto:[email protected]]On Behalf Of Damien Solodow
Sent: Tuesday, January 12, 2016 3:04 PM
To: [email protected]
Subject: RE: [mssms] error 8007000E in windowsupdates log    Accessing WID is a 
bit tricky; what version of Windows are you running the WSUS instance on, and 
are you trying to run Management Studio from that server or a remote machine?   
 DAMIEN SOLODOW Senior Systems Engineer 317.447.6033 (office) 317.447.6014 
(fax) HARRISON COLLEGE    From:[email protected] 
[mailto:[email protected]]On Behalf Of David McSpadden
Sent: Tuesday, January 12, 2016 2:56 PM
To: [email protected]
Subject: RE: [mssms] error 8007000E in windowsupdates log    Read the articles. 
Want to access SUSB but I don’t see it. I see MSSQLSERVER for (SCCM I am sure) 
and WID  for (WSUS I am sure) I can not access the WID from Management Studio? 
What am I doing wrong?       From:[email protected] 
[mailto:[email protected]]On Behalf Of Sherry Kissinger
Sent: Tuesday, January 12, 2016 10:41 AM
To: [email protected]
Subject: Re: [mssms] error 8007000E in windowsupdates log     some possibly 
related reading material:    
http://blog.coretech.dk/kea/house-of-cardsthe-configmgr-software-update-point-and-wsus/
    
http://www.mnscug.org/blogs/sherry-kissinger/360-wsus-sup-servers-in-configmgr-2012-custom-configuration-settings
             On Tuesday, January 12, 2016 7:51 AM, David McSpadden 
<[email protected]> wrote:    Hadn’t seen that mentioned yet. Will push in that 
direction as well. Thank you   From:[email protected] 
[mailto:[email protected]]On Behalf Of Enley, Carl
Sent: Tuesday, January 12, 2016 8:47 AM
To: [email protected]
Subject: RE: [mssms] error 8007000E in windowsupdates log   I was recently 
facing that same error message on a child site even after applying KB3112343 to 
those clients. It turns out that the WSUS App pool needed more memory, you can 
check some of the IIS logs and the sofwaredistribution logs on the WSUS server 
and see error messages.   From:[email protected] 
[mailto:[email protected]]On Behalf Of Niall Brady
Sent: Tuesday, January 12, 2016 8:41 AM
To: [email protected]
Cc: Patch Management Mailing List ([email protected])
Subject: Re: [mssms] error 8007000E in windowsupdates log   that error 
translates to

"Not enough storage is available to complete this operation.

Source: Windows
-----
" maybe something to check ? (memory wise..) i seem to recall others with the 
same issue recently.. can't recall the fix though   On Tue, Jan 12, 2016 at 
2:28 PM, David McSpadden <[email protected]> wrote: I am applying Q3112343 for 
these machines that are showing the error 8007000E (Win7pro32bit). Once this 
update is applied and the machine has rebooted all other updates should flow 
correctly, right?     David McSpadden System Administrator Indiana Members 
Credit Union P: 317.554.8190           This e-mail and any files transmitted 
with it are property of Indiana Members Credit Union, are confidential, and are 
intended solely for the use of the individual or entity to whom this e-mail is 
addressed. If you are not one of the named recipient(s) or otherwise have 
reason to believe that you have received this message in error, please notify 
the sender and delete this message immediately from your computer. Any other 
use, retention, dissemination, forwarding, printing, or copying of this email 
is strictly prohibited.   Please consider the environment before printing this 
email.         This e-mail and any files transmitted with it are property of 
Indiana Members Credit Union, are confidential, and are intended solely for the 
use of the individual or entity to whom this e-mail is addressed. If you are 
not one of the named recipient(s) or otherwise have reason to believe that you 
have received this message in error, please notify the sender and delete this 
message immediately from your computer. Any other use, retention, 
dissemination, forwarding, printing, or copying of this email is strictly 
prohibited.    Please consider the environment before printing this email.      
    This e-mail and any files transmitted with it are property of Indiana 
Members Credit Union, are confidential, and are intended solely for the use of 
the individual or entity to whom this e-mail is addressed. If you are not one 
of the named recipient(s) or otherwise have reason to believe that you have 
received this message in error, please notify the sender and delete this 
message immediately from your computer. Any other use, retention, 
dissemination, forwarding, printing, or copying of this email is strictly 
prohibited.    Please consider the environment before printing this email.      
 This e-mail and any files transmitted with it are property of Indiana Members 
Credit Union, are confidential, and are intended solely for the use of the 
individual or entity to whom this e-mail is addressed. If you are not one of 
the named recipient(s) or otherwise have reason to believe that you have 
received this message in error, please notify the sender and delete this 
message immediately from your computer. Any other use, retention, 
dissemination, forwarding, printing, or copying of this email is strictly 
prohibited.
Please consider the environment before printing this email.


  


Reply via email to