Everything works except viewing a report *in* the Report Viewer web part

[Former Member]

Hello!

I'm having an issue with the SharePoint 2007 PIK where the following works fine...

1. Adding the Document List to the web page and clicking a report to view it in a new browser window

2. Adding a Document View web part and pointing it to a Document on the BOE server repository views fine in the Doc View web part

However, when I try to use the Crystal Report View web part, click Edit, and Browse to select a report to view, it selects it fine but does not display it. Instead I get this error:

Report cannot be displayed because no report processing server is available. Please try again later or contact your BusinessObjects Enterprise administrator.

It setting up a connection between the Document List and Crystal Report View also gives the same error when a report is selected by the end user.

Any ideas what I can check? Do I have to install the BOEXIR2 web components on this SharePoint server too?

Right now it just has the BOE .NET SDK and SharePoint PIK. The full BOE XI R2 server that I'm calling is on another computer.

Thanks!

Horus

[Former Member]

Hi, I get exactly the same error with Sharepoint 2003 and the PIK for BOIX 3.1, any ideas? Was just about to post when read this so thought I'd tag this on in the hope I'd get a quick response. I can select a report, I can see all the correct parameters on the report so it obvously is the correct one but then I get the exact error reported in this thread.

Thanks, Simon

[Former Member]

Can you try the workaround mentioned in the thread, i.e creating crystalreportviewer115 virtual directory

Thanks,

Shivanand

[Former Member]

Ok, got this to work finally. The virtual directory steps were helpful but I still got broken links on my images.

I tried right clicking the toolbar and report images in the browser and found the URL. Then I just entered that URL in the browser. This helped a bunch since at least I had a new error to research.

Server Error in '/crystalreportviewers115' Application.
--------------------------------------------------------------------------------
Configuration Error 
Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately. 

Parser Error Message: Cannot use 'partitionResolver' unless the mode is 'StateServer' or 'SQLServer'.

Googling this lead me to a tip to add a sessionState key in my X:\Program Files\Business Objects\common\3.5\crystalreportviewers115\web.config file as follows:

<sessionState mode="SQLServer" timeout="60" allowCustomSqlDatabase="true" partitionResolverType="Microsoft.Office.Server.Administration.SqlSessionStateResolver, Microsoft.Office.Server, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" />

After this my buttons and images worked. I'm not sure if your config is different but as a beginner with this stuff myself hopefully this works for you.

Horus

[amsidory]

That is correct...

Can you please check if all the necessary servers in BOE are enabled and running

[Former Member]

From what I can tell the servers are running. I can tell the Application Server I'm connecting to works, since I can open InfoView from our web server and select it as the System and the reports come up fine.

Maybe an answer to the following would help....

Consider 3 servers:

Server W: Web server running BOE InfoView engine

Server A: Application server running BOE XIR2 Server

Server S: Running Sharepoint 2007, SharePoint PIK, and the BOE XIR2 SDK (from the BOE client install)

If I navigate to Web Server W, select App Server A as the system, I can select and view reports fine.

If I open the webpart from Sharepoint Server S which has server A in it's web config, then I can navigate the folders of documents/reports in SharePoint, the Document view shows a Excel file, for example, fine in SharePoint, however, reports just give that error in the Report web part.

What on either the App or SharePoint S may be missing or need to be installed? Does the Server S need some BOE server components too (other than PIK and SDK)? Does App Server A need some web components?

Thanks!

Horus

[Former Member]

Hi,

Please try the following workaround to display crystal report in crystal report web part

Define a new virtual directory for crystalreportviewer115 under your new Virtual Server. Go into IIS Administration, expand the Default Web Site. Create a new virtual directory under your new Virtual Server (ie. Compuwarehouse) and name it crystalreportviewers115 exactly as it shows under the Default Web Site. The new crystalreportviewers115 Virtual Directory will point to this folder: C:\Program Files\Business Objects\common\3.5\crystalreportviewers115. Give it Read and Execute permissions.

Thanks,

Shivanand

[Former Member]

Thanks! Getting closer now, the SharePoint PIK Crystal Report Viewer WebPart now shows the report-- well almost.

If I don't set the parameter prompts to be handled by SharePoint, the Prompt for Values screen appears in the webpart but none of the Date Select or OK buttons work. Also the button icons/graphics seem to be missing. I just "Error on Page" at the bottom of my browser if I click anything.

Now, if I edit the web part to make the web part prompt for the parameters in it's toolbar, the report appears but the Images appear as broken links.

Any idea what my SharePoint server may be missing?

As a reminder I have a 3 server setup (BOE/Infoview/Web front-end server, BOE/App/CMS Server, SharePoint 2007 Server).

Thanks!

Horus

[amsidory]

Did you get this working..I don't see any reason it shouldn't. From your details it looks like you are setting the connection between CR viewer webpart and doc list webpart. This should work.

.NET SDK is the minimum pre-requisite and should not not any concerns.

Regards

-Amit-

[Former Member]

Hi Amit,

I'm afraid not, I wasn't sure what else to check or settings to fix. It's clear the PIK web part is able to connect to the CMS since the document list and document view is working. It would stand to reason the report view would also work since they use the same setup, correct?

Thanks!

Horus