E1: UPG: Unicode Conversion with SQL Server 2019 Failing From Second Table Onwards With Error '<Tbl name="FXXX">FAILED: Table 'FXXX' failed to convert. error: HRESULT = 80040e05, SQLState = UNKWN, NativeError = 0, msg = Object was open' (Doc ID 3017404.1)

Last updated on MAY 22, 2024

Applies to:

JD Edwards EnterpriseOne Tools - Version 9.2 and later
Information in this document applies to any platform.

Symptoms

When running the Unicode conversion from B7333 release to 9.2 with Microsoft SQL server 2019 and ODBC 17 the process fails from the second table onwards with below errors in

<Tbl>FAILED: Table 'F01111Z1' failed to convert. error: HRESULT = 80040e05, SQLState = UNKWN, NativeError = 0, msg = Object was open..

The first table is converted successfully

Steps

Run the unicode conversion process as mentioned in E1: UPG: JD Edwards EnterpriseOne Unicode Data Conversion Guide (Doc ID 647336.1)
Check the results

Changes

Unicode conversion on data sources as part of upgrade from B7333 to 9.2

Cause

	To view full details, sign in with your My Oracle Support account.
	Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.

E1: UPG: Unicode Conversion with SQL Server 2019 Failing From Second Table Onwards With Error '<Tbl name="FXXX">FAILED: Table 'FXXX' failed to convert. error: HRESULT = 80040e05, SQLState = UNKWN, NativeError = 0, msg = Object was open' (Doc ID 3017404.1)

Applies to:

Symptoms

Changes

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!