Cause for the sudden shutdown of Essbase?

Hello Experts,
One of my customer would like to know the cause for the sudden shutdown of Essbase. They started receiving the below error when tried to connect through EAS or through Spread sheet Add-in
network error [145]: unable to connect to essolap.east:1423
Please find the application log as below:
[Tue Apr 7 23:01:52 2009]Local/MRI_R_09///Info(1019018)
Writing Parameters For Database [MRI_R_09]
[Tue Apr 7 23:01:52 2009]Local/MRI_R_09///Info(1013207)
RECEIVED SHUTDOWN COMMAND - SERVER TERMINATING
[Tue Apr 7 23:02:36 2009]Local/MRI_R_09/MRI_R_09/admin/Info(1013273)
Database MRI_R_09.MRI_R_09 altered
[Tue Apr 7 23:02:36 2009]Local/MRI_R_09/MRI_R_09/admin/Error(1270095)
Specified load buffer resource usage [1] is above currently available value [0]
[Tue Apr 7 23:02:36 2009]Local/MRI_R_09/MRI_R_09/admin/Info(1019018)
Writing Parameters For Database [MRI_R_09]
[Tue Apr 7 23:02:39 2009]Local/MRI_R_09/MRI_R_09/admin/Error(1270040)
Data load buffer [123] does not exist
[Tue Apr 7 23:02:39 2009]Local/MRI_R_09/MRI_R_09/admin/Error(1003050)
Data Load Transaction Aborted With Error [1270040]
Any suggestions on this? Thanks in advance.
Regards,
Sonal

Hello Amol,
I reviewed the log files. I could find only these logs:
[Tue Apr 7 23:01:52 2009]Local/MRI_R_09///Info(1019018)
Writing Parameters For Database [MRI_R_09]
[Tue Apr 7 23:01:52 2009]Local/MRI_R_09///Info(1013207)
RECEIVED SHUTDOWN COMMAND - SERVER TERMINATING
[Tue Apr 7 23:02:36 2009]Local/MRI_R_09/MRI_R_09/admin/Info(1013273)
Database MRI_R_09.MRI_R_09 altered
[Tue Apr 7 23:02:36 2009]Local/MRI_R_09/MRI_R_09/admin/Error(1270095)
Specified load buffer resource usage [1] is above currently available value [0]
[Tue Apr 7 23:02:36 2009]Local/MRI_R_09/MRI_R_09/admin/Info(1019018)
Writing Parameters For Database [MRI_R_09]
[Tue Apr 7 23:02:39 2009]Local/MRI_R_09/MRI_R_09/admin/Error(1270040)
Data load buffer [123] does not exist
[Tue Apr 7 23:02:39 2009]Local/MRI_R_09/MRI_R_09/admin/Error(1003050)
Data Load Transaction Aborted With Error [1270040]
After this, the server was hung. When server was restarted, it did not crash again.
Thanks in advance.
Regards,
Sonal

Similar Messages

What is the cause for the mac to become slow

what is the cause for the mac to become slow?

Things You Can Do To Resolve Slow Downs
If your computer seems to be running slower here are some things you can do:
Start with a visit to: OS X Maintenance - MacAttorney.
Boot into Safe Mode then repair your hard drive and permissions:
Repair the Hard Drive and Permissions Pre-Lion/Mountain Lion
Boot from your OS X Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Utilities menu. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the installer.
If DU reports errors it cannot fix, then you will need Disk Warrior and/or Tech Tool Pro to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.
Repair the Hard Drive - Lion/Mountain Lion
Boot from your Lion Recovery HD. When the recovery menu appears select Disk Utility. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported, then click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the main menu. Select Restart from the Apple menu.
Boot to the Recovery HD:
Restart the computer and after the chime press and hold down the COMMAND and R keys until the menu screen appears. Alternatively, restart the computer and after the chime press and hold down the OPTION key until the boot manager screen appears. Select the Recovery HD and click on the downward pointing arrow button.
Restart your computer normally and see if this has helped any. Next do some maintenance:
Suggestions for OS X Maintenance
For situations Disk Utility cannot handle the best third-party utility is Disk Warrior; DW only fixes problems with the disk directory, but most disk problems are caused by directory corruption; Disk Warrior 4.x is now Intel Mac compatible.
OS X performs certain maintenance functions that are scheduled to occur on a daily, weekly, or monthly period. The maintenance scripts run in the early AM only if the computer is turned on 24/7 (no sleep.) If this isn't the case, then an excellent solution is to download and install a shareware utility such as Macaroni, JAW PseudoAnacron, or Anacron that will automate the maintenance activity regardless of whether the computer is turned off or asleep. Dependence upon third-party utilities to run the periodic maintenance scripts was significantly reduced since Tiger. These utilities have limited or no functionality with Snow Leopard or Lion and should not be installed.
OS X automatically defragments files less than 20 MBs in size, so unless you have a disk full of very large files there's little need for defragmenting the hard drive. As for virus protection there are few if any such animals affecting OS X. You can protect the computer easily using the freeware Open Source virus protection software ClamXAV. Personally I would avoid most commercial anti-virus software because of their potential for causing problems. For more about malware see Macintosh Virus Guide.
I would also recommend downloading a utility such as TinkerTool System, OnyX 2.4.3, or Cocktail 5.1.1 that you can use for periodic maintenance such as removing old log files and archives, clearing caches, etc.
For emergency repairs install the freeware utility Applejack. If you cannot start up in OS X, you may be able to start in single-user mode from which you can run Applejack to do a whole set of repair and maintenance routines from the command line. Note that AppleJack 1.5 is required for Leopard. AppleJack 1.6 is compatible with Snow Leopard. There is no confirmation that this version also works with Lion.
When you install any new system software or updates be sure to repair the hard drive and permissions beforehand.
Get an external Firewire drive at least equal in size to the internal hard drive and make (and maintain) a bootable clone/backup. You can make a bootable clone using the Restore option of Disk Utility. You can also make and maintain clones with good backup software. My personal recommendations are (order is not significant):
1. Carbon Copy Cloner
2. Data Backup
3. Deja Vu
4. SuperDuper!
5. SyncTwoFolders
6. Synk Pro
7. Synk Standard
8. Tri-Backup
Visit The XLab FAQs and read the FAQs on maintenance, optimization, virus protection, and backup and restore.
Additional suggestions will be found in Mac maintenance Quick Assist.
Referenced software can be found at CNet Downloads or MacUpdate.
Additional Hints
Be sure you have an adequate amount of RAM installed for the number of applications you run concurrently. Be sure you leave a minimum of 10% of the hard drive's capacity as free space.
Add more RAM. If your computer has less than 2 GBs of RAM and you are using OS X Leopard or later, then you can do with more RAM. Snow Leopard and Lion work much better with 4 GBs of RAM than their system minimums. The more concurrent applications you tend to use the more RAM you should have.
Always maintain at least 15 GBs or 10% of your hard drive's capacity as free space, whichever is greater. OS X is frequently accessing your hard drive, so providing adequate free space will keep things from slowing down.
Check for applications that may be hogging the CPU:
Open Activity Monitor in the Utilities folder. Select All Processes from the Processes dropdown menu. Click twice on the CPU% column header to display in descending order. If you find a process using a large amount of CPU time, then select the process and click on the Quit icon in the toolbar. Click on the Force Quit button to kill the process. See if that helps. Be sure to note the name of the runaway process so you can track down the cause of the problem.
Often this problem occurs because of a corrupted cache or preferences file or an attempt to write to a corrupted log file.

Can we make a sticky for the RAID shutdown issue?

Hi guys - I'm new to the forum...
I'm experiencing the hanging shutdown issue with my K8N Neo4 Platinum board and SATA Raid 0 in XP. I've searched the forum for answers, but think it would be a good idea if someone made a sticky of this as its a popular problem.
If not - has anyone got a final fix?
I've got version 1.B bios with 6.70 nVidia drivers - still no joy!

I have two k8n neo 4 platinums that are doing the same thing.
I installed a clean drive & a basic windows install (no dedicated drivers) & flashed the bios to 1.c. Same issues. Msi says it is a hardware compatability issue , I say BS!
After speaking with Nvidia they supplied newer driverd than the 6.70. The problem went away. However these drivers are not stable. I am having other issues. And am still working with Nvidia to solve them.

What is a cause for the error

Anyone out there knows waht is a cause for error message bellow:
          /vol01/local/bea/weblogic5.1/wl-vinlkup/classfiles/jsp_servlet/_vin/_VINsearch.java:244: Wrong number of arguments in method.
          resultof = LocationBean.getCounties(stateName); //[ /vin/VINsearch.jsp; Line: 111]
          Servlet failed with Exception
          java.io.IOException: Compiler failed executable.exec


          Wrong number of arguments in method
          - resultof = LocationBean.getCounties(stateName);
          Perhaps getCounties is defined with zero or more than one argument.
          Mike
          Yuping Xu <[email protected]> wrote:
          >Anyone out there knows waht is a cause for error message bellow:
          >/vol01/local/bea/weblogic5.1/wl-vinlkup/classfiles/jsp_servlet/_vin/_VINsearch.java:244:
          >Wrong number of arguments in method.
          > resultof = LocationBean.getCounties(stateName); //[
          >/vin/VINsearch.jsp; Line: 111]
          >Servlet failed with Exception
          >java.io.IOException: Compiler failed executable.exec

A possible cause for the Lion freezes: Spotlight indexing

Does your Mac freeze mysteriously after upgrading to Lion?
Mine had that problem, but after troubleshooting, I seem to have identified the culprit (at least for my MacBook) and, after deleting the offending file, I have since experienced no problem. Here, I will share a case report with the hope that it will help others troubleshoot their computers experiencing the same problem.
The Problem: Mac (running Lion 10.7 or 10.7.1) freezes sometime after logging on. The freeze begins by an inability to get a response to clicks. The cursor is still active, but after a click or two the cursor turns into a spinning disc. After some time, the clock stops updating on the menu bar.
Mine froze consistently after about 15-20 min after logging on. It happened regardless of which application I was using, it froze even if I didn't do anything after logging on. It required a reboot (control-command-power button on a MacBook) everytime.
Was Spotlight indexing active right before the freeze happened? When Spotlight indexing is active, the magnifying glass icon on the upper right corner of your display will show a blinking dot. Mine was.
A Possible Culprit: Spotlight may have encountered a corrupt file on the hard disk during indexing.
What you can do:
Before you do anything, it is recommended that you have backed up all your files. Unfortunately, it is difficult to back up now because the Mac may freeze during the back up process.
1. Check the errors related to Spotlight by opening Console, which is an utility app that you can find in the Applications>Utilities folder. Do you see error messages for "mdworkers"? It does not always show up before the freeze, but this may indicate some problems during Spotlight indexing.
2. Confirm the problem by turning off Spotlight indexing. You can do this in a number of ways, but I will list two ways below:
a) Go to System Preferences and click on Spotlight icon. Under the Privacy tab, click on "+" icon and add the "Users" folder (or any particular folder that you may suspect). The indexing will not happen to files in that folder. Also, turn off Time Machine and disconnect back up disks, if you use any. Apparently Spotlight indexes within the Time Machine backups. OR
b) For experienced users: Open Terminal and type "sudo mdutil -i off" without the quotes. (To turn it back on, type "sudo mdutil -i on /" without the quotes)
3. Try using your computer with Spotlight turned off. Does it still freeze? If it does not, you have confirmed that the problem is with Spotlight indexing.
4. Find the offending file that causes problem by turning Spotlight indexing back on...
a) Remove the folder by highlighting and clicking on "-" button under the Privacy tab. OR
b) For experienced users: Type "sudo mdutil -i on /" without the quotes.
5. ...and then repeating steps 2a, 3, and 4a. Try isolating different folders until you can narrow down the problem. This process may take a while.
6. Once you narrowed down to a few folders, try QuickLook through the contents of the folder while the Console is open. To use QuickLook, highlight a file in the Finder and hit a space bar on your keyboard. It is helpful to set the Finder in a column view so you can use arrow keys to navigate through the folders. Does Console show you an error when you QuickLook a file? Can you double click and open that file? If not, the file may be corrupt. Trash that file and empty trash.
7. Now turn Spotlight indexing back on (step 4) and use your computer for a while. Does it still freeze? If so, repeat the process and find other corrupt files.
For me, it was a single corrupt image file in the Documents folder that caused the freezing problem. I deleted it and the problem went away. Since that file had been untouched for years, and I did not experience the same freezing problem in Snow Leopard, I suspect that Spotlight in Lion is somehow less permissive of corrupt files assuming that the file did not corrupt after the upgrade.
Steps 4-7 is cumbersome and it takes a long time to troubleshoot. If you know of a faster way to identify corrupt files, please share in this thread. Also, I think Spotlight should alert the users when it encounters a corrupt file and give us a choice to delete it on the spot. Please join me by sending a feedback to Apple about this.

My G5, PPC, came with Tiger installed and ran great. I decided to upgrade to Leopard (not snow leopard) and at first it seemed to work well.
Here is where you should backup, reinitialize, and make sure you use retail 10.4 rather than any OEM DVD?
After several days I noticed I have Permission errors that Disk Utility would not fix. (The only way to repair this was to insert the install disk and run Disk Utility from there: which means you have to reimport/install all the OS updates over again)
Some real confusion. Permissions can and should be done while booted from your hard drive; never run from older version of OS X.
Not all permission messages are errors.
Bootable backups (clones).
Invest in 3rd party repair programs.
Eventually the OS was crashing and freezing so I went to a local Apple repair store to ask why. Apparently Leopard is unstable on some G5 towers.
No, not really.
But you do have to insure your hardware, your software, is also current.
I decided to reinstall Tiger and still had problems. After about 5 attempts at reinstalling the OS I realized I was using a disk from a G4 tower that my kids use, so I found the disk that come with my G5 and the install worked perfectly.
So it appears that not all OS install disks are the same:
No secret there. NEVER use an OEM disc except your own; or, use retail full install versions is all. I guess you never came across that bit.
Sorry you had to take so much time, but sounds like came away with some misconceptions.

Possible Fix for the Random Shutdown Issue

One of the readers at MacFixit was able too find a solution to his RSD Macbook. He discovered when he removed the top case (they keyboard) off his machine, the Macbook worked fine. After further investigation, he found out that the top case and the heat sync seem to touch each other while the machine is closed (generating more heat). To fix the RSD he put kapton tape on the top case (to separate the heat sync and the top case) and on the track pad cable. Not only did it fix the RSD problem, another plus it causes the computer to run cooler.
So it appears what Apple needs to do is, either put Kapton tape on the top case, or move some the thermal grease from the processor too the top case. Another easy fix might be just to send out new top cases (since only a significant minority are effected by this problem, their might just be a set of bad cases out their).
Before you decide to open up your machine and put on Kapton tape on your machine, keep this in mind, it will void your warranty.
http://www.macfixit.com/article.php?story=20060821101232169
Macbook Mac OS X (10.4.7)

Holding down the power button until it beeps is still the only way that I can get my machine to boot up fully and become operational. I was starting to think that I was crazy after reading above that all it did was to remind me that my finger was still on the power button. I've had my husband and my son watch this process just to convince myself I wasn't crazy.
I've been deleting software, going through log files, making other changes to make sure that they weren't interfering with the machine working. I shut the machine off this morning to go do something else. When I turned it on again I forgot to hold the power button until I heard the beep. After I logged in, I realized that I hadn't done that and that the machine had actually gone through the complete boot cycle and login. I thought "wow, maybe I fixed it. Maybe it was something software related." I waited for a few minutes to make sure that everything that it had to do in its start up was finished before I did anything thinking "well maybe its just that I try to do too many things too quickly, and it is operator error and my fault I've been having this problem". Then I went to open Safari and "blink" the machine went dead.
Then I put my finger on the power button until it beeped to start it up a second time. I've been working on it for six hours now. It's gone to sleep while I've been on the phone, I've woken it up with a short press of the power button and logged in a few times today.....not one single problem in 6 hours.
It's crazy. I don't know what holding the power button for that long does but it must be resetting or otherwise doing something that causes it to override whatever problem was causing it to just shut down by itself. I love everything else about this MacBook. I don't want to have someone start taking it apart and putting it back together again. If the fix is just remembering to "hold power until it beeps" I"ll live with it.

Causes for the "Expected an array object" error

I'm using Acrobat Pro X and am getting the "Expected an array object" error recently when inserting a PDF that was created by inserting a smaller collection of other PDF documents, if that makes sense.
Oddly, or maybe not, I can build the second level PDF by inserting all of the individual PDFs one at a time. The error only occurs when I try to "build up" the larger document.
My searches come up empty as far as revealing what causes this error.
Anyone know what causes it?
Thank you.

How are you creating the pdf. Your comment about putting a publication together gives us nothing to go on.

The root cause for the case that "cannot close labview-generated exe file"

Hi All, I have a big program including a lot of things. When I converted it to an exe file, it cannot be closed properly. I used to load the dynamic vi in this program and cannot close it by clicking "X" of the window. Now I have removed that dynamic load but still cannot close the exe. Could anyone give me some advice? Thank you!

Hi Freelance_LV, thank you for your advise, here is a program for a USB dongle. Here are the answers:
for now, questions:
1. how are you closing the EXE? Panel close (X) on the top right corner/stop or exit button on the GUI?
[A] I use (X) on the top right corner but it did not work. But when I use exit button on the GUI it worked.
2. Or are you using a FP Close invoke node?
[A] No
3.how are you handling the event for Panel close or for Stop/exit button?
[A] events are inside a sequence frame
how many loops are running in parallel inside the EXE?
[A] It is hard to tell. I am not the original creator of this code, but the main structure is this: a big "for" loop, inside there are some sequence frame, and some events in one of the frame.
how are you stopping those loops when the panel is closed or a Stop/Exit button is pressed.
[A] the main loop inlcudes some events, sequence frame, and something like this. And there is a subvi from some previous people's work to close USB.
have you checked if all the loops are closing when you stop the EXE?
[A] Sorry I don't know how to check all the loops are closed.
does this work well when you run the source code?
[A] yes source code can be always be closed well.
have you checked for any errors when yuo stop your EXE?
[A] sorry I don't know how to check for errors?
when you say it cannot be closed properly, there could be two things:
1. the front panel/GUI does not close and it stays there. you cannot perform any GUI actions, or it seems to have hung.
[A] Yes GUI still there. But cannot perform any GUI actions.
2. the GUI closes but you can still it in the task bar below, you will have to use the Task manager to force close the executable.
[A] Not this case.
Thank you very much!

Random, Sudden Shutdowns - A redux and other things to rule out first

Do a google search for "macbook random shutdown" and you'll find many people with similar problems reporting on various forums. At present, this issue has not been picked up by the mainstream PC news media. However, one should also note that only a fraction of those with problems are suffering this particular fault. A large number of other reasons must be ruled out before a MacBook owner should become convinced their machine is one which suffers this problem. Bad RAM, poorly seated RAM, improperly installed hard drive, corrupted OS, corrupted plists, bad batteries, bad chargers, corrupted PMU, and corrupted NVRAM all need to be ruled out first!
My own MacBook suffered the random sudden shutdown malady and eventually required complete replacement after a logic board replacement did not solve the issue. Some of the MacBooks appear to have a hardware problem which surfaces after a period of use. Many reported their problems starting after a month of ownership. Coincidentally, that also coincided with the release of 10.4.7, but most likely that is not at the root of the sudden, random, shutdown problem.
(However, 10.4.7 is strongly implicated in a separate MacBook problem - colored vertical lines during boot on some machines. That is probably a separate issue.)
Description of the Random, Sudden Shutdown Problem
MacBook suddenly shuts off to a completely powered down state seemingly at random. There are no kernel panic, mouse freezing, or other premonitory symptoms. The machine simply powers down suddenly. The screen goes black. The hard drive spins down and no sleep light illuminates. The machine simply turns itself off.
The shutdowns may occur on either battery or with AC adapter attached. Some owners report their MacBook is less prone to sudden shut down while on battery vs AC adapter. My own afflicted MacBook would suddenly shutdown on a fully charged battery or on either of two AC adapters.
The shutdowns occur with either 10.4.6 or 10.4.7 OS loaded. I went through several cycles of clean installs of the base 10.4.6 and the Intel Combo update to 10.4.7 before it became clear that it mattered not which OS was running. Another indicator that this is not an OS issue is that sudden shutdowns can occur in target mode and also when running just the Apple Hardware Test - which relies on minimal software to operate.
The shutdowns tend to grow more frequent once they begin. They may worsen to the point that a machine will not complete boot up before shutting down. It may take several power up presses to start the machine. Oddly enough, a machine that had difficulty starting up, may be easy to start up several minutes later. It may run for hours or minutes before another sudden shutdown. The frequency is low and random enough that is very difficult to demonstrate this fault to a service technician.
Some users are able to induce a sudden shutdown by running their CPU's at high load and thus heating up the machine. This is easily done by running the yes command in two Terminal windows. Some users report their MacBook is more prone to sudden shutdowns when their CPU is relatively cool. The bipolar reporting is confusing. There may be more than one type of sudden shutdown being reported. One due to CPU overheating and another due to another hardware problem which has yet to be elucidated.
Resetting of the PMU and PRAM MAY temporarily reduce the frequency of the sudden shutdowns, but the effect is temporary. Indeed, the effect may not even be real given the randomness of the shutdowns. None-the-less, one must perform PMU and PRAM resets to ensure that some corruption of those devices is not creating a reason for shutdowns. On my own MacBook, resetting PMU and PRAM (four chimes) did not prevent the random sudden shutdowns.
The sudden shutdowns occur with well seated stock RAM, replacement RAM, and reseated/replaced hard drives. Swapping out and testing both RAM and hard drive helps to eliminate those as the source of the problem. On my own machine, I exchanged the RAM and the hard drive to eliminate them as the cause. This made it considerably easier for the Apple genius to decide it was an internal problem.
In my case, a logic board replacement did indeed solve the fault, but several days later, sudden shutdowns began again. Presumably either the replacement board has the same weakness as the original or some other component of the machine was the actual reason for the sudden shutdowns. The former is quite likely because the machine was made stable for several days with a new logic board. At that point, I requested to be swapped to a new machine and the Apple Store manager wisely decided to help out his customer. For that I am most grateful. However, it is unlikely that the majority of people will have their machines swapped out, but instead repaired.
At this time, no official statement regarding cause for or acknowledgment of the MacBook's sudden random shutdown problem has been made. Because the underlying cause has not been revealed, it is impossible to know that a logic board replacement will permanently solve the problem or merely result in the same fault recurring later on the replacement board. Of course, we do not know if it actually is a logic board flaw.
My advice to MacBook owners whose machines develop the sudden random shutdown symptoms are to...
1. Get your data backed up immediately. The machine will likely suffer more and more frequent shutdown events.
2. Revert to stock RAM and hard drive if you have installed after-market replacements. You must do this and see if the shutdowns continue to occur. Otherwise, the first thing blamed will be your RAM and hard drive.
3a. Perform a PMU reset, by shutting down the MacBook. Removing the battery. Disconnect the AC Adapter. Then, press the power button for five seconds. The reinstall the battery and mains adapter. Restart the machine.
3b. Reset PRAM by holding option-command-P-R keys down during startup until you hear the chime at least three or four times.
Resetting the PMU and PRAM are standard procedures you'll otherwise be asked to perform to diagnose your machine.
4. Do a CLEAN install of the OSX if you wish to totally eliminate a bad OS install as the problem. This will destroy all your data. Alternatively, an archive and install will be helpful without totally destroying your data, but that will not let you exonerate your system files and settings. An alternative is to run Apple's hardware test utility which is found on your OS installation disc. However, an extended hardware test is needed because the shutdown flaw may take hours to surface.
Note: If your MacBook has become so "narcoleptic" that it cannot even complete a boot up sequence, try holding the power button down until you hear a loud beep. That may allow an otherwise balky machine to start.
Once you have done the above, and are still seeing random sudden shutdowns, you have largely done the preliminary footwork that you'll need to prove whether your MacBook has this particular problem and not something more common. Then, call AppleCare or visit your Apple Genius to have the machine repaired or replaced. Hopefully, the root cause of this problem will be discovered, disclosed, repaired and prevented. For now, it appears only a fraction of the MacBooks are suffering this fault, but the machine population is still young. Overall, the MacBook is perhaps the finest laptop I've bought from Apple. It will be nice to trust the machine to not lose my work.
BTW - resetting PMU may induce a separate 10.4.7 related bug which results in your MacBook exhibiting a white screen with progressively more numerous vertical color lines during startup. This appears to be fixable by resetting PRAM and then temporarily changing display resolution to something other than the current setting and then back.

thanks for the comprehensive info. i experienced this for the first time today. i bought my macbook the day they were released. the shutdown happenned for me after leaving my computer on overnight with no programs running. about two minutes into web browsing it shutdown. it then shutdown in the middle of restarts. i disattached power cord, external hard drive, dvd burner & ethernet & it powered up and has been working for about 20 minutes since.
this computer has really been a lemon. first my superdrive scratches the **** (just previewed this, i can't believe they sensor the h_ word?) out of discs, then the trackpad button becomes very hard to push. i've been working around those issues using an external dvd burner and mouse, but not sure how to work around sudden shutdowns. i haven't been able to send it in for repairs yet since i bought it cause i needed it's dvd authoring capabilities for a class i was taking, plus i wanted to make sure nothing else went wrong (self fulfilling prophecy?). i was planning on taking it on vacation with me, but guess i better pack my old ibook too (which other than a cd burner which sucked from the start, has been very reliable). i'll send in my macbook when i get back.
anyway, thanks for the info & advice! i'll back up my crucial data now.
white macbook, 2GHz, 1GB ram (factory installed) Mac OS X (10.4.7)
macbook Mac OS X (10.4.6)
macbook Mac OS X (10.4.6)

Unable to Export iMovie project in everyway I have attempted for the past 2 weeks. Please Help! Due date coming up!

I've unable to Export iMovie project in everyway I have attempted for the past 2 weeks.I have a late 2012 iMac with 8gb of RAM and 700 gb of free space on the hard drive. The video I am trying to export is 48 mins long with most of the source footage from a NIkon D3100 and several other cammcorders. I've been exporting with Apple Intermediate codec because that was the only one that has work so far but it only worked once and since then I have had to make changes to the project and now I'm unable to get it to work. For all Quicktime exports in H.264 or AIC (my prefered format for this export since I figured it'd offer the highest quality when I import it into Encore for making a dvd out of it) Which just stops exporting in the last few minutes without explination as to why or it crashes and quits. It either leaves a partial file or nothing at all. When I do "export movie" I get a "not enough memory Heap zone error"
I don't know what to do any help would be greatly appreciated!
By the way I happen to have Adobe CS6 Production Premium but didn't know how to use it as well when starting the project and now really regret not using it because it appears to be 10x more stable and capable of handling all the tasks I want it to do.

Hi
Error -108 memFullErr Ran out of memory [not enough room in heap zone]
Turn off - TimeMachine usually works - re-try.
(the Application down in the Dock - not the Device)
But this can mean many thing's - My first thought is
Free Space on Start-Up hard disk. How much ? (other disks do not count)
AppleMan1958
Are your event clips in h.264? If so, you can solve this by Right clicking on your Event Name and choose "Optimize Media". You can choose Full for 1080P or Large for 960P according to your preference.
After you have optimized your Event, you should be able to Share with no problem.
Lennart Thelander
-108 mean you are running out of (free) RAM.
Try restarting the computer just prior to sharing. That frees up RAM.
from mynameisearl
Final Entry
Ok - after much cutting, trial and error and days of work I have never really established a root cause for the -108 error. Nothing I did resolved the issue to the orginal project.
The only work around I have found is to split the Original Project into two.
What I found was that anything around the 60 mins mark and above just failed to render in HD and showed the -108 error.
What worked for me was creating two project files - one around 57mins long - the other a part 2 - around 17 mins long. All using exactly the same source clips, photo's, music and transitions as the orginal.
This now works. I guess having it split in two makes it a little easier to work with as I wont have to keep rendering the first part which does not change but really wish Apple would throw some light on this.
Anyway - I hope all of the above at least proves useful for others.
Good Luck

Tax value is not picked up correctly for the condition type in SO creation

Hi All,
I have a issue in Picking up Tax value correctly for the condition type in SO Creation.
Actual Issue:
When creating the sales order manually,
tax value is picked up correctly for one condition type: ISS3.
When the Sales Order is created via Idoc using the function module 'idoc_input_orders', tax value is not picked for same condition type: ISS3.
We need to find out why the value for the condition type 'ISS3' is not picked in this way!
Can anybody solve this issue!
What can be the reason which is stopping picking up tax value for condition type: ISS3 when Sales Order is created via F.M 'IDOC_INPUT_ORDERS'! While it picked up the same while creating Sales Order manuallly.
Thanks in advance.
Thanks,
Deep.

Hi All,
Can anybody give the solution for above posted issue!
Working:
When creating the sales order manually,
tax value is picked up correctly for the condition type ISS3.
Actual Issue:
When the Order is created via Idoc using the function module 'idoc_input_orders',
tax value is not picked .
I need to find out why the value for the condition type 'ISS3' is not picked.
I have debugged the issue from WE19 but upto Conditions tab it is picking up tax value but then it is becoming zero again it remains zero after saving SO.
But Manually tax value is picked up for condition type ISS3 and remains same after saving order.
I have debugged it several times fro WE19 but not able to find route cause for the issue.
What can be the issue over here!
Can anybody give me solution for the same!
Thanks in advance.
Thanks,
Deep.

SFLIGHT is NOT defined for the current logical database.

I have just started learning ABAP and bought an ABAP Objects book by Horst Keller. I have installed 4.6d mini sap and SAP GUI 6.4 on win XP Prof. I executed S_FLIGHT_MODEL_DATA_GENERATOR to load DB tables.
(1). When I tried to check a sample program, I get an error message SFLIGHT is not defined for the current logical database.
Here is the partial code:
REPORT zbcb01f1 .
TABLES: sflight, sbook.
DATA: BEGIN OF sr OCCURS 100,
      carrid LIKE sbook-carrid,
      connid LIKE sbook-connid,
      fldate LIKE sbook-fldate,
      bookid LIKE sbook-bookid,
      order_date LIKE sbook-order_date,
      loccuram LIKE sbook-loccuram,
      END OF sr.
GET sflight.   <---- Error is pointed here
(2). I am also not getting Graphical Screen Painter when selecting Layout for a screen. Instead, I am getting alphanumeric editor.
Someone please help me.
Raizak.

Hi Raizak,
the easiest way is to go to service.sap.com/notes and enter the note number. For this time I've copied the 2 notes below.
Best regards,
Christian
Symptom
The Graphical Layout Editor of the Screen Painter either does not start or terminates.Error message 37527 is displayed in the session in which the call was made (Graphical Layout Editor not available.
Additional key words
() EUNOTE, EUSCREENPAINTER, 37 527
Cause and prerequisites
This note comprises all the common causes for error message 37527 and provides you with information on how to systematically trouble shoot the problem.
1. Windows32 or UNIX/motif?
As of Release 4.6B there is only the program version for 32bit Windows (NT, 95, 98, 2000 ff.).Up to Release 4.6A there was also a version for UNIX/Motif.All of the more current notes (with the exception of Note 45490) refer only to the Windows version.
2. Termination at the start or during use?
The following diagnostic steps refer to the causes of the errors which prevent the Graphical Layout Editor from starting. However, there are also known error causes, which result in the program terminating when the application is being used and which also produce the 37527 error message. This affects -
Rel.4.6C/D: Termination when attempting to read texts in the logon language -> Note 375494
Crash after transferring program and dictionary fields. Termination after transferring program and dictionary fields -> Note 189245
Release 3.1I: Termination after inputting field text -> Note 113318
3. Is the SAPGUI installation correct?
The Graphical Layout Editor is automatically installed during the standard installation of the SAPGUI.If you chose a non-standard installation, then you should have explicitely selected its installation (component "Development Tools - Graphical Screen Painter").
The program executable is called gneux.exe.During the SAPGUI installation it is placed in the same directory as the SAPGUI programms (for example, front.exe) (usually C:\Program Files\SAPpc\sapgui). The following belong to the program:
- An additonal executable gnetx.exe (RFC starter program)
- the DLL eumfcdll.dll
- various eusp* data files (that is, the names all begin with eusp.)
You can check the completeness of the program installation by starting the program gneux.exe locally in the SAPGUI directory (for example, by double-clicking on the program name in the Explorer window).The Layout Editor is displayed with German texts and an empty drawing area for the pseudo screen EUSPDYND 0000.
If the installation is not complete, an error dialog box provides information regarding the cause of the error, for example, sometimes the DLL eumfcdll.dll is missing after reinstalling the SAPGUI. For example, the eumfcdll.dll DLL was sometimes missing after the SAPGUI was reinstalled.
4. System link defined and okay?
The Graphical Layout Editor is a separate program which is started by the Screen Painter Transaction (SE51) on the Frontend machine.
Up to Release 3.0F, the programs communicated with each other via the graphics log of the SAPGUIs (gmux).The definition of the environment variable SAPGRAPH may be the cause for the program not being being found where it is.
As of Release 3.1 G, the programs use a separate RFC link which is set up in addition to the SAPGUI's RFC link.Missing or incorrect definitions of the RFC destination EU_SCRP_WN32 or problems with the creation of the RFC link are the most frequent causes for error message 37527 being displayed.Below you can find the correct settings for the RFC destination EU_SCRP_WN32 (under "Solution").Note 101971 lists all the possible causes for problems with the RFC link set-up. Attention:The Graphical Layout Editor may not be operated through a firewall (for example between the SAP and the customer system) because this does not allow an additional RFC connection in addition to the SAPGUI.
Solution
ad 1 UNIX/Motif
Note 45490 describes possible errors resulting from an incorrect program installation under UNIX/Motif (up to Release 4.6A).
ad 2 Termination when using
The above-mentioned notes may contain options for solving individual problems.However, you usually have to replace the program with an corrected version.You can do this either by downloading a patch from sapservX or by installing a more current SAPGUI.The patch is mentioned in the respective note.
ad 3 Installation
You either need to reinstall the SAPGUI or manually copy the missing file into the SAPGUI directory.In both cases you should make sure beforehand that a Graphical Layout Editor is no longer running.To do this you can either remove all processes gneux.exe from the process list by using a tool such as Task Manager (on WindowsNT) or exit the Graphical Layout Editor from the Screen Painter Transaction menu via Edit -> Cancel Graphical Screen Painter). Attention:For each session or system an individial Layout Editor process may exist so that, if need be, several processes should be cancelled.
ad 4 System link
Up to Release 3.0F:you can either delete the environment variable SAPGRAPH or copy all the files of the Graphical Layout Editor into the directory which is specified by SAPGRAPH.
As of Release 3.1G:you can use Transaction SM59 to check the RFC destination EU_SCRP_WN32 (expand the TCP/IP connections, select destination EU_SCRP_WN32).If the destination is missing, then you should create it with the following settings:
- Connection type "T" (start of an external program via ...)
- Activation type "Start"
- Start on "Front-end workstation"
- Front-end workstation program "gnetx.exe" (caution! NOT gneux.exe)
- Description (optional) "Graph. Screen Painter (Windows32)
Start Program gneux.exe using the gnetx.exe starter program."
If you want to start the program from a different directory than the SAPGUI standard directory, then replace the default value under Frontend work station by the complete path name for program gnetx.exe.Transaction SM59 also allows you to check the RFC connection via the pushbutton "Test connection").In this case the system attempts to localize and start the program gnetx.exe.If there are errors, a message is displayed regarding the possible causes (for example, gateway problem, timeout problem or the like).Note 101971 provides a detailed explanation of the problems involved with an RFC connection set-up.As the Graphical Screen Painter requires a functional RFC connection as of Release 3.1G, contact the System Administrator or create an message on the topic Middleware (BC-MID-RFC) if you encounter RFC problems.
If the program gnetx.exe can be found and started, the banner dialog box with logo, release data and version number is displayed briefly.As the Layout Editor itself is not started, the error cause must be in the installation of the Layout Editor program gneux.exe if the connection test was successful.
Release 4.5A to 4.6B: Use with Releases <3.1G>.
The Graphical Layout Editor is downward-compatible as regards the system connection, that is, an RFC-based Layout Editor for example from Release 4.6C can also be used on a non-RFC-based Screen Painter, for example of Release 3.0F.However, the releases mentioned above have a program error which causes a crash due to memory violation in the start phase of the program.Note 197328 describes the solution by installation of the corrected program version.
Important: Trace file dev_euspNNN!
If none of the diagnosis steps leads to the cause of the error and to the solution of the problem via the corresponding note, then you should add the contents of the trace files dev_euspNNN (NNN = process number) to the message for SAP, if possible.You can find this file in the current directory of the SAP System, for example under Windows NT in C:\Winnt\Profiles\<user>\SAPworkdir.If several such trace files can be found there, make sure that you use the file which matches the termination time with respect to date and time of creation.In most cases the ERROR message in the last lines of this trace file provides an important note on the cause of the error.
Source code corrections
Symptom
The graphic layout editor of the Screen Painter cannot be started (RFC version).
Other terms
() EUNOTE, EUSCREENPAINTER
Reason and Prerequisites
This is generally caused by the fact that the RFC connection between the frontend graphics layout editor and the calling screen painter program at the backend cannot be set up.
Possibility 1: Route permission denied
In the trace file dev_eusp<Process Id> of the graphics layout editor you find the entry "ERROR in RFCMgr_accept: not accepted", and in the RFC trace file dev_rfc.trc you have an entry of the form "ERROR route permission denied (<Front-Id> to <BackId>,<Service>)".
If there is a firewall between frontend computer and application
server, you need to decide whether the port for the RFC of the graphical layout editor can be released here (see Solution 1 below).
In case no firewall exists between the frontend computer and the application server, in its route permission table, the SAProuter contains either no entry for the frontend computer, on which the graphics layout editor is started, or the entry says that the link is saved by a password.Since the connection is denied, the graphics editor processes exits again, and the screen painter switches to the alphanumeric layout editor.
Possibility 2: Service 'sapgw<ServiceId>' unknown
In the trace file dev_eusp<ProzessId> of the graphics layout editor you have the entry "ERROR in RFCMgr_accept: not accepted", and in the RFC trace file dev_rfc.trc you have an entry of the form "ERROR service 'sapgw<ServiceId>' unknown".
The service sapgw<ServiceId> (for example, sapgw00) is not known on one of the computers participating in the RFC communication because the corresponding entry is missing in its service file. The affected computer can be the frontend computer or the gateway computer.
Possibility 3: The system parameter gw/cpic_timeout value is too low
This system parameter determines how many seconds the gateway is waiting for the RFC connection to be set up.In case of a high network load, the default value of 20 seconds is too small with the result that the connection cannot be created on time.Here the graphics layout editor process also exits with the trace file entry "ERROR in RFCMgr_accept: not accepted".
Possibility 4: System parameter abap/no_sapgui_rfc set
The profile parameter abap/no_sapgui_rfc of the system is set (that is, it has a value not equal to space or 0).This prevents the program of the graphics layout editor from being started with RFC at the frontend.
Possibility 5: Unnecessary authorization check
The error message "No RFC authorization for user xxxxxx" is generated although the check of the RFC authorization was deactivated by profile parameter auth/rfc_authority_check (value = space or 0). The problem is caused by a program error, that ignores the value of the profile parameter let during the call of the RFC authorization check (see Note 93254). This error can occur as of Release 4.5.
Solution
ad 1) If a Firewall is installed between frontend computer and the application server, you need to decide whether the port for the RFC link of the graphical layout editor shall be released in the firewall. This is port 33nn, where nn is the 2-digit system number of the SAP application server. As of Release 3.1G, the graphical layout editor needs an RFC link for communication with the application server in addition to the already existing linkof the SAP GUIs. Such a second link is not allowed by the firewall in general because it would contradict the security concept (password protection, logging of the connection).
If no firewall exists, you should check whether the frontend computer can be added to the route permission table or whether the password option can be removed from out of the available entry.
For details refer to chapter 4.4 of the attached Note 30289.
ad 2) Include service sapgw<ServiceId> in the service file.
Refer to Note 52959 for details.
ad 3) Increase value for system parameter gw/cpic_timeout. 60 seconds should be sufficent as a timeout limit.
ad 4) Set the system parameter abap/no_sapgui_rfc to space or 0
Start the application server so that the new parameter value comes into effect.
ad 5) Import the Support Package specified in the attachment for the release in question or implement the advance correction in the source code as described in the attached correction instructions.
As a workaround, assign RFC authorizations as described in Note 93254.

Cause for routing delay

I have a motor control design on my spartan 6 lx9 device. As my design grew routing delays became large, which is normal
as i understand.
I was wondering what is the cause for the routing delay. Is ist the actual time the signal needs in the fpga to
traverse the distance between the gates(traveling at some percentage of c)? If so, for a routing delay of 1ns this would mean
a routing lenght between gates of around 300 cm (assuming v=c) which seems like to much..

Short answer: RC time constants due to FETs (likely). I say "likely" because I cannot find, in a very short attempt, any Xilinx documentation on how their routing matrix works at the lowest level.
Routing matrix
This is an FPGA. Unlike an ASIC, general purpose routing is configurable, and that configuration as far as routing is concerned is achieved with active elements controlled by SRAM bits, such as muxes, FETs. It is not done with little nano-creatures spooling and unspooling wire within the FPGA based on your bitstream. Consequently, to get from one side of a large FPGA to the other, using the general purpose routing, can take orders of magnitude longer than it would take light to traverse the same distance in free space.

Hello congratulations for the work you have been developing. The iCREATE has helped me greatly improve my Mac and better understand some applications. Recently my iPhoto has given me problems and I do not realize what is happening. When I double click a p

Hello congratulations for the work you have been developing. The apple support has helped me greatly improve my Mac and better understand some applications. Recently my iPhoto has given me problems and I do not realize what is happening. When I double click a photo it does not appear ... or rather the background is black and only the zoom window appears. How to solve this? I've done a restoration of the library, but the problem remains. Thanks and good job.

There are several possible causes for the Black Screen issue
1. Permissions in the Library: Back Up and try rebuild the library: hold down the command and option (or alt) keys while launching iPhoto. Use the resulting dialogue to rebuild. Include the option to check and repair permissions.
2. Minor Database corruption: Back Up and try rebuild the library: hold down the command and option (or alt) keys while launching iPhoto. Use the resulting dialogue to rebuild.
3. A Damaged Photo: Select one of the affected photos in the iPhoto Window and right click on it. From the resulting menu select 'Show File (or 'Show Original File' if that's available). (On iPhoto 11 this option is under the File -> Reveal in Finder.) Will the file open in Preview? If not then the file is damaged. Time to restore from your back up.
4. A corrupted iPhoto Cache: Trash the com.apple.iPhoto folder from HD/Users/Your Name/Library/ Caches...
5. A corrupted preference file: Trash the com.apple.iPhoto.plist file from the HD/Users/ Your Name / library / preferences folder. (Remember you'll need to reset your User options afterwards. These include minor settings like the window colour and so on. Note: If you've moved your library you'll need to point iPhoto at it again.)
If none of these help:
As a Test:
Hold down the option (or alt) key key and launch iPhoto. From the resulting menu select 'Create Library'
Import a few pics into this new, blank library. Is the Problem repeated there?

Cause for ORA-21000?

Hello,
What is usually the cause for the following error?
ORA-21000: error number argument to raise_application_error of -21000 is out of range
Any help is appreciated.
Thanks.

I may be wrong but this looks like to me that your application raised an error and the number argument was out of the proper range (-20000 to -20999).
Have the application administrator check the code.
ORA-21000 error number argument to raise_application_error of stringstring
is out of range
Cause: An attempt was made to specify a number not in the allowed range.
Action: Use an error number in the range of -20000 to -20999, inclusive.
ORA-06512 at stringline string
Cause: Backtrace message as the stack is unwound by unhandled exceptions.
Action: Fix the problem causing the exception or write an exception handler
for this condition. Or you may need to contact your application
administrator or database administrator.
Regards
Tim

Cause for the sudden shutdown of Essbase?

Similar Messages

Maybe you are looking for