OBIEE 11.1.1.9 – BI Publisher Set Up Fails on Windows Server 2012

Thoughts on “OBIEE 11.1.1.9 – BI Publisher Set Up Fails on Windows Server 2012”

1. Jonathan Johnson June 14, 2015 at 1:37 pm

   Awesome! Thanks for the post! This worked great for me! I actually was installing BI Publisher 11.1.1.7, but ran into the exact same error since I was installing on Server 2012. This fix the issue for my installation as well.

   -Jonathan
2. sajsan September 3, 2015 at 12:52 pm

   very helpful. I was able to get obiee 11.1.1.9 working on my windows 8 laptop due to this input.
3. Chris September 27, 2015 at 7:39 am

   Hi, I proceed just like you did but Windows 10 so I have :
   _osTypeMap = (
   ( “nt”, ( ‘nt’, ‘Windows NT’, ‘Windows NT 4.0’, ‘WindowsNT’,
   ‘Windows 2000’, ‘Windows 2003’, ‘Windows XP’, ‘Windows CE’,
   ‘Windows Vista’, ‘Windows Server 2008’, ‘Windows 7’, ‘Windows 10’ ))
   in my javashell.py.
   But I still have the same error. My java is 1.7.0_79.
   Do you think Windows 10 is not OK for OBIEE 11g(1.1.1.9) ?
   Thanks.
4. Kathy Nguyen October 17, 2015 at 1:32 pm

   Thanks for document, it works.
   I followed the steps, but fixed as soon as it’ completed the weblogic and click retry button then it will pick up the new change and continue processing.

   I mean, I install the OBIEE 11.1.1.9 (enterprise install) without the weblogic first.
5. Patrick Abram Post author October 18, 2015 at 8:01 pm

   Chris,

   Please refer to the OBIEE 11.1.1.9 Certification Matrix for complete details on what is supported. http://www.oracle.com/technetwork/middleware/bi/bi-11gr1certmatrix-11-1-1-9-0-2541437.xls

   You will see that Windows 10 is not listed as a supported operating system. Also, the Java version required for most installations is 1.7.0_80+. Since 1.7.0_80 is the terminal version of Java 7 that is the version I recommend if you want to try again.
6. Kathy Nguyen October 19, 2015 at 6:00 pm

   Make sure you have step 5 as documents :
   5.Import the javashell.py file with the following command: [JDK Home]/bin/jar uf jython-modules.jar Lib\javashell.py
7. Mike January 27, 2016 at 4:34 am

   I had the same error, same version of OS (Win server 2012 R2), but I use another workaround:
   1)Install the OBIEE component from setup selecting Enterprise Install (ignoring AppCrash at 97%)
   2)Exit the configuration tool after complete the install task just before “Create a new BI System” step.
   3)I use your guide,step 3
   ” Update the javashell.py file
   Open a Command Prompt
   Navigate to the [Middleware Home]\wlserver_10.3\common\wlst\modules directory
   Extract the javashell.py file with the following command: [JDK Home]/bin/jar xf jython-modules.jar Lib\javashell.py
   Use a text editor to modify the [Middleware Home]\wlserver_10.3\common\wlst\modules\Lib\javashell.py file
   Search for the first incidence of _osTypeMap in the file
   Add ‘Windows Server 2012’ to the map for “nt” right after ‘Windows 7’ (see below for details)
   Import the javashell.py file with the following command: [JDK Home]/bin/jar uf jython-modules.jar Lib\javashell.py”
   4)Execute the config tool ($OBIEE_HOME\Oracle_BI1\bin\config.sh or config.bat)
   It worked for me 😉

   Good luck and thanks for this helpful post!
8. Haitham Ibrahim July 17, 2016 at 1:51 am

   please right the final command for step 3 and 5 beacuse i can’t run this script right as example .

   Extract the javashell.py file with the following command: [JDK Home]/bin/jar xf jython-modules.jar Lib\javashell.py
   Use a text editor to modify the [Middleware Home]\wlserver_10.3\common\wlst\modules\Lib\javashell.py file
   Search for the first incidence of _osTypeMap in the file
   Add ‘Windows Server 2012’ to the map for “nt” right after ‘Windows 7’ (see below for details)
   Import the javashell.py file with the following command: [JDK Home]/bin/jar uf jython-modules.jar Lib\javashell.py
9. Patrick Abram Post author July 17, 2016 at 9:19 am

   I cannot be more specific on the commands to 3.3 and 3.5 since I don’t know the location of your JDK. An example location is “C:\Program Files\Java\jdk1.8.0_92”. Find your JDK and replace [JDK Home] with that location.

   Please remember that Microsoft Windows command prompt commands consider a space a break in the command. If your JDK home has a space in the name as the example above you will need to put the entire command up to “jar” in quotes.

   “C:\Program Files\Java\jdk1.8.0_92\bin\jar” xf jython-modules.jar Lib\javashell.py
10. Dustin Hammersmith July 22, 2016 at 1:51 pm

    I am having the same issue and when I go to run the script from the directory using the syntax C:\Program Files\java\jdk1.7.0_79/bin/jar xf jython-modules.jar Lib\javashell.py I get the response ” ‘C:\Program’ is not recognized as an internal or external command, operable or batch file. Please help me it seems I’m on the right track with your workaround but I can’t quite execute.

    I’m deploying on WLS 12.1.3 with BI Pub 11.1.1.9 JDK 7u79 and Windows Server 2012 R2
11. Chris DeBracy July 25, 2016 at 9:31 am

    Try enclosing the command line/path with quotes. The space between C:\Program and Files is causing a parsing problem, I imagine.
12. Muhammad Arshad December 25, 2016 at 1:09 am

    does the same workaround also work for Windows 10? or reverting to Windows 8 or server version is the only alternate?

This site uses Akismet to reduce spam. Learn how your comment data is processed.