Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Data Insight for Sharepoint upgrade - 4.0.1 failed

Created: 30 Oct 2013 • Updated: 11 Nov 2013 | 1 comment
ndaniel71's picture
This issue has been solved. See solution.

Working with a client now on upgrading their DataInsight production servers.

The Manager, Collector/indexer upgrades including about 20 agents were all successfull. Moving to upgrade the Sharepoint farm per documenation we uninstalled 4.0 and ran the installer for 4.01 and it failed. We used the same procedures (with exception to uninstalling DI 4.0) and Admin account to install DI 4.0 just a month ago and did so successfully.

Below is the error log followed by our installation procedures. Any assistance would be appreciated.

I will only include where the errors in the log begin as its a large log (The complete log is attached). It seems an issue with JRE

JRE is packed
Unpacking JRE
jre\bin\unpack200.exe
-r "jre\lib\rt.jar.pack" "jre\lib\rt.jar"
waiting for unpack200 to finish
unpack done
pack path doesn't exists
jre\bin\unpack200.exe
-r "jre\lib\charsets.jar.pack" "jre\lib\charsets.jar"
waiting for unpack200 to finish
unpack done
jre\bin\unpack200.exe
-r "jre\lib\plugin.jar.pack" "jre\lib\plugin.jar"
waiting for unpack200 to finish
unpack done
jre\bin\unpack200.exe
-r "jre\lib\deploy.jar.pack" "jre\lib\deploy.jar"
waiting for unpack200 to finish
unpack done
jre\bin\unpack200.exe
-r "jre\lib\ext\localedata.jar.pack" "jre\lib\ext\localedata.jar"
waiting for unpack200 to finish
unpack done
jre\bin\unpack200.exe
-r "jre\lib\jsse.jar.pack" "jre\lib\jsse.jar"
waiting for unpack200 to finish
unpack done
Unpacking JRE done
JRE dir: C:\Users\SVC_SH~1\AppData\Local\Temp\5\e4j8C51.tmp_dir1382985889\jre
LoadDLL (0, C:\Users\SVC_SH~1\AppData\Local\Temp\5\e4j8C51.tmp_dir1382985889\jre, 0)
Got JRE location C:\Users\SVC_SH~1\AppData\Local\Temp\5\e4j8C51.tmp_dir1382985889\jre (java exe: 0)
MinVersion: 1.6, MaxVersion:
Trying to load JVM-DLL from c:\users\svc_sh~1\appdata\local\temp\5\e4j8c51.tmp_dir1382985889\jre\bin\java.exe
Setting PATH C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Windows Imaging\;e:\Program Files (x86)\Smart Projects\IsoBuster;c:\users\svc_sh~1\appdata\local\temp\5\e4j8c51.tmp_dir1382985889\jre\bin
Trying c:\users\svc_sh~1\appdata\local\temp\5\e4j8c51.tmp_dir1382985889\jre\bin\hotspot\jvm.dll (exists 0)
Trying c:\users\svc_sh~1\appdata\local\temp\5\e4j8c51.tmp_dir1382985889\jre\bin\client\jvm.dll (exists 1)
Failed with error code 2
Trying c:\users\svc_sh~1\appdata\local\temp\5\e4j8c51.tmp_dir1382985889\jre\bin\server\jvm.dll (exists 0)
Trying c:\users\svc_sh~1\appdata\local\temp\5\e4j8c51.tmp_dir1382985889\jre\bin\classic\jvm.dll (exists 0)
Trying c:\users\svc_sh~1\appdata\local\temp\5\e4j8c51.tmp_dir1382985889\jre\bin\jrockit\jvm.dll (exists 0)
Setting PATH C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Windows Imaging\;e:\Program Files (x86)\Smart Projects\IsoBuster
Setting PATH C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Windows Imaging\;e:\Program Files (x86)\Smart Projects\IsoBuster;c:\users\svc_sh~1\appdata\local\temp\5\e4j8c51.tmp_dir1382985889\jre\bin\..\jre\bin
Trying c:\users\svc_sh~1\appdata\local\temp\5\e4j8c51.tmp_dir1382985889\jre\bin\..\jre\bin\hotspot\jvm.dll (exists 0)
Trying c:\users\svc_sh~1\appdata\local\temp\5\e4j8c51.tmp_dir1382985889\jre\bin\..\jre\bin\client\jvm.dll (exists 0)
Trying c:\users\svc_sh~1\appdata\local\temp\5\e4j8c51.tmp_dir1382985889\jre\bin\..\jre\bin\server\jvm.dll (exists 0)
Trying c:\users\svc_sh~1\appdata\local\temp\5\e4j8c51.tmp_dir1382985889\jre\bin\..\jre\bin\classic\jvm.dll (exists 0)
Trying c:\users\svc_sh~1\appdata\local\temp\5\e4j8c51.tmp_dir1382985889\jre\bin\..\jre\bin\jrockit\jvm.dll (exists 0)
Setting PATH C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Windows Imaging\;e:\Program Files (x86)\Smart Projects\IsoBuster
ERROR: Could not get DLL-Handle.
ERROR: Could not load functions
ERROR: Could not load bundled JRE. Trying to find another JRE.
LoadDLL (0, (null), 0)
Searching for a JVM
GetTempPath returned 39 (last error 3)
make dir returned -1
Testing location .\jre (type B)
checkJavaExe (\\tsclient\c\sharepoint_agent_data_insight_4.0rp1\jre\bin\java.exe, [out], 1.6, , 1)
file doesn't exist
checkJavaExe returning 0
GetTempPath returned 39 (last error 183)
make dir returned -1
Testing location .\jre (type R)
checkJavaExe (\\tsclient\c\sharepoint_agent_data_insight_4.0rp1\jre\bin\java.exe, [out], 1.6, , 1)
file doesn't exist
checkJavaExe returning 0
GetTempPath returned 39 (last error 183)
make dir returned -1
Testing location  (type Y)
GetTempPath returned 39 (last error 183)
make dir returned -1
Testing location JAVA_HOME (type E)
GetTempPath returned 39 (last error 203)
make dir returned -1
Testing location JDK_HOME (type E)
Testing relative location .\jre
Search sequence finished
ERROR: No JVM found
ERROR: Could not find another JRE.
 

Here is our Sharepoint 2010 installation procedure:

1. Logon to the SharePoint farm machine where the SharePoint agent has been previously installed.

2. Uninstall the old agent using the "Add/Remove Programs" applet in the Control Panel.

3. Unzip the patch files to a temporary folder. In this folder, locate the SharePoint agent installer.

The installer is called either: Symantec_DataInsight_sharepoint2010_40RP1_4_0_0_4007.exe

4. Launch the installer to install the new agent.  

Verify the installation:

In the Central Administration console, click the Sytsem Settings.

Under the Farm Management page, select Manage Farm Solutions.

Verify that the status for Data Insight solution for SharePoint, sdispwebsvc.wsp, is set to Deployed.

Click the link for the solution. Verify that the solution is deployed to all the

front-end Web servers in the farm by checking the value of “DeployedTo” field.

 

Operating Systems:

Comments 1 CommentJump to latest comment

ndaniel71's picture

Solved - The problem was UAC and executing the update file with Admin rights Run As. Silly as the admin account should have them but UAC does some quirky things at time.

SOLUTION