JCO.Server could not find server function 'SET_SLD_DATA'

[Former Member]

Hi

When RZ70, I hit "JCO.Server could not find server function 'SET_SLD_DATA", SLD server log also register some message as below, kindly advise what has been missing.

Thank you

//psl

#44 04/09/2005 20:43:49.412 [JCO.ServerThread-25] ERROR com.sap.lcr.sagent.SAPProxyServer: JCO Server exception raised: JCO.Server could not find server function 'SET_SLD_DATA'

Thrown:

com.sap.mw.jco.JCO$Exception: (123) JCO_ERROR_FUNCTION_NOT_FOUND: JCO.Server could not find server function 'SET_SLD_DATA'

[Former Member]

Hi,

Just resolved the same issue in our landscape.

STEPS TO ANALYZE:

1) Check SLDDSUSER is locked or not

2) Check J2ee_admin is locked or not

3) Check txn SLDAPICUST for correct password set for SLDDSUSER

4) Delete RFCs SLD_UC and SLD_NUC at abap level

5) Run RZ70 now and give it a try

If nothing works, check with bi portal initial setting checks.

Thanks & Regards,

Naveen

[Former Member]

I had this same error. It turned out to be a security issue. In Visual Admin, the userid for the Jco RFC Provider/SLD_UC (we are unicode) service was set to a basis administrator's id. After changing it to j2ee_admin, the problem went away.

[Former Member]

I Have a Configuration that I have followed to advoid

this problem.

I don not know it is useful for you or not, but a least it will be useful for the new one.

1. Set up Sld

Come to http://server:50000/sld

Enter server object name : name of Web AS JAVA.

Enter SLD Path : drive:\... default

Select ABAP radio button

Config your R/3 Server [easy]

2. Set up bridge

set update sld from flase to true

Enter RFC gateway : enter your r/3 server and sapgw00

as service.

3. Come to J2ee Administrator, cluster JCO RFC Provider.

Register new ProgramID, remember do not user program

ID name as SLD_NUC or SLD_UC it can cause to later bug.

Enter your gateway server and service as in r/3 system

(to know about <b>gateway server</b> and <b>service</b> come to SMGW and see report list attribute).

Enter your application server that is all your

information about R/3 server.

4. Come to SAP R/3, transaction sm59, find SLD_NUC RFC

destination, you change gatway host and service same

as what you have entered in step 3.

In program enter your program ID name.

5. Come to transaction SLDAPICUST, switch to editing mode

and chose insert row, Specify the connection parameter

of your WAS JAVA host, and remember active the primary

checkbox. Uncheck any other primary check box.

6. Come to transaction RZ70, enter your gateway server

and service as you see in report in transaction SMGW.

7. Now your can run, schedule batch job.

Hope this help.

Nguyen Lam.

[Former Member]

I am having the same problem. Tried all kind of error analysis mentioned in this thread.

Does anyone know the solution.

Thanks

Shravan

[Former Member]

I Have a Configuration that I have followed to advoided this problem.

I don not know it is useful for you or not, but a least it will be useful for the new one.

1. Set up Sld

Come to http://server:50000/sld

Enter server object name : name of Web AS JAVA.

Enter SLD Path : drive:\... default

Select ABAP radio button

Config your R/3 Server [easy]

2. Set up bridge

set update sld from flase to true

Enter RFC gateway : enter your r/3 server and sapgw00

as service.

3. Come to J2ee Administrator, cluster JCO RFC Provider.

Register new ProgramID, remember do not user program

ID name as SLD_NUC or SLD_UC it can cause to later bug.

Enter your gateway server and service as in r/3 system

(to know about <b>gateway server</b> and <b>service</b> come to SMGW and see report list attribute).

Enter your application server that is all your

information about R/3 server.

4. Come to SAP R/3, transaction sm59, find SLD_NUC RFC

destination, you change gatway host and service same

as what you have entered in step 3.

In program enter your program ID name.

5. Come to transaction SLDAPICUST, switch to editing mode

and chose insert row, Specify the connection parameter

of your WAS JAVA host, and remember active the primary

checkbox. Uncheck any other primary check box.

6. Come to transaction RZ70, enter your gateway server

and service as you see in report in transaction SMGW.

7. Now your can run, schedule batch job.

Hope this help.

Nguyen Lam.

[Former Member]

I Have a Configuration that I have followed to advoided this problem.

I don not know it is useful for you or not, but a least it will be useful for the new one.

1. Set up Sld

Come to http://server:50000/sld

Enter server object name : name of Web AS JAVA.

Enter SLD Path : drive:\... default

Select ABAP radio button

Config your R/3 Server [easy]

2. Set up bridge

set update sld from flase to true

Enter RFC gateway : enter your r/3 server and sapgw00

as service.

3. Come to J2ee Administrator, cluster JCO RFC Provider.

Register new ProgramID, remember do not user program

ID name as SLD_NUC or SLD_UC it can cause to later bug.

Enter your gateway server and service as in r/3 system

(to know about <b>gateway server</b> and <b>service</b> come to SMGW and see report list attribute).

Enter your application server that is all your

information about R/3 server.

4. Come to SAP R/3, transaction sm59, find SLD_NUC RFC

destination, you change gatway host and service same

as what you have entered in step 3.

In program enter your program ID name.

5. Come to transaction SLDAPICUST, switch to editing mode

and chose insert row, Specify the connection parameter

of your WAS JAVA host, and remember active the primary

checkbox. Uncheck any other primary check box.

6. Come to transaction RZ70, enter your gateway server

and service as you see in report in transaction SMGW.

7. Now your can run, schedule batch job.

Hope this help.

Nguyen Lam.

[former_member91687]

Hi,

Take a look at the following threads, they might help you out.

/thread/15414 [original link is broken]

Hope this helps you.

Regards,

Chandra

[Former Member]

The scenario is like this.

1. Central SLD installed on WebAS - J2EE(no abap stack).

2. We are trying to connect an XI BOX to this central SLD.

Steps did in XI BOX:

1. SLDAPICUST - points to SLD host.

2. Exchange Profile - values set for Connections like cr.name and landscape.name.

3. SLD Data supplier - in visadm - points to Central SLD - due to this, The Java stack of XIBOX is listed as a technical system in central SLD and data collection works correctly.

3. JcoRfc Destination - LCRSAPRFC_XIBOX - program id registerd in visadm with gateway host and service as XIBOX gateway service itself.

Steps did in Central SLD:

1. Jco Rfc Destination - SAPSLDAPI_XIBOX - program id registered in visadm with gateway host and service as that of the XIBOX.

2. SLD Data Supplier - points to sld itself and when data collection is done - sld itself is added as a technical system in SLD.

Problems:

1. In XIBOX - in transaction RZ70 - SLD bridge is given as Central SLD hostname and service. When data collection is done, I am getting Error in RFC connection

in SLD_UC.

Questions:

1. Do I have to give RFC Destinations in Visadm for SLD_NUC and SLD_UC in central SLD???

2. I am planning to install a gateway service in central SLD because I dont have a gateway service for ABAP components - is it right??

3. When I open SLD in the browser in XI box - sld works. But if I open in my local system - SLD link opens a page cannot be displayed error page - what steps should be done? I have host file correct already in my system.

Please suggest..also sldcheck is workinig fine..

[Former Member]

Ok problem solved ....data supplier works...but only when i open sld from my desktop - it doesnt work..

[STALANKI]

can u check sldcheck transaction?

[Former Member]

I have SLD_NUC, SLD_UC working good..I am getting this exception,

ERROR com.sap.lcr.sagent.SAPProxyServer: JCO Server exception raised: Server repository could not create function template for 'SET_SLD_DATA' caused by: com.sap.mw.jco.JCO$Exception: (106) JCO_ERROR_RESOURCE: Invalid connection encountered

Thrown:

com.sap.mw.jco.JCO$Exception: (123) JCO_ERROR_FUNCTION_NOT_FOUND: Server repository could not create function template for 'SET_SLD_DATA' caused by: com.sap.mw.jco.JCO$Exception: (106) JCO_ERROR_RESOURCE: Invalid connection encountered

at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java:2019)

at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java:1516)

at com.sap.mw.jco.JCO$Server.listen(JCO.java:6926)

at com.sap.mw.jco.JCO$Server.run(JCO.java:6855)

at java.lang.Thread.run(Thread.java:534)

As you could see -

"Invalid Connection Enounterd" is the problem - DID someone find a solution for this??

[Former Member]

Hi,

Did you check the SAP NOTE :731436 and see the thread

(See the reply from arpit)

Hope this helps,

Regards,

Anirban.

[Former Member]

I am having the same issue. I think it might be authorization related?

[former_member86837]

Had the same problem and this is what solved it:

a) in the J2EE Visual Administrator navigate to

Services -> Jco RFC Provider

check that there is a definition for SLD_NUC and that the unicode checkbox for this is NOT enabled.

[Former Member]

I am getting the same problem and whatever solutions quoted above doesnt work for me..Is there anything else to be checked?

[Former Member]

I had the same problem. The way I fixed it was to make sure the SLD_UC and SLD_NUC are NOT defined anywhere in the VA. These two processes are created implicitly and should not be defined. Remove them from anywhere they appear in the VA, and recycle the gateway. You should then see that each program is registered twice in the SLD gateway and RZ70 should work.

Regards,

Casey

[Former Member]

thanks to casey,

that was the right answer, see note 1057720.

regards,

christoph

[Former Member]

Apart from the note, you can also update the SLD CR content by referring to the following notes

Note: 669669

Note: 907897

After import the content, configure your systems based on the above note

Note: 1057720 and restart the SLD.

Thanks,

Ikram Shah

[Former Member]

Hi

Can anybody please help...

Thank you very much

//psl

[vittal_agirishetti]

PSL,

When you configure RZ70, an RFC connection SLD_NUC will be created. Check this RFC connection. It should work to get rid of this error. Configure same Program ID in JCo connection in J2EE visual administrator.

It will work.

[Former Member]

Hello,

We are having the same problem.

We checked SM59 for the RFC connection and it works fine.

Still, it doesn't seem to work.

Also - the j2ee visual admin - shows a well configured RFC dest. under JCO RFC provider - is that where we should look ?

Thanks a bunch,

Yoad.