Serious log in issues.........graphics related??

hi everyone!
I am having a serious issue with logging in to my mac. The problem started when i began having problems with my graphics cards. I have 2 ati hd2600xt cards in my 8 core mac pro, and they have run 3 of my monitors with absolutley no problem before but then suddenly a few weeks ago when i started up my machine only one screen would start working. If I re booted the mac then it would see all 3 monitors and work fine thereafter. However today i turned on the mac and it wouldnt see the other 2 screens at all. i unplugged everything from the machine and made sure the card was in the slot correctly, and reconnected the screens, booted up and had the same issue. I then wondered if there was a firmware update for the cards so i hooked up one monitor and went on to the internet and found some newer firmware. I installed the firmware, it said click to restart machine, i done that and when it restarted it just hung for a few minutes, I thought it may have been writing firmware so i left it for 20 minutes and nothing happened. At this point i decided to take the card out of the machine, i did that and then it got me to the login screen, i enter my password and it goes to log me in, then takes me straight back to the login screen again. I tried to reset my password, and it does exactly the same thing. I then wondered if my user account had gone wrong so i booted from disc and went in to terminal and checked everything was still on the hd which it was. I have managed to log in to my account through my laptop on the network and i can browse through my files and folders just fine from there, i have copied files on to my laptop, its all there just fine. I tried to screen share and enter the password to my account but it wont let me in. strange how my laptop will let me in to the file structure with the same log in as on my 8 core but the 8 core wont let me in.
I even tried logging in in safe mode and it does the same thing.
Any ideas?
thanks
Pete Crossman

I am having a similar issue, but in my situation, my users cannot log in. All of my users are network users on Mini's. I am running 10.6.8 on my server. I have created users before with no issues, but have not done so in months. When I try to log the new user in, I get the following error:
xpchelper: Could not get path of user account (uid:1029) home directory:/Network/Servers/server.xxx.net/Volumes/Data/Users/username; error; The operation couldn't be completed. No such file or directory. Using home directory.
CFPreferences: user home directory at file://localhost/Network/Servers/server.xxx.net/Volumes/Data/Users/username/ is currently unavailable. User domains will be volatile.
Authorizationhost: error |-[homedirmounter mount NetworkHomeWithURL: attributes: dirPath: username:]|PremountHomeDirectoryWithAuthentication (url=AFP://server.xxx.net/Users/homedir= /Network/Servers/server.xxx.net/Volumes/Data/Users/username, name=username) returned 5.
I have no idea of what to do. I have verified that the user looks the same as my other users in WGM. The user's folder was created on the server. The user has access to the folder. I'm not sure what else could be wrong here.

Similar Messages

Serious log in issues after installing Lion Server

Hi all,
I am relatively inexperienced with software involving essentially anything technical, so you will have to pardon my ignorance.
I am currently trying to set-up a wireless network at home using Lion Server, and it would appear I have bitten off more than I can chew. I installed Lion Server on Tuesday, and have been battling with it ever since - attempting to use a 'We Got Served' guide to walk me through.
I installed the Server app on my iMac as I figured the 3 computers on the network would not require very much space, and so there would be little point in buying a whole new machine to run it from. Whilst I was having little luck in making it work as I had hoped - I have now managed to completely lock the iMac. Since it's installation I have had no issue logging in and out of my actual account on OSX, however earlier the computer froze following an Adobe update and I was forced to do a hard restart. However, when I attempted to log back in I now get the following error:
"You are unable to log in to the user account "xxxx" at this time.
Logging in to the account failed because an error occurred."
I have tried everything in my limited knowledge to rectify this, and nothing works it would seem. I've read examples of this happening when trying to log into the actual server app, or where the hard drive is corrupt on the machine itself - this seems to be a hybrid of the two.
I can no longer open the computer in Safe Mode, however when I go into Disk Utility all disks when verified appear to be absolutely fine with disc repair making no difference. The only available drive is now listed as a Server drive so I cannot even re-install Lion on there.
This is causing me much distress as I can as far as I can tell not only log into my computer, but can do nothing to repair the issue bar erasing everthing from it. There is a lot of important data on there and I am confident that it is not actually corrupt, however Server seems to have just locked it completely.
Help would be much appreciated!

I am having a similar issue, but in my situation, my users cannot log in. All of my users are network users on Mini's. I am running 10.6.8 on my server. I have created users before with no issues, but have not done so in months. When I try to log the new user in, I get the following error:
xpchelper: Could not get path of user account (uid:1029) home directory:/Network/Servers/server.xxx.net/Volumes/Data/Users/username; error; The operation couldn't be completed. No such file or directory. Using home directory.
CFPreferences: user home directory at file://localhost/Network/Servers/server.xxx.net/Volumes/Data/Users/username/ is currently unavailable. User domains will be volatile.
Authorizationhost: error |-[homedirmounter mount NetworkHomeWithURL: attributes: dirPath: username:]|PremountHomeDirectoryWithAuthentication (url=AFP://server.xxx.net/Users/homedir= /Network/Servers/server.xxx.net/Volumes/Data/Users/username, name=username) returned 5.
I have no idea of what to do. I have verified that the user looks the same as my other users in WGM. The user's folder was created on the server. The user has access to the folder. I'm not sure what else could be wrong here.

I get two kinds of crashes whenever I'm doing anything graphics-related...

I think. I think it's got something to do with graphics-related. But I don't know. Here's what happens.
Sometimes I'll be in iPhoto working on my photos. All of a sudden, the screen will go dim and I'll get the message that goes like "You have to restart your computer at this time". This often kills my iPhoto database and I have to rebuild everything... which is killing my workflow.
Other times, I'll get this massive crash which I think dims the screen but also spills out tons of weird code and gibberish. If I remembmer correctly, some it has to do with "stacking error" and there's also some "debug" stuff. Not sure, can't remember, I'm at work right now. This is what I'd call a hard crash in that it's not even "friendly" like the crash above which at least tells you you crashed and need to restart.
In both cases, I have to push the power button for a few seconds to shut down and then power on again.
This also happens more frequently if I'm in iPhoto and I'm editing an image which then opens Photoshop CS2. I'll be working in CS2 and BAM, i get one of those crashes.
I'll also get these crashes sometimes even if I'm ONLY in Adobe Photoshop CS2.
I swear, if someone can help me with this, I'll put them in for Sainthood! These crashes are KILLING my iPhoto work.
I run DiskWarrior frequently, I repair permissions frequently, etc. But I'm just hunting and gathering for solutions. I haven't found a real cohesive "troubleshooting list" that might tell me if I have some hardware issues or what.
G5 1.8GHz (old model) Mac OS X (10.3.9) iPhoto 5.x and Adobe Photoshop CS2

Since you said you repair permissions and use a hard-drive repair utility, then I'd wager (guessing) you have bad RAM.
You can diagnose it, as long as you can repeat the kernal panic:
If you have more than one stick of RAM, then try taking one out and see if you get the panic. If not, put the other back in and try again for the panic. If you don't have more than one stick of RAM, there's no reliable way I know of to diagnose RAM...
Keep in mind that it's possible for the RAM slot itself to be bad. In this case, start over with the RAM in a different slot--just to make sure a slot isn't bad.
Generally, if you're getting kernal panics that you can't pinpoint to isolated operations, then bad RAM could be the culprit. I've gone through a bout of this myself.
**obviously you have to power off before changing RAM, and use precautions for static, such as a static strap, or grounding yourself before touching it. If none of that makes sense, then take it to a repair center.

Graphics related crashes since Yosemite on a 27' late 2013 iMac

Hello all,
My 27 inch late 2013 iMac with a NVIDIA GeForce GTX 775M 2048 MB started freezing or auto-rebooting since I updated to Yosemite.
Crashes would occur randomly and were sometimes accompanied by lots of red boxes on the screen.
These kind of crashes seem to have stopped happening but now shifted to almost everytime I fire up Launchpad or Expose (and once when I opened the notifcation center). The screen freezes for a couple of seconds and the system will reboot, prompting me with a graphics related error.
Because my searches on this issue come up empty I would like to ask if anyone can tell me whether or not this is a bug or a hardware related problem.
Thanks for any help
Maybe related: My iMac sometimes takes a more than usual amount of seconds to wake from sleep. The screen will turn on but remain black.

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.

IMac 27" Late 2013 Wi Fi Log in Issue

Hello everyone,
I apologize if my questions have been asked in the past. I'm completely new to the Apple Mac OS. I bought a new iMac 27" in the middle of 2014 and use it about once or twice a week and have had no issues to-date. I'm still in the process of learning though so my use of it is limited to basic emailing, web browsing and Skype.
In the last 2 weeks I have had problems logging into my Wifi network at home. It would not log on even after I had reset the modem. After trying and rebooting my iMac 3-4 times it would finally do so without changing anything in the it. I'm not sure what is causing it, but thought I would ask here.
What would be causing the log in issue to my Wi Fi network?
Do I need to be concern with the findings in the Etre check?
Startup after logging in my password would take longer than usual...what would be causing it?
Here is the result from the Etre scan. I guess what concerns me is in red...and also if it shows the Wi Fi log in issue.
Thank you in advance for your help and advice.
EtreCheck version: 2.1.8 (121)
Report generated 9 February 2015 11:23:18 am AEST
Download EtreCheck from http://etresoft.com/etrecheck
Click the [Click for support] links for help with non-Apple products.
Click the [Click for details] links for more information about that line.
Hardware Information: ℹ️
    iMac (27-inch, Late 2013) (Technical Specifications)
    iMac - model: iMac14,2
    1 3.4 GHz Intel Core i5 CPU: 4-core
    32 GB RAM Upgradeable
        BANK 0/DIMM0
            8 GB DDR3 1600 MHz ok
        BANK 1/DIMM0
            8 GB DDR3 1600 MHz ok
        BANK 0/DIMM1
            8 GB DDR3 1600 MHz ok
        BANK 1/DIMM1
            8 GB DDR3 1600 MHz ok
    Bluetooth: Good - Handoff/Airdrop2 supported
    Wireless: en1: 802.11 a/b/g/n/ac
Video Information: ℹ️
    NVIDIA GeForce GTX 780M - VRAM: 4096 MB
        iMac 2560 x 1440
System Software: ℹ️
    OS X 10.9.5 (13F34) - Time since boot: 0:24:23
Disk Information: ℹ️
    APPLE SSD SD0128F disk0 : (121.33 GB)
        EFI (disk0s1) <not mounted> : 210 MB
        Boot OS X (disk0s3) <not mounted> : 134 MB
        Macintosh HD (disk2) / : 1.11 TB (1.04 TB free)
            Encrypted AES-XTS Unlocked
            Core Storage: disk0s2 120.99 GB Online
            Core Storage: disk1s2 999.35 GB Online
    APPLE HDD ST1000DM003 disk1 : (1 TB)
        EFI (disk1s1) <not mounted> : 210 MB
        Recovery HD (disk1s3) <not mounted> [Recovery]: 650 MB
        Macintosh HD (disk2) / : 1.11 TB (1.04 TB free)
            Encrypted AES-XTS Unlocked
            Core Storage: disk0s2 120.99 GB Online
            Core Storage: disk1s2 999.35 GB Online
USB Information: ℹ️
    VIA Labs, Inc.          USB3.0 Hub
        VIA Labs, Inc.          USB3.0 Hub
            Seagate Backup+ SL 2 TB
        EFI (disk3s1) <not mounted> : 210 MB
        Seagate Backup Plus Drive (disk3s2) /Volumes/Seagate Backup Plus Drive : 2.00 TB (1.82 TB free)
        Recovery HD (disk3s3) <not mounted> [Recovery]: 650 MB
            Initio   INIC-3609
    Apple Inc. FaceTime HD Camera (Built-in)
    Apple Inc. BRCM20702 Hub
        Apple Inc. Bluetooth USB Host Controller
    Logitech Inc. Logitech USB Headset H340
    Apple, Inc. Keyboard Hub
        Apple Inc. Apple Keyboard
    VIA Labs, Inc.          USB2.0 Hub
        VIA Labs, Inc.          USB2.0 Hub
Thunderbolt Information: ℹ️
    Apple Inc. thunderbolt_bus
Gatekeeper: ℹ️
    Mac App Store and identified developers
Startup Items: ℹ️
    ProTec6b: Path: /Library/StartupItems/ProTec6b
    Startup items are obsolete in OS X Yosemite
Launch Agents: ℹ️
    [loaded]    com.google.keystone.agent.plist [Click for support]
Launch Daemons: ℹ️
    [loaded]    com.adobe.fpsaud.plist [Click for support]
    [loaded]    com.bombich.ccc.plist [Click for support]
    [loaded]    com.google.keystone.daemon.plist [Click for support]
    [loaded]    com.microsoft.office.licensing.helper.plist [Click for support]
User Launch Agents: ℹ️
    [failed]    com.spotify.webhelper.plist [Click for support]
    [not loaded]    jp.co.canon.Inkjet_Extended_Survey_Agent.plist [Click for support]
User Login Items: ℹ️
    iTunesHelper    Application (/Applications/iTunes.app/Contents/MacOS/iTunesHelper.app)
    Alfred 2    Application (/Applications/Alfred 2.app)
    Spotify 08-26-32-444    Application (/Users/[redacted]/.Trash/Spotify 08-26-32-444.app)
    Dropbox    Application (/Applications/Dropbox.app)
    Canon IJ Network Scanner Selector EX    Application Hidden (/Applications/Canon Utilities/IJ Network Scanner Selector EX/Canon IJ Network Scanner Selector EX.app)
    Speech Startup    Application (/System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecogn ition.framework/Versions/A/Speech Startup.app)
Internet Plug-ins: ℹ️
    FlashPlayer-10.6: Version: 16.0.0.296 - SDK 10.6 [Click for support]
    QuickTime Plugin: Version: 7.7.3
    Flash Player: Version: 16.0.0.296 - SDK 10.6 Outdated! Update
    EPPEX Plugin: Version: 3.0.5.0 [Click for support]
    Default Browser: Version: 537 - SDK 10.9
    SharePointBrowserPlugin: Version: 14.4.3 - SDK 10.6 [Click for support]
    Silverlight: Version: 5.1.20125.0 - SDK 10.6 [Click for support]
3rd Party Preference Panes: ℹ️
    Flash Player [Click for support]
Time Machine: ℹ️
    Auto backup: YES
    Volumes being backed up:
        Macintosh HD: Disk size: 1.11 TB Disk used: 75.54 GB
    Destinations:
        Seagate Backup Plus Drive [Local]
        Total size: 2.00 TB
        Total number of backups: 33
        Oldest backup: 2014-04-16 03:45:27 +0000
        Last backup: 2015-02-09 01:07:51 +0000
        Size of backup disk: Adequate
            Backup size 2.00 TB > (Disk used 75.54 GB X 3)
Top Processes by CPU: ℹ️
         3%    WindowServer
         2%    Safari
         2%    Google Chrome
         1%    fontd
         1%    coreaudiod
Top Processes by Memory: ℹ️
    481 MB    WindowServer
    309 MB    Airmail
    206 MB    mds_stores
    206 MB    Safari
    172 MB    Google Chrome
Virtual Memory Information: ℹ️
    27.13 GB    Free RAM
    4.39 GB    Active RAM
    1.08 GB    Inactive RAM
    1.75 GB    Wired RAM
    912 MB    Page-ins
    0 B    Page-outs
Diagnostics Information: ℹ️
    Feb 9, 2015, 10:58:33 AM    Self test - pass

Hi, Jiyujin.
Thank you for visiting Apple Support Communities.
I would need some clarification of the reference to log on and a little more information about the behavior to provide a better answer. However, here is a troubleshooting article that may help.
Wi-Fi: How to troubleshoot Wi-Fi connectivity
http://support.apple.com/HT202222
Cheers,
Jason H.

Send mail to the user who logged the issue

Hi,
As it is currently the mail goes to the key user, which is a business partner. That is an organization. However several users are maintained under a business partner.
So now the mail goes to all these users at a status change. However can we only have the user who logged the issue getting the mail. Can you please advice me on how to get this?
Thanks loads.
Keshi

Hi.. Thanks for all ur replies..
Yes we hv assigned the key user as a business partner which is an organization,, This is also and requirement,
But since the mail is activated as to the key user it goes to all the users in that group, under teh business partner.
But when configuring this came across the Partner, in which we selected it as key user. But there were also other partners as Creator,Reported by etc..
I tried using both these but again it didnt work. Can anyone suggest anything?
Yes, when u assign the key user as a business partner and assign several users to it you can send multiple mails to users
Any help on this is very much appreciated,.,
Thanks all for replying once again.
Keshi

Enterprise Portal Log off Issue for External User

Hello
We are facing a Enterprise Portal log off issue for one of our external users.
User is logged in and clicks on the "Log Off" link .
User is prompted as seen below:
Are you sure you want to logg off?
Choose Yes or No
Click on Yes and popup window goes away and nothing else happens.
These problems logg off issue problem happening on Internet Explorer 6 but from from firefox browser, its working.
Also popups are not blocked on IE.
EP version with SP level is EP 7.00 SP12.
Even though from Internet explorer 6, i can log in and log off with internal user.
Please advise for the log off problem .

Hello
I added the value ume.logoff.redirect.url =https://poqwas.synenco.com/irj/portal
on Config Tool Global Paramter settings.
Then restart the server.
But I am getting the same problem.when I login with external user ID, then make log off. Nothin Happen...
Please advise

LION screen sharing and remote log in issues

Hi,
In Snow Leopard I could access my iMac screen from my macbook and have the iMac restart and allow me to log in and continue to use the iMac.
In Lion I cannot access the log in screen remotely after a restart.
I need to go to the iMac and actually log into it with the keyboard before it will show up again on the network.
I tried to adjust the sharing preferences but nothing is allowing me to manage the iMac and restart it from a different machine.
Once I am logged in the screen sharing works fine. It's the log in issue that is not working for me.
thanks for any help in advance,
christos

i have not been able to get screen sharing to work at all, which has never been a problem for me. i'm registered as an authorized user on both computers, the passwords are correct, but it keeps telling me that the username/passwords don't work. and this is after the computers have already been "connected" using the exact same passwords and user name.

Dreamweaver log in issues

Is there anyone experiencing log in issues to B.C. through Dreamweaver? My log in issue started about a few hours ago. I can log in directly to B.C., but when I try to log in using the same name and password that I've always used, I can't log in.

Hey Legacys7, please PM me your login details and I'll test this for you. If you can access admin you should be able to log in to BC Extension. It's using the same auth system.
Cheers,
mario

WARNING: Canon Pro Printers and CS4 – Serious Colour Management Issue

Over the last four days (and over fifty prints) I have undertaken extensive and meticulous tests to identify the cause of a problem; namely that targets for profiling a new printer (a Canon Pro9000), printed with ‘no colour management’, were printing far too dark and with what appeared to be a colour cast.
I have conclusively eliminated the printer, the printer drivers, the Mac OS, corrupted preference files, corrupted user accounts, incorrect Photoshop settings, incorrect printer driver settings, the ‘sticky settings' issue, and user error as possible causes of the problem.
I can say with 95% certainty that my tests, conducted using Mac OSX 10.4.11, have proved the following:
That, printing to a Canon Pro9000 or iP4500, Photoshop CS4 does not print accurate targets suitable for producing profiles. This applies to both the No Colour Management (NCM) and the Printer Manages Colour (PMC) settings.
Photoshop CS and CS2 are not effected.
I did not test CS3.
Furthermore, colour managed prints (using the same accurate profile made in CS2), printed in CS2 and CS4, show subtle differences. This may not be an issue except in the most critical applications.
It is likely that the problem will not be confined to the two Canon printers above since many other Canon printers share the same driver architecture.
Reading posts and discussions on other websites would seem to indicate that this problem is also manifest with some Epson printers and may also effect Mac OSX 10.5.
I have to conclude, therefore, that Photoshop CS4 cannot be replied upon to print targets of sufficient accuracy to produce reliable profiles for a colour managed workflow.
The fact that this is only just being reported can be attributed to four factors:
That many CS4 users are continuing to use profiles made under older versions of Photoshop and have yet to make new profiles using CS4.
Some users may not immediately notice a problem, or may ascribe it to other causes.
Some users may take the line of least resistance and use a previous version of Photoshop to work around the problem.
Some users are still using the older versions of Photoshop not effected.
Eric Chan (of Adobe) has stated on another website that CS4 implemented some new APIs for printing and that this has given rise to some "minor glitches". If Eric Chan is correct, and Adobe changed the APIs in Photoshop CS4, this begs question of whether Adobe sufficiently tested CS4 before release ? If Adobe did not test their software, and therefore failed to identify this critical problem, this would suggest negligence on Adobe’s part. If Adobe identified the problem but then did not inform users that a potentially serious colour management issue existed this would suggest wilful or gross negligence.
It is not good enough to say that Adobe simply followed the ‘conventional’ path and ‘followed the rules’ regarding API implementation. The experience of end users does not correspond to a “minor glitch” and, in my case, has been extremely costly in terms of time (over five days in all), lost revenues, and materials. Furthermore, why should Adobe's customers be forced to use their valuable time diagnosing problems clearly of Adobe's creation – and actually admitted.
In UK law providers of goods and services (and this includes software) have to supply them as “fit for purpose”. Clearly, in terms of colour management, CS4 is not fit for purpose. Neither can Adobe hide behind its labyrinthine licensing terms since any exclusions would be ruled unlawful under the UK’s ‘Unfair Contract Terms’ Act.
My strong and unequivocal recommendation is that representatives from Adobe, Apple, and the printer manufacturers meet together – with the utmost urgency – and provide a rapid and complete solution. It is simply not good enough to pass this ‘over the wall’ saying “it’s not our problem”. It is. Adobe's, Apple's, and the printer manufacturers'. Please solve it. And quickly.
Identify the problem clearly, make it and the solution/s public; and publicise it widely and thoroughly.

Dear DYP.
Thank you for your concern.
"What fixes have you tried?"
If I may quote from my post above:
"I have conclusively eliminated the printer, the printer drivers, the Mac OS, corrupted preference files, corrupted user accounts, incorrect Photoshop settings, incorrect printer driver settings, the ‘sticky settings' issue, and user error as possible causes of the problem.
I can say with 95% certainty that my tests, conducted using Mac OSX 10.4.11, have proved the following:
That, printing to a Canon Pro9000 or iP4500, Photoshop CS4 does not print accurate targets suitable for producing profiles. This applies to both the No Colour Management (NCM) and the Printer Manages Colour (PMC) settings.
Photoshop CS and CS2 are not effected.
I did not test CS3"
These tests took place over three weeks and involved over five days of work and the replacement of the printer on Canon's recommendation (although the printer is clearly not at fault).
Please note that I am using Mac OSX 10.4.11.
"What driver versions are you using?"
Pixma iP4500 6.9.3 (also 6.9.1, 6.9.2 and the driver supplied on the CD).
Pro 9000 4.8.7 (also 4.7.3, 4.8.4 and the driver supplied on the CD).
"Yes it is frustrating but in a lot of cases it is fixable as I and others have clear reported, on this and the LR forums."
I have not found any fix on any website referring to Canon printers, despite exhaustive searches (this includes Canon's European and US websites which are mute on the issue).
The ReadMe file supplied with the installation disc of CS4 refers to problems with "some Canon printers" when printing with the 'Printer Manages Color' but does not identify using 'No Color Management' nor Epson printers as having issues.
I hope this post answers your questions.
Clearly all users of CS4 need to be warned of this problem which is likely to effect other printers. I believe that I am assisting others by issuing this warning. It is done, not to cause mischief, but in the spirit of a public service. CS4 users can then treat their printing results from CS4 with caution, and then conduct their own tests. I have presented a workaround which is to use a prior version of CS4.

Facetime and Message log in issue

Hi to all,
I would like to seek your assistance with the Facetime and message log in issue that I am having.
I recently installed the Mountain Lion OS 10.8, now using version 10.8.2, on my personal laptop, Macbook Pro (Mid-2009 model). I have tried many times to log into both applications via my Apple ID but have been unsuccessful.
This afternoon I tried accessing Facetime on my work laptop (Macbook 2010 model, OS Lion 10.7.5) via my Apple ID and it worked.
Can someone please help me in resolving my log in issue with my personal laptop? Much appreciated.
Kind Regards,
Wing Kuen

I would make sure you are logged into iCloud in the System Preference pane, "Icloud".
Then go the the indivusial prefrences of Facetime and Messages, and try to log in.
Hope this helps!

Upgrade System Center Operations Manager 2007 R2 CU6 -- 2012 RTM issues (Assembly related exception in log)

Hi guys
I am currently performing a distributed, complex upgrade with a customer:
4 management servers (1 being RMS), both databases (OM & DW) on a single SQL Server (2008 R2 SP2)
We moved over the RMS role to another server and decomissioned the old one due to it being a 2003 server.
Then we upgraded all non-RMS management servers.
We had some issues with them as well (same error in the log), but when we reinstalled the 2007 R2 binaries & patches and redid the upgrade it came through fine.
The RMS however keeps throwing the same error. Things I tried:
- Full clean of the server including momclean and msizap, then reinstall the RMS and retry the upgrade
- Reregister of the msiexec server
I am suspecting some issues with assemblies and / or GAC, but no clear proof on that, only that it crashes after performing assembly operations.
Below an extract from the RemoveMOMServer.log (the error occurs when uninstalling SCOM 2007 R2)
Can anyone help out or give me some pointers on possible causes?
Many thanks in advance!
MSI (s) (F4:CC) [15:43:55:259]: Executing op: UpdateEstimatedSize(EstimatedSize=0)
MSI (s) (F4:CC) [15:43:55:261]: Executing op: ProductCPDisplayInfoRegister()
MSI (s) (F4:CC) [15:43:55:263]: Executing op: ActionStart(Name=NetFxExecuteNativeImageCommit,,)
MSI (s) (F4:CC) [15:43:55:264]: Executing op: CustomActionSchedule(Action=NetFxExecuteNativeImageCommit,ActionType=3649,Source=BinaryData,Target=ExecNetFx,)
MSI (s) (F4:CC) [15:43:55:266]: Executing op: ActionStart(Name=NetFxExecuteNativeImageCommitUninstall,,)
MSI (s) (F4:CC) [15:43:55:266]: Executing op: CustomActionSchedule(Action=NetFxExecuteNativeImageCommitUninstall,ActionType=3649,Source=BinaryData,Target=ExecNetFx,CustomActionData=C:\Windows\Microsoft.NET\Framework64\v2.0.50727\ngen.exe uninstall "Microsoft.EnterpriseManagement.OperationsManager,
Version=6.0.4900.00, Culture=neutral, PublicKeyToken=31BF3856AD364E35"€500€C:\Windows\Microsoft.NET\Framework64\v2.0.50727\ngen.exe uninstall "Microsoft.EnterpriseManagement.OperationsManager.Common, Version=6.0.4900.00, Culture=neutral, PublicKeyToken=31BF3856AD364E35"€500€C:\Windows\Microsoft.NET\Framework\v2.0.50727\ngen.exe
uninstall "C:\Program Files\System Center Operations Manager 2007\Microsoft.EnterpriseManagement.UI.Foundation.dll"€500€C:\Windows\Microsoft.NET\Framework\v2.0.50727\ngen.exe uninstall "C:\Program Files\System Center Operations Manager 2007\Microsoft.EnterpriseManagement.UI.ConsoleFramework.dll"€500€C:\Windows\Microsoft.NET\Framework\v2.0.50727\ngen.exe
update /queue€500€C:\Windows\Microsoft.NET\Framework64\v2.0.50727\ngen.exe update /queue€500)
MSI (s) (F4:CC) [15:43:55:268]: Executing op: ActionStart(Name=NetFxExecuteNativeImageCommitInstall,,)
MSI (s) (F4:CC) [15:43:55:268]: Executing op: CustomActionSchedule(Action=NetFxExecuteNativeImageCommitInstall,ActionType=3649,Source=BinaryData,Target=ExecNetFx,)
MSI (s) (F4:CC) [15:43:55:270]: Executing op: ActionStart(Name=PublishFeatures,Description=Publishing product features,Template=Feature: [1])
MSI (s) (F4:CC) [15:43:55:270]: Executing op: FeaturePublish(Feature=MOMServer,,Absent=3,Component=@+h863e0NAgaZ7OoE1)HM[lp(tNC_AUZ$SF(D`%aFTE9fFyfs=F=$JG3?U4%Jg+a[OgIJ9l,ltBUJ6}nEPr^ulwB]8CeSrDJOg^Dv6-5{b^j}@^?vz.j7,3M6C%7,*@eo93k8pr6&&N9$znhtI3,f=ds,sbkr{FsK5s,aat+W9Luq^c2T)%]NK-`Nh95Q?1j(Dg@M-ujVqmWklfnQ9{a+G7w.5xHY-FhkL+vZAB~5y'c@}'jr8WIsm`xe=5orHD{+mjmr3jr^W2UX?7PmxUa@v*Z]~U%@4u.j?-mBUeMsh74(}?767KRj@A72,VR{&Ndp=1kRf[ZQAWW2Vmir6O-EYNi`aVy0=sY*I`g=~^zgj-K41CWIAn3+(O4}ZvX8=hVDIvD^A&7iGA]RjL$JKo'QVT)b@Y@NcD-awAKEm,xN7,?,Ad7cW2b8}K?@`XVc]R`h8k*+PKa=CULr]CV`GY24=J**5wT+^.,Yw,vNCs'_A95dR?W8yIC[JXIm!nzq@5?Enk}PZewbi(r&t1H!94?5m0NzSd96@yq+0'^.?}G.RFEU^J@e`)a-_.e4@W?a@,yfmDTR]^+cbWf.=hV2Lk`!5yfUciqXO0JF?wIvuYFC{LBr*ENyKNMv9@3O~EdzJ!$jxy*dl]uq8{j_GLM1aC_g[-UdCQiC90o{ZS=lW(WUciqXme3eSKW@5fYZQ*R{[[yk0@XZAwJAUIK=yaPrb5j3zZII9*^7LD'L6,,V{p7-suLJ?`v(5R1a5&ko,1X$zkt~8Ic75fYZQ*RaE1v.2pOX8dqQ4PWI)'Vx5^d6cT~W@m1M]xA+z~*JWKX5swUG9JO-4h}&rH2H%obQfhOk?@2$kky4Qx]3yC3vPpLx@bP%U&2$(719F%lc[~}z8HzR.HDHZ)c]{SAz-boA9DSkLX$,eI5Tm1KmpVu+AzEhUp4Ka@(9k~3kSgQX@N@a@gaH@B-,TlvgYR`J9ET02Ay.r4F*v&OktBzm?8g^(@8)Udj
MSI (s) (F4:CC) [15:43:55:273]: Executing op: ActionStart(Name=PublishProduct,Description=Publishing product information,)
MSI (s) (F4:CC) [15:43:55:273]: Executing op: CleanupConfigData()
MSI (s) (F4:CC) [15:43:55:273]: Executing op: RegisterPatchOrder(Continue=0,SequenceType=0,Remove=0)
MSI (s) (F4:CC) [15:43:55:276]: Executing op: RegisterPatchOrder(Continue=0,SequenceType=1,Remove=0)
MSI (s) (F4:CC) [15:43:55:280]: Executing op: End(Checksum=0,ProgressTotalHDWord=0,ProgressTotalLDWord=80035200)
MSI (s) (F4:CC) [15:43:55:280]: Entering MsiProvideAssembly. AssemblyName: Microsoft.EnterpriseManagement.OperationsManager,fileVersion="6.1.7221.99",version="6.0.4900.00",culture="neutral",publicKeyToken="31BF3856AD364E35",processorArchitecture="MSIL",
AppContext: , InstallMode: -4
MSI (s) (F4:CC) [15:43:55:280]: Pathbuf: 0, pcchPathBuf: 0
MSI (s) (F4:CC) [15:43:55:281]: MsiProvideAssembly is returning: 1607
MSI (s) (F4:CC) [15:43:55:289]: Verifying accessibility of file: Microsoft.EnterpriseManagement.OperationsManager.dll
MSI (s) (F4:CC) [15:43:55:291]: Using source file security for destination.
MSI (s) (F4:CC) [15:43:55:304]: Entering MsiProvideAssembly. AssemblyName: Microsoft.EnterpriseManagement.OperationsManager, Version=6.0.4900.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=MSIL, AppContext: , InstallMode: -4
MSI (s) (F4:CC) [15:43:55:304]: Pathbuf: 0, pcchPathBuf: 0
MSI (s) (F4:CC) [15:43:55:305]: MsiProvideAssembly is returning: 1607
MSI (s) (F4:CC) [15:43:55:306]: Entering MsiProvideAssembly. AssemblyName: Microsoft.EnterpriseManagement.OperationsManager, Version=6.0.4900.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=MSIL, AppContext: , InstallMode: -4
MSI (s) (F4:CC) [15:43:55:306]: Pathbuf: 0, pcchPathBuf: 0
MSI (s) (F4:CC) [15:43:55:307]: MsiProvideAssembly is returning: 1607
MSI (s) (F4:CC) [15:43:55:308]: Entering MsiProvideAssembly. AssemblyName: Microsoft.EnterpriseManagement.OperationsManager, Version=6.0.4900.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=MSIL, AppContext: , InstallMode: -4
MSI (s) (F4:CC) [15:43:55:308]: Pathbuf: 0, pcchPathBuf: 0
MSI (s) (F4:CC) [15:43:55:310]: MsiProvideAssembly is returning: 1607
MSI (s) (F4:CC) [15:43:55:310]: Entering MsiProvideAssembly. AssemblyName: Microsoft.EnterpriseManagement.OperationsManager, Version=6.0.4900.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=MSIL, AppContext: , InstallMode: -4
MSI (s) (F4:CC) [15:43:55:310]: Pathbuf: 0, pcchPathBuf: 0
MSI (s) (F4:CC) [15:43:55:312]: MsiProvideAssembly is returning: 1607
MSI (s) (F4:CC) [15:43:59:483]: Internal Exception during install operation: 0xc00000fd at 0x0000000077C24EDC.
MSI (s) (F4:CC) [15:43:59:483]: WER report disabled for silent install.
MSI (s) (F4:CC) [15:43:59:483]: WER report disabled for non-console install.
MSI (s) (F4:CC) [15:43:59:483]: Internal MSI error. Installer terminated prematurely.

Thanks for you updating! For SQL related issue, please post on the following forum:
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/home?category=sqlserver
Regards,
Yan Li
Regards, Yan Li

OSX Issues on G4--Graphics Related

I installed OS X 10.4.3. I began to experience kernal panics one right after the other. The only way the computer would boot was in safe mode. I Zapped PRAM, performed fsck, reset open firmware. Checked all RAM disabled all non-shipped perifs. I even erased all hard disks, checked them out and reinstalled OS X.
What would happen in reg boot mode, the screen would get all distorted. This would usually happen when a graphic action was taking place. Like a sub-menu coming down from a window (asking for a ok or cancel action). In safe mode this never happens, but the menus are not smooth when the action is taking place). When it crashes, a kernal panic screen always occurs. I even installed panther on another hard drive but it did it there too. I have been running OS X since version 10.0.1 and it never did it untill tiger was installed.
I was running in safe mode almost exclusively. Then perchance I booted in reg. mode and the computer seems fine...however, when I run some graphic programs, I get a window that says OpenGL not installed or cannot access.
I did notice that preview will not display any graphic files. when I double click a jpeg file or tiff file...Preview launches but the screen is grey and no file displayed. I can open them in QuickTime or the graphic program (photoshop).
the odd thing is that when I check About this Mac, the graphics card and settings say that QuartzExtreme and core Image is not supported.
NVIDIA GeForce2 MX:
Chipset Model: GeForce2 MX
Type: Display
Bus: AGP
Slot: SLOT-1
VRAM (Total): 32 MB
Vendor: nVIDIA (0x10de)
Device ID: 0x0110
Revision ID: 0x00a1
ROM Revision: 1057.019
Displays:
Q95-2:
Resolution: 1024 x 768 @ 60 Hz
Depth: 32-bit Color
Core Image: Not Supported
Main Display: Yes
Mirror: Off
Online: Yes
Quartz Extreme: Not Supported
The thing I cannot understand is why for the longest time I could not even boot in reg. mode. Now all of a sudden it starts up. My suspicion is that the graphics card or something on the board is going. Can anyone shed some light on this issue. If you need further info, feel free to ask.
AL
G4 Quicksilver 2001 Mac OS X (10.4.3) SCSI Card, GeForce2 MX, Internal Zip, 2 60gb Internal HD, 1 120gb external HD, 1.5gb of RAM

Hello hartfree,
> I installed OS X 10.4.3.
Was it an install disk or an update? If it was an update, you may have encountered an error in the download. You may want to re-download the combo and try again:
<a href:"http://www.apple.com/support/downloads/macosxupdate1043combo.html">
Mac OS X Update 10.4.3 Combo
>I began to experience kernal panics one right after the other.
The problems you're experiencing could be any number of things.
1. It could happen with a bad installation of OS X. (an error in the installation disk, a glitch in the optical drive when installing, other unecessary peripherals attached to the computer via USB/Firewire...)
2. Hardware such as memory, cpu, graphics card, can all of a sudden go bad. (But, that doesn't seem to be the case here.)
>My suspicion is that the graphics card or something on the board is going.
Your graphics card is, to put it as gently as possible, old. But, it is well within the requirements of Tiger.
The only suggestion I have, when a kernal panic (or anything else unusual) happens, is to go to the Console (in /Applications/Utilities) and view the system log file. Sometimes, and sometimes not, there are clues that can indicate the source of the problem(s).
Gary

Configuration Changes logging issue, ASDM related?

I've run into an interesting problem.
ASA: 8.4(2)
ASDM: 6.4(5)
When I make a change at the CLI, syslog message ASA-5-111008 is generated and sent to the syslog servers, local buffer, and ASDM.
When I make a change in ASDM, syslog message ASA-5-111008 is generated and sent to the local buffer and ASDM. It is NOT sent to the syslog server.
Here's my logging config...
Firewall# sh run logging
logging enable
logging timestamp
logging standby
logging buffer-size 409600
logging buffered informational
logging trap notifications
logging asdm notifications
logging host Inside xx.xx.xx.AA 6/1468
logging host Inside xx.xx.xx.BB 6/1468
logging flash-minimum-free 10240
logging flash-maximum-allocation 10240
logging permit-hostdown
Surely I'm missing something obvious. Is this a known bug?
Thanks!

Ha, I did upgrade just a few minutes ago, but same result.
That does look similar, and so does ...
CSCth14248 ASA not sending all logging messages via TCP logging
Looks like I'll need to upgrade to 8.4(3) to fix these and see how it goes.
thanks!

Photoshop CS2 issues & Customer Relation's solution

i bought a g5 quad in June 06 that failed in july 06. they were unable to resolve the issue and gave me a replacement machine.
i was given a mac pro with 4GB of RAM and a terabyte of internal storage. the 2 oem 500GB Seagate 7200.10 hard drives took over 9+ hours to zero out: the apple store genius told me this was normal. i have since purchased 2 different hard drives. one of the same capacity which zero's out in under 2 hours. that number IS normal.
Adobe Photoshop CS2 Bridge and Camera RAW have never worked properly on this machine since i got it, quitting all the time when renaming files or browsing my hard drive folders in Bridge. i was told that this is normal and that CS3 and Leopard will fix all this. then the CS3 Beta came out and the machine quits even with the new version.
i contacted Adobe, they say it is my hardware. i went to the apple store and showed them the problem and was able to duplicate it on every mac pro in their store and they said it must be a software issue.
i bought more RAM from apple. the machine works somewhat better now, but it still crashes in photoshop and adobe camera raw and bridge. i purchased lightroom and have looked at changing my workflow, and this program too quits intermittently.
i called apple customer support again. they walked me through using a different user account. same issues. i asked to speak to customer relations. i got on the phone with the lady, and i asked if it was possible to send someone out to look at the machine since it is not working properly, and she said that it is not something they would do since it is not their problem. i asked if they would be able to help me decipher the crash logs so i can find out WHY the machine is crashing.
her exact words were, "well, maybe you can sell it? if it is giving you all these problems and since it is not our hardware, it might be best for you to sell it and buy something that works."
"sell it." i would like to say that "sell it" was not the answer i was looking for. i wasn't even mean to her. i was extremely polite and i got, "sell it" from customer relations. i hope none of you get "sell it"
good luck to all of you.

You use to use Windows but decided to move to Macs at some point, and not look or go back. And that the Quad G5 worked up until some point.
When I got my Mac Pro back in late August/early Sept, I ran into some oddities that no one could help me with. Drivers from Lexmark for their laser printers. Suffice to say that I spent weeks if not month trying to track down why etc. and doing the "clean install" but ended up with the original install disk image.
I'm always afraid if I am forced to install any drivers for now as a result.
I updated SoftRAID (I thought) and ran into every driver and extension conflict possible, known and unknown.
Clean install and avoided anything I could "live without" this time around, and it was stable. For a few days, any and every - and I mean absolutely anything I tried to launch, run or whatnot would CRASH.
I was ready to point fingers. But at whom? ah! must be the Ramjet. Passes all tests, but there must be a gremlin and nothing is good enough to find the cause.
System is now rock solid and stable.
I don't know really what or why. And whether it was SMC reset (I wish they would paint the button in RED!) or zapping PRAM/NVRAM.
I also installed Vista to see if it was OS X or hardware or not. But I never learned what is needed to really use and secure a Windows system - or troubleshoot it if it goes haywire. But you would.
I have spent 40+ yrs tinkering with computers, and 20 with Macs. I think I still remember some of the troubleshooting days from 1990 hunting down shareware bugs.
If it is hardware, it would fail running XP too, maybe? did you retain your license for and copies of Windows and CS2 or whatever you would use? (The Mac Pro really shines running Windows Vista from what I've seen).
It doesn't take a lot to turn a Mac into a crash-prone system. There are some bugs even with the OS update installer itself it seems.
Troubleshooting is as much art as science. Hunches based on what feels wrong with some sweat and guesses backed by some "CSI" sleuthing and detective work.
Only Apple or Intel would know if they have had to come out with re-designed chips, a newer motherboard, or cpus. Or the AMB used on the Risers.
As I said (5 pages ago?) a friend had a G5 Quad that would not run CS2 properly, was crashing etc. (and had on-site Care etc) and the latest logicboard (3rd) stopped the problems, CS2 runs faster and better, it doesn't crash, and the benchmarks show it.
There are revisions to logic-boards. I read it takes 3-6 months to get a pattern of a problem, and another 3-6 months to redesign parts, manufacturing, testing, between engineering prototypes and manufacturing.
I thought the whole idea of AppleCare was sort of the "care" in AppleCare. And to solve a problem.
It would take someone with access to what engineering errata is going on. What changes were made to G5s. There were other problems with Quad it seems as well, heat, the liquid cooling components (there are two varieties).
I don't have the stomach or temper to deal with customer service, phones, etc. But I would make an appointment (yes, again!). I don't know what terms there are for small business or customers to get premium care, probably not good.
We had a mainframe with a bad memory card or bank. We thought. We also swapped out every part trying to get it fixed. We even had to keep the room temp colder and controlled humidity. A new system for us would have been lower maintenance, lower energy bill, less strain on a/c even. And smaller (so we didn't need to use as much floor space). But government can be "penny wise and pound foolish" in such matters.
I know you are just getting familiar with things like "Onyx" and "Disk Warrior" and such. Those can be helpful.
Crashing does tend to lead to more crashes. Mac OS X is not immune to side effects of what they can do. And usually you want to finish a project, not get sidelined.
I wish you had a G5 Quad in there. Two systems. Maybe two G5s even if you have the work or so you can be running CS2 on one and CS3 on another. Or have a techie "gearhead" come in and test and insure that your systems are in working order. Something.
It ain't normal. And it should get more than a "brush off."

Serious log in issues.........graphics related??

Similar Messages

Maybe you are looking for