Skip to Content

How to troubleshoot an IOMS Application

In BOE Context IOMS Application has many dependencies, Hence it is recommended to follow the mentioned steps judiciously.

  1. To check the details of correlation id in the ULS logs.
  2. To check the IIS log files
  3. To check if solution is deployed correctly and check IOMS install logs.
  4. To check COM SDK traces
  5. To take SAP Integration Option for Microsoft SharePoint (ipoint) trace.

Now , We will go though the steps for each line Item mentioned above.

How to check the details of correlation id in the ULS logs.

It is understood that by default, SharePoint server will log error messages. to view such messages please follow the below steps.
1.Navigate to Install DIR of SharePoint software E.g.--> C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS
2.Collect logs from the current time date or proffered time.
3.Install Microsoft ULS viewer from here:, this is recommended for better readability.
4.Normally SharePoint will provide a Correlation ID (alphanumeric string) in the error message.  by using the ULS viewer we can find the Correlation ID in the log files.

How to check the IIS log files

IIS which runs SharePoint will log messages in the below folders.
1.Navigate to C:\inetpub\logs\LogFiles\
2.Collect logs from current time date or proffered time.

How to check if solution is deployed correctly and check IOMS install logs.

In SharePoint central administration site, at first navigate to site setting and manage form solutions and check if infoview.wsp file is deployed to the web application selected during installation .If not installed , deploy it again. The install logs will indicate any issues that occurred during installation or deployment of the Integration option:
1.Navigate to BOE Install DIR E.g.--> C:\Program Files (x86)\SAP BusinessObjects\Install Data\logs
2.Review logs from the time/date in which IOMS was installed.

How to check COM SDK traces.

1.On servers where IOMS is installed,  create a system environment variable logged in as an Administrator user
Variable Value: -trace -logging Path C:/logs/
Note that the logging patch in the variable value above was provided as an example and can be any accessible folder on the system.
2.Create a directory as configured in the logging path for example C:\logs  on the IOMS system.
3.Restart the System.
4.To generate logs, access the IOMS logon page, and try connecting to the BI system from IOMS, and make sure the logs get generated in C:\logs folder. Reviewing the logs generated in C:\logs will give some hints around commutation issues such as why some users cannot login to certain BI servers from IOMS web application.

How to take SAP Integration Option for Microsoft SharePoint (ipoint) trace.

1.Navigate to the root directory for the web application which was configured in SharePoint. (Example: c:\inetpub\wwwroot\wss\myserver8888\)
2.Create a backup of web.config
3.Edit web.config:

Add the following entry in the <configSections> of web.config:

<section name=""log4net"" type=""log4net.Config.Log4NetConfigurationSectionHandler, log4net, Version=, Culture=neutral, PublicKeyToken=692fbea5521e1304""/>

Add the following entry in the <appSettings> of web.config:

<add key=""bobj.logging"" value=""True""/>
<add key=""bobj.logging.log4net.override"" value=""c:\inetpub\logs\iomstrace.xml"" />

4.Create the iomstrace.xml file in the location indicated above with the following content:

<?xml version=""1.0"" encoding=""utf-8"" ?>
<!---   For log -->
<appender name=""LogAppender"" type=""log4net.Appender.FileAppender"" >
<file value=""c:\inetpub\logs\iPointLog.log""/>
<!--   Can give any path but the container Folder name for the log file has to be Logs -->
<layout type=""log4net.Layout.PatternLayout"">
<conversion Pattern value=""%date[%thread] %-5level %logger %class - %m%n"" />
<level value=""DEBUG""/>
<level value=""FATAL""/>
<level value=""ERROR""/>
<level value=""WARN""/>
<level value=""INFO""/>
<level value=""ALL""/>
<appender-ref ref=""LogAppender""/>
<!-- End for log -->

5.The log files will be written to the location indicated in the ""file value"" directive above"

Hope, this helps..

No comments