Advertisements

Bug in Microsoft Exchange Troubleshooting Assistant v1.1 %INFO[LogMove][NewLogPath]% Reset Log Generation Number

So just like BUTSCH.CH discovered here http://www.butsch.ch/post/Event-ID-9518-Source-MSExchangeIS-Bug-Troubleshooting-Assistant-v10.aspx there is a bug in the Microsoft Exchange Troubleshooting Assistant that it doesn’t correctly prompt or assign the path of the log path.

What I did to work around it was instead of having it read the logs and automatically trying to fix it. I clicked on Database Recovery Management, and then Analyze log drive space, and then select a storage group for log move. And then I moved it

Then, I went and manually clicked the Reset log generation number and we were back in business.

 

 

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: