|
Deployments fails after Planning Store tables are upgraded to 8.4 |
 |
 |
 |
|
Written by Martijn Christenhusz
|
|
Thursday, 07 May 2009 08:39 |
From the planningerrorlog.csv for the service account:
Unable to assign 196 character BLOB value to field cm..P_PNREQUEST.request.~~~~Multiple-step operation generated errors. Check each status value.
Multiple-step operation generated errors. Check each status value., Error number -2147217887 was raised by Microsoft Cursor Engine
Cause
The request field in the P_PNREQUEST table did not get updated to the appropriate data type.
Solution
Create a new Planning Store or Content Store if a separate Planning Store was not used.
or Use a a SQL script to correct the table. /**** Cleanup table P_PNREQUESTPROGRESS ****/ TRUNCATE TABLE [dbo].[P_PNREQUESTPROGRESS]; /**** Drop table P_PNREQUEST ****/ DROP TABLE [dbo].[P_PNREQUEST]; /**** Create Table [dbo].[P_PNREQUEST]****/ SET ANSI_NULLS ON GO SET QUOTED_IDENTIFIER ON GO SET ANSI_PADDING ON GO CREATE TABLE [dbo].[P_PNREQUEST]( [requestguid] [char](38) NOT NULL, [requestname] [varchar](500) NOT NULL, [requesttype] [varchar](500) NOT NULL, [runstateid] [varchar](250) NOT NULL, [startdt] [char](29) NULL, [lastcompletiondt] [char](29) NULL, [failurenote] [text] NULL, [executioncommand] [varchar](250) NULL, [request] [image] NULL, CONSTRAINT [pk_0jn85] PRIMARY KEY CLUSTERED ( [requestguid] ASC )WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY] ) ON [PRIMARY] TEXTIMAGE_ON [PRIMARY] GO SET ANSI_PADDING OFF
www.cogknowhow.com
|
|
Last Updated on Saturday, 30 January 2010 11:35 |
Knowledge Articles 
Comments