If you are unable to create a new account, please email support@bspsoftware.com

 

News:

MetaManager - Administrative Tools for IBM Cognos
Pricing starting at $2,100
Download Now    Learn More

Main Menu

Server Error Code: 1160 - Mobile App - Running Any Report

Started by Northern_Monkey, 11 Feb 2014 02:11:56 AM

Previous topic - Next topic

Northern_Monkey

Any help would gratefully be appreciated...

I have tried a few different version of Cognos Mobile, 10.2.1.1 and 10.2.1.2 and I keep getting the same error.
(Server setup, App Tier, Gateway, Mobile, FM all on one box. Version, 10.2.1 with FP2)

I just cannot get any reports to run on mobile devices when trying it via the APP or the Mobile URL (HTTP://Server/ibmcognos/m).

App returns an error saying:
Server Error
Contact your administrator for assistance (code: 1160)


Mobile URL returns an error saying:
HTTP://Server
Sorry! The following error occurred while making your request:
Unexpected exception while running handle (code 1160)


The report works fine in using the full URL in Safari. The report is also very basic, no prompts, no html, just a chart!

I can't for the life of me work out what's going on!

MFGF

Hi,

Do you get the same error if you use the mobile URL in Safari on your PC and run the report? Knowing that answer will help determine whether it's an issue with Mobile generally or an issue with how your mobile devices are connecting...

MF.
Meep!

Northern_Monkey

The report runs fine when run from the URL!

Have set the mobile logging to debug levels..

Have the following errors in the log file:

2014-02-11 12:06:25,597 [mob-worker-1] ERROR com.cognos.mobile.server.html.HTMLResourceHandler - parser failure
2014-02-11 12:06:25,597 [mob-worker-1] ERROR com.cognos.mobile.server.runner.RegularReportRunner - failed to compile report - /Public Folders/Incidents by Cause
2014-02-11 12:06:26,066 [mob-worker-2] ERROR com.cognos.mobile.server.html.HTMLResourceHandler - parser failure
2014-02-11 12:06:26,066 [mob-worker-2] ERROR com.cognos.mobile.server.runner.RegularReportRunner - failed to compile report - /Public Folders/Incidents by Cause
2014-02-11 12:06:26,644 [mob-worker-1] ERROR com.cognos.mobile.server.html.HTMLResourceHandler - parser failure
2014-02-11 12:06:26,644 [mob-worker-1] ERROR com.cognos.mobile.server.runnable.RunReportRunnable - failed to run report: /content/folder[@name='Mobile']/report[@name='Incidents by Cause']
2014-02-11 12:06:26,800 [mob-worker-2] ERROR com.cognos.mobile.server.html.HTMLResourceHandler - parser failure
2014-02-11 12:06:26,800 [mob-worker-2] ERROR com.cognos.mobile.server.runnable.RunReportRunnable - failed to run report: /content/folder[@name='Mobile']/report[@name='Incidents by Cause']
2014-02-11 12:06:26,909 [http-9300-11] ERROR com.cognos.mobile.server.bus.MobileController - completed operation 'report' with error:
2014-02-11 12:06:26,925 [http-9300-11] ERROR com.cognos.mobile.server.bus.MobileService - (no message)

etc etc

Any ideas?

MFGF

Hi,

If it works fine using the mobile URL from Safari on your server then it looks like it's a connectivity issue between your server and mobile devices. Is your CAF enabled? You could perhaps see if this is interfering by temporarily disabling CAF and restarting your IBM Cognos service.

Failing that, I'd suggest you log this with IBM support. They will probably ask for your mob.log file from the server, and your iPad app log file.

MF.
Meep!

Northern_Monkey

CAF enabled or disabled still causes the error.
Think it's time to raise a ticket with IBM!
Thanks

MFGF

Meep!

Northern_Monkey

Seems the issue lies with the connection to the gateway. IBM are looking in to this as the cutomer site curently uses IHS instead of IIS which has stumped them for ideas!

Grim

Quote from: Northern_Monkey on 14 Feb 2014 01:47:21 AM
Seems the issue lies with the connection to the gateway. IBM are looking in to this as the cutomer site curently uses IHS instead of IIS which has stumped them for ideas!
Very weird, shouldn't matter if it's IIS, IHS, or Apache. Are they using CGI, or mod?

Keep us posted on this. I'm very curious to know what the outcome is.
"Honorary Master of IBM Links"- MFGF
Certified IBM C8 & C10 Admin, Gamer, Geek and all around nice guy.
<-Applaud if my rant helped! 8)

Northern_Monkey

CGI....

Think we have fallen in to the IBM blackhole at present!

whogotdafunk

We've recently had one of our users run into the same issue here. We are running Cognos 10.2.1. FP1 with CAF disabled.

We had a bunch of other issues during go-live that IBM eventually fixed, but we thought we were done with mobile errors.

In our environment there is only a single gateway and a single dispatcher with mobile service running (2 additional dispatchers, but they don't have mobile service active, because that caused all sorts of other errors). IBM was very adamant that we ensure the mobile app is connecting using the same gateway URL as is used for the internal config of the app-tier, so we've got that covered.

Has anyone resolved this issue? We're also in the process of testing Mobile FP2 for 10.2.1 and we've seen this same error there as well.

Thanks for any insight! Daniel

tmathew81

Same issue happens over here after Mobile FP2 had been applied. IBM has stated that I should try to roll back the FP2 installation and then re-install, but use installation files through Download Director, not the standard http download method.

I haven't done this yet, but am wondering if anyone has come across a resolution for this.

Thanks,
Tom

pavel.gneushev

Hello!

I have same error when I try run report in mobile URL.
I create empty report in Report Studio with only one textbox:"Hello, World!". Next I run it in Web Url - It's OK, but if I run this report in mobile URL I getting error "unexpected exception while running handler (code 1160)"

Can you help me?

Thanks!

shelby435

Was there ever any resolution to this?

We had the same issue after we set the mobile logs to debug.

I cant even push the active report to the iPad either.

raghu88

Hi,

Im getting same error. did you get any solution.

Thanks,
Raghu

Northern_Monkey

This was never resolved. I ended up forcing the users to use the mobile URL instead of the app.