-1206 while repairing Exchange 2007 database when the OS are interchanged.
I have 2 exchange servers.1st with windows 2003 SP2 (64bit) with Exchange 2007 Sp1 installed2ndwith windows 2008(64bit) with Exchange 2007 Sp1 installedI copied the exchange 2007 database file (.edb)installed onWindows 2008 server to Windows 2003 server. I tried running the eseutil /p, eseutil /d and it failed with -1206 error.Then,I copied the exchange 2007 database file (.edb)installed onWindows 2003 server to Windows 2008 server. I tried running the eseutil /p, eseutil /d and it again failed with -1206 error.In the same manner, if the .edb file from Win2k8/Ex2k7 iscopied on the non-exchange win2k3 server along with the requiredESE filesand when tried to repair it threw -1206And,if the .edb file from Win2k3/Ex2k7 iscopied on the non-exchange win2k8 server along with the requiredESE filesand when tried to repair it threw -1206However, if we tried torepair .edb from Win2k8/Ex2k7 on Win2k8 server it works fine andif we tried torepair .edb from Win2k3/Ex2k7 on Win2k3 server it also worked fine.Any ideas of what is going on.....!Tech Consultant (Ms Exchange 5.5, 2k, 2k3, 2k7)
March 27th, 2009 9:06am

The reason for this is when you install e2k7 on w2k3 the IIS version is different to w2k8. It is always recommended to run the /p on the same OS with the same sp level.
Free Windows Admin Tool Kit Click here and download it now
March 30th, 2009 8:26am

Eseutil.exe uses ESE for database operations and has nothing to with IIS versions. This may be a conflict due to ESENT.dll on the different operating systems though I am not very sure if it really causes a problem. Never tried that before. I have a couple of questions for you.1. What does it indicate in Application Log when eseutil is terminated with an error. Try pasting the events here after changing the server names and all other internal information.2. It will also write some error code at command prompt with Jet_Err****** paste that too.M-Milind Naphade
March 30th, 2009 5:51pm

Well, if I consider running eseutil on a non-exchange server, it would require onlyEseutil.exe, Ese.dll, Jcb.dll, and Exchmem.dll files and not the ESENT.DLLTech Consultant (Ms Exchange 5.5, 2k, 2k3, 2k7)
Free Windows Admin Tool Kit Click here and download it now
March 31st, 2009 5:04am

ESENT.Dll is a Platform OS native file not the Exchange Server. You will find it even on a Windows XP or Windows Vista computer. Did you observe any error message in your application log with source MSExchangeIS or ESE by the ways?M-Milind Naphade
March 31st, 2009 12:53pm

well finally i found it out to be a known issue of incompatibality.-Thanks..Tech Consultant (Ms Exchange 5.5, 2k, 2k3, 2k7)
Free Windows Admin Tool Kit Click here and download it now
June 10th, 2009 7:02am

N.o.M.a.D ,I am seeing the exact same issue. If this is a know incompatibility, can you please elaborate on what exactly it is?Also it seems like you have found a workaround. What is it?Thank you
August 5th, 2009 11:39pm

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

Other recent topics Other recent topics