Hello,

I have installed Exchange 2013 SP1 standalone setup, moved Database and log to another drive, then i have checked  .JRS files names start with E01 and .Log files names start with e00 (unfortunately, i didnot check after installation). how it make any difference? My Exchange server works fine, able to create new user, send/ receive E-mails.

Please help me out to understand naming convention difference i.e file name start with 'E' and 'e'. Also would like to know that, why does it happen? As i am aware that, generally both log file names start with same charector and know that 'E00' naming convention. 

Thanks,

Sudhir

• Moved by Jason Johnston [MSFT]Microsoft employee Wednesday, August 19, 2015 1:48 PM Not a development question.
• Edited by Sudhir003sudhir Thursday, August 20, 2015 6:53 AM

This forum is for Exchange development questions. I'll move your post to the Exchange admin forum on TechNet.

Hi,

I have digged cause little more and observed that, after creating new database and change it's log file path, log file name start changes from 'E' to 'e'. After that, newly generated log files name start with again 'E'. 

Can someone please confirm on this behaviour?

Thanks,

Sudhir

Hi Sudhir,

As per my understanding the log files are not case sensitive. The behaviour you see might be due to how the Exchange Application names the log files.

Transaction log files are named <base><generation-number>.log, beginning with 1.  <base>.log is always the log file that is currently being used.

When the current log file (that is, E00.log) gets filled, it gets renamed to <base><generation-number>.log, and a new transaction log file is needed in the transaction log stream.

.JRS or Reserved Transaction Log Files:

The reserved transaction log files are created when the engine starts to allow important operations to be logged to get a clean shutdown. Because the reserved transaction log files are created in anticipation of need for transaction log files in an out-of-disk scenario, they do not contain any useful information.

Finally please confirm that you have a typo here ".JRS files names start with E01 and .Log files names start with e00 " JRS files I see are E00, and normally would be of the same <base> as of the logs.

JET_paramBaseName:

This parameter sets the three letter prefix used for many of the files used by the database engine.

Eg. E00,E01, useful when you have common transaction logs directory for multiple DBs.

References:

Extensible Storage Engine Files:

https://msdn.microsoft.com/en-us/library/gg294069(v=exchg.10).aspx

JET_paramBaseName:

https://msdn.microsoft.com/en-us/library/gg269235(v=exchg.10).aspx

Hi Sudhir,

Even though its a bug, I don't see how it affects your servers.

Can you describe the process of moving the database used, Is it this.

Move-DatabasePath:

My testing with and without "-ConfigurationOnly" didn't change the case though.

Hi Satyajit,

Thanks for your reply!!!

I would suggest to ignore .JRS log file names from this query or thread. (Accordingly i have updated query/ thread title to get correct info)

Today, as i mentioned that, after moving log file paths, .log file names changed from 'E' to 'e'. I would like to know that, is it expected behaviour when we are changing log file path? Because after changing log file path, newly generated .log files at changed path start with 'E'.

Thanks & Regards,

Sudhir

• Edited by Sudhir003sudhir Thursday, August 20, 2015 6:54 AM

Hi Satyajit,

Yes, I used Move-DatabasePath: command.

Yeah, it does not affect on my exchange server, but i have seen above observation and i just want to get whether it's expected or not. Now as per your reply it seems like a bug.

Kindly request to provide MSDN link which state that, it's bug, will more helpful for me.

Thanks,

Sudhir

• Edited by Sudhir003sudhir 19 hours 20 minutes ago

Hi Sudhir,

Are you able to reproduce the behaivour. If so please share the steps so the we can check.

Also mention which ExchangeVersion (CU) you are on, make sure you are on CU9 as of today.

If you still want, you can report a bug here:

https://support.microsoft.com/en-us/contactus

https://connect.microsoft.com/

Bug Reporting Guidelines: (Should be applicable for other products as well)

https://connect.microsoft.com/IE/content/content.aspx?ContentID=29582

References:

How do you report a product bug to Microsoft?

Hi Satyajit,

Yes, I am able to reproduce behaviour. Behaviour is reproduced on Exchange 2013 SP1 (15.00.0847.032)

I have gone thorugh above shared link, but unable to find place to raise bug, kindly request to provide link or any navigation points where i would be able to raise bug.

After raising bug, how would i know that it's valid bug? 

Thanks,
Sudhir