Posts

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