# ProcessOlap - The attribute Unit does not have any members

# Problem

There will be times that when running the ProcessOlap command, the following error occurs:

Example
There were errors during execution:
 The attribute unit does not have any members.
 Server: The current operation was cancelled because another operation in the transaction failed.
 Internal Error: The opreration terminated unsuccessfully.
 OLE DB error: OLE DB or ODBC error: Operation cancelled; HY008.
 Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of
'Time', Name of 'Time' was being processed.
 Errors in hte OLAP storafe engine: An error occured while the 'Start of Hour' attribute
of the 'Time' dimension from the 'OpeniT' database was being processeed.

# Resolution

Use the following list of suggestions to troubleshoot the issue:

# Check if data was loaded and processed

Follow these instructions to check if data was loaded and processed from the the Open iT Core Server database:

  1. Go to the Analysis Server Log directory, which is by default in C:\Program Files\OpeniT\Analysis Server\Log.

  2. Open the OpeniT.Server.Etl.Console.log log file.

  3. Look for the latest execution of ProcessSQL.

2021-02-24 06:00:12,886 +08:00 INFO ProcessSqlJob - Open iT Analysis Server Version:
 9.6.46 (1debb9c3)
2021-02-24 06:00:12,898 +08:00 INFO ProcessSqlJob - Job started. Running as SVG\jplanas
2021-02-24 06:00:13,016 +08:00 INFO ProcessSqlJob - Processing SQL data warehouse.
Please wait...
2021-02-24 06:00:13,038 +08:00 INFO ProcessSqlJob - Finished Loading Factory Files
for Labeling.
2021-02-24 06:00:13,072 +08:00 INFO ProcessSqlJob - Finished running procedure
BackupProductLabels. Affected rows: -1.
2021-02-24 06:00:13,114 +08:00 INFO ProcessSqlJob - Finished running procedure
ModifyLOViews. Affected rows: -1.
2021-02-24 06:00:13,158 +08:00 INFO ProcessSqlJob - Finished running procedure
MakeSmsRaw. Affected rows: 0.
2021-02-24 06:00:13,265 +08:00 INFO ProcessSqlJob - Finished running procedure
InsertNewVendorDaemon. Affected rows: 0.
2021-02-24 06:00:14,219 +08:00 INFO ProcessSqlJob - Finished running procedure
InsertNewLicenses. Affected rows: 0.
2021-02-24 06:00:14,651 +08:00 INFO ProcessSqlJob - Finished running procedure
InsertNewUsersAndHosts. Affected rows: 0.
2021-02-24 06:00:15,565 +08:00 INFO ProcessSqlJob - Finished running procedure
InsertNewEpochs. Affected rows: 1.
2021-02-24 06:00:15,849 +08:00 INFO ProcessSqlJob - Finished running procedure
InsertNewTimeData. Affected rows: 0.
2021-02-24 06:00:15,879 +08:00 INFO ProcessSqlJob - Finished running procedure
ProcessMaps. Affected rows: -1.
2021-02-24 06:00:16,013 +08:00 INFO ProcessSqlJob - Finished running procedure
InsertProductAndFeatureLabelProperty. Affected rows: 0.
2021-02-24 06:00:16,284 +08:00 INFO ProcessSqlJob - Finished running procedure
MakeXPropertyTable User. Affected rows: 0.
2021-02-24 06:00:16,428 +08:00 INFO ProcessSqlJob - Finished running procedure
MakeXPropertyTable Application. Affected rows: 0.
2021-02-24 06:00:16,440 +08:00 INFO ProcessSqlJob - Finished updating FileStatus.
Affected rows: 0.
2021-02-24 06:00:16,442 +08:00 INFO ProcessSqlJob - Job done. Duration 03.53s
  1. Verify that the InsertNewLicenses affected rows is greater than zero (0).

  2. If the affected rows are zero, run the command RunEtl and make sure that data is loaded and processed.

# Check the configured Core Server Database Path

Follow these instructions to check if the configured Core Server database path is correct:

  1. Go to the Configuration page under the Administration tab of the Analysis Server web interface.

  2. Look for the configuration key Root.Etl.CoreDatabasePath.

  3. Verify that the value of the key is correct.

    Analysis Server Troubleshooting: Check Core Server Database Path

    Analysis Server Troubleshooting: Check Core Server Database Path

  4. If the value is incorrect, update the configuration key and execute the command RunEtl using the Analysis Server console.

We value your feedback!

Please take a few minutes to complete our survey and share your thoughts on your recent experience with our documentation.

Take survey

Close