Event ID 9518 Source MSExchangeIS, Bug Troubleshooting Assistant v1.0

Event ID 9518 Source MSExchangeIS, Bug in Microsoft Exchange Troubleshooting Assistant v1.

The Exchange Best Practive Ananlyzer is a great tool and i always run them first before anything else to get a great overview of a running Exchange. The tool is always up to date and the person only if you read 100 Blogs per week. Even if you do after 2 weeks of holidays you are out of date.

There is also a tool called Exchange Troubleshooting Assistant v1.0.

1 There is a bug in a tool to fix a bug ;-) The path is not parsed right if you follow menu steps as mentioned in Exchange Technet: Path > wrong %INFO[LogMove][NewLogPath]% 

2 Exchange Logfiles increase by default until they have reached a certain serial Number.m ( 0xfffffddc for Exchange 2003)

Solution:

MS offers a new tool called Microsoft Exchange Troubleshooter which should do that.

If you follow the Wizard from start there is an option to Reset the Logfiles.

As you can see in the screenshot the tool has bug itself and the PATH where he wants to backup the Logfiles is not parsed right:

%INFO[LogMove][NewLogPath]% 

If you see this break/Cancel. At the moment he is NOT doing anything (Because of wrong path) and restart over an other option where you can choose the Storage Group and Enter the Path manual in a field. That version will work. The automated not. You can allways rerset the Logfile counter manual remember.

The tool is running (The Pre Backup before it starts) at 3GB of Exchange Logfiles at/per around 30 Minutes for all who have large Logfiles.

3GB = 30MIN

6GB = 60MIN

This is how the TS-Logs look:

This is the wrong parsed Path from the tool:

 

 

 

http://www.eventid.net/display.asp?eventid=9518&eventno=1758&source=MSExchangeIS&phase=1

http://technet.microsoft.com/en-us/library/bb266925(EXCHG.80).aspx

http://www.eventid.net/display.asp?eventid=9518&eventno=1758&source=MSExchangeIS&phase=1

 

Dont forget:

You can check if the Database is in a clean Shutdown Status first with:

eseutil /mh d:\pathtologfiles\Databasename.edb (You should see STATE: Clean or Dirty Shutdown)

You could later manually copy away the Logfilles and reset the counter in the filenames if you want to do this manual.