Client Stop reporting in WSUS after Approval patches

Hi Team,
Recently i faced lot of issue in my wsus server during patching activity, After approving patches certain client stop reporting in wsus . I have tried all the troubleshooting but no one help.
can any one help me and provide troubleshooting steps which required in this type of cases
Regards, Triyambak

I am facing same issue in one of server , here is the log file
2014-06-24 02:56:11:066
852 c18
PT WARNING: SOAP Fault: 0x00012c
2014-06-24 02:56:11:066
852 c18
PT WARNING: faultstring:Fault occurred
2014-06-24 02:56:11:066
852 c18
PT WARNING: ErrorCode:ServerChanged(4)
2014-06-24 02:56:11:066
852 c18
PT WARNING: Message:Server rolled back since last call to GetCookie
2014-06-24 02:56:11:066
852 c18
PT WARNING: Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/GetCookie"
2014-06-24 02:56:11:066
852 c18
PT WARNING: ID:2f956ab6-fac3-4e68-bffa-48557d580e88
2014-06-24 02:56:11:066
852 c18
PT WARNING: PTError: 0x80244015
2014-06-24 02:56:11:066
852 c18
PT WARNING: GetCookie_WithRecovery failed : 0x80244015
2014-06-24 02:56:11:066
852 c18
PT WARNING: RefreshCookie failed: 0x80244015
2014-06-24 02:56:11:066
852 c18
PT WARNING: RefreshPTState failed: 0x80244015
2014-06-24 02:56:11:066
852 c18
PT WARNING: Sync of Updates: 0x80244015
2014-06-24 02:56:11:066
852 c18
PT WARNING: Cached cookie has expired or new PID is available
2014-06-24 02:56:11:066
852 c18
PT Initializing simple targeting cookie, clientId = 60adbf7d-5194-4cd9-90c7-e00efccedcb7, target group = WSUS 2003 x32 Prod Group 1, DNS name = lpsjcmwbp13.sumcweb.com
2014-06-24 02:56:11:066
852 c18
PT Server URL = http://lpchweb-wsus.sumcweb.com/SimpleAuthWebService/SimpleAuth.asmx
2014-06-24 02:56:30:488
852 c18
Agent * WARNING: Failed to synchronize, error = 0x80244015
2014-06-24 02:56:30:504
852 c18
Report CWERReporter finishing event handling. (00000000)
2014-06-24 02:56:30:504
852 c18
DnldMgr File locations for service 3DA21691-E39D-4DA6-8A4B-B43877BCB1B7 changed
2014-06-24 02:56:30:504
852 c18
Agent Server changed and need resyncing with server
2014-06-24 02:56:30:895
852 c18
PT +++++++++++ PT: Synchronizing server updates +++++++++++
2014-06-24 02:56:30:895
852 c18
PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://lpchweb-wsus.sumcweb.com/ClientWebService/client.asmx
2014-06-24 02:56:35:692
852 c18
PT +++++++++++ PT: Synchronizing extended update info +++++++++++
2014-06-24 02:56:35:692
852 c18
PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://lpchweb-wsus.sumcweb.com/ClientWebService/client.asmx
an AU detection already in progress
2014-06-24 01:35:37:030
832 700
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:37:030
832 700
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:37:077
832 700
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:37:077
832 700
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:37:296
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:37:296
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:37:562
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:37:562
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:37:655
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:37:655
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:37:968
832 700
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:37:968
832 700
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:38:015
832 700
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:38:015
832 700
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:38:343
832 700
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:38:343
832 700
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:38:515
832 700
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:38:515
832 700
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:38:655
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:38:655
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:38:937
832 700
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:38:937
832 700
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:38:999
832 700
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:38:999
832 700
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:39:421
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:39:421
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:39:421
832 700
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:39:421
832 700
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:39:640
832 700
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:39:640
832 700
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:39:859
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:39:859
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:39:968
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:39:968
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:40:312
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:40:312
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:40:374
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:40:374
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:40:609
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:40:609
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:40:859
832 700
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:40:859
832 700
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:41:030
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:41:030
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:41:202
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:41:202
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:41:374
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:41:374
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:41:515
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:41:515
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:41:796
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:41:796
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:41:952
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:41:952
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:42:077
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:42:077
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:42:374
832 700
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:42:374
832 700
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:42:499
832 700
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:42:499
832 700
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:42:671
832 700
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:42:671
832 700
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:42:952
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:42:952
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:43:062
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:43:062
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:43:327
832 700
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:43:327
832 700
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:43:499
832 700
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:43:499
832 700
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:43:624
832 700
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:43:624
832 700
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:43:859
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:43:859
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:43:984
832 700
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:43:984
832 700
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:44:218
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:44:218
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:44:343
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:44:343
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:44:687
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:44:687
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:44:859
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:44:859
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:44:984
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:44:984
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:45:281
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:45:281
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:45:343
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:45:343
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:45:749
832 700
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:45:749
832 700
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:45:749
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:45:749
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:45:984
832 700
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:45:984
832 700
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:46:281
832 700
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:46:281
832 700
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:46:452
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:46:452
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:46:593
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:46:593
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:46:765
832 700
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:46:765
832 700
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:46:968
832 700
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:46:968
832 700
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:47:124
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:47:124
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:47:343
832 700
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:47:343
832 700
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:47:515
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:47:515
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:47:734
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:47:734
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:48:015
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:48:015
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:48:109
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:48:109
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:48:327
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:48:327
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:48:499
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:48:499
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:48:702
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:48:702
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:48:906
832 700
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:48:906
832 700
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:49:234
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:49:234
832 1378
AU Piggybacking on an AU detection already
Regards, Triyambak

Similar Messages

WSUS - Clients stopped reporting on downstream replicas

Just looking for some advice on what could be wrong here.
Some of our downstream WSUS replicas have stopped 'receiving' updates from machines on the network. Below is an example of one group affected. In this case WSUS is on a 2003 server but there is 1 instance where there is a 2008 R2 replica with
the exact same problem.
<image can't be posted until account is verified>
Image was of the WSUS console with machines in the group stuck on 'Last Status Report' on '15/04/2015'. Once account is verified, will post.
There doesn't seem to be a common denominator between the replicas that do work and those that don't.
WSUS v3.2.7600.256
According to Add or Remove Programs, the following hotfixes are installed:
KB2720211
KB2734608
There are no client connectivity issues, one of the machines is actually the WSUS server itself (so local). The others are all on the same local LAN
Machines are pointed to the correct WSUS server via GPO and worked up until the 15th.
The only thing that stands out in the WindowsUpdate.log on each machine is this:
2015-04-20   10:49:22:094   900   15f0   Report   REPORT EVENT: {3B186FC1-29B3-4D3E-800E-19BF108CE254}   2015-04-20 10:40:45:606+0200   1
202   102   {00000000-0000-0000-0000-000000000000}   0   0   AutomaticUpdates   Success   Content Install   Reboot completed.
2015-04-20   10:49:22:094   900   15f0   Report   WARNING: Reporter failed to upload events with hr = 80240004.
I'm not convinced the error is totally relevant to the issue.
I have searched through many online posts but haven't found an answer that works.
Can anyone point me in the right direction or aware of what could be the problem?
Thanks
-- Edit for Further Info --
These are not new replicas and definitely have been working up until recently. All 'broken' replicas seemed to stop on the same day.

Hi,
Have you changed anything before this issue occurs?
Are these clients able to be updated from WSUS server successfully?
Did you install any update on these WSUS servers or clients before this issue occurs?
If you have configured SSL on the WSUS server, please check if the certificate was expired.
Best Regards.
Steven Lee Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Hi,
Thanks for getting back to me.
1) No changes other than deleting expired updates through the WSUS control panel.
2) Not anymore, no
3) Server updates were applied, but I don't believe there were any for WSUS specifically. The same updates would have been applied to other servers which are not affected
4) No SSL in this case.

Clients not reporting to WSUS

I too have many clients that have not reported to the Wsus Server.
The clients are listed in the All Computers group of WSUS
I have created target groups
The computers are listed in the correct target groups
I have approved update for the target group
Clients are not reporting at all
Thanks

I too have many clients that have not reported to the Wsus Server.
The computers are listed in the correct target groups
Clients are not reporting at all
What do you mean by "not reporting"... they're listed in the console? What is the "Last Contact" date? What is the "Last Reported Date".
Run a detection event on one of the clients and post the results from the WindowsUpdate.log.
Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2013)
My MVP Profile:
http://mvp.support.microsoft.com/profile/Lawrence.Garvin
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

Make expense report read only after approval

Hello,
Please guide on how to make an expense report read only once it is approved and no change option should be enabled on enterprise portal. I have tried all the combinations of security in the ESS roles inside ABAP but not able to find the right combination. Please suggest.
Thank you.

it needs P_travl authorisaiton
Create a new Travel Request or Expense report (AUTHF W)
Change open travel Request or Expense report (AUTHF W10, W30)
Change returned Travel Request or Expense report (AUTHF W11, W31)
Create Expense report from approved Travel request (AUTHF W21)
use the note 1402925
If you create an expense report based on a not approved travel request,
the system asks for authorization to change this request
(W11 or W10) for AUTHF and then 30 or 31 for AUTHS.
THis combination is of course given by your P_TRAVEL object.
You need at least 2 seperate P_TRAVEL objects, whereas only 1 of them
contains AUTHS values for expense report. This must only contain
W2* and 30 / 31. Hopefully this could help.

Help on Discount after Approval Procedures

Hi Experts,
Our customer is reporting an error after approval process that some documents has discount after the approval procedure.
Our customer insist that there are no discount when they approved the PO/ or Ap invoice but after approval, the originator can no longer add the documnts due to discounts.
Is there anybody experience the same problems with thier system.
I cannot report this since I cannot simulate the error
We are using 2007B Pl15
Regards,
Sandra

HI Sandra,
I agree with Gordon, I faced similar issues with the discount field but not with approval process though.
This happens when Quantity and unit price of an item are entered and the line total gets populated automatically after this if the user changes the line total without deleting unit price or quantity the discount field gets populated according to the change in the line total, please check if the end user is doing any of this.....or similar changes in these lines.....
regards,
Murali

Patches not visible in SCCM 2007 Site server even after approving the patches in WSUS

Hi,
The patches are not appearing in SCCM 2007 site server after approving the same patches in WSUS.
Below are the patches.
MS14-080: Cumulative Security Update for Internet Explorer - Windows Server 2008 SP2 - IE 7 - KB3008923 [23,186.1]
MS14-018: Cumulative Security Update for Internet Explorer - IE 11 - KB2929437 - Windows Server 2008 R2 SP1 (x64) [4,32.4]
MS14-066: Vulnerability in Schannel Could Allow Remote Code Execution - Windows Server 2008 SP2 - KB2992611 (x64) - V2 [1,8.3]
MS14-038: Vulnerability in Windows Journal Could Allow Remote Code Execution - Windows Server 2008 SP2 - KB2971850 [1,8.1]
MS09-060: Vulnerabilities in Microsoft Active Template Library (ATL) ActiveX Controls for Microsoft Office Could Allow Remote Code Execution - Visio Viewer 2007 SP1/SP2 [1,8.1]
MS12-001: Vulnerability in Windows Kernel Could Allow Security Feature Bypass - Windows Server 2008 R2 Gold (x64) [1,8.1]
MS14-033: Vulnerability in Microsoft XML Core Services Could Allow Information Disclosure - Windows Server 2008 SP2 - KB2939576 [1,8.1]
MS14-025: Vulnerability in Group Policy Preferences Could Allow Elevation of Privilege - Windows Server 2008 SP2 - KB2928120 (x64) [1,7.8]
MS13-014: Vulnerability in NFS Server Could Allow Denial of Service - Windows Server 2008 R2 Gold/SP1 (x64) [1,7.7]
I have approved the above patches in WSUS and ran syncronization. The log wsyncmgr.log show that synchronization is done and even all child sites are syncronized. But I am unable to find the above even in the parent site. Checked all the SUP settings and
all the 2008 server updates are set and marked to download.
Please help me out on fixing this.

So you should NEVER approve anything in WSUS. This will cause problems with your clients. Honestly since you approved things in WSUS, I would uninstall WSUS and reinstall it, reinstall the SUP, this will clear up any issues that now exist.
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ

SBS 2008 Security report not showing correct status after Feb patch cycle

Hello,
I wonder if anyone can shed any light on this strange problem which has occurred after February patch cycle. On the SBS detailed report that comes through, the security section is showing as RED error. Though
if you look at the detail, each section is listed as green compliant. Not sure why this has happened? Has anyone else seen this before?
Many thanks,

Hi,
Can you provide me the detailed information about the patch you installed before the issue occurred? Have you tried to uninstall the patch and reinstall it again to see if the same issue persists?
In addition, please also try to repair the monitoring and reporting feature to see if it could resolve the issue.
Repair monitoring and reporting features in Windows Small Business Server 2008
http://technet.microsoft.com/en-us/library/dd560614(v=ws.10).aspx
Hope this helps.
Best Regards,
Andy Qi
TechNet Subscriber Support
If you are
TechNet Subscription user and have any feedback on our support quality, please send your feedback
here.
Andy Qi
TechNet Community Support

DBCA stopped working after installing Patch 13783453

I apologize if this has been answered before but I could not find a thread using the search.
I am running Windows 7 64-bit with 64-bit JDK 1.6.0_41. I installed 11.2.0.3 successfully. I used DBCA to create a desktop edition database. I then installed Patch 13783453 (Patch 4). The patch was installed successfully. After the patch installation everything works except DBCA and Upgrade Assistant.
It looks like some of the jar files are corrupted after the patch installation. When I rollback the patch, I am again able to run DBCA. The exception that I see when I run DBCA is
$ ./dbca.bat
Exception in thread "main" java.lang.ClassFormatError: Unknown constant tag 13 in class file oracle/cluster/deployment/ClusterwareInfo
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:621)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)
at java.net.URLClassLoader.access$100(URLClassLoader.java:56)
at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
at oracle.sysman.assistants.util.hasi.HAUtils.<init>(HAUtils.java:236)
at oracle.sysman.assistants.util.hasi.HAUtils.getInstance(HAUtils.java:279)
at oracle.sysman.assistants.util.NetworkUtils.getAllListeners(NetworkUtils.java:347)
at oracle.sysman.assistants.util.step.StepContext.<init>(StepContext.java:334)
at oracle.sysman.assistants.dbca.backend.Host.<init>(Host.java:823)
at oracle.sysman.assistants.dbca.ui.UIHost.<init>(UIHost.java:258)
at oracle.sysman.assistants.dbca.ui.InteractiveHost.<init>(InteractiveHost.java:54)
at oracle.sysman.assistants.dbca.Dbca.getHost(Dbca.java:164)
at oracle.sysman.assistants.dbca.Dbca.execute(Dbca.java:112)
at oracle.sysman.assistants.dbca.Dbca.main(Dbca.java:180)
Any ideas how to fix this?
Thanks in advance.
Edited by: 1002504 on Apr 25, 2013 7:20 AM

which version of windows 7 you are using ? any version expect home like sb said open SR

Adobe form not working after MSS Patch Upgrade

Hi,
We have implemented ESS/MSS and in one of the MSS scenario to create a new personnel chnage request we have an Adobe interactive form (WD) which actually validates the users Social Security number by calling an RFC in the ECC 6.0 and updates the form's filed on the front end. There was an issue of "Expired SSO Ticket" and to resolve this SAP recommended to apply SAP_JTECHS (SAPJTECHS13P_14-10003467) and SAP_JTECHF (SAPJTECHF13P_15-10003468) patches to fix the problem. But after applying these patches Adobe form for PCR has stopped working and it just gets hanged, form appears on the front end and when user enters the values and hit enter to validate, it doesnt communicate with the Backend ECC system only the SAP status picture keeps rotating, i turned the trace ON and checked it, its not at all communicating with the ECC system. Where as in other systems where we have not appplied the pacthes, those are working fine. One of the error i noticed in the server log is as below:
jco.client.mysapsso2=AjExMDAgAA5wb3J0YWw6QkNPTFNUT4gAE2Jhc2ljYXV0aGVudGljYXRpb24BAAdCQ09MU1RPAgADMDAwAwADU1BEBAAMMjAwODExMDMxNjU3BQAEAAAAEAoAB0JDT0xTVE//AQUwggEBBgkqhkiG9w0BBwKggfMwgfACAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHATGB0DCBzQIBATAiMB0xDDAKBgNVBAMTA1NQRDENMAsGA1UECxMESjJFRQIBADAJBgUrDgMCGgUAoF0wGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMDgxMTAzMTY1NzQwWjAjBgkqhkiG9w0BCQQxFgQUfD7V7TS!58cgzIFyucxCSL4ltuswCQYHKoZIzjgEAwQvMC0CFA4Q0!Rr2xYFPwFwXz8WeFF1UALlAhUAmHiTdHw!3s4Q!Jc9gDyY4QSvxa4=, user=, mshost=sapdv2.company.com, r3name=DV2, jco.client.type=B, jco.client.trace=0, group=SRS, codepage=1100}
Client not connected#
#1.5 #76C1EDD07B440026000000000007501600045ACC2EF6809D#1225732914577#/Applications/BusinessLogic#sap.com/home~zb2bzsrs#com.sap.isa.core.eai.sp.jco.JCoConnectionStateful#BCOLSTO#1480##hadspd1.bnet_SPD_306896250#BCOLSTO#daca9e30a9cb11dd99c976c1edd07b44#SAPEngine_Application_Thread[impl:3]_19##0#0#Error#1#/Applications/BusinessLogic#Java###Error occcurred in EAI layer "".#2#com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: Error in module RSQL of the database interface.#parameters: [client]='null' [user]='null' [language]='null' [ashost]='null' [systemnumber]='null' [mshost]='null' [gwhost]='null' [gwserv]='null' [group]='null' [systemid]='null'
Properties: {passwd=?, lang=en, client=150,
Can someone please suggest what could be the possible reason for such a problem with Adobe form and whats the way out to resolve this. Appreciate a quick help in this regard.
Thanks in advance,
Sarabjeet.

Hi,
We had the same issue after the Patch update to SP17 in both Backend as well in Portal, to resolve my colleagues had a look at the standard forms which were working and found that because of the patch update the script used in the custom forms was changed and not the standard and
on event trigger which was processed in the container they replace the script to the standard one. and it started working.
But this is not the solution we are looking at solution on having the same version of script as in the standard even after the patch update.
So to your point to resolve compare the scripts in both standard and customized forms and do the same.
And also have a look at the SAP Note: 1109392
.... this is a temporary solution.....
Hope this helps.
Cheers-
Pramod

Errors found retrieving data after SAP Patching

Hi Team,
I received the error "errors found retrieving data" when I try to click
the ‘Refresh’ button to display data for my reports. Refer to the
attached screen.
I’m receiving it from trying to refresh data in ‘Reports’ and ‘Input
schedule’ templates from the BPC Excel Client. This was happen after we
done the SAP Patching earlier it was working fine.
Appreciate your help in advance
Thank you
Regards
Raghu

Hi,
Try to process all dimensions.
If not try to find more details from EPM-->More-->Log
Hope it helps..
regards,
Raju

User sip folder have many .cache files with 4kb and the folder is becoming full and Lync Client stops working

User sip folder have manu Mailitem&username&.cache files until folder is full and Lync client stops working.

Hi,
You can try to change the Lync Profile name. After you do it, Lync will create a new Profile. The Lync Profile path is following:
%UserProfile%\AppData\Local\Microsoft\Office\15.0\Lync
If the issue persists, please repair Office 2013 and then test again.
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Webi scheduling error in BO 4.0 SP04 after security patch updates in windows server 2008 R2

We are getting below error in BO 4.0 SP04 Web Intelligence report scheduling after security patch updates in windows server 2008 R2
while trying to invoke the method com.businessobjects.sdk.core.server.IServer.getServerContext() of an object returned from com.businessobjects.rebean.wi.impl.services.DocumentInstanceManagementServiceImpl.getServer(com.businessobjects.sdk.core.context.IContext, com.businessobjects.rebean.wi.model.engine.IDocumentInstance)
We have reverted back security patch but still giving above scheduling problem in BO 4.0 SP04 WebI and we can view and refresh report.
Is there any way to fix the scheduling problem in BO 4.0 SP04 WebI?

HI,
Check SAP notes if they will help you.
1934855 - Scheduled Web Intelligence documents fail with com.businessobjects.sdk.core.server Error
1916443 - Scheduling Web Intellignce reports which are having long names to excel and pdf fails.
1792921 - Unable to schedule Webi documents in Excel or PDF format

Windows 8 and 2012 are not reporting to wsus

hi
i have a windows server 2008 r2 sp1 with latest patch installed wsus
3.2.7
newly installed windows 8 and server 2012 are not reporting to wsus
please help

Am 29.04.2014 schrieb Prasoon.PV:
i have a windows server 2008 r2 sp1 with latest patch installed wsus 3.2.7
Which version from WSUS exactly do have?
WSUS 3.0 (SP2):    Build 3.2.7600.226
WSUS 3.0 (SP2) + KB2720211:    Build 3.2.7600.251
WSUS 3.0 (SP2) + KB2734608:    Build 3.2.7600.256
WSUS 3.0 (SP2) + KB2828185:    Build 3.2.7600.262
The Version Number you will find on the startpage from WSUS.
http://www.wsus.de/images/wsus-version.png
newly installed windows 8 and server 2012 are not reporting to wsus
If you have .262 installed, pls control in registry for WSUS-Settings:
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate]
"WUServer"="http://WSUS-Server-Name oder IP-Adresse:Port"
"WUStatusServer"="http://WSUS-Server-Name oder IP-Adresse:Port"
If there is your WSUS, have a look in %windir%\WindowsUpdate.log for
errors.
Servus
Winfried
Gruppenrichtlinien
WSUS Package Publisher
HowTos zum WSUS Package Publisher
NNTP-Bridge für MS-Foren

Issue with Default Variable in WAD after Java Patch 7.01.7.31

Hello all,
I'm running into an issue with the Web Application Designer Template execution for a particular default variable. This started occuring after Java Patch 7.01.7.31 we had implented over the weekend.
The issue is when Executing the WAD Template, we have a selection screen with a variable with default values assigned to it. When leaving the default values and hitting Ok to execute through the screen does not register and stays as is and I get a message at the top with the following: Characteristic Prob % Number has no master data for "1.00" or you do not have authorization.
This only seems to occur for this default variable on info object Prob % Number, the other default variables seem to work fine. Also another note when clearing out the values it returns data and executes through. The value 1.00 is also a valid value in the cube and also in the output display. If we run this report in the BEx analyzer, the selection screen executes through with the default variable perfectly fine, this is only an issue with the Web Application Designer Template.
Has anyone ran into this? I've searched and have not found any notes as of yet.
Thank you,
-Andy

Dear Andy,
Please raise this to SAP, seems like a strange problem this needs to be addressed by OSS note only.
Close this thread once you get a solution.
Regards.
Den

XL Reporter gives Error after updating from PL 25 to SBO 2005 B PL 38

Thnaks Shridhar,
I have tested it in PL 38, its work fine but it has occoured one more problem i.e. XL Reporter is not working now.
However I have updated XL Reporter to PL30, but it gives error.
It has reamed used userdefined fields of the report. I have correct it too. But it gives error " Expansion has problem ".
Can any body has idea for running XL reporter successfully after updating patch level.
Can any one has faced this error or have solutions.
Pl. Help. so that i can updating it to Final Live Database.
Warm Regards,
Chintesh Soni

Hi..Shridharan,
Thanks for reply and guidance....!!
But I have successfully installed the XL Reporter means upgraded.
Now, When I am running existing reports which are preapred in previous version, is not running. It gives error i.e. Expansion has problem.
B4 this error, it has shown me some other error for user defined field was not found, when i have checked, the upgradation of patch level has changed the name of UDFs.
I have modified the udf names in the report.
Can u identify wht is the problem exactly please..
With Warm Regards,
Chintesh Soni

Client Stop reporting in WSUS after Approval patches

Similar Messages

Maybe you are looking for