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 Dim10: Dimensions 10.1.1 web client cannot build baseline. Get error: "There are no targets to build for this build configuration."
Dim10: Dimensions 10.1.1 web client cannot build baseline. Get error: "There are no targets to build for this build configuration."
CMS-XML RLC: Error "PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target" when not using SSL
RLC: Error "PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target " when not using SSL
CMS-XML km-dim 10 : build Z/os : Error : Targets specified should be no more than 16383 characters
It seems that we reached the limit of the number of items to build at one time.
CMS-XML Dim: ORA-01502: index "index_name" or partition of such index is in unusable state COR0004731E Error: failed to query details for build targets
When building an item, an error occurs of ORA-01502: index <index_name> or partition of such index is in unusable state COR0004731E Error: failed to query details for build targets
CMS-XML Dim10: Build: Problem building baseline "ERROR: Target not found"
The directories were defined correctly in the Build Configuration, however the target directory was set to read only. Specifying the target directory as writeable resolved the issue.
CMS-XML 10.1.3.x : z/os build with using pre-script => MDHSB160225E Processing resulted in no targets being detected: if no other errors have occurred this indicates an invalid template
when executing a build configuration without pre-script, build ends susccessfully when adding to the build configuration the following pre-script : //* -----------------------------------------------------
CMS-XML IEW2606S error message from binder when target is PDS when building SQL components
Customers who wish to target their SQL component builds at a PDS can change 2 skels as follows: 1. CMN$$PLK - Should input the &&&&OBJECT dataset into the SYSIN. 2. CMN$$LNK - Should input the &&&&LOADSET dataset if prelink was run.
CMS-XML Dim2009R2: Build: File deployment status: Error: Target not found -
Connect to admin console, go to areas: Select the work area where the build will take place Assign the correct users or groups, which will need access to the area in order to run the build.
CMS-XML 14.3.3 / build => BCB1901000E Error: SOAP FAULT: SOAP-ENV:Client"No connection could be made because the target machine actively refused it."
BCB1901000E Error: SOAP FAULT: SOAP-ENV:Client"No connection could be made because the target machine actively refused it." COR1601012E The allocation of a build job by the SCBC failed with code -1; processing cannot continue COR3600433E Job Queue id = 0; Job Id = 0
CMS-XML Dim10-12: Build returns: 19BC1000E Error: SOAP FAULT: SOAP-ENV:Client"No connection could be made because the target machine actively refused it. ".
Ensure that under Network Administration in Admin Console has the port explicitly defined as a number. Also ensure that the port number is specified in the Network Node Connection between the server and the Node for the build area.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs