COGNOiSe.com - The IBM Cognos Community

IBM Cognos 8 Platform => COGNOS 8 => Report Studio => Topic started by: rashmi.cognos on 25 Jun 2015 08:58:07 AM

Title: prompt issue in report studio
Post by: rashmi.cognos on 25 Jun 2015 08:58:07 AM
Hi,
Some of the users who create their report are getting issue suddenly in report studio with prompts. When they try to validate a query by generating tabular data or try to generate SQL for a query, they get prompts but after applying values in the prompts, they get permission denied error while submitting. They do have report author access. I as an admin do not get this error. Users are getting in all reports. browser is IE8. Cognos version is 8.4.

Details of the error is in attachment. Any guidance is appreciated as this is a production server issue.
Title: Re: prompt issue in report studio
Post by: cognostechie on 25 Jun 2015 11:46:03 AM
Was anything changed/updated on the server like javascript or any other application? Have you checked the browser compatibility?
Title: Re: prompt issue in report studio
Post by: rashmi.cognos on 26 Jun 2015 12:22:49 AM
No, I checked many files in prompting folder...webcontent\prompting...
dates of the file seem to be very old...dated back to 2009
Title: Re: prompt issue in report studio
Post by: rashmi.cognos on 26 Jun 2015 12:26:18 AM
cognostechie, thankyou for the response

where  and which files should I check on the servers...
Title: Re: prompt issue in report studio
Post by: cognostechie on 26 Jun 2015 10:44:28 AM
Rashmi - It seems to be denying access to the javascript files in that folder which is shown in the error message. Can you check the permissions of that folder on your Cognos app server ? Files dating to 2009 may be ok because that may be the last time that file was modified. Those are source code files. These kind of things usually happen after an upgrade of something. 
Title: Re: prompt issue in report studio
Post by: rashmi.cognos on 03 Jul 2015 04:18:05 AM
Thanks Cognostechie. What kind of permission should I check for? I think, if it is at application server, permissions should already be restricted to admins?