PSA - manual update of incorrect packages possible?

Hello,
I scheduled initialization extraction to data target and PSA in series. Now I saw in monitor that some packages have status "red" or "yellow".
The job is running since three days.
I have following questions:
How to proceed with this incorrect packages? Via PSA -> "Start the update immediately". Here in data target request have to be deleted. That's not an option.
What's about option "Simulate update".
I just want to update after job is finised the incorrect packages again.
Any idea?
Edited by: STARWARS on Dec 3, 2008 9:30 AM

Hi,
Are you getting the option of "manual update" when you right click on the data package??
If your all the packages are loaded succsefully in the PSA??
If yes.... then only they can be updated the individual data packages manually...if not then you will have to start the whole data load again from the PSA.
Just check for the data packages and see if it gives you the option...it will not you give the option for those data packages which are already red...so you may have to do the data loads from PSA again.
But if the data packages are not even in PSA then you may have to start load from the source system.
Thanks
Ajeet

Similar Messages

[Solved] Do I need to manually update my -vcs packages in the AUR?

I've got a few -vcs packages in the AUR (one hg, 3 svn). Do I need to manually update the versions in the AUR as the code changes, or does this happen automatically? I know that makepkg updates the version automatically in the local PKGBUILD, but I want to make sure the people using these packages see the new versions in the AUR.
Last edited by nofrak (2010-11-06 19:03:42)

You need to do it manually.
!next

Reason for Error in Manual Update of Data Package

Hey,
Sometimes while loading huge amount of data, one of the data package doesnt get uploaded. For those data packages we do a manual update of the data package and it works well.
My question is why do we get this error,
Is it to do with the system contention or any IDOC issue?
Please help me out to find the root cause of this, so that we can avoid the manual update of the data packges.

We usually get this issue , when we are doing a lot of processing in the Update Rules. The Data package processing gets timed out.
If it is happening very often then you would need to sit with your Basis person and modify the Timeout settings for your system.

Is it possible to un-suppress updates in AAMEE packages?

Hi,
After creating a Creative Suite CS5.5/6 package with AAMEE (updates suppressed in options), is it possible to un-suppress updates once the package is deployed to the machines by editing a .plist file or similar (Macs in this case)?
Many thanks!

Hi,
Yes this is possible. I am not sure why you created the packages with updates turned off, I assume it suited at the time, the reason I bring this up is. By using the Enterprise IT Tool RUM (Remote Update Manager) you could continue to keep updates turned off so the client doesn't manually try and bring them in but instead only does so when you send a command to the clients. The command would be issued to clients through a 3rd party deployment tool like SCCM, Casper, Alteris. This way they are installed as admin and only on your designated schdule. This might not be appealing but I wanted to make you aware of it. The Enterprise Deployment guide will give you more information about the overide file required to change the update options and RUM can be found in Adobe Labs http://labs-staging.macromedia.com/technologies/aameetools/
Cheers
Karl

Loads using DTP - manual update possible?

Hi,
I have a question regarding loads done using DTP in BW 7.0.
In 3.X loads using infopackages, sometimes a data package will get runtime errors such as DBIF_RSQL_SQL_ERROR (deadlocks). Usually, we would change the status to red and do a manual update of the affected data package in the data load monitor.
However, I cannot find this option for DTP and I have to reload the whole request even only 1 data package has failed because of the SQL error. Does anyone know how to repair this in a DTP load?
Any help will be appreciated, thanks in advance!

Hi CK,
Not found a way of doing this at current but I know where you are coming from, you're thinking of the old set manual status or even try a sm58 and trigger the idocs. If a DTP fails you might have the option of using the error stack but only if this has been configured. A failed load will prompt you to do this. Other ways of trying to fix the SQL errors are to check what the SQL problems are, most of our problems have been tablespace issues, etc.
Daily monitoring by basis/bw admin should sort these.
Cheers,
Pom

Guide me for any way to avoid manual update for processing data package

Hi sap gurus,
I am new to SAP BI. In my project everyday I have to manually update for processing data packets for an infocube. Can you tell me why it happens that some time data get stuck and we have to do manual update? Is there any possible solution to avoid or correct that? Can we make some kind of Process chains that automatically do these things?
Please reply..as it is very irritating to do same thing everyday..
-Thanks in advance.

We have program RSARFCEX, which can execute all of them in one go.
But you can not schedule it in process chain, as you will never know when TRFC will struck. So it will execute without anything if there is no TRFC struck.
Pravender

Updating license data not possible [Maintenance Package]

Hi,
I want to activate Automatic Maintenance Certificate Renewal via solution manager system as per SNOTE: 1280660.
SOL MAN: ST400 SP 18
SCM : ST-PI 2008_1_700 SP 01
when i run Maintenance package in my managed (satellite) system i got the log as below.
Updating license data not possible [Maintenance Package]
No active master Solution Manager destination maintained. [Maintenance Package]
Updating license data completed from destination [Maintenance Package]
Maintenance Package completed
when i run Maintenance package in my Solution Manager system i got the log as below.
Refresh sessions from destination SM_KSMCLNT000_BACK started [Maintenance Package]
> error reading function module interface DSWP_API_SESSIONLIST_GET from SM_KSMCLNT000_BACK
> Logon not possible (error in license check)
> Sessions cannot be refreshed from destination SM_KSMCLNT000_BACK ( KSM , 0020472195 )
Refresh sessions from destination SM_KSMCLNT000_BACK finished [Maintenance Package]
Refresh sessions from destination SM_KSMCLNT001_BACK started [Maintenance Package]
> error reading function module interface DSWP_API_SESSIONLIST_GET from SM_KSMCLNT001_BACK
> Logon not possible (error in license check)
> Sessions cannot be refreshed from destination SM_KSMCLNT001_BACK ( KSM , 0020472195 )
Please anyone facing the same or related issue, give me a suggestion..
Thanks,
Manikandan B

Hello Manikandan
The error indicates that there is an issue with the *_back RFC destination
itself.
Have you done an authorisation check within SM59?
Utilities > Authorisation check?
You can also do so by testing the connection in SDCCN.
Goto > Taskspecific settings > RFC destination > Backdestination
This problem is often caused by the user in the RFC connection
being locked in the Solution Manager.
Make sure the RFC user account is a communication user so the password does not expire. Sometimes the password expires and the RFC user locks the account as the old expired password is provided too many times.
The message also indicated "No active master Solution Manager destination maintained"
Please make sure the relevent Solution Manager system has been marked as Master in SDCCN Goto > Taskspecific settings > RFC destination >
These are things you will want to check.
I hope this information helps you resolve this problem.
Regards,
Paul

Delta update in Info package

Hai all
what is the us of delta update in info package
I had intially loaded data from R/3 to psa using
(INFO PACKAGE->UPDATE-->Initilize delta process)
Then I had created to more records in r/3 side .
this time I scheduled using DELTA UPDATE I am getting 0 records
then what is the use of delta update
How can I get only delta records with out use of selection condition in DATA SELECTION of INFO PACKAGE
thanks
chaithanya

Hi,
You must specify "1" (day) in the lower limit of the delta maintenance.
I could not post my previous reply so here a new try :
Hi Chaithanya,
Let me explain how the generic delta mechanism with "date"-field works on the R/3 side:
When doing a delta extraction, the current date is stored in table ROOSGENDLT or ROOSGENDLM (anyway not so important).
This date will serve as a "from" date for the next delta extraction, though excluding the current value.
This in order to prevent duplicate records to be extracted during a second delta run on the same day.
Without extra settings, it will thus not be possible to extract two different delta's on date the same day.
Solution :
1. If you do not care about duplicate data (e.g. only field assignments with overwrite functionality in the transformation) goto RSO2 in change mode for your extractor and go into the generic delta maintenance screen. In the settings, enter "1" as safety interval lower limit. Like this, the delta processing mechanism will always subtract 1 day from the day stored as 'low-value'.
In your example this means that the initialisation will transfer 4 records, the delta will transfer 6 (although only 2 were added).
2. Use timestamps to determine delta (timestamp should be updated on savetime of record)
I hope this helps.
regards,
Olav

Process Chain : Read PSA and Update Data Target in BI 7.0

Hello Experts,
In my Process Chain I have a variant Execute Infopackage to load the data only into PSA. then I have next variant as *Read PSA and Update Data Target*. my data target was a Master Data table Hierarchy
In the variant " Read PSA and Update Data Target". the selection Parameters were
PSA.Table : 0GLACCEXT_T011_HIER_BA1
Selection Object Type : same Infopackage in Varaint Execute Infopackage
the Error message was Variant doesnot contain a valid combination request/data target
I checked the PSA-Table using RSA1OLD Transaction then I find four PSA Tables:
0GLACCEXT_T011_HIER_BA1
0GLACCEXT_T011_HIER_BA2
0GLACCEXT_T011_HIER_BA3
0GLACCEXT_T011_HIER_BA4
All the requests are linked to PSA Table *0GLACCEXT_T011_HIER_BA4*.
I can't understand why there exists four PSA Tables?
I try to link the PSA-table 0GLACCEXT_T011_HIER_BA4 in the variant *Read PSA and Update Data Target and try to save it it raises short dump.
If I select 0GLACCEXT_T011_HIER_BA1 in the varaint I shouldn't face any problems.?
but the process chain raises an Error message Variant doesnot contain a valid combination request/data target with this variant.
How shall I handle this issue?
Please carify me the issues as soon as possible.
thanks in advance
Regards
sailekha

Hello,
In the Variant Read PSA and Update Data Target I have to select the PSA Tabelle Name from the preselection list in the System it shows me all the four PSA Tables that I mentioned.
I can select any one of them. So I trieed with all the four PSA Tables in the list but I can selct only the XXXX......BA1 table then only I can save and include it in the PC. If I select the remaining tables BA2, BA3, BA4.........while I try to save the Variant it raises short dump.
I checked the PSA using the Transaction RSA1OLD under PSA...... I find 4 PSA Tables( I don't know whether they are PSA Tables or not but in the Variant it states that they are PSA Tables) in which all the requests are attached to BA4. only.
I observed that ony for Hierarchies I find four PSA tables for remaining one only one PSA table was available.
I totally confused how to handle this situation. any suggestions......... please help me to resolve this problem.
Thanks & Regards

Go from manually update to auto-update without losing songs?

I was trying to delete some podcasts from my ipod, and was following the directions on the help menu which told me to go to preferences and choose manual update, then delete. I tried it, and it didn't work. When I decided to go back to auto update, I received a message that everything on my ipod would be deleted and the update would be just what is on the itunes on that machine. I have more than one computer, and have itunes on each one. There are different songs on each computer. If I go to manually update on this computer, it will erase the songs I've put on from other computers. All this and I still have the unwanted podcasts. Can anyone help me to go back to auto-update without losing songs? If worse comes to worst I guess I'll have to update, lose the songs, and then re-update at my other computers. thanks.

Afraid that's not possible. If you go to auto-update, the iPod gets cleared and replaced with the current contents of the iTunes library.

SQL Developer 1.5 disable manual updates

We are creating an SMS package to push this out to the client desktops since we are trying to wean ourselves off of TOAD.
We don't want users doing any updates to the client via the manual check updates.
There is a check box for disabling auto updates; however, we would also like to disable manual updates.

To completely disable check for updates (remove the UI from the product), you should be able to do:
AddVMOption -Dide.noextensions=oracle.ide.webupdate
You can also customize the installation by removing the jar file oracle.ide.webupdate.jar from the ide/extensions directory, which has the safe effect.
Thanks,
Brian

Java was blocked due to the threat I have followed the update & other options to reenable it ie.manual updates reinstalls yet websites like YouTube still wont load up.Works fine in Chrome & IE!

Java was blocked due to the threat I have followed the update & other options to reenable it ie.manual updates reinstalls yet websites like YouTube still wont load up.Works fine in Chrome & IE!

Your plugins list in "more system details" shows Next Generation Java Plug-in 1.6.0_31 for Mozilla browsers so Java should not be blocked.
Could you post a link to a webpage where Java isn't working for you? YouTube uses Flash, not Java. Here is a list of Java test pages you can try, to confirm that Java is working, from http://kb.mozillazine.org/Java#Testing_Java
* [http://www.java.com/en/download/help/testvm.jsp Test your Java Virtual Machine (JVM)] at java.com.
* [http://browserspy.dk/java.php Java Information - BrowserSpy.dk]
* [http://javatester.org/ Java Tester] - The test pages at javatester.org will tell you if your web browser is enabled for Java and, if so, the Java version.
* [http://www.pinlady.net/PluginDetect/Java/ Java Plugin Detector]
By the way, I see in your plugins list that you also have the VLC media player Web Plugin 2.0.0 so, it's possible that the VLC plugin is causing a conflict if YouTube or other videos don't work. See [[Video or audio does not play]] (you may need to disable the VLC Media Player plugin in the Add-ons -> Plugins list for some media to play).

Update Java Support Package Stack in JSPM

Hi all,
When i update Java Support Package Stack in JSPM i can't start the dispatcher
[Thr 920] JLaunchIExitJava: exit hook is called (rc = -11113)
[Thr 920] **********************************************************************
ERROR => The Java VM terminated with a non-zero exit code.
Please see SAP Note 943602 , section 'J2EE Engine exit codes'
for additional information and trouble shooting.
[Thr 920] JLaunchCloseProgram: good bye (exitcode = -11113)
When i goto the log-file of the dispatcher (server.0.log):
E:
usr
sap
P01
DVEBMGS01
j2ee
cluster
dispatcher
bin
services
log_configurator
log_configurator.jar
Loading model: {parent,local,references}
The error occurred while trying to load "com.sap.engine.services.log_configurator.LogInterfaceImpl".
     at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:401)
     at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
     at com.sap.engine.services.log_configurator.LogConfiguratorServiceFrameImpl.init(LogConfiguratorServiceFrameImpl.java:156)
     at com.sap.engine.services.log_configurator.LogConfiguratorServiceFrameImpl.start(LogConfiguratorServiceFrameImpl.java:127)
     at com.sap.engine.core.service630.container.ServiceRunner.startCommunicationServiceFrame(ServiceRunner.java:228)
     at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:158)
     at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
     at com.sap.engine.core.thread.impl6.SingleThread.execute(SingleThread.java:82)
     at com.sap.engine.core.thread.impl6.SingleThread.run(SingleThread.java:154)
#1.5 #0050569379EA000A00000004000010880004B40696AFED19#1323840297756#/System/Server##com.sap.engine.core.service630.container.ServiceRunner#######SAPEngine_System_Thread[impl:6]_32##0#0#Error#1#/System/Server#Plain###Core service log_configurator failed. J2EE Engine cannot be started.#
#1.5 #0050569379EA000A00000006000010880004B40696AFF1F0#1323840297756#/System/Server/Critical##com.sap.engine.core.Framework#######SAPEngine_System_Thread[impl:6]_32##0#0#Fatal#1#com.sap.engine.core.Framework#Plain###Critical shutdown was invoked. Reason is: Core service log_configurator failed. J2EE Engine cannot be started.#
Somebody know how to solve this problem?
Thanks in advance,
Cheung

defaulttrc.0.trc"
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[1.5.3.7185 - 630]/>
<!NAME[./log/defaultTrace.trc]/>
<!PATTERN[defaultTrace.trc]/>
<!FORMATTER[com.sap.tc.logging.ListFormatter]/>
<!ENCODING[UTF8]/>
<!FILESET[0, 2, 10485760]/>
<!PREVIOUSFILE[defaultTrace.1.trc]/>
<!NEXTFILE[defaultTrace.1.trc]/>
<!LOGHEADER[END]/>
#1.5 #0050569379EA001500000D53000016300004B40029F81C09#1323812703907#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###com.sapportals.portal.prt.runtime.PortalRuntimeException: [ApplicationItem.release]: SAPJ2EE::sap.com/tcwd4vccorestdinfoactors#
#1.5 #0050569379EA001500000D54000016300004B40029F8209A#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.core.broker.ApplicationItem.release(ApplicationItem.java:506)#
#1.5 #0050569379EA001500000D55000016300004B40029F82100#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.core.broker.PortalAppBroker.releaseAllItems(PortalAppBroker.java:590)#
#1.5 #0050569379EA001500000D56000016300004B40029F82147#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.core.broker.PortalAppBroker.shutdown(PortalAppBroker.java:672)#
#1.5 #0050569379EA001500000D57000016300004B40029F8218D#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.runtime.Portal.shutdown(Portal.java:725)#
#1.5 #0050569379EA001500000D58000016300004B40029F821D1#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.core.PortalCoreInitializer.shutdown(PortalCoreInitializer.java:111)#
#1.5 #0050569379EA001500000D59000016300004B40029F82215#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.dispatcher.PortalInitializer.shutdown(PortalInitializer.java:164)#
#1.5 #0050569379EA001500000D5A000016300004B40029F8225A#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.dispatcher.Dispatcher.destroy(Dispatcher.java:651)#
#1.5 #0050569379EA001500000D5B000016300004B40029F8229E#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sap.engine.services.servlets_jsp.server.runtime.context.WebComponents.destroyServlets(WebComponents.java:722)#
#1.5 #0050569379EA001500000D5C000016300004B40029F822E4#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadDestroyer.run(ApplicationThreadDestroyer.java:62)#
#1.5 #0050569379EA001500000D5D000016300004B40029F82329#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)#
#1.5 #0050569379EA001500000D5E000016300004B40029F8236C#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at java.security.AccessController.doPrivileged(Native Method)#
#1.5 #0050569379EA001500000D5F000016300004B40029F823AF#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)#
#1.5 #0050569379EA001500000D60000016300004B40029F823F3#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)#
#1.5 #0050569379EA001500000D61000016300004B40029F826A8#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception during stop of application: SAPJ2EE::sap.com/tcwd4vccorestdinfoactors#
#1.5 #0050569379EA001500000D62000016300004B40029F82700#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.core.broker.SAPJ2EEApplicationItem.releaseResources(SAPJ2EEApplicationItem.java:162)#
#1.5 #0050569379EA001500000D63000016300004B40029F82747#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.core.broker.ApplicationItem.release(ApplicationItem.java:479)#
#1.5 #0050569379EA001500000D64000016300004B40029F8278A#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     ... 12 more#
#1.5 #0050569379EA001500000D65000016300004B40029F82AA4#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###Caused by: java.lang.NullPointerException#
#1.5 #0050569379EA001500000D66000016300004B40029F82AF6#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sap.portal.prt.sapj2ee.SAPJ2EEPortalRuntime.getSAPJ2EEApplicationState(SAPJ2EEPortalRuntime.java:630)#
#1.5 #0050569379EA001500000D67000016300004B40029F82B41#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.service.sapj2ee.Mediator.getSAPJ2EEApplicationState(Mediator.java:216)#
#1.5 #0050569379EA001500000D68000016300004B40029F82B87#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.core.broker.SAPJ2EEApplicationItem.releaseResources(SAPJ2EEApplicationItem.java:121)#
#1.5 #0050569379EA001500000D69000016300004B40029F82BCB#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     ... 13 more#
#1.5 #0050569379EA001500000D6A000016300004B40029F82D15#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###com.sapportals.portal.prt.runtime.PortalRuntimeException: [ApplicationItem.release]: SAPJ2EE::sap.com/com.sapportals.connectors.sap#
#1.5 #0050569379EA001500000D6B000016300004B40029F82FE9#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.core.broker.ApplicationItem.release(ApplicationItem.java:506)#
#1.5 #0050569379EA001500000D6C000016300004B40029F8303F#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.core.broker.PortalAppBroker.releaseAllItems(PortalAppBroker.java:590)#
#1.5 #0050569379EA001500000D6D000016300004B40029F83085#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.core.broker.PortalAppBroker.shutdown(PortalAppBroker.java:672)#
#1.5 #0050569379EA001500000D6E000016300004B40029F830E5#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.runtime.Portal.shutdown(Portal.java:725)#
#1.5 #0050569379EA001500000D6F000016300004B40029F8312A#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.core.PortalCoreInitializer.shutdown(PortalCoreInitializer.java:111)#
#1.5 #0050569379EA001500000D70000016300004B40029F8316F#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.dispatcher.PortalInitializer.shutdown(PortalInitializer.java:164)#
#1.5 #0050569379EA001500000D71000016300004B40029F831B4#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.dispatcher.Dispatcher.destroy(Dispatcher.java:651)#
#1.5 #0050569379EA001500000D72000016300004B40029F831F8#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sap.engine.services.servlets_jsp.server.runtime.context.WebComponents.destroyServlets(WebComponents.java:722)#
#1.5 #0050569379EA001500000D73000016300004B40029F8323E#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadDestroyer.run(ApplicationThreadDestroyer.java:62)#
#1.5 #0050569379EA001500000D74000016300004B40029F83283#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)#
#1.5 #0050569379EA001500000D75000016300004B40029F832C9#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at java.security.AccessController.doPrivileged(Native Method)#
#1.5 #0050569379EA001500000D76000016300004B40029F8330C#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)#
#1.5 #0050569379EA001500000D77000016300004B40029F83350#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)#
#1.5 #0050569379EA001500000D78000016300004B40029F835C4#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception during stop of application: SAPJ2EE::sap.com/com.sapportals.connectors.sap#
#1.5 #0050569379EA001500000D79000016300004B40029F8361A#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.core.broker.SAPJ2EEApplicationItem.releaseResources(SAPJ2EEApplicationItem.java:162)#
#1.5 #0050569379EA001500000D7A000016300004B40029F83662#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.core.broker.ApplicationItem.release(ApplicationItem.java:479)#
#1.5 #0050569379EA001500000D7B000016300004B40029F836AA#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     ... 12 more#
#1.5 #0050569379EA001500000D7C000016300004B40029F83A09#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###Caused by: java.lang.NullPointerException#
#1.5 #0050569379EA001500000D7D000016300004B40029F83A67#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sap.portal.prt.sapj2ee.SAPJ2EEPortalRuntime.getSAPJ2EEApplicationState(SAPJ2EEPortalRuntime.java:630)#
#1.5 #0050569379EA001500000D7E000016300004B40029F83AAF#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.service.sapj2ee.Mediator.getSAPJ2EEApplicationState(Mediator.java:216)#
#1.5 #0050569379EA001500000D7F000016300004B40029F83AF5#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.core.broker.SAPJ2EEApplicationItem.releaseResources(SAPJ2EEApplicationItem.java:121)#
#1.5 #0050569379EA001500000D80000016300004B40029F83B3A#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     ... 13 more#

TS3989 how do I manually update my photos on my Apple Tv with photo stream?

how do I manually update my photos on my Apple Tv with photo stream?

Incorrect. Photos added to the Camera Roll are automatically uploaded to Photo Stream. Photos deleted from the Camera Roll are not automatically deleted from Photo Stream.

Unable to update or install packages in pacaur

Hello All!
I have been using pacaur for a well over a year and have loved it. Yesterday, I started to run into an issue where I was unable to install or update any AUR packages using pacur. I looked online and didn't see anyone who was running into the same issue as I was. I have a gist that shows the output of:
bash -x pacaur -Syu
Does anyone have any suggestions for resolving this issue?
Thanks in advance!

Thank you so much for your help. Spyhawk, I found your previous post here. I tried using the --ignore flag with the chef and ruby-mime-types packages, but that didn't work. I finally went and manually installed the chef aur package and all its dependencies. Still, when I go to update my system with pacaur, it doesn't work. Here is the new output. Any further ideas?

PSA - manual update of incorrect packages possible?

Similar Messages

Maybe you are looking for