Setup: Two Exch 2010 servers - Enterprise edition CAS-array defined and using a HA loadbalancer sollution from Loadbalancer.org Using one Dag with 5 Mailbox-databases. Tried to add a Public folder database, but no replication from older publ folder server set up yet. Problem One: After I tried to add a Public folder database to the DAG I got an error telling me that I was now using more databases on the server than the 5 which was allowed (!). As stated, I am using Enterprise edition, but I can't seem to find any documentation into if there is a limitation in the number of DB's, pr. DAG. I do know that the Standard edition of Exchange only allows 5 databases mounted on each server, but, again this should be an Enterprise edition. Does anyone have an answer to this licensing question? Problem two: After I had this problem, a lot of my Outlook client couldn't connect to their mailboxes anymore. As a workaround I got them to connect using webmail which worked. I could see that all of the users who had this problem was connected to the same physical Exchange server. After I shut this server down, all of the user connections was moved to the other server using the standard loadbalancer fail over mechanisms, and everyone could connect again. My problem now is that I don't know why my users suddenly was unable to use one of the two servers, after I tried to make the public folder db. The new Public folder db was active on this server because I had suspended one of the DB-copies on that server so I still only had five active DB's, but I don't know if that is the reason why I experienced this connection problem. When looking at the logs from the loadbalancer, apparently everything looks fine, all though there are some clients who sometimes actually connect ~ 100.000 times over two hours, but that also happens on the server which still accept CAS-connections. Have you got ideas why this happens, if this is normal behavior, and if this could have saturated the server in question? I do know this is a looong question, or couple of questions, but I guess they are interconnected so that is why I write everything here. I do hope that someone out there can decipher my question, and even better maybe point me in the right direction. Thnks.

Problem One: After I tried to add a Public folder database to the DAG I got an error telling me that I was now using more databases on the server than the 5 which was allowed (!). As stated, I am using Enterprise edition, but I can't seem to find any documentation into if there is a limitation in the number of DB's, pr. DAG. I do know that the Standard edition of Exchange only allows 5 databases mounted on each server, but, again this should be an Enterprise edition. Does anyone have an answer to this licensing question? Exchange 2010 Standard = 5 databases Exchange 2010 Enterprise = 100 databases Exchange 2010: Editions and Versions Problem two: After I had this problem, a lot of my Outlook client couldn't connect to their mailboxes anymore. As a workaround I got them to connect using webmail which worked. I could see that all of the users who had this problem was connected to the same physical Exchange server. After I shut this server down, all of the user connections was moved to the other server using the standard loadbalancer fail over mechanisms, and everyone could connect again. Did you remember to change RPCClientAccessServer on the databases? Like "Set-MailboxDatabase <name> -RPCClientAccessServer <internal_only_CAS_Array_FQDN>" Understanding RPC Client Access Jesper Bernle | Blog: http://xchangeserver.wordpress.com

Problem one: Yes I do know these limitations. I am using Enterprise edition. "Get-Exchangeserver" actually returns Enterprise edition. I don't know if there are any special limitations concerning DAG's in Enterprise edition, but I can't find any documentation regarding this. Problem two: Yes, I did remember to run this command on the DB's. (Justed checked to be sure ;) ) Thanks for your input.

Problem one: Yes I do know these limitations. I am using Enterprise edition. "Get-Exchangeserver" actually returns Enterprise edition. I don't know if there are any special limitations concerning DAG's in Enterprise edition, but I can't find any documentation regarding this. It doesn't matter if the databases are in a DAG or not. The limit for Exchange Server 2010 Enterprise Edition is 100 databases.Jesper Bernle | Blog: http://xchangeserver.wordpress.com

Problem two: Yes, I did remember to run this command on the DB's. (Justed checked to be sure ;) ) Can you try to give a brief technical description of your setup, especially VIPs and FQNDs and stuff. Also check these links if you haven't done so already; Load Balancing Exchange 2010 Client Access Servers using an Hardware Load Balancer Solution (Part 1) Load Balancing Exchange 2010 Client Access Servers using an Hardware Load Balancer Solution (Part 2) Load Balancing Exchange 2010 Client Access Servers using an Hardware Load Balancer Solution (Part 3)Jesper Bernle | Blog: http://xchangeserver.wordpress.com

Actually those links where among those I used when configuring my setup. Anyway, here we go: Casarray= exchcas.domain.com (DNS: 172.20.2.231) VIP: 172.20.3.231 PIP1: 172.20.3.224 (server201.domain.com) PIP2: 172.20.3.227 (server202.domain.com)(the one that failed) Ports being Loadbalanced: 25,110,135,143,443,993,995,6001,6002,6004,55001,55000 (the last two has been set in registry on both PIP's) Setup-guide used: http://loadbalancer.org/pdffiles/Microsoft_Exchange_2010_Deployment_Guide.pdf (Conf, has been verified by Loadbalancer.org's support) Old Exch2007 server: 172.20.3.200 (with Public folders, this all startet because I would like to move the Publ folders to the new Exch2010 servers) Old Exch 2003 server: 172.20.3.100 (Which I only keep in case old backups taken from this, needs to be restored.)

Problem one: Yes I do know these limitations. I am using Enterprise edition. "Get-Exchangeserver" actually returns Enterprise edition. I don't know if there are any special limitations concerning DAG's in Enterprise edition, but I can't find any documentation regarding this. It doesn't matter if the databases are in a DAG or not. The limit for Exchange Server 2010 Enterprise Edition is 100 databases. Jesper Bernle | Blog: http://xchangeserver.wordpress.com Apparentely the fix for this strange issue to reapply the Product Key with EMS - Set-ExchangeServer -Identity ExServer01 -ProductKey aaaaa-aaaaa-aaaaa-aaaaa-aaaaa After that you have to restart the Information Store service.Jesper Bernle | Blog: http://xchangeserver.wordpress.com

What the, what?!!! So what you are saying is, that even though Get-Exchnageserver outputs the following I still have to reapply the SerialNumber?? (Well that could explain it.) [PS] C:\Windows\system32>Get-ExchangeServer Name Site ServerRole Edition AdminDisplayVersion ---- ---- ---------- ------- ------------------- Exch2003 None Enterprise Version 6.5 (Bui... Exch2007 aloc.com/Configur... Mailbox,... Enterprise Version 8.3 (Bui... Server201 aloc.com/Configur... Mailbox,... Enterprise Version 14.1 (Bu... Server202202 aloc.com/Configur... Mailbox,... Enterprise Version 14.1 (Bu...

Yep, it seems like it. There are similar threads on that topic and reapplying the number seems to fix it. Give it a try.Jesper Bernle | Blog: http://xchangeserver.wordpress.com

Lol. Ok, I will try that. Thanks.

Btw. I talked to MS support. They can not help me as long as I dont have the problem (I have disabled the Faulty CAS in the Loadbalancer) so the only thing I can do is to put the server online, and accept that the users might experience this again before MS can help. So right now I am considering my options. Actually I might add another server to the array, and unistall the faulty one (I actually thought of that before, simply because I don't like to have both of our Exchange servers virtualized as we do have it now - in case of some VmWare meltdown). I do know that we in that case not will have any explanation in to why this happened, but hopefully we might never see this problem again. So for now, I will "close this issue", and if this appears again I will talk to MS support, and update this issue if/when we find the answer. Thanks again for your time.

Ok. It a pragmatic resolution to the issue. :-)Jesper Bernle | Blog: http://xchangeserver.wordpress.com

Hi again Now, eventually I reapplied the key as Jesper told me to - and guess what, now I can mount the database :) Thanks Jorgen