RAM install leads to weird problems

I installed extra RAM in my iBook G4 about 2 weeks ago. Since then everything has sort of been acting up, especially Mail, Safari, and Photoshop, as they quit frequently. I also have received 4 error messages saying that OSX (the operating system, not a program) has unexpectedly quit and I must restart my computer??? Needless to say, I am freaking out.
Has anyone heard of such a thing?!
Anything would be greatly appreciated.
Thanks,
Nancy
iBook G4 Mac OS X (10.4.4)

Hi Nancy,
Your iBook is having what is known as a Kernel Panic. Bad memory can cause these symptoms and seeing that these issues started after you installed the memory it is reasonable to assume that the memory is at fault.
When you remove the memory does everything operate as it should? If it does then you will need to contact the place where you bought the module and ask for a replacement.
RD

Similar Messages

Weird problems with 2007 15" MBP after installing new HD, any solution?

Folks-
For a couple of months my machine has been really weird.
(1) Safari will not work. Firefox does, other internet apps do, but no Safari.
(2) everything is ever slower. Spinning beachballs constantly.
(3) won't remember home wifi network. It remembers the pw, but must select the network
(4) won't sleep when scheduled, only when closed or immediately commanded to sleep.
I would say that these weird problems surfaced after I installed a new optical drive, after I upgraded to 10.7, etc, except that the main problems are absent when I start up from the old HD externally mounted (the refusal to sleep when scheduled is also present statring from the old HD).
This could indicate some wierd driver thing with the new drive, or a system software event I didn't notice or one of these "malware" things, right? Maybe?
Any ideas for how to troubleshoot this would just rock.
Thanks!

Since you have your old hard drive here's a suggestion:
Step One: Boot from the external drive. Restart the computer and after the chime press and hold down the OPTION key until the boot manager appears. Select the icon for the external drive then click on the downward pointing arrow button.
Step Two: New Hard Drive Preparation
1. Open Disk Utility in your Utilities folder.
2. After DU loads select your new internal hard drive (entry with the mfgr.'s ID and size) from the left side list. Note the SMART status of the drive in DU's status area. If it does not say "Verified" then the drive is failing or has failed and will need replacing. Otherwise, click on the Partition tab in the DU main window.
3. Under the Volume Scheme heading set the number of partitions from the drop down menu to one. Set the format type to Mac OS Extended (Journaled.) Click on the Options button, set the partition scheme to GUID then click on the OK button. Click on the Partition button and wait until the process has completed.
4. Select the volume you just created (this is the sub-entry under the drive entry) from the left side list. Click on the Erase tab in the DU main window.
5. Set the format type to Mac OS Extended (Journaled.) Click on the Options button, check the button for Zero Data and click on OK to return to the Erase window.
6. Click on the Erase button. The format process can take up to several hours depending upon the drive size.
Step Three: Clone the old drive to the new drive
1. Open Disk Utility from the Utilities folder.
2. Select the destination volume from the left side list.
3. Click on the Restore tab in the DU main window.
4. Check the box labeled Erase destination.
5. Select the destination volume from the left side list and drag it to the Destination entry field.
6. Select the source volume from the left side list and drag it to the Source entry field.
7. Double-check you got it right, then click on the Restore button.
Destination means the new internal drive. Source means the old external drive.
Step Four: Open the Startup Disk preferences and select the new internal volume. Click on the Restart button. You should boot from the new drive. Eject the external drive and disconnect it from the computer.

Weird problems with OSX Tiger

I'm with a weird problem with my OS Tiger. I have a G4/400 AGP Graphics with a Fastmac 1.5GHz processor upgrade, 1 GB RAM, 128MB video card, USB 2.0 card and a Sonnet serial ATA card. I have two HDs: one of 80GB and another one with 250GB (serial ATA) connected to the serial ATA card.
I have installed OS X Tiger in this serial ATA HD. Some weird things are happening since then. Sometimes when I shutdown my Mac, the delay is too long, all the icons disappear and the spinning wheel cursor remains in the screen for a long time until the Mac shuts down.
Sometimes when I try to open some applications, the same thing happens, the delay is long. And it happens too when I try to quit some applications. The sintom doesn't follow a rule - sometimes happen and other times it don't happen. And when I hit optioncommandesc to force quit, the application appears in the list as 'not responding', and even when I force quit it doesn't quit at all.
I already have checked the disk permissions, I have runned MacJanitor, but the problem is still there.
Any idea?

Hello! Long delays are often caused by corrupt disk directories. I'd first boot from the install Tiger disc and run the repair disk routine and then repair permissions AFTER rebooting from the hard drive. Other than that I'd get Diskwarrior to keep the directories in good shape. Tom

Weird problem with Macbook Pro 15" and Asus PB278 monitor

Hi there
I recently bought a brand new MacBook pro 15" the one with a dedicated nvidia 750 vid card. However I'm facing weird problems while connecting it to a external monitor Asus PB278 (1440p monitor). I use a mini display port to display port cable.
My problem is: Sometimes it works perfectly, but then if I put the laptop to sleep, sometimes it won't recognise the screen at wake up, at first I tried to restart the system, power on and off the monitor, connecting and reconnecting the cable... nothing worked. I even bought a expensier cable thinking it was probably a low quality cable. I found that then only way to fix this is to connect the monitor with a mini display to HDMI cable I have (won't support over 1080p), and then put the mini display to display port cable again... it is freaking bizarre.
This is very frustrating, I live outside the US and while the retailer will honor the guarantee I'm not sure if this is a Software or Hardware problem, It will take them about 3 weeks to replace my system which is unfortunate due to I have plenty of work to do. I don't want to send it on guarantee just to find out hey... display recognition is broken again. My questions are:
Is there a way to know if this is a hardware or software problem?
I've heard Yosemite is having some issues regarding external displays, is this one of those?
Have you found yourself experiencing this problem? Could you fix it?
Sorry if my english is a bit weird, thanks in advance.

Hi Gatobolo,
Thank you for contributing to the Apple Support Communities.
It appears that you've discovered unusual behavior with your MacBook Pro and an external display, where you need to temporarily connect a different display adapter before you can use your Asus PB278 again.
I can offer some additional tips to help resolve or further isolate the issue you're seeing.
First, try the following resets to see if they eliminate the behavior:
You can reset the Mac's parameter RAM and SMC.
Next, if the issue occurs again, try restarting your Mac into Safe Mode:
Start up in Safe Mode.
From the Apple () menu, choose System Preferences.
Choose Displays from the View menu to open the preferences pane.
Select any resolution and refresh rate that your display supports.
Restart your computer.
You can find the steps above in this article:
Apple computers: Troubleshooting issues with video on internal or external displays - Apple Support
If your display is recognized in Safe Mode, or after restarting again, the issue may be due to a software conflict.
Another suggestion mentioned in the article above is to try a different type of display adapter, such as a Mini DisplayPort to Dual Link DVI adapter.
If the issue persists, you can also back up your data, erase your hard drive, and reinstall a fresh copy of OS X Yosemite.
OS X Yosemite: Erase and reinstall OS X
If the issue still occurs after a clean install, troubleshooting the hardware may be necessary.
Best Regards,
Jeremy

Slow boot after installing SSD drive + Grub problem + Kernel panicks

Hey
So i just got a Samsung 840 EVO, and was ready to see my system fly, so i installed Arch on it, the instalation was kinda weird, since im in the middle of some major developing for a startup i couldnt risk to lose time configuring my all system so what i did was this:
Install Arch on the SSD (/root on sdb1) while keeping my other Arch install (/root on sda5) and sharing the /home and /swap (on sda6 and sda7) between both systems, i installed grub on sdb also because i didnt knew what to do
So now when i boot the laptop i get the grub from sda wich only has Old Arch and windows, if i press f9 at boot and boot from the ssd i go to sdb grub that has Old Arch, New Arch and Windows, since the SSD was instaled via a caddy it doesnt get recognized in the BIOS, but strangely i get 2 Universal Hard Drives (hdd and sdd) when pressing f9
So first question is, should i reeinstall grub on sda or is there a way to put the SDD as primary?
The other problem is that systemd-analyze is giving me worst times than with the hdd, and i dont see a huge improvement with the SSD as i should. Is it because i have /home /swap on the hdd? I have read https://wiki.archlinux.org/index.php/Solid_State_Drives and did as told.
systemd-analyze
Startup finished in 1.820s (kernel) + 1min 30.406s (userspace) = 1min 32.226s
systemd-analyze output (only top lines)
1min 1.093s ntpdate.service
4.320s systemd-modules-load.service
1.159s mysqld.service
986ms [email protected]
967ms [email protected]
609ms [email protected]
511ms [email protected]
359ms lvm2-monitor.service
systemd-analyze critical-chain
graphical.target @1min 30.156s
└─multi-user.target @1min 30.154s <------------- a lot of time
└─ntpd.service @1min 7.575s +9ms
└─network.target @6.473s
└─[email protected] @5.962s +511ms <------------- a lot of time
└─basic.target @5.948s
└─timers.target @5.948s
└─systemd-tmpfiles-clean.timer @5.948s
└─sysinit.target @5.942s
└─systemd-backlight@backlight:acpi_video1.service @8.148s +59ms <------------- a lot of time
└─system-systemd\x2dbacklight.slice @5.646s
└─system.slice @155ms
└─-.slice @154ms
laptop specs:
Intel(R) Core(TM) i5-2430M CPU @ 2.40GHz
8 GB RAM
512 GB HDD
250 GB 840 EVO
Last edited by archoriano (2014-08-29 01:19:22)

You did not share what the kernel panic says, but I guess it has to do with your root file systems not mounted correctly. If it happens like 75% of the time, sounds like you are using /dev/sdax and it gets enumarated differently? Use UUID's instead.
Your "slow boot" is a seperate problem, see the thread you linked too for how to fix that.
Its a fresh install but i alredy have DE and programs, i used Helmuth script to install all the stuff, just so i didnt forget to install stuff.
No idea what this means, but if it is some third party script downloaded off the internet - use them only if you understand exactly what it does, else the chances are you will run into some problems with no idea how you got there. For simply keeping a list of packages to install, put them in a text file and pipe them into pacman (see also here.

Is the RAM installed correctly in my 'new' Mac Pro 1,1???

Hey folks, just picked up a used Mac Pro 1,1 2x2Ghz on ebay earlier this week to replace my 2Ghz dual core G5..
Im looking at adding some more RAM to the machine and am wondering if the person I bought this from even has the ram installed correctly.
When I opened it up, the 2x2GB sticks were both in the first two slots in the bottom memory tray. Luckily I had some RAM I planned on putting in it right when I got it out of the box (and then found out my 4GB of DDR2 SDRAM doesnt work with it hehehe), which required me to go look it up online before I even plugged the thing in, so I moved the tray with the RAM in it to the upper slot like the article I read said it was supposed to be..
Now I just read the Apple support doc that pops up when you click the Upgrade Memory link in the Memory tab in System Profiler and am confused even more..
Am I supposed to have both of those FB-DIMMs on the upper tray or do I need to move one of them to first slot of the lower tray??
Also, I noticed in the installation pictures, the top tray is pictured as being installed upside down, so the RAM in both trays is right above/below one another, but both of mine are right side up..
My Mac looks like everythings fine, system profiler shows me both DIMMs in tray A and isnt complaining... Gave Logic Pro a nice run the other night and havent really run into any problems or a KP yet.. Been reinstalling my recording software like crazy and no problems yet either..
Just wanted to make sure how its really supposed to be installed in case I could possibly end up frying something down the line..

See even the first two links posted have conflicting information.. According to OWC, I should have one 2GB stick on each riser, but that second link with the memory configuration pictures, the last config for the 4GB shows both 2GB sticks on riser A (thats actually the doc I was referring to earlier that I looked at when I first got the Mac) so I figured I was ok.. None of those options show one stick on each riser..
And again in regards to the way the riser is installed.. Apples own memory upgrade doc does indeed show the top riser installed upside down so the heat sinks are facing each other.. But every actual picture Ive seen, and OWC's own installation video shows them both installed right side up.. Now that I think about it after watching the OWC video, the riser cards are keyed, so I dont see how it would fit upside down in the first place..
I dont know I guess Ill just leave it like it is. I should be getting a pair of 2GB DIMMs hopefully in another week or so when money permits so Ill have both risers in use anyways..
Maybe mine is a later 2007 version of the 1,1 or something and there was a revision done??? Wish you could tell the actual date by serial number instead of just the timeframe the model was in existence hehehe.

I just had more ram installed in my 2009 mac mini and now there is no audio at all.

Hi all,
I have a late 2009 Mac Mini which I update to mavericks. This was not a great idea. The performance has been aweful since upgrading. I finally looked into adding RAM. I was told by the Genius at my local store to buy RAM on line and bring it back to the store for install. I had the Ram installed today and I am satisfied that things function much faster now.
The problem now is that the computer does not make any noise. I have speakers plugged into the headphone jack but no noise comes out. When the system boots up, there are no beeps or tones audible. The speakers were all working earlier today when I unplugged everything to take the mini to the store. I also plugged the speakers jack into my phone and they work. I was able to connect a bluetooth speaker and play music through it.
I have tried to reset the PRAM but I"m not sure if I was successful. The instructions I have read for PRAM reset say hold keys until second chime is heard. I heard no chimes at all.
I am a novice when it comes to computers but I am good at following detailed instructions.
Any help would be graetly appreciated!

Yes, this was an Apple retail location.
I made an appiontment thinking that they would sell and install the RAM. When I got there, the genius looked up the specs for my mini and said they did not sell what I needed. He explained that the mini was older and out-dated. He looked up the specs on what RAM i needed and suggested that I purchase it elsewhere and bring it back for them to install. He suggested that I purchase a new computer but I couldn't justify spending $600 or more. I am a very light user and would only be wasting money on a newer set up.
It was when I returned that I was informed (by a different tech) that Apple would not be responsible for any damage that might occur during the replacement.
I decided to proceed anyway thinking that an apple tech was less likely to do damage than I was.
After taking it in the back and swapping the chips, he brought it out, plugged it in and proceeded to open a bunch of Ram hogging apps, graphing software, and internet sites. I was happy to see that the performance was greatly improved and the spinning ball was not dominating the system.
After I hooked it back up at home and tried to play some music, I realized that there was no sound.

SAP GUI 7.10p15 weird problem on FB70

Hi all,
We upgraded SAP GUI 7.10 to patch level 15 from patch level 14 using the install server on our Windows XP machines. A weird problem seems to appear since then on FB70. You press once or twice the ENTER key, without filling any field on the screen and the GUI stays on a busy state forever (trying to constantly redraw the screen as to show an error message on missing account number). It results to 100% CPU usage on the client (Windows XP machines, tried on Windows 7 also with same result) and seems to also stress the SAP system a bit. The only way to stop that behavior is to use the Windows task manager and kill the busy window. I have not seen this behavior before and can't reproduce it in any other transaction until now.
I got access on a machine that was still on patch level 14 and works just fine. I did the upgrade and the same behaviour (busy, 100% CPU) instantly appears. Oddly enough, this behavior does not occur if I run FB70 throught the debugger (/h) in any case.
Have you seen something like this or do you have any clue why that weird behavior might appear?
Thank you very much in advance for any insight

Hello Artemios,
Yes, this seems to be a know issue with Patch 15. Please open a ticket on BC-FES-GUI to get a fix for that or wait until Patch 16 is released.
Kind regards,
Martin

Weird problem involving my external hard drive - help please!

I recently got a formac mini 120 gb firewire hard drive, which had been working fine with my g4 quicksliver.
i then went to a friends (g5 machine) with my drive and he put some data on it - bought it back to mine and managed to re connect the drive and take the data - no problem - very happy.
I recently gave my drive to another friend using a g5 and when it came back, nothing - i don't get the drive symbol appearing. turned the comp on and off many times and tried re-connecting etc still no drive appearing.
Then i took the drive to my friend with a mac lap top power book. connected there - working fine. Baffling. was happy that my data can still be accessed.
I know it's not the firewire cable because i can get power to the drive - i can see the red light at the fron on.
Can anyone help with this weird problem?
Thanks

Thought you could use this info about getting FireWire to work!
First, you should always Repair Permissions in Disk Utility before and after any update; I would do that now. If you installed your update with FireWire plugged in, your Mac may not recognize it anymore.
Try resetting your FireWire ports by disconnecting all FW devices, shut down your Mac and unplug it from AC power (wall socket) for 30 minutes. plug it back in and try FW.
If that did'nt work, download the combo update from this site (yours may be corrupt), not Software Update, disconnect all firewire + USB devices except keyboard + mouse, Repair Permissions, re-install update, Repair Permissions again + try. Yours might be the 10.4.10 Combo update. I have no idea since you did not fill out your specs. fully when you signed in to this site. Others reading, download the Combo that applies to your system. This link is for PPC Macs not Intel Macs.
If that still did'nt get it Zap the PRAM. While restarting Mac hold down the following key combo Command-Option-P-R. Keep holding those keys down till you hear the second start-up chime, then release.
For those of you with Macs that are not PowerBooks or iBooks, a bad internal battery can cause FireWire to not be recognized, so make sure it's good! Also, here is Apple doc.#88338 on getting FireWire to work.
Good Luck!
Cheers!
DALE

I have a 2009 Macbook Pro with 1T hdd 8GB Ram and ran Maverick without problem...Yosemite installation has me completely frozen, nothing works but the spinning ball...I had to force shutdown last night, and haven't turned it on again...what do you ad

I have a 2009 Macbook Pro with 1T hdd 8GB Ram and ran Maverick without problem...Yosemite installation has me completely frozen, nothing works but the spinning ball...I had to force shutdown last night, and haven't turned it on again...what do you advise? During installation emptied cache, etc. Backed up using time machine, fortunately.

Try these in order testing your system after each to see if it's back to normal:
1. a. Resetting your Mac's PRAM and NVRAM
    b. Intel-based Macs: Resetting the System Management Controller (SMC)
2. Restart the computer in Safe Mode, then restart again, normally. If this doesn't help, then:
Boot to the Recovery HD: Restart the computer and after the chime press and hold down the COMMAND and R keys until the Utilities 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.
3. Repair the Hard Drive and Permissions: Upon startup select Disk Utility from the Utilities menu. Repair the Hard Drive and Permissions as follows.
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 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.
4. Reinstall Yosemite: Reboot from the Recovery HD. Select Reinstall OS X from the Utilities menu, and click on the Continue button.
Note: You will need an active Internet connection. I suggest using Ethernet if possible
            because it is three times faster than wireless.
5. Reinstall Yosemite from Scratch:
Be sure you backup your files to an external drive or second internal drive because the following procedure will remove everything from the hard drive.
How to Clean Install OS X Yosemite
Note: You will need an active Internet connection. I suggest using Ethernet if possible
            because it is three times faster than wireless.

8GB of RAM Installed, only 4GB detected/used by BIOS/Windows 7 (with P67A-GD55)

Let me start off by saying that I'm not very good with computers. At all. I know a little bit about them, but I am by no means an expert. That said, I have 8GB of RAM installed on my motherboard, spread out across 4 sticks. However, upon looking at my BIOS and my Windows Resource Monitor, it declares that I only have 4GB of RAM installed and usable. This is what I know so far:
- This issue has been prevalent as long as I've had my computer, and by extension my motherboard and my RAM sticks, so this issue isn't recent.
- I do have a 64bit version of Windows 7. I've checked and double-checked, and I'm 99.5% positive that it is.
- Speccy, a 3rd party program designed for checking system specs, declares that I do, in fact, have 8GB installed.
- I don't think that the RAM is bad because the BIOS still does pick up on different statistics of the RAM that are in the slots; it just fails to register the actual fact that they're there.
System Specs:
OS: Windows 7 64bit SP1
CPU: Intel Core i5 2500K @ 3.30GHz
RAM: Patriot PSD32G133K 4x2GB DDR3 @ 498MHz
Motherboard: MSI P67A-GD55 P67 LGA 1155
HDD: 977GB SAMSUNG SAMSUNG HD103SJ ATA Device (SATA)
Optical Drive: LG DVDRAM GH24NS50 ATA Device
GPU: AMD Radeon HD 6870 1GB VRAM
PSU: Cooler Master 750 Watt
BIOS Version: E7681IMS V1.5
Now this is where it gets interesting: My motherboard has 4 DIMM slots for the RAM, and the motherboard (I assume by default) works in dual-channel mode. This means that DIMM 1 and 3 work together and so do DIMM 2 and 4, which most of you probably understand. However, filling up all 4 slots only gives me half the RAM. So I remove the RAM from slots 2 and 4, and it results in all 4GB of RAM being detected. Then, I add in each other RAM stick one at a time, and it fails to register both. So I remove the RAM from slots 1 and 3, and keep the RAM from slots 2 and 4, and it ends up in all 4GB being registered.
I feel like the answer should be directly in front of me, but from endless Google searches and posts on other forums, I have ended up at a dead end. I'm completely clueless, so I could really use some help.
Any and all help would be appreciated.
Also, if this is the wrong forum for this, feel free to move it wherever.

Quote from: Jack on 28-August-11, 01:11:56
What is your current UEFI/BIOS Version?
The usual cause of such problems is (apart from bad memory slots or a defect of the processor's memory controller) a contact problem between the boards CPU Socket contact pins and the CPU's contact pads. Broke or bent pins are one explanation, in other instances a heatsink that is fastened to tight can also cause such issues.
I'll have the BIOS version up in a moment, but I'll see about diagnosing if one of those problems might just be what is my problem. Any tips on doing that?
Also, BIOS version is up in the OP now.

StarForce GF FX 5700: weird problem

Since I bought this geforce I used the 52.14 drivers from MSI. After having troubla with a game, I had to update my drivers. After installing the 56.72 ForceWare-drivres from nVidia, I had a quite weird problem.
After booting my PC, I started Battlefield Vietnam, and got this: The menu
in-game (normally it's even worse)
I tried a few other games, but they all had the same problem.
I rebooted, restarted BF:V and everything was normal again.
But, with those newer drivers, I had the same thing every day. If I worked in Windows too long, I had to reboot before I could play my games (descent).
A few weeks later someone told me that the weird colors where caused by overheats.
Down-clocking (starting from the standards, I never over-clocked the card) didn't solve my problem. Then I realized that everything worked perfect with the 52.14-drivers. I re-installed the drivers from the disc (52.14), and yes, my problem didn't exist any longer.
The problem is gone (by using the 52.14), but I can't update my drivers, which is necessary to play certain games, without having to reboot to play.

i put a post up about my problem with my fx5700 and bf1942 earlier, but no one has responded as of yet. the 1st screen that was posted (all red) thats EXACTLY how my screen looks. i've tried the drivers that came with the card (dont remember the version off the top of my head) and the latest drivers both showing the red screen. did anyone come up with a resolution for this situation?

SD Query Install - No Entry Found Problem

Gurus,
I have this weird problem in Bex. I installed around 15 Business Content SD query and transported to the assigned Z package. I was able to view the query and have data populated last week.
But recently when i tried to open a particular sales revenue query it says "No Entry Found". The strange thing is that i am able to see the query in the drill down infoarea list. Moreover i checked the query in RSRT1 and ABLE to run it.
Any idea about what is wrong? Even i tried to reinstall it but the same problem again for a particular query.
Shreya

Hi, if you have transport query just rightnow, then just close the screen and then again open RSRT and execute the query,,,
OR just check the system you are watching for data is proper(i.e. if you see the data in analyzer for PD and in RSRT for DV) or not, (Sometime it may be happend)
Just check it out users are same or not?
Regards,

Weird problem with role assignment in Portal

Hi,
In our newly installed Portal for eRecruitment Production System we encounter a weird problem with assigning roles to users.
When I open User Administration and search for roles, it displays the Portal roles perfectly.
However, when I search for a user in User Administration and click on it when found, I am unable to find any roles to assign! So I am unable to find any roles, when I want to modify the assigned roles for a particular user, while the roles do exist and can be found on its own. How is this possible? Am I missing something here?
We have installed SPS 15 and use ABAP as user store. We have used reverse proxy and web dispatchers in this case.
Thanks in advance and best regards,
Jan Laros

Found some entries in the default trace from this morning:
#1.#005056A15F78006A000004F400006D310004520B11DB3CE8#1216107404407#com.sap.security.core.jmx.impl.CompanyPrincipalFactory#sap.com/tc~wd~dispwda#com.sap.security.core.jmx.impl.CompanyPrincipalFactory.static Set evaluateDatasourcesToSearchFor(String[] requestDatasourceIds,     String privateType, Locale locale)#JALAROS#58762##nun.efteling.nl_POP_9750151#JALAROS#581700b0524011ddc029005056a15f78#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Java###Error while connecting to remote producer {0}
[EXCEPTION]
{1}#2#PRODUCER_0KTHQ3YTJV#com.sap.security.core.persistence.remote.CommunicationException: Cannot display remote roles of selected producer. The producer has removed your consumer instance from their portal.
        at com.sap.portal.ivs.global.roles.RemoteProducerAccessImpl.sendToRemote(RemoteProducerAccessImpl.java:497)
        at com.sap.portal.ivs.global.roles.RemoteProducerAccessImpl.checkConnectivity(RemoteProducerAccessImpl.java:220)
        at com.sap.security.core.jmx.impl.CompanyPrincipalFactory.evaluateDatasourcesToSearchFor(CompanyPrincipalFactory.java:656)
        at com.sap.security.core.jmx.impl.CompanyPrincipalFactory.simplePrincipalSearchByDatasources(CompanyPrincipalFactory.java:3172)
        at com.sap.security.core.jmx.impl.JmxSearchHelper.getSimpleEntitySearchResult(JmxSearchHelper.java:74)
        at com.sap.security.core.jmx.impl.JmxSearchHelper.calculateSimpleEntityTable(JmxSearchHelper.java:1182)
        at com.sap.security.core.jmx.impl.JmxServer.calculateSimpleEntityTableByDatasources(JmxServer.java:1061)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
        at java.lang.reflect.Method.invoke(Method.java:391)
        at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)
        at javax.management.StandardMBean.invoke(StandardMBean.java:286)
        at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944)
        at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)
        at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:409)
        at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)
        at com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:258)
        at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)
        at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)
        at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:287)
        at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:776)
        at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)
        at com.sap.security.core.jmx._gen.IJmxServer$Impl.calculateSimpleEntityTableByDatasources(IJmxServer.java:717)
        at com.sap.security.core.wd.jmxmodel.JmxModelCompInterface.calculateSimpleEntityTable(JmxModelCompInterface.java:396)
        at com.sap.security.core.wd.jmxmodel.wdp.InternalJmxModelCompInterface.calculateSimpleEntityTable(InternalJmxModelCompInterface.java:443)
        at com.sap.security.core.wd.jmxmodel.wdp.InternalJmxModelCompInterface$External.calculateSimpleEntityTable(InternalJmxModelCompInterface.java:746)
        at com.sap.security.core.wd.umeuifactory.UmeUiFactoryCompInterface.getSimpleEntityTable(UmeUiFactoryCompInterface.java:471)
        at com.sap.security.core.wd.umeuifactory.wdp.InternalUmeUiFactoryCompInterface.getSimpleEntityTable(InternalUmeUiFactoryCompInterface.java:517)
        at com.sap.security.core.wd.umeuifactory.wdp.InternalUmeUiFactoryCompInterface$External.getSimpleEntityTable(InternalUmeUiFactoryCompInterface.java:894)
        at com.sap.security.core.wd.relaterole.RelateRoleComp.searchNewRoles(RelateRoleComp.java:259)
        at com.sap.security.core.wd.relaterole.wdp.InternalRelateRoleComp.searchNewRoles(InternalRelateRoleComp.java:282)
        at com.sap.security.core.wd.relaterole.AssignParentRolesView.onActionSearchNewRoles(AssignParentRolesView.java:215)
        at com.sap.security.core.wd.relaterole.wdp.InternalAssignParentRolesView.wdInvokeEventHandler(InternalAssignParentRolesView.java:261)
        at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
        at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
        at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:420)
        at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132)
        at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
        at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
        at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:313)
        at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:733)
        at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:668)
        at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
        at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
        at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73)
        at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:860)
        at com.sap.tc.webdynpro.portal.pb.impl.localwd.LocalApplicationProxy.sendDataAndProcessAction(LocalApplicationProxy.java:77)
        at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1257)
        at com.sap.portal.pb.PageBuilder.SendDataAndProcessAction(PageBuilder.java:325)
        at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:826)
        at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processPhaseListener(WindowPhaseModel.java:755)
        at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doPortalDispatch(WindowPhaseModel.java:717)
        at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:136)
        at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
        at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
        at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:313)
        at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
        at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
        at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
        at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
        at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
        at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
        at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
        at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
        at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
        at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
        at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
        at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
        at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
        at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
        at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
        at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
        at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
        at java.security.AccessController.doPrivileged(AccessController.java:180)
        at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
        at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
#1.#005056A15F780060000004FD00006D310004520C6A35F87C#1216113181849#com.sap.engine.services.security.roles.SecurityRoleReference##com.sap.engine.services.security.roles.SecurityRoleReference#J2EE_GUEST#0####399cb180524e11dd9849005056a15f78#SAPEngine_Application_Thread[impl:3]_37##0#0#Error#1#/System/Security/Audit/J2EE#Java###{0}: Authorization check for caller assignment to J2EE security role [{1} : {2}] referencing J2EE security role [{3} : {4}].#5#ACCESS.ERROR#service.naming#jndi_all_operations#SAP-J2EE-Engine#administrators#
#1.#005056A15F78005C00000C0500006D310004520C6A394185#1216113181992#com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImpl##com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImpl#J2EE_GUEST#0####39aa6d20524e11ddaee2005056a15f78#SAPEngine_Application_Thread[impl:3]_29##0#0#Error#1#/System/Server#Java###Runtime exception occurred while processing external JMX request [ JMX request (java) v1.0 len: 150 | src: 2 target-node: 9750150 req: getAttribute params-number: 2 params-bytes: 0 | ]
[EXCEPTION]
{0}#1#com.sap.engine.services.jmx.exception.JmxSecurityException: Caller J2EE_GUEST not authorized, only role administrators is allowed to access JMX
        at com.sap.engine.services.jmx.EngineAuthorization.checkMBeanPermission(EngineAuthorization.java:88)
        at com.sap.engine.services.jmx.auth.UmeAuthorization.checkMBeanPermission(UmeAuthorization.java:77)
        at com.sap.engine.services.jmx.JmxServerFrame.checkMBeanPermission(JmxServerFrame.java:98)
        at com.sap.engine.services.jmx.MessageClientSecurityWrapper.checkPermissions(MessageClientSecurityWrapper.java:76)
        at com.sap.engine.services.jmx.MessageClientSecurityWrapper.invokeMbs(MessageClientSecurityWrapper.java:38)
        at com.sap.engine.services.jmx.ClusterInterceptor.invokeMbs(ClusterInterceptor.java:196)
        at com.sap.engine.services.jmx.ClusterInterceptor.getAttribute(ClusterInterceptor.java:512)
        at com.sap.engine.services.jmx.MBeanServerInterceptorInvoker.invokeMbs(MBeanServerInterceptorInvoker.java:84)
        at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImpl.invokeMbs(P4ConnectorServerImpl.java:61)
        at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:64)
        at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:313)
        at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:199)
        at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136)
        at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
        at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
        at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
        at java.security.AccessController.doPrivileged(AccessController.java:180)
        at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
        at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)

I have this weird problem. I have an iPhone. Next to where it says "slide to unlock", there is a camera button that just appeared. Is there a way I can delete it?

I have a weird problem. I have an iPhone 3G. I just got the camera sliding button next to where it says "slide to unlock". Is there a way I can delete that then restore my original screen?

It actually says my iPhone is 3G Version 5.1.
Then you must have a 3GS, not a 3G. iOS5 cannot be installed on a 3G.
Either way, the camera icon cannot be removed. It gives you quick access to the Camera but not your Camera Roll without unlocking, assuming you're using a passcode.

RAM install leads to weird problems

Similar Messages

Maybe you are looking for