cancel
Showing results for 
Search instead for 
Did you mean: 

.Net Runtime server did not respond

Former Member
0 Kudos

Hi all,

I am trying to configure the .NET Settings on the portal.

This is the error.

<b>.Net Runtime server: 172.17.51.77:50100 did not respond. Make sure the server is running and configured correctly.</b>

Now the steps i have performed are as follows: -

1. Installed Visual Studio 2005 (on my machine)

2. Upgraded Portal Server to 2004s SP 9

3. Installed PDK for .NET (Two files and Two SDAs)

4. Now, after having done the prior setting as per the document when i try connecting to the .NEt Server I am unable to connect.

And I get the above error. (I have tried using the following ports: - <b>172.17.x.x:50100</b> and <b>172.17.x.x:8050</b>) both did not work.

Please help me with this.

Regards,

Preksha

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Preksha,

This is a generic error message from the .NET Runtime.

Please post the error message from the Portal server in addition for a little clearer understanding of the problem.

if you are not sure where the file is, please let me know

with respect,

amit

Former Member
0 Kudos

Can you pls tell me whr I can find the detailed error message?

Former Member
0 Kudos

Hi Preksha,

how are you doing ?

i'm in the middle of a few things, so will apologise for the delay in replying, i would have liked to reply much sooner, but i was held up.

so, getting on with the problem at hand :

please look in the folder which is equivalent to :

C:\usr\sap\EP2\JC04\j2ee\cluster\server0\log

there you will find a few applications.1.log

or applications.2.log, etc ...

so run the .NET PDK functionality to recreate the error then sort the folder by last modified date, and open the latest application.X.log file

find the appropriate lines which talk about the error (will be towards the end of the file, if done quickly)

then please post them here for me to analyse

also have a look at the equivalent of C:\usr\sap\EP2\JC04\work\dev_server0

;

you can also add a tail to the file to monitor the logs at as close to run time as possible

with respect,

amit