Tag Archives: Migration

randypaulo 10:17 am on June 26, 2018
Tags: , , Migration   

BizTalk – SAP Adapter – RFC_INVALID_HANDLE

All receive location green and by the moment you’ve send your first IDoc this warning occurs:

The adapter “WCF-Custom” raised an error message. Details “Microsoft.Adapters.SAP.RFCException: Details: ErrorCode=RFC_INVALID_HANDLE. AdapterErrorMessage=An exception has occurred on the listener while executing RfcWaitForRequest..”.

To solve this error you’ll need to install the BizTalk SAP Adapter Schema.

Steps:

  1. Create a BizTalk application or use the default BizTalk Application
  2. Right Click Add Resource.
  3. Browse to: \bin\Microsoft.Adapters.SAP.BiztalkPropertySchema.dll
  4. In the options check all.

BizTalkSchemas

randypaulo 3:53 pm on May 28, 2018
Tags: Migration, SSIS 2012 to 2016,   

SSIS 2012 to SSIS 2016 Migration – Arithmetic operation resulted in an overflow

We’ve recently upgraded our SSIS 2012 to SSIS 2016, during the package upgrade it goes without issue. In Visual Studio, there’s no problem running it, however when we use the SSIS runtime we’ve encountered the following error:

“Arithmetic operation resulted in an overflow.”. Possible failure reasons: Problems with the query, “ResultSet” property not set correctly, parameters not set correctly, or connection not established correctly.

The Execute method on the task returned error code 0x80131516 (Arithmetic operation resulted in an overflow.). The Execute method must succeed, and indicate the result using an “out” parameter.

To solve this issue,  I’ve recreated the SQL Task and viola no error!.

 

 

randypaulo 4:41 pm on December 8, 2011
Tags: , Migration, Visual Studio 2010   

BizTalk upgrade issue – Missing Assembly.cs file

All BizTalk solutions from 2006R2 was upgraded to 2010 version and was checked-in to TFS couple of months back and today I try to get the latest version and tried to compile it and boom! it throws an error.

It seems that when you use the upgrade wizard and try to check-in (TFS), the Assembly.cs file is being ignored.

To solve this I went to the copy of the solution (or History if not available) and copy every Properties folder (which contains the Assembly.cs) to the new one.

Finally in the Source Control, I selected the top folder then click Add Items to the Folder -> Sort it by Name -> Exclude all that is not Assembly.cs -> Finish.

Lesson of the day:  to always check whether the Assembly.cs is included during the checkin when migrating a BizTalk solution.