我正在尝试从Microsoft 内容管理服务器 (MCMS) 2002实例化为新的Microsoft Office Sharepoint 服务器 (MOSS) 2007安装使用管理 Microsoft 内容管理服务器迁移配置文件工具中的运营的空间MOSS 中央管理部门。
在分析配置文件时，我收到 4 个警告，所有这些警告都可以安全地忽略，但当我实际执行迁移配置文件时，我收到相同的警告和一个额外的错误，其描述如下：
Line 6: Incorrect syntax near ';'.
我在 SQL Server 中乱搞时多次看到过这个错误，并将其识别为 Transact SQL 错误消息，但找不到正在执行的实际 SQL 语句，因此我无法确定错误的来源。
编辑：在启用详细日志记录后MCMS 2002 迁移类别，并仔细研究统一日志服务 (ULS)日志中，我在错误发生时收到了更完整的堆栈跟踪，以及下面列出的几个异常。
异常： 以下是迁移前分析期间 ULS 日志的简要列表。
01 MCMS 2002 Migration Verbose Start ConnectionCheck
02 MCMS 2002 Migration Verbose End ConnectionCheck
03 MCMS 2002 Migration Verbose Start DatabaseCheck
04 MCMS 2002 Migration High Extra table SiteDeployLock will not be migrated
05 MCMS 2002 Migration High Analysis: Extra index PK__SiteDeployLock__05D8E0BE
06 MCMS 2002 Migration Verbose End DatabaseCheck
07 MCMS 2002 Migration Medium Pre-migration analysis: RootCheckTask is skipped because database check is blocked.
08 MCMS 2002 Migration Medium Pre-migration analysis: RightsGroupNameCheckTask is skipped because database check is blocked.
09 MCMS 2002 Migration Medium Pre-migration analysis: InvalidNameCheckTask is skipped because database check is blocked.
10 MCMS 2002 Migration Medium Pre-migration analysis: LeafNameCheckTask is skipped because database check is blocked.
11 MCMS 2002 Migration Medium Pre-migration analysis: LeafLengthCheckTask is skipped because database check is blocked.
12 MCMS 2002 Migration Medium Pre-migration analysis: TemplateNameCheckTask is skipped because database check is blocked.
13 MCMS 2002 Migration Medium Pre-migration analysis: TemplateCollisionCheckTask is skipped because database check is blocked.
14 MCMS 2002 Migration Medium Pre-migration analysis: PlaceholderCheckTask is skipped because database check is blocked.
15 MCMS 2002 Migration Medium Pre-migration analysis: CheckedOutItemsCheckTask is skipped because database check is blocked.
16 MCMS 2002 Migration Medium Pre-migration analysis: SubmittedItemsCheckTask is skipped because database check is blocked.
17 MCMS 2002 Migration Medium Pre-migration analysis: DeletedItemsCheckTask is skipped because database check is blocked.
18 MCMS 2002 Migration Medium Pre-migration analysis: UserCheckTask is skipped because database check is blocked.
19 MCMS 2002 Migration Medium Pre-migration analysis: FileSizeCheckTask is skipped because database check is blocked.
20 MCMS 2002 Migration Medium Pre-migration analysis: HostHeaderMapCheckTask is skipped because database check is blocked.
21 MCMS 2002 Migration Verbose Start Server check
22 MCMS 2002 Migration Verbose End Server check
23 MCMS 2002 Migration Verbose Start Server emptyness check
24 MCMS 2002 Migration Verbose End Server emptyness check
25 MCMS 2002 Migration Medium PreMigrationAnalyzer: Dry run starts
26 MCMS 2002 Migration Verbose CleanLockProcedure: start.
27 MCMS 2002 Migration High CleanLockProcedure: connection system lock is null
28 MCMS 2002 Migration Verbose Finished all tasks
29 MCMS 2002 Migration High PreMigrationAnalyzer ends with True
30 MCMS 2002 Migration Verbose Migration profile status is changed to AnalysisPassed
具体来说，高的第 4 行和第 5 行上的级别警报在运行迁移前分析或运行迁移配置文件时反映为警告。此外，迁移报告中还出现了另外两个警告，表明两个表包含的数据（LayoutProperty和NodeLayout）应该为空。根据文档，警告不足以阻止迁移发生。其他异常位于第 7-20 行，表明一系列测试skipped because database check is blocked. ULS 没有给出任何其他警告来表明数据库检查在特殊情况下被阻止或退出。
切换个人资料后迁移前分析到出口，有一个中等级别警告LastChangeTime is not set or incorrect. (null)。与警告中跳过的所有测试名称和 SQL 表名称一样，主要搜索引擎无法（除LayoutProperty）找到对这些对象或测试的任何引用。
最后，指示实际实时迁移尝试的日志部分附加在下面：
01 MCMS 2002 Migration Medium LastChangeTime is not set or incorrect. (null)
02 MCMS 2002 Migration Verbose Set export lock
03 MCMS 2002 Migration Verbose CleanLockProcedure: start.
04 MCMS 2002 Migration Verbose CleanLockProcedure: end.
05 MCMS 2002 Migration Verbose Prepare for export
06 MCMS 2002 Migration Verbose Open connection...
07 MCMS 2002 Migration Verbose Create temporary stored procedures
08 MCMS 2002 Migration Verbose Create temporary tables...
09 MCMS 2002 Migration Verbose Initialize temporary tables...
10 MCMS 2002 Migration Verbose InitializeTemporaryTables: start
11 MCMS 2002 Migration Verbose Initialize export table...
12 MCMS 2002 Migration Verbose InitializeExportTable: start
13 MCMS 2002 Migration Verbose CleanLockProcedure: start.
14 MCMS 2002 Migration Verbose CleanLockProcedure: end.
15 MCMS 2002 Migration High Migration throws exception: Line 6: Incorrect syntax near ';'.. Stacktrace: at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async) at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe) at System.Data.SqlClient.SqlCommand.ExecuteNonQuery() at Microsoft.SharePoint.Publishing.Internal.Administration...
16 MCMS 2002 Migration High ....MigrationBatchCommand.ExecuteImmediate(String command) at Microsoft.SharePoint.Publishing.Internal.Administration.MigrationBatchCommand.ExecuteWaitingCommands() at Microsoft.SharePoint.Publishing.Internal.Administration.MigrationDBSerializer.SerializeSelectedExportObject(StringCollection objectAttribs) at Microsoft.SharePoint.Publishing.Internal.Administration.MigrationDataAccess.InitializeExportTable(ScopeType scopeType) at Microsoft.SharePoint.Publishing.Internal.Administration.MigrationDataAccess.InitializeTemporaryTables(DateTime lastChangeTime) at Microsoft.SharePoint.Publishing.Internal.Administration.MigrationDataAccess.InitializeDatabase(DateTime lastChangeTime, Boolean isAnalysis, SqlConnection connection) at Microsoft.SharePoint.Publishing.Internal.Admin...
17 MCMS 2002 Migration High ...stration.MigrationDataAccess.InitializeDatabase(DateTime lastChangeTime, Boolean isAnalysis) at Microsoft.SharePoint.Publishing.Administration.ContentMigration.Export(MigrationDataAccess dataAccess) at Microsoft.SharePoint.Publishing.Administration.ContentMigration.MigrateInternal().
18 MCMS 2002 Migration Verbose MigrationProfile: GetInstance. Start.
19 MCMS 2002 Migration Verbose MigrationProfile: GetInstance. End.
20 MCMS 2002 Migration Verbose Migration profile status is changed to Failed
SQL 命令解析失败的堆栈跟踪出现在第 15-17 行。下面附有堆栈跟踪的更清晰版本。
完整堆栈跟踪：
迁移引发异常：第 6 行：';' 附近的语法不正确。
在 System.Data.SqlClient.SqlConnection.OnError （SqlException 异常，
布尔值断开连接）
在 System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning（
TdsParserStateObject 状态对象)
在 System.Data.SqlClient.TdsParser.Run（RunBehavior runBehavior，
SqlCommand cmdHandler、SqlDataReader dataStream、BulkCopySimpleResultSet
bulkCopyHandler，TdsParserStateObject stateObj）
在 System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds （字符串方法名称，
布尔异步）
在 System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery（DbAsyncResult 结果，
字符串方法名称，布尔值sendToPipe）
在 System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
在 Microsoft.SharePoint.Publishing.Internal.Administration.MigrationBatchCommand
.ExecuteImmediate（字符串命令）
在 Microsoft.SharePoint.Publishing.Internal.Administration.MigrationBatchCommand
.执行等待命令()
在 Microsoft.SharePoint.Publishing.Internal.Administration.MigrationDBSerializer
.SerializeSelectedExportObject（StringCollection objectAttribs）
在 Microsoft.SharePoint.Publishing.Internal.Administration.MigrationDataAccess
.InitializeExportTable（范围类型范围类型）
在 Microsoft.SharePoint.Publishing.Internal.Administration.MigrationDataAccess
.初始化临时表（日期时间上次更改时间）
在 Microsoft.SharePoint.Publishing.Internal.Administration.MigrationDataAccess
.InitializeDatabase（DateTime lastChangeTime，布尔值isAnalysis，
SqlConnection 连接）
在 Microsoft.SharePoint.Publishing.Internal.Administration.MigrationDataAccess
.InitializeDatabase（日期时间上次更改时间，布尔值isAnalysis）
在 Microsoft.SharePoint.Publishing.Administration.ContentMigration.Export
（迁移数据访问数据访问）
在 Microsoft.SharePoint.Publishing.Administration.ContentMigration
.MigrateInternal()。
这些日志信息均未表明解析器检查失败的 SQL 命令。我已检查了托管源数据库和目标数据库的 SQL 服务器以查找查询的踪迹，但似乎都没有触发解析失败情况。这似乎发生在 SharePoint 服务器上。
我还应该调查其他什么位置来告诉我哪里可以找到错误的根源？
答案1
ULS 日志将包含您正在寻找的数据。将您的 SharePoint 日志设置为详细，然后开始挖掘。