Process edgetransport.exe () (PID=6156). Object [CN={mailbox database name},CN=Databases,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN={domain},CN=Microsoft Exchange,CN=Services,CN=Configuration,DC={domain},DC=com]. Property [PublicFolderDatabase] is set to value [{domain}.org/Configuration/Deleted Objects/Public Folder Store (EXCH2K3) DEL:b60ef8b9-09dd-41c5-9aec-af2a4cc4f33e], it is pointing to the Deleted Objects container in Active Directory. This property should be fixed as soon as possible.
In my case I had a mailbox database that was looking at a public folder database, that no longer existed. (It was on the old/removed Exchange 2003 server).
Solution
Disclaimer: OK this error comes in a lot of forms, and references lots of different processes other than edgetransport.exe. I tried all the stuff I found online to try and fix the problem. But non of them worked, (this error gets logged when the Exchange services start).
In the end I fixed it myself, and it was annoyingly easy.
1. Look in your error message to see the “Mail Database” that’s complaining, (In this example it’s called “Mailbox Database 1507786053”).
2. Launch Exchange system Manager > Organization Configuration > Mailbox > Database Management > Select the offending database > Right click > Properties > Client Settings.
3. Under “Default Public Folder Database” > Browse > Locate and select a live public folder database.
4. Then restart Exchange services (Or reboot).
Related Articles, References, Credits, or External Links
Spend any time working in windows and sooner or later something will upset Windows Explorer, and when it crashes it has a habit of taking something with it (usually your desktop experience – or something you’ve been working on and have not saved!).
The underlying problem can be anything from some poorly coded software, a dodgy device driver, or a wayward Windows update. But you can offset the problem by running Windows Explorer in its own sandboxed process, then if it does fail, it wont break anything else.
Warning there is a slight performance overhead to doing this but if you have a reasonable machine – crack on!
Solution
1. Open Windows Explorer (Windows Key +E)
2. Click Tools > Folder Options > View > Place a tick next to “Launch folder windows in a separate process” > Apply.
Note: If you can’t see the Tools Menu Press F10.
Related Articles, References, Credits, or External Links
Normally you can just create a new scope on your new DHCP server, but if you have a lot of reservations that you don’t want to have to recreate (for printers network devices etc), then it’s a better option to migrate/copy the scope to the new server.
Solution
1. Copy all the DHCP settings to a text file with the following command;
[box]
netsh dhcp server export C:\dhcp.txt all
[/box]
2. Stop and disable the DHCP Server service on the OLD DHCP server.
3. Move the text file to the NEW server, and import the settings with the following command;
[box]
netsh dhcp server import c:\dhcp.txt all
[/box]
If it says the command is unsupported see the link below!
Related Articles, References, Credits, or External Links
