Device
Setup Fails Due to Client Issues
Problem
The setup of a device fails when using the setup package.
Analysis
The status of installation is logged in the file C:\Program Files\SAP\SAP NetWeaver Mobile MassDeviceSetup\install.log. Use this file together with the installation.properties file to analyze problems that occurred during installation.
The log file contains the following message types:
Messages types in install.log
Message type |
Description |
INFORMATION |
Information messages are messages that log information |
ERROR |
Error messages indicate that the device setup encountered an error and that installation failed. |
WARNING |
Warning messages indicate that a particular step could not be performed but this did not have an impact on the device setup process. |
SUCCESS |
Success messages indicate the Step was successfully executed. |
Case 1
Problem
The log file shows the following error message:
ERROR: Software Folder not found at C:\Program Files\SAP\SAP NetWeaver Mobile MassDeviceSetup\software
When you set up a device, MassDeviceSetup.exe expects that the software folder specified above is present as a subfolder of the device folder for which the setup was performed. If this folder is not present, then the device setup fails.
Corrective measure
Copy the software folder to the device folder, from the location where the installation of mass device setup was triggered.
As an example, if after performing the Device Setup the folder was copied to C:\DeviceSetup\{DeviceName_DeviceID}, then copy the software folder as a subfolder to this folder.
Case 2
Problem
The log file shows the following error message:
ERROR: Unable to read installation.properties.
Corrective measure
The installation.properties file is missing and the mass device setup on the server needs to be triggered again to obtain the file.
As a workaround, you can create the installation.properties file manually in the MassDeviceSetup folder.
...
1. Find the list of all mobile components for which the device was setup from the DOE Portal.
2. Create a new blank file named install.properties.
3. Create entries for the components to be installed according to the following rules and examples:
The order of installation sequence is JRE, MAXDB, and FRAMEWORK. Each of these mobile components can have pre and post installations. For example, JRE can have a pre installation as a batch file that performs some registry entry. In addition, this batch file can have a pre and post installation.
The JRE has a preinstallation mobile component called UpdateRegistry. Then the sequence of installation on the Laptop is UpdateRegistry.bat, JRE1_5.exe, MaxDB_7_6.zip, and FW.zip.
The installation.properties file contains the entries as shown below:
ADDON=UpdateRegistry.bat
JVM=jre-1_5_0_08-windows-i586-p.exe
DB=MaxDB_7_6.zip
FRAMEWORK=sap.com~tc~mobile~setup~win32.zip
MCDNAME_VERSION=sap.com~test~5model.sda
MCDNAME_VERSION=sap.com~devre_cust.sda
Each mobile component is a file and the name of that file can be obtained from the property COMPONENT_FILE_NAME.
4. Copy the file to the MassDeviceSetupfolder of the device.
Case 3
Problem
The log file shows the following error message:
ERROR: Unable to read JRE Path from registry
Corrective measure
The JRE registry cannot be read. This can be because JRE installation failed. Perform the following checks to see why the JRE installation failed.
...
1. Check if the installation.properties file has an entry for JRE. If not, trigger mass device setup again from the server to see why the installation.properties file was generated incorrectly.
2. If the JRE entry is present in the installation.properties file, check if the file is present in the Software folder of the device. If not, the download of the JRE from the DOE had a problem.
Case 4
Problem
The log file shows the following error message:
ERROR: Unable to split installation.properties file
Corrective measure
The installation.properties file was not generated correctly on the server or was edited on the device. There is no corrective measure possible. Trigger the mass device setup again.
Case 5
Problem
The log file shows the following error message:
ERROR: Unable to invoke installation of Framework & MAXDB
Corrective measure
The above error could be due to the following:
· The MAXDB and Framework zip files were not downloaded.
· The framework zip file should contain two files setup.exe and setup.iss. This error is possible if the wrong build of the framework file was used.
· MAXDB zip file could be incorrectly packaged.
· Check if the installation has created a folder with the name FW inside the software folder in the installation directory of the mass device setup.
Open the file install.log. If the ResultCode=-3 the command line parameters passed to the installation were wrong or the framework failed to install in silent mode.
To check if the files uploaded are correct, install CFS and MAXDB manually on a laptop. This is only a precautionary step.
Case 6
Problem
The log file shows the following error message:
ERROR: Unable to execute ZipFolder.jar Java Program
Corrective measure
Check if there is a file called ZipFolder.jar inside the C:\Program Files\SAP\SAP NetWeaver Mobile MassDeviceSetup\lib folder. If not the MassDeviceSetup.exe that was build and delivered is incorrect. The error can only be corrected with the fix from the right build.
Performing the Setup again
To perform the setup again, first perform the following steps:
...
1. To open the registry, choose Start → Run and enter RegEdit.
2. In the registry, navigate to the following:
MyComputer → HKEY_LOCAL_MACHINE → SOFTWARE → Microsoft → Windows → CurrentVersion → Uninstall
3. Search for MassDeviceSetup.
In the left pane, you see the product ID of the mass device setup, in the right pane you see all properties.
4. In the right pane, right-click the Remove property and select Modify. Enter 0 as Value data.
5. Repeat the above step for the SystemComponent property.
6. Close the registry.
7. To remove the installation, choose Start → Control Panel → Add or Remove Programs.
8. Select SAP NetWeaver Mobile MassDeviceSetup and choose Change/Remove.
9. After taking the corrective steps described above, restart installation.