Error exporting SAP functions in .NET designer.

[Former Member]

Hi,

I am using SAP.NET connector from last one year in my project. The SAP server to which I connect to is located in a different country altogether. This SAP server was using ORACLE as its native database. However, before few days, this has been moved to SQL Server 2000 and all the functions and BAPIs are transferred to this new server.

After this migration took place, I tested the RFC functions from SAP and they are working fine. Even the functions which I am using in my .NET application through SAP .NET connector seem to be working without any problems. But when I try to export (drag and drop or for that matter use "add to designer" option) any of the RFC functions on the proxy designer (SAPProxy1.sapwsdl), it doesnt allow me to do so. Infact it doesnt even expand the tree in server explorer for me to see the structures used by those functions.

After dragging and dropping any of the SAP functions, it takes a lot of time, at the end of which my system generates the following error and closes the Visual studio .NET IDE.

-

---

Microsoft Visual C++ Runtime Library

-

---

Runtime Error!

Program: ...Microsoft Visual Studio .NET 2003\Common7\IDE\devenv.exe

This application has requested the Runtime to terminate it in an unusual way.

Please contact the application's support team for more information.

-

---

OK

-

---

Along with this, it creates a trace named "dev_rfc.trc" which is as follows:

M [Thr 3876] -

---

C-STACK -

---

SAP (R) - R/3(TM) Callstack, Version 1.0

Copyright (C) SAP AG. All rights reserved.

-

---

Callstack without Exception:

App : devenv.exe (pid=2132)

When : 7/13/2006 11:48:51.947

Threads : 1

-

---

Computer Name : NIDHI

User Name : Nidhi

-

---

Number of Processors: 1

Processor Type: x86 Family 15 Model 3 Stepping 3

Windows Version : 5.1 Current Build: 2600

-

---

State Dump for Thread Id f24

eax=00000000 ebx=04767034 ecx=000007b7 edx=00056524 esi=04767034 edi=04767008

eip=7c90eb94 esp=10ece828 ebp=10ece838 iopl=0 nv up ei pl nz ac po nc

cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000216

function : KiFastSystemCallRet

7c90eb94 c3 ret

7c90eb95 8da42400000000 lea esp,[esp] ss:10ece828=00000001

7c90eb9c 8d642400 lea esp,[esp] ss:21d9c5bb=????????

7c90eba0 90 nop

7c90eba1 90 nop

7c90eba2 90 nop

7c90eba3 90 nop

7c90eba4 90 nop

--> Stack Back Trace <--

FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name

10ece838 00000000 1049ae50 1049ae4c 00000001 104600b4 ntdll!KiFastSystemCallRet

-

---

M [Thr 3876] -

---

I even refered to RSNAPDOK report of ABAP, but didnt understand anything in that.

Do you have any idea, why is it working like this?..where the problem lies, in SAP or .NET???

Awaiting your reply.

[reiner_hille-doering · Accepted solution]

Has the system also migrated to Unicode? I have seen this crash with older .NET Connector version (2.0.0) and Unicode backends.

[Former Member · Accepted solution]

I will have to check that. Should it migrate to unicode or it should not? I am using SAP .NET connector version 2.0. Awaiting your reply.

[reiner_hille-doering · Accepted solution]

No, simply upgrade your connector to 2.0.1. This should fix the issue.

[Former Member · Accepted solution]

Thanx for your reply. But then can you tell me how come it was working before that migration took place?

Awaiting your reply.

[reiner_hille-doering · Accepted solution]

SAP Server can either run Non-Unicode or Unicode.

In the past most system have been running non-Unicode. Also non-Unicode systems support a large number of different languages, but usually they are limited in the way how the languages can be mixed.

A DB-Migration is a good possibility to switch to Unicode. I assume this has been done in your case.

The problem with NCo is that for Unicode backends all proxies need to have the length and offset attributes for Unicode additionally to non-Unicode. In some of the proxies we are using internally in the Connector, the Unicode attributes have been missing - which was fixed with 2.0.1.

For your proxies it may mean that you have to update proxies metadata (some older non-unicode systems could not deliver the length and offset attributes for BAPIs).

[Former Member · Accepted solution]

Thanks. I used SAP .NET connector 2.0.1 and issue got resolved!!!!!