Issues in PI after patching

Hello everyone,
Basis has applied patches to our system.
However, after the patching,all the communication channels are in red status or turn red when we try to test a scenario.
We did a cache refresh and also restarted server level service: CPA cache via netweaver administrator,which was ok.
But, all scenarios are failing in sxmb_moni with error: "Communication failure during JCo call ,error when opening an RFC connection"
When we tried to change the password in RFC communication channels, it gives error "Error loading adapter metadata", Attempt to access application Repository using HMI failed, sxmb_ifr transaction is not working.
Our sm59 connection tests are failing: Error while opening an RFC connection.
Error: program sapfallback not registered.
Can you please help in this.
Thanks,
Monika

Hi Everyone,
The issue seems to be with the JCO communication that interacts with JAVA and ABAP.
Change the KeepAlive parameter to 0 and can try.
We had this issue, SAP suggested to change the KeepAlive parameter.

Similar Messages

ALV table issue after patching.

Hi Experts.
In our applications, there is a button. On click of that button an ALV list will be displayed in the POP-UP.
First time when we click the button this works fine. After that the ALV list does not get displayed in the POU-UP.
Every time we have to re login and do the process.
Note: This is happening only after patching.
Thanks.

Hi i have attached the piece of code. This code is written in DOINIT Method of the view in which the ALV is embedded. Everytime the table lt_locations will have the data which needs to be displayed in the ALV. The ALV gets displayed only first time and next time if we click the button, the ALV list is not displayed.
DATA lo_nd_srlocations TYPE REF TO if_wd_context_node.
DATA lo_el_srlocations TYPE REF TO if_wd_context_element.
DATA ls_srlocations    TYPE wd_this->element_srlocations.
DATA it_srlocations    TYPE wd_this->elements_srlocations.
DATA lt_srlocations    TYPE STANDARD TABLE OF zxr_locations.
navigate from <CONTEXT> to <SRLOCATIONS> via lead selection
lo_nd_srlocations = wd_context->get_child_node( name = wd_this->wdctx_srlocations ).
get element via lead selection
lo_el_srlocations = lo_nd_srlocations->get_element( ).
SELECT * FROM zxr_locations INTO TABLE lt_srlocations.
DATA lo_nd_locations TYPE REF TO if_wd_context_node.
DATA lo_el_locations TYPE REF TO if_wd_context_element.
DATA ls_locations TYPE wd_this->element_locations.
    DATA lt_locations TYPE wd_this->elements_locations.
navigate from <CONTEXT> to <LOCATIONS> via lead selection
lo_nd_locations = wd_context->get_child_node( name = wd_this->wdctx_locations ).
get all declared attributes
lo_nd_locations->get_static_attributes_table(
    IMPORTING
      table = lt_locations ).
lo_nd_srlocations->bind_table( lt_locations ).
lo_nd_srlocations->bind_table( lt_srlocations ).
DATA lo_cmp_usage TYPE REF TO if_wd_component_usage.
lo_cmp_usage =   wd_this->wd_cpuse_alv_srlocations( ).
IF lo_cmp_usage->has_active_component( ) IS INITIAL.
    lo_cmp_usage->create_component( ).
ENDIF.
DATA lo_interfacecontroller TYPE REF TO iwci_salv_wd_table .
lo_interfacecontroller =   wd_this->wd_cpifc_alv_srlocations( ).
DATA lo_value TYPE REF TO cl_salv_wd_config_table.
lo_value = lo_interfacecontroller->get_model(
data lr_column_settings type REF TO if_salv_wd_column_settings.
*data lr_table_settings type ref to if_salv_wd_table_settings.
lr_column_settings ?= lo_value.
*lr_table_settings ?= lo_value.
lr_column_settings->delete_column( 'MANDT' ).

CTI OS Toolkit issue after patching CTI OS 7.5.8

Hi all,
We are setting up the UCCE 7.5.1, and we have patched the system with ICM 7.5.8 and CTI OS
7.5.8. We have also patched the agents' PC with CTI OS 7.5.8.
Our developer has actually customized the CTI OS Toolkit softphone, to intergrate it with
a 3rd party application. It was running fine before patching the agents' PC with CTI OS
7.5.8. The customized CTI OS Toolkit could start up after the agents' PCs were patched.
When I tried to uninstalled CTI OS 7.5.8 from the PCs, then it works fine again. What
could be the problem here? Are there any additional steps that I need to take note after
patching CTI OS 7.5.8?
I also noticed that after running the software patch, the CTI OS Softphone would be
replaced.
Appreciate any help and advice on this.
Thanks & Regards,
Eric

The client patches are meant to be applied to the out of the box software. How is the patch supposed to know how to update your custom software? If you are trying to apply the patch onto a customized desktop then you are overwriting or breaking that customization. Your developer needs to apply the new software release to his custom code and provide a patch for you. The previous release remains backwards compatible so there's no rush.

Startup after patching (9654983) ORA-32004

I patched a nearly identical system before this one with no issues however after patching this one
on attempting to startup I get :
ORA-32004: obsolete or deprecated parameter(s) specified for RDBMS instance.
ORA-24324: service handle not initialized
ORA-24323: value not allowed
ORA-01092: ORACLE instance terminated. Disconnection forced.
What gives?
Thanks for any and all help in advance,
Brian

ORA-32004: obsolete or deprecated parameter(s) specified for RDBMS instance.
ORA-24324: service handle not initialized
ORA-24323: value not allowed
ORA-01092: ORACLE instance terminated. Disconnection forced.
What gives? Check the alert.log to identify the obsolete parameter and remove it.
OR
Check V$OBSOLETE_PARAMETER to see the matching on and remove it.
Then,startup the database.
-Anantha

After patching Portal 7.31 SP9 - SP13, CM BW reports fail

Our links to the BI credit reports (like Early Warning Risk) stopped working after patching the NW Portal 7.31 from SP9 to SP13. No other changes were made, and the reports worked prior to the patching.
The child window for the report opens, but then comes back with error:
com.sap.portal.appintegrator.sap.BWReport::BWReport/AskForReport
And then it asks for a BEx Web Application Query String.
I would put this in the portal/netweaver forum, but this error seems strictly related to the CM delivered content (we are on the most current 1.41 BP). We've validated that that the SSO tickets from portal to back end ERP and BI are working properly. Has anyone had this kind of issue after a patch (while staying on same portal release)? We didn't make any changes/patches to the back end ERP and BI systems either.

Yes we have experienced the same thing. We upgraded from 30 to 353 and now we are getting the BW logon prompt. It is very frustrating. I have been searching these message boards for help.
Brien

Non priviledged commands fail after patch cluster install

For several years, to allow users to access system functions for higher clock resolutions in their
applications, we have made the following mods to two files (per Sun recommendations):
In the /etc/system file, add lines:
* 10 ms clock resolution*
set higher_tick = 1*
In /etc/user_attr, add:
dssuser::::type=normal;defaultpriv=proc_clock_highres,file_link_any,proc_info,proc_session,proc_fork,proc_exec
Everything was fine until I installed the latest patch cluster (from 2-14-2011) on our Netra 210. No issues installing the cluster. Upon reboot, the dssuser cannot do some simple things, like use ftp or ping. Messages like this:
ping: unknown host
ftp: socket: Permission denied.
The root user has no problems using any of these commands. As soon as I comment out the dssuser line from the /etc/user_attr file, everything works as expected. But we need the highres clock settings for our applications. I am unfamiliar with the workings and intent of the entries in user_attr so any help would be most appreciated.
Mark

The problem is that after patch implementation, the special privileges for any user defined in the /etc/user_attr file were modified to append the string "!net_privaddr" specifically denying use of common commands ping and ftp for example. The output of ppriv:
$ ppriv $$
14870: -sh
flags = <none>
E: basic,proc_clock_highres,!net_privaddr
I: basic,proc_clock_highres,!net_privaddr
P: basic,proc_clock_highres,!net_privaddr
L: all
I had to add the keyword net_privaddr in the user_attr file like:
dssuser::::type=normal;defaultpriv=proc_clock_highres,file_link_any,proc_info,proc_session,proc_fork,proc_exec,net_privaddr
to get past this problem. A bug or what?

Smc fails after patching

Good evening
Running a freshly installed 11/06 build of solaris 10 x86, I don't have any issues with smc. Immediately after patching, installing all recommended patches, smc so longer starts up.
bash-3.00# smc
Warning: Cannot convert string "-monotype-arial-regular-r-normal--*-140-*-*-p-*-iso8859-1" to type FontStruct
Warning: Unable to load any usable ISO8859-1 font
Warning:
Name: FONTLIST_DEFAULT_TAG_STRING
Class: XmRendition
Conversion failed. Cannot load font.
Java Accessibility Bridge for GNOME loaded.
java.lang.InternalError: java/langNullPointerException
at sun.awt.motif.MComponentPeer.pSetFont(Native Method)
at sun.awt.motif.MComponentPeer.setFont(MComponentPeer.java:247)
at sun.awt.motif.MWindowPeer.init(MWindowPeer.java:116)
at sun.awt.motif.MFramePeer.<init>(MFramePeer.java:58)
at sun.awt.motif.MToolkit.createFrame(MToolkit.java:231)
at java.awt.Frame.addNotify(Frame.java:491)
at java.awt.Window.addNotify(Window.java:462)
at java.awt.Window.show(Window.java:514)
at com.sun.management.viper.console.gui.VSplashScreen.show(VSplashScreen.java:166)
at com.sun.management.viperimpl.console.BaseConsoleOptionsManager.openConsole(BaseConsoleOptionsManager.java:746)
at com.sun.management.viperimpl.console.BaseConsoleOptionsManager.redirectToConsole(BaseConsoleOptionsManager.java:648)
at com.sun.management.viperimpl.console.BaseConsoleOptionsManager.launchConsole(BaseConsoleOptionsManager.java:173)
at com.sun.management.viperimpl.console.BaseConsoleOptionsManager.main(BaseConsoleOptionsManager.java:861)
I'm guessing that something got horked up during patching, however, I'm not really sure which one(s) might have done so. Anyone have any ideas?
-Matt

I'm more familiar with the similarly-named Sun Management Center, but I think this may be a Java compatibility issue: possibly the patched version requires a later version of java. It would help to know which version's in your environment (java -version).

How to solve problem After patch 10.2.0.4 applying on owb 10.2.0.1

HI OWB Gurus,
We have recently a patchapplied for oracle 10g .
prev version was oracle 10 g r2 10.2.0.1
new version is 10.2.0.4 ( patchset 4)
After patch applied at database and owb level there are some problem we are facing like
ETL process is very slow , cpu is going to 100% after start any mapping.
and audit browser are not opening.
Can any one help me on this so that we can resolve the problem.
- Umesh

Hi Umesh,
This might help you in diagnosing the client's performance
Accurate optimizer statistics are generally very important. They are gathered automatically at OWB install time and the Design Center -> Tools -> Optimize Repository menu selection is available to refresh them on an as needed basis.
The DBA can always help by pre-expanding tablespaces, making sure multiple tablespaces are available on separate disks or disk arrays so that I/O to indexes, metadata tables, snapshot tables, DB undo and redo logs, etc., can be evenly distributed.
With more complex metadata in this OWB release, you can expect many JDBC round-trips to the DB. Network latency can have a big impact on performance. To see how much time the owbclient uses for JDBC roundtrips to the DB, add the following line to Preference.properties in <owb home>/owb/bin/admin on your client machine:ClientProfile=true
Run OWB, then check ClientProfile.log in the admin directory. Keep in mind that a ping to localhost is probably about 0.025 ms, to another machine in the LAN about 0.25 ms. If the roundtrips are greater than 40 ms, then the issue is likely related network latency.
The two basic workarounds for network latency are:
-Remote control an OWB client machine that is physically close to the server.
-Do design-time work on a local repository, then MDL export the work for import to a central repository.
If the client and server are not on the same (high bandwidth) LAN, then total available bandwidth may become a factor. Same thing if the DB server is heavily loaded with respect to CPU or I/O, or if all your OWB design-time metadata is located on the same tablespace on the same hard drive. Distributing projects across multiple repositories which use their own
tablespaces spread across multiple hard drives would be very desirable.
The object editors are more functional and complex, as such, the required processing power to render them is greater (processor > 2GHz) Also note the OWB client software is mostly single-threaded, so it won't take advantage of multiple processors on one machine.
Long running sessions or large bulk operations (MDL import, validation, generation, deployment over large or multiple modules) can push up against the JVM memory limit. If performance begins to suffer due to memory, either:
a)exit and restart the OWB session;
b) if adequate physical memory exists, increase the -Xmx and -Dlimit values in the owbclient and OMBPlus startup scripts to better accommodate large operations.
ie.
If you have 2 GB or more, backup and edit owb\bin\win32\owbclient.bat file and modify line starting with %JAVAPATH
ie.
%JAVAPATH%\jre\bin\java -Xms128M -Xmx1024M -Dlimit=1024M -XX:MaxPermSize=1024M
This will add more memory to JVM for OWB client. Do the same for owb.cl file
Hope this will add some value.
Best Regards,
Prasad Bolla.

Ciscowork 3.2.1 daemon manager is not working after patch installation

Hi Team
Ciscowork 3.2.1 daemon manager is not working after patch installation.
C:\Documents and Settings\Administrator>net start crmdmgtd
The CiscoWorks Daemon Manager service is starting.
The CiscoWorks Daemon Manager service could not be started.
The service did not report an error.
More help is available by typing NET HELPMSG 3534.
Also I checked syslog.log and it is showing below error
an 17 14:39:34 127.0.0.1 100: <28> dmgt[1316]: 2507(W):Daemon manager anonymous user has not been set up: 00000569
Please suggest.
With Regards,
neena

During installation, an user casuser is created with certian security settings and if those are modified\removed, DM will not start.
Following message will be seen in /log/syslog.log
Daemon manager anonymous user has not been set up: 00000775
To solve the issue, run resetcasuser.exe located under /setup.support to recreate the settings.
Make sure casuser account is not locked out. Make sure casuser is a member of casusers group and is set to "password never expires".
Additionally you can try to make casuser a member of adiministrators group.
-Thanks

Problems after patch abap/java sp04 to sp07 and cimmodel/cr data on PI7.1

hello friends,
after patch abap/java stack aan update cim model and cr content 3.00 to 4.xx, i have the following error by url:
http://<hostname:50000>/dir
error:
Internal Error
Internal error; contact your system administrator
Internal error: Unable to start component DIRECTORY_SERVER. Specified StartupCodeEntry class "com.sap.aii.ibdir.server.applcomp.StartupCodeEntry" does not exist
i have manually added the parameter in exchangeprofle, but what is the right value? is this the right way?
Thanks,
christoph

Guys,
Any success????
I am working on PI 7.1. I m also facing same issue..... when I tried to upgrade SAP-XICONS and SAP_XIPCK component from SP 4.0 to 7.0.
In my case the SLD, RWB and NWA is working... but I am not able to access
http://pidev:50000/dir/start/index.jsp.
The error says:
Internal error: Unable to start component DIRECTORY_SERVER. Specified StartupCodeEntry class "com.sap.aii.ibdir.server.applcomp.StartupCodeEntry" does not exist
deatiled error ************************
Stacktrace
Thrown:
com.sap.aii.ib.core.applcomp.StartupException: Internal error: Unable to start component DIRECTORY_SERVER. Specified StartupCodeEntry class "com.sap.aii.ibdir.server.applcomp.StartupCodeEntry" does not exist
     at com.sap.aii.ib.core.applcomp.StartupException.newEntryClassNotFound(StartupException.java:78)
     at com.sap.aii.ib.core.applcomp.ExplicitApplicationComponentImpl.startup(ExplicitApplicationComponentImpl.java:101)
     at com.sap.aii.ib.core.applcomp.ExplicitApplicationComponents.startup(ExplicitApplicationComponents.java:438)
     at com.sap.aii.ib.core.applcomp.ApplicationComponent.startup(ApplicationComponent.java:203)
     at JEE_jsp_start_index_6931850_1232360340765_1232372432437._jspService(JEE_jsp_start_index_6931850_1232360340765_1232372432437.java:122)
     at com.sap.engine.services.servlets_jsp.lib.jspruntime.JspBase.service(JspBase.java:102)
     at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:66)
     at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:433)
     at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:240)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
     at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:66)
     at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:32)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:431)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:289)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:376)
     at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:85)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
     at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:160)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
     at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:67)
     at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
     at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
     at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
     at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
     at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
     at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
     at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
     at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:295)
     at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.run(Processor.java:222)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:152)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:247)
Initial Startup Exception
Internal error: Unable to start component DIRECTORY_SERVER. Specified StartupCodeEntry class "com.sap.aii.ibdir.server.applcomp.StartupCodeEntry" does not exist
Thrown:
com.sap.aii.ib.core.applcomp.StartupException: Internal error: Unable to start component DIRECTORY_SERVER. Specified StartupCodeEntry class "com.sap.aii.ibdir.server.applcomp.StartupCodeEntry" does not exist
     at com.sap.aii.ib.core.applcomp.StartupException.newEntryClassNotFound(StartupException.java:78)
     at com.sap.aii.ib.core.applcomp.ExplicitApplicationComponentImpl.startup(ExplicitApplicationComponentImpl.java:101)
     at com.sap.aii.ib.core.applcomp.ExplicitApplicationComponents.startup(ExplicitApplicationComponents.java:438)
     at com.sap.aii.ib.core.applcomp.ApplicationComponent.startup(ApplicationComponent.java:203)
     at com.sap.aii.ibdir.server.cache.monitoring.CacheMonitorServlet.startup(CacheMonitorServlet.java:104)
     at com.sap.aii.ibdir.server.cache.monitoring.CacheMonitorServlet.init(CacheMonitorServlet.java:45)
     at javax.servlet.GenericServlet.init(GenericServlet.java:241)
     at com.sap.engine.services.servlets_jsp.server.security.PrivilegedActionImpl.run(PrivilegedActionImpl.java:97)
     at java.security.AccessController.doPrivileged(Native Method)
     at javax.security.auth.Subject.doAs(Subject.java:396)
     at com.sap.engine.services.servlets_jsp.server.application.WebComponents.addServlet(WebComponents.java:341)
     at com.sap.engine.services.servlets_jsp.server.deploy.ApplicationThreadInitializer.loadServlets(ApplicationThreadInitializer.java:849)
     at com.sap.engine.services.servlets_jsp.server.deploy.ApplicationThreadInitializer.run(ApplicationThreadInitializer.java:219)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:152)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:247)
Regards,
Siddhesh S.Tawate

Requested delivery date becomes empty after Patching CRM

Hi Experts,
We are using CRM 4.0 with ISA 4.0.
We recently have patched our SAP systems with latest patches. CRM (BBP CRM 4.) system has been patched from SAPKU40009 to SAPKU40016.
We do not Patch ISA. We have upgraded only CRM system.
But after Patching, We are facing issue with Requested devliery date in Shopping basket of ISA.
Issue Scenario :
step 1 : Create shopping basket.
It initializes the shopping basket and requested delivery date is set to default date as per logic.
Step 2 : Go to Product catalaog.
Stetp 3 : Choose any product and and transfer it into shopping basket.
Step 4 : Come back to shopping basket.
Now Requested delivery date becomes empty and again requested delivery date set to current date .
Can any one help me to solve this issue?
Regards,
Murugan Arumugam.

Issue solved.

Error after patch EP6.0 SP3- EP6.0 SP4(patch4)- WAS6.40SP6

We have WAS 6.40 SP 6.0 and EP 6.0 SP3 on HP-Unix 11i 64-bit.
I have tried to patch the portal twice to SP4 and after patching I got
twice the same problem.
The patch application - the exact patch is EP 6.0 SP4 Patch4 is
successful. There are no errors in the installation logs, etc.
But when I try to login to the portal url I get this error message:
Portal Runtime Error
An exception occurred while processing a request for :
iView : N/A
Component Name : N/A
Could not find portal application com.sap.portal.ivs.api_iview.
Exception id: 02:21_05/08/04_0001_1516650
See the details for the exception ID in the log file
The error part of the portal log file is attached. The WAS is running
perfectly, no other errors or issues. The heap memory is set as per the
OSS 723909. I wonder if I have to add the 32-bit compatible UNIX shared
memory parameter settings as per OSS 497427, but I do not think it is
related the issue.
Please, advise.
Vladimir
Portal Log:
Aug 5, 2004 2:18:19 PM # SAPEngine_Applica... Info Loading
application com.sap.portal.yahoo #
Aug 5, 2004 2:18:19 PM # SAPEngine_Applica... Fatal Operation
failed - application: com.sap.portal.ivs.iviewservice
com.sapportals.portal.prt.runtime.PortalRuntimeException:
[PortalApplicationItem.__prepareClassLoaderAndDependencies]:
com.sap.portal.ivs.iviewservice
at
com.sapportals.portal.prt.core.broker.PortalApplicationItem.__prepareCla
ssLoaderAndDependencies(PortalApplicationItem.java:361)
at
com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare
(PortalApplicationItem.java:207)
at
com.sapportals.portal.prt.core.broker.PortalApplicationItem.getCoreLoade
r(PortalApplicationItem.java:276)
at
com.sapportals.portal.prt.core.broker.PortalApplicationItem.__initJNDISu
pport(PortalApplicationItem.java:1780)
at
com.sapportals.portal.prt.core.broker.PortalApplicationItem.__initJNDISu
pport(PortalApplicationItem.java:1746)
at
com.sapportals.portal.prt.core.broker.PortalApplicationItem.initJNDISupp
ort(PortalApplicationItem.java:1730)
at
com.sapportals.portal.prt.core.broker.PortalAppBroker.preparePortalAppli
cations(PortalAppBroker.java:1306)
at com.sapportals.portal.prt.core.broker.PortalAppBroker.start
(PortalAppBroker.java:1429)
at
com.sapportals.portal.prt.core.broker.PortalAppBroker.startNonCoreApplic
ations(PortalAppBroker.java:1389)
at com.sapportals.portal.prt.runtime.Portal.init
(Portal.java:359)
at
com.sapportals.portal.prt.core.PortalCoreInitializer.coreInit
(PortalCoreInitializer.java:54)
at
com.sapportals.portal.prt.dispatcher.PortalInitializer.<init>
(PortalInitializer.java:129)
at
com.sapportals.portal.prt.dispatcher.Dispatcher$doSetupPortalInitializer
.run(Dispatcher.java:156)
at java.security.AccessController.doPrivileged(Native Method)
at
com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher
(Dispatcher.java:354)
at com.sapportals.portal.prt.dispatcher.Dispatcher.access$000
(Dispatcher.java:40)
at
com.sapportals.portal.prt.dispatcher.Dispatcher$InitRunner.run
(Dispatcher.java:109)
at com.sapportals.portal.prt.dispatcher.Dispatcher.init
(Dispatcher.java:387)
at
com.sap.engine.services.servlets_jsp.server.runtime.context.WebComponent
s.addServlet(WebComponents.java:130)
at
com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadI
nitializer.loadServlets(ApplicationThreadInitializer.java:376)
at
com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadI
nitializer.run(ApplicationThreadInitializer.java:110)
at com.sap.engine.core.thread.impl3.ActionObject.run
(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute
(SingleThread.java:94)
at com.sap.engine.core.thread.impl3.SingleThread.run
(SingleThread.java:144)
Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException:
[PortalApplicationItem.__prepareClassLoaderAndDependencies]:
com.sap.portal.ivs.api_iview
at
com.sapportals.portal.prt.core.broker.PortalApplicationItem.__prepareCla
ssLoaderAndDependencies(PortalApplicationItem.java:361)
at
com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare
(PortalApplicationItem.java:207)
at
com.sapportals.portal.prt.core.broker.PortalApplicationItem.__prepareCla
ssLoaderAndDependencies(PortalApplicationItem.java:352)
... 24 more
Caused by:
com.sapportals.portal.prt.core.broker.PortalApplicationNotFoundException
: Could not find portal application com.sap.portal.ivs.api_iview
at
com.sapportals.portal.prt.core.broker.PortalApplicationItem.refresh
(PortalApplicationItem.java:1093)
at
com.sapportals.portal.prt.core.broker.PortalApplicationItem.__prepareCla
ssLoaderAndDependencies(PortalApplicationItem.java:326)
... 26 more
Follow errors of other applications like
com.sap.portal.ivs.systemlandscapeservice, which are probably dependent
on the com.sap.portal.ivs.iviewservice.

We needed exactly the SP Stack 3 specification - WAS 6.40 SP6 and EP 6.0 SP4, so I could not go to higher SP on both WAS and EP.
I resolved the issue by applying all EP6.0 SP4 patches sequentially. SAP claims that these patches are cumulative and you can directly install the latest available patch, but it did not work in our case.
I was suspicious at the beginning, because the files size of the first patch is much bigger that patch 4, but the installation did not complained:
08/03/2004 06:13p 32,672,495 EP6PORTAL04P_4-20000394.SAR
08/03/2004 06:03p 50,455,982 EP6PORTAL04_0-20000394.SAR
Regards,
Vladimir

OracleCSService unable to start on win2003 node after patching to 10.2.0.4

Hi,
Anyone facing problem starting the CS service after patching to 10.2.0.4 on 1 win2003 node while other win2003 node works fine?
Well seems I found the solution to it. Pl read on if u r facing same problem:
1. on the non-working node goto the log folders inside "$ORACLE_HOME/log/<node1name>/css/cssdout.log"
2. if u see any errors like ssmain_run_css going into looping then
3. from cmd run "crsctl check boot"
4. check any dll error reporting...(in my case it was orahasgen10.dll)
5. compare this dll size/date with the one on working node.
6. If its different copy same dll from workingnode to non-working node.
7. try restart oraclecsservice. It should start now.
Hope this helps. I spent a lot of time researching this so hope someone benefits from this.
Rgds,
Mounesh.

Just wanted to help techies out there if facing cs service issue.

Import/Export problems after patching oracle from 9.2.0.1 to 9.2.0.5

Hi, After I applied the 5 patch to oracle 9201 on Win XP the export utility has started to complain about
EXP-00008: ORACLE error 942 encountered
ORA-00942: table or view does not exist
EXP-00024: Export views not installed, please notify your DBA
EXP-00000: Export terminated unsuccessfully
And after I applied catexp.sql script, it didn't fix the issue with export, the error message has become like this:
EXP-00056: ORACLE error 31600 encountered
ORA-31600: invalid input value EMIT_SCHEMA for parameter NAME in function SET_TRANSFORM_PARAM
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 105
ORA-06512: at "SYS.DBMS_METADATA_INT", line 3926
ORA-06512: at "SYS.DBMS_METADATA_INT", line 4050
ORA-06512: at "SYS.DBMS_METADATA", line 836
ORA-06512: at line 1
EXP-00000: Export terminated unsuccessfully
Can someone advise, what's wrong with it? With oracle 9.2.0.1 export worked fine, after upgrade to 9.2.0.5 it fails every time it gets to the table data export stage.
Thanks in advise

It seems that you have found an answer in other forum :
Imp/Exp problems after patching oracle to 9205
Nicolas.

Null Exception in Family Iview after Patch Upgrade

Hello
We have SAP XSS installed on our production portal.
following was the composition.
SAP_ESS 603 SP3
SAP_MSS 600 SP16
SAPPCUI_GP 603 SP3
recently we upgraded patch level to
SAP_ESS 603 SP7 (1000.603.0.7.4.20110124060804)
SAP_MSS 600 SP18 (1000.600.0.18.0.20100830054638)
SAPPCUI_GP 603 SP7 (1000.603.0.7.0.20100914080506)
as per the link [https://wiki.sdn.sap.com/wiki/display/ERPHCM/HOWTOGETRIDOFSPSTACKMISMATCHISSUES] and SAP note 1521297
Backend patches remain the same viz
EA-HR Release: 604 ,level : 011
Now when we try to test the Personal Information Iview it gives us the following error
com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException: Access via NULL object reference not possible., error key: RFC_ERROR_SYSTEM_FAILURE
Note: We have already implemented note no 1018036 which reports the above issue.Jcos are working fine , SSo is properly established and User remains valid.
Thanks
Surender Dahiya

Hi,
The logs from ST22 as as follows:
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_REF_IS_INITIAL', was not
caught in
procedure "HRXSS_PER_CLEANUP" "(FUNCTION)", nor was it propagated by a RAISING
clause.
Since the caller of the procedure could not have anticipated that the
exception would occur, the current program is terminated.
The reason for the exception is:
You attempted to use a 'NULL' object reference (points to 'nothing')
access a component.
An object reference must point to an object (an instance of a class)
before it can be used to access components.
Either the reference was never set or it was set to 'NULL' using the
CLEAR statement.
Other ESS applications are working fine.Issue is in Family application.Server is also restarted after patch upgradation.
Please suggest.
Thanks,
Surendra

Issues in PI after patching

Similar Messages

Maybe you are looking for