Help user cannot open mailbox

Hi Guys
I have a user connecting to his imap account on os x server 10.4.11 all his other folders pop up fine and sync fine but cannot access his inbox, this has only happened in the last day or two, I have tried reconstructing it but to no avail it just sits there and constantly says Opening Mailbox, all other users connect fine. At my wits end and the user is screaming at this stage, any help would be appreciated.
Niall

strange one this,
Reconstruct operation confirmed.
Mail Services were already stopped before
running mailbfr.
Reconstructing the Mail database.
Moving database: /var/imap -> /var/imapold10162008-235148
Making new database: -> /var/imap
reading configure file...
i will configure directory /var/imap.
i saw partition /var/spool/imap.
i saw partition /lcIMAP.
i saw partition /Users/Shared.
done
configuring /var/imap...
creating /var/spool/imap...
creating /lcIMAP...
creating /Users/Shared...
done
Fixing owner: -> cyrusimap:mail
Reconstructing the database: -> /var/imap
This can take a while. Please be patient.
reconstruct: couldn't open partition: /lcIMAP/user
fatal error: Unknown/invalid partition
Fixing quota

Similar Messages

  • PC users cannot open my Pages-exported PDF documents

    Has anyone encountered this? When I want to give someone a PDF, I need to export it from Pages, choose "Open with Adobe Reader," and then re-save from Reader as a different name. (If I just export from Pages, some PC users cannot open it.) When I look at the file information for these two supposed PDFs, the one that's only exported from Pages says "Portable Document Format (PDF)" and the one opened and resaved with Reader says "Adobe PDF Document." What's going on here? Is there a reason my PC friends can't open a Pages-generated PDF?

    Thanks for the suggestions. Funny, when I changed the "Open With" selection inside the "File Info" box to tell it to use Reader, it it still tells me in the "General" information section that it's a "Portable Document Format (PDF)", but it does replace the "Preview" icon in the upper left with the Adobe logo. Only the version that I physically opened with Reader and re-saved lists the "Kind" of document as an "Adobe PDF Document". Wacky.
    Regarding the extension, when I exported from Pages, the "Hide Extension" box was unchecked in the "Save" window, yet the file's PDF extension is in fact hidden (and the "File Info" box also says it's hidden). What's up with that? Grr.
    Seems like a small bug--now I just have to get some PC-using friends to let me know which ones they can open! Thanks for your (tres rapide) help guys!

  • Some Users cannot Open Workflow Approval Task

    We have a SPD workflow published to our production site and it includes a 'Start Approval Process' task which involves a number of users (determined by a lookup to another list) this worked brilliantly until we republished the workflow with some minor changes,
    none of which were to this particular approval task. Now we are seeing some strange behaviours. When some users click the task to approve they are seeing 'This from cannot be opened in a browser, To open this form use Microsoft Infopath'. Now strangely it's
    only certain users, if you're a site collection admin you never have this error. So if a user previously had the error and i then add them to the site collection administrators list the error goes away and they can complete the task.
    Obviously not a solution! giving users full control permissions on the task list or task item doesnt fix the error either. The same workflow on our UAT works without any issues. The task forms in SPD have not been customised either. Its a SP2010 Standard
    farm with no infopath services obviously. Bizarrely there are some users with only Contribute rights to the task list who can open approve tasks, so it's looking like a permissions issue to me but I'm at a loss to find a fix. I've tried totally removing
    the worklows and republishing, regenerating the .xsn task forms in SPD by deleting them and republishing, removing and re-adding the task related content types to site, Changing the Approval Task settings 'only allow users to edit their tasks...' to false
    and then back to true, the works, but to no avail.
    Anybody any ideas?
    TIA
    Chris

    Hi,
    According to your post, my understanding is that Some Users cannot Open Workflow Approval Task.
    I recommend that you can create a new list and workflow to check whether it works.
    Then use the user who get the error to open task.
    If he can open the task in the brower, the issue is related to the older list.
    Then you can use the new created list and assgin the task.
    Here is a similar thread for your reference:
    https://social.msdn.microsoft.com/Forums/en-US/67dc8577-f248-4d6c-bb82-3aca0f084d24/this-form-cannot-be-opened-in-a-web-browser-error-not-an-infopath-form?forum=sharepointcustomizationprevious
    Thanks,
    Linda Li                
    Forum Support
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Linda Li
    TechNet Community Support

  • Cannot open mailbox system attendand- randomly

    Hello,
    our environment have Exchange 2013 with CU7 installed, and lately receive weird problem that is not persistent but it unexplained.
    All databases mounted that are in DAG, all arbitration mailboxes good, in ADSIEDIT checked homeMDB, and it is not set, however, i dont know is this relevant because sometimes is failing, sometimes is success.
    When we run user creation we randomly get error:
    Cannot open mailbox /o=ORGANIZATION/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=SERVER/cn=Microsoft System Attendant. CategoryInfo: NotSpecified: (:) [Set-MailboxRegionalConfiguration],
    MailboxUnavailableException, FullyQualifiedErrorId: [Server=SERVER,RequestId=ba479b62-bda0-4c55-9347-9279f6121d62,TimeStamp=3/18/2015 7:57:29 PM] [FailureCategory=Cmdlet-MailboxUnavailableException] 45AC6FDA,Microsoft.Exchange.Management.StoreTasks.SetMailboxRegionalConfiguration
    Googled many answers, tried many workarounds, and I'm out of ideas now, so any suggestion will be more than welcome!
    Thanks,
    Ivica

    Well, i would do that, except that Exchange 2013 don't have System attendant service.
    Also, we have 6 databases, how do i know which one to put in homeMDB field?
    I did as you instructed anyway for test and still receive error:
    <?xml version="1.0"?>
    <Objects>
      <Object Type="System.Management.Automation.PSCustomObject">
        <Property Name="message" Type="System.String">Can't create user</Property>
        <Property Name="detailMessage" Type="System.String">Cannot open mailbox /o=secureemail/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=SERVER/cn=Microsoft System Attendant. CategoryInfo:
    NotSpecified: (:) [Set-MailboxRegionalConfiguration], StorageTransientException, FullyQualifiedErrorId: [Server=SERVER,RequestId=557e3eb8-ddbb-44c9aab1-d18c0682beb5,TimeStamp=3/19/2015 2:45:32 PM] [FailureCategory=Cmdlet-StorageTransientException] 2CC71ED6,Microsoft.Excha
    nge.Management.StoreTasks.SetMailboxRegionalConfiguration</Property>
        <Property Name="responseCode" Type="System.String">400</Property>
      </Object>
    </Objects>
    Keep in mind that servers are in remote AD sites, replication and AD health is good!
    This is script that is failing:
    $ErrorActionPreference = "Stop";
    try{
    Add-PSSnapin Microsoft.Exchange.Management.PowerShell.SnapIn
    $OrganizationName = "[email protected]" #User defined mail address
    $organizationUnit = "OU=$OrganizationName,OU=users,DC=domain,DC=priv";
    $name = "John"                                            
    #this should be asked in web interface (firstname)
    $lastname = "Dpe"                                              
    #this should be asked in web interface (lastname)
    $displayName = "John Doe" # this is display name in OWA and in all address books
    $logonName = "john"    # this will be users choosen logon name (before @externaldomain.com)
    $ExternalDomain = "example.com"        #this value user will enter as his wanted username and will use it together with his external domain name [email protected]
    $UPN = "$LogonName@$ExternalDomain"   #this should remain to be done automatically and under assumption domain is provisioned!!
    $DomainController = "server"   #this value must be specified based on domain controller in AD site where user will be created
    $nonadmin = "$OrganizationName All Users"; #This is field for entire tenant management and members are used for calendar sharing
    $database = "database"                               
    $retentionPolicy = "DoNotRemove"
    $customattribute1 = "$OrganizationName" #Add for possible manipulation of tenants for future need
    $customattribute2 = "ServiceID"
    $customattribute3 = "ContactID"
    $customattribute4 = "ClientID"
    $password =ConvertTo-SecureString 'Password123' -AsPlainText -Force
    $mailbox = New-Mailbox -DomainController "$DomainController" -RetentionPolicy $retentionPolicy -UserPrincipalName $UPN -Name "$name $lastname" -OrganizationalUnit "$organizationUnit" -Password $password -FirstName "$name"
    -LastName "$lastname" -Displayname "$Displayname" -database $database -ResetPasswordOnNextLogon $false  #This is part where user is created
    Start-Sleep -s 2;
    Add-DistributionGroupMember -Identity "$nonadmin" -Member "$UPN" -BypassSecurityGroupManagerCheck  -DomainController "$DomainController"      #at this line user is placed in distribution group and
    that group is used for additional security
    Start-Sleep -s 2;
    Set-Mailbox -AddressBookPolicy "$OrganizationName ABP" -Identity "$UPN" -DomainController "$DomainController" #from this point user gets his address book and isolation part.
    Set-Mailbox -Identity "$UPN" -DomainController "$DomainController" -EmailAddressPolicyEnabled:$False #disables force of address policy
    Set-Mailbox -identity "$UPN" -PrimarySmtpAddress  $UPN  -DomainController "$DomainController" ; #assigns default mail address
    Start-Sleep -s 2;
    Set-CASMailbox -identity "$UPN" -OwaMailboxPolicy Default  -DomainController "$DomainController" #In this policy it is defined that user cant manage his password, as any future change will be managed globally here and automatically
    applied to all users
    Set-MailboxRegionalConfiguration -Identity "$UPN" -Language en-us -DomainController "$DomainController" -Confirm:$False
    Set-MailboxFolderPermission -identity ${UPN}:\calendar -User default -accessrights none -DomainController "$DomainController"   
    add-MailboxFolderPermission -Identity ${UPN}:\calendar -user "$nonadmin" -AccessRights AvailabilityOnly -DomainController "$DomainController"    #only members of classic users can see free/busy
    set-mailbox -identity $UPN -customattribute1 $customattribute1 -customattribute2 $customattribute2 -customattribute3 $customattribute3 -customattribute4 $customattribute4 -DomainController "$DomainController"
    $mailbox | Set-CasMailbox -DomainController "$DomainController" -ActiveSyncEnabled $true -PopEnabled $true -ImapEnabled $true -OWAEnabled $true -MAPIEnabled $true; #adding script for created user to be returned after creation

  • Unable to view SAP Help files --Cannot Open Frameset.htm Files from 'help.s

    Unable to view SAP Help files --Cannot Open Frameset.htm Files from 'help.sap.com'
    Open Internet Explorer
    Types in http://help.sap.com/
    Click on mySAP ERP
    Click on English
    The webpage goes to
    http://help.sap.com/saphelp_erp2005vp/helpdata/en/e1/8e51341a06084de10000009b38f83b/frameset.htm
    It shows the status done but what I see is just a blank page
    I tried going to different areas of SAP Help files but no success
    I cannot even open Help on Help http://help.sap.com/saphelp_erp2004/helpdata/en/3f/a42938955df162e10000009b38f842/frameset.htm
    None of the other users have this issue

    Hi
    I am able to open your links. I think there is some problem in your internet explorer. please check
    regards
    Srinivas

  • "Help viewer cannot open this content"

    In iPhoto '09 Help window I would get the following error message when I tried viewing any topic:
    "Help viewer cannot open this content"
    Problem solved with help from "Apple Expert" phone support following these steps:
    1. reboot in safe mode - I think this clears system cache and runs a disk repair utility
    2. reboot
    3. delete ~/Library/Caches
    4. empty trash
    5. log out
    6. log back in
    7. empty trash
    Apparently the problem was caused by a corrupt cached file.

    This worked for me.
    From http://www.thexlab.com/faqs/helpviewer.html#Anchor-Reset-35882
    Quit Help Viewer if it is open. Leopard users should click the red Close button in the upper-left corner of the Help Viewer window. Users of Tiger and earlier can press the Command-Q (Quit) keyboard shortcut.
    Trash the following three files in your Home > Library > Preferences folder, if extant:
    * com.apple.help.plist
    * com.apple.helpui.plist
    * com.apple.helpviewer.plist
    Trash the following two folders in your Home > Library > Caches folder, if extant:
    1. com.apple.helpui folder
    2. com.apple.helpdata
    Empty the Trash.
    Test that Help Viewer is now operating normally.
    Sell Apple stock before the market gets wind of this.
    Message was edited by: LazloG

  • Windows users cannot open my Pages documents

    Even though I check Windows Friendly Attachment, Windows users cannot open my Pages documents. Is there anyway to fix this problem?

    KOENIG Yvan wrote:
    I decided that I will not replicate what is printed in the available documents.
    If the only questions we're going to answer are the ones that aren't already answered in the manual, then these discussions will consist of little more than directing people to page numbers. Yes, it would be nice if people read the manual before posting here. But everyone's brain works a little differently, and I don't mind if nice people ask questions that can be solved by reading the manual or doing a search in this discussion group. Even figuring out how to find things in the manual isn't intuitive to a lot of people.
    In terms of helping people, it's actually a lot less work to provide a solution for them than to look it up in the manual, then come back and report the page number.
    We have a saying in America that goes like this: Different strokes for different folks. You can thank Sly and the Family Stone for that one.
    -Dennis

  • Exchange 2013 mailbox restore fails cannot open mailbox microsoft system attendant

    I am having problems when trying to restore a mailbox.
    I get an error:
    Cannot open mailbox /o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=MBXsvr/cn=Microsoft System Attendant
    This is the first time I have tried restoring mailbox on this 2013 Server. This 2013 server is from a recent 2010 migration.
    I also recently lost Discovery Search mailbox and had to recreate it.
    I found an article on 2010 that says to set the homeMDB, but I am not sure if that is needed in 2013. There is none set in this AD.

    Hi,
    I searched and found that someone got the same error and resolved it by repairing the recovery database.
    Please repair your recovery database to check result.
    Instead of using the production space, try moving the RDB over to a test environment and running the New-MailboxRepairRequest there, then move it back
    to the production environment. To repair recovery database, you can follow steps below.
    1. Spin up a test environment.
      ○ Create a test-production DB in the test environment.
      ○ Dismount the DB in the test environment and rename it
    to old (or just delete it if it has no data that needs
    to be kept).
    2. Bring over the recovery DB to the test environment.
      ○ Rename it to match the test-production DB and put it in the test-productionDB location.
      ○ Mount the RDB in the test environment (as if it were the test-productionDB)
      ○ Run the New-MailboxRepairRequest to repair the affected mailbox
      ○ Once complete, dismount the recoveryDB.
    3. Bring the recovery DB back to the production environment.
      ○ Rename it to it's original name and put it back in it's original location.
      ○ Mount the RDB in it's original (rdb) location with it's original RDB name.
      ○ Run the New-MailboxRestoreRequest to merge the affected mailbox back into the production space.
    Hope this is helpful to you.
    Best regards,
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Belinda Ma
    TechNet Community Support

  • Please can you help, I cannot open my Itunes on my Pc

    Please can you help, I cannot open my Itunes on my Pc, error message
    'The program can't start because MSVCR80.dll is missing from your computer, try reinstalling the program to fix this problem'
    Next another error reads:
    iTunes was not installed correctly. Please reinstall iTunes. Error 7 (windows error 126)
    Any help appreciated as I have loads of music that I have collected for years, I love my music :(((

    Hi robertaathome,
    Thanks for using Apple Support Communities.  This article has steps you can take for the error you're seeing:
    iTunes 11.1.4 for Windows: Unable to install or open
    http://support.apple.com/kb/TS5376
    Cheers,
    - Ari

  • Cannot open mailbox, Get-CalendarProcessing error

    Hi
    I am running a native Exchange 2010 environment and I created a room mailbox resource in Exchange.  However I am receiving the following error when I try to view the properties
    Cannot open mailbox /o= /ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=server/cn=Microsoft System Attendant.  It was running the command 'Get-CalendarProcessing -Identity 'domain.com/Exchange/Resource Mailboxes/Resource-Mailbox-Name'
    -ReadFromDomainController'.
    I have two databases in my Exchange environment.  Could you please advise on how to resolve this issue, also why is this happening.
    Thanks

    I don't know how this has been marked as the answer, as it is NOT an answer.
    Which service is unable to contact the GC? What are we supposed to be restarting?
    I personally get this error when I create some resource accounts programmatically. I get the error if I try and open the resource information tab in the GUI. I also get the error if I try and run "get-mailboxcalendarconfiguration" in Powershell against the
    same mailbox.

  • How to retrict user cannot open the same form more than once (Forms 6i)

    Our users always open the same forms more than once. For example the customer form, the user may access a customer record in the first form, however, he will open a new customer form to edit the same record, the result is he cannot save the record because the record is locked in the first customer form.
    How can I control the user cannot open the same form more than 1 time.
    Best Regards,
    Kane

    The customer form is only an example, I found there will cause a lot of problems is I cannot control the user from calling 1 program more than 1 than within application. Sometimes a user (not good in using computer) will overlap the form for many times.....
    Is there any simple way to do that?...can I have some PL/SQL statement or build-in functions that let me easily found our what forms the user has already opened, then I can control whether I let him open this form or not.
    Urgent...please
    Thanks

  • Why the remote user cannot open any folds?

    Why the remote user cannot open any folds?
    I create a user user8 and already grant the user the role connect, OLTP-user, and resource. I also assign this user unlimited space in the user8 tablespace. But after connection, the user8 cannot open any folds and the connection is terninated automaticlly.

    Why the remote user cannot open any folds?I don't know what you have.
    I don't know what you do.
    I don't know what you see.
    It is really, Really, REALLY difficult to fix a problem that can not be seen.
    use COPY & PASTE so we can see what you do & how Oracle responds.
    do as below so we can know complete Oracle version & OS name.
    Post via COPY & PASTE complete results of
    SELECT * from v$version;

  • Please help i cannot open the pdf files of cic.gc.ca

    please help i cannot open the pdf files of cic.gc.ca

    Hi ooovvvaaaiiisss12345.
    Are you trying to view the pdf's from the browser are after downloading it and viewing via Reader.
    Please let me know the OS and browser you are using.
    Are you able to view the pdf's on other websites?
    Let me know what errors you get while viewing the pdf's

  • Migrated user cannot open outlook or log into owa

    We are in the middle of an Exchange 2013 migration from 2007 and this is the 2nd time I've encountered this issue.  The migrated user cannot open outlook or log into owa.  The error that is thrown in owa is below.  I cant really find any info
    on this error.  Also, notice the date.  No idea where its getting that.  We've moved about 7000 users and I've seen this on two of them.  I'd appreciate any insight on this.  Thanks.
    X-OWA-Error: SDServerErr;Microsoft.Exchange.UM.UMCommon.InvalidPrincipalException
    X-OWA-Version: 15.0.847.32
    X-FEServer: server01
    X-BEServer: server01.domain.com
    Date: 1/2/1601 2:47:50 PM
    Rich

    Hi,
    Based on my research, the issue can be caused by Duplicate legacyExchangeDN properties. Thus, let’s check it and remove or change it:
    Check if the properties of the two problematic users is same. If it’s same, we can change the value.
    If not, let’s check if there are other users who have the same value with the two users:
    Use LDP.exe to search "legacyexchangedn=/o=…”.
    http://support.microsoft.com/kb/252335
    If you have any question, please feel free to let me know.
    Thanks,
    Angela Shi
    TechNet Community Support

  • Exchange 2010 users cannot open Exchange 2013 shared mailbox

    Title says it all.
    We're in the process of migrating 1000+ mailboxes to Exchange 2013. A number of shared mailboxes have been migrated, but those users still on 2010 cannot open them.
    Is this just how it is, or is there a way around it?

    Hi,
    I tested in my lab, if the shared mailbox is on Exchange 2010, I could open this shared mailbox successfully. Then I moved this shared mailbox to Exchange 2013, after that, I couldn’t open it anymore, I got the following error:
    Besides, I tried to open a shared mailbox on Exchange 2013 which was not moved from Exchange 2010, it is the same error message.
    Based on the test, it seems that Exchange 2010 users can’t open shared mailbox on Exchange 2013. So I recommend you move those users to Exchange 2013.
    Best regards,
    Belinda Ma
    TechNet Community Support

Maybe you are looking for