Problem to open DB after rename diskgroup

Hello,
Version 11202 single instance with ASM
After renaming diskgroup from DATA to PUDWHDATA using :
smcmd umount DATA
renamedg phase=both dgname=DATA newdgname=PUDWHDATA verbose=true
asmcmd mount PUDWHDATA I also had to change the entries in the init.ora after renaming diskgroup as followed :
*.control_files='+PUDWHDATA/pudwh/controlfile/current.263.616243789','+PUDWHDATA/pudwh/controlfile/current.262.616243789'
*.db_create_file_dest='+PUDWHDATA'
*.db_name='dudwh'
*.db_recovery_file_dest='+PUDWHDATA'I am getting the following error message:
ORA-01157: cannot identify/lock data file 1 - see DBWR trace file
ORA-01110: data file 1: '+DATA/pudwh/datafile/system.265.616243837'The alert log shows:
Completed: ALTER DATABASE   MOUNT
Tue Apr 12 14:23:46 2011
ALTER DATABASE OPEN
Errors in file /u01/app/oracle/diag/rdbms/dudwh/dudwh/trace/dudwh_dbw0_22435.trc:
ORA-01157: cannot identify/lock data file 1 - see DBWR trace file
ORA-01110: data file 1: '+DATA/pudwh/datafile/system.265.616243837'
ORA-17503: ksfdopn:2 Failed to open file +DATA/pudwh/datafile/system.265.616243837
ORA-15001: diskgroup "DATA" does not exist or is not mounted
ORA-15001: diskgroup "DATA" does not exist or is not mountedPlease advice

Your control file still thinks you are in the old location.
You need to correct before the database will open.
Use "select name from v$datafile " to find the mismatch and correct.
Oracle note 330103.1 will help after you recover.
Best Regards
mseberg

Similar Messages

  • Problem with opening mail after nstalling OS 10.6.6

    On the application directory I only see "mail.app (original)". Clicking here will give the same error message. On spotlight I don't see any other mail.app. Thanks
    This is the error message I get
    Hi, anybody can help??
    Problem started immediately after upgrading to 10.6.6
    Tried to open mail with different user but problem persist.
    Going into the application folder and opening mail from there did not help.
    I get this message when trying to open mail.
    You can’t use this version of Mail with this version of Mac OS X
    You tried to open Mail version 4.3 (1081/1082) in:
    /Applications/Mail (original).app
    It can’t be used on this version of Mac OS X. Try opening the version of Mail located in the Applications folder on your computer. For more information, click the Help button.
    Thanks

    For some reason I can't change names on the application folder.
    Hmm, you're right... wonder when that changed. It's probably a good idea to prevent you from renaming apps, except that your Mail app has the wrong name.
    Try this... open the Terminal (in the Utilities folder in the Applications folder) and paste in the following command:
    sudo mv /Applications/"Mail (original).app" /Applications/Mail.app
    Then press return. You will be prompted for your password, and when you type it nothing will show up. Press return again after typing it.
    If that doesn't work, you can use [Pacifist|http://www.charlessoft.com> to reinstall the original Mail application from your Mac OS X install disk.
    Either way, after getting some version of Mail with a correct name installed, run the combo updater again to bring that copy of Mail up to the current version.

  • Problems with opening ical after upgrdade

    Error msg:
    "calendar cahce" could not be moved you have insuficent priviliges to "calendars". Anyone?

    vals1979 wrote:
    I wasn't given the option of not installing google chrome
    How did you install the update - via website?  If so, you can always uncheck any optional software
    Either way, Chrome behaves very badly - especially when uninstalled.  Try setting your usual browser as the default browser, and Outlook, Word, etc. should open links normally after that.
    P.S. I do not endorse Adobe's policy to push optional software with their free products, but there is nothing we can do about that.  However, Adobe would not go as far as pushing spyware (Ask toolbar); most likely it was the harmless Google toolbar.

  • Problems to open folder after backup

    Dears,
    One of my old macbook A1181 OS (10.6) crashed and I desided to backup a document files from HDD by plug-in to the External HDD device and coping into iMac (OS 10.9). After transfer of files I can not see a content of main folder. The amount of folder is the same as it was in Macbook.
    Is it possible that after transfer of folder they became a "hidden" files?
    Thank you in advance

    Stirke,
    I presume that you didn't use the Time Machine, right? The method you used was a direct copy to an external HDD, there are some issues you may encounter which will mainly depends on the format of your HDD (suggest that the best format if it's a direct copy is MacOS Journaled).
    Cheers.

  • Bug Report: Page # and Icon Lost After Rename

    I love the new file management features in version 10.3 but I noticed some problems right away.
    After renaming a document, the current page position is lost and the document opens at page 1.  This first one I renamed was a 400-page book and this was a bit annoying.  I realize this is consistent with the desktop version which does not save the page position, but it is inconsistent with the iPad behavior for opening and closing documents.  A fix or a warning should be implemented.
    Also lost is the document icon, which reverts to a generic Reader logo.  This is more of a cosmetic thing.  I noticed the icon does not get restored after opening the document.  It seems necessary to scroll down to page 2 for the icon to refresh.

    Here is  the bug report page:
    https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform

  • HT1414 my iphone has problem in open and if it open iphone shut  down after few minuate

    I have bought this iphone5 from Hannova German in April2013 and I am using this iphone5 in Nepal. In Nepal there is no authorized dealer. This problem came just from 15th July 2013. It has problem in opening and if it open it shut down after few minuate. So how to solve this problem and I think it has a guarantee period. I woud like your support to solve this problem. Thank you.
    <Edited by Host>

    Hi Prashun,
    Thanks for visiting Apple Support Communities.
    You can use these steps to troubleshoot your iPhone if it's powering off unexpectedly:
    iPhone: Hardware troubleshooting
    http://support.apple.com/kb/TS2802
    Will not turn on, will not turn on unless connected to power, or unexpected power off
    Verify that the Sleep/Wake button functions. If it does not function, inspect it for signs of damage. If the button is damaged or is not functioning when pressed, seek service.
    Check if a Liquid Contact Indicator (LCI) is activated or there are signs of corrosion. Learn about LCIs and corrosion.
    Connect the iPhone to the iPhone's USB power adapter and let it charge for at least ten minutes.
    After at least 15 minutes, if:
    The home screen appears: The iPhone should be working. Update to the latest version of iOS if necessary. Continue charging it until it is completely charged and you see this battery icon in the upper-right corner of the screen . Then unplug the phone from power. If it immediately turns off, seek service.
    The low-battery image appears, even after the phone has charged for at least 20 minutes: See "iPhone displays the low-battery image and is unresponsive" symptom in this article.
    Something other than the Home screen or Low Battery image appears, continue with this article for further troubleshooting steps.
    If the iPhone did not turn on, reset it while connected to the iPhone USB power adapter.
    If the display turns on, go to step 4.
    If the display remains black, go to next step.
    Connect the iPhone to a computer and open iTunes. If iTunes recognizes the iPhone and indicates that it is in recovery mode, attempt to restore the iPhone. If the iPhone doesn't appear in iTunes or if you have difficulties in restoring the iPhone, see this article for further assistance.
    If restoring the iPhone resolved the issue, go to step 4. If restoring the iPhone did not solve the issue, seek service.
    Regards,
    Jeremy

  • Here is my problem: "To open "Adobe Photoshop CS5.1" you need to install the legacy Java SE 6 RUNTIME" after upgrading iMac to Yosemite, can anybody help?

    Here is my problem: "To open "Adobe Photoshop CS5.1" you need to install the legacy Java SE 6 RUNTIME" after upgrading iMac to Yosemite, can anybody help?

    This answer may be somewhat late, but just in case other have the same issues, I went to site listed below and it solved the problem.  No need to reinstall CS5 product.  I hope this works for you.
    http://support.apple.com/kb/DL1572

  • Having problems opening CS5 after upgrading to Yosemite, any suggestions?

    Can not open CS% after upgrading to Yosemite... is there a fix anywhere?

    Chris, thank you !!
    i wish i could be as Technical as you..
    not sure what you mean Apple is telling me because  they are not  saying anything about what Java version i need to download.
    any further advise is welcome

  • Problem after renaming Subject Area

    Hi,
    After renaming de Subject Area in Administration I´m not able to edit the reports built with this Subject Area. A message shows up in the columns pane telling something like "either you don´t have permission to use the subject area XXX within answers or the subject area does not exist".
    What´s going on?
    I really need help.

    Check the "Aliases" tab of the presentation catalog (Subject Area) that you renamed. It should contain the previous name of your presentation catalog. If that doesn't exist, your reports should get the errors you have mentioned.

  • Error 503 after renaming SharePoint Foundation 2013 Server

    We renamed a SharePoint Foundation 2013 server using the procedure outlined here:
    http://www.bluesphereinc.com/blog/renaming-a-sharepoint-20102013-server/
    Everything seemed to work fine until we tried to access the site afterwards. Now all we get when trying to access the site is the Error 503: Service is unavailable message. We can get into central administration without any problems.

    Hi  ,
    According to your description, my understanding is that you encountered 503 error after renaming SharePoint Foundation 2013 Server.
    For your issue, please refer to the actions as follow:
    1.Check the web site properties in IIS. Under home directory tab, check the application pool value and then open that application pool from the application pools (separate node in the IIS tree). Click the
    identity tab and see who is the pool assigned to. For the sake of testing, you can select "Predefined" and select local service from the drop down. Restart IIS and see if things work out for you. Http 503 error is generated by the IIS and it happens
    when web server sends data stream back to the web site.
    2.Verify that all SharePoint services are started, this error might occur because of changing the service account password. You may need to change the new password to application pool or SharePoint timer
    service. Click the stopped application pool -> click advanced settings ->Identity ->click the user to retype the user ->Application Pool Identity dialog ->click set -> manually type the user name and password. Then restart the server.
    If your issue persists, please provide detail error message of ULS log 
    to determine the exact cause of the error?
    For SharePoint 2013, by default, ULS log is at      
    C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\LOGS
    Best Regards,
    Eric
    Eric Tao
    TechNet Community Support

  • After renaming a file extention from .jpeg to .jpg I can no longer type ...

    After renaming a file extention from .jpeg to .jpg I can no longer type in any of the finder related editable fields/boxes. I can still type in my open applications fields.
    This problem also happens when I happen to find a file that has been named, for instance, 2008jpg. When I add the period to have the file read correctly as 2008.jpg, a warning box appears asking - {*Are you sure you want to change the extention from ".jpeg" to ".jpg"?* If you make this change, your document may open in a different application.} Two radio buttons are available within this warning box that read - 1 - {Use .jpg}(it is not color coded, which means it must be selected manually. - 2 - {Keep .jpeg}(it is colored w/my Blue highlight color, which means it will be selected if the Enter Key is used.
    The warning box does Not appear if I remove the period from a file and not again when i re-add the period to that same file.
    After trying to make these types of edits to the name of any file, with any of the various extentions available for files in our digital world, I usually get an anomaly where myability to type in the Finder ceases to be a possibility.
    I have found that I can Force Quit the Finder for a quick fix, but, I'm not sure that this Typing problem should have to be dealt with at all by this quick fix. Is this an issue with the Indexing in Spotlight, which seems to be giving many users problems?

    I downloaded and tried EasyFind. It works but it took 30+ seconds to complete finding 3 files that are on One of my Five 25+ Gb partitions of my 130 Gb Seagate Cuda(Really 160 Gb, but my Sawtooth will only recognize 130) I figured that if I ever got a better box, I could reformat it to see the whole 160 Gb. So, as far as I can see, Spotlight's indexing scheme which finds the files instantly is probably preferable. Spot light allows you to rename your files from within it's app window. I've always thought that was pretty powerful. Could my doing so be causing me any issues? As i said it is the inability to Type in the Finder that seemed to be caused from changing file Extentions that were mis-written. Maybe it was a delayed reaction to my renaming files in the Spotlight app? I've done both on occasion.
    As for these .DS_Store files. Apparently you can NOT stop them from being written to any folder that you touch/open/view during a days session. But, as a function of the OS, are the essential to have in their respective folders Forever? I've looked at the .DS_Store terminator app briefly and assume that getting rid of these files won't hurt the regular operation of my OS. They will just be re-written if I ever have to go back to any particular folder again. But, apparently, some have said that if the plan on burning a CD or DVD of their data, they delete the .DS_Store files first and then do the burn.
    I'm thinking from your having suggested this tremination app that you suspect that my having all of these ,DS_Store files could be a situation where any of them could have become corrupted and terminating them regularly should be part of my regular maintenance.
    Does that sound like I'm understanding what I can do?
    TIA

  • Help! iWeb won't open properly after I updated to Yosemite. No old websites, no workspace- nothing is displayed even when the app is open. HELP!

    Help! iWeb won't open properly after I updated to Yosemite. No old websites, no workspace- nothing is displayed even when the app is open. HELP!

    To open your domain file in Lion, Mountain Lion or Mavericks or to switch between multiple domain files Cyclosaurus has provided us with the following script that you can make into an Applescript application with AppleScript Editor. Open Script Editor, copy and paste the script below into Script Editor's window and save as an application.
    do shell script"/usr/bin/defaults write com.apple.iWeb iWebDefaultsDocumentPath -boolean no"
    delay 1
    tell application "iWeb" to activate
    You can download an already compiled version with this link: iWeb Switch Domain. Note:  you may have to Control (right) - click on the app after uncompressing and select Open due to the Sandboxing feature of OS X.  If you have problems with the app create your own with AppleScript Editor.
    Just launch the application, find and select the domain file in your Home/Library/Application Support/iWeb folder that you want to open and it will open with iWeb. It modifies the iWeb preference file each time it's launched so one can switch between domain files.
    WARNING: iWeb Switch Domain will overwrite an existing Domain.sites2 file if you select to create a new domain in the same folder.  So rename your domain files once they've been created to something other than the default name.
    NOTE: In Lion and Mountain Lion the Home/Library folder is now invisible. To make it permanently visible in Lion or Mt. Lion enter the following in the Terminal application window: chflags nohidden ~/Library and press the Return key - 10.7: Un-hide the User Library folder.
    For Mavericks and Yosemite go to your Home folder and use the View ➙ Show View Options menu to bring the this window:

  • Cannot open mail after upgrade to Yosimite 10.10.1

    Hello everyone,
    I cannot open mail after I just update from OS X v10.9 (Mavericks) to Yosimite 10.10.1 and I use console to capture the log as below. Pls. help to find the solution.
    Thank you
    Spaide
    1/2/2558 BE 7:14:13.222 PM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
    1/2/2558 BE 7:14:14.605 PM bird[859]: Assertion failed: ![_xpcClients containsObject:client]
    1/2/2558 BE 7:14:14.606 PM bird[859]: Assertion failed: ![_xpcClients containsObject:client]
    1/2/2558 BE 7:14:14.935 PM bird[859]: Assertion failed: ![_xpcClients containsObject:client]
    1/2/2558 BE 7:14:26.958 PM Mail[941]: *** Assertion failure in -[MFIMAPAccount mailboxForRelativePath:isFilesystemPath:create:], /SourceCache/Mail/Mail-1993/MailFramework/Accounts/MFMailAccount.m:4467
    1/2/2558 BE 7:14:27.595 PM Mail[941]: An uncaught exception was raised
    1/2/2558 BE 7:14:27.596 PM Mail[941]: Absolute path passed into -[MFIMAPAccount mailboxForRelativePath:isFilesystemPath:create:]: /็Homeworks
    1/2/2558 BE 7:14:27.596 PM Mail[941]: (
      0   CoreFoundation                      0x0000000111c5764c __exceptionPreprocess + 172
      1   libobjc.A.dylib                     0x000000010ffe26de objc_exception_throw + 43
      2   CoreFoundation                      0x0000000111c5742a +[NSException raise:format:arguments:] + 106
      3   Foundation                          0x000000010fb435b9 -[NSAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 195
      4   Mail                                0x000000010f402f5c -[MFMailAccount mailboxForRelativePath:isFilesystemPath:create:] + 251
      5   Mail                                0x000000010f360404 -[MFIMAPAccount mailboxForRelativePath:isFilesystemPath:create:] + 491
      6   Mail                                0x000000010f404696 +[MFMailAccount mailboxForURL:forceCreation:syncableURL:] + 473
      7   Mail                                0x000000010f41b168 __43+[MFMailbox queueUpdateCountsForMailboxes:]_block_invoke_2 + 68
      8   CoreFoundation                      0x0000000111b81ea6 __65-[__NSDictionaryM enumerateKeysAndObjectsWithOptions:usingBlock:]_block_invoke + 102
      9   CoreFoundation                      0x0000000111b81db9 -[__NSDictionaryM enumerateKeysAndObjectsWithOptions:usingBlock:] + 217
      10  Mail                                0x000000010f41b0b6 __43+[MFMailbox queueUpdateCountsForMailboxes:]_block_invoke + 275
      11  Foundation                          0x000000010fb8d2e8 __NSBLOCKOPERATION_IS_CALLING_OUT_TO_A_BLOCK__ + 7
      12  Foundation                          0x000000010fa79905 -[NSBlockOperation main] + 97
      13  Foundation                          0x000000010fa5859c -[__NSOperationInternal _start:] + 653
      14  Foundation                          0x000000010fa581a3 __NSOQSchedule_f + 184
      15  libdispatch.dylib                   0x0000000113ad5c13 _dispatch_client_callout + 8
      16  libdispatch.dylib                   0x0000000113ad9365 _dispatch_queue_drain + 1100
      17  libdispatch.dylib                   0x0000000113adaecc _dispatch_queue_invoke + 202
      18  libdispatch.dylib                   0x0000000113ad86b7 _dispatch_root_queue_drain + 463
      19  libdispatch.dylib                   0x0000000113ae6fe4 _dispatch_worker_thread3 + 91
      20  libsystem_pthread.dylib             0x0000000113e136cb _pthread_wqthread + 729
      21  libsystem_pthread.dylib             0x0000000113e114a1 start_wqthread + 13
    1/2/2558 BE 7:14:27.597 PM Mail[941]: *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'Absolute path passed into -[MFIMAPAccount mailboxForRelativePath:isFilesystemPath:create:]: /็Homeworks'
    *** First throw call stack:
      0   CoreFoundation                      0x0000000111c5764c __exceptionPreprocess + 172
      1   libobjc.A.dylib                     0x000000010ffe26de objc_exception_throw + 43
      2   CoreFoundation                      0x0000000111c5742a +[NSException raise:format:arguments:] + 106
      3   Foundation                          0x000000010fb435b9 -[NSAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 195
      4   Mail                                0x000000010f402f5c -[MFMailAccount mailboxForRelativePath:isFilesystemPath:create:] + 251
      5   Mail                                0x000000010f360404 -[MFIMAPAccount mailboxForRelativePath:isFilesystemPath:create:] + 491
      6   Mail                                0x000000010f404696 +[MFMailAccount mailboxForURL:forceCreation:syncableURL:] + 473
      7   Mail                                0x000000010f41b168 __43+[MFMailbox queueUpdateCountsForMailboxes:]_block_invoke_2 + 68
      8   CoreFoundation                      0x0000000111b81ea6 __65-[__NSDictionaryM enumerateKeysAndObjectsWithOptions:usingBlock:]_block_invoke + 102
      9   CoreFoundation                      0x0000000111b81db9 -[__NSDictionaryM enumerateKeysAndObjectsWithOptions:usingBlock:] + 217
      10  Mail                                0x000000010f41b0b6 __43+[MFMailbox queueUpdateCountsForMailboxes:]_block_invoke + 275
      11  Foundation                          0x000000010fb8d2e8 __NSBLOCKOPERATION_IS_CALLING_OUT_TO_A_BLOCK__ + 7
      12  Foundation                          0x000000010fa79905 -[NSBlockOperation main] + 97
      13  Foundation                          0x000000010fa5859c -[__NSOperationInternal _start:] + 653
      14  Foundation                          0x000000010fa581a3 __NSOQSchedule_f + 184
      15  libdispatch.dylib                   0x0000000113ad5c13 _dispatch_client_callout + 8
      16  libdispatch.dylib                   0x0000000113ad9365 _dispatch_queue_drain + 1100
      17  libdispatch.dylib                   0x0000000113adaecc _dispatch_queue_invoke + 202
      18  libdispatch.dylib                   0x0000000113ad86b7 _dispatch_root_queue_drain + 463
      19  libdispatch.dylib                   0x0000000113ae6fe4 _dispatch_worker_thread3 + 91
      20  libsystem_pthread.dylib             0x0000000113e136cb _pthread_wqthread + 729
      21  libsystem_pthread.dylib             0x0000000113e114a1 start_wqthread + 13
    1/2/2558 BE 7:14:31.133 PM com.apple.xpc.launchd[1]: (com.apple.ReportCrash[947]) Endpoint has been activated through legacy launch(3) APIs. Please switch to XPC or bootstrap_check_in(): com.apple.ReportCrash
    1/2/2558 BE 7:14:31.482 PM diagnosticd[896]: error evaluating process info - pid: 941, punique: 941
    1/2/2558 BE 7:14:33.551 PM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
    1/2/2558 BE 7:14:49.406 PM mds[32]: (DiskStore.Normal:2376) 2a001 2.808408
    1/2/2558 BE 7:15:01.570 PM hidd[72]: IOHIDEventQueue unable to get policy for event of type 11. (e00002e8)
    1/2/2558 BE 7:15:01.577 PM hidd[72]: IOHIDEventQueue unable to get policy for event of type 11. (e00002e8)
    1/2/2558 BE 7:15:01.586 PM hidd[72]: IOHIDEventQueue unable to get policy for event of type 11. (e00002e8)
    1/2/2558 BE 7:15:01.594 PM hidd[72]: IOHIDEventQueue unable to get policy for event of type 11. (e00002e8)
    1/2/2558 BE 7:15:01.602 PM hidd[72]: IOHIDEventQueue unable to get policy for event of type 11. (e00002e8)
    1/2/2558 BE 7:15:01.610 PM hidd[72]: IOHIDEventQueue unable to get policy for event of type 11. (e00002e8)
    1/2/2558 BE 7:15:01.626 PM hidd[72]: IOHIDEventQueue unable to get policy for event of type 11. (e00002e8)
    1/2/2558 BE 7:15:01.633 PM hidd[72]: IOHIDEventQueue unable to get policy for event of type 11. (e00002e8)
    1/2/2558 BE 7:15:01.641 PM hidd[72]: IOHIDEventQueue unable to get policy for event of type 11. (e00002e8)
    1/2/2558 BE 7:15:01.665 PM hidd[72]: IOHIDEventQueue unable to get policy for event of type 11. (e00002e8)
    1/2/2558 BE 7:15:01.673 PM hidd[72]: IOHIDEventQueue unable to get policy for event of type 11. (e00002e8)
    1/2/2558 BE 7:15:01.682 PM hidd[72]: IOHIDEventQueue unable to get policy for event of type 11. (e00002e8)
    1/2/2558 BE 7:15:01.689 PM hidd[72]: IOHIDEventQueue unable to get policy for event of type 11. (e00002e8)
    1/2/2558 BE 7:15:05.659 PM com.apple.xpc.launchd[1]: (com.apple.mail.52288[941]) Service exited due to signal: Abort trap: 6
    1/2/2558 BE 7:15:13.065 PM ReportCrash[947]: Saved crash report for Mail[941] version 8.1 (1993) to /Users/kulanak/Library/Logs/DiagnosticReports/Mail_2015-01-02-191512_apples-mac book-pro-3.crash
    1/2/2558 BE 7:15:19.526 PM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
    1/2/2558 BE 7:15:19.767 PM bird[859]: Assertion failed: ![_xpcClients containsObject:client]
    1/2/2558 BE 7:15:19.767 PM bird[859]: Assertion failed: ![_xpcClients containsObject:client]
    1/2/2558 BE 7:15:20.368 PM bird[859]: Assertion failed: ![_xpcClients containsObject:client]
    1/2/2558 BE 7:15:25.817 PM Mail[951]: *** Assertion failure in -[MFIMAPAccount mailboxForRelativePath:isFilesystemPath:create:], /SourceCache/Mail/Mail-1993/MailFramework/Accounts/MFMailAccount.m:4467
    1/2/2558 BE 7:15:25.819 PM Mail[951]: An uncaught exception was raised
    1/2/2558 BE 7:15:25.819 PM Mail[951]: Absolute path passed into -[MFIMAPAccount mailboxForRelativePath:isFilesystemPath:create:]: /็Homeworks
    1/2/2558 BE 7:15:25.820 PM Mail[951]: (
      0   CoreFoundation                      0x0000000111d3164c __exceptionPreprocess + 172
      1   libobjc.A.dylib                     0x00000001100c96de objc_exception_throw + 43
      2   CoreFoundation                      0x0000000111d3142a +[NSException raise:format:arguments:] + 106
      3   Foundation                          0x000000010fc285b9 -[NSAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 195
      4   Mail                                0x000000010f4e2f5c -[MFMailAccount mailboxForRelativePath:isFilesystemPath:create:] + 251
      5   Mail                                0x000000010f440404 -[MFIMAPAccount mailboxForRelativePath:isFilesystemPath:create:] + 491
      6   Mail                                0x000000010f4e4696 +[MFMailAccount mailboxForURL:forceCreation:syncableURL:] + 473
      7   Mail                                0x000000010f4fb168 __43+[MFMailbox queueUpdateCountsForMailboxes:]_block_invoke_2 + 68
      8   CoreFoundation                      0x0000000111c5bea6 __65-[__NSDictionaryM enumerateKeysAndObjectsWithOptions:usingBlock:]_block_invoke + 102
      9   CoreFoundation                      0x0000000111c5bdb9 -[__NSDictionaryM enumerateKeysAndObjectsWithOptions:usingBlock:] + 217
      10  Mail                                0x000000010f4fb0b6 __43+[MFMailbox queueUpdateCountsForMailboxes:]_block_invoke + 275
      11  Foundation                          0x000000010fc722e8 __NSBLOCKOPERATION_IS_CALLING_OUT_TO_A_BLOCK__ + 7
      12  Foundation                          0x000000010fb5e905 -[NSBlockOperation main] + 97
      13  Foundation                          0x000000010fb3d59c -[__NSOperationInternal _start:] + 653
      14  Foundation                          0x000000010fb3d1a3 __NSOQSchedule_f + 184
      15  libdispatch.dylib                   0x0000000113bbac13 _dispatch_client_callout + 8
      16  libdispatch.dylib                   0x0000000113bbe365 _dispatch_queue_drain + 1100
      17  libdispatch.dylib                   0x0000000113bbfecc _dispatch_queue_invoke + 202
      18  libdispatch.dylib                   0x0000000113bbd6b7 _dispatch_root_queue_drain + 463
      19  libdispatch.dylib                   0x0000000113bcbfe4 _dispatch_worker_thread3 + 91
      20  libsystem_pthread.dylib             0x0000000113f0f6cb _pthread_wqthread + 729
      21  libsystem_pthread.dylib             0x0000000113f0d4a1 start_wqthread + 13
    1/2/2558 BE 7:15:25.821 PM Mail[951]: *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'Absolute path passed into -[MFIMAPAccount mailboxForRelativePath:isFilesystemPath:create:]: /็Homeworks'
    *** First throw call stack:
      0   CoreFoundation                      0x0000000111d3164c __exceptionPreprocess + 172
      1   libobjc.A.dylib                     0x00000001100c96de objc_exception_throw + 43
      2   CoreFoundation                      0x0000000111d3142a +[NSException raise:format:arguments:] + 106
      3   Foundation                          0x000000010fc285b9 -[NSAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 195
      4   Mail                                0x000000010f4e2f5c -[MFMailAccount mailboxForRelativePath:isFilesystemPath:create:] + 251
      5   Mail                                0x000000010f440404 -[MFIMAPAccount mailboxForRelativePath:isFilesystemPath:create:] + 491
      6   Mail                                0x000000010f4e4696 +[MFMailAccount mailboxForURL:forceCreation:syncableURL:] + 473
      7   Mail                                0x000000010f4fb168 __43+[MFMailbox queueUpdateCountsForMailboxes:]_block_invoke_2 + 68
      8   CoreFoundation                      0x0000000111c5bea6 __65-[__NSDictionaryM enumerateKeysAndObjectsWithOptions:usingBlock:]_block_invoke + 102
      9   CoreFoundation                      0x0000000111c5bdb9 -[__NSDictionaryM enumerateKeysAndObjectsWithOptions:usingBlock:] + 217
      10  Mail                                0x000000010f4fb0b6 __43+[MFMailbox queueUpdateCountsForMailboxes:]_block_invoke + 275
      11  Foundation                          0x000000010fc722e8 __NSBLOCKOPERATION_IS_CALLING_OUT_TO_A_BLOCK__ + 7
      12  Foundation                          0x000000010fb5e905 -[NSBlockOperation main] + 97
      13  Foundation                          0x000000010fb3d59c -[__NSOperationInternal _start:] + 653
      14  Foundation                          0x000000010fb3d1a3 __NSOQSchedule_f + 184
      15  libdispatch.dylib                   0x0000000113bbac13 _dispatch_client_callout + 8
      16  libdispatch.dylib                   0x0000000113bbe365 _dispatch_queue_drain + 1100
      17  libdispatch.dylib                   0x0000000113bbfecc _dispatch_queue_invoke + 202
      18  libdispatch.dylib                   0x0000000113bbd6b7 _dispatch_root_queue_drain + 463
      19  libdispatch.dylib                   0x0000000113bcbfe4 _dispatch_worker_thread3 + 91
      20  libsystem_pthread.dylib             0x0000000113f0f6cb _pthread_wqthread + 729
      21  libsystem_pthread.dylib             0x0000000113f0d4a1 start_wqthread + 13
    1/2/2558 BE 7:15:26.815 PM com.apple.xpc.launchd[1]: (com.apple.mail.52288[951]) Service exited due to signal: Abort trap: 6
    1/2/2558 BE 7:15:26.892 PM ReportCrash[947]: Saved crash report for Mail[951] version 8.1 (1993) to /Users/kulanak/Library/Logs/DiagnosticReports/Mail_2015-01-02-191526_apples-mac book-pro-3.crash
    1/2/2558 BE 7:15:26.904 PM ReportCrash[947]: Removing excessive log: file:///Users/kulanak/Library/Logs/DiagnosticReports/Mail_2015-01-02-061109_app les-macbook-pro-3.crash

    Try a restart.
    Do a backup, using either Time Machine or a cloning program, to ensure files/data can be recovered. Two backups are better than one.
    Try setting up another admin user account to see if the same problem continues. If Back-to-My Mac is selected in System Preferences, the Guest account will not work. The intent is to see if it is specific to one account or a system wide problem. This account can be deleted later.
    Isolating an issue by using another user account
    Try booting into the Safe Mode using your normal account.  Disconnect all peripherals except those needed for the test. Shut down the computer and then power it back up after waiting 10 seconds. Immediately after hearing the startup chime, hold down the shift key and continue to hold it until the gray Apple icon and a progress bar appear and again when you log in. The boot up is significantly slower than normal. This will reset some caches, forces a directory check, and disables all startup and login items, among other things. When you reboot normally, the initial reboot may be slower than normal. If the system operates normally, there may be 3rd party applications which are causing a problem. Try deleting/disabling the third party applications after a restart by using the application un-installer. For each disable/delete, you will need to restart if you don’t do them all at once.
    Safe Mode - About
    Safe Mode - Yosemite

  • Can´t open LR after upgrade to 5.3 without entering a licens key

    Can´t open LR after upgrade to 5.3 without entering a licens key

    I have seen comments from someone who indicated that every time they started Lightroom they were prompted for the serial number, even though they had already entered it. Is this your situation? I can't remember what the solution is, but I have seen that problem mentioned in the past.

  • Can't open iphoto after complete reboot.

    Hi!
    My computer stoped working a while back and I had the harddrive replaced, now I can't open iphoto after importing it from time mashine. I still have the same OS X (10.6.8) on a Mac Book pro from 2009. I can't buy the new one, or update it, because my OS X is too old and after seeing all the problems with the new system I don't really want to install it. How do I make iphoto work again? When I try to open it, it just says it can't open because of a problem (no, really?).

    Is there a crash report?  Have you tried reinstalling it?
    To re-install iPhoto
    1. Put the iPhoto.app in the trash (Drag it from your Applications Folder to the trash)
    2. Download it from the App Store to reinstall It's on your Purchases List* there.
    For older versions that have been installed from Disk you'll need these additional steps:
    2a: On 10.5:  Go to HD/Library/Receipts and remove any pkg file there with iPhoto in the name.
    2b: On 10.6: Those receipts may be found as follows:  In the Finder use the Go menu and select Go To Folder. In the resulting window type
    /var/db/receipts/
    2c: on 10.7 or later they're at
    /private/var/db/receipts
    A Finder Window will open at that location and you can remove the iPhoto pkg files.
    3. Re-install.
    If you purchased an iLife Disk, then iPhoto is on it.
    If iPhoto was installed on your Mac when you go it then it’s on the System Restore disks that came with your Mac. Insert the first one and opt to ‘Install Bundled Applications Only.
    *Sometimes iPhoto is not visible on the Purchases List. it may be hidden. See this article for details on how to unhide it.
    http://support.apple.com/kb/HT4928
    One question often asked: Will I lose my Photos if I reinstall?
    iPhoto the application and the iPhoto Library are two different parts of the iPhoto programme. So, reinstalling the app should not affect the Library. BUT you should always have a back up before doing this kind of work. Always.

Maybe you are looking for