IPad issue when connecting to external server on 8.81 PL03

Question

This thread is split off from "Extenally connection for the i-phone or i-pad. "
The issue is that the iPad fails to connect to an external server, while it did so successfully to a server on an ad hoc network setup.
In Integration Framework page -> Monitoring -> Authent. Monitor I only see feedback on the sap.Xcelsius scenario - again it says the info is from 8080 (while B1mobile is on port 8443, since Enforce Secure Transport = True for sap.B1Mobile?)
The attemps by the iPad to login only shows in the B1authcheck log. I have confirmed the time stamps.
I compared this unsuccessful log entry to my successful ad hoc network's log entry and it seems to break here:
"#177765 --- 2011-03-26T11:58:14, millis=1301165894004
Level CONFIG
Logger com.sap.b1i.bizprocessor
Class/Method com.sap.b1i.bizprocessor.BPLogger, log
Thread 9422
BPC141 XSL-stylesheet to execute: bizstore:/com.sap.b1i.vplatform.scenarios.authen/sap.B1Mobile/Authenticate1.xsl
#177768 --- 2011-03-26T11:58:14, millis=1301165894004
Level INFO
Logger com.sap.b1i.dblayer
Class/Method com.sap.b1i.dblayer.DBLayer$DBConnection, logP
Thread 9422
DBL012 DBConn.#65 Did an explicit DB-Rollback at point java.lang.Throwable
at com.sap.b1i.dblayer.DBLayer$DBConnection.Rollback(DBLayer.java:215)..."
I have tried connecting both via 3G and with the iPad connected to local Wifi.
SAP is 8.81 PL3 with the B1iC that ships with the patch. The iPad is running the 1.1.1 app.  Secure Transport is enforced (i.e. SSL is ON and port 8443 is in use)
Any insight will be appreciated!
Edited by: Maria Trinidad MARTINEZ GEA on Mar 28, 2011 2:38 PM

Answer 1

Hi Frank,
The SQL password was in the format Xxxxxx! - with '!' being the offending character.
As a consequence of changing the password, I had to reinstall B1iC (I could not figure out how to get it to use the new password otherwise).  Given that I reinstalled B1iC a few times in the preceding 20 hours' process of elimination, I don't think the reinstallation itself triggered sap.B1mobile into suddenly working.
Which leaves me to conclude that it was the '!' in the SQL sa password.
I am glad to hear that it supports special characters (elsewhere) now
I'd like to suggest to anybody having problems to install it in as simple an environment as possible, and to add layers of complexity (firewalls, special characters, etc.) only after you get it working.  There is little documentation for this process, which makes it challenging to troubleshoot from the top down.