Print and save dialog not showing up on reports

We're having a problem where the print and save dialogs don't pop up on reports. The buttons show up at the top of the report but when the user clicks on the button the report quickly flashes "loading.." at the bottom but the windows dialogs never pop up. Has anyone seen this before? We're using Metastorm 9 SR 3.

Update:

We only get this problem when using SSO. If the user is an administrator on the local machine running the engine and the website then the dialogs work fine. Obviously we can't make every user an administrator on the machine. So it looks like a rights/permissions issue when using SSO. Anyone have any ideas where to look next?

Find more posts tagged with

BPM

Comments

Tony Tran

What IIS do you have?

If you use IIS 7, add user into group IIS_IUSRS. This group is a local group on IIS server that was created by IIS 7.

Best Practice: Create a BPM_User group on Domain. Add users to that group, and add BPM_User group to IIS_IUSRS group.

Good Luck.

Alex Mathew

Hi Thomas,

We are facing the same issue as you have mentioned. The dialog works with users having admin privileges but not for normal user. Were you able to resolve the issue you faced and how did you do it. We are using V9.1

Thanks,

Alex

Duncan_Baxter

We are experiencing this issue with 9.1 - does anyone have a fix for this as it is preventing users from analysing the data from our reports.

Thanks

Jacob_Eastman

I believe there was a previous post here that I resolved but an quick search and I'm not seeing it. Either way, here is the fix from my notes:

This occurs when you open a Report and click the Save or Print buttons. These generate a PDF either to download or to send to a printer. When using SSO, these buttons appear to do nothing. This will work properly if a non-SSO web client is used.

The issue is that a temp file is created when the PDF file is generated. If the file cannot be created, the PDF will not be generated. As SSO requires IIS impersonation, the temp file will be generated as the client's user instead of the App Pool's identity. As such, that user needs write access to the temp directory. While the IIS AppPool is running at High Integrity, when it impersonates a user it picks up that user's integrity level. As your users aren't elevated users on the server, UAC blocks them from modifying files in Program Files by default even if they have write permission.

The temp directory will be in one of two places depending on your setup:

C:\Program Files (x86)\Metastorm\BPM\Web\app_data\XtraReports\Filestore

C:\Windows\Microsoft.NET\Framework64\v2.0.50727\Temporary ASP.NET Files\metastorm\c59c8eb7\dc5ad27e\XtraReports\Filestore

***Note that this directory will not exist if a PDF has not been successfully generated. Login as a windows admin user and generate the PDF first if you haven't successfully generated a PDF.

To fix this for all users you will need to do the following

1)Add Write access for the BUILTIN\Users group to the "FileStore" directory. This will cover all of your users but you could give them individual permissions if you wanted to lock it down further.

2)In a command prompt, move to the FileStore directory and run the following command:

icacls . /setintegritylevel l

This will set the integrity level to low and allow un-elevated users to write to the directory. The output should look something like this:

C:\Program Files (x86)\Metastorm\BPM\Web\app_data\XtraReports\FileStore>icacls .
 /setintegritylevel l
processed file: .
Successfully processed 1 files; Failed processing 0 files

C:\Program Files (x86)\Metastorm\BPM\Web\app_data\XtraReports\FileStore>icacls .

. NT SERVICE\TrustedInstaller:(I)(F)
  NT SERVICE\TrustedInstaller:(I)(CI)(IO)(F)
  NT AUTHORITY\SYSTEM:(I)(F)
  NT AUTHORITY\SYSTEM:(I)(OI)(CI)(IO)(F)
  BUILTIN\Administrators:(I)(F)
  BUILTIN\Administrators:(I)(OI)(CI)(IO)(F)
  BUILTIN\Users:(I)(RX)
  BUILTIN\Users:(I)(OI)(CI)(IO)(GR,GE)
  CREATOR OWNER:(I)(OI)(CI)(IO)(F)
  Mandatory Label\Low Mandatory Level:(NW)

Successfully processed 1 files; Failed processing 0 files