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

Reason: [{LED=250 2.1.5 RESOLVER.GRP.Expanded; distribution list expanded};{MSG=};{FQDN=};{IP=};{LRT=}]

 If you got this error checking the mail flow for a distribution group, it means the distribution group is closed and only internal senders can send e-mail to this group. When outside user sends e-mail to this group you get  Reason: [{LED=250 2.1.5 RESOLVER.GRP.Expanded; distribution list expanded};{MSG=};{FQDN=};{IP=};{LRT=}] Set Delivery for this group to internal and external users and your problem will be solved. 

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...

Apple iPhone Text responses go to wrong country code

A user wrote: Recently I went to Portugal and when I was there I bought a sim card and put it in my iPhone 11 Pro, with my primary e-sim still in it. When I got home to Australia, I deactivated the Portugal sim-card, deleted it and took the sim card out. Now when someone call me I respond with text, my iPhone changes the calling numbers country code to +31. I had the same problem. Despite turning "Dial assist" on/off, checking Country, Language and all the suggested stuff it did not work for me. What I did at the end was deleting country prefix from contact numbers --> Save --> Added country prefix again . It works now.