cancel
Showing results for 
Search instead for 
Did you mean: 

iPad issue when connecting to external server on 8.81 PL03

Former Member
0 Kudos

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

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

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.

former_member185703
Active Contributor
0 Kudos

Hi Eugene,

Thanks a lot for your response - I will double-check...

...and right:

There should be specific documentation how to make B1i aware of changed DB or B1 user "B1i" passwords all-over!

Beyond that it sounds like the "Troubleshooting Guide" here on SDN wasn't really helpful for you?

Thx,

Frank

Former Member
0 Kudos

The troubleshooting guide was great back when I had to get the dashboards working in 8.8, but confused me somewhat when going to 8.81, as some things had changed and were no longer relevant.

It was of some use for troubleshooting the mobile scenario, but not much.

Perhaps post an updated, separate troubleshooting guide for the 8.81 B1iC?

former_member185703
Active Contributor
0 Kudos

FYI1: Lisa is working on an update for 8.81...

FYI2: ...and more guidance regarding setup of the Mobile solution is being worked on too...

Trinidad
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Eugene,

I'm happy to hear it works now ;o)

Thanks for the feedback, it is very important for everybody in order to have it fixed as soon as possible

Best Regards,

Trinidad.

Former Member
0 Kudos

It now works - after removing a special character from the sa SQL password and updating all components as appropriate to use the updated password.

Moral of the story: B1i does not like special characters in any password it processes!

former_member185703
Active Contributor
0 Kudos

Hi Eugene,

I am afraid your last statement is "immoral"

Issues with special characters were known in the initial version of B1iC (PL00) last June; they were (supposed to be) fixed (and tested) with PL01 + are ever since B1 8.81 was available.

I would be curious to knwo which special character you used - and maybe whether it was at the beginning, in the middle or at the end.

Other than that:

B1i supports using special characters for passwords (B1i, DB, B1); anything else is a bug.

Thanks,

Frank