Find Answers

Filter Search Results
All Operating Systems:
All Products:

All Solution Types:
Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
  Results
CMS-XML WSDL definition files using the duration data type fail to be imported into Mashup Composer
WSDL definition files using the duration data type fail to be imported into Mashup Composer
CMS-XML Import to Composer fails with message "Failed to Import Mashup: Circular type reference"
If already in Composer then it can be deployed successfully. This occurs if the mashup contains a wsdl schema contains a complex type with an element reference to a simple type. For example:
CMS-XML Composer crashes with message: Failed to import process app. Name 'EventDefinitionSource' is already used
4) Add new web service created from the external event WSDL 5) Export the process app into the MSD file 6) Import this MSD file back to Composer
CMS-XML Failed to Import Mashup error
When using Mashup Composer and trying to check an item into the repository the user may receive: Failed to import mashup: Could not find file 'C:\Documents and Settings\user.name\Local Settings\ApplicationData\Serena\Studio\Repository\Local\Serena.Studio.Framework.ObjectModel.ModelApplication\f5b1ac1a-e42f-46b0-96fd-6506b52abee5\0.S'
CMS-XML Failed to import mashup: Object Reference not set to an instance of an object
Exporting a mashup that contains a WSDL, and then trying to import it into Composer in another environment will generate an error.
CMS-XML When importing a .msd file into Composer you may see the following error. Failed to import process app because of the following issues: The Application Definition entry is not valid
When importing a .msd file into Composer you may see the following error. Failed to import process app because of the following issues: The Application Definition entry is not valid
CMS-XML SBM: After merge, importing process app fails with "Object reference not set to an instance of an object"
This was seen after merging two process apps together. When importing the final MSD, Composer fails with error:
CMS-XML Error on import of a Process App to Composer - Error: ... Could not locate resource ... or resource is corrupt
If you get errors similar to below when importing an blueprint or snapshot to Composer ( msd or mss) then see the resolution below. Failed to import process app . Exception Details:
CMS-XML Import of MSD (blueprint) to Composer fails with Object reference not set to an instance of an object.
When trying to import a Process App if you get a similar error to below it could be because there is an element reference in the a pre- or post transition webservice call datamapping for an element that does not exist. Exception Details: ------------------
CMS-XML Error: Root element is missing - importing a Process App into Composer after generating it from a Get from AE if any of your Process Apps contain a Reset Data Source
If you create any Rest Data Source in ANY Process app and deploy and then do a Get from AE ALL process apps will now fail when importing to Composer. They all contain this Rest Data Source (including the global) and will fail with error "Root element is missing".
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Product Demos

Dimensions RM: Importing Requirements
This demonstration show you how to import requirements from CSV, Microsoft Word, and Microsoft Excel files to Dimensions RM.

Additional Assistance

  • Submit a Case Online
  • FAQs