Setup EWA in Solman - Service Cannot be Reached

Hi,
I was trying to setup EWA in solman for my satellite system. In Dswp-> Solution->Operation Setup->Setup EarlyWatch Alert, I got the following error:
Service cannot be reached
What has happened?
URL http://serverxxx:port/sap/bc/webdynpro/sap/dswp_earlywatch_admin call was terminated because the corresponding service is not available.
Note
The termination occurred in system SMN with error code 403 and for the reason Forbidden.
The selected virtual host was 0 .
What can I do?
Please select a valid URL.
If you do not yet have a user ID, contact your system administrator.
ErrorCode:ICF-NF-http-c:000-u:SAPSYS-l:E-i:ACMSAPD02_MNR_03-v:0-s:403-r:Forbidden
May I know how to rectify this? Thank you.
regards,
zl

Hi,
Please check if the service is activated.
Transaction SICF.
Hierarchy Type: Service and execute it.
default_host-> sap-> bc-> webdynpro-> sap-> dswp_earlywatch_admin check if this is activated, If it snsot activated, activate it and test the service by using right mouse option. While testing the service it will ask for a userid and password, enter your user id and password. and login it should allow you to login and check the service successfully.
If you are not able to login due to authorization issues, please use transaction SU53, there you will find any missing authorizations. After you add those authorization objects you should be successfully open the service.
If possible perform the IMG activity SAP Solution Manager-> Basic Settings-> HTTP Services-> Activate Solution Manager service.
Hope this helps.
Thanks & Best Regards,
Raghavendra.

Similar Messages

SOLMAN_WORKCENTER Service cannot be reached ... Help

Helo Gurus,
I have problem runing T-Code solman_workcenter, after starting this transacion appear screen with info :
Service cannot be reached
What has happened?
URL http://<server>:8077/sap/bc/webdynpro/sap/ags_workcenter call was terminated because the corresponding service is not available.
Note
The termination occurred in system SSM with error code 403 and for the reason Forbidden.
The selected virtual host was 0 .
What can I do?
Please select a valid URL.
If you do not yet have a user ID, contact your system administrator.
ErrorCode:ICF-NF-http-c:000-u:SAPSYS-l:E-i:sap-dev_SSM_77-v:0-s:403-r:Forbidden
HTTP 403 - Forbidden
Your SAP Internet Communication Framework Team
I have on my server installed :
SAP Solution Manager 7.0
SAP_BASIS     700     0016     SAPKB70016     SAP Basis Component
SAP_ABA     700     0016     SAPKA70016     Cross-Application Component
PI_BASIS     2006_1_700     0006     SAPKIPYM06     Basis Plug-In (PI_BASIS) 2006_1_700
ST-PI     2005_1_700     0006     SAPKITLQI6     SAP Solution Tools Plug-In
SAP_BW     700     0018     SAPKW70018     SAP NetWeaver BI 7.0
SAP_AP     700     0014     SAPKNA7014     SAP Application Platform
BBPCRM     500     0012     SAPKU50012     BBPCRM
CPRXRPM     400     0013     SAPK-40013INCPRXRPM     SAP xRPM/cProjects/cFolders 4.00 (ABAP)
ST     400     0017     SAPKITL427     SAP Solution Manager Tool
ST-A/PI     01J_CRM500     0000          -     Application Servicetools for CRM 500 / 5
ST-ICO     150_700     0011     SAPK-1507BINSTPL     SAP Solution Manager Implementation Cont
ST-SER     700_2008_1     0005     SAPKITLOO5     SAP Solution Manager Service Tools
ags_workcenter SAP Solution Manager Work Centers is Activated (no extra configuration just Activated)
My login has role sap_all and sap_new.
Where is error, what iam missing ?
Please help,
Regards

Hi
Check these services are active
/sap/bc/webdynpro/sap/ags_work_incident_man
/sap/bc/webdynpro/sap/ags_workcenter
/sap/bc/ags_workcenter/ags_work_appln
/sap/bc/ags_workcenter/ags_work_webgui
/sap/bc/webdynpro/sap/ags_work_trans_print
/sap/bc/webdynpro/sap/ags_work_incident_create_app
/sap/bc/webdynpro/sap/ags_work_change_man
/sap/bc/webdynpro/sap/ags_work_setup
/sap/bc/webdynpro/sap/ags_work_job_sch_man
/sap/bc/webdynpro/sap/ags_work_implementation
/sap/bc/webdynpro/sap/ags_work_bp_iterf_mon
/sap/bc/webdynpro/sap/ags_work_services
/sap/bc/webdynpro/sap/ags_rbe
/sap/bc/solman/nwbc/solmanwork
/sap/bc/webdynpro/sap/ags_work_gui_selection
/sap/bc/dal/demoA
/sap/bc/webdynpro/sap/wdc_wba_rfc_monitoring
/sap/bc/bsp/sap/wba_start_smdia
/sap/bc/webdynpro/sap/ags_work_gui_default_set
There is one work center role per work center, and the user needs the role SAP_SMWORK_BASIC, which contains the authorization objects required for the work center
SAP note 834534
Also check these roles
SAP_SUPPDESK_CREATE
SAP_SMWORK_INCIDENT_MAN
SAP_SMWORK_BASIC
Regards
Uday

SSO to BI - Service Cannot Be Reached Error

Hi All-
I'm working on integrating BI and EP (both Netweaver 7). We've exported/imported the certificates for both systems and defined the BI system in the System Landscape of EP. All connection tests return OK.
I created an iView using the iView template for "BEx Web Application iView (SAP NetWeaver 7.0 Format)", assigned the alias of the BI system created, and added the BEx query string.
When I preview this iView, I get the error:
"Service cannot be reached",
What has happened?
URL
http://<domain>.com/irj/servlet/prt/portal/prtmode/preview/prtroot/com.sap.ip.bi.web.portal.integration.launcher call was terminated because the corresponding service is not available.
However, if I switch the iView property for Version to "BW 2.x/3.x", then I can connect to the report, but it opens to the variable screen.
Any ideas on how to correct the service cannot be reached error?
Thanks

Dear Tim,
A couple of things you might want to look at.
1. In the system that you have created for BI, ensure that you have
a. ITS Path : /sap/bc/gui/sap/its/webgui
b. Web AS Path : /sap/bw/BEx
Also for the hostnames, ITS and WebAS a FQDN is given followed by the portnumber.
2. In the system where your BI resides, go to transaction SICF and ensure this patch under
default_host : /sap/bc/gui/sap/its/webgui is active and
default_host : /sap/bw/BEx is active as well.
To ensure it is active, just do a right click and activate it, if it already active, you can deactive it and active it again and test.
Cheers!
Sandeep Tudumu

Service cannot be reached while sending a smart form in html format

Hello,
I'm trying to send a smart form as email in html format and I'm getting the following error message at the beginning of the message:
Service cannot be reached
What has happened?
URL http://localhost/SAP/BC/BSP/SAP/SMART_FORMS/DEFAULT.CSS call was terminated because the corresponding service is not available.
Note
The termination occurred in system XD1 with error code 403 and for the reason Forbidden.
The selected virtual host was 0 .
What can I do?
Please select a valid URL.
If you do not yet have a user ID, contact your system administrator.
Error code:ICF-NF-http-c:100-u:MYUSER-l:D-i:my_test_system:0-s:403-r:Forbidden
HTTP 403 - Forbidden
Your SAP Internet Communication Framework Team
.SYSTEM div#B.par{ font-family : "Courier New" ; font-size : 12pt ; font-weight : normal ; line-height : 4.23mm ; text-decoration : none ; text-align : justify ; clear : both ;}.SYSTEM div#L.par{ font-family : "Courier New" ; font-size : 12pt ; font-weight : normal ; line-height : 4.23mm ; text-decoration : none ; text-align : left ; clear : both ;}.SYSTEM a.SYSTEM span#H.char{ font-weight : bold ;}.SYSTEM span#I.char{ font-style : italic ;}.SYSTEM span#U.char{ text-decoration : underline ;}#PAGE1-001.page@media screen {#MAIN.win{ overflow : auto ;}}@media print {#MAIN.win{ overflow : hidden ;}}#PAGE1-001.page #MAIN.win.AGGR-BILL div#B.par{ font-family : "Arial" ; font-size : 12pt ; font-weight : normal ; line-height : 4.23mm ; text-decoration : none ; text-align : justify ; clear : both ;}.AGGR-BILL div#F.par{ font-family : "Arial" ; font-size : 8pt ; font-weight : normal ; line-height : 3.39mm ; text-decoration : none ; text-align : left ; clear : both ;}.AGGR-BILL div#L.par{ font-family : "Arial" ; font-size : 12pt ; font-weight : normal ; line-height : 4.23mm ; text-decoration : none ; text-align : left ; clear : both ;}.AGGR-BILL div#R.par{ font-family : "Arial" ; font-size : 12pt ; font-weight : normal ; line-height : 4.23mm ; text-decoration : none ; text-align : right ; clear : both ;}.AGGR-BILL a.AGGR-BILL span#H.char{ font-family : "Arial" ; font-size : 12pt ; font-weight : bold ;}.AGGR-BILL span#I.char{ font-family : "Arial" ; font-size : 12pt ; font-style : italic ;}.AGGR-BILL span#K.char{ font-family : "Arial" ; font-size : 8pt ;}.AGGR-BILL span#M.char{ font-family : "Arial" ; font-size : 10pt ;}.AGGR-BILL span#U.char{ font-family : "Arial" ; font-size : 12pt ; text-decoration : underline ;} div#PROJEKTE.tab@media screen { div#PROJEKTE.tab table.tr{ border-collapse : collapse ;}}@media print { div#PROJEKTE.tab table.tr{ border-collapse : collapse ;}}@media screen { div#PROJEKTE.tab table.tr{ margin-top : -1px ;}}@media print { div#PROJEKTE.tab table.tr{ margin-top : 0px ;}} div#PROJEKTE.tab table.tr div#PROJEKTE.tab .topline{ border-top : 1pt solid black ;} div#PROJEKTE.tab .bottomline{ border-bottom : 1pt solid black ;} div#PROJEKTE.tab .leftline{ border-left : 1pt solid black ;} div#PROJEKTE.tab .rightline{ border-right : 1pt solid black ;}#PROJEKTE.tab #sf--LTYPE1.tr td#C1
and here comes the email's body: bla,bla,bla... bla.
Do you have any idea how can I solve the problem with the css file? Any suggestion is welcome!
Regards,
Jaime

I just solved the problem by activating the service /SAP/BC/BSP/SAP/smart_forms/ through the transaction SICF. So I close the thread!
Jaime

Integrated Planning Service cannot be reached

Hi Experts,
I am having an issue in opening the planning modeller. Once i click on start modeller on transaction RSPLAN, i get the following error.
Service cannot be reached
What has happened?
URL http://imtsapm01.massap.corp.pri:8000/sap/public/myssocntl call was terminated because the corresponding service is not available.
Note
The termination occurred in system PP1 with error code 403 and for the reason Forbidden.
The selected virtual host was 0 .
What can I do?
Please select a valid URL.
If you do not yet have a user ID, contact your system administrator.
ErrorCode:ICF-NF-http-c:000-u:SAPSYS-l:E-i:imtsapm01_PP1_00-v:0-s:403-r:Forbidden
HTTP 403 - Forbidden
Your SAP Internet Communication Framework Team
BI reporting works fine without any issue. Not sure why this doesnt work. is there some special service which needs to be activated for integrated planning? I am running BI-7 and BI and portals are hosted on the same machine. I have done all the connection tests and there is no error on the system.
Would appreciate you're help.
thanks and regards
dilanke

Hi,
Please check the following things:
1. Check whether the necessary services are active. You can check this using SICF transaction. If its inactive, please activate.
2. Check if the BI server is properly connected to the Intergrated Planning portal.
3. Check if you have added the URL in internet explorer connections settings. Open internert explorer -> Internet options-> Connections-> LAN settings -> Advanced -> Exceptions. Check if you url is added here.
4. Check the drivers settings. Go to run -> drivers-> etc (folder name) ->host (file name). Open this host file as notepad and check if the BI server id and url is added here.
If all the above steps are correct, the IP portal should work correctly.
Thanks.
Regards.

Server Cannot be reached error

Hi All,
While executing test bsp application, i am getting the following error on browser.
<b>Service cannot be reached
What has happened?
URL http://server.sairam.com:8000/sap/bc/bsp/sap/zjvs_bsp/page1.htm call was terminated because the corresponding service is not available.
Note
The termination occurred in system XII with error code 403 and for the reason Forbidden.
The selected virtual host was 0 .
What can I do?
Please select a valid URL.
If you do not yet have a user ID, contact your system administrator.
ErrorCode:ICF-NF-http-c:000-u:SAPSYS-l:E-i:server_XII_00-v:0-s:403-r:Forbidden
HTTP 403 - Forbidden
Your SAP Internet Communication Framework Team</b>
Can anyone help me in rectifying this problem?
regards,
sundaram J

Hi Sundaram,
Please go to transaction SICF and check the Vir.Hosts/Service .
I believe is service is not active. Please try to activate by right clicking on the Default_host. Let me know if its already activated.
Regards,
Shailaja

Service cannot able to open in UWL from the ESS tasks

Hi Team,
I'm facing a issue like
path: MSS --> work overview --> tasks --> click on any link.
we got the following error.
Service cannot be reached
What has happened?
URL http://<hostname>:8001/webdynpro/dispatcher/sap.com/ess~lea/LeaveRequestApprover call was terminated because the corresponding service is not available.
Note
The termination occurred in system GCP with error code 404 and for the reason Not found.
The selected virtual host was 0 .
What can I do?
Please select a valid URL.
If you do not yet have a user ID, contact your system administrator.
ErrorCode:ICF-NF-http-c:000-u:SAPSYS-l:E-i:gccia-erpn01_GCP_01-v:0-s:404-r:Notfound
HTTP 404 - Not found
Your SAP Internet Communication Framework Team
I have check forum thread
Service cannot be reached in UWL from the ESS tasks
but I'm not able to find out the solution.
Any help will be appriciated.
Regards,
Mahee.

i said to you that it shouldnt point to ABAP system!
read my solution again
Please ensure system configuration-
>system landscape->system(my system)->Web Application server settings
please check is it pointing to ABAP Server, If yes then change to Java
server then your Application will work.
The two types want different WAS properties. Now if you set
up the WAS so that the BSP works well. There is a possibility that you
can modify the WAS settings when you use WebDynpro launcher. You have
three possibilities to change this:
1. In the UWL connector settings modify the "Web Dynpro Launch System"
property to SAP_LocalSystem. This case the webdynpro uses the URL and
the port of the portal.>> I think this can suit you.
2. In the System Landscape create a new system with the same properties
as the R3_TEST1 but the WAS properties are different. After that you use
the name of the new system as "Web Dynpro Launch System" in the UWL
connector settings. This solution should be used if the SAP_LocalSystem
is different than the necessary WAS settings.
3. You can modify this setting in the configuration also under the
ItemType. You should add the system property and the UWL uses it instead
of the default one.
Here is the help documentation:
http://help.sap.com/saphelp_nw70/helpdata/en/92
/a88931f2dd4631b9e8d530697d89c9/content.htm
in regards to this parameter.

Proxy exposed as a web service but cannot be reached

Hello,
I've exposed a server proxy as a web service and it looks OK in WSADMIN and WSCONFIG, also a service is created in ICM. But when I test the service, the browser page that opens cannot be reached and if I try to send a message to the service, I get the error HTTP Error: Could not POST file.
What might be the cause?
Thanks,
Gökhan

I had an error in my implementation.. nothing serious.

Im trying to setup my phone and I Keep getting this error. "Your iPhone could not be activated because the activation server cannot be reached. Try Connecting your iPhone to iTunes to activate it, or try again later.

Im trying to setup my phone and I Keep getting this error.
"Your iPhone could not be activated because the activation server cannot be reached. Try Connecting your iPhone to iTunes to activate it, or try again later.

Are you running one of the beta versions of iOS 7?
Has the iPhone been jailbroken or modified to work with other
than the original wireless provider?

Iphone 6 screen broken. local authorized service center cannot be reached despite arranging for "schedule a call" session. pls help

iphone 6 screen broken. local authorized service center cannot be reached despite arranging for "schedule a call" session. pls help

They do not know where your phone is yet because it has not had enough time to go through the process yet. I also started to worry when two weeks had passed and my iPhone 5S was still showing not received on the status website. That's when I joined this forum to see if anyone else was having the same problem. What I found out was that some people had been given reduced value for their trade in, but I also found posts from people like myself that were worried that their phone was lost and then came back and posted a week or two later that they had received their gift card.
I decided to chill and give it some time and about a week later my gift card arrived. If it had been for less than the promised amount I would no doubt still be upset and posting about it like the many posts I still see on here on a regular basis.
This is no doubt a popular program for Verizon. I would imagine there have been thousands of phones traded in. There are going to be at least some screw ups in the process. There is no point in getting ahead of yourself and assuming your case will be one of the screw ups unless it already is. Verizon has been consistently posting that it could take 4-6 weeks for processing. You will at some point likely hear the status on your traded-in phone. Patience would not hurt in this case.

IDOC to abap proxy- Receiver Service Cannot be converted into ALE logical

Dear all,
I have idoc to abap proxy -
R3 to SRM scenario.
I am getting the error Receiver service cannot be converted to ale logical system.
I have check the receiver bs SRM_BS , adapter specific attributes ... im getting the logical system ( this is not the problem)
i am using receiver XI adapter
with XI 3.0 as protocol
and http destination with /sap/xi/engine?type = receiver
i can see the data in the moni of receiver SRM system but it shows a red flag
pls help

Hi kiran,
i have checked all the RFC destinations ... seems OK
problem is in SRM moni .. sender service and sender interface are not visible.
trace ::::
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST" />
- 
<Trace level="1" type="T">XMB was called with URL /sap/xi/engine/?type=entry</Trace>
<Trace level="1" type="T">COMMIT is done by XMB !</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />
- 
<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">XMB entry processing</Trace>
<Trace level="1" type="T">system-ID = SR5</Trace>
<Trace level="1" type="T">client = 300</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = RFCADMIN_SR5</Trace>
<Trace level="1" type="Timestamp">2008-06-01T16:27:03Z CET</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
- 
<Trace level="1" type="T">Message-GUID = DD2FF717DAE395F186DF001560A1C7CB</Trace>
<Trace level="1" type="T">PLNAME = RECEIVER</Trace>
<Trace level="1" type="T">QOS = EO</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline = RECEIVER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Get definition of internal pipeline = SAP_RECEIVER</Trace>
<Trace level="1" type="T">Queue name : XBTR0003</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTR0003</Trace>
<Trace level="1" type="T">Schedule message in qRFC environment</Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Going to persist message</Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
<Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="T">--start sender interface action determination</Trace>
<Trace level="1" type="T">select interface *</Trace>
<Trace level="1" type="T">select interface namespace</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--start receiver interface action determination</Trace>
<Trace level="1" type="T">Loop 0000000001</Trace>
<Trace level="1" type="T">select interface SupplierPortalTradingPartner_CreateOrChange_In*</Trace>
<Trace level="1" type="T">select interface namespace http://sap.com/xi/SRM/SupplierEnablement</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--no sender or receiver interface definition found</Trace>
<Trace level="1" type="T">Hence set action to DEL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- 
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline RECEIVER</Trace>
<Trace level="1" type="T">system-ID = SR5</Trace>
<Trace level="1" type="T">client = 300</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = RFCADMIN_SR5</Trace>
<Trace level="1" type="Timestamp">2008-06-01T16:27:04Z CET</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline RECEIVER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Corresponding internal pipeline SAP_RECEIVER</Trace>
<Trace level="1" type="B" name="PLSRV_CALL_INBOUND_PROXY" />
- 
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- 
<Trace level="1" type="B" name="Inbound Framework" />
- 
- <asx:abap xmlns:asx="http://www.sap.com/abapxml" version="1.0">
- <asx:values>
<CX_ERROR href="#o3314" />
</asx:values>
- <asx:heap xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:abap="http://www.sap.com/abapxml/types/built-in" xmlns:cls="http://www.sap.com/abapxml/classes/global" xmlns:dic="http://www.sap.com/abapxml/types/dictionary">
- <cls:CX_SY_NO_HANDLER id="o3314">
- <CX_ROOT>
<TEXTID>1F09B73915F6B645E10000000A11447B</TEXTID>
<PREVIOUS href="#o3313" />
<KERNEL_ERRID>UNCAUGHT_EXCEPTION</KERNEL_ERRID>
- <INTERNAL_SOURCE_POS>
<PROGID>496</PROGID>
<CONTID>1564</CONTID>
</INTERNAL_SOURCE_POS>
</CX_ROOT>
<CX_NO_CHECK />
- <CX_SY_NO_HANDLER>
<CLASSNAME>CX_BBPX1_STD_MESSAGE_FAULT</CLASSNAME>
</CX_SY_NO_HANDLER>
</cls:CX_SY_NO_HANDLER>
- <cls:CX_BBPX1_STD_MESSAGE_FAULT id="o3313">
- <CX_ROOT>
<TEXTID>65B8FEB5F43CC949B7CD662AB888ED34</TEXTID>
<PREVIOUS />
<KERNEL_ERRID />
- <INTERNAL_SOURCE_POS>
<PROGID>496</PROGID>
<CONTID>1738</CONTID>
</INTERNAL_SOURCE_POS>
</CX_ROOT>
<CX_DYNAMIC_CHECK />
<CX_AI_APPLICATION_FAULT />
- <CX_BBPX1_STD_MESSAGE_FAULT>
<AUTOMATIC_RETRY />
<CONTROLLER />
<NO_RETRY />
- <STANDARD>
<CONTROLLER />
<FAULT_TEXT>An error occured within an XI interface: Exception occurredE:BBP_BUPA_SUPPLIER:089 -Unable to determine logical system of sender; check your data Programm: CX_BBP_BD_ERROR===============CP; Include: CX_BBP_BD_ERROR===============CM002; Line: 57</FAULT_TEXT>
<FAULT_URL />
<FAULT_DETAIL />
</STANDARD>
</CX_BBPX1_STD_MESSAGE_FAULT>
</cls:CX_BBPX1_STD_MESSAGE_FAULT>
</asx:heap>
</asx:abap>
</Trace>
<Trace level="1" type="T">System Error at Receiver... => ROLLBACK WORK</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="System_Error">Error exception return from pipeline processing!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
</SAP:Trace>
fault message says the sender is not having logical sys...but my sender sys is showing logical system in adapter specific attributes
pls help
points will be awarded

Waiting for the service MSExchangeMailboxAssistants to reach status Running

I have to say that the installation of Exchange Server 2013 SP1 has been an emotional experience so far. I have encountered and fixed approximately 20 errors so far and can still not complete the installation. Errors have ranged from adding a registry
key for "Pickup" to toggling IPv6 settings etc. The errors haven't been too bad up to now as they're clearly stated in both the setup log and event viewer. A quick Google search usually gives a few solutions to try and eventually fix
the problem.
My recent error has been difficult to find a solution to as the setup log simply says it cannot start the "MSExchangeMailboxAssistants" service. I have tried to start the service manually but the event log doesn't show any messages relating
to the stopping of the service.
Error:
Service 'MSExchangeMailboxAssistants' failed to reach status 'Running' on this server.
Platform:
Windows Server 2012 R2
Exchange Server 2013 SP1
Things I've tried:
Starting all Exchange services. All are working fine.
Started MSExchangeMailboxAssistants. Stopped immediately without an errors in event log.
Started MSExchangeMailboxAssistants.exe from command prompt. Wouldn't start as it's a service.
Used cmdlet to increase logging level to "high" and "expert" for all 'MSExchangeMailboxAssistants' services. Started service again and nothing logged.
Installed Operations Manager. Nothing logged.
Manually removed Exchange from server several times and reinstalled. Cleaned out AD, registry, files, IIS etc. No change, same error.
Try installing with and without Malware Protection.
Checked IPv6 is enabled on all NICs.
Checked registry settings for quotes around file name. It does contain the quotes so nothing to fix.
Checked Exchange 2013 SP1 is compatible with Windows Server 2012 R2. The original version wasn't but SP1 is.
I'm all out of ideas now and no error message in the logs to google.
Any help would be appreciated.

Thank you for your reply Exchange Shelly, I really appreciate your help.
Unfortunately, "MSExchangeTransport" failing to start was one of the many issues that I encountered during the installation of Exchange 2013 SP1 on Windows 2012 R2. I had already visited the website mentioned above (which was very helpful) and
the registry key is already in place.
I did double check the registry after reading your reply just in case and can confirm it's definitely there.
If I could get an error message when the MSExchangeMailboxAssistants service fails to start, I would have a fighting chance. I've tried increasing the logging level using the cmdlet and the registry but still not seeing anything in the Event Log.

Invalid Credentials: The Network location cannot be reached

I am working with MDT 2010, and I am getting the error, "Invalid Credentials: The Network location cannot be reached." When I run the LiteTouch 64 bit, I don't think the network is working. It's like there is not driver for the network card in
the LiteTouch 64 bit to make the network connection. When I hit F8 key, it brings a DOS box up for testing, and I found out these things.
- I can ping the loop back address 127.0.0.1.
- Cannot use the net use command to connect to the server share \\server01\DeploymentSahre$.
- I can not ping by name or IP address the server that is holding my Deployment Share.
This is the first time I am working with this technology, and I was following a guide off the Technet library. It almost like I am missing the driver for the network card. I have Windows Deployment installed on server01, the server will answer,
and I am able to put in my user name and password, it accepts and starts loading.
I did figure out how to inject the network drivers into Windows Deployment for the Motherboard I was using, do I have to do the same thing here again? MDT is using the Windows Deployment Images on the server01; MDT is setup on server01. I would have
thought that since the driver was already injected into the Image MDT would use that as well. So, do I need to put a driver into the LiteTouch 64bit image and if I do how do I do that?
thanks very much for your help,
Rick Arnold
ArnoldConsult
Rick Arnold Arnoldconsult, MCP

If you haven't updated the deployment share after adding the proper drivers to OOBD then your LiteTouch boot images will not have them included. Just right click the deployment share and click on Update Deployment Share, it will take a while but it
will rebuild the boot images with the drivers you've included in OOBD. Then it's just a matter of either recreating the flash drives or loading the updated image into WDS.
Another thought:
We had an issue with some HP's that had Main Boards replaced. the BIOS time was WAY off and the UUID wasn't setting itself because the network was denying it access to our servers (because of the horribly wrong time). Once we corrected the time
in the BIOS everything ran fine. The error we got while trying to do the deployment was the same as what you describe and we could still ping various machines on the network too.

Control Framework: Fatal error - GUI cannot be reached

Hello All,
Iam using BDC for creating a ZCR order throught VA01 - Credit Memo request. When executed in the foreground, it works fine.But when ran in background gives an error message - Control Framework: Fatal error - GUI cannot be reached and gives a short Dump for 'RAISE_EXCEPTION'.
Please suggest.

Normally, BDC should run the same way whether it is in background of Foreground.
No, BDC does not run the same way in background and foreground
To understand BDC in background : different behavior or termination read those OSS notes :
- [Note 33319 - Batch input: Backgr. runs diff. than in the dialog|https://service.sap.com/sap/support/notes/33319]
- [Note 311440 - Batch input and controls|https://service.sap.com/sap/support/notes/311440]
Also this note of interest :
- [Note 554139 - FAQ 2: Batch input|https://service.sap.com/sap/support/notes/554139]
Regards,
Raymond

What's wrong with the activation server? i just bought my ipad wifi celllular... and have a 3g cellular network connection... when i press the bottom to activate my ipad it says the activation server cannot be reached. what to do then?

what's wrong with the activation server? i just bought my ipad wifi celllular... and have a 3g cellular network connection... when i press the bottom to activate my ipad it says the activation server cannot be reached. what to do then?

Hey aries35,
I found the following that goes over troubleshooting the same issue for the iPhone. I know you have an iPad, but the steps should still apply:
Perform the following steps:
Restart the iPhone.
Try another means of reaching the activation server and attempt to activate.
Try connecting to a known-good Wi-Fi network if you're unable to activate using a cellular data connection.
Try connecting to iTunes if you're unable to activate using Wi-Fi.
Restore the iPhone.
If you receive an alert message when you attempt to activate your iPhone, try to place the iPhone in recovery mode and perform a restore. If you're still unable to complete the setup assistant due to an activation error, contact Apple for assistance.
via: iPhone: Troubleshooting activation issues
http://support.apple.com/kb/TS3424
Cheers,
Delgadoh

Setup EWA in Solman - Service Cannot be Reached

Similar Messages

Maybe you are looking for