Steps to Enable BI Publisher logging

 When ever we face an issue in configuration of BI Publisher the easiest method to resolve is by looking into logs.Please find below the steps to enable BI Publisher logging:

1. In the Bi Publisher enterprise go to Admin > Server Configuration.
2. Under General Properties, set Debug Level to Debug.
3. Create a target folder for the logs like D:\BIPLogs.
4. Create xdodebug.cfg with the following test:
  LogLevel=STATEMENT.
  LogDir=D:\BIPLogs.
5. Place the file in jdk\jre\lib in the OraHome folder where the application server is installed.
6. Restart Bi Publisher server.
7. Do some activities in BIP like scheduling.
8. Wait for some time and attach the logs from D:\BIPLogs folder.

ORA-12154: TNS:could not resolve the connect identifier specified

The cause of this error: SQL Plus cannot identify the connect string specified.
What can be the possible reasons:
1. The tnsnames.ora is not present under $ORACLE_HOME. You can check for it by typing %ORACLE_HOME% in command prompt.
2. The file is not accessible.
3. The file is invalid – because of the presence of junk characters or unmatched parenthesis.
4. The connect string that you have used – may not be present in the tnsnames.ora or present with somewhat different name – basically a mismatch of what you have entered and what is present in tnsnames.ora
5. Check the default directories for old or bad copies of tnsnames.ora
6. Please check with the database admins that the Listener is up and running for the connect string that you are trying to connect to.
7. Please check if TNSNAMES is present as one of the values for the NAMES.DIRECTORY_PATH parameter present in the sqlnet.ora file
NAMES.DIRECTORY_PATH= (TNSNAMES)
Please find below sample tnsnames and sqlnet.ora
TNSNAMES.ORA
ORCL =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.3.90)(PORT = 1521))
)
(CONNECT_DATA =
(SERVICE_NAME=ORCL)
)
)

Macro Cannot be found error in BI Publisher- MS Office

After installing BI Publisher for MS Office Suit I got an error stating "Macro Cannot be found..." Just like anybody else i was also frustrated when i saw the following error for the first time.

Solution
Close all MS Office Applications (Including Outlook, Groove etc)
For 64-bit operating systems, type the following in command prompt:
Regsvr32 "C:\Windows\SysWOW64\MSCOMCTL.OCX"
For 32-bit operating systems, type the following in command prompt:
Regsvr32 "C:\Windows\System32\MSCOMCTL.OCX"

It worked fine for me and my colleagues

.
Waiting for your valuable feedback.