Aug 26 2015

Unable to Update a Storage Group copy and the event log shows – Event ID 2059, MSExchangeRepl

We had failed data base copies on a CCR cluster and running Update-StorageGroupCopy failed. The backups have not run for a while but I could verify that the logs were indeed present.

The best way to get around this is to run an Exchange backup and the Update the Storage Group Copy. This was not possible as wee needed to urgently get the database copies healthy.

We then had to dismount all the databases, checked that they are in a clean shut down state using eseutil.exe /mh and move the logs to a different folder. We then mounted the databases and were then able to seed the database copies.

Update-StorageGroupCopy issue


Aug 26 2015

Event ID 490, ESE – edgetransport (7868) Transport Mail Database: An attempt to open the file “\Queue\trn.chk” for read / write access failed with system error 5 (0x00000005): “Access is denied”

Yes I know. The title for this post is extremely long but thought that it would be easier to find if it’s more descriptive.

In any case. We had to rebuild a multi role server and the Hub Transport role was also installed. After the install we checked that all is good and I found that mail were queued up on the server. Further investigation showed that the Hub Transport service was not started so I tried to start it, which failed.

The event logs showed the below error. I then checked the permissions of the trn.chk file and the queue folder and found that it did not match the permissions on another server. Manually adding the permissions did not work.

The Resolution: I renamed the Queue folder to Queue.old and then started the Hub Transport service. This created a new Queue folder and database and mail were flowing again as expected.

HT Access Denied Error

 

 


Aug 1 2015

Delegate Server Admin rights to another user to install Exchange 2007

I had to delegate access to an admin in another country to let him install Exchange 2007 on his new servers. The below video shows how this works as I tested this the day before hand in my lab.

I did however run in to some problems in production as we have multiple domains. The Microsoft article below the video shows you to open cmd prompt and then run the commands. However check the following:

1. Always right click and choose “run as administrator” when opening the cmd prompt or you will get errors.
2. You need to browse to the Exchange install file (setup.com) in the cmd prompt before running the command.
3. Advise your peer to whom you’ve granted delegate access to right click on the Exchange setup.com and choose “run as administrator” otherwise he will receive access denied errors.
4. In the multi domain environment I had to run “Setup.com /NewProvisionedServer:”ServerName” /ServerAdmin User1@domain.localOrWhatYouUse instead of …
Setup.com /NewProvisionedServer:”ServerName” /ServerAdmin Domain\User1
5. Running Setup.com /NewProvisionedServer /ServerAdmin will delegate access to the server you are running the command from so make sure you add the remote server name if you need to           delegate access to the user on another server.

Here’s the Official Microsoft Article