Netdrive fails to connect Portal

I have been using Netdrive 4.1 to connect Oracle Portal for a while. One of the environments was restored by the DBA a few weeks before. Since then, the netdrive cannot connect to it anymore. It always return 503 Service Unavailable.
I tried other webdav client and it works. The IE and Firefox also works without any error. Anyone know is it a problem of netdrive itself?

Similar issue has hsppen to my 2 gen itouch after 3.1.1 update. If the ssid is not broadcasted, itouch wont remember the network name.
Network at work, the ssid is not broadcasted and there is no password for the network. Every time after I put itouch to sleep, I will need to enter the network name again when I turn on the itouch. The 1st gen itouch without 3.1.1 update doesn't require me input the network name over and over.
Just tested the home network. Everything works fine if I have ssid broadcasted. Once I hide the ssid, itouch wont pick up the network at all until I manually type in the network name. It also forgets the password as well just like what posthocergopropterhoc had mentioned.
I am very positive that firmware 2.2.2 does pick up hidden ssid once it has been entered once. However, I will double check again with my friend's itouch again tomorrow and post the confirmation.
I am not sure if Apple purposely design 3.1.1 upgrade to act this way, but its for sure very inconvenient. Especially when it says on itouch network interface that "Known networks will be joined automatically". I do consider I know my own network even if the ssid is hidden for privacy reason.
Message was edited by: WonderingPisces

Similar Messages

REP-56110: Failed to connect to security repository Oracle Portal.

Dear All,
I need your help on the error REP-56110: Failed to connect to security repository Oracle Portal.
I have installed Oracle Application Server 10g R2.
I have enabled SSO for form Sevice and Report Service.
I created OID user login and map it to my database user (on which my Application Run).
When i run my application, SSO page apear. I login it with user id and Password and My application Runing Succesfully. But when i call Reports from my Application through Run_Repor_Object or Web.Show document. I get the error REP-56110: Failed to connect to security repository Oracle Portal.
my oid user id and passwor is as follow
username = ssotest
password = ssotest1
IF i run rwservlet command. It is showing the Server page with Secure mode.
http://server:7778/reports/rwservlet/showjobs?
What is the reasong behind this? Help me out.
http://server/reports/rwservlet?destype=cache&desformat=pdf&report=sr_master.rdf&FromDate='01-JAN-12'&ToDate='31-DEC-12'&SSOConn=test/OracleDB/ssotest
where -- test is my Resoruce Name define in OID
oracleDB Resource Type
ssotest my sso user name
Edited by: Meherban Khan on Mar 27, 2012 6:21 AM

I changed %PORTAL_DB_USERNAME%/%PORTAL_DB_PASSWORD%@%PORTAL_DB_TNSNAME%
with the actual username/password of the portal schema. Now i get the following Error.
REP-56071: Security check failed with error message: Error code30004 - Cannot access the output type:cache
In package:wwv_rw_usr function:security_check
Command line is: server=rep_portal_form_report_services report=KPIx/Churn Analysis/ChurnByAgeGroup.jsp destype=cache desformat=html rundate="27-DEC-05 12:12:20"
Executed on:12/27/05 12:12:29

RSP- Fail to connect SAP Portal

Good morning...
Hopefully you can help me....
I need to download new tasks from RSP task: System task to retrieve tasks, but I can't do it, cause it shows me : Fail to retrieve tasks on back-end. I don't know what does it means...
I checked and had test e-mail connection and the result was ok. Data base connection either.
But, when I try to connect on SAP channel from RSP, the following message display: Fail to connect to SAP channel...
Some help?
Regards...

Hi Seth...
Thanks for answer...
Yes...I've imported it...
I upgraded it to PL05 too...And tried again, but by using another S-user.
I know if I can't connect to SAP channel, I can upload new tasks...But I still can't do it...
Wait for news...
Regards...
Valter Martins da Silva

Problem while creating Logical System Connecting Portal to ECC (Backend)...

Hi
- I am trying to connect portal to ABAP so that from portal's iView i could access any ABAP T-Code (e.g. SE37).
- Secondly, just wanted to let you know that i am not implementing SSO.
- I used iView's SAP GUI Type = SAP GUI for HTML.
I made following 3 tests, out of which ITS connection is failed. and while previewing my iView i m not able to connect with ABAP and giving error: "The URL http://192.168.1.104:8001/sap/bc/gui/sap/its/webgui was not called due to an error."
Could u pls guide me what to do.... And i mentioned everything at the bottom in detail.
Thanks & looking forwarded for your replies.....
SAP Web AS Connection (Successful)
Test Details:
The test consists of the following steps:
1. Checks the validity of system ID in the system object.
2. Checks if the system can be retrieved from the PCD.
3. Check whether a SAP system is defined in the system object
4. Validate the following parameters: WAS protocol; WAS host name
5. Checks if the host name of the server can be resolved.
6. Pings the server to see if it is alive.
7. Pings the WAS ping service; works only if the service is activated on the ABAP WAS.
8. Checks HTTP/S connectivity to the defined back-end application
Results
1. The system ID is valid
2. The system was retrieved.
3. The system object represents an SAP system
4. The following parameters are valid: Web AS Protocol (http) Web AS Host Name (192.168.1.104:8001)
5. The host name 192.168.1.104 was resolved successfully.
6. The server 192.168.1.104 was pinged successfully.
7. The Web AS ping service http://192.168.1.104:8001/sap/bc/ping was pinged successfully.
8. An HTTP/S connection to http://192.168.1.104:8001/sap/bc/bsp/sap was obtained successfully.
ITS Connection (Failed)
Test Details:
The test consists of the following steps:
1. Checks the validity of system ID in the system object.
2. Checks if the system can be retrieved from the PCD.
3. Check whether the system object has a valid system alias
4. Check whether a SAP system is defined in the system object
5. Validate the following parameters: ITS protocol; ITS host name
6. Checks if the host name of the server can be resolved.
7. Pings the server to see if it is alive.
8. Checks HTTP/S connectivity to the defined back-end application
Results
1. The system ID is valid
2. The system was retrieved.
3. Retrieval of the default alias was successful
4. The system object represents an SAP system
5. The following parameters are valid: ITS Protocol (http) ITS Host Name (192.168.1.104:8001)
6. The host name 192.168.1.104 was resolved successfully.
7. The server 192.168.1.104 was pinged successfully.
8. User mapping is valid
9. An HTTP/S connection to http://192.168.1.104:8001/sap/bc/gui/sap/its/webgui/ was not obtained successfully; this might be due to a closed port on the Firewall.
Test Connection with Connector (Successful)
Test Details:
The test consists of the following steps:
1. Retrieve the default alias of the system
2. Check the connection to the backend application using the connector defined in this system object
Results
1. Retrieval of default alias successful.
2. Connection successful.
I am getting following error while Previeiwng iView.
Error when processing your request
What has happened?
The URL http://192.168.1.104:8001/sap/bc/gui/sap/its/webgui was not called due to an error.
Note
The following error text was processed in the system D10 : Template interpretation cancelled, syntax error.
The error occurred on the application server eccdcs1s_D10_01 and in the work process 0 .
The termination type was: RABAX_STATE
The ABAP call stack was:
      SYSTEM-EXIT of program SAPLSFUNCTION_BUILDER
      Function: RS_FUNCTION_INITIAL_SCREEN of program SAPLSFUNCTION_BUILDER
      Method: IF_WB_PROGRAM~PROCESS_WB_REQUEST of program CL_FB_FUNCTION_INITIAL_SCREEN=CP
      Method: DO_THE_NAVIGATION of program CL_WB_NAVIGATOR===============CP
      Method: DO_THE_NAVIGATION of program CL_WB_NAVIGATOR_VIS_AS_DYNPRO=CP
      Method: PROCESS_WB_REQUEST of program CL_WB_MANAGER=================CP
      Method: PROCESS_REQUEST_QUEUE of program CL_WB_MANAGER=================CP
      Method: IF_WB_MANAGER~SET_WORKSPACE of program CL_WB_MANAGER=================CP
      Method: START_INTERNAL of program CL_WB_STARTUP=================CP
      Module: MANAGER_START of program SAPLWB_MANAGER
What can I do?
If the termination type was RABAX_STATE, then you can find more information on the cause of the termination in the   system D10 in transaction ST22.
If the termination type was ABORT_MESSAGE_STATE, then you can find more information on the cause of the termination on the application server eccdcs1s_D10_01 in transaction SM21.
If the termination type was ERROR_MESSAGE_STATE, then you can search for more information in the trace file for the work process 0 in transaction ST11 on the application server eccdcs1s_D10_01 . In some situations, you may also need to analyze the trace files of other work processes.
If you do not yet have a user ID, contact your system administrator.
Error code: ICF-IE-http -c: 001 -u: SAPUSER -l: E -s: D10 -i: eccdcs1s_D10_01 -w: 0 -d: 20090924 -t: 202054 -v: RABAX_STATE -e: ITS_CANT_LOAD_INCLUDE
HTTP 500 - Internal Server Error
Your SAP Internet Communication Framework Team
Edited by: Harpal Singh on Sep 24, 2009 4:55 PM

Hi,
> Goto SE80, Select "Internet Service". Give service name as WEBGUI and enter. Right click on the WEBGUI and select Publish - > Complete service.
Source : http://wiki.sdn.sap.com/wiki/display/BI/BiAdminCockpit+Issues
Or call transaction SIAC_PUBLISH_ALL_INTERNAL to publish all services.
[Note 964521 - Short dump ITS_CANT_LOAD_INCLUDE w/ call of SAP GUI for HTML|https://service.sap.com/sap/support/notes/964521].
Regards,
Pierre

Mail Fails To Connect In My Office Network, Works on Reboot

This is baffling me and my network admin:
Mail fails to connect to any of my accounts at work. But it recovers if I reboot my machine.
Here is what happens:
- Mail works just fine at home. Connects to gmail, iCloud, and a 3rd party email account no problems.
- I get to the office
- I log in to the office WiFi with my password - for this I have to open a browser window, and enter my credentials.
(I kind of assume that this is the problem ^^)
- All my internet connections work fine, I can use the browser to access Gmail etc
- Mail refuses to connect to any of my email servers, and all accounts go offline
- Connection Doctor says "Mail can connect to the internet" but all individual connections are red, not reachable. I checked "detail" too - its empty.
Then I reboot my Mac, and after that everything's happy. Mail connects to my accounts normally, and Connection Doctor marks all as green.
Since it works on reboot, we can rule out network problems like closed ports etc. So the only thing I can think of is that Mail initially tries to connect as soon as I am on WiFi, then hangs (because I am not logged in yet), and somehow this hang is of a kind that does not recover (I've left it on for hours at a time, no difference, it never recovers).
Anyone have any ideas about this? Is there some way I can restart networking daemons to kill the hung connections. Or any other way I can diagnose this?

A captive portal, which is what you have, can work in any of at least three ways: by HTTP redirection, IP redirection, or DNS poisoning. I'm guessing that yours is the last type. In that case, a TTL of zero should be used. If the TTL is non-zero, then Internet applications may not work until the DNS cache is flushed. That happens when you reboot.
You should discuss the possibility with your network admin. If the network configuration isn't going to be changed, you may be able to avoid the need to reboot by flushing the DNS cache manually, as described in the article linked below:
OS X: How to reset the DNS cache

Failed to connect to VMware web service: Invalid keystore

Hi,
We have a CPO 2.3.1 that refuses to connect to vCenter (see log extract at the end of the post).
We recently changed our vCenter server (part of an update to 5.1).
We tried following workarounds:
remove and add all platform elements from the portal using SE services
re import automation packs (the 4 from the Starter Edition v2.3.1.38)
re set the keystore password
No change at all...
Would you have a clue on how to correct that?
Thank you.
Regards,
Pierre
||235|2012/10/02 15:46:21.667|6072||||WCF: <TraceRecord xmlns="http://schemas.microsoft.com/2004/10/E2ETraceEvent/TraceRecord" Severity="Error"><TraceIdentifier>http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.TraceHandledException.aspx</TraceIdentifier><Description>Handling an exception.</Description><AppDomain>Tidal.Automation.Server.exe</AppDomain><Exception><ExceptionType>Tidal.Scheduler.Common.Communications.CommunicationException, Tidal.Scheduler.Common, Version=2.3.0.0, Culture=neutral, PublicKeyToken=fba593b23cf207cd</ExceptionType><Message>The attempt to connect to (VMware vCenter Server (603)@VMware vCenter Server (603)) has failed due to following error: Failed to connect to VMware web service: Invalid keystore.</Message><StackTrace> at Tidal.Automation.Server.JavaAdapterBase.PerformServerAssistedOperation(ServerAssistedOperation operation, TargetConfiguration target, RuntimeUserConfiguration runtimeUser)
 at Tidal.Automation.Server.JavaAdapterBase.PerformServerAssistedOperation(ServerAssistedOperation operation)
 at Tidal.Automation.Engine.Core.Adapter.SuspendableAdapter.&lt;&gt;c__DisplayClass1c.&lt;PerformServerAssistedOperation&gt;b__1b(IAdapter adapter)
 at Tidal.Automation.Engine.Core.AdapterLifecycleManager.PerformAdapterAction(Guid adapterId, AdapterAction action, Boolean haltingAction, Int32 remainingRetries)
 at Tidal.Automation.Engine.Core.AdapterLifecycleManager.PerformAdapterAction(Guid adapterId, AdapterAction action, Boolean haltingAction)
 at Tidal.Automation.Engine.Core.AdapterLifecycleManager.PerformAdapterAction(Guid adapterId, AdapterAction action)
 at Tidal.Automation.Engine.Core.Adapter.SuspendableAdapter.PerformServerAssistedOperation(ServerAssistedOperation operation)
 at Tidal.Automation.Engine.Core.AdapterSystem.PerformServerAssistedOperation(ServerAssistedOperation operation)
 at Tidal.Automation.Server.WebService.AdapterService.PerformServerAssistedOperation(ServerAssistedOperation operation)
 at SyncInvokePerformServerAssistedOperation(Object , Object[] , Object[] )
 at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]&amp; outputs)
 at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc&amp; rpc)
 at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc&amp; rpc)
 at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage31(MessageRpc&amp; rpc)
 at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)</StackTrace><ExceptionString>Tidal.Scheduler.Common.Communications.CommunicationException: The attempt to connect to (VMware vCenter Server (603)@VMware vCenter Server (603)) has failed due to following error: Failed to connect to VMware web service: Invalid keystore.
 at Tidal.Automation.Server.JavaAdapterBase.PerformServerAssistedOperation(ServerAssistedOperation operation, TargetConfiguration target, RuntimeUserConfiguration runtimeUser)
 at Tidal.Automation.Server.JavaAdapterBase.PerformServerAssistedOperation(ServerAssistedOperation operation)
 at Tidal.Automation.Engine.Core.Adapter.SuspendableAdapter.&lt;&gt;c__DisplayClass1c.&lt;PerformServerAssistedOperation&gt;b__1b(IAdapter adapter)
 at Tidal.Automation.Engine.Core.AdapterLifecycleManager.PerformAdapterAction(Guid adapterId, AdapterAction action, Boolean haltingAction, Int32 remainingRetries)
 at Tidal.Automation.Engine.Core.AdapterLifecycleManager.PerformAdapterAction(Guid adapterId, AdapterAction action, Boolean haltingAction)
 at Tidal.Automation.Engine.Core.AdapterLifecycleManager.PerformAdapterAction(Guid adapterId, AdapterAction action)
 at Tidal.Automation.Engine.Core.Adapter.SuspendableAdapter.PerformServerAssistedOperation(ServerAssistedOperation operation)
 at Tidal.Automation.Engine.Core.AdapterSystem.PerformServerAssistedOperation(ServerAssistedOperation operation)
 at Tidal.Automation.Server.WebService.AdapterService.PerformServerAssistedOperation(ServerAssistedOperation operation)
 at SyncInvokePerformServerAssistedOperation(Object , Object[] , Object[] )
 at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]&amp; outputs)
 at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc&amp; rpc)
 at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc&amp; rpc)
 at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage31(MessageRpc&amp; rpc)
 at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)</ExceptionString></Exception></TraceRecord>
||236|2012/10/02 15:46:21.667|6072||||An exception that was not of type RhapsodyException was caught while a webmethod call was being made. This exception has been caught and genericized.
||237|2012/10/02 15:46:21.667|6072||||EXCEPTION (Tidal.Scheduler.Common.Communications.CommunicationException): The attempt to connect to (VMware vCenter Server (603)@VMware vCenter Server (603)) has failed due to following error: Failed to connect to VMware web service: Invalid keystore.
Stack Trace: at Tidal.Automation.Server.JavaAdapterBase.PerformServerAssistedOperation(ServerAssistedOperation operation, TargetConfiguration target, RuntimeUserConfiguration runtimeUser)
 at Tidal.Automation.Server.JavaAdapterBase.PerformServerAssistedOperation(ServerAssistedOperation operation)
 at Tidal.Automation.Engine.Core.Adapter.SuspendableAdapter.<>c__DisplayClass1c.<PerformServerAssistedOperation>b__1b(IAdapter adapter)
 at Tidal.Automation.Engine.Core.AdapterLifecycleManager.PerformAdapterAction(Guid adapterId, AdapterAction action, Boolean haltingAction, Int32 remainingRetries)
 at Tidal.Automation.Engine.Core.AdapterLifecycleManager.PerformAdapterAction(Guid adapterId, AdapterAction action, Boolean haltingAction)
 at Tidal.Automation.Engine.Core.AdapterLifecycleManager.PerformAdapterAction(Guid adapterId, AdapterAction action)
 at Tidal.Automation.Engine.Core.Adapter.SuspendableAdapter.PerformServerAssistedOperation(ServerAssistedOperation operation)
 at Tidal.Automation.Engine.Core.AdapterSystem.PerformServerAssistedOperation(ServerAssistedOperation operation)
 at Tidal.Automation.Server.WebService.AdapterService.PerformServerAssistedOperation(ServerAssistedOperation operation)
 at SyncInvokePerformServerAssistedOperation(Object , Object[] , Object[] )
 at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]& outputs)
 at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc)
 at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc)
 at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage31(MessageRpc& rpc)
 at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)

You have an invalid keystore file because the HTTPS certification has changed. You need to delete the old keystore file and restart the CPO server and then reconnect/run something against vCenter.
There is also a possibility for Adatper Host Framework/java issues that I have seen commonly.
If you need more help, you'll need to open a TAC case with your services contract please. We normally try to not troubleshoot logs on the forums.
-Shaun Roberts
CIAC/CPO Support Team Lead
[email protected]

Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)

Hello All,
There are some changes in out portal sever, but not related to SAP EP.
So it is needed to restart the server. After restarting the server,
we are not avail to start the server. There is nothing in the SAPMMC.
"There is no item to display" is showing in the SAPMMC.
So we tried couple of time to get the SAPMMC icons by restarting the server.
But it is not getting any display in SAPMMC.
I am sending some part of the latest log file of that server below:
Our server name is INMAA02AS03.
1.5#00145E3D3B630046000000000000175000041A3F6EB5EB39#1154759649523#com.sap.engine.core.cluster.impl6.ms.MSEventListener##com.sap.engine.core.cluster.impl6.ms.MSEventListener.putLogonInfo(protocol, port, serverCount)#######OrderedChannel for http service##0#0#Error##Plain###java.net.SocketException: Socket closed#
#1.5#00145E3D3B630046000000010000175000041A3F6EB5EC0B#1154759649523#com.sap.engine.core.cluster.impl6.ms.MSEventListener##com.sap.engine.core.cluster.impl6.ms.MSEventListener.putLogonInfo(protocol, port, serverCount)#######OrderedChannel for http service##0#0#Error##Plain###java.net.SocketException: Socket closed
     at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:99)
     at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
     at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:66)
     at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:124)
     at com.sap.engine.core.cluster.impl6.ms.MSMessageHeader.write(MSMessageHeader.java:401)
     at com.sap.engine.core.cluster.impl6.ms.MSRawConnection.sendRawMessage(MSRawConnection.java:1017)
     at com.sap.engine.core.cluster.impl6.ms.MSRawConnection.sendRawMessage(MSRawConnection.java:971)
     at com.sap.engine.core.cluster.impl6.ms.MSEventListener.putLogonInfo(MSEventListener.java:1374)
     at com.sap.engine.core.cluster.impl6.ms.MSConnectionImpl.putLogonInfo(MSConnectionImpl.java:605)
     at com.sap.engine.core.cluster.impl6.ClusterManagerImpl.putLogonInfo(ClusterManagerImpl.java:3144)
     at com.sap.engine.core.service630.context.cluster.session.CommunicationSessionContextImpl.putLogonInfo(CommunicationSessionContextImpl.java:143)
     at com.sap.engine.services.httpserver.dispatcher.HttpDispatcherFrame.putLogonInfo(HttpDispatcherFrame.java:854)
     at com.sap.engine.services.httpserver.dispatcher.HttpDispatcherFrame.closeSocket(HttpDispatcherFrame.java:800)
     at com.sap.engine.services.httpserver.dispatcher.HttpDispatcherFrame.stop(HttpDispatcherFrame.java:404)
     at com.sap.engine.core.service630.container.ServiceStopper.run(ServiceStopper.java:31)
     at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
     at com.sap.engine.core.thread.impl6.SingleThread.execute(SingleThread.java:78)
     at com.sap.engine.core.thread.impl6.SingleThread.run(SingleThread.java:148)
#1.5#00145E3D3B630046000000020000175000041A3F6EB5F178#1154759649523#com.sap.engine.services.httpserver.dispatcher##com.sap.engine.services.httpserver.dispatcher#######OrderedChannel for http service##0#0#Error##Plain###Cannot update HTTP load balancing information in the Message service
com.sap.engine.frame.cluster.ClusterException: Socket closed
     at com.sap.engine.core.cluster.impl6.ms.MSEventListener.putLogonInfo(MSEventListener.java:1377)
     at com.sap.engine.core.cluster.impl6.ms.MSConnectionImpl.putLogonInfo(MSConnectionImpl.java:605)
     at com.sap.engine.core.cluster.impl6.ClusterManagerImpl.putLogonInfo(ClusterManagerImpl.java:3144)
     at com.sap.engine.core.service630.context.cluster.session.CommunicationSessionContextImpl.putLogonInfo(CommunicationSessionContextImpl.java:143)
     at com.sap.engine.services.httpserver.dispatcher.HttpDispatcherFrame.putLogonInfo(HttpDispatcherFrame.java:854)
     at com.sap.engine.services.httpserver.dispatcher.HttpDispatcherFrame.closeSocket(HttpDispatcherFrame.java:800)
     at com.sap.engine.services.httpserver.dispatcher.HttpDispatcherFrame.stop(HttpDispatcherFrame.java:404)
     at com.sap.engine.core.service630.container.ServiceStopper.run(ServiceStopper.java:31)
     at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
     at com.sap.engine.core.thread.impl6.SingleThread.execute(SingleThread.java:78)
     at com.sap.engine.core.thread.impl6.SingleThread.run(SingleThread.java:148)
Caused by: java.net.SocketException: Socket closed
     at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:99)
     at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
     at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:66)
     at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:124)
     at com.sap.engine.core.cluster.impl6.ms.MSMessageHeader.write(MSMessageHeader.java:401)
     at com.sap.engine.core.cluster.impl6.ms.MSRawConnection.sendRawMessage(MSRawConnection.java:1017)
     at com.sap.engine.core.cluster.impl6.ms.MSRawConnection.sendRawMessage(MSRawConnection.java:971)
     at com.sap.engine.core.cluster.impl6.ms.MSEventListener.putLogonInfo(MSEventListener.java:1374)
     ... 10 more
#1.5#00145E3D3B6300400000000B0000175000041A3F6EC43762#1154759650461#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B6300400000000D0000175000041A3F6EF146BF#1154759653414#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B6300400000000F0000175000041A3F6F1E56B0#1154759656367#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B630040000000110000175000041A3F6F4B6526#1154759659320#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B630040000000130000175000041A3F6F787519#1154759662273#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B630040000000150000175000041A3F6FA584C7#1154759665226#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B630040000000170000175000041A3F6FD29438#1154759668179#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B630040000000190000175000041A3F70014F86#1154759671242#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B6300400000001B0000175000041A3F70300A99#1154759674304#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B6300400000001D0000175000041A3F705D1A24#1154759677257#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B6300400000001F0000175000041A3F705D1B81#1154759677257#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###ReadThread: failed to connect to server 11 times#
#1.5#00145E3D3B630040000000210000175000041A3F708A296B#1154759680210#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B630040000000230000175000041A3F70B738CB#1154759683163#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B630040000000250000175000041A3F70E4487A#1154759686116#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B630040000000270000175000041A3F7111581F#1154759689069#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B630040000000290000175000041A3F713E67B3#1154759692022#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B6300400000002B0000175000041A3F716B77A1#1154759694976#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B6300400000002D0000175000041A3F719886C2#1154759697929#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B6300400000002F0000175000041A3F71C596D5#1154759700882#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B630040000000310000175000041A3F71F45176#1154759703944#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B630040000000330000175000041A3F72230C96#1154759707007#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B630040000000350000175000041A3F72230DF3#1154759707007#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###ReadThread: failed to connect to server 21 times#
#1.5#00145E3D3B630040000000370000175000041A3F72501BF9#1154759709960#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B630040000000390000175000041A3F727D2BC1#1154759712913#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B6300400000003B0000175000041A3F72AA3BCA#1154759715866#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B6300400000003D0000175000041A3F72D74B1A#1154759718819#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B6300400000003F0000175000041A3F73045A4C#1154759721772#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B630040000000410000175000041A3F73316A0D#1154759724725#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B630040000000430000175000041A3F735E799A#1154759727678#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B630040000000450000175000041A3F738D34D0#1154759730740#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B630040000000470000175000041A3F73BBEF81#1154759733803#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B630040000000490000175000041A3F73E8FF05#1154759736756#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B6300400000004B0000175000041A3F73E90064#1154759736756#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###ReadThread: failed to connect to server 31 times#
#1.5#00145E3D3B6300400000004D0000175000041A3F74160E68#1154759739709#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B6300400000004F0000175000041A3F74431E16#1154759742662#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B630040000000510000175000041A3F74702DEA#1154759745615#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B630040000000530000175000041A3F749D421D#1154759748568#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B630040000000550000175000041A3F74CA4CD6#1154759751521#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B630040000000570000175000041A3F74F75CC8#1154759754474#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B630040000000590000175000041A3F75246C5C#1154759757427#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B6300400000005B0000175000041A3F75517C0B#1154759760381#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B6300400000005D0000175000041A3F7580368E#1154759763443#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B6300400000005F0000175000041A3F75AEF19A#1154759766505#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B630040000000610000175000041A3F75AEF2F2#1154759766505#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###ReadThread: failed to connect to server 41 times#
Any idea what to do?
Please help me out.
**Points will be rewarded for a suitable answer.
Regards,
Uttam.

Hi Uttam,
Were you able to solve the problem? I am also getting a similar error message. If you had solved your problem, please share, how?
Thanks & Regards,
Santhosh.C

Failed to connect to backend system

Hello,
I have installed visual composer and experience some errors.
My system fails to connect to the backend system in VC. I am able to create SAP transaction iviews for the system, see the alias, and user mapping is configured.
When I perform the System Connection test for my system which based on the load balancing template. All the test fail except the ITS test.
- SAP Web AS - SAP Web Application Server
- ITS Connection Tests the connection to an SAP
- Connection Test for Connectors Tests
- Connection Test Through DQE
Must all these test pass, or is it enough with only a subset of these tests. Does the alias have to be the same as the logical system.

Hi Jørgen,
It is a genuin problem. Just tell your Portal Administrator to give the userid (which you are using to log in to the portal from VC) the full authority for the alias you want to access from VC, as it is the portal administrator who has the rights to give access to various portal users. In the portal, the administrator can give a user the access to an alias by selecting that alias and change the required property.
Try the following flow to get the required document:-
help.sap.com->SAP Netweaver->SAP Netweaver 2004->people integration->portal->Administration Guide->System Administration->Permission,Role/User........
Check out the given help document, I hope it will help you in solving your problem.
Check out the section 3.2 (specially steps 25-30) in the pdf file provided in the following link :-
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/6209b52e-0401-0010-6a9f-d40ec3a09424
Thanks in advance,
Deep.

Error when connecting Portal to ECC system

I am trying to connect Portal system to our ECC system.
We are on Portal 7.00 ECC 6.0. Portal is on SP 18
I performed following activities:
1. Created certificates on both sides and imported them
2. Created the ECC system in Portal with followin values
1) Connector:
     Application Host : pos_bmt.com:8000
     SAP Client:100
     SAP System: REC
     Port: 3200
     System type: SAP_R3
   2) Web AS:
     Web AS Host Name: pos_bmt.com:8000
     Web AS Path: /sap/bc/bsp/sap
     Protocol : http
   3) ITS
     ITS Host Name: pos_bmt.com:8000
     ITS Path: /sap/bc/gui/sap/its/webgui/
     Protocol : http
   4) User management
     Authentication: SAP Logon Ticket
     Logon Method: SAPLOGONTICKET
     User Mapping Type: admin, user
3. Crearted Alias and did connection test
   1) SAP Web AS Connection was successful
   2) ITS Connection was successful
   3) Connection Test for Connectors was successfu;
After then, I created an iview, but I was promted to login with an error : u201CSSO logon not possible; cookies must be activated in the browseru201D. So I performed a test on the support desk, SAP GUI for windows was successful, but SAP GUI for html was failed with the same error message, u201CSSO logon not possible; cookies must be activated in the browseru201D]
Any feedback would be greatly appreciated.
Justin
Edited by: Juhan Kim on Jul 9, 2009 10:53 AM

Hi Justin,
SSO logon not possible; logon tickets not activated on the server
Please check your WAS Profile Parameters in RZ11:
For enabled SSO,WAS should have the possibility to create and accept SSO-Tickets. For that the Profile Parameters should be:
login/create_sso2_ticket = 2
login/accept_sso2_ticket = 1
Regards,

Potal Authorisation Error:"Failed to connect backend system.Check your syst

Hi Experts,
Please advise me on how to proceed....
I created a dashboard reports (5) based on 5 different reports in BI Queries using Visual Composer...I deployed them to portal and in portal i assigned those iviews to a role and assigned that role to a end user.
In BW end user is autorized to execute those 5 queries and in portal user is able to access those queries as well
But when he tried to execute Dashboard reports..it is displaying error
"Failed to connect backend system.Check your system definition and user priviliges"
Then i modified his authorisations in BW assigned SAP_J2EE_ADMIN role in BW and then in portal he is able to execute the Dashboard reports...by assigning the SAP_J2EE_ADMIN role he is able to execute dashboards in portal and he got more authorisation in portal than he required like 'Content Admin','User Admin' and 'System Admin'
I tried by using SAP_J2EE_GUEST role but he is getting error
"Failed to connect backend system.Check your system definition and user priviliges"
Please advise on how to proceed
Thanks

Hi,
Refer,
Visual composer
Failed to connect to backend system. Check your system definition and user
Regards,
P.Manivannan.

"Failed to connect backend system.Check your system definition and user pri

Hi Experts,
I am a BW Consultant working on Portal & Visual Composer (7.0)
As a Developer i got SAP_ALL & SAP_J2EE_ADMIN roles in BW and System Admin and VC role in Portal.
In Portal Created/Published iviews for BW Queries (Transaction) and Published them to a role (role1) in portal.
In Visual Composer i developed Dashboard reports on BW Queries ,made them public and deployed them to a portal role(role 1) in portal.
I assigned portal role to my self and tested the queries and dashboards in portal everything is working perfectly.
In VC i can see 3 different systems defined in Portal
I created a Test user (with profile of end user) in BW,Testuser is authorised to view all the reports in BW and All data in all data targets and in portal testuser is assigned with Role1 and VC Role.
(Note: In BW Testuser doesn't had J2EE_ADMIN role).
Portal:
When i login to portal as testuser and tries to execute the BW Queries (Transaction) and it working perfectly.
When i tried to execute Dashboard reports developed in Visual Composer it gives me an error
"Failed to connect backend system.Check your system definition and user priviliges"
In Visual Composer i logged in as testuser (as test user got VC role assigned) i can't see any list of avaliable systems under "Find Data"
When i modified testuser profile in BW and updated with SAP_J2EE_ADMIN then i can execute the dashboard report but at the same time testuser got more than what he should have like user admin,system admin...etc
I searched the sdn and find some similar threads ...but nothing was useful
Please update me what went wrong and how to fix this...
Thanks in advance

Hi,
Refer,
Visual composer
Failed to connect to backend system. Check your system definition and user
Regards,
P.Manivannan.

Failed to connect backend system

Hi Experts,
I am a BW Consultant working on Portal & Visual Composer (7.0)
As a Developer i got SAP_ALL & SAP_J2EE_ADMIN roles in BW and System Admin and VC role in Portal.
In Portal Created/Published iviews for BW Queries (Transaction) and Published them to a role (role1) in portal.
In Visual Composer i developed Dashboard reports on BW Queries ,made them public and deployed them to a portal role(role 1) in portal.
I assigned portal role to my self and tested the queries and dashboards in portal everything is working perfectly.
In VC i can see 3 different systems defined in Portal
I created a Test user (with profile of end user) in BW,Testuser is authorised to view all the reports in BW and All data in all data targets and in portal testuser is assigned with Role1 and VC Role.
(Note: In BW Testuser doesn't had J2EE_ADMIN role).
Portal:
When i login to portal as testuser and tries to execute the BW Queries (Transaction) and it working perfectly.
When i tried to execute Dashboard reports developed in Visual Composer it gives me an error
"Failed to connect backend system.Check your system definition and user priviliges"
In Visual Composer i logged in as testuser (as test user got VC role assigned) i can't see any list of avaliable systems under "Find Data"
When i modified testuser profile in BW and updated with SAP_J2EE_ADMIN then i can execute the dashboard report but at the same time testuser got more than what he should have like user admin,system admin...etc
I searched the sdn and find some similar threads ...but nothing was useful
Please update me what went wrong and how to fix this...
Thanks in advance

Hi,
Please check the permissions on your system object. This issues is from Portal itself not BW backend.
System Administration->System Configuration->System landscape->Browse for the System Object that has been used in your VC->right click to open the permissions.
Check for the permission for eu_role/everyone group. These should have alteast "read"permission on the System Object. If this permission is missing add up here.
By default all users fall in "everyoone' group, so I suggest adding 'read' permission to this group itself.
Hope this helps,
Thanks,
Vamshi

Error in MDM - EP integration : "Failed to connect to MDM server. ....."

Dear SDN,
I m in middle of configuring the MDM and EP integration.
EP Version Info :
J2EE Engine 6.40 PatchLevel 108290.313
Portal 6.0.20.0.0
BP has been installed.
We are able to view MDM system and MDM search IViews in the Wizards in the portal.
MDM Version Info : MDM 5.5 SP 04
I come across the following error :
Step 4: An error has occurred
Failed to connect to MDM server. Check your system. The server may be down or there may be an error in one or more of your system parameters.
System parameters are Server name and pwd .
This parameters are used to start the server and pwd for accessing the server while mounting the server.
Also at the same time, my MDM server is running and repository is shown loaded and running.
Kindly suggest what should have been missed out from our side or some way we can make sure that error does not occur.
Please help.
Regards,
Chandani Shah.

Hi Chandani,
in Portal clik on Personalization, and in User Mapping you need to map the MDM repository user (may be Admin)..... then try another time.
Please, check the BP version in order to unserstand if it is the rigjt version for your MDM.
Hoper this help you.
Regards,
Vito

Webdispatcher error while trying to connect portal

Hi ,
I am facing an issue while trying to connect portal from web dispatcher server.
We have the portal http port as 5XX00 where XX is the instance no for portal .
Our portal is a standalone java system.
Now in between portal and web dispatcher there is a firewall and the required port for portal i.e. 5XX00 is opened in firewall.
To connect message server I have to give 2 parameters.
rdisp/mshost - portal FQDN
ms/http_port - 5XX00
Now I am getting the below error.
Checking SAP Web Dispatcher Configuration
=========================================
maximum number of sockets supported on this host: 8192
Server info will be retrieved from host: Porttalhost:5XX00 with protocol: http
Checking connection to message server...
ERROR: Unexpected HTTP OK code 404 received -
please check that 5XX00 is really the HTTP port of the Message Server
Check ended with 1 errors, 0 warnings.
I have tried with the ms/http_port - 81XX parameter as well.
Checking SAP Web Dispatcher Configuration
=========================================
maximum number of sockets supported on this host: 8192
Server info will be retrieved from host: Porttalhost:81XX with protocol: http
Checking connection to message server...
ERROR: Connection to message server failed: NIECONN_REFUSED
Check ended with 1 errors, 0 warnings
Experts I need your help on this .
Please reply.
Thanks,
Sandip

Hi,
>We have some web dynpro abap applications running in portal connected to ECC and SRM server.
You configured successfully external access to your internal portal using the Web dispatcher but you did not give access to your SRM or ECC systems.
I think that when an abap web dynpro application is displayed in a portal iview, the web browser needs to connect to the abap server. I think that the portal does not act as a kind of reverse proxy.
I say "I think" because I have not yet tested this case.
If I am right you have to configure external access to ECC or SRM using an other web dispatcher (or the same if it is 7.2) and you have to configure the portal to use the web dispatcher enabled URLs for the abap web dynpro applications.
That should be an interesting project !
Regards,
Olivier

Failed to connect Error - Need Help, Please

I installed , created the simple "Hello" program and it ran fine on the simulator.
Then, I click the run OTA and now I'm in deep yogurt!
I get the message:
*** Error ***
Failed to connect to device 0!
Reason:
Emulator 0 terminated while waiting for it to register!
BUILD SUCCESSFUL (total time: 4 seconds)
I just want to restore things to what they were before I selected Run OTA. I've been reading for the past 3 hours and haven't found out to restore. I even deleted and re-installed but, still get the same meassge (probably some saved java pref file...). Anyway, HOW TO RESTORE to a virgin setup????
Thanks

... I read somewhere I need to reboot - I did and it took care of it.

Netdrive fails to connect Portal

Similar Messages

Maybe you are looking for