.Net Server is not running, at a loss

[Former Member]

When trying to run my .Net PDK Iview from the portal I am getting "Problems occured while trying to connect to .NET server..NET server is not running."

We are using the SAP IISProxy from an IIS server to pick up NTLM authentication, passing it then to EP6 running on a Unix (sapepb) server. The SAP .Net framework is running on an NT box (nt4m). Both the nt box and the unix box are in the same dcdomain net domain. I have verified the SAP .Net Runtime Engine 1.0 Server 01 service is running. We have not changed any default ports for this functionality. Since these are two different machines, I do not use localhost to refer to the SAP machine in it's own configurations. I use sapepb dcdomain net 8051 and nt4m dcdomain net 8050 .

I have struggled with this for some time. If anyone has any ideas for where I can look to solve this, it would be much appreciated.

[Former Member · Accepted solution]

We have changed the Portal setting to ALL for logging. However, we are not finding any log information after running the iview several more times. I am working with an SAP consultant on site with this, but we cannot find where dotnet logs on the portal. Any advice on this?

[Former Member · Accepted solution]

You should look at the portal trace -

"..\j2ee\cluster\server0\log\*.trc"

[Former Member · Accepted solution]

I have found this in the logs....trying to make sense of it.

>>#1.5#0003BA9A554B008C0000000800001E600003F03CA2C71209#1108568149791#com.sap.portal.dotnet#sap.com/irj#com.sap.portal.dotnet#JWGAUS2#16337####6f470090803011d9b4a00003ba9a554b#Thread[PRT-Async 3,5,PRT-Async]##0#0#Fatal#1#/System/Server#Java###.NET server is not running.##

#1.5#0003BA9A554B003C0000004B00001E600003F03CA2CA4BE1#1108568150002#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#BP000920#16307####6f681d20803011d9cf2e0003ba9a554b#SAPEngine_Application_Thread[impl:3]_27##0#0#Info##Plain###UserAgentHook: component com.sap.portal.appdesigner.contentcatalog.Tree supports (MSIE, >=5.5, *) (Netscape, *, ) (Mozilla,,*)and doesn't support #

#1.5#0003BA9A554B00580000004300001E600003F03CA2D9F07F#1108568151027#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#JWGAUS2#16337####3a9a4e907f5111d995710003ba9a554b#SAPEngine_Application_Thread[impl:3]_22##0#0#Info##Plain###UserAgentHook: component com.sap.portal.ui.uiservice.treepreload supports (*, *, *) #

#1.5#0003BA9A554B00490000002B00001E600003F03CA2DAF5D0#1108568151094#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#JWGAUS2#16337####700ebd60803011d989550003ba9a554b#SAPEngine_Application_Thread[impl:3]_38##0#0#Info##Plain###UserAgentHook: component com.sap.portal.pagebuilder.emptyDocument supports (*, *, *) #

#1.5#0003BA9A554B00640000004600001E600003F03CA2E23DE1#1108568151571#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#BP000920#16307####70578630803011d9cbb50003ba9a554b#SAPEngine_Application_Thread[impl:3]_35##0#0#Info##Plain###UserAgentHook: component com.sap.portal.appdesigner.contentcatalog.Tree supports (MSIE, >=5.5, *) (Netscape, *, ) (Mozilla,,*)and doesn't support #

#1.5#0003BA9A554B00400000002F00001E600003F03CA3610254#1108568159879#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#JWGAUS2#16337####5afac630803011d98f910003ba9a554b#SAPEngine_Application_Thread[impl:3]_37##0#0#Info##Plain###UserAgentHook: component com.sap.portal.pagebuilder.pageBuilder supports (MSIE, >=5.5, *) (Netscape, *, ) (Mozilla,,*)and doesn't support #

#1.5#0003BA9A554B00400000003000001E600003F03CA3610B70#1108568159882#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#JWGAUS2#16337####5afac630803011d98f910003ba9a554b#SAPEngine_Application_Thread[impl:3]_37##0#0#Info##Plain###UserAgentHook: component com.sap.portal.navigation.detailedtree.DetailedNavigationTree supports (MSIE, >=5.5, *) (Netscape, *, ) (Mozilla,,*)and doesn't support #

#1.5#0003BA9A554B00400000003100001E600003F03CA36146FB#1108568159897#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#JWGAUS2#16337####5afac630803011d98f910003ba9a554b#SAPEngine_Application_Thread[impl:3]_37##0#0#Info##Plain###UserAgentHook: component com.sap.portal.navigation.dynnavarea.DynamicNavigationArea supports (MSIE, >=5.5, *) (Netscape, *, ) (Mozilla,,*)and doesn't support #

#1.5#0003BA9A554B00400000003200001E600003F03CA3615D74#1108568159903#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#JWGAUS2#16337####5afac630803011d98f910003ba9a554b#SAPEngine_Application_Thread[impl:3]_37##0#0#Info##Plain###UserAgentHook: component com.sap.portal.navigation.targets.default supports (MSIE, >=5.5, *) (Netscape, *, ) (Mozilla,,*)and doesn't support #

#1.5#0003BA9A554B00400000003300001E600003F03CA361740D#1108568159908#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#JWGAUS2#16337####5afac630803011d98f910003ba9a554b#SAPEngine_Application_Thread[impl:3]_37##0#0#Info##Plain###UserAgentHook: component com.sap.portal.navigation.targets.default supports (MSIE, >=5.5, *) (Netscape, *, ) (Mozilla,,*)and doesn't support #

#1.5#0003BA9A554B00400000003400001E600003F03CA3618CAB#1108568159915#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#JWGAUS2#16337####5afac630803011d98f910003ba9a554b#SAPEngine_Application_Thread[impl:3]_37##0#0#Info##Plain###UserAgentHook: component com.sap.portal.navigation.contentarea.default supports (MSIE, >=5.5, *) (Netscape, *, ) (Mozilla,,*)and doesn't support #

#1.5#0003BA9A554B00400000003500001E600003F03CA36193A0#1108568159916#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#JWGAUS2#16337####5afac630803011d98f910003ba9a554b#SAPEngine_Application_Thread[impl:3]_37##0#0#Info##Plain###UserAgentHook: component PDK.PortalComponent1 supports (MSIE, >=5.5, *) (Netscape, *, ) (Mozilla,,*)and doesn't support #

#1.5#0003BA9A554B00400000003600001E600003F03CA3619D4F#1108568159919#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#JWGAUS2#16337####5afac630803011d98f910003ba9a554b#SAPEngine_Application_Thread[impl:3]_37##0#0#Info##Plain###UserAgentHook: component com.sap.km.cm.navigation supports (MSIE, >=5.5, *) (Netscape, *, ) (Mozilla,,*)and doesn't support #

#1.5#0003BA9A554B00400000003700001E600003F03CA361A27F#1108568159920#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#JWGAUS2#16337####5afac630803011d98f910003ba9a554b#SAPEngine_Application_Thread[impl:3]_37##0#0#Info##Plain###UserAgentHook: component com.sap.portal.layouts.framework.WAandNavPanel supports (MSIE, >=5.5, *) (Netscape, *, ) (Mozilla,,*)and doesn't support #

#1.5#0003BA9A554B009A0000000200001E600003F03CA361DF98#1108568159936#com.sap.portal.dotnet#sap.com/irj#com.sap.portal.dotnet.ProcessRequest#JWGAUS2#16337#####Thread[PRT-Async 2,5,PRT-Async]##0#0#Debug##Java###Non-Remote exception##

#1.5#0003BA9A554B009A0000000300001E600003F03CA361E152#1108568159936#com.sap.portal.dotnet#sap.com/irj#com.sap.portal.dotnet.ProcessRequest#JWGAUS2#16337#####Thread[PRT-Async 2,5,PRT-Async]##0#0#Debug##Java###ProcessRequest has failed.##

#1.5#0003BA9A554B009A0000000400001E600003F03CA361E791#1108568159938#com.sap.portal.dotnet#sap.com/irj#com.sap.portal.dotnet#JWGAUS2#16337#####Thread[PRT-Async 2,5,PRT-Async]##0#0#Debug##Java###ProcessRequestException

[EXCEPTION]

#1#java.lang.StringIndexOutOfBoundsException: String index out of range: -1

at java.lang.String.substring(String.java:1438)

at java.lang.String.substring(String.java:1411)

at com.intrinsyc.janet.RemoteException.<init>(Unknown Source)

at com.intrinsyc.janet.control.Janet.init(Unknown Source)

at com.intrinsyc.janet.RemoteProxy.<init>(Unknown Source)

at SAP.Portal.Interoperability.Framework.Server.iViewProcessor.<init>(iViewProcessor.java:44)

at com.sap.portal.dotnet.interoperability.framework.server.DotNETiViewProcessor.processRequest(DotNETiViewProcessor.java:79)

at com.sap.portal.dotnet.framework.iViewProcessorService.ProcessRequest(iViewProcessorService.java:141)

at com.sap.portal.dotnet.framework.iViewProcessorComponent.doContent(iViewProcessorComponent.java:16)

at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)

at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)

at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)

at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)

at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)

at com.sapportals.portal.prt.core.async.AsyncPortalComponentResponse.include(AsyncPortalComponentResponse.java:355)

at com.sapportals.portal.prt.core.async.AsyncPortalComponentResponse.include(AsyncPortalComponentResponse.java:310)

at com.sapportals.portal.navigation.workAreaiView.doContent(workAreaiView.java:212)

at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)

at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)

at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)

at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)

at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable$1$DoDispatchRequest.run(AsyncIncludeRunnable.java:377)

at java.security.AccessController.doPrivileged(Native Method)

at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable.run(AsyncIncludeRunnable.java:390)

at com.sapportals.portal.prt.core.async.ThreadContextRunnable.run(ThreadContextRunnable.java:164)

at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:729)

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

[Former Member · Accepted solution]

We did network tracing in our NT server, it is receiving NO traffic from the portal server. 😕

[Former Member · Accepted solution]

Hi Joseph,

Actually the log is very helpful - I can see a kind of bug that we hade when the Portal is running on machine which are not UNIX or Windows – It is your case?

Are you able to view .NET portal component when you hit Refresh? (after you see the message .NET Server is not running).

Ok for the bottom line - if it is the Bug – It was fixed in PDK for .NET 1.0 Patch 2 that released today and can be downloaded from SAP Service Marketplace.

Regards,

Yehuda

[Former Member · Accepted solution]

We are on a Unix box with the portal, though. However, I will try installing Patch 2 to see if we have any luck with that.

Yes, any refresh receives the same ".net server is not running" error.

I should also note, we have tried changing the configuration to point at non existant servers and we receieve the same error, so the error message is not all that useful to us.

[Former Member · Accepted solution]

I just spent a half hour looking for this patch. Do you know what section of the marketplace it is in?

[Former Member · Accepted solution]

In this section:

Installations and Upgrades->SAP NetWeaver-> PDK FOR MS .NET

Regards,

Yehuda

[Former Member · Accepted solution]

I cannot find it. I went to Downloads -> Installations and Guides -> Entry by Application Group -> SAP Netweaver. Nowhere under there could I find it.

I tried searching on PDK FOR MS .NET and other variations with no luck (for that matter I cannot find patch 1 either).

I've been going to service.sap.com and going into SAP Support Portal. I log into that and that's where I go into Downloads, etc.

I'm a bit new to SAP's web setup here yet... what am I missing? Is this something I just don't have access to?

[Former Member · Accepted solution]

try this one -

<u>https://www.sdn.sap.com/sdn/downloaditem.sdn?res=/html/dotnetpdk_download.htm</u>

[Former Member · Accepted solution]

That worked. Now to try this patch out to see if it helps. Thanks!

[Former Member]

Okay, Patch 2 did not help the situation. However, I do have new information.

We have an SAP Portal consultant on site from SAP. When he logs onto our portal server an manually logs in, the PDK iview <u>works correctly</u>. However, if he goes to the portal via our IISProxy redirect for single sign on, it does <u>not</u> work.

When I go to the PDK page, it does not work at all, either way.

Any guesses as to why it works under that one circumstance but not others?

continued thanks...

[Former Member]

I've got this on the NT server's event logs....

1) Exception Information

*********************************************

Exception Type: System.Runtime.Remoting.RemotingException

Message: Remoting configuration failed with the exception System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Net.Sockets.SocketException: Only one usage of each socket address (protocol/network address/port)

is normally permitted

at System.Runtime.Remoting.Channels.Tcp.TcpServerChannel.StartListening(Object data)

at System.Runtime.Remoting.Channels.Tcp.TcpServerChannel.SetupChannel()

at System.Runtime.Remoting.Channels.Tcp.TcpServerChannel..ctor(IDictionary properties, IServerChannelSinkProvider sinkProvider)

at System.Runtime.Remoting.Channels.Tcp.TcpChannel..ctor(IDictionary properties, IClientChannelSinkProvider clientSinkProvider, IServerChannelSinkProvider serverSinkProvider)

--- End of inner exception stack trace ---

at System.Reflection.RuntimeConstructorInfo.InternalInvoke(BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean isBinderDefault)

at System.Reflection.RuntimeConstructorInfo.Invoke(BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)

at System.RuntimeType.CreateInstanceImpl(BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes)

at System.Activator.CreateInstance(Type type, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes)

at System.Runtime.Remoting.RemotingConfigHandler.CreateChannelFromConfigEntry(ChannelEntry entry)

at System.Runtime.Remoting.RemotingConfigHandler.ConfigureChannels(RemotingXmlConfigFileData configData)

at System.Runtime.Remoting.RemotingConfigHandler.ConfigureRemoting(RemotingXmlConfigFileData configData).

TargetSite: Void ConfigureRemoting(System.Runtime.Remoting.Activation.RemotingXmlConfigFileData)

HelpLink: NULL

Source: mscorlib

StackTrace Information

*********************************************

Server stack trace:

at SAP.Portal.Framework.Host.PortalHost.RemotingConfig(String configFile)

at System.Runtime.Remoting.Messaging.StackBuilderSink.PrivateProcessMessage(MethodBase mb, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)

at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg, Int32 methodPtr, Boolean fExecuteInContext)

Exception rethrown at [0]:

at SAP.Portal.Framework.Host.PortalHost.Start(HostData hostData)

at SAP.Portal.Framework.PortalInstance.Server.Start()

at SAP.Portal.Framework.PortalInstance.Server.Main()

I'm looking into deciphering what this means.

[Former Member]

Hi Joseph,

First you need to ensure that this is not an old log.

at your log you can see - "...Only one usage of each socket address (protocol/network address/port).."

[Removed by the moderator.]

Regards,

Yehuda

[Former Member]

The time on the event is from my testing this morning.

The port is available. we stopped the service, attempted to telnet to it on 8050, and it failed. We started the service, attempted the telnet, and it succeeded. We also enumerated the ports and 8050 was listed as a status of LISTENING when the service was running.

We also tried shutting down the service and running the command app. That made no change.

We also noticed that events are not always logged on the NT box. I'm going to try and get log information from the Portal, but our Portal admin is overloaded with other issues so it may not be soon. Any further debugging ideas are appreciated.

[Former Member]

I will check out the debugging options. We are using EP 6 SP 10, and Patch 1 of the .Net PDK.

[Former Member]

Hi Joseph,

First of all which version of the PDK for .NET and the Portal you are using ?

If the PDK for .NET is - Patch 1

The portal should be EP6 SP9.

You can get more information from the Logger - go to the Visual Administration ->Log configurator -> Location : com\sap\portal\dotnet change the severity to All.

You should get more information a bout the problem.

BTW

You can also can check the NT Event Log under source SAP for more details.

Regards,

Yehuda