JSS 8.7 Installer for Windows

[kmadriz]

Hello, I'm trying to update to JSS 8.7 but in the last Installation step it stops with this error: "There was an error installing the JSS, please check the JSSInstaller.log located at C:WindowsTemp":
: -------------------Tomcat7 Logs Configuration-------------------
: Checking if Logs directory exists...
: Error changing log paths.

What can I do? The installation rolled back.

[kmadriz]

This is the complete Log:

5/8/2013 12:58:55 PM : -------------------Checking for upgrade-------------------
5/8/2013 12:58:56 PM : -------------------Checking Port Requirements-------------------
5/8/2013 12:58:56 PM : Checking port 8080...
5/8/2013 12:58:56 PM : Port 8080 is not in use.
5/8/2013 12:58:56 PM : Checking port 8443...
5/8/2013 12:58:56 PM : Port 8443 is not in use.
5/8/2013 12:58:56 PM : -------------------Java Check-------------------
5/8/2013 12:58:56 PM : Checking for JDK and JRE environment variables...
5/8/2013 12:58:56 PM : Checking for JAVA_HOME...
5/8/2013 12:58:56 PM : Unable to find JAVA_HOME, checking for Java jdk...
5/8/2013 12:58:56 PM : Checking in C:Program FilesJava...
5/8/2013 12:58:56 PM : Found Java jdk at C:Program FilesJavajdk1.7.0_05
5/8/2013 12:58:56 PM : Checking for JRE_HOME...
5/8/2013 12:58:56 PM : Found JRE_HOME at C:Program FilesJavajre7
5/8/2013 12:58:56 PM : Checking for 64-bit Java...
5/8/2013 12:58:56 PM : Found required 64-bit Java.
5/8/2013 12:58:56 PM : -------------------JCE Requirement-------------------
5/8/2013 12:58:56 PM : Checking for Java Cryptography Extension...
5/8/2013 12:58:58 PM : Found required Java Cryptography Extension.
5/8/2013 12:58:58 PM : -------------------JCE Requirement-------------------
5/8/2013 12:58:58 PM : Checking for Java Cryptography Extension...
5/8/2013 12:59:01 PM : Found required Java Cryptography Extension.
5/8/2013 12:59:03 PM : -------------------Tomcat7 Configuration-------------------
5/8/2013 12:59:05 PM : Checking for Tomcat7 Windows Service
5/8/2013 12:59:05 PM : Tomcat7 Windows Service already exists. Attempting to delete Tomcat7 Windows Service...
5/8/2013 12:59:05 PM : Successfully deleted Tomcat7 Windows Service
5/8/2013 12:59:05 PM : Installing Tomcat7 Windows Service...
5/8/2013 12:59:06 PM : Successfully created the Tomcat Windows Service.
5/8/2013 12:59:06 PM : Configuring the Tomcat7 Windows Service to start automatically...
5/8/2013 12:59:06 PM : Sucessfully configured the Tomcat7 Windows Service to start automatically.
5/8/2013 12:59:06 PM : Setting JSS' memory usage...
5/8/2013 12:59:06 PM : Successfully changed JSS' memory usage: min=256 max=1024
5/8/2013 12:59:06 PM : Moving and unpacking JSS Web App...
5/8/2013 12:59:06 PM : Starting Tomcat7 Windows Service...
5/8/2013 12:59:10 PM : Successfully started Tomcat service.
5/8/2013 12:59:26 PM : Successfully unpacked ROOT.WAR.
5/8/2013 12:59:26 PM : -------------------Keystore Configuration-------------------
5/8/2013 12:59:26 PM : Searching for keytool.exe...
5/8/2013 12:59:26 PM : Creating keystore for Tomcat7...
5/8/2013 12:59:26 PM : Successfully created the Tomcat keystore.
5/8/2013 12:59:26 PM : -------------------Tomcat7 Logs Configuration-------------------
5/8/2013 12:59:26 PM : Checking if Logs directory exists...
5/8/2013 12:59:37 PM : Error changing log paths.

[benjamin_michae · Accepted solution]

Hey kmadriz

Lots of pretty rapid logging there regarding this issue. Fortunately, this has been seen before and we have documentation on the problem:

https://jamfnation.jamfsoftware.com/article.html?id=322

That should get you back to where you need to be!

[kmadriz]

Thanks Michael.

[andregignac]

Greetings, is this the same solution for trying to upgrade from 8.71 to 9.01 on Win 2008 R2 64-bit?

[dwandro92]

1. Perform an administrative install using the following command: MSIEXEC /A "<path to JSS Installer.msi>". Pick an install directory that you will remember (I just create a "Transformed" folder in the same folder as the MSI and install it there).
2. Navigate to the directory you performed the administrative install in and open the newly created MSI using an archive utility such as WinRAR or 7-Zip. Extract the file named "binary.update_log_files.vbs_1" to the directory you performed the administrative install in.
3. Open "binary.update_log_files.vbs_1" in your favorite text editor and find the following line near the top of the script (should be line 14): Do While Not checkBool AND i < 5
4. Change the above line to read as follows: Do While Not checkBool AND i < 30
5. Install the Microsoft Windows SDK for Windows 7 and .NET Framework 3.5 SP1.
6. Go to the program files location for the SDK and install Orca.msi
7. Navigate to the directory you performed the administrative install in and right-click the MSI, then select Edit with Orca
8. From the toolbar, select Transform > New Transform
9. In the Tables pane on the left, select Binary. Find update_log_files.vbs_1 in the Name column and double-click the cell to the right of it that says [Binary Data]. Click the browse button and select the newly modified "Binary.update_log_files.vbs_1" file. Verify that "Read binary from filename" is selected and press OK, then press OK again to overwrite the current contents of the stream.
10. From the toolbar, select Transform > Generate Transform and save the file in the same directory as the original installer and name it LogFix.mst
11. Open a command prompt window in the same directory as the original installer and run the following command: MSIExec /I "JSS Installer.mst" TRANSFORMS=LogFix.mst
12. The install should complete correctly now. If you run into different install errors (e.g. tomcat fails to start after the service is created), you may need to do the following and repeat step 11: - Open task manager and kill any open processes named tomcat7.exe and/or tomcat7w.exe - Delete the tomcat 7 service by opening a command prompt and running the following command: sc delete tomcat7 - Delete the C:Program FilesJSS folder

Sorry that this process can take a while, I would've simply uploaded the MST file but there's no "add attachment" option here. On the bright side, the resulting MST should be usable on any version of the JSS MSI until the problem is resolved. Hope this helps!