Page Comparison

...

1. In which process does the error occur?
   1. Creating a source → go to 2
   2. Pushing metadata → go to 3
   3. Pushing data → go to 4
   4. Other → go to 5
      
      
2. Error in creating a source. Check the following steps:
   1. Is there an error in the OneStream Error Log? (see System tab → Error Log)
   2. If the error is about communication with the CXO OneStream Web API, check the following:
      1. Is the URL to the Web API correct in settings?
      2. Is the URL to the Identity Server correct in settings?
      3. Is the secret properly created in Identity Server and configured in the OneStream dashboard?
      4. Is the CXO OneStream Web API running properly? (see IIS on the CXO machine)
      5. Is there an error message in the Web API logging? (see OneStream Web API logging in Configurator) → Contact support with the error message from Web API logging at the ready.
      6. Is there any firewall, gateway, etc. in between that is not properly configured?
   3. If the error is about not being able to find a source with the same name in CXO, check the following:
      1. Is there are source of type OneStream created in CXO? (see Source System Manager on the CXO machine)
      2. Is there a record in the Sources table of the OneStream configuration database with that name already? → Delete the record from the Sources table and try again.
      3. Is there an error message in the Web API logging? (see OneStream Web API logging in Configurator) → Contact support with the error message from Web API logging at the ready.
   4. Does it complain about GUID not in the correct format?
      1. Check whether the Application ID in the settings is configured properly. Make sure it matches the ID of an application in the CXO master database
         
         
3. Error in metadata. Check the following steps:
   1. Is there an error in the OneStream Error Log? (see System tab → Error Log)
   2. If yes, analyze the error message. If it seems like it cannot push data to the CXO OneStream Web API, check the following:
      1. Is the CXO OneStream Web API running properly? (see IIS on the CXO machine)
      2. Is there an error message in the Web API logging? (see OneStream Web API logging in Configurator) → Contact support with the error message from Web API logging at the ready.
      3. If the service is running, but there is no error in the logging then there's probably something infrastructure-related going wrong in communication between OneStream and CXO (firewall issue, gateway, etc.)
   3. If there is an error message in the OneStream logging but it does not relate to communication with the CXO OneStream Web API, there's something wrong with our business rule code → Contact support with the error message from OneStream Error Log at the ready.
      
      
4. Error in data. Check the following steps:
   1. What is the status of the extraction process:
      1. ExtractionFailed → go to b.
      2. DataUploadFailed → go to c.
      3. Process Cube Pending → go to d.
      4. Process Cube Failed → go to e.
      5. Warning → go to f.
   2. Extraction of data from the OneStream system to a file on disk failed, check the following:
      1. Is there an error in the OneStream Error Log? (see System tab → Error Log)
      2. Analyze the error. Could be something easily fixable, like a full disk.
      3. If not, then → Contact support with the error message from OneStream Error Log at the ready.
   3. Push from file on disk to CXO OneStream Web API failed, check the following:
      1. Same Is this a scheduled data job? If so, please specify a server to run the scheduled task as described in OneStream Scheduling - Documentation - Confluence (atlassian.net) 
      2. If this is a manual process, or if the previous point didn't resolve the issue, please follow the same steps as for metadata failing → check steps 3a, 3b and 3c.
   4. Data is uploaded successfully but the cube processing is not started, check the following:
      1. Is it a status from an older job? It might be an inconsistency in the progress reporting.
      2. Is the CXO OneStream Processing Service running properly? (see Services on the CXO machine)
      3. Is there an error message in the Processing Service logging? (see OneStream Processing Service logging in Configurator) → Contact support with the error message from Processing Service logging at the ready.
   5. Cube processing is started but failed, check the following:
      1. Is there an error message in the Processing Service logging? (see OneStream Processing Service logging in Configurator)
      2. Does the error make sense from a functional perspective? Maybe it complains about missing members or anything that require a new metadata push.
      3. If not, then → Contact support with the error message from Processing Service logging at the ready.

   6. Full process is completed, but ended with a warning. This happens when data was pushed on members that do not exist in the metadata, check the following:

      1. There should be a warning in the OneStream Error Log saying what members are missing. (see System tab → Error Log)

      2. Push the correct metadata and try data extraction again.

...

• Make sure that the connectionString to the factDB in "OneStreamAdapter ConfigurationDB->Source"  table is the same as connectionString to factDB from "cxo_repositories DB"
• Make sure that OneStreamAdapaterProcessingService  is up and running

OneStream Scheduler is not working while manual loads do work

• Please check the data management settings in OneStream. The same server should be used for scheduled tasks as for manual tasks.