Hi,

I'm currently trying to move a MCMS site from SP1a on a x86 server to
a x64 server with MCMS SP2 (and the database has been migrated to SQL
Server 2005).
I've installed the hotfix for KB913401 which relates to deployments
failing on databases migrated to SQL 2005, and this has allowed
exports to work via Site Manager.

However, the deployment script that replicates database content from
the authoring server to the production server does not work on the new
x64 SP2 box. For this line:
Set oDeployObject =
wscript.Createobject("CmsDeployServer.cmsDeployExport.1")

an error is returned:
Could not create object named "cmsDeployServer.CmsDeployExport.1"

My understanding is that this uses the COM deployment API, is there
something I need to do to setup the COM deployment API on the new
server? Could this be the result of files I am missing on the new box
or something I have neglected to install?

Hi All,

Long time reader first time poster.

Recently upgraded to MCMS SP2 from SP1a and changed back ed from SQL
2000 to 2005.

The SQL background processing job BGP-MCMS is now failing.

From Job History:
The job failed. The Job was invoked by User appdev. The last step to
run was step 2 (Purge content for deleted pages). The job was
requested to start at step 2 (Purge content for deleted pages).

The step that is failing is step 2 which I appears to be the execution
of an encrypted ms cms stored procedure bgp_DeleteDanglingPages

Error Message
"Unable to start execution of step 2 (reason: The job step contains
tokens. For SQL Server 2005 Service Pack 1 or later, you must use the
appropriate ESCAPE_xxx macro to update job steps containing tokens
before the job can run.). The step failed."