Business Intelligence with SAP Business Objects 4.3

Desktop Compatibility Pack (DCP)  The “Desktop Intelligence Compatibility Pack” has been delivered in Fix Pack (FP) 6.1 which is to be installed over Desktop Intelligence XI 3.1 SP6 desktop product.  When installed, it  allows the Desktop Intelligence reports, users, universes and database connections to be managed by the BI 4.1 platform.  The goal is to allow Desktop Intelligence users and content to move to BI 4 as easily as possible. The Desktop Intelligence Compatibility Pack helps in scenarios with reports are difficult or costly to convert to Web Intelligence. Don't bet on "DCP" to keep your Deski documents alive, this feature is only there to facilitate your migration project and nothing more. We must not forget that a migration project is often associated with a project to convert your Deski (.REP) documents to Webi (WID). The  steps to follow for installing are the following: 1.       Install SBOP Enterprise Clients 3.1 Service Pack 6

Error c3_qtds_error_it_505 Envirnonment SAP BO 40 SP 8 Db Oracle 10 i The problem was that no group had the right at least to view this connection So in order to solve the error we gave the view right to the specific group Another solution you can try to solve this problem requires to follow these steps: Log on to CMC->Universe Connection->Manage->Top level Security Assign the Data access right in Relational connection Choose your connection  Data Access(Owner right) Use Connection (Owner Right)

Dear readers soon I will write down for you troubleshooting  with Upgrade Management Tool  and Promotion management while migrating from XI R3.1 SP 4 to BI 4 sp8. Best regards Giuseppe

CCM  Error : Visual C++ Runtime library Environment  BI 4 SP 8 Windows Server 2008 R2 sp1 On opening the CCM tool from the BO server it crashed more times. In our case we just restared the Server and this solved the problem.

 Cannot initialize Report Engine Server. (Error:RWI 00226) (Error:INF) Environment BO XI R3.1 SP 4 Windows Server 2008 R2  sp1  While rescheduling a Webi report one of our users experienced the error in exam. Solution: In our case we just restared WebIntelligence group servers: See also: SAP BI 4.0 Errors List XI R 3.1 errors solutions

After moving the server under Win Domain both cmc and bi launchpad url erased the following error: Environment  SAP BI 4.0 SP 8 Microsoft Windows Server 2008 R2 HTTP Status 500 - type Exception report message description The server encountered an internal error () that prevented it from fulfilling this request. exception java.lang.NullPointerException         com.businessobjects.servletbridge.customconfig.Config. (Config.java:37)         com.businessobjects.servletbridge.customconfig.ConfigReader.getConfig(ConfigReader.java:274)         com.businessobjects.pinger.TimeoutManagerFilter.getSessionState(TimeoutManagerFilter.java:201)         com.businessobjects.pinger.TimeoutManagerFilter.doFilter(TimeoutManagerFilter.java:82) note The full stack trace of the root cause is available in the Apache Tomcat/6.0.35 logs. The problem was caused by the user wich started SIA wich was Windows Domain user that was administrator of the machine, we hav

 Scheduling reports error -  source file error. [Invalid argument]: [CrystalEnterprise.DiskUnmanaged]  Environment SAP BI 4 SP8  The BI 4 server is not in windows domain  but SIA service is runned by a domain user As suggested in other B.O. forum we perfomed the following steps: in CMC,  the Job Server  must use a NETWORK SERVICE user that has all the permissions to read/write, that run's as a service, log on as service account etc. ( admin user) ; user has full read/write access to the folders.  we are following  the UNC naming conventions while specifying the folder name including the sub-directories. So when we scheduled reports in order to create acrobat files on a network folder such as \\ServerName\Path  directories. the scheduled istance Fails  and raises the error source file error. [Invalid argument]: [CrystalEnterprise.DiskUnmanaged]  Solution: In our case we decide to move the server in the Windows Domain and this solved the p