Hi @all,
I am trying to install the Timesheet App in the following landscape: SAP ECC 6.0; SUP 2.1.3; Gateway 2.0 SPS02; mobile device: iPhone 4 iOS version 6.0.
During the installation and configuration I followed the document "Administrator's Guide SAP Timesheet 2.3", I do also the business customizing at the backend system.
After the work is done I jabbed the connection data into the Timesheet app of mobile device. The registration could be established, but the protocol shows the following error:
****************************************************************************************************************
SAP Timesheet LOGS / 2.3.5 2013-04-02 15:10:18 +0000 Device:iPhone 4 iOS version: 6.0
| Level = 4 | Time = 02.04.2013 17:09:57 | TimeNanoSec = 795102000 | Message = Application windows are expected to have a root view controller at the end of application launch
| Level = 4 | Time = 02.04.2013 17:08:40 | TimeNanoSec = 711760000 | Message = [ERROR] (null):Empty URL Passed/Location:-[SUPRequest startSynchronous] + 1021
| Level = 4 | Time = 02.04.2013 17:08:09 | TimeNanoSec = 723596000 | Message = [ERROR] (null):Empty URL Passed/Location:-[SUPRequest startSynchronous] + 1021
| Level = 4 | Time = 02.04.2013 17:07:50 | TimeNanoSec = 884643000 | Message = [ERROR] (null):Empty URL Passed/Location:-[SUPRequest startSynchronous] + 1021
| Level = 4 | Time = 02.04.2013 17:07:40 | TimeNanoSec = 19392000 | Message = Application windows are expected to have a root view controller at the end of application launch
****************************************************************************************************************
What does that error say? Is there a problem with the connection between SUP and Gateway? I tested the SUP domain connection for the proxy connection. I used the default domain and the basic security:
com.sap.meps.timesheetentry_default_Basic_proxy
The connection test to the endpoint via SUP, connection type proxy says: Endpoint test result: Unauthorized. Within the browser it's possible to call the wsdl of the endpoint.
Any idea how to fix that or what the real problem is? I turned all the logs upside down at Gateway and SUP but with no result.
Could an update of the Gateway component to SPS03 help?
Thanks,
Stefan