Originally Posted by sergeyd
The policy is invoiked only if the app has done the connection both ways after the reload. Seem there is an issue with this app and the config you have.
The application (or BlackBerry) gives you just enough rope to hang yourself by in this scenario.
There are three settings for the Network Connection:
Device TCP: Originate the network connection on the device and go over public networks
MDS: Originate the network connection from the MDS server
Device Default: Whatever the carrier deemed the most appropriate setting to be. This is the default Ramble setting.
If you try any combination of Device TCP and MDS, you will get the split pipe error, even if the first connection fails. Here is one scenario:
Initial Setting is Device Default which is Device TCP in this example. You try connecting, it fails.
You change the setting to Read Device TCP, you try connecting, and it fails.
Now you set it to MDS, it fails to connect, and gives you the Split Pipe error because the application has now tried to open a connection inside the firewall, and at one point, it tried opening a connection outside the firewall. This is not allowed by BlackBerry.
Does this help explain how you might be getting a split pipe error on a 'fresh blackberry'?
If not, try having the administrator temporarily disable the 'Split Pipe' security in the IT Policy. This is not a long term solution, but it should get you past the problem.
If you're dealing with an administrator though, I suspect you should clean the device, set the Network Connection to MDS, and leave it there. Please let me know how it goes. If there is a problem that others have not run into, I'd like to resolve it.
Thanks for trying to use Ramble!