Business Intelligence with SAP Business Objects 4.3

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

[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

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

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

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

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

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

 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

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

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

Environment: BO XI R3.1 SP 4 on WindowsServer 2008 R2 An error occurred during document utilization. This might be due to insufficient memory or an I/O error. Action Ensure that there is sufficient memory available. Also check for any webi.properties customization. That is: look for  ..: \Business Objects XI 31\Tomcat55\webapps\dswsbobje\WEB-INF\classes #WID_FAILOVER_SIZE=10 #WID_STORAGE_TOKEN_STACK_SIZE=10 #REP_FAILOVER_SIZE=10 – DeskI documents #REP_STORAGE_TOKEN_STACK_SIZE=10 >> Change all the values to 0 (no limit) >>Remove the # symbol - uncomment  More Intrusive solution  Add a request Timeout in the WebI and WebJob Servers (36000 for example)  Modify the CCM settings for Webi Server:  Add -port ServerIP  Add : -requesttimeout 36000  Modify -ns ServerIP After that restart Tomcat and all servers. See also: BUSINESS OBJECTS ERRORS LIST

Export Failed  - [Deski XI]  Environment BO XI  R3.1  After having Imported Webi reports, folders,universe,connection and repository objects into a BIAR file the BIAR was created successfully, but connection import failed so we Deleted all my objects, folders, universe and connections from the BO server ,Exported successfully the BIAR file back into the BO server After  the Webi reports cannot be used since the universe connection is not available We redefined the universe connection and re-exported the universe  to the BO server so Webi reports work But we cannot export Deski reports to the server anymore - We get DX0034 error Problem solution on Deski open tools-> universes-> Refresh Perform the following sequence: Re-point the problematic reports.                                           - Go to Data menu à View data.                                                                               - Go to Definition tab in the Data manager window.          

Error Message: Your Web Intelligence session has reached timeout. Log out and log in again to Infoview (Error : WIS 30553)  EnvironmenT BO XI R 3.1 SP4 After getting this error message we have been not able to use the same session to create the reports successfully. Solutions The timeout parameter in web.xml is for Infoview web application. Can you try changing Web Intelligence Server Timeout properties from CMC. CMC->WebIntelligence Server ->Properties. More complex solution for JSP increase the application session-timeouts for the web.xmls for the three application locations as follows: Business Objects XI 31\Tomcat55\webapps/WEB-INF/web.xml Business Objects XI 31\Tomcat55\webapps\InfoViewApp/WEB-INF/web.xml Business Objects XI 31\Tomcat55\webapps\CmcAppActions/WEB-INF/web.xml 2. Increase the attribute value under to perhaps 60 in this example:    20 3. To modify the default session timeout value in the CMC, search for web.config in the folder: C

Error WIS 00003 - Some pre-defined filters are no longer available in the universe. See your Business Objects administrator. One or more predefined filters are no longer available in the universe. Predefined filters are condition objects that are predefined WHERE clauses. You use these to restrict the data returned in a query. Solution  Remove the predefined filters from the query, and manually create the same condition in the query by using the appropriate operators and operands. Exception case: In order to correct this problem the designer has renamed one  object in the universe   and has replaced it with the previous original name. This action has not solved the problem: The correct fix is to delete the new object in the last universe version, copy the filter  object from the old universe containing the original filter and  paste it into the current version of the universe. See also: BUSINESS OBJECTS ERRORS LIST

Error WIS 00001 - Some objects are no longer available in the universe. See your Business Objects administrator One or more objects in a universe are no longer available to a document, because they have been deleted in the Universe. Solutions: If you have the old Universe backup ( containing the deleted objects nedeed)  you can publish it again otherwise delete the objects from the query that seem to be missing.  The available objects are listed on the Data tab. Rebuild the query without the obsolete objects. See also: BUSINESS OBJECTS ERRORS LIST

Universe Syntax Error This error message appears when special characters are used in object names, including: [ ] = & @ × $ % , ; ! ß £ ~ § μ + ' ( ) { } - There is no solution just: do not use special characters in object names. See also: BUSINESS OBJECTS ERRORS LIST

LO 01003 - An error occurred when refreshing. Cause This error might be caused by the following reasons: 1. The report is corrupted. 2. Drawing Live Office object on unsupported areas, like Word Header or Footer, or Office 2007 PowerPoint Slide Master. 3. The server is not accessible. If not in the list, check the detail error. Action For cause: 1. Check from InfoView to make sure the document is valid. If yes, log-off and log-on BOE on Live Office Option dialog then try again, or re-start the Office application, then try again. 2. Do not drawing Live Office object on unsupported areas. 3. Fix the network connectivity or start up the server. If not in previous causes, use the error code in the detail to find the solution,or just follow the guide in the detail See also: BUSINESS OBJECTS ERRORS LIST

There are three options to recover a deleted folder depending  on what kind of backup you have done: 1. backup of the CMS database and File Store. 2. You created recently a BIAR file. 3. You have a Development/Test environment where you have this folder. Let's see the  Solution in case you have a back up of the CMS database. Follow the steps to recover deleted folder and sub-folders: 1. Copy the CMS database from the backup to your database server and point the CMS ODBC system DSN to it. 2. Copy the backed up file store to a Temp directory. 3. Change the path of input and output file repository servers in the CMC, for each server, to the Temp file store directory. 4. You will now be able to find the reports. Copy those reports to the BusinessObjects server's local disk, or create a BIAR file using the Import Wizard. 5. Point the ODBC system DSN back to the original database, and also change the paths on input file repository and output file repository se

Could not save document to the repository  (WIS 30567) Environment : BusinessObjects XI3.1 SP3; Windows Server 2003 SP2 Errors erased when trying to save Web Intelligence documents "Could not save the document to the repository for the following reason: [repo_proxy 30] InfoStore::ObjectExport::commit - (Helpers::InfoStore::ObjectExport::commit) File Repository Server error: Could not save the file .wid to the File Repository Server. File already exists. (hr=#0x80042a4a)(Error #-2147210678 (WIS 30567)" This error tells that when report was being saved into Input FRS, another report with the same ID was found there and the product couldn't overwrite it. So possible reasons are: you have no rights to overwrite docs in the BOE there are OS issues with restrictios on IFRS Drive space issues Beside, make sure the following servers are up and running and also check your rights on saving the object in BOE: Web Intelligence Report Server Input Report

Hello Everybody, would you help to collect more frequent BO Errors,  better if indicating BO version? If you want you can also write down your personal fix or standard solution. This could by useful for somebody. Thanks in advance for co-operating! Best regards Giuseppe SAP BI 4 - Scheduling reports error - source file error. [Invalid argument]: [CrystalEnterprise.DiskUnmanaged] wij-20002 error webi rich client Internal error Error RFC 00101 - No server was available to process the request FWM 00001 Transport error: Communication failure. Error WIS 30272 - Max character file size limit exceeded Error WIS 00509 - Universe data connection could not be found Error RWI 00323 - Cannot retrieve the document with the passed obsolete token Error RWI 00239 - Connection failed. The server has reached the maximum number of simultaneous connections Error RWI 00239 - The maximum number of server connections allowed has been reached Error RWI 00322 - An error occurred whi