SAP DCOM Connector message wrong codepage

Hi!
I need help.
I've got RFC module that executing report through submit.
Report is generating error messages. When I'm trying to call RFC module through SAP DCOM Connector, I'm always get message text with wrong codepage. Than I'm saying wrong code page, I mean sap server iternal code page, not a windows code page. Any other data transfer works fine with correct windows code page.
SAP code page is 1500.
Windows code page is 1504.
Do you have any solutions?

I'm using SAP DCOM Connector Version 6.20(english). I don't know where I can get russian version of this product. It seems there is no such one. I don't really know who wrong or right, maybe SAP or DCOM software, because in trace log of DCOM connector I've got something like this:
>>>> RFC MESSAGE/ERROR : 104
RFC_ERROR_SYSTEM_FAILURE
³àãßßþÒþÙ ßþØáÚ ÝÕ àÐ×àÕèÕÝ.
>>>> rfccoctx:985 closing RFC connection (context 016B6708)
>>>> FREE abrfcio.c 3253 (26582468)
-{4A8EB0A1-4D42-44C0-8F2D-1B359DAE74CC}
Trace file opened at 20050727 132222 Russian Dayligh, SAP-REL 620,0,480 RFC-VER 3 525755 MT-SL
>>>> rfccopar:100 End Function ( Parameter FILESIZE: Type 8 Length 4 Variant 16387 Req. Vartype 16387 ).
>>>> rfccopar:100 End Function ( Parameter HTML: Type 5 Length 255 Variant 16393 Req. Vartype 9 ).
>>>> rfccopar:100 End Function ( Parameter PAR: Type 5 Length 286 Variant 9 Req. Vartype 9 ).
>>>> rfccopar:100 End Function ( Parameter PDF: Type 5 Length 134 Variant 16393 Req. Vartype 9 ).
>>>> rfccopar:100 End Function ( Parameter RETURN: Type 5 Length 548 Variant 16393 Req. Vartype 9 ).
>>>> rfccoctx:1077 SetAbort (context 016B6708)
sapmtx.h:1273 Error code 0x80004004 ().
>>>> rfccoctx:720 return to dispenser (context 016B6708)
>>>> rfccosrc:184 Dispenser: returning resource 016B6718 ...
>>>> rfccosrc:195 Dispenser: resource 016B670C broken ...
>>>> rfccoctx:1029 releasing resource (context 016B6708)
Text of error message we have here in wrong code page(SAP internal-1500), then other text from SAP in correct code page(1504). How to force DCOM software to use correct code page for FREE messages?

Similar Messages

SAP DCOM Connector on Windows Server 2008

Does anybody know, if it is possible to use the "old" SAP DCOM Connector on a Windows Server 2008 ?
I want to migrate an old ASP Web Solution with DCOM Connection to SAP from Windows 2003 Server to Windows 2008 Server.
When I try to install the DCOM Connector I get the Error Message:
"Setup could not find ActivX(R) Data Objects verion 2.5 or higher on your computer...."
That is strange, because ADO is there under C:\Program Files\Common Files\System\ado !
Thanks in advance for your help !

This forum is dedicated to all other development-related questions which are not directly addressed by other forums. This includes Business Objects SDKs, products, or technologies which do not fall under BusinessObjects Enterprise, BusinessObjects Edge, Crystal Reports Server, or Crystal Reports (for example Desktop Intelligence SDK, Universe Designer SDK, Portal Integration Kits, Java User Function Libraries, and other third party technologies or development languages).
I think, you'll have better luck getting an answer in one of the SAP product forums.
Ludek

SAP DCOM Connector

Hello All,
Is it possible to use DCOM connector technique to make data available in MS Excel from SAP ECC6.0 without going to SAP GUI? I know it was possible in older versions, but I am not sure about ECC 6.0 as now Duet Add-on is introduced.
Thanks and regards,
Chishre

Hi chishre,
You cans till use DCOM connector to upload data into the Excel with the higher versions. However, it is advisable to go with Duet since it has been integrated with SAP Higher versions and SAP made data download and upload easy for the SAP User through this functionality.
Hope this helps.
Thanks,
Naga

DCOM Connector for SAP SAP 5.x

Does any one know that the DCOM Connector works with SAP 5.x for BAPI calls? Or SAP 5 only works with .Net Connector?
Regards,
Jingmin Wei

I've answered to this question in the thread:
SAP DCOM Connector Download
Check it.

DCOM connector: could not load dll

When I want to add a dll file (created with DCOM connector) to the component services, I get an error 'could not load dll, check to make sure all application runtime files are present etc'.
This only occurs with a dll created on another machine (but with all the same settings; user, rfc's, etc).
Anyone can please help me? This is quite urgent :o(

Hi,
Can I ask where you found the SAP DCOM connector? I cannot seem to find it anywhere on the internet
If you could help me / send the dcom files to me I would be much apprecaited
Thanks
Stu

ASP DCOM CONNECTOR XI

I all,
We've an ASP application wich uses a DCOM Connector to call SAP R/3 RFCs (in a synchronous way, and receiving parameters). We need to use XI instead DCOM Connector for the communication with R/3.
How can we do this? Do we need first to migrate our ASP application to an ASP.NET application and use the .NET CONNECTOR to communicate with XI?
Is it possible to call RFCs in a synchronous way and receive parameters back to the web application using XI?
regards,
Mario Cristóbal

Hi,
Can I ask where you found the SAP DCOM connector? I cannot seem to find it anywhere on the internet
If you could help me / send the dcom files to me I would be much apprecaited
Thanks
stu

Can SAP DCOM be in 2003 Server?

Hi,
Can SAP DCOM connector be installed in 2003 server? Ive done it, but I cant create a new destination. It always display this error: Security is not enabled for ccadmin package. [-2147467260]. I tried it in 2000 advanced server and it works. Does anyone know this issue?
Kind regards,
Jun

Xiaojun,
Have you found the answer for this yet? I am having the same problem.
Thanks!

DCOM Connector.

Hi
I am new to SAP DCOM connector, our company is using DLL created by connector for passing/fetching data to/from Sap.
I need to add an additional field to the return Table structre, do I need to re-complie the whole applixation again using DCOM.
thanks
Lakhbir

hi, GUID is global unique identitfy ID, which will generated when a component created.
It was used to identify each component in windows, you can treat it as a unique name of component.
When you try to create a component in memory, GUID will be used. But we can also create the component by other name, E.G. XXX.XX.1, these kind of name will be mapped to GUID to system at last.
For you problem, I think you'd better use a complete new name for you component, when build it.
and then go to start->setting->control panel Administrative Tools->Component Services
Navigate in this tools, under the Component Service->Computer->My Computer node, your new proxy component will be listed there.
The name will like XXX.XX.N
Then in you VB code, instant the component like following:
SET XXX = oSession.CreateInstance("XXX.XX.N").
And also reference to the following link:
http://help.sap.com/saphelp_nw04/helpdata/en/09/6b3212419311d2952000a0c94260a5/frameset.htm
Hope it will be helpful
thanks

Error: SAP R/3 DCOM connector

Hi.
I kept receiving COM+ error(eventID 4786)for SAP R/3 DCOM connector:
<i>"The system has called a custom component and that component has failed and generated an exception. This indicates a problem with the custom component. Notify the developer of this component that a failure has occurred and provide them with the information below.
Component Prog ID:
Server Application ID: {90C0B162-33A1-4638-BB05-EB38D7065E01}
Server Application Instance ID:
{DB8B9626-51C4-41D5-A200-09373CAD9ABC}
Server Application Name: SAP R/3 DCOM Connector
The serious nature of this error has caused the process to terminate.
Exception: C0000005
Address: 0x000AECEC
Call Stack:
! + 0xAECEC
OLEAUT32!DispCallFunc + 0x6D3
CCADMIN! + 0x32AB
OLEAUT32! + 0x7BF39
OLEAUT32! + 0x7B1BD
RPCRT4!NdrProxyFreeBuffer + 0xB5
RPCRT4!CStdStubBuffer_Invoke + 0x82
OLEAUT32!VarMonthName + 0xCF89
ole32!StgGetIFillLockBytesOnFile + 0x10439
ole32!StgGetIFillLockBytesOnFile + 0x103E3
ole32!CoReleaseMarshalData + 0x7DC
ole32!CoReleaseMarshalData + 0x701
ole32!StgGetIFillLockBytesOnFile + 0x10319
ole32!StgGetIFillLockBytesOnFile + 0x101C4
ole32!StgGetIFillLockBytesOnFile + 0xFF1D
RPCRT4!NdrGetTypeFlags + 0x1C9
RPCRT4!NdrGetTypeFlags + 0x12E
RPCRT4!NdrGetTypeFlags + 0x5A
RPCRT4!CreateStubFromTypeInfo + 0x2E2
RPCRT4!CreateStubFromTypeInfo + 0x323
RPCRT4!NdrConformantArrayFree + 0x28B
RPCRT4!I_RpcBCacheFree + 0x14C
RPCRT4!I_RpcBCacheFree + 0x5EA
RPCRT4!I_RpcBCacheFree + 0x403
RPCRT4!I_RpcBCacheFree + 0x5D2
kernel32!GetModuleFileNameA + 0x1B4
"</i>
and Application Error(EventID1000):
<i>"Faulting application dllhost.exe, version 5.1.2600.2180, faulting module unknown, version 0.0.0.0, fault address 0x000aecec."</i>
Besides, i had ErrorID "CALL_FUNCTION_REMOTE_ERROR" (ST22) when calling RFC.
Does anyone know what's wrong?

Hi,
Is this what you are looking for?
http://help.sap.com/saphelp_46c/helpdata/de/ae/409e36cf0ecb7de10000009b38f889/frameset.htm
Regards
Vijaya

Finding message in SAP Business Connector with IDoc number

Hi Experts,
Since there is no separate forum for Business Connector, posing my question here.
Does anyone have idea how we can find a message in SAP Business Connector if we know the source IDoc number, the same way we use IDX5 in PI.
Thanks,
Dhawal

AFAIK there is no simple way. What I usually do is compare timestamps. The Idoc is usually processed on the B.C. within the same minute.
We only have up to 10 Idocs within one minute and I do not have to search every day. So it works for me.

Message: 'user' missing BI SAP Query Connector Test

Dear all,
The BI SAP Connector test to SAP R/3 system D01 results in :
Portal version is EP7 SP15. Any help will be greatly appreciated.
Error> occured >Tue Mar 31 13:42:56,777<
RfcException:
message: 'user' missing
Return code: RFC_INVALID_PARAMETER(19)
error group: 101
key: RFC_ERROR_PROGRAM
at com.sap.mw.rfc.api.RfcOptions.checkLogonData
(RfcOptions.java:201)
at com.sap.mw.rfc.api.RfcOptions.checkParameters
(RfcOptions.java:498)
at com.sap.mw.rfc.api.RfcApi.RfcOpen(RfcApi.java:707)
at com.sap.mw.jco.MiddlewareJRfc$Client.connect
(MiddlewareJRfc.java:1018
at com.sap.mw.jco.JCO$Client.connect(JCO.java:3255)
at
com.sap.ip.bi.sdk.dac.connector.sapq.impl.Connection.connectDB(Connec
tion.java:333)
at com.sap.ip.bi.sdk.dac.connector.sapq.impl.Connection.connect
(Connecti
on.java:128)
at
com.sap.ip.bi.sdk.dac.connector.sapq.SapqManagedConnection.<init>(Sap
qManagedConnection.java:117)
at
com.sap.ip.bi.sdk.dac.connector.sapq.SapqManagedConnectionFactory.cre
ateManagedConnection(SapqManagedConnectionFactory.java:117)
Best Regards, Neeta

hi Aamod;
it seems like you already have your BI SAP Query system working properly, if you can use it in the BI Integration Wizard. what's the problem you're seeing in VC?
systems created with the BI SAP Query Connector are relational systems and therefore expose tables and fields in VC. via the BI Connector, these systems are 'lent' BI functionality and you can use these tables in the BI Integration Wizard, as you've seen. you might therefore call these "relational BI systems" (just like systems created with the BI JDBC Connector are).
if you have consulted the System Landscape documentation on configuring properties for a BI SAP Query System (<a href="http://help.sap.com/saphelp_nw04s/helpdata/en/4b/9afe3323d14005a283dee9101c66fc/frameset.htm">here</a>) and you're still having problems connecting with the BI SAP Query Connector, i'd suggest you write up a CSS message.
hope it helps;
-m

Error when building object with DCOM Connector

Hello everybody,
I'm new to SAP programming so please forgive my ignorance...
We are trying to build a com object to call some RFC-functions from a VB 6 application. We use DCOM Connector V6.2, I have MS Visual C++ 6.0 installed, unfortunately I don't know the R/3 version of our client.
Every time I click the button "Build Component DLL", the following message appears: "cannot read value of registry entry software\sap\mts\proxygenerator\additionalincludedirs"
This registry entry exists, so I don't know, whats wrong. I run DCOM Connector on Win XP, IE 6. I also tried on a Windows 2000 system, with the same error message.
I hope you can help me, I searched a long time on the forums and didn't find anything.

Obviously my question did not get to much interest. Luckily I found out the answer myself.
The message from the component builder results from this registry key beeing empty. For some reason the SAP GUI installation routine did not fill it out. I then found that by inserting whatever value into that key, the compilation started and hung with another error (file mkenv.inc not found). After surching for that file I found it was installed in C:\Programme\SAP\FrontEnd\SAPgui\rfcsdk\include
So, bingo, the empty registry value "software\sap\mts\proxygenerator\additionalincludedirs" must be filled "C:\Programme\SAP\FrontEnd\SAPgui\rfcsdk\include" or what corresponds to your installation and it works. At least the component dll was built, I have to test now if it is running correctly...

SAP dcom connecter

Tring to create a new destination in the SAP dcom connecter.......
and getting an error message
CDestination::OnNewDestination Failed!
Operation aborted.
user is a local admin on the box.....Any Ideas????

Hi Ken,
is this dcom Connector part of CRM? If not this is the wrong forum.
Regards
Gregor

BAPI CommitWork error DCOM Connector

I have a VB program using BAPIs with the DCOM Connector. The BAPI object and session object are exported to an MTS
server machine. In the VB program I create a global oSession object and logon to R/3 at the form load event. In one function I instantiate the BAPI Object locally with Set oBO = oSession.CreateInstance("BOprogId"), and run some methods on the object that work fine and Set oBO = nothing at the end of the function.
In a followup function I instantiate the BO again locally with Set oBO = CreateInstance("BOprogid"), then do a change method on instance dependant object after doing oBO.InitKeys. The BAPI return is succesful, so I want to commit the change and issue an oSession.CommitWork. The DCOM connector monitor shows the last function is ABAP4_COMMIT_WORK but it remains in an active state there and the VB program gets a nonzero return: error> -2147023170, automation error The remote procedure call failed. I don't know why this happens.
If I use oBO.CommitWork I get an error also: -2147467259 Object created in Session, so I assume if you instantiate an object with oSession.CreateInstance you have to commit
changes using the Session object.
If I use Set oBO = CreateObject("BOprogId") and commit with oBO.Commit, it works without error. This is not practical since I need to enqueue the SAP object in the first function with oBO.Enqueue method before the user makes changes in the UI. When the user requests the update I invoke the change function, then oBO.Dequeue, then oSession.CommitWork.
Can you tell me why the commit fails, or what I may be doing wrong? Incedentanlly, the SAP object is sucessfully
changed. The change BAPI does not have a commit work, so my program must request it.
Please don't suggest using the dotNet Connector, this is not an option for this project.
Thank you.

Dear Rhonda,
Which OS installed on your machine ? I fronted the same problem with windows 200 and windows server 2003.
On windows 2000 you have to register: msado15.dll and msado15r.dll.
On windows 2003 server you have to install MDAC 2.8 and the register those two files.
If you still have problem feel free to email me.
Good luck,
Shay E

BAPI CommitWork fails DCOM Connector

I have a VB program using BAPIs with the DCOM Connector. The BAPI object and session object are exported to an MTS
server machine. In the VB program I create a global oSession object and logon to R/3 at the form load event. In one function I instantiate the BAPI Object locally with Set oBO = oSession.CreateInstance("BOprogId"), and run some methods on the object that work fine and Set oBO = nothing at the end of the function.
In a followup function I instantiate the BO again locally with Set oBO = CreateInstance("BOprogid"), then do a change method on instance dependant object after doing oBO.InitKeys. The BAPI return is succesful, so I want to commit the change and issue an oSession.CommitWork. The DCOM connector monitor shows the last function is ABAP4_COMMIT_WORK but it remains in an active state there and the VB program gets a nonzero return: error> -2147023170, automation error The remote procedure call failed. I don't know why this happens. If I use oBO.CommitWork I get an error also: -2147467259 Object created in Session, so I assume if you instantiate an object with oSession.CreateInstance you have to commit changes using the Session object.
If I use Set oBO = CreateObject("BOprogId") and commit with oBO.Commit, it works without error. This is not practical since I need to enqueue the SAP object in the first function with oBO.Enqueue method before the user makes changes in the UI. When the user requests the update I invoke the change function, then oBO.Dequeue, then oSession.CommitWork.
Can you tell me why the commit fails, or what I may be doing wrong? Incedentanlly, the SAP object is sucessfully
changed. The change BAPI does not have a commit work, so my program must request it.
Please don't suggest using the dotNet Connector, this is not an option for this project.
Thank you.

Refer to this link
SAP Business One SDK Version 2005 [original link is broken]
Search here for sap software distribution center link
https://websmp203.sap-ag.de/~form/handler?_APP=00200682500000001943&_EVENT=SEARCH&HIDE=&SEARCH_SPAT=X&SEARCH_BPAT=X&SEARCH_CD=X&SEARCH_P=X&SEARCH_PV=X&SEARCH_C=X&SEARCH_CV=X&SEARCH_TA=&SEARCH_V=&HIDE_EXPERT_SEARCH=X&SEARCH_MAX_RESULT=20
Regds
Manohar

SAP DCOM Connector message wrong codepage

Similar Messages

Maybe you are looking for