Windows 2008 R2 server BSOD; The bugcheck was: 0x0000001e (0xffffffffc0000005, 0xfffff88002b89950, 0x0000000000000000, 0x0000000000000000)

I have an unexpected shutdown today with the following error in Event Viewer -
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001e (0xffffffffc0000005, 0xfffff88002b89950, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 121813-82805-01.
Looks like this is related to some bad device drivers/software drivers - but dont know which one it is?? Could anyone please help me to identify what is the culprit device/software driver here?
Few more details are below (debugchk output) -
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
FAULTING_IP:
+0
fffff880`02b89950 78a8 js fffff880`02b898fa
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 0000000000000000
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800026c5100
GetUlongFromAddress: unable to read from fffff800026c51c0
0000000000000000 Nonpaged pool
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
Any help would be highly appreciated.
Regards,
Jami

Hi,
Thanks for posting in the forum.
Regarding the BSOD issue, it may be caused by the defective or mismatched RAM. At this time, I suggest we could try to run Memory Diagnostics test to check for any memory problems, or update
the chipset, video card, display and network adapter drivers to the latest to see if it could help.
Here is the similar thread as reference, hope it helps.
Getting Blue Screen stop code error 0x0000001E
http://answers.microsoft.com/en-us/windows/forum/windows_7-system/getting-blue-screen-stop-code-error-0x0000001e/61bb8396-6f66-49fc-9b8d-d103774485f4
Best Regards,
Andy Qi
Andy Qi
TechNet Community Support

Similar Messages

Need assistance with Windows 2008 R2 server BSOD - ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (fc)

Need assistance with Windows 2008 R2 server BSOD - ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (fc)
I have a Windows 2008 R2 server which is experiencing random BSOD during the night. This is occurring maybe once or twice a week. I have gathered two Memory crash files. This server is running Citrix XenApp 6.5 but nothing else is reporting an issue except
for the memory dump. I’m looking for assistance in reading crash file and finding the cause.
I’ve spent over a week going through articles trying to learn and trouble shoot the BSOD but no closer to understanding the WinDbg 6.3.9600 report.
This is a production server and I have verified that Windows Updates has updated the server with latest releases. I’m hoping that the crash file will show something before I have to run the Driver Verifier.
The crash zip file is located -
https://onedrive.live.com/redir?resid=9644A4E0A26873B1!2359&authkey=!AMS4Svuk-SS3-JA&ithint=file%2czip
*                        Bugcheck Analysis
ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (fc)
An attempt was made to execute non-executable memory. The guilty driver
is on the stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: fffff880009eff38, Virtual address for the attempted execute.
Arg2: 8000000002cfe963, PTE contents.
Arg3: fffff8800da2eea0, (reserved)
Arg4: 0000000000000002, (reserved)
Debugging Details:
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0xFC
PROCESS_NAME: powershell.exe
CURRENT_IRQL: 0
ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre
TRAP_FRAME: fffff8800da2eea0 -- (.trap 0xfffff8800da2eea0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa80070f3648 rbx=0000000000000000 rcx=fffffa80070f3648
rdx=fffff8800da2fbf8 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80001680b80 rsp=fffff8800da2f030 rbp=fffff8800da2fbd0
r8=fffff8a01804c680 r9=fffff8800da2fc68 r10=fffffffffffffffd
r11=fffff8800da2fa90 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up di pl nz na pe nc
nt!KiPageFault:
fffff800`01680b80 55              push    rbp
Resetting default scope
STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+44dfc
fffff800`017008b8 cc              int     3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+44dfc
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 531590fb
IMAGE_VERSION: 6.1.7601.18409
FAILURE_BUCKET_ID: X64_0xFC_nt!_??_::FNODOBFM::_string_+44dfc
BUCKET_ID: X64_0xFC_nt!_??_::FNODOBFM::_string_+44dfc
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0xfc_nt!_??_::fnodobfm::_string_+44dfc
FAILURE_ID_HASH: {aa632d36-b0f7-67cf-89e2-1cec389c0a11}
Followup: MachineOwner

Hi Kaysel_GTG,
Just addition. Regarding to Bug Check 0xFC, please refer to following article and check if can help you.
Bug Check 0xFC: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
By the way, since it is not effective for us to debug the crash dump file here in the forum. If this issues is a state of emergency for you. Please contact Microsoft Customer
Service and Support (CSS) via telephone so that a dedicated Support Professional can assist with your request.
To obtain the phone numbers for specific technology request, please refer to the web site listed below:
http://support.microsoft.com/default.aspx?scid=fh;EN-US;OfferProPhone#faq607
if any update, please feel free to let us know.
Hope this helps.
Best regards,
Justin Gu

How to solve repeated Bugcheck. The bugcheck was: 0x000000d1 (0x0000000000000010, 0x0000000000000002, 0x0000000000000000, 0xfffff8016a71d56c).

Log Name:      System
Source:        Microsoft-Windows-WER-SystemErrorReporting
Date:          6/25/2014 08:09:27
Event ID:      1001
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x000000d1 (0x0000000000000010, 0x0000000000000002, 0x0000000000000000, 0xfffff8016a71d56c). A dump was saved in: C:\windows\MEMORY.DMP. Report Id: 062514-17078-01.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck" />
    <EventID Qualifiers="16384">1001</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-06-25T15:09:27.000000000Z" />
    <EventRecordID>18419</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Security />
</System>
<EventData>
    <Data Name="param1">0x000000d1 (0x0000000000000010, 0x0000000000000002, 0x0000000000000000, 0xfffff8016a71d56c)</Data>
    <Data Name="param2">C:\windows\MEMORY.DMP</Data>
    <Data Name="param3">062514-17078-01</Data>
</EventData>
</Event>

Hi,
Do you need any further help regarding the BSOD here?
Besides, regarding Bugcheck ID 0xD1, please see:
Bug Check 0xD1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Please follow the suggestion provided by ZigZag team, upload us the dump file for further assistance.
Here for more information:
How to read the small memory dump file that is created
by Windows if a crash occurs
Best regards
Michael Shao
TechNet Community Support

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009e (0xfffffa8036f00980, 0x000000000000003c,

Hi,
I have an issue in my with my one of my Windows 2012 Failover node. One server was rebooted unexpectedly and i found the event id 1001 BugChecks
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009e (0xfffffa8036f00980, 0x000000000000003c, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 092614-45458-01.
Any solution ?
Regards
Kris

Hi Lotusnotes,
Please also refer to following article and check if can help you.
Why
is my Failover Clustering node blue screening with a Stop 0x0000009E?
In addition, troubleshoot this kind of kernel crash issue, we need to analyze the crash dump file to narrow down the root cause of the issue. You can refer to following articles
and check if can help you to analyze dump files.
Analyzing a Kernel-Mode Dump File
How to read the small memory dump file that is created by Windows if a crash occurs
Meanwhile, if this issues is a state of emergency for you. Please contact Microsoft Customer Service and Support (CSS) via telephone so that a dedicated Support Professional
can assist with your request.
To obtain the phone numbers for specific technology request, please refer to the web site listed below:
http://support.microsoft.com/default.aspx?scid=fh;EN-US;OfferProPhone#faq607
If any update, please feel free to let us know.
Hope this helps.
Best regards,
Justin Gu

Internet Explorer Security Support on Windows 7 & WIndows 2008 Std Server

I have an app page (tomcat https) that i was able to open from a windows 7 professional remotely but could not open from a windows 2008 std server. Is there a security settings I need to disable from windows 2008 std server? The firewall is disabled.
Both Win 7 & 2008 is on the same network.
Thanks in advance.
DT

Hi,
I need the error information from the Internet Explorer, if the error code is 404 that should be the webpage is not correctly developed, error code 500 means the tomcat server is not available, you should check the tomcat server, or another situation is
the port number is in use by another application, normally the default port number is 8080, you can try another port number in the comcat configuration file to see the result.
Regards
Wade Liu
TechNet Community Support

OS X Leopard and Windows 2008 file server mount_smbfs

Hello
I am unable to use the command mount_smbfs to mount a share on a Windows 2008 file server in OS X 10.5.8 Leopard.
Here is what I am trying to do:
I have a Mac Mini running OS X 10.5.8 that is joined to a Windows 2003 Active Directory domain. I also have a stand alone Windows file server running Windows Server 2008.
I want to mount a share on the Windows 2008 file Server using the command line and not Finder. I do have a reason for wanting to do this which I wont bore you with.
On the Mac Mini, I log in with an Domain account that has permission to access the file shares on the Windows 2008 file server. In Terminal I do the following:
cd /Users/username
mkdir mountpoint
mount_smbfs //windows2008server/fileshare /Users/username/mountpoint
This command should mount the share "fileshare" hosted on server "windows2008server" in the folder "mountpoint" on the Mac Mini.
Here is the problem:
When I execute this command, I get:
Password: so I put in my password
then I get:
mount_smbfs: mount error: /Users/username/mountpoint: Broken pipe
Analysis of the problem:
I tried exactly the same commands to mount a share on a Windows 2003 file server. I am not asked for my password and the share mounts perfectly. I also tried the same command in OS X 10.6 to mount a share on a Windows 2008 file server, again, I was not asked for my password and the share mounted perfectly.
So the problem is only mounting Windows 2008 file shares using mount_smbfs in OS X 10.5.8. I am not sure quite what is going wrong here, as the Mac is joined to the domain, it is granted a Kerberos ticket so should not be asking for my password. Is this a known bug in OS X 10.5? Is there a fix/workaround for it?
Many thanks
Richard.

Not sure what user the mount command defaults to. You may want to specify your user name in the mount command (you can also specify the password). Try using this:
mount_smbfs //username@windows2008server/fileshare /User/username/mountpoint
Of course substituting the Windows 2008 account name you are mounting with for the username.
Cheers,
Dave

Windows 2008 R2 Server without Service Pack 1 was flag "Not Required" during the SCCM patching/deploying SP1 for 2008

Dear Brothers,
I come to a scenario were one of our Windows 2008 R2 Server without Service Pack 1, was Flag under SCCM 2007 Reports Update Status for Service Pack 1 deployment to be "Not
Required" which definitely inaccurate.
What I want to know what are the conditions for the Software Update to send a status to SCCM Server that the Service Pack is “Not
Required” instead of the other way around?
Is there anyone that can guide me to any KB Article regarding this behavior?
Regards,

Yes, I know this is an old post, I’m trying to clean them up. Did you figure this out, if so how?
I have seen this before and what I have done is manually applied the SP1 to the server. Only then did the error show up as why SP1 didn’t apply. After fixing the error, CM was apply to apply SP1 and other SU to the server.
http://www.enhansoft.com/

Windows 2008 R2 Client computer backup files (*.dat) can't get restored after re-imaging the Windows 2008 R2 server

I have a Windows server 2008 R2 and I'm using backup feature to backup all computers in the network on it. Recently I ran into an issue and had to re-image my Windows 2008 R2 server and had to restore 2 of my client computers but now I can't restore
files from my client computer backups because they are not listed under Backups & Devices anymore however all backup files are still available on my Backup drive. How can I retrieve files from these backup files?

Anyone out there to help me with this issue?

Exchange Server 2013 server restarts automatically (The bugcheck was: 0x000000ef (0xffffe00000ee8080, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000)

Hi,
We have Exchange server 2013 restarting issue.(15.0.847.32)
Found The bugcheck was: 0x000000ef (0xffffe00000ee8080, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000) Event in the logs.
We have performed below steps but still same issue.
1. We have removed
Global Override for
ServiceHealthMSExchangeReplForceReboot responder (Reason for this as its not getting disabled)
2. Created Local Override and set the value to "0" (Disabled)
Server still restarting.

Hi,
I have followed above already the problem remain same.
I have disabled Microsoft Exchange Health
Manager Service to monitor till now issue not reported.
Is this best practice to disable the service in these kinds of issues or is there any other way?
Its a workaround that many have used yes.
However, having said that, its not something you want to leave in place.
I would suggest upgrading to at least CU6 or CU7 and if that does not resolve the issue, opening a support case with Microsoft.
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

When I try to print using Windows 2008 print server I have to use the generic print drivers supplied. If I use the OEM driver the printer locks up. I have tried a HP 4 plus and a Canon Copier.

When I try to print using Windows 2008 print server I have to use the generic print drivers supplied. If I use the OEM driver the printer locks up. I have tried a HP 4 plus and a Canon Copier.

A number of vendor drivers written for OS X cannot be used when connecting via SMB to a printer that is shared by Windows. This is due to limitations of the driver.
In some cases, if you were to enable the LPD Print Service in Windows, you can connect to the share using the same syntax as SMB but on the Mac you would use the LPD as the protocol.
If you can reply with the brand and model of printer you have then we may be able to provide more information.

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000007e (0xffffffff80000003, 0xfffff80001a8d016, 0xfffff880029eb788, 0xfffff880029eafe0). A dump was saved in: C:WindowsMEMORY.DMP. Report Id: .

I had the following issue on Windows Server 2008 R2 Enterprise. I want to know if it's relarted with a specific driver in orider to avoid this happend again.
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000007e (0xffffffff80000003, 0xfffff80001a8d016, 0xfffff880029eb788, 0xfffff880029eafe0). A dump was saved
in: C:WindowsMEMORY.DMP. Report Id: .
The dump is uploaded to the following skydrive link:
https://skydrive.live.com/?cid=FE2E04A1A3CB9D1D&id=FE2E04A1A3CB9D1D%21150
Please Could someone help me to know to witch is related?
Regards.
Juan.

thanks a lot for the answer!
the expeption code of the bugcheck is the following:
0x80000002: STATUS_DATATYPE_MISALIGNMENT indicates an unaligned data reference was encountered
I'm checking the drivers...maybe is related with some drivers installed in the system.
Is there any way to check the dump and confirm to witch driver is related?
Regards.
Juan.

Unable to login to Report Service on Windows 2008 R2 server

I have reporting services installed on a Windows 2008 R2 server, When I make and RDP connection to the server and go to http://servername/Reports everything works fine. When I try to connect from another client to the web service, it asks for username and
password. it fails 3 times and the shows a blank page.
When I see the Event Viewer in the server (Windows Logs --> Security, I can see an Audit Failure:
Log Name:      Security
Source:        Microsoft-Windows-Security-Auditing
Date:          9/4/2014 11:46:25 AM
Event ID:      4625
Task Category: Logon
Level:         Information
Keywords:      Audit Failure
User:          N/A
Computer:      MI-SWACO-DB.houston.livequest.net
Description:
An account failed to log on.
Subject:
   Security ID:       NULL SID
   Account Name:       -
   Account Domain:       -
   Logon ID:       0x0
Logon Type:           3
Account For Which Logon Failed:
   Security ID:       NULL SID
   Account Name:       Administrator
   Account Domain:       HOUSTONLQ
Failure Information:
   Failure Reason:       An Error occured during Logon.
   Status:           0xc000035b
   Sub Status:       0x0
Process Information:
   Caller Process ID:   0x0
   Caller Process Name:   -
Network Information:
   Workstation Name:   MI-SWACO3
   Source Network Address:   -
   Source Port:       -
Detailed Authentication Information:
   Logon Process:
   Authentication Package:   NTLM
   Transited Services:   -
   Package Name (NTLM only):   -
   Key Length:       0
This event is generated when a logon request fails. It is generated on the computer where access was attempted.
The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.
The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).
The Process Information fields indicate which account and process on the system requested the logon.
The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.
The authentication information fields provide detailed information about this specific logon request.
   - Transited services indicate which intermediate services have participated in this logon request.
   - Package name indicates which sub-protocol was used among the NTLM protocols.
   - Key length indicates the length of the generated session key. This will be 0 if no session key was requested.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="Microsoft-Windows-Security-Auditing" Guid="{54849625-5478-4994-A5BA-3E3B0328C30D}" />
    <EventID>4625</EventID>
    <Version>0</Version>
    <Level>0</Level>
    <Task>12544</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8010000000000000</Keywords>
    <TimeCreated SystemTime="2014-09-04T16:46:25.247229500Z" />
    <EventRecordID>8917</EventRecordID>
    <Correlation />
    <Execution ProcessID="504" ThreadID="1344" />
    <Channel>Security</Channel>
    <Computer>MI-SWACO-DB.houston.livequest.net</Computer>
    <Security />
</System>
<EventData>
    <Data Name="SubjectUserSid">S-1-0-0</Data>
    <Data Name="SubjectUserName">-</Data>
    <Data Name="SubjectDomainName">-</Data>
    <Data Name="SubjectLogonId">0x0</Data>
    <Data Name="TargetUserSid">S-1-0-0</Data>
    <Data Name="TargetUserName">Administrator</Data>
    <Data Name="TargetDomainName">HOUSTONLQ</Data>
    <Data Name="Status">0xc000035b</Data>
    <Data Name="FailureReason">%%2304</Data>
    <Data Name="SubStatus">0x0</Data>
    <Data Name="LogonType">3</Data>
    <Data Name="LogonProcessName">
    </Data>
    <Data Name="AuthenticationPackageName">NTLM</Data>
    <Data Name="WorkstationName">MI-SWACO3</Data>
    <Data Name="TransmittedServices">-</Data>
    <Data Name="LmPackageName">-</Data>
    <Data Name="KeyLength">0</Data>
    <Data Name="ProcessId">0x0</Data>
    <Data Name="ProcessName">-</Data>
    <Data Name="IpAddress">-</Data>
    <Data Name="IpPort">-</Data>
</EventData>
</Event>
The firewall is OFF in both client and server.
I saw a similar question and the answer is related to firewall which is not may case.

Hi Mario,
According to your description, when you try to access the Report Manager in another client, a login dialog prompt. After typing a valid username and password 3 times, a blank page displays.
Generally, the issue is always caused by the Report Server is configured to use Kerberos authentication, while the Service Principal Name(SPN) is not configured correctly. To fix this issue, please refer to the following methods:
Register an SPN for the Report Server service under the domain user account.
Change the service account to run under a built-in account such as Network Service.
Remove RSWindowsNegotiate and ensure RSWindowsNTLM is specified in the rsreportserver.config file.
Besides, the issue can also be caused by the Internet Explorer (IE) didn't pass the user's credential to the Report Server automatically or the IE is not Windows Integrated enabled. For more detail steps about how to address this issue, please refer to the
following steps:
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/184c4f6c-b292-4f9a-beca-80b70f4392fe/report-manager-prompts-3-or-4-times-for-usernamepassword-before-letting-users-in?forum=sqlreportingservices
Reference:
Resolving Kerberos Authentication Errors When Connecting to a Report Server
Solving the Reporting Services Login issue in the February CTP of SQL Server 2008
If there are any other questions, please feel free to ask.
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support

Solaris nis client can't connect to Windows 2008 NIS Server across subnets

I have been using Microsoft Windows Server for NIS for years to centralize some accounts accessing Solaris and Linux OS.
Windows 2003 R2 Indentity Management for UNIX version of Server for NIS was last working version with Solairs.
After upgrading Domain to Windows 2008 all Solaris clients that are on different subnets fail to bind and connect to NIS servers now.
These servers already were setup using ypinit -c to manually add the NIS servers to connect to and prior to Windows 2008 this worked.
Now no Solaris nis clients on different subnets (no firewall between) can connect , but other Unix/Linux OS connect fine.
Is this a known issue and can we get a resolution as it seems only Solaris is affected?

Hi Mid.Hudson-IT,
Before we begin ,we should ensure we have configured the printer server correctly .
Here is a link for reference of configuring the printer server .
Print server role: Configuring a print server
https://technet.microsoft.com/en-us/library/cc775791(v=ws.10).aspx
"I can map all of the printers on the network to the print server as-well as install the drivers correctly and I can resolve the IP and server name via DNS"
From this sentence ,I can`t figure out whether you have tried to ping the server both with the IP adress and name adress from the client ?
If we can ping the print server from the client,we can ensure the connection to the printer server is good .
Then we can try to install the printer driver directly to have a check .In the adress bar of Windows Explorer ,input "\\server name \the printer name"
If we cannot ping the print server ,we should troubleshoot the network issue firstly.
We also can check the event viewer for more information to troubleshoot this issue .
Best regards

Moving SAP Content Server/MaxDB 7.6 to a Windows 2008 R2 Server

Hi All.
We are in the process of upgrading our server where the SAP content server is located. We are going from SAP CS 6.30/MaxDB 7.6 to a Windows 2008 R2 server where we want to install SAP CS 6.40/MaxDB 7.8. I have been following the latest manual from SAP for upgrading to MaxDb 7.8 (2010-10-05) from MaxDb 7.6 using the in-place method.
To date we have installed MaxDB 7.6 on the server. We restored our latest backup and performed the index checks as spelled out in the manual. I have the database in ADMIN mode and went to run the MaxDb 7.8 install for the 64 bit window version. THe install GUI comes up, but the Update selection is grayed out. This tells me that the install program can not detect our existing database. I did make sure I was running the install as Admim so I do not think that is the issue.
This is the second time I have tried this upgrade. The first time I did a comand line upgrade by runing the .bat file DBUPDATE.bat. We have a 110 Gbyte database and this upgrade ran in about 15 minutes, and of course when I went to openthe database it was toast. Do not want to make the same mistake again.
One other point, since we did a restore of the database, then the index check, we did not run a backup as the manual suggested as we felt it was not necessary. Does the system require a backup before upgrade and that is why it does not see the database?
Any assistance will be greatly appreciated.

I beleive we have resolved the issue with upgrading the database, but now we are having a problem with Datbase Studio 7.8. Before the upgrade we used Data Manager 7.6. After the upgrade we installed Database Studio 7.8 and when we go to start it up, we are getting the Problems opening perspective 'com.sap.sdb.tools.ut.perspectives.mainPerspective'. I followed the instruction in another post Problems opening perspective in Database Studio, but we still are getting the error.
Can anybody offer any assistance as we are getting close to the weekend when we want to do the cutover and we are not even done with our first pass at upgrading the SAP content server.
Thanks
John

Windows 2008 R2 Server not showing update history and not detecting new updates

Hi Sirs,
We have a Windows 2008 R2 server which is showing an empty windows update history, and is not detecting new updates from the WSUS server. It says that the windows is up to date, no error when trying to detect new updates, but I doubt it because when I checked
the installed updates menu, it shows that that the most recent update date installed was last 2013, it just stop detecting and installing updates. I've already tried the ff workarounds but to no avail:
1. restart wuauserv and bits service
2. rename/delete the software distribution folder
3. reinstalled the update agent/restarted the server
4. deleted the susclientid on the registry
Thanks in advanced for your help.
here's the windowsupdate.log:
2014-07-22   00:57:06:728   928   a34   AU   #############
2014-07-22   00:57:06:728   928   a34   AU   Successfully wrote event for AU health state:0
2014-07-22   00:57:06:728   928   a34   AU   Featured notifications is disabled.
2014-07-22   00:57:06:728   928   a34   AU   AU setting next detection timeout to 2014-07-21 20:50:56
2014-07-22   00:57:06:728   928   a34   AU   Successfully wrote event for AU health state:0
2014-07-22   00:57:06:728   928   a34   AU   Successfully wrote event for AU health state:0
2014-07-22   00:57:11:727   928   abc   Report   REPORT EVENT: {AF0753F1-F6F9-4583-87B0-A0B0AEA0C6A7}   2014-07-22 00:57:06:728+0800   1
147   101   {00000000-0000-0000-0000-000000000000}   0   0   AutomaticUpdates   Success   Software Synchronization   Windows
Update Client successfully detected 0 updates.
2014-07-22   00:57:11:727   928   abc   Report   REPORT EVENT: {188957AA-577F-4DC5-9CDB-2D8CFEE96670}   2014-07-22 00:57:06:728+0800   1
156   101   {00000000-0000-0000-0000-000000000000}   0   0   AutomaticUpdates   Success   Pre-Deployment Check   Reporting
client status.
2014-07-22   00:57:11:727   928   abc   Report   CWERReporter finishing event handling. (00000000)
2014-07-22   01:11:10:931   928   abc   Report   Uploading 2 events using cached cookie, reporting URL = http://mtp-wsus2/ReportingWebService/ReportingWebService.asmx
2014-07-22   01:11:10:947   928   abc   Report   Reporter successfully uploaded 2 events.
2014-07-22   04:50:56:736   928   1130   AU   #############
2014-07-22   04:50:56:736   928   1130   AU   ## START ## AU: Search for updates
2014-07-22   04:50:56:736   928   1130   AU   #########
2014-07-22   04:50:56:736   928   1130   AU   <<## SUBMITTED ## AU: Search for updates [CallId = {F40B494F-91F1-4FFB-B7A5-46CEA397AA52}]
2014-07-22   04:50:56:736   928   d08   Agent   *************
2014-07-22   04:50:56:736   928   d08   Agent   ** START ** Agent: Finding updates [CallerId = AutomaticUpdates]
2014-07-22   04:50:56:736   928   d08   Agent   *********
2014-07-22   04:50:56:736   928   d08   Agent      * Online = Yes; Ignore download priority = No
2014-07-22   04:50:56:736   928   d08   Agent      * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation'
or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
2014-07-22   04:50:56:736   928   d08   Agent      * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
2014-07-22   04:50:56:736   928   d08   Agent      * Search Scope = {Machine}
2014-07-22   04:50:57:017   928   d08   Setup   Checking for agent SelfUpdate
2014-07-22   04:50:57:017   928   d08   Setup   Client version: Core: 7.6.7600.256 Aux: 7.6.7600.256
2014-07-22   04:50:57:017   928   d08   Misc   Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2014-07-22   04:50:57:017   928   d08   Misc   Microsoft signed: Yes
2014-07-22   04:50:59:611   928   d08   Misc   Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2014-07-22   04:50:59:611   928   d08   Misc   Microsoft signed: Yes
2014-07-22   04:50:59:611   928   d08   Misc   Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2014-07-22   04:50:59:611   928   d08   Misc   Microsoft signed: Yes
2014-07-22   04:50:59:626   928   d08   Misc   Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2014-07-22   04:50:59:626   928   d08   Misc   Microsoft signed: Yes
2014-07-22   04:50:59:626   928   d08   Setup   Determining whether a new setup handler needs to be downloaded
2014-07-22   04:50:59:626   928   d08   Setup   SelfUpdate handler is not found. It will be downloaded
2014-07-22   04:50:59:626   928   d08   Setup   Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256"
2014-07-22   04:51:01:095   928   d08   Setup   Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
2014-07-22   04:51:01:095   928   d08   Setup   Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256"
2014-07-22   04:51:01:110   928   d08   Setup   Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
2014-07-22   04:51:01:110   928   d08   Setup   Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256"
2014-07-22   04:51:01:142   928   d08   Setup   Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
2014-07-22   04:51:01:142   928   d08   Setup   SelfUpdate check completed. SelfUpdate is NOT required.
2014-07-22   04:51:01:860   928   d08   PT   +++++++++++ PT: Synchronizing server updates +++++++++++
2014-07-22   04:51:01:860   928   d08   PT      + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://mtp-wsus2/ClientWebService/client.asmx
2014-07-22   04:51:01:891   928   d08   PT   WARNING: Cached cookie has expired or new PID is available
2014-07-22   04:51:01:891   928   d08   PT   Initializing simple targeting cookie, clientId = 487b95fe-31a4-44f7-9989-bd77766ce5fa, target group = , DNS name = itg-soatrainsvr.mbtc.mgc.local
2014-07-22   04:51:01:891   928   d08   PT      Server URL = http://mtp-wsus2/SimpleAuthWebService/SimpleAuth.asmx
2014-07-22   04:51:04:485   928   d08   PT   +++++++++++ PT: Synchronizing extended update info +++++++++++
2014-07-22   04:51:04:485   928   d08   PT      + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://mtp-wsus2/ClientWebService/client.asmx
2014-07-22   04:51:04:875   928   d08   Agent      * Found 0 updates and 68 categories in search; evaluated appl. rules of 503 out of 777 deployed entities
2014-07-22   04:51:04:875   928   d08   Agent   *********
2014-07-22   04:51:04:875   928   d08   Agent   ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]
2014-07-22   04:51:04:875   928   d08   Agent   *************
2014-07-22   04:51:04:875   928   1278   AU   >>## RESUMED ## AU: Search for updates [CallId = {F40B494F-91F1-4FFB-B7A5-46CEA397AA52}]
2014-07-22   04:51:04:875   928   1278   AU      # 0 updates detected
2014-07-22   04:51:04:875   928   1278   AU   #########
2014-07-22   04:51:04:875   928   1278   AU   ## END ## AU: Search for updates [CallId = {F40B494F-91F1-4FFB-B7A5-46CEA397AA52}]
2014-07-22   04:51:04:875   928   1278   AU   #############
2014-07-22   04:51:04:875   928   1278   AU   Successfully wrote event for AU health state:0
2014-07-22   04:51:04:875   928   1278   AU   Featured notifications is disabled.
2014-07-22   04:51:04:875   928   1278   AU   AU setting next detection timeout to 2014-07-22 00:38:28
2014-07-22   04:51:04:875   928   1278   AU   Successfully wrote event for AU health state:0
2014-07-22   04:51:04:875   928   1278   AU   Successfully wrote event for AU health state:0
2014-07-22   04:51:09:874   928   d08   Report   REPORT EVENT: {FE398C01-75A1-4AD8-8C43-0894FCFCE13F}   2014-07-22 04:51:04:875+0800   1
147   101   {00000000-0000-0000-0000-000000000000}   0   0   AutomaticUpdates   Success   Software Synchronization   Windows
Update Client successfully detected 0 updates.
2014-07-22   04:51:09:874   928   d08   Report   REPORT EVENT: {CDA386AD-6392-4C34-859E-35307BCB5EA0}   2014-07-22 04:51:04:875+0800   1
156   101   {00000000-0000-0000-0000-000000000000}   0   0   AutomaticUpdates   Success   Pre-Deployment Check   Reporting
client status.
2014-07-22   04:51:09:874   928   d08   Report   CWERReporter finishing event handling. (00000000)
2014-07-22   05:05:09:109   928   d08   Report   Uploading 2 events using cached cookie, reporting URL = http://mtp-wsus2/ReportingWebService/ReportingWebService.asmx
2014-07-22   05:05:09:109   928   d08   Report   Reporter successfully uploaded 2 events.
2014-07-22   08:38:28:883   928   1130   AU   #############
2014-07-22   08:38:28:883   928   1130   AU   ## START ## AU: Search for updates
2014-07-22   08:38:28:883   928   1130   AU   #########
2014-07-22   08:38:28:883   928   1130   AU   <<## SUBMITTED ## AU: Search for updates [CallId = {9A097F9F-88DD-4037-A4DD-48B9CC891327}]
2014-07-22   08:38:28:883   928   53c   Agent   *************
2014-07-22   08:38:28:883   928   53c   Agent   ** START ** Agent: Finding updates [CallerId = AutomaticUpdates]
2014-07-22   08:38:28:883   928   53c   Agent   *********
2014-07-22   08:38:28:883   928   53c   Agent      * Online = Yes; Ignore download priority = No
2014-07-22   08:38:28:883   928   53c   Agent      * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation'
or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
2014-07-22   08:38:28:883   928   53c   Agent      * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
2014-07-22   08:38:28:883   928   53c   Agent      * Search Scope = {Machine}
2014-07-22   08:38:29:195   928   53c   Setup   Checking for agent SelfUpdate
2014-07-22   08:38:29:195   928   53c   Setup   Client version: Core: 7.6.7600.256 Aux: 7.6.7600.256
2014-07-22   08:38:29:195   928   53c   Misc   Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2014-07-22   08:38:29:195   928   53c   Misc   Microsoft signed: Yes
2014-07-22   08:38:31:804   928   53c   Misc   Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2014-07-22   08:38:31:804   928   53c   Misc   Microsoft signed: Yes
2014-07-22   08:38:31:804   928   53c   Misc   Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2014-07-22   08:38:31:820   928   53c   Misc   Microsoft signed: Yes
2014-07-22   08:38:31:820   928   53c   Misc   Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2014-07-22   08:38:31:820   928   53c   Misc   Microsoft signed: Yes
2014-07-22   08:38:31:835   928   53c   Setup   Determining whether a new setup handler needs to be downloaded
2014-07-22   08:38:31:835   928   53c   Setup   SelfUpdate handler is not found. It will be downloaded
2014-07-22   08:38:31:835   928   53c   Setup   Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256"
2014-07-22   08:38:33:241   928   53c   Setup   Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
2014-07-22   08:38:33:241   928   53c   Setup   Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256"
2014-07-22   08:38:33:272   928   53c   Setup   Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
2014-07-22   08:38:33:272   928   53c   Setup   Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256"
2014-07-22   08:38:33:288   928   53c   Setup   Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
2014-07-22   08:38:33:288   928   53c   Setup   SelfUpdate check completed. SelfUpdate is NOT required.
2014-07-22   08:38:33:991   928   53c   PT   +++++++++++ PT: Synchronizing server updates +++++++++++
2014-07-22   08:38:33:991   928   53c   PT      + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://mtp-wsus2/ClientWebService/client.asmx
2014-07-22   08:38:34:038   928   53c   PT   WARNING: Cached cookie has expired or new PID is available
2014-07-22   08:38:34:038   928   53c   PT   Initializing simple targeting cookie, clientId = 487b95fe-31a4-44f7-9989-bd77766ce5fa, target group = , DNS name = itg-soatrainsvr.mbtc.mgc.local
2014-07-22   08:38:34:038   928   53c   PT      Server URL = http://mtp-wsus2/SimpleAuthWebService/SimpleAuth.asmx
2014-07-22   08:38:36:616   928   53c   PT   +++++++++++ PT: Synchronizing extended update info +++++++++++
2014-07-22   08:38:36:616   928   53c   PT      + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://mtp-wsus2/ClientWebService/client.asmx
2014-07-22   08:38:37:022   928   53c   Agent      * Found 0 updates and 68 categories in search; evaluated appl. rules of 503 out of 777 deployed entities
2014-07-22   08:38:37:022   928   53c   Agent   *********
2014-07-22   08:38:37:022   928   53c   Agent   ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]
2014-07-22   08:38:37:022   928   53c   Agent   *************
2014-07-22   08:38:37:022   928   aa8   AU   >>## RESUMED ## AU: Search for updates [CallId = {9A097F9F-88DD-4037-A4DD-48B9CC891327}]
2014-07-22   08:38:37:022   928   aa8   AU      # 0 updates detected
2014-07-22   08:38:37:022   928   aa8   AU   #########
2014-07-22   08:38:37:022   928   aa8   AU   ## END ## AU: Search for updates [CallId = {9A097F9F-88DD-4037-A4DD-48B9CC891327}]
2014-07-22   08:38:37:022   928   aa8   AU   #############
2014-07-22   08:38:37:022   928   aa8   AU   Successfully wrote event for AU health state:0
2014-07-22   08:38:37:022   928   aa8   AU   Featured notifications is disabled.
2014-07-22   08:38:37:022   928   aa8   AU   AU setting next detection timeout to 2014-07-22 04:15:53
2014-07-22   08:38:37:022   928   aa8   AU   Successfully wrote event for AU health state:0
2014-07-22   08:38:37:022   928   aa8   AU   Successfully wrote event for AU health state:0
2014-07-22   08:38:42:021   928   53c   Report   REPORT EVENT: {45B5AD35-C612-4C43-8FE0-DFC63B114FC9}   2014-07-22 08:38:37:022+0800   1
147   101   {00000000-0000-0000-0000-000000000000}   0   0   AutomaticUpdates   Success   Software Synchronization   Windows
Update Client successfully detected 0 updates.
2014-07-22   08:38:42:021   928   53c   Report   REPORT EVENT: {BA606714-0153-41BA-ADC8-78520F678D97}   2014-07-22 08:38:37:022+0800   1
156   101   {00000000-0000-0000-0000-000000000000}   0   0   AutomaticUpdates   Success   Pre-Deployment Check   Reporting
client status.
2014-07-22   08:38:42:021   928   53c   Report   CWERReporter finishing event handling. (00000000)
2014-07-22   08:52:41:224   928   53c   Report   Uploading 2 events using cached cookie, reporting URL = http://mtp-wsus2/ReportingWebService/ReportingWebService.asmx
2014-07-22   08:52:41:240   928   53c   Report   Reporter successfully uploaded 2 events.
2014-07-22   12:15:53:027   928   1130   AU   #############
2014-07-22   12:15:53:027   928   1130   AU   ## START ## AU: Search for updates
2014-07-22   12:15:53:027   928   1130   AU   #########
2014-07-22   12:15:53:027   928   1130   AU   <<## SUBMITTED ## AU: Search for updates [CallId = {9BDC1D71-5139-49D4-88F0-E2B639CE8846}]
2014-07-22   12:15:53:043   928   a58   Agent   *************
2014-07-22   12:15:53:043   928   a58   Agent   ** START ** Agent: Finding updates [CallerId = AutomaticUpdates]
2014-07-22   12:15:53:043   928   a58   Agent   *********
2014-07-22   12:15:53:043   928   a58   Agent      * Online = Yes; Ignore download priority = No
2014-07-22   12:15:53:043   928   a58   Agent      * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation'
or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
2014-07-22   12:15:53:043   928   a58   Agent      * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
2014-07-22   12:15:53:043   928   a58   Agent      * Search Scope = {Machine}
2014-07-22   12:15:53:308   928   a58   Setup   Checking for agent SelfUpdate
2014-07-22   12:15:53:308   928   a58   Setup   Client version: Core: 7.6.7600.256 Aux: 7.6.7600.256
2014-07-22   12:15:53:308   928   a58   Misc   Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2014-07-22   12:15:53:324   928   a58   Misc   Microsoft signed: Yes
2014-07-22   12:15:55:901   928   a58   Misc   Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2014-07-22   12:15:55:901   928   a58   Misc   Microsoft signed: Yes
2014-07-22   12:15:55:901   928   a58   Misc   Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2014-07-22   12:15:55:917   928   a58   Misc   Microsoft signed: Yes
2014-07-22   12:15:55:917   928   a58   Misc   Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2014-07-22   12:15:55:917   928   a58   Misc   Microsoft signed: Yes
2014-07-22   12:15:55:933   928   a58   Setup   Determining whether a new setup handler needs to be downloaded
2014-07-22   12:15:55:933   928   a58   Setup   SelfUpdate handler is not found. It will be downloaded
2014-07-22   12:15:55:933   928   a58   Setup   Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256"
2014-07-22   12:15:57:167   928   a58   Setup   Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
2014-07-22   12:15:57:167   928   a58   Setup   Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256"
2014-07-22   12:15:57:167   928   a58   Setup   Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
2014-07-22   12:15:57:167   928   a58   Setup   Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256"
2014-07-22   12:15:57:198   928   a58   Setup   Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
2014-07-22   12:15:57:198   928   a58   Setup   SelfUpdate check completed. SelfUpdate is NOT required.
2014-07-22   12:15:57:917   928   a58   PT   +++++++++++ PT: Synchronizing server updates +++++++++++
2014-07-22   12:15:57:917   928   a58   PT      + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://mtp-wsus2/ClientWebService/client.asmx
2014-07-22   12:15:57:963   928   a58   PT   WARNING: Cached cookie has expired or new PID is available
2014-07-22   12:15:57:963   928   a58   PT   Initializing simple targeting cookie, clientId = 487b95fe-31a4-44f7-9989-bd77766ce5fa, target group = , DNS name = itg-soatrainsvr.mbtc.mgc.local
2014-07-22   12:15:57:963   928   a58   PT      Server URL = http://mtp-wsus2/SimpleAuthWebService/SimpleAuth.asmx
2014-07-22   12:16:00:572   928   a58   PT   +++++++++++ PT: Synchronizing extended update info +++++++++++
2014-07-22   12:16:00:572   928   a58   PT      + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://mtp-wsus2/ClientWebService/client.asmx
2014-07-22   12:16:00:932   928   a58   Agent      * Found 0 updates and 68 categories in search; evaluated appl. rules of 503 out of 777 deployed entities
2014-07-22   12:16:00:932   928   a58   Agent   *********
2014-07-22   12:16:00:932   928   a58   Agent   ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]
2014-07-22   12:16:00:932   928   a58   Agent   *************
2014-07-22   12:16:00:932   928   1120   AU   >>## RESUMED ## AU: Search for updates [CallId = {9BDC1D71-5139-49D4-88F0-E2B639CE8846}]
2014-07-22   12:16:00:932   928   1120   AU      # 0 updates detected
2014-07-22   12:16:00:932   928   1120   AU   #########
2014-07-22   12:16:00:932   928   1120   AU   ## END ## AU: Search for updates [CallId = {9BDC1D71-5139-49D4-88F0-E2B639CE8846}]
2014-07-22   12:16:00:932   928   1120   AU   #############
2014-07-22   12:16:00:932   928   1120   AU   Successfully wrote event for AU health state:0
2014-07-22   12:16:00:932   928   1120   AU   Featured notifications is disabled.
2014-07-22   12:16:00:932   928   1120   AU   AU setting next detection timeout to 2014-07-22 08:15:22
2014-07-22   12:16:00:932   928   1120   AU   Successfully wrote event for AU health state:0
2014-07-22   12:16:00:932   928   1120   AU   Successfully wrote event for AU health state:0
2014-07-22   12:16:05:931   928   a58   Report   REPORT EVENT: {25E75367-1205-4F59-A812-02DA28BB3234}   2014-07-22 12:16:00:932+0800   1
147   101   {00000000-0000-0000-0000-000000000000}   0   0   AutomaticUpdates   Success   Software Synchronization   Windows
Update Client successfully detected 0 updates.
2014-07-22   12:16:05:931   928   a58   Report   REPORT EVENT: {FE1434F8-C6AF-4F87-B3DF-6E4D6C4B05FB}   2014-07-22 12:16:00:932+0800   1
156   101   {00000000-0000-0000-0000-000000000000}   0   0   AutomaticUpdates   Success   Pre-Deployment Check   Reporting
client status.
2014-07-22   12:16:05:931   928   a58   Report   CWERReporter finishing event handling. (00000000)
2014-07-22   12:30:05:116   928   a58   Report   Uploading 2 events using cached cookie, reporting URL = http://mtp-wsus2/ReportingWebService/ReportingWebService.asmx
2014-07-22   12:30:05:131   928   a58   Report   Reporter successfully uploaded 2 events.
2014-07-22   14:05:29:584   928   10a0   AU   Triggering AU detection through DetectNow API
2014-07-22   14:05:29:584   928   10a0   AU   Triggering Online detection (interactive)
2014-07-22   14:05:29:584   928   1130   AU   #############
2014-07-22   14:05:29:584   928   1130   AU   ## START ## AU: Search for updates
2014-07-22   14:05:29:584   928   1130   AU   #########
2014-07-22   14:05:29:584   928   1130   AU   <<## SUBMITTED ## AU: Search for updates [CallId = {CC67CC44-7DFB-49DE-AA83-8D6A7995ABFA}]
2014-07-22   14:05:29:584   928   8e0   Agent   *************
2014-07-22   14:05:29:584   928   8e0   Agent   ** START ** Agent: Finding updates [CallerId = AutomaticUpdates]
2014-07-22   14:05:29:584   928   8e0   Agent   *********
2014-07-22   14:05:29:584   928   8e0   Agent      * Online = Yes; Ignore download priority = No
2014-07-22   14:05:29:584   928   8e0   Agent      * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation'
or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
2014-07-22   14:05:29:584   928   8e0   Agent      * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
2014-07-22   14:05:29:584   928   8e0   Agent      * Search Scope = {Machine}
2014-07-22   14:05:29:584   928   8e0   Setup   Checking for agent SelfUpdate
2014-07-22   14:05:29:584   928   8e0   Setup   Client version: Core: 7.6.7600.256 Aux: 7.6.7600.256
2014-07-22   14:05:29:584   928   8e0   Misc   Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2014-07-22   14:05:29:600   928   8e0   Misc   Microsoft signed: Yes
2014-07-22   14:05:29:616   928   8e0   Misc   Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2014-07-22   14:05:29:631   928   8e0   Misc   Microsoft signed: Yes
2014-07-22   14:05:29:631   928   8e0   Misc   Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2014-07-22   14:05:29:631   928   8e0   Misc   Microsoft signed: Yes
2014-07-22   14:05:29:647   928   8e0   Misc   Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2014-07-22   14:05:29:662   928   8e0   Misc   Microsoft signed: Yes
2014-07-22   14:05:29:662   928   8e0   Setup   Determining whether a new setup handler needs to be downloaded
2014-07-22   14:05:29:662   928   8e0   Setup   SelfUpdate handler is not found. It will be downloaded
2014-07-22   14:05:29:662   928   8e0   Setup   Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256"
2014-07-22   14:05:29:662   928   8e0   Setup   Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
2014-07-22   14:05:29:662   928   8e0   Setup   Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256"
2014-07-22   14:05:29:694   928   8e0   Setup   Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
2014-07-22   14:05:29:694   928   8e0   Setup   Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256"
2014-07-22   14:05:29:709   928   8e0   Setup   Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
2014-07-22   14:05:29:725   928   8e0   Setup   SelfUpdate check completed. SelfUpdate is NOT required.
2014-07-22   14:05:30:037   928   8e0   PT   +++++++++++ PT: Synchronizing server updates +++++++++++
2014-07-22   14:05:30:037   928   8e0   PT      + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://mtp-wsus2/ClientWebService/client.asmx
2014-07-22   14:05:30:053   928   8e0   PT   WARNING: Cached cookie has expired or new PID is available
2014-07-22   14:05:30:053   928   8e0   PT   Initializing simple targeting cookie, clientId = 487b95fe-31a4-44f7-9989-bd77766ce5fa, target group = , DNS name = itg-soatrainsvr.mbtc.mgc.local
2014-07-22   14:05:30:053   928   8e0   PT      Server URL = http://mtp-wsus2/SimpleAuthWebService/SimpleAuth.asmx
2014-07-22   14:05:35:630   928   8e0   PT   +++++++++++ PT: Synchronizing extended update info +++++++++++
2014-07-22   14:05:35:630   928   8e0   PT      + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://mtp-wsus2/ClientWebService/client.asmx
2014-07-22   14:05:36:411   928   8e0   Agent      * Found 0 updates and 68 categories in search; evaluated appl. rules of 503 out of 777 deployed entities
2014-07-22   14:05:36:411   928   8e0   Agent   *********
2014-07-22   14:05:36:411   928   8e0   Agent   ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]
2014-07-22   14:05:36:411   928   8e0   Agent   *************
2014-07-22   14:05:36:411   928   1360   AU   >>## RESUMED ## AU: Search for updates [CallId = {CC67CC44-7DFB-49DE-AA83-8D6A7995ABFA}]
2014-07-22   14:05:36:411   928   1360   AU      # 0 updates detected
2014-07-22   14:05:36:411   928   1360   AU   #########
2014-07-22   14:05:36:411   928   1360   AU   ## END ## AU: Search for updates [CallId = {CC67CC44-7DFB-49DE-AA83-8D6A7995ABFA}]
2014-07-22   14:05:36:411   928   1360   AU   #############
2014-07-22   14:05:36:411   928   1360   AU   Successfully wrote event for AU health state:0
2014-07-22   14:05:36:411   928   1360   AU   Featured notifications is disabled.
2014-07-22   14:05:36:411   928   1360   AU   AU setting next detection timeout to 2014-07-22 10:01:01
2014-07-22   14:05:36:411   928   1360   AU   Successfully wrote event for AU health state:0
2014-07-22   14:05:36:411   928   1360   AU   Successfully wrote event for AU health state:0
2014-07-22   14:05:41:410   928   8e0   Report   REPORT EVENT: {6A2B180E-A95F-42F7-B775-5750DFFD6ECD}   2014-07-22 14:05:36:411+0800   1
147   101   {00000000-0000-0000-0000-000000000000}   0   0   AutomaticUpdates   Success   Software Synchronization   Windows
Update Client successfully detected 0 updates.
2014-07-22   14:05:41:410   928   8e0   Report   REPORT EVENT: {83041427-693D-4A42-AED0-E8E7BFB8E7E3}   2014-07-22 14:05:36:411+0800   1
156   101   {00000000-0000-0000-0000-000000000000}   0   0   AutomaticUpdates   Success   Pre-Deployment Check   Reporting
client status.
2014-07-22   14:05:41:410   928   8e0   Report   CWERReporter finishing event handling. (00000000)

No Service Pack 1 installed. Does this mean that no updates will be detected if SP1 is not installed? thanks
That's exactly what that means!
Updates have not been available for Windows Server 2008 R2 *RTM* systems since April, 2013.
http://support.microsoft.com/lifecycle/?p1=14134
Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

Windows 2008 R2 server BSOD; The bugcheck was: 0x0000001e (0xffffffffc0000005, 0xfffff88002b89950, 0x0000000000000000, 0x0000000000000000)

Similar Messages

Maybe you are looking for