cancel
Showing results for 
Search instead for 
Did you mean: 

The proxyWizard can't conjur ... and other .net connector mystics

Former Member
0 Kudos

Hello,

I am trying to pursade the proxy wizard to work for me but I am afraid it is unwilling ...

When I follow the documentation the wizard should starting something when I add it to the application using the project explorer but infact it is just added - period. Did I get something wrong ?

Another problem I have is that that I can use the Server-Explorer to receive wonderfull lists (BOR, functions etc.) from a connected R/3 system, but it is impossible to add anything from there to the project itself.

Whenever it is trying to receive the data it is unable to connect to the system. Reading the rfc-trace (in the install directory of the sapconnector) I noticed that at this time VS is trying to connect to the SAP system without using the (nescessary) router string and the result is "server XY unknown".

Close to despair I hope any1 can help me.

Regards,

Karsten

Accepted Solutions (1)

Accepted Solutions (1)

reiner_hille-doering
Active Contributor
0 Kudos

Can it be that you are reading the SAP .NET Connector 1.0 documentation?

You should better have a look int the 2.0 FAQ document that should answer most of your questions.

PS: The 2.0 documentation is contained in Visual Studio integrated help system.

Former Member
0 Kudos

Well, YES ! This definitely solves my 1st problem (sorry, should have read more carefully)

But sadly I am still struggeling with the connection.

I can access the SAP system using the server explorer, get a list of the desired functions etc., but as soon as I want to drag them into the design window it is trying to receive the data and pops up with a message "...connect failed".

As I stated before, the rfc trace shows me, that the ASHOST parameter in the connection string only has the hostname in it, but NOT the (nescessary) router string.

Karsten

reiner_hille-doering
Active Contributor
0 Kudos

Ok, that's something I forgot: While the .NET Connector (that is used inside of the Server Explorer) correctly uses the router string, it's not passed over to the Java program fetching the metadata.

You can workarround by using "Custom Settings" to create the Application Server node in Server Explorer. Into the AppServier property enter the concatination of router string and application server hostname (without any character). Then it should work both in the Server Explorer and later in the Java program.

Former Member
0 Kudos

Yep, it works now, thanks

Karsten

Former Member
0 Kudos

Hi Karsten,

You marked the question as answered, so please assign contributor points too. I did this time, but you can change them.

See: <u>/people/mark.finnern/blog/2004/08/10/spread-the-love for directions.

Click on the yellow Star icon per reply. You can give:

1 - 10 pts (Which marks the question as answered)

2 - 6 pts (Very helpful)

Lots of 2 pts (Helpful)

It's just a little thank you for the responses.

Thanks!

Joan (and Mark Finnern)

Answers (0)