How Do I Resolve the Issue of Exporting on a v5.1 Service Release Site?

How Can We Help?

< Back

Issue

1) Create a new 5.1.1 website.

2) Connected to an old database.

3) Upgraded old database.

4) Verified the version history is v5.1.1

When I export from the XMDesigner, it indefinitely hangs at the “Exporting” stage.

v5.1.1_DatastructureFile

Resolution

The problem occurs as the fcCustomError table is not present within the site.

The Integration File used by the exporter is expecting the table to export.

To resolve, execute the following SQL on the database in question, this applies to both new installs and upgrades:

CREATE TABLE [dbo].[fcCustomError](

[ID] [bigint] IDENTITY(1,1) NOT

NULL,

[ErrorCode] [nvarchar](30) NULL,

[Description]

[nvarchar](1024) NULL,

CONSTRAINT [PK_fcCustomError] PRIMARY KEY

CLUSTERED

(

[ID] ASC

)WITH (PAD_INDEX  = OFF,

STATISTICS_NORECOMPUTE  = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS

= ON, ALLOW_PAGE_LOCKS  = ON) ON [PRIMARY]

) ON [PRIMARY]

GO

Resolution 2

Download the following Database Export File that can be used versus the build-in file.

This negates the need to add the fcCustomError table back to the database.

Database Export FIle

Please rename this text file to .xml.

Comments are closed.

This is the legacy version of the XMPro Documentation site. For the latest XMPro documentation, please visit documentation.xmpro.com

X