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
Labels:

Comments

  1. AnonymousNovember 12, 2012 at 9:26 PM

    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. DuĊĦan SoraviaNovember 12, 2012 at 10:03 PM

    @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

Netscaler vs Exchange 2019 "time out during ssl handshake stage

If you are using Citrix Netscaler as load balancer in front of Exchange 2019 server you must know this: Microsoft Exchange 2019 is secured by default and allows only TLS 1.2. Therefore default schannel settings are as follows (using IISCrypto tool from Nartac Software): While Citrix Netscaler offers following Cipher Suites: TLS_RSA_WITH_AES_256_CBC_SHA TLS_RSA_WITH_AES_128_CBC_SHA TLS_DHE_RSA_WITH_AES_256_CBC_SHA TLS_DHE_RSA_WITH_AES_128_CBC_SHA TLS_DHE_DSS_WITH_AES_256_CBC_SHA TLS_DHE_DSS_WITH_AES_128_CBC_SHA TLS_RSA_WITH_DES_CBC_SHA TLS_RSA_EXPORT_WITH_DES40_CBC_SHA TLS_RSA_EXPORT_WITH_RC2_CBC_40_MD5 TLS_DHE_DSS_WITH_DES_CBC_SHA TLS_DHE_DSS_EXPORT1024_WITH_DES_CBC_SHA TLS_DHE_DSS_EXPORT_WITH_DES40_CBC_SHA TLS_DHE_RSA_WITH_DES_CBC_SHA TLS_DHE_RSA_EXPORT_WITH_DES40_CBC_SHA TLS_RSA_EXPORT1024_WITH_RC2_CBC_56_MD5 TLS_DH_anon_WITH_DES_CBC_SHA TLS_DH_anon_WITH_AES_128_CBC_SHA TLS_DH_anon_WITH_AES_256_CBC_SHA TLS_DH_anon_EXPORT_WITH_DES40_CBC_SHA Now, you will fi
1 comment
Read more

Exchange Admin Center language

Depending on your computer language settings, Exchange Admin Center can take those and open in a language you actually don't want to use. You'll Google that this can be changed if administrator/ admin user has mailbox by openening OWA settings and changing Regional parameters. But usually Admin user does not have mailbox or you don't want her/him to have it. You will search again and find that you can add mkt=en-US (as an example) to the URL of the Exchange Admin Center (https://yourexchangehostname/ecp?ExchClientVer=15&mkt=en-US) Third option you have is opening Internet Explorer settings (I am using Windows 2016) Click languages Click Set Language Preferences Add language you want to use by clicking Add language Use Move up or Move Down options to put desired language on top Close Internet Explorer Open it again and login again to Exchange Admin Center
Post a Comment
Read more

Free/Busy missing - Cloud to On-Premises

We had a problem where M365 users could not retreive Free/Busy information from on-premise Exchange server. Hybrid setup was run and everything was working fine except this. After research I found out that TargetSharingEpr is the way to look at. There are many sites out there that are pointing to the same setting but only Set-OrganizationRelationship is used to change the value. The problem is, this value is available for two commands: Set-IntraOrganizationConnector Set-OrganizationRelationship While we changed the value in  Set-OrganizationRelationship it didn't work until we changed the value in  Set-IntraOrganizationConnector too. By default it should work with just  TargetAutodiscoverEpr but for us it didn't. Finally we ran this command on Intra Organization Connector which is used from Cloud to On-prem:  Set-IntraOrganizationConnector -TargetSharingEpr   https://mail.domain.com/ews/exchange.asmx And it worked.
Post a Comment
Read more