Using ORAMTS on Microsoft Vista Results in The Error ORA-161 (Doc ID 467181.1)

Last updated on JULY 07, 2017

Applies to:

Oracle Services for Microsoft Transaction Server - Version 11.1.0.6 and later
Microsoft Windows (32-bit)

*** Checked for relevance on 07-Jul-2017 ***

Symptoms

When trying to enlisting transaction on Microsoft Vista or Microsoft Windows 2008 using the Oracle Services for Microsoft Transaction Server resulted in the following error:

 

ORA-161: transaction branch length 112 is illegal (maximum allowed 64)


or

Oracle.DataAccess.Client.OracleException was unhandled
Message="Unable to enlist in a distributed transaction"
Source="Oracle Data Provider for .NET"
ErrorCode=-2147467259
DataSource=""
Number=-1050
Procedure=""
StackTrace:
at Oracle.DataAccess.Client.OracleException.HandleErrorHelper(Int32 errCode, OracleConnection conn, IntPtr opsErrCtx, OpoSqlValCtx* pOpoSqlValCtx, Object src, String procedure)
at Oracle.DataAccess.Client.OracleException.HandleError(Int32 errCode, OracleConnection conn, IntPtr opsErrCtx, Object src)
at Oracle.DataAccess.Client.OracleConnection.Open()


This can be reproduced with Oracle Client, ODP.NET, ODBC, Oracle Provider for OLE DB.

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms