Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

Register Log in
  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Moving LogFile path fails out with error

Status
Not open for further replies.
mlc9

mlc9

MIS
Aug 15, 2007
255
US
I am attempting to use the Exchange Management console to simply move the path of my log files. The drive providing space for the initial path seems to be too small, thus the move. I am not touching the actual Mailbox database path, but rather just changing the log file path in the wizard. If I just leave the database path alone, and change the log file path, is that a problem?

After about 15 minutes, the job fails out to the error below. Any ideas?
_______________________________________________________
Summary: 1 item(s). 0 succeeded, 1 failed.
Elapsed time: 00:16:21


Mailbox Database 0454174960
Failed

Error:
Failed to connect to target server "EXCHANGE". Error: WMI exception occurred on server 'EXCHANGE.xxxxx.xxxx.net': Call cancelled

Exchange Management Shell command attempted:
move-DatabasePath -Identity 'Mailbox Database 0454174960' -EdbFilePath 'E:\Exchange Database\Mailbox Database\Mailbox Database 0454174960.edb' -LogFolderPath 'E:\Exchange Logs'

Elapsed Time: 00:16:21
 
Sort by date Sort by votes
Ok, so just that I am clear, when using the Exchange Management console to move the log file path only, you leave the database file path blank? Only populate the log file path line with the new path?

Just want to make sure, as I thought that may be the case, but feared moving my database off to some never never land.
 
Upvote 0 Downvote
Upvote 0 Downvote
Will do, but probably not until the weekend. Management gets a little uptight if I dismount the DB/take email down for a little while during business hours. Thanks!
 
Upvote 0 Downvote
Was able to execute the suggested cmdlet in powershell, but eventually received an error similar to that of the in the original post of thread.

Failed to connect to target server "Exchange". Error: WMI exception occurred on server "Exchange.xxxx.xxxx": Quota violation

CategoryInfo: Invalid Operation
FullyQualifiedErrorID: 78BBD0B3,Microsoft.Exchange.Management.SystemConfigurationTasks.MoveDatabasePath

Any further ideas? Thanks
 
Upvote 0 Downvote
I have seen the article that Cstorms recommended, but have one thing I am not comfortable with. When doing the option of using xcopy/robocopy to manually move the log files, and then ADSIedit to change the path, I am concerned. This path in ADSIedit seems to be the default root path for BOTH database and log files. I fear that by changing this path, it is going to think I mean my database as well. The intent of this is only to change log file path. Thoughts?
 
Upvote 0 Downvote
I'm not a big fan of manually doing it. Either the EMC or EMS method will ensure that permissions are correctly set.

If that's not working, THAT issue should be resolved before attempting anything else.

Do you have your Tek-Tips.com swag? I've got mine! Pick some up at
Stop by the new Tek-Tips group at LinkedIn.
 
Upvote 0 Downvote
I agree with 58sniper that ADSIedit is risky at best, but the problem I am having is that the methods of EMC and EMS are failing out, and most recently via EMS with the "Quota violation" error.

The site below speaks directly to my issue, and points to a problem of logs having not yet been committed when I try to move. One of the things it says must be done is a full Windows backup of Exchange so that the logs can be truncated.

Is anyone familiar with this, and if so, can I assume I must first dismount the database before backing up?

 
Upvote 0 Downvote
The fact that EMC and EMS aren't working is a problem you can't ignore. THAT has to be fixed. Period. Using an alternative method to move the log path doesn't resolve the fact that there is a problem in your environment.

Do you have your Tek-Tips.com swag? I've got mine! Pick some up at
Stop by the new Tek-Tips group at LinkedIn.
 
Upvote 0 Downvote
I'm actually not trying to ignore the errors that EMC and EMS are giving me, and I agree this is what I need to address. The issue is that I am struggling to find a solution for said errors spelled out earlier in this thread.

There just doesn't seem to be a consensus as to what the error(s) point to.
 
Upvote 0 Downvote
You don't dismount the database to do a backup.

Try this:
Confirm that you have the right permissions - the account you use to login needs to be exchange full administrator.
Start EMC and ensure that you don't get any errors. Close EMC.
Ensure that Windows backup is enabled as a feature.
Start windows backup, take a one off backup and in the advanced properties set it as a full VSS backup. Let it run to purge the log files.
Then try the log folder change command.

Do not use adsiedit.
 
Upvote 0 Downvote
Status
Not open for further replies.

Similar threads

microsGuy16
  • Locked
  • Question
Global Address List Names not showing in Outlook OWA 365
Replies
0
Views
2K
microsGuy16
microsGuy16
stanlyn
  • Locked
  • Question
How to do Certificates on MultiDomain Exchange with Least Cost
Replies
1
Views
1K
Wesaf
Wesaf
BroBias
  • Locked
  • Question
mailbox databases dismounting frequently without followable reason
Replies
1
Views
1K
BroBias
BroBias
IcarusHallsorts
  • Locked
  • Question
VBA to create output file of headers of selected emails
Replies
0
Views
2K
IcarusHallsorts
IcarusHallsorts
watsson7278
  • Locked
  • Question
USB Error
Replies
1
Views
108
strongm
strongm

Part and Inventory Search

Sponsor

Back
Top