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

Similar Messages

Problems using SQL Server 2014 upgrade advisor on a windows 2008 sp2 server

I got sql server 2014 upgrade advisor up and running on a windows 2012 vm and every thing works fine, but I am having trouble installing it locally for a SSRS Box. The SSRS box is running windows 2008 sp2 enterprise edition, but when I try
and run the SQLUA.msi install nothing happens.
anyone else experience this issue?

Hi jesse,
Welcome to the forum :-)
Can you please clarify your issue in more details. I did not understand what you are doing. What do you mean by "installing it locally for a SSRS Box". Do you mean that you are trying a simple installation which do not work, and raise an error?
If so then (1) we dont need the extra information about "why you need the SQL Server" :-) we just need to help you install it regardless the SSRS. (2) We do need the full error log and the error message that you get.
By the way, The SQLUA.msi is just a small utilities named "Upgrade Advisor"
http://msdn.microsoft.com/en-us/library/ms144256.aspx
Do you want to install the SQL Server itself?
What is your current SQL Server on the local windows 2008 server?
[Personal Site] [Blog] [Facebook]

SAP Sybase ASE 15.7 DB error on Windows 2008 R2 Server

Hello SAP Gurus !
We are in process of Installing SAP ASE 15.7 DB on win 2008 R2 64bit. When i Run setup file on ASE folder and after following the required screen at the last phase it comes out throwing error saying New Adaptive service unable to create?.
We tried all the options but no luck, Can anyone in this group help me out of it, Your early reply really appreciated.
Thanks -
Amjad

Hi Amjad,
Please check whether below components are installed on Windows sever.
Microsoft Visual C++ 2010 Service Pack 1 Redistributable Package and KB2565063
Microsoft Visual Studio 2010 Service Pack 1 and KB2565057
If not please do so and check the results.
Secondly which path level of ASE do you have ?
You may refer some known installation issues on link
SyBooks Online
Hope this helps.
Regards,
Deepak Kori

SAP support Windows 2008 x64 server

Hi,
SAP 2007 supports the Windows 2008 x64 server? If support, what I need to do to run the sap add on at this Server.
Please give me any suggestiong.
Thanks and regards,
Lei Nandar Myint

Hi,
You may check this link: https://websmp203.sap-ag.de/smb/sbo/platforms (S-Number logon)
Regards, Yatsea

SAPSprint installation on Windows 2008 R2 Server 64-bit

Dear Gurus,
as we change our print server to Windows 2008 R2 Server 64-bit I need to install SAPSprint for SAP printing with connection type 'S' out of a NW7.0 based system on HP-UX.
Till now we used SAPlpd on a 32-bit Windows Server......
1) Do I simply need to install the xSPrint.exe or can this happen only in combination with the whole SAPGui?
2) According to note 66971 for Windows 2008 R2 Server 64-bit only SAPGui 7.20 is supported.
Does this mean that I also have to use SAPSprint release 7.20 or can I use any other release as well.
On our Windows clients we run SAPGui 7.10.
Is there any correlation between the SAPGui running on the clients and the SAPGui / SAPSprint release running on the print server or can I simply install the highest SAPSprint release 7.20 on the print server to be sure that it will work with WK8 R2 64-bit?
I hope I could explain my problem and I am looking forward to your reply.
Thanks a lot in advance!
Günter

Dear Günter.
Your question is spread over some different areas. Let me point out some tracks to follow:
There is only a 32-bit version of SAPSprint but that one works also under 64-bit; please refer to SAP note 894444.
Regarding SAPgui, in general it is recommended to have the last version as it is downwards-compatible with older versions.
But specially, let me highlight that Windows 2008 R2 is not yet listed in the PAM - and hence not yet supported. The technical prerequisites are met (with a special kernel patch) but not all software is released.
In fact, and just to provide you further details it is not possible to expect the 710 products released for Windows Server 2008 R2 before around four weeks; 700 products will be released even after 710.
See SAP note 1383873 ("Windows Server 2008 R2 Support").
You can be always up to date with the latest Windows news at:
--> Support of Microsoft Windows Server 2008 R2
Cheers!

Installing CR VS2010 on Windows 2008 Core Server

Hello,
We are attempting to re-build our web servers and reduce their footprint. In this effort we have chosen to use Windows 2008 Core Server with all of the web server installation features. In addition we upgraded our application to CR for VS2010 after finding that it supported Windows Server 2008. However, while trying to deploy the MSI packages to the server we are encountering the following error.
MSI PACKAGE
CRRuntime_32bit_13_0_1.msi
ERROR
Error 1904. Modeule C:\Program Files (x86)\SAP BusinessObjects\Crystal Reports for .NET Framework 4.0\Common\SAP BusinessObjects Enterprise XI 4.0\win32_x86\pageobjectmodel.dll failed to register. HRESULT -2147024770
SYSTEM INFORMATION
OS Name:                   Microsoft Windows Server 2008 R2 Standard
OS Version:                6.1.7601 Service Pack 1 Build 7601
OS Manufacturer:           Microsoft Corporation
OS Configuration:          Member Server
OS Build Type:             Multiprocessor Free
Registered Owner:          Windows User
Registered Organization:
Product ID:                00477-001-0000421-84205
Original Install Date:     4/27/2011, 10:12:31 AM
System Boot Time:          9/27/2011, 9:47:41 AM
System Manufacturer:       Microsoft Corporation
System Model:              Virtual Machine
System Type:               x64-based PC
Processor(s):              1 Processor(s) Installed.
                           [01]: Intel64 Family 6 Model 44 Stepping 2 GenuineInt
el ~3058 Mhz
BIOS Version:              American Megatrends Inc. 090004 , 3/19/2009
Windows Directory:         C:\Windows
System Directory:          C:\Windows\system32
Boot Device:               \Device\HarddiskVolume4
System Locale:             en-us;English (United States)
Input Locale:              en-us;English (United States)
Time Zone:                 (UTC-08:00) Pacific Time (US & Canada)
Total Physical Memory:     1,536 MB
Available Physical Memory: 1,031 MB
Virtual Memory: Max Size: 3,840 MB
Virtual Memory: Available: 3,316 MB
Virtual Memory: In Use:    524 MB
Hotfix(s):                 32 Hotfix(s) Installed.
                           [01]: KB2425227
                           [02]: KB2446710
                           [03]: KB2476490
                           [04]: KB2478662
                           [05]: KB2503665
                           [06]: KB2506014
                           [07]: KB2506212
                           [08]: KB2506223
                           [09]: KB2507618
                           [10]: KB2507938
                           [11]: KB2508429
                           [12]: KB2509553
                           [13]: KB2510531
                           [14]: KB2511455
                           [15]: KB2518869
                           [16]: KB2524375
                           [17]: KB2525694
                           [18]: KB2533552
                           [19]: KB2534366
                           [20]: KB2536275
                           [21]: KB2536276
                           [22]: KB2539635
                           [23]: KB2552343
                           [24]: KB2555917
                           [25]: KB2556532
                           [26]: KB2560656
                           [27]: KB2563894
                           [28]: KB2567680
                           [29]: KB2570791
                           [30]: KB2570947
                           [31]: KB2616676
                           [32]: KB976902
INSTALLED PACKAGES
Name=Microsoft ASP.NET 2.0 AJAX Extensions 1.0
Name=SolarWinds Log Forwarder for Windows
Name=Microsoft Visual C++ 2005 Redistributable
Name=Microsoft Visual C++ 2008 Redistributable - x86 9.0.21022
Name=Microsoft .NET Framework 4 Extended
Name=Microsoft .NET Framework 4 Client Profile
Any insight you can provide on the issue would be appreciated.
Thanks,
Phil

The DLLS that fail to register are:
pageobjectmodel.dll
reportrenderer.dll
PageObjectModel.dll is missing the following dependencies:
MSVCR80.DLL
OLEDLG.DLL
DEVMGR.DLL
EFSADU.DLL
NETPLWIZ.DLL
RASAPI32.DLL
RASDLG.DLL
SHDOCVW.DLL
TAPI32.DLL
ReportRenderer.dll is missing the following dependencies:
MSVCR80.DLL
OLEDLG.DLL
DEVMGR.DLL
EFSADU.DLL
NETPLWIZ.DLL
RASAPI32.DLL
RASDLG.DLL
SHDOCVW.DLL
TAPI32.DLL
If I ignore the registration errors the installer completes. When I run my application I get the following error:
The type initializer for 'CrystalDecisions.CrystalReports.Engine.ReportDocument' threw an exception. >>> Could not load file or assembly 'CrystalDecisions.ReportAppServer.CommLayer, Version=13.0.2000.0, Culture=neutral, PublicKeyToken=692fbea5521e1304' or one of its dependencies. The system cannot find the file specified.
Do we need to run the full version of Windows Server 2008 for this to work? I have installed the required VC++ run-time dependencies and still no luck.

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

Windows 2008 Terminal Server issue after swapping modem/router

Hi, I have a problem I just can't crack.
Windows 2008 Terminal Server, all patched and up to date. The IP Address is 192.168.1.11 (on a teamed intel controller). Terminal services enabled and working ok.
TP-Link Modem 192.168.1.1, RDP Port forwarded ok.
Set the Windows gateway to 192.168.1.1 and external access to RDP is not a problem.
We had some modem speed issues, so we got a much faster connection, but it can't be used for incoming RDP, so left the TP-Link in place. So added a 3G modem at 192.168.1.5 and set that as the gateway.
External RDP access still works perfectly, and now users have much faster internet.
The TP-Link is giving some reliability issues, so I swapped it over for another modem, a Billion modem. Same 192.168.1.1 IP address, same port forwarding. External RDP access is no longer possible.
Swap back to the TP-Link and everything is fine. Test the modem on another site, everything works as expected.
If I set the gateway on the terminal server to 192.168.1.1 with the Billion attached then external RDP access is no problem. If I set it to 192.168.1.5 then it stops working again.
I tried with a new TP-Link modem of the same model with exactly the same settings and this also had the same problem. External RDP access will only work the existing TP-Link modem, which is a problem as the modem appears to be faulty.
It's almost like it hasn't worked out that it's a new network, and when Windows does that it seems to lock down RDP. That is only my assumption from experience of moving computers to new networks and RDP won't work until windows prompts you with the new
network screen to select home, office or public.
Has anyone experienced anything like this before or can shed some light on the problem?
Thanks.

Hi,
How is the issue going now? Is there any update?
Thanks.
Jeremy Wu
TechNet Community Support

BO XI 3.1 SP2 error while installing in Windows 2008 ENT Server 32 Bit

Hi
We have windows 2008 enterprise edition 32 Bit SP2 , While installing BO 3.1 SP2 we are getting the following error.
"Some files could not be created.
Please close all applications, reboot Windows and restart this installation."
1.we do have enough space as well as we are installing it through administrator account.
2.I increase the virtual memory size from 2 GB to 4 GB, still same error.
3.we downloaded the software in two diffrent machines. We tried extracting the "exe" file in two machine but still getting the same error.
4.We dont have any firewall connected and windows firewall is off.
Is there BO 3.1 Sp2 is available for windows 2008 ent server 32-Bit?
Because In the download site there is Windows Server on IA32 32-bit.
is it the correct version?
Please help us to solve this problem
Thanks

We have opened a ticket for this. After subsequent discussion with the forum support person we have installed BO Enterprise 3.1 SP2 fixed pack 2.5 on the server (Windows Server 2008 SP2). On the client side, we have also installed BO Enterprise 3.1 SP2 fixed pack 2.5 and Live Office SP2 fixed pack 2.5.
Once we tried to use the Web Intelligence document based on OLAP Universe in excel through Live Office it gives the following error.
"Failed to get the document information. (LO 26315) A database error occured. The database error text is: Failed to set properties (The component Microsoft® OLE DB Provider for Analysis Services returned server error (Database 'Sales' does not exist.)). (WIS 10901)(6315)".

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

Unable to list SFTP Directory on windows 2008 r2 server from internet

Hi experts,
I have configured a SFTP on windows 2008 r2 server. And i am using the Filezilla on client machine to connect to SFTP server.
The connection works properly on internal network but it displays error when i connect from internet.
Error: GnuTLS error -53: Error in the push function.
Response: 550 Data channel timed out.
Error: Failed to retrieve directory listing
This machine is publish with public IP and port22. The connection and authorization process gets complete but stops are Directory Listing.
PLease suggest the troublshooting steps..
Let me know if any more info is rquired.

Hi,
Do you also use the Filezilla to configure SFTP server? Since you use Filezilla on client machine to connect to SFTP server, I would suggest you ask for help from Filezilla forums for better and accurate answer.
https://forum.filezilla-project.org/
Best Regards,
Mandy
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Does WCS run on Windows 2008 R2 server?

Can anybody share his/her experience with running WCS on Windows 2008 R2 server?
Is it possible and did you experience any problems with it? (during installation or during normal usage)
Is it supported by Cisco already?
Our distributor is a little bit vague about that, that's is why I am asking it here.

From WCS 7 release notes :
Operating Systems Requirements
The following operating systems are supported:
•Windows 2003/SP2 and Windows 2003 R2/SP2 32-bit installations with all critical and security Windows updates installed.
Windows 2003/SP2 64-bit installations are not supported. A 32-bit operating system running on a 64-bit capable hardware is supported.
Windows 2003 32-bit installations provide support for up to 64 GB of RAM if Physical Address Extension (PAE) is enabled. See the Windows documentation for instructions on enabling this mode.
•Red Hat Linux Enterprise Server 5.X 32-bit operating system installations.
Red Hat Linux Enterprise Server 5.X 64-bit operating system installations are not supported. A 32-bit operating system running on a 64-bit capable hardware is supported.
•Windows 2003 and Red Hat Linux version support on VMware ESX version 3.0.1 and above with either local storage or SAN over fiber channel.
Individual operating systems running WCS in VMware must follow the specifications for the size of WCS that you intend to use.
No Windows 2008 ! I know lots of people have been crying for it and it should be coming in next releases but no promises as of now :-(
Nicolas

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.

Oracle 11g ODAC 11.1.0.6.21 on Windows 2008 Standard server gives TNS error

Hi,
I have Oracle 11g ODAC 11.1.0.6.21 installed on my Application server that has 32 bit Windows 2008 Standard. The Oracle database 10g is installed on another 2008 server. On database server I can connect using SQLPlus. But on application server I cannot connect using ODAC SQLPlus. I have given correct service name in tnsnames.ora file.
Error is ORA-12154 TNS: Listener cannot resolve service name
What's wrong? Is 11.1.0.6.21 not meant for Windows 2008? I did not get any errors while installing.
This 11.1.0.6.21 works perfectly for me on XP machine.
I have browsed this forum but not getting clear steps to peform.
Can someone guide me what is needed?
Thanks
Shrini

Hi,
The request to connect from the client is reaching the server but it seems the parsing of the service name is either wrong or the information is correct. Here are a couple of suggestions.
If you have a good known set of sqlnet.ora and tnsnames.ora files on another client where the same connection descriptor works, then backup the curreny client network config files and copy the good known files to the Windows 2008 web server where you see the error. Make sure you recycle the worker processes once the files have been copied.
Try to connect via Ezconnect and by pass the config files to see if you get the same error.
//hostname:port/servicenameofdb
where hostname is the machine where the target database is running
port is the port on the DB machine where the tns listener is running and listening
service name is the service name of the target DB
Use this syntax in the connect string box when attempting to connect from SQL PLUS out of the ODAC home.
You can also run lsnrctl utility on the server and vertify there is a handler for the service name or instance that is the target,
HTH
Jenny B.

INS-20802: Problem installing Grid Infrastructure on Windows 2008 R2 Server

Hello,
I try to install the Grid Infrastructure on a Windows 2008 x64 Server. Everything works fine (the SCAN configuration and Verify) but at the end of the installation process I get the following error message:
[INS-20802]: Grid Infrastructure Configuration not successfull.
The errors that I found in the file oraInstall2012-02-27_11-58-26AM.log inside the INVENTORY\LOGS directory :
INFO: Unable to read C:/app/11.2.0/grid/inventory/ContentsXML/comps.xml. Some inventory information may be lost.
INFO: Install type for "Oracle Database 11g 11.2.0.3.0 " is "ASM".
INFO: Conflict while setting install type of "Required Support Files 11.2.0.3.0 " to "Typical (Typical)". Install type already set to "Complete (Complete)". Seting it to "Custom (Custom)".
INFO: OUI-10066:Not all the dependencies for the component Oracle Database 11g 11.2.0.3.0 could be found. Missing component oracle.assistants.server 11.2.0.3.0.
INFO: OUI-10066:Not all the dependencies for the component Oracle Database 11g 11.2.0.3.0 could be found. Missing component oracle.ntrdbms.oraconfig 11.2.0.3.0.
INFO: OUI-10066:Not all the dependencies for the component Oracle Database 11g 11.2.0.3.0 could be found. Missing component oracle.xdk 11.2.0.3.0.
INFO: OUI-10066:Not all the dependencies for the component Oracle Database 11g 11.2.0.3.0 could be found. Missing component oracle.xdk.server 11.2.0.3.0.
INFO: OUI-10066:Not all the dependencies for the component Oracle Database 11g 11.2.0.3.0 could be found. Missing component oracle.mgw.common 11.2.0.3.0.
INFO: OUI-10066:Not all the dependencies for the component Oracle Database 11g 11.2.0.3.0 could be found. Missing component oracle.rdbms.install.seeddb 11.2.0.3.0.
INFO: OUI-10066:Not all the dependencies for the component Oracle Database 11g 11.2.0.3.0 could be found. Missing component oracle.ctx 11.2.0.3.0.
INFO: OUI-10066:Not all the dependencies for the component Oracle Database 11g 11.2.0.3.0 could be found. Missing component oracle.owb.rsf 11.2.0.3.0.
INFO: OUI-10066:Not all the dependencies for the component Oracle Database 11g 11.2.0.3.0 could be found. Missing component oracle.sysman.console.db 10.1.0.2.0.
INFO: OUI-10066:Not all the dependencies for the component Oracle Database 11g 11.2.0.3.0 could be found. Missing component oracle.rdbms.oci 11.2.0.3.0.
INFO: OUI-10066:Not all the dependencies for the component Oracle Database 11g 11.2.0.3.0 could be found. Missing component oracle.ovm 11.2.0.3.0.
INFO: OUI-10066:Not all the dependencies for the component Oracle Database 11g 11.2.0.3.0 could be found. Missing component oracle.sqlj.sqljruntime 11.2.0.3.0.
INFO: OUI-10066:Not all the dependencies for the component Oracle Database 11g 11.2.0.3.0 could be found. Missing component oracle.rdbms.hsodbc 11.2.0.3.0.
INFO: OUI-10066:Not all the dependencies for the component Oracle Database 11g 11.2.0.3.0 could be found. Missing component oracle.marvel 11.2.0.3.0.
INFO: OUI-10066:Not all the dependencies for the component Oracle Database 11g 11.2.0.3.0 could be found. Missing component oracle.dbdev 11.2.0.3.0.
INFO: OUI-10066:Not all the dependencies for the component Oracle Database 11g 11.2.0.3.0 could be found. Missing component oracle.dbjava.server 11.2.0.3.0.
INFO: Install type for "Cluster Ready Services Files 11.2.0.3.0 " is "Complete".
INFO: Conflict while setting install type of "HAS Common Files 11.2.0.3.0 " to "Complete (Complete)". Install type already set to "Typical (Typical)". Seting it to "Custom (Custom)".
INFO: Install type for "Oracle Net Listener 11.2.0.3.0 " is "Typical".
INFO: Install type for "Oracle Internet Directory Client 11.2.0.3.0 " is "Typical".
INFO: Install type for "Oracle JVM 11.2.0.3.0 " is "Typical".
INFO: OUI-10066:Not all the dependencies for the component Oracle JVM 11.2.0.3.0 could be found. Missing component oracle.javavm.companion 11.2.0.3.0.
INFO: Install type for "Oracle Net 11.2.0.3.0 " is "Typical".
INFO: Install type for "Oracle Netca Client 11.2.0.3.0 " is "Typical".
INFO: Install type for "SQL*Plus 11.2.0.3.0 " is "Typical".
INFO: Install type for "Oracle Database Utilities 11.2.0.3.0 " is "Typical".
INFO: OUI-10066:Not all the dependencies for the component Oracle Database Utilities 11.2.0.3.0 could be found. Missing component oracle.omwb 10.1.0.1.0.
INFO: Install type for "Oracle Recovery Manager 11.2.0.3.0 " is "Typical".
INFO: Install type for "PL/SQL 11.2.0.3.0 " is "Typical".
INFO: Install type for "HAS Files for DB 11.2.0.3.0 " is "Typical".
INFO: Install type for "Assistant Common Files 11.2.0.3.0 " is "Typical".
INFO: Conflict while setting install type of "Oracle Help For Java 4.2.9.0.0 " to "Typical (Typical)". Install type already set to "Complete (Complete)". Seting it to "Custom (Custom)".
INFO: Conflict while setting install type of "Buildtools Common Files 11.2.0.3.0 " to "Typical (Typical)". Install type already set to "Complete (Complete)". Seting it to "Custom (Custom)".
INFO: Conflict while setting install type of "Sun JDK 1.5.0.30.03 " to "Maximum (Complete)". Install type already set to "Maximum (Complete)". Seting it to "Custom (Custom)".
INFO: OUI-10066:Not all the dependencies for the component Assistant Common Files 11.2.0.3.0 could be found. Missing component oracle.bali.kodiak 1.2.1.0.0I.
INFO: Install type for "HAS Common Files 11.2.0.3.0 " is "Custom".
INFO: Install type for "Oracle Multimedia 11.2.0.3.0 " is "Typical".
INFO: Install type for "Oracle Multimedia Locator 11.2.0.3.0 " is "Typical".
INFO: Install type for "Required Support Files 11.2.0.3.0 " is "Custom".
INFO: Conflict while setting install type of "Oracle Net Required Support Files 11.2.0.3.0 " to "Custom (Custom)". Install type already set to "Complete (Complete)". Seting it to "Custom (Custom)".
INFO: Conflict while setting install type of "Oracle Globalization Support 11.2.0.3.0 " to "Custom (Custom)". Install type already set to "Typical (Typical)". Seting it to "Custom (Custom)".
INFO: Conflict while setting install type of "Oracle Core Required Support Files 11.2.0.3.0 " to "Custom (Custom)". Install type already set to "Typical (Typical)". Seting it to "Custom (Custom)".
INFO: Conflict while setting install type of "RDBMS Required Support Files 11.2.0.3.0 " to "Custom (Custom)". Install type already set to "Complete (Complete)". Seting it to "Custom (Custom)".
INFO: Conflict while setting install type of "Oracle RAC Required Support Files-HAS 11.2.0.3.0 " to "Custom (Custom)". Install type already set to "Typical (Typical)". Seting it to "Custom (Custom)".
INFO: Install type for "Oracle JDBC/THIN Interfaces 11.2.0.3.0 " is "Typical".
INFO: OUI-10066:Not all the dependencies for the component Oracle JDBC/THIN Interfaces 11.2.0.3.0 could be found. Missing component oracle.dbjava.ucp 11.2.0.3.0.
INFO: Install type for "Oracle Core Required Support Files 11.2.0.3.0 " is "Custom".
INFO: Install type for "Installation Common Files 11.2.0.3.0 " is "Typical".
INFO: Install type for "Precompiler Required Support Files 11.2.0.3.0 " is "Custom".
INFO: Install type for "Parser Generator Required Support Files 11.2.0.3.0 " is "Custom".
INFO: Install type for "Agent Required Support Files 10.2.0.4.3 " is "Custom".
INFO: Install type for "XDK Required Support Files 11.2.0.3.0 " is "Custom".
INFO: Install type for "Oracle RAC Required Support Files-HAS 11.2.0.3.0 " is "Custom".
INFO: Install type for "Buildtools Common Files 11.2.0.3.0 " is "Custom".
INFO: Install type for "Oracle Globalization Support 11.2.0.3.0 " is "Custom".
INFO: Install type for "Oracle Locale Builder 11.2.0.3.0 " is "Custom".
INFO: Conflict while setting install type of "Oracle JFC Extended Windowing Toolkit 4.2.36.0.0 " to "Custom (Custom)". Install type already set to "Complete (Complete)". Seting it to "Custom (Custom)".
INFO: Install type for "Oracle Clusterware RDBMS Files 11.2.0.3.0 " is "Typical".
INFO: Install type for "Cluster Verification Utility Common Files 11.2.0.3.0 " is "Typical".
INFO: Install type for "CFS 11.2.0.3.0 " is "Complete".
INFO: Install type for "Oracle Notification Service (eONS) 11.2.0.3.0 " is "Typical".
INFO: Install type for "Cluster Verification Utility Files 11.2.0.3.0 " is "Complete".
INFO: Install type for "Oracle LDAP administration 11.2.0.3.0 " is "Typical".
INFO: Install type for "Deinstallation Tool 11.2.0.3.0 " is "Complete".
INFO: Conflict while setting install type of "Oracle Database Deconfiguration 11.2.0.3.0 " to "Complete (Complete)". Install type already set to "Typical (Typical)". Seting it to "Custom (Custom)".
INFO: Install type for "Enterprise Manager Common Files 10.2.0.4.3 " is "Complete".
INFO: Install type for "Oracle Notification Service 11.2.0.3.0 " is "Typical".
INFO: Install type for "Oracle Help For Java 4.2.9.0.0 " is "Custom".
INFO: Conflict while setting install type of "Bali Share 1.1.18.0.0 " to "Custom (Custom)". Install type already set to "Maximum (Complete)". Seting it to "Custom (Custom)".
INFO: Conflict while setting install type of "Oracle Ice Browser 5.2.3.6.0 " to "Custom (Custom)". Install type already set to "Complete (Complete)". Seting it to "Custom (Custom)".
INFO: Install type for "Oracle Ice Browser 5.2.3.6.0 " is "Custom".
INFO: Conflict while setting install type of "Oracle Extended Windowing Toolkit 3.4.47.0.0 " to "Custom (Custom)". Install type already set to "Complete (Complete)". Seting it to "Custom (Custom)".
I have read and implemented all the settings described in DOCs ID 811271.1 , ID 810394.1 and RAC on Windows Step by Step Installation Instructions.
After many attempts with the same error Ii am trying to install in a single node (RAC1). But the error looks the same, my server is clean with no oracle.
Note: For this installation I downloaded and uncompressed the files p10404530_112030_MSWIN-x86-64_1of7.zip, p10404530_112030_MSWIN-x86-64_2of7 and p10404530_112030_MSWIN-x86-64_3of7 of the oracle site.
I do not know what to do for this installation work.
Thanks

My recommendation would be to format the disks and install Linux.
And I say that only half-jokingly. Fail-over with Windows is never as fast or as transparent as with a *NIX O/S.
As to your specific issue ... open an SR with Oracle Support. Hardly anyone uses Windows for Oracle ... even fewer with RAC ... for the reason I gave above.

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

Similar Messages

Maybe you are looking for