BOE XI R2 Version Numbers - Update
Version number for FP3.4 has been added to the list.
http://boinshort.blogspot.com/2007/05/boxir2-version-numbers.html
News and experiences working as a BI consultant
Version number for FP3.4 has been added to the list.
http://boinshort.blogspot.com/2007/05/boxir2-version-numbers.html
Posted by Oakleaf at 10:59 AM 0 comments
Version number for FP3.5 has been added to the list.
http://boinshort.blogspot.com/2007/05/boxir2-version-numbers.html
Posted by Oakleaf at 9:52 PM 0 comments
Version number for SP5 has been added to the list.
http://boinshort.blogspot.com/2007/05/boxir2-version-numbers.html
Posted by Oakleaf at 5:23 PM 1 comments
This post is a clarification about the language settings in the platform when installing BusinessObjects Enterprise (BOE). When installing the Enterprise platform you get an dialog box at the very beginning that asks about the language that is to be used during installation (Please Choose Setup Language). This is the language that the Central Management Server (CMS) will use.
The default language selected in the dialog box is based on the Regional Options of the operating system. You can change this to any language you want. But be aware! The selection you make here is pretty permanent. The only way to change this is to create a new CMS database and migrate the old database over to the new database. But as you don't have any option to choose which language to be used when you create a new CMS database you can do the language selection through the Regional Options. When you create a new CMS database it uses
the language in the Regional Options as the CMS language. Here are a short summary of the steps needed to change language in an already installed environment.
Why is this important? For a couple of reasons. I have used the above method to change language to English when the BOE platform has been installed in a country specific language. When you have a country specific language set in the CMS much of the error messages and log entries are in that language. When you want to use the error message it could be difficult to translate it to English. It is much more difficult to find a solution when you don't have the exact error message to go by. If you must create a case with SAP Support it is impossible for them to read some of the error messages. And in that case you must translate all error messages to English manually.
Posted by Oakleaf at 10:47 AM 0 comments
Here is a tip on how to troubleshoot an error in a Crystal Reports report when using files like Excel and Access.
The error that you get when trying to view the report in InfoView is Error: The database logon information for this report is either incomplete or incorrect.
This is due to the configuration made in Crystal Reports when creating the report against an Excel file. When you create the report you often point your data source against a file through a mapped drive. This setup doesn't work when publishing the report to the repository on the BusinessObjects Enterprise server. You must specifiy the data source name as an UNC path (like //server/) or as an name of an DSN that exist on the server.
If you have entered a path for a mapped drive and you try to reconfigure that setting in Central Management Console (CMC) it will not work. I don't know why this doesn't work for this data source setting.
Example, if you make a report with a local DSN with name DSN_A against a database server named DB_A and publish it to the repository server there are two scenarios;
But for the case with a data source file path it doesn't work.
Perhaps elementary for some but not for me. Why doesn't this work? It could work if you wanted to...
Posted by Oakleaf at 5:08 PM 0 comments
We have had alot of logging about assert failures in the log files for our different BusinessObjects Enterprise systems. I contacted Business Objects support to try to get an explanation of these messages and if we should act on any of them.
The answer is that the log files with assert failures are only interesting when there are some specific issues with the system. When a certain problem arises the support goes through the assert failure log files to try to get an explanation. And as you can see in the examples below the source code file name and line number is logged to ease up the trace.
I also asked if there was some way to turn that logging off and the answer was No.
Assertion generally stops the execution of code but Business Objects said that their assertion doesn't. If you don't know what assertion is you can take a minute or two and read this article from Wikipedia http://en.wikipedia.org/wiki/Assertion_(computing).
Here are some examples of assert failures that we experienced in one of our BOXI 3.0 environments.
[Mon Oct 13 08:30:39 2008] 304 7312 assert failure: (.\frsresmgr.cpp:1242). (false : FileResourceMgr::unlockFile: Cannot find entry for file E:\Business Objects\BusinessObjects Enterprise 12.0\FileStore\Input\a_049\017\036\2363697\~fc_23f0568ca38e233.xls).
[Mon Oct 20 06:36:24 2008] 12112 3684 assert failure: (d:\titan_rtm\src\framework\servers\cpp\cms\include\infoobj.h:787). (GetPropString( id, ret, bSearchWireObj ) : no message).
[Mon Oct 27 10:00:42 2008] 9288 9724 assert failure: (.\sessionmgr.cpp:271). (beforeAuthen != serverAuthen && afterAuthen == serverAuthen : no message).
[Thu Oct 02 14:41:43 2008] 7228 1864 assert failure: (.\secssoplugin_impl.cpp:62). (0 : UnInitializePlugin() -- Unexpected Exception!).
[Thu Oct 02 14:41:43 2008] 7228 1864 assert failure: (.\secssoplugin_impl.cpp:62). (0 : UnInitializePlugin() -- Unexpected Exception!).
[Tue Sep 23 19:52:26 2008] 2444 2440 assert failure: (.\auditsubsystem_impl.cpp:1233). (cuidToIdMap.Lookup( auditCUID, auditId ) : Auditor::CreateRecordsForServer - the AuditingService seems to be missing from this deployment.).
[Wed Oct 01 10:46:49 2008] 7028 3824 assert failure: (.\auditsubsystem_impl.cpp:1233). (cuidToIdMap.Lookup( auditCUID, auditId ) : Auditor::CreateRecordsForServer - the AuditingService seems to be missing from this deployment.).
[Wed Oct 01 10:47:51 2008] 7028 6824 assert failure: (.\ScheduleObject.cpp:199). (0 : no message).
[Wed Oct 01 10:47:51 2008] 7028 6824 assert failure: (.\ScheduleObject.cpp:253). (0 : objectId[2278305] is missing SI_NEXTRUNTIME property; isRunnable[true], hasScheduleStatus[false]=[9], hasProgress[false]=[0], hasOutcome[false]=[0].).
[Wed Oct 01 20:00:12 2008] 8072 6944 assert failure: (.\wireob.cpp:749). (state == foundFlag : no message).
[Wed Oct 01 20:00:12 2008] 8072 6944 assert failure: (.\wireob.cpp:775). (false : Error: Wrong number of parameters in URL ).
[Wed Oct 01 20:00:12 2008] 8072 6944 assert failure: (.\infosessionmgr.cpp:913). (false : Couldn't get token).
[Fri Oct 24 08:27:55 2008] 8668 8504 assert failure: (.\DocumentConnectionRepository_common.cpp:78). (0 :
ReportSourceRepositoryCommon::getServerDisabled(): m_varSvrFactory is NULL).
Posted by Oakleaf at 10:37 AM 1 comments
I have updated the BusinessObjects Enterprise XI Release 2 version number list again.
Check it out here:
http://boinshort.blogspot.com/2007/05/boxir2-version-numbers.html
Posted by Oakleaf at 8:41 AM 0 comments
Platform:
Desktop Intelligence
BusinessObjects XI, XI Release 2
A common problem is when you delete a report from the repository and then realises that it was a mistake removing it. Even though you have a local copy of the report you can't open it. This is because BOE is validating the rights against the repository and when the report does not exist there it can't be opened.
If you try to open that report in Desktop Intelligence you will get an error stating: You are not authorized to use this document. (FRM00008).
There are a number of possible workarounds for this problem, one being that you create a dummy report in the repository with the same name as the report you just deleted. Then you find out the path and file name through Central Management Console. Browse to the report folder in Input File Repositry Server and delete the file (remember the file name). Add the original report to the same place and change it's name to the same as the deleted file. Now you are able to import it into Desktop Intelligence.
This solution doesn't work in all situations and it's not a supported method. Manually deleting files from FRS is NOT a good idea in most cases. With this particual problem there exist a different solution that will solve this.


And, yes, a backup is also one way out of this...
Posted by Oakleaf at 11:43 AM 4 comments
I have done another update on my list of version numbers for different patch levels available for BusinessObjects Enterprise XI Release 2. Check it out here:
http://boinshort.blogspot.com/2007/05/boxir2-version-numbers.html
Posted by Oakleaf at 12:15 PM 0 comments
In BusinessObjects Enterprise there are a number of alternatives to choose from if you want to place the report/report instance somewhere else than in your available folders in InfoView.
There are two ways to handle report objects from InfoView:


To get all of this to work there are four destination plugins that has to be configured for each Job Server.
In the picture above two destinations are enabled and two are disabled.
If a user gets a error message that reads something like "Error Message: destination DLL disabled. CrystalEnterprise.DiskUnmanaged:" or something like "The destination plugin required for this action is disabled. If you require this functionality, please contact your system administrator." it probably means that the destination is not enabled for that Job Server.
To enable the destination you have to find out which report type (i.e. Job Server) and which destination the user tried to use. Logon to CMC and navigate Home -> Servers -> SERVER_NAME.JOB_SERVER -> Destinations tab. Mark the checkbox for the destination you want to enable and press button Enable. Select the same destination and configure it. Done.
Here are the different Job Servers available and which report type that uses them:
Web Intelligence: SERVER_NAME.Web_IntelligenceJobServer
Desktop Intelligence: SERVER_NAME.Desktop_IntelligenceJobServer
Crystal Reports: SERVER_NAME.reportjobserver
Send button in InfoView: SERVER_NAME.destinationjobserver
If you change settings in destinationjobserver you must restart that service for changes to take effect.
Which Job Server to configure and when to do it is not that complicated but it is alot of confusion about this from various sources. This KBase Article (ID 8010998) from Business Objects for example is wrong and confusing:
http://technicalsupport.businessobjects.com/KanisaSupportSite/search.do?cmd=displayKC&docType=kc&externalId=8010998&sliceId=&dialogID=19218054&stateId=1%200%2019214535
Posted by Oakleaf at 9:19 PM 1 comments
I have updated a previous post where I describe the different patches that are available on the BOXIr2 platform:
http://boinshort.blogspot.com/2007/07/patches-explained.html
Posted by Oakleaf at 9:03 PM 0 comments
Version number for SP3 has been added to the list.
http://boinshort.blogspot.com/2007/05/boxir2-version-numbers.html
Posted by Oakleaf at 9:12 PM 0 comments
One of our customers have had problem naming objects, in this case user objects, that have similar user names. Only the letter v and w differs.
The problem is that if you create a user with the name abcv you can't create a user named abcw. After alot of investigation from Business Objects technicians the problem was isolated to the regional and language settings in the server OS. We had Swedish settings when we installed BusinessObjects Enterprise which caused this problem. The settings needed to be English during installation for some reason. Even if we changed settings later it didn't work. The server regional and language settings are stored in the repository database in some way.
The solution for this problem was:
Posted by Oakleaf at 10:33 PM 1 comments
When you create a scheduled report and you want to e-mail the hyperlink of the report in BOE you can configure this in the schedule settings. You include the Viewer Hyperlink by selecting that option in the drop down below the Message box. This selection adds %SI_VIEWER_URL% to the message field which later translates to a valid URL to that report using the openDocument method.
The resulting URL in the e-mail could look something like this (ASP platform):
http://xyz/businessobjects/enterprise115/infoview/scripts/openDocument.aspx?sIDType=CUID&iDocID=BUXpQ_n_fITEsTtHIPe_oXY
The %SI_VIEWER_URL% adds the URL that was specified in CMC->Objects->Object Settings...->Processing Settings->Default viewer URL and translates it to the hyperlink above.
But what if you manually wanted to specify the URL without changing it in the Object Settings? It's easy and it's possible. Just type the URL manually specifying the JSP or ASP path and the openDocument part. Based on settings above (CR document) you would type
'http://xyz/businessobjects/enterprise115/infoview/scripts/openDocument.aspx?sIDType=CUID&iDocID=%SI_CUID%'
in the Message field. The %SI_CUID% adds the unique object id of that document.
If you want to explore the openDocument parameters in detail, look at this document. It describes both the ASP and JSP version of the openDocument syntax.
Posted by Oakleaf at 11:15 PM 0 comments
Scheduled reports with e-mail sending functionality fail with the error message specified below:
write error. CrystalEnterprise.Smtp: SMTP_E_EXCEEDED_STORAGE(552)
The error is not due to BOE. The error message (SMTP_E_EXCEEDED_STORAGE) is a standard SMTP error, in this case it's because the attachment hit the mail size limit. This limit is configured in the SMTP Service on the SMTP server.
Here is how to find the size limit of the SMTP server:
Posted by Oakleaf at 11:57 AM 0 comments
I have found three small issues when installing FP2.5 that could be of interest. Environment is BOXIr2 SP2 on Windows Server.
One positive note about FP's is that they are now visible in the Add or Remove Programs dialog for easier overview and uninstallment.
Posted by Oakleaf at 2:02 PM 0 comments
To make things a bit easier (?!) the Fix Packs, starting with FP2.5, have been split into two parts;
Posted by Oakleaf at 11:41 AM 0 comments
Critical Hot Fix 19 is now official.
Posted by Oakleaf at 4:40 PM 0 comments