Posts

Showing posts with the label Errors

OPENDOC SYNTAX - Err WIO 00002 - Cannot open the hyperlink

Err WIO 00002 - Cannot open the hyperlink Environment BOE XI R3.1 SP 4 Cause The URL in the hyperlink is incorrectly constructed. The hyperlink references a document in a “CMC”. Documents in a “CMC” are not always accessible from Web Intelligence Rich Client for two reasons: The hyperlink does not specify the name of the server hosting the document because the Use complete URL path to build document hyperlink setting is not selected. Incomplete URLs are invalid when used outside InfoView. The hyperlink builds the complete URL, but the server specified in the URL is not accessible from the computer running Web Intelligence Rich Client. Action We corrected the hyperlink syntax as follow http://BOserver:8080/ OpenDocument/opendoc/openDocument.jsp?iDocID=AXMjJh.aOSZGpYx29mOaSmU&sIDType=CUID&sRefresh=Y&lsSNazione=FRANCIA

WebI Query Panel - JRE error with Firefox 3.6.28 on Windows 7 on opening

Image
WebI Query Panel -JRE error with Firefox 3.6.28 on Windows 7 on opening WebI Query Panel Environment  BO XI R3.1 SP 4 Client:  Windows 7 In order to resolve this issue:  go in the Java Control Panel and set the options as in the following images Enable Java system

WIS 30286 - You do not have access to one or more data providers; only the ones to which you have access will be refreshed. Do you want to continue?

Image
WIS 30286 You do not have access to one or more data providers; only the ones to which you have access will be refreshed. Do you want to continue? Environment XI R 3.1 SP 4 Cause: The problem is due to the missing  access rights to the universe for a specific user  Solution: We solved this issue by giving to the user  the right to access to related Universes !

WIS 30951 -The document can't be retrieved from the File Repository Server. Contact your System administrator

Image
 WIS 30951 -The document can't be retrieved from the File Repository Server. Contact your System administrator Environment BO XI R3.1 SP 4 Solution: 1. You can try to  restart Tomcat  and BO Servers and this operation  could resolved the  error. 2. The problem was due to the low available space on the disk where FRS is. So after freeing the disk space this problem was solved.

Error WIS 10083 - The qualification of the variable cannot be changed

WIS 10083 - The qualification of the variable  '......' cannot be changed. Error Messages Explained The qualification of the variable '%1%' cannot be changed. (WIS 10083) Cause You cannot change the qualification of the variable. (For example, you cannot change a measure to a dimension if its definition includes an aggregate.) Action Create a new variable with the appropriate qualification. Envirnonment: BO XI 3.1 SP 4 WebI Our customer variable with the above error : =[Rank_tab].[Anno]+"-"+[Rank_tab].[Region]+"-"+ConteggioCumulato([Nazione Cliente]) Is composed by text type and the last part wich is an numeric type. We solved the problem creating a second variable for the measure: ConteggioCumulato([Nazione Cliente]) and then we concataneted the first variable with the above one. See also: Business Objects errors list

How to install live office XI 3.1 with Office 2010

Image
Error: Microsoft Office XP and later applicatations: Excel, Word, Outlook or PowerPoint must be pre-installed. Environment  BO XI 3.1 SP 4 Xcelsius 2008 SP 4 Live Office XI 3.1 SP 4 If you need to install Live Office on a pc with Office 2010 already installed you will get the following warning: In can bypass this error with a  a workaround wich aims to avoid that MS installer checks if Office is installed. In order to do so you need an MSI editor, we suggest http://www.instedit.com/ So follow these steps: Create a copy of   Lifeoffice.msi file located in the Package folder. Open with InstEd the  Lifeoffice . msi file and select the “Tables” tab and click on LaunchCondition; Then delete the row which refers to Office ( “EXCELl10 OR OUTLOOK10″) and save the file. Then run this modified  Lifeoffice.msi,  previous error will not appear any more and you will accomplish your installation! Please note that this Workaround can be used with Xcelsius.msi

Error WIH 00013 - Invalid Session

'WIH 00013 - Invalid Session'  error returning when our user ran  Deski reports through infoview. Environment BOXI R 3.1 Windows Server 2008 R2 Tomcat Webapplication Server Solution We changed timeout-settings for Infoview increased to 120 minutes. However as we left an web intelligence document idle for more than 20 minutes the same error came again. We increased the idle connection timeout and idle document timeout settings for the WebIntelligenceProcessingServer using the CMC  but it was not sufficientto be neccessary) As Webi reports are not handled by the InfoView application   the timeout settings from InfoView are not helpful. We had to change the timeout settings for the AnalyticalReporting Application  BOInstallDir\Tomcat55\webapps\AnalyticalReporting\WEB-INF\web.xml See similar post: ERROR WIS 30280 BUSINESS OBJECTS ERRORS LIST

ERROR WIS 30280 - WEB INTELLIGENCE SERVER MEMORY FULL

ERROR WIS 30280 We had a problem on opening all Webi reports. We found that the error message appears because the Web Intelligence server stresses the memory resources when processing many reports containing a large amount of data. Solution To resolve the error message, it is necessary to increase the memory heap size value.  Follow these steps:  Open  the regedit ( Registry Editor) Go to the HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Control/Session Manager. Click Subsystems > right-click Windows key > click Modify. Edit the SharedSection value from 1024,3072,512 to 1024,3072,1024. Go to HKEY_LOCAL_MACHINE\SOFTWARE\Business Objects\Suite 11.5\default\WebIntelligence\Server\Admin\SwapTimeOut. Update  this value to 1500 seconds. Otherwise you could set this to a value higher than the Web Intelligence Report Server connection time out value found in the Central Management Console. This value is expressed in minutes.( default is 20). Restart the Web Inte

Error WIJ 20006 - One or more data sources are unavailable for queries

Error WIJ 20006 - One or more data sources are unavailable for queries  Environment: BOXI R3.1 SP4  with WebIntelligence The universe connection is working fine. This error came while a user was editing a Webi query. Solution: We resolve the problem by assigning the user to the group with access rights to the universe on which the report pointed. See also related posts: Error DA0005 CONNECTION or SQL SENTENCE ERROR - ORA-12154 BUSINESS OBJECTS ERRORS LIST

Error DA0005 CONNECTION or SQL SENTENCE ERROR - ORA-12154

Environment: Business Objects XI R 3.1 - Desktop Intelligence/ Rich Client We had this error CONNECTION or SQL SENTENCE ERROR (DA0005) ORA-12154: TNS:could not resolve service name :-12154 just  for one a client in another site of our customer. We checked this  problem by typing  in CMD tnsping Oracle SID  for example: tnsping oracledatabase. The problem was that int the tnsname on the client under the path : C:\app\username\product\11.2.0\client_1\network\admin had not the same Oracle SID. Another  solution  could also be that the tnsping does not respond so the listener could be down. Similar case: On another Desktop Intelligence client with the same issue (error code) the problem was due to a double Oracle installation and a double Business Obects Intallation. Solution: In this case we unified the two different TNSNAMES in only one ! For other error see also: BUSINESS OBJECTS ERRORS LIST

Error FWM 00001 - USR0013 - openSessionLogon with user info has failed - Cannot access the repository

Let see another case of the error: [repo_proxy 13] SessionFacade:openSessionLogon with user info has failed(Transport error: Communication failure.(FWM 00001) (hr=#0x80042a01) related to the error : Cannot access the repository (USR0013) Using Rich Client  (or Desktop Intelligence)  in a Business Objects XI R3.1 with Enterprise authentication on the System NOT USING J2EE system. As I wrote before  SYSTEM:6400(J2EE) means you are using 3 tier Deski which happens through web works fine as there is no firewall in between. while using SYSTEM:6400 we are in case of 2 tier login and your firewall is blocking the connection. In order to solve the problem you need to open some ports in the firewall for detail please read FWM 00001 - openSessionLogon with user info has failed If this operation does not solve the problem you can edit the REGEDIT - Registry Editor  (after making a copy of it in order to recover it in case of problem) then go to: HKEY_LOCAL_MACHINE KE

Error FWM 00001 - openSessionLogon with user info has failed - [repo_proxy 13]

[repo_proxy 13] Session Facade::openSessionLogon with user info has failed(Transport error: Communication failure. (FWM 00001) (hr=#0x80042a01) Environment: Business Objects XI R 3.1 Enterprise SP 4 Desktop Intelligence client from extranet site cannot access to the BO Server. We used the right credentials, we checked our firewalls. Our firewall is open for the ports 6400 and 8080 (as default). The log shows that the network packages are sent between the client and server. The request is reaching the CMS as 6400 (BO server port) is enable but the Clients are not getting the response back as the request port is not enabled on the Firewall. On CMS there are two ports: one is Name Server port the other is the Request Port , by default the name server port is assigned the port 6400 and the request will reach the CMS when the name server is enabled on the firewall. The problem is that Web/client application cannot communicate as the Request port is unaware and the f

Error FWM 00001 Transport error: Communication failure.

Environment BO XI R 3.1 SP 4 On logging on Desktop Intelligence,  the following error occurs:  SessionFacade::openSessionLogon with user info has failed(Transport error: Communication failure.(FWM 00001) Cause The client could not talk to the Server . This is the main  reason.  1)SYSTEM:6400(J2EE) means you are using 3 tier Desktop Intelligence which happens through web works fine as there is no firewall in between.  2)SYSTEM:6400 is 2 tier login and your firewall is blocking the connection.  The first one is a key that gets created when you modify or create a new Desktop Intelligence document from Infoview, that is 3-tier. The second one is you entering manually the information for 2-tier. Others Possible causes of the problem are: The server may be down. There may have been a network communication problem. The request my have timed out. Could be also a database connectivity issue between the CMS server and the Repository database. In order to

Error WIS 00010 - The universe does not allow using a complex expression in a GROUP BY statement

The universe does not allow using a complex expression in a GROUP BY statement. You cannot run this query. See your Business Objects administrator. (Error: WIS 00010) Cause A query contains a GROUP BY clause that uses formulas or aliases. The universe does not allow these expressions in GROUP BY clauses. The behavior is determined by the parameter Y in the PRM file for the target RDBMS. Action You have two solutions: • Modify the query so that objects using formulas or aliases are not included in the query. • A universe designer can open the PRM file for the target RDBMS and change the value for the parameter GROUPBY_EXCLUDE_COMPLEX to N. This change should be made only if you are sure that your RDBMS supports complex GROUP BY expressions. Please note: The parameter GROUPBY_EXCLUDE_COMPLEX by default is 'N' . Check your .prm file in your environment and change accordingly.  See also: BUSINESS OBJECTS ERRORS LIST

Error WIS 30272 - Max character file size limit exceeded

Max character file size limit exceeded. The document is too large to be processed by the server. Contact your BusinessObjects administrator. (WIS 30272) Cause: When you view a Web Intelligence document in HTML format, the Web  Intelligence server generates character based output, which is then interpreted by your web browser. This errors occurs, if the size of the  character output is greater than the maximum size specified by your administrator for the Web Intelligence server. Solution The administrator can change the parameters set for Maximum character output on the Administration Console.  Please note that however, increasing the maximum  binary output can affect performance. Log  on  CMC -> servers -> Web Intelligence Report Server -> Properties  Maximum Binary File Size:  Maximum Character File Size: The Binary file size shold be  for PDF; the character size is for webi reports.  You have to increase you current limits unt

Error FWM 02088 - Account Information Not Recognized

Account Information Not Recognized: The CMS system database is not available. This error cannot be rectified by the end user. Report this error to your system administrator or database administrator. (FWM 02088)  Environment XI R3.1 Cause The CMS database is unavailable. Solution Check if all the servers including CMS are running and enabled in CCM on BOBJ server. If yes,  r estart the SIA, it always works! See also: BUSINESS OBJECTS ERRORS LIST

Error WIS 00509 - Universe data connection could not be found

Universe data connection could not be found. Either the connection has been deleted or you do not have the rights to use it. The universe data connection is not available, either because it has been deleted or because you do not have the right to access it. Solution: The Business Objects Administrator must  give to a specific users group (user)   the right to access to the universe and its related connection. See also: BUSINESS OBJECTS ERRORS LIST

Business Objects HTTP 404 errors

 HTTP 404 errors in Business Objects XI R 3.1 The HTTP 404 error may happen for one of the following reasons: 1. The requested page was deleted in error. Check the deployment folder of the web application to make sure that the requested page exists. 2. The web application is not properly configured. Try to access other pages in this web application. If there are other pages in this web application that are not accessible, then there is a problem with the web application configuration. Consult the web application deployment instructions to check that the configuration files are valid, or redeploy the web application. 3. A system setting is incorrect. For example, the memory limit was reached or an ODBC DSN was not correctly configured. As a result, an exception was thrown and the expected page was not generated. Check the web server log or the web application log for error or exception records. 4. An environment variable is not properly set. This environment variable can

Error RWI 00323 - Cannot retrieve the document with the passed obsolete token.

Cannot retrieve the document with the passed obsolete token. (RWI 00323) Cause An error occurred during document state deserialization. This might be caused by a storage token that identifies a document state, which is no longer available in the storage tokens stack. Action In the webi.properties file, increase the value of storage tokens stack size. Also, ensure that the storage token is valid before using it. In BO XI R3.1 environment this problem could be also fixed installing the latest fixpack/service pack. See also: BUSINESS OBJECTS ERRORS LIST

Error RWI 00239 - Connection failed. The server has reached the maximum number of simultaneous connections

Connection failed. The server has reached the maximum number of simultaneous connections. (RWI 00239) Cause The maximum number of server connections allowed has been reached. Action Either raise the value of the maximum connections server parameter, or add another server instance. To modify the maximum connections value: 1. Log on to BusinessObjects Enterprise Central Management Console. 2. Click on Servers. 3. Expand Server Categories, and click on Web Intelligence. 4. Under Server name, double-click on WebIntelligenceProcessingServer. The Properties window appears. 5. In Properties window, under Web Intelligence Processing Service, enter a greater value for Maximum Connections. In our customer case environment BO XI R3.1 on windows server 2008 R2, with 4 cpu, 16 GB Ram and more then 300 BO users   we inserted a 100 connections value  and this value fixed the problem. See also: BUSINESS OBJECTS ERRORS LIST