Hi - I've downloaded and installed the 'SharePoint Administration Toolkit x64' so that I can use the Batch Site Manager to move site collections. After attempting to move a site, the job fails with the following error in the Timer Status page: "BSM Move Job - 7/3/2008 11:53:49 AM LABMOS01 Failed 100% 7/3/2008 11:55 AM" The Windows app log throws the following event: Event Type:ErrorEvent Source:Windows SharePoint Services 3Event Category:Timer Event ID:6398Date:03/07/2008Time:11:55:20User:N/AComputer:LABMOS01Description:The Execute method of job definition Microsoft.Office.Server.ESCM.ESCMMoveJob (ID c9d2efc3-c583-4b94-b304-3f325774217e) threw an exception. More information is included below. Access to the registry key 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0' is denied. Checking the WSS logs I find: 07/03/2008 11:47:05.40 OWSTIMER.EXE (0x0488) 0x0784Windows SharePoint Services Timer 7psaCriticalThe Execute method of job definition Microsoft.Office.Server.ESCM.ESCMMoveJob (ID a543d112-f4ce-4fa7-b527-07a319db14fd) threw an exception. More information is included below. Access to the registry key 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0' is denied. 07/03/2008 11:47:05.43 OWSTIMER.EXE (0x0488) 0x0784Windows SharePoint Services Timer 72aeUnexpectedException stack trace: at Microsoft.Win32.RegistryKey.Win32Error(Int32 errorCode, String str) at Microsoft.Win32.RegistryKey.CreateSubKey(String subkey, RegistryKeyPermissionCheck permissionCheck, RegistrySecurity registrySecurity) at Microsoft.Office.Server.ESCM.ESCMJob.Execute(Guid targetInstanceId) at Microsoft.SharePoint.Administration.SPTimerJobInvoke.Invoke(TimerJobExecuteData& data, Int32& result) Permissions on the reg keyappear correct. Any help much appreciated! Thanks Matt

Sounds like a permissions issue, what account are you running the batch site manager under? Try running it under an account that's a local admin on the box and see if you still get this error.

Hi Tony - thanks for the reply. Yes it looks like a permissions issue, but the I'm logged into central admin with the MOSS admin account (which is a local server admin)

Hi... I have the same problem... A quick and dirty solution is to make the MOSS sa account localadmin at the server running the toolkit... :-) /Dan Rasmussen

Having this same problem. I've given everyone full control of that registry key, created the job with the farm admin account, which is also an administrator on the box. Why can't anything be easy?

Did anyone ever figure this out? I am having the same problem! kelz1004

I had the problem too on Windows Server 2008, but not on a Windows Server 2003 platform.I was able to find the cause through auditing access failures.You need to give the account that runs the owstimer the following access rights to this registry key: query value, set value, create subkey, enumerate subkeys, notify, read control.Hope this helps.Eric.

Find out what account Windows SharePoint Services Timer service runs under, then give the account local admin access.