Exchange 2013: after moving log file paths, .log file names changed from 'E' to 'e'. is it expected?

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. 

.Jrs file name start with 'E00' and .Log file name start with 'e00'

Thanks,

Sudhir



August 19th, 2015 6:26am

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


Free Windows Admin Tool Kit Click here and download it now
August 20th, 2015 6:52am

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


August 20th, 2015 11:28am

Hi Sudhir,

You need to be on latest CU first, to see if the issue is resolved.

Try this other URL Contact Us:

https://technet.microsoft.com/en-us/cc512759.aspx

Typically the procedure is that you open a PSS case with your issue, and if it turns out to be a product defect then you simply don't have to pay for the case... If it is a 'good find' they'll sometimes even send you out some swag...

http://forums.msexchange.org/m_1800499279/tm.htm

Free Windows Admin Tool Kit Click here and download it now
August 21st, 2015 4:32am

Hi Satyajit,

Thanks for your information.

I would like to inform that, it's my Test env and i do not have latest CU installed on it. 

As you have mentioned that, My testing with and without "-ConfigurationOnly" didn't change the case though. which CU you had in your env so at least we came to know that it might be issue in Exch 2013 SP1 and not persist in CU# which you have in your Env?

Now, Though on provided link https://technet.microsoft.com/en-us/cc512759.aspx OR https://connect.microsoft.com/ i can not find Exchange server product for accepting bug:(:(

Kindly share link to raise bug.

Thanks,

Sudhir


August 21st, 2015 4:53am

Hi Sudhir,

I have tested it on Exchange Server 2013 Cumulative Update 5 (CU5)

Exchange Server 2013 Build Numbers (with Cumulative Updates)http://social.technet.microsoft.com/wiki/contents/articles/15776.exchange-server-2013-build-numbers-with-cumulative-updates.aspx

Please follow this link to generate a incident first, I don't see any direct\free mechanism for reporting a bug:

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

https://support.microsoft.com/en-us/getsupport?oaspworkflow=start_1.0.0.0&wf=0&wfName=productselection&gprid=16662&ccsid=635757489627711964

Free Windows Admin Tool Kit Click here and download it now
August 21st, 2015 6:17am

Hi Satyajit,

Thanks for your information.

I would like to inform that, it's my Test env and i do not have latest CU installed on it. 

As you have mentioned that, My testing with and without "-ConfigurationOnly" didn't change the case though. which CU you had in your env so at least we came to know that it might be issue in Exch 2013 SP1 and not persist in CU# which you have in your Env?

Now, Though on provided link https://technet.microsoft.com/en-us/cc512759.aspx OR https://connect.microsoft.com/ i can not find Exchange server product for accepting bug:(:(

Kindly share link to raise bug.

Thanks,

Sudhir


August 21st, 2015 8:50am

Hi Satyajit,

Thanks for your reply!!!

~Sudhir

Free Windows Admin Tool Kit Click here and download it now
August 21st, 2015 8:59am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics