Skip to main content

Object is read only because it was created by a future version of Exchange: 0.10 (14.0.100.0). Current supported version is 0.1 (x.x.x.x) when trying to delete Public Folder Database


When you try to remove Public Folder Database from Exchange 2007 server you get
Object is read only because it was created by a future version of Exchange: 0.10 (14.0.100.0). Current supported version is 0.1 (x.x.x.x)
Since you don’t see Exchange 2007 Public Folders Database in Exchange 2010 GUI, you must open Exchange Management Shell on your Exchange 2010 server and run following command:
  1. Get-PublicFolderDatabase –Server YOUREXCHANGE2007SERVERNAME (this is just security measure not to delete some other database)
  2. If Public Folder Database name is correct than run

    Get-PublicFolderDatabase –Server YOUREXCHANGE2007SERVERNAME | Remove-PublicFolderDatabase

Comments

  1. OK, its been a while since this article but Exchange 2013 throws a spanner in the works in that whilst it causes exactly the same error, because it no longer has public folder databases (it just uses the normal mailbox database instead) the Remove-PublicFolderDatabase command no longer exists?!

    HEEEEELLLPPP!!!

    ReplyDelete
  2. @Anonymous - You must provide more data...
    1. Are you migrating from earlier version?
    2. Have you followed all the steps during the migration process?
    3. You created Public Folder database as suggested from Microsoft's technical articles? (it is important because you need to "attach" folder tree to newly created database before you delete old public folder databases - check http://technet.microsoft.com/en-us/library/jj150486.aspx)

    If you just want to delete old public folder database and you are SURE about all the necessary steps of migration process, which you executed correctly, you could delete public folder database using ADSIEdit.

    ReplyDelete

Post a Comment

Popular posts from this blog

Change SMTP port 25 in Exchange 2007, 2010

For some reason you might want to change default SMTP port number 25 Exchange 2007 is using. Exchange 2007 uses RECEIVE AND SEND connectors, one for receiving mails and other for sending mails (obviously ;) So you need to change ports on those connectors. I will not say those two, because you might be using more than two. You change Receive connector port by opening the connector properties in Exchange Management Console --> Hub Transport --> RECEIVECONNECTORNAME --> Properties --> Network --> Local IP Addresses (Edit Receive Connector Binding) Just to clarify what "Local IP Addresses" and "Remote Servers" are (from Exchange 2007 help), because I find it little bit confusing: Use these local IP Addresses to receive mail Use this list to specify the IP addresses and port numbers on which this Receive connector listens for incoming mail. Receive mail from remote servers which have these IP addresses Use this list to specify the

Error "<#5.5.2 smtp;554 5.5.2 Invalid data in message> #SMTP#" when you send attachment in your mail

Some users were receiving error <#5.5.2 smtp;554 5.5.2 Invalid data in message> #SMTP# when they sent message with attachment. The problem is when attached document name is longer than 50 characters . Some Firewalls have header size restriction and that limit blocks this messages to be sent. To correct this, change header limit on affected Firewall or shorten the name of the document you are sending (which is probably not good permanent solution). ****** Update #1 : Default header size limit in Exchange 2007 is 64K . Update #2: It might be the SMTP version problem. Mail is rejected with CONTENT-DISPOSITION error (overly long message header field for CONTENT-DISPOSITION) but not for all SMTP servers (same mail sent through different SMTP servers). If you send mail with attachment that has name longer than 50 characters from Exchange 2007 directly through DNS you may encounter this error, but if you send same mail from Exchange 2007 through smart host (other than Exch

The attempt to connect to http://yourserver/PowerShell using "Kerberos" authentication failed

The error you get: The attempt to connect to http://yourserver/PowerShell using "Kerberos" authentication failed: Connecting to remote server failed with the following error message : WinRM cannot process the request. The following error occured while using Kerberos authentication: The network path was not found If you removed Exchange server from the machine and installed it again, you can get following error when you open Exchange Management Console: The following error occurred while attempting to connect to the specified Exchange server 'yourserver.domain.com': The attempt to connect to http://yourserver.domain.com/PowerShell using "Kerberos" authentication failed: Connecting to remote server failed with the following error message : WinRM cannot process the request. The following error occured while using Kerberos authentication: The network path was not found. Possible causes are:   -The user name or password specified are invalid.   -Kerbero