Problem with SAP.Connector.dll/SAPftp

[bernd_kresse]

We developed a small .net application (VB), which download a document via SAP-RFC_CALL.

Inside this RFC we use standard BAPI's for check out, eg BAPI_DOCUMENT_CHECKOUTVIEW2

and all works fine for nearly 2 Years.

Suddenly nothing works anymore and we are getting a strange error from the BAPI (?!):

"I:001 Only available with the RFC library from 4.0C onwa" ... and the rest of the error message is missing.

I thought about some Windows changes (as usual ). Annybody else out there with such problems?

[Andre_Fischer · Accepted solution]

Hi Bernd,

[SAP Note 885058|https://service.sap.com/sap/support/notes/885058] - EasyDM: Unicode versions are required describes a similar error message.

Best regards,

Andre

[bernd_kresse · Accepted solution]

Thanks Andre,

good hint. It was problem with our change to unicode.

After using the new unicode dlls and programs an a complete rebuild it works as before.

Greetings Bernd

[Andre_Fischer · Accepted solution]

Hi Bernd,

since I solved the problem I deserve 10 points, don't I ?

Best regards,

Andre

[bernd_kresse · Accepted solution]

np

[Former Member · Accepted solution]

Hello!

I'm facing exactly the same problem.

I have

- SAP .NET Connector with Visual Studio 2003 installed.

- The latest SAP Gui installed

- Recreated the whole proxy project in Visual Studio

- Copied the latest sapftp.exe to my app's bin directory

But still the same problem.

What did you do in detail?

Kind regards

Holger

[bernd_kresse · Accepted solution]

Hi Holger,

i also use the newest rfclib32.dll, especially the unicode version.

After haveing all the newest files i defined all the connections to functions/bapis new an recreate the proxy.

After a rebuild it work on my station.

At least i think it was somthing regarding our change to unicode in the sap-system.

Greetings Bernd

[Former Member · Accepted solution]

Hi Bernd,

what exactly do you mean by "i also use the newest rfclib32.dll, especially the unicode version"??

Did you exchange the SAP Gui's librfc32.dll with the one from the SAP note and reregister it?

What did you do with librfcu*.dll?

What about those icu*.dll?

Did you do anything different with sapftp.exe than copy it to the bin directory?

After installing the latest SAP Gui, I've created a completely new solution and created a new proxy for bapi_document_checkoutview2. But it doesn't work. Any hint, where to look except rfc tracing?

Kind regards

Holger

[bernd_kresse · Accepted solution]

Hi Holger,

answers:

Did you exchange the SAP Gui's librfc32.dll with the one from the SAP note and reregister it?

=> Yes

What did you do with librfcu*.dll?

=> i moved it in´the system32 folder

What about those icu*.dll?

=> I don't know. Seems to me, that this dll's belongs to different programs (Acrobat, Opentext Viewer etc.)

Did you do anything different with sapftp.exe than copy it to the bin directory?

=> No

Any hint, where to look except rfc tracing?

=> No, sorry ... i didn't install a new GUI, and afer a complete rebuild and a restart suddenly it works.

I use several tools, e.g. depends.exe to find out, which dlls call each other ...

Best Regards, Bernd

[Former Member]

I have the same problem, but when i wath the return0 messages after call ,

appears message_v1 with "Message = "I::001 RFC"

and the file is not in the originalpath

This is the VB.NET code:

-

---

ddDocumentnumber = "0000000010000000000000004"

ddDocumentpart = "000"

ddDocumentversion = "00"

ddDocumenttype = "ZMA"

ddOriginalpath = "C:\"

proxy.BapiDocument_Checkoutview2(ddDocbomchangenumber, _

ddDocbomrevisionlevel, _

ddDocbomvalidfrom, _

ddDocumentfile, _

ddDocumentnumber, _

ddDocumentpart, _

ddDocumenttype, _

ddDocumentversion, _

ddGetcomponents, _

ddGetheader, _

ddGetstructure, _

ddHostname, _

ddOriginalpath, _

ddPf_Ftp_Dest, _

ddPf_Http_Dest, _

ddReturn0, _

ddComponents, _

ddDocumentfiles, _

ddDocumentstructure)

-

---

Can you help me!?

[ganimede_dignan]

We have solved with add this lib on target application:

icuuc30.dll

icudt30.dll

icuin30.dll

Bye.

[Former Member]

What do you mean "add this lib on target application" ?

Regards,

Alex

[ganimede_dignan]

Install Visual Studio 2003

Install Java (a release supported by .Net connector)

Install .Net connector

Install last SAPgui 7.10 with last available patches

Create and build you proxy dll

Create and buil your custom application

Make sure that librfc32.dll, librfc32u.dll, sapftp.exe, saphttp.exe and mentioned lib ara available on host that run you vb application.

Regards.

[Former Member]

Hello,

I have

- installed Visual Studio 2003,

- .Net connector ver 2.0.0.26,

- SAPgui 7.10 with last available patches,

- created and built my proxy dll and added it into my application C# VS2008

- placed librfc32.dll (ver 7100.3.141.6078), librfc32u.dll (ver 7100.4.181.6370), icuuc30.dll, icuin30.dll, icudt30.dll, sapftp.exe (ver 7100.0.13.28508), saphttp.exe (ver 7100.0.13.28508) in WINXP/system32 folder

but I get an error "I:001 Only available with the RFC library from 4.0C onwa"

Please, help if you know how to solve this issue. Any help appreciated, and thanks in advance for the help, you can post your answer to

Best regards,

Alex

[Former Member]

I have solved my issue with RFC error and described it [here|]. But I get another error:

Could not open the ICU common library.

The following files must be in the path described by

the environment variable "PATH":

icuuc30.dll, icudt30.dll, icuin30.dll

I have placed icuuc30.dll, icuin30.dll, icudt30.dll in system32 folder and system32 folder described by the environment variable "PATH"

Please, help if you know how to solve this issue.

Regards,

Alex