Driver update to support S.M.A.R.T. software from Drive Genius/Prosoft

I just purchased software from Drive Genius/Prosoft to maintain and defrag my harddrive. Upon installing I was informed that S.M.A.R.T. is unsuported. Tech support from Drive Genius suggested that my DVD equip is too old. She suggested that I try to download an updated driver. Any advice and suggestions? Thanks. Roger.

I don't understand how your DVD has anything to do
with SMART. S.M.A.R.T. stands for Self-Monitoring
Analysis and Reporting Technology. It is related to
the HD. Your HD might not support SMART. I don't see
how that prevents the software from doing a de-frag
etc.
These pages help explain SMART:
http://www.ariolic.com/activesmart/smart-technology.ht
ml
http://en.wikipedia.org/wiki/Self-Monitoring,_Analysis
,and_ReportingTechnology
TechTool Pro 4.x does support SMART.
MJ
OK, simply, how can I get t he program to run on my computer? Thanks.
Apologies, I am an artist, not a computer expert.
Again, thanks,
Roger

Similar Messages

Problem while updating the Support Package 17 on my SAP WAS SP9

Hi,
I'm facing problem while updating the Support Package 17 on my SAP WAS SP9
ERROR 2006-10-13 10:23:22
FSL-06002 Error 2 (The system cannot find the file specified.
) in execution of a 'CreateProcess' function, line (284), with parameter (java.exe ...).
Please help me in this regard.....
Thanks in advance...
Satya

Hello gentlemen, I am also having problem with the following running on 64 bit Windows and SQL2005/64 bit. I am erroring in Step 8 'Updating JDBC' driver. I am attempting to update from SP9 to SP18. The WEBAS Jave installed went flawless but I seem to be stuck here. Any help is appreciated...
ERROR 2006-11-22 10:13:57
FSL-06002 Error 2 (The system cannot find the file specified.
) in execution of a 'CreateProcess' function, line (284), with parameter (java.exe ...).

Hi, Had boot issue and got the following from DU repair function on Macintosh hd: updating boot support.....Error: Disk utility can't repair this disk.....reformat and restore backed up files. How is that done or do I go to Genius?

In reference to question the computer gave no warning but lost internet connectivity. I shut down for a while and when returned it would only boot to gray logo screen with spinning gear. Ran disk utility and on Mac HD drive it stopped after "Updating boot support partitions as required". Then in red: Error: Disk utility can' repair this disk ....disk, and restore backed up files. I'm running OS X 10.8 and had just updated the iOS about three days ago. Not familiar with reformat process on MacBook Pro and would like some ideas whether I should go to the Genius Bar here in Sydney or try it on my own. I have been using time machine to back up to a 1TB La Cie drive right up to the crash. Thanks for any advice.

Well it turned out the drive was shot. Took it to the genius bar yesterday and they ran a test on the drive before trying the restore routine again. Drive failed.
Replaced the drive and got the MBP back today. Pretty quick and decent service once you get an appointment.
Now having trouble figuring how to do the Time Machine saved files. Have several applications which I'd like to keep but not sure how to trans the apps from my backup to the new. Hunting for answers on that on the web.
Thanks for you help, Eustace.

Disk Utility stuck on "updating boot support partitions for the volume as required"

Tonight when I mounted my Time Machine drive (a WD My Passport drive), it failed to mount properly, and I received a warning from Drive Genius that it needed repair. But when I launched Drive Genius, the disk would not show up.
Through a series of mounts, unmounts, and sleeping the computer, I managed to get it to show up in Disk Utility, so I seleted "Time Machine Backups" under the main listing for the drive ("319.37GB WD My Passort..."), and clicked Repair.
The detail window showed "Volume repair complete" almost immediately. But for almost four hours now, it's been stuck on "Updating boot support partitions for the volume as required."
Meanwhile, Activity Monitor has been showing fsku_hfs taking 30%-85% of the CPU the whole time.
Anyone have advice?

Apparently not:
Error: Disk Utility can’t repair this disk. Back up as many of your files as possible, reformat the disk, and restore your backed-up files.
But when I ran Disk Utility again this morning, not on the Time Machine Backup, but up the hierarcy on the level labeled "319.37GB WD My Passort...," I got...
The volume Time Machine Backups appears to be OK.
And now the drive seem to be OK.
I think I'll still offload everything and reformat it.

Update Boot Support Partitions, how do I do that??

I have just carried out a Disk Repair on MBP and "Repaired Successfully" message came up but it is asking to "Update Boot Support Partitions", can someone tell me how I do that please??

With the Error 2, let's try a standalone Apple Application Support install. It still might not install, but fingers crossed any error messages will give us a better idea of the underlying cause of the issue.
Download and save a copy of the iTunesSetup.exe (or iTunes64setup.exe) installer file to your hard drive:
http://www.apple.com/itunes/download/
Download and install the free trial version of WinRAR:
http://www.rarlab.com/
Right-click the iTunesSetup.exe (or iTunes64Setup.exe), and select "Extract to iTunesSetup" (or "Extract to iTunes64Setup"). WinRAR will expand the contents of the file into a folder called "iTunesSetup" (or "iTunes64Setup").
Go into the folder and doubleclick the AppleApplicationSupport.msi to do a standalone AAS install.
Does it install properly for you?
If instead you get an error message during the install, let us know what it says. (Precise text, please.)

MOVED: MSI live update not supported on Win XP 64

This topic has been moved to Operating Systems.
MSI live update not supported on Win XP 64

Yes you are right. The system drive will always be Drive C, but I am not sure if D will be my storage drive or the other sytem drive. I could always try and find out but just havn't.
In the past, I had lots of virtual drives (partitions), and HDD's (as many as 10 total IDE devices). But when the larger drives became more affordable, I prefer running with just 2, the system and storage for the sake of simplicity. Since I do beta testing, I have having to reformat and reinstall a lot, so this system has worked great for me.

When the update to support LTE will be released for Claro in the Dominican Republic?

Claro in the Dominican Republic has launched LTE (since yesterday) and proceeded to sell or give the 4G LTE Sim cards so the users can have the service. I went over, got my new sim card and inserted in my Iphone 5 (A1428), and said to my self "I'm good to go". Turns out I wasn't. Unfortunately, I could not get it working. I even moved around the city to see where I could get 4G coverage.
When I called customer service to argue about the lack of coverage and to discuss that this may be a scam from the company. The customer service person told me to go to settings>cellular> to toggle Enable LTE, and I replied that I did not have that option. Then the customer service clerk argued that I did not have an updated Device. My iphone 5 IOS version is 7.1.2.
After doing some research while on the phone with the customer service representative (it was a 45 min long call) I had to agree with him that maybe apple has to "released" or "enabled" the service for this specific carrier, just like it happened in Colombia when the LTE was introduced.
Currently there are 3 companies (Tricom, Orange, and now Claro) offering 4G LTE in the Dominican Republic and None are listed in the 4G LTE availability per device per country according to apple. https://www.apple.com/iphone/LTE/.
So my question is: When the update to support LTE will be released for Claro in the Dominican Republic? (it would be great if an apple employee could get involve in this thread, or escalated it to who can do something about it.)

FelipeV
Let me tell you something: no one is saying go and do something illegal to enable this feature on your phone and no one is reporting any confidential information; the purpose of this thread is to clarify some points:
The LTE Network for Claro DO is real, is functional and is not a Scam
The LTE Network works with compatible devices except iPhones, not by decision of the carrier but the manufacturer.
About that the date that when will be available is not a confirmed date, it's an estimate based on previous releases in other countries and information that I received from inside Claro, not a speculation (find the definition). Of course Claro hasn't confirmed because, like other says, is apple decisions and not their (you don't have to be a genius to figure that out).
Forums are to express yourself freely about a specific topic, and to give your point of view whether you agree or disagree with something, but when you do be polite and do it with respect and not with arrogance as you just did hinting others are stupid and do not know what they are doing. Take an advice from some one with a little bit of experience, you don't know when you will need some help.
Have a good night.

Can't Find SAPKD70021 - SPAM Update Tool Support Package

Hi, All:
     We now need patch SPAM support package 21 - SAPKD70021. But now from http://service.sap.com/swdc , we can only find patch 22 - 24. There's no patch 21, but our currently patch level is 20.
     Do we the only one meet the problem?
     Anyone can help? Thanks!
B.R.
H.D

Hi,
       you can directly update the latest one..ie., 24
Regards
Umesh K

Just update to Pages 5.1 - its dropped the pictures from my Pages files - 'Some features aren't supported - objects in table cells were removed' - how do I get pictures back?

Just update to Pages 5.1 - its dropped the pictures from my old Pages files - 'Some features aren't supported - objects in table cells were removed' - how do I get the pictures back?

Thanks Peter
Can you just walk me through dumping Pages 5 and getting to the Applications/iWork folder - and does this mean that when I see future Pages Upgrades I should block them?
I'm new to Apple so need a step by step
Many thanks
Glyptic

HT1338 Macbook Pro Updates to Support Nano

I recently bought the new iPod Nano, which needs itunes 10.7. I was trying to update my itunes; however it says I need Mac OS 10.6.8 or later (I have 10.5.7). When I look for the software updates it says there are none at this time. What update do I need? I have tried several from the Apple Supports but when I run them it tells me that they aren't supported by my device.
Thanks!!

Welcome to the Apple Support Communities
Check if Mac is supported > http://support.apple.com/kb/sp575 If it's supported, call Apple to buy Snow Leopard > http://support.apple.com/kb/HE57 Then, make a backup, insert the DVD and upgrade. Finally, open  > Software Update and install the latest version.
If you prefer, you can use Mountain Lion > http://www.apple.com/osx/specs. If your Mac is supported, open App Store and purchase OS X

Is there a camera raw update to support NikonD5300?

I'm unable to find an update to support NikonD5300, I cannot open my raw files in camera raw.

What version of Camera Raw do you have in PS? Help / About Plug-in / Camera Raw
If you used an old version of Nikon Transfer for View NX you may have corrupted the files from the camera. You need to either update your Nikon software to the versions that came with your new camera or stop using Nikon software.
To fix the corruption caused by obsolete Nikon software you can use a utility from here:
http://owl.phy.queensu.ca/~phil/exiftool/fix_corrupted_nef.html

Time updation for Support desk message and business calender working hours

Hi Experts,
I would like to know how to set the time updation of Support desk message in CRM_DNO_MONITOR. After i receive a new message in it, I can see the from timing and to timing (even after changing the status of message) as 00:00:00. Is there any standard job to automatically update the timing of message?
Also i would like to know, how to set the working hours for various days. Lets say i want to set my business hours for Monday from 10am to 6pm and for Tuesday as 9am to 5pm.
Suitable points will be rewarded.
Thanks in advance,
Naresh Dodeja.

Hi,
The reason is "created by me" selects the role "Creator" of a message/notification.
There are three roles "Creator", "Contact" or "Reporter" and "Responsible" or "Processor".
The creator is identified by his user name and the others by their BP-ID.
Therefore using the report "created by me" does not work if your users are defined for BPgen only.
That it works you have additionally to define in BP the role "BUP003 - Employee".
You find in the transaction BP for "BUP003 - Employee" in the tab "identfication" a field "User Name".
If you enter the User-ID the user has in the Solution Manager then it works.
Good look!
Best regards,
Adelbert

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#

I just updated to Lion and my Microsoft Word, Excel and PowerPoint will not open because PowerPC applications are no longer supported. I bought this software from Apple and the store installed it when I bought the MAC. What do I do?

I just updated to Lion and my Microsoft Word, Excel and PowerPoint will not open because PowerPC applications are no longer supported. I bought this software from Apple and the store installed it when I bought the MAC. What do I do?

Buy version 2011 of MS Office.
Or you can download OpenOffice, LibreOffice or NeoOffice, which all come very close to working with MS files just like MS Office does.
Or iWord, I have heard, you can purchase.

When will Photoshop Touch be updated to support the new iPad (3)?

Since the screen is now greater than HD and the camera has just been enhanced to 5 MP, PS Touch should be updated to support pictures larger than 1600 x 1600 as quickly as possible as well as adding direct support for the Retina screen. Otherwise it will look fuzzy and seem underpowered for the device going forward. Any estimate on what date this much-needed update will be released?

Hi Plossi,
I don't have an iPad3 myself but I have heard from others that PS Touch looks and runs great on it. Adobe will continue to release updates to PS Touch to make the app better and take advantage of the latest hardware (including iPad3). It's not possible to provide dates around any future releases though. Larger image support is a very common request. Please add your vote here is you haven't already.
http://forums.adobe.com/ideas/1028
Thanks for posting,
-Dave

Driver update to support S.M.A.R.T. software from Drive Genius/Prosoft

Similar Messages

Maybe you are looking for