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 UpdateWithLock() appscript method doesn't lock item so it fails
line 4182. Resource Msg Id = IDS_MSG_ LOCKS _RECORDMUSTBELOCKEDBEFOREUPDATE The user must have the record locked before update. Instead of using UpdateWithLock() you will want to use the Lock() method, do your update, and then use UnLock() method.
CMS-XML Import process locked
If an import fails in the Application Administrator then the import process is not released and an error message is received telling the user the Process is still in use and therefore locked . The user can not run the import process again until the system is restarted.<\p>>
CMS-XML Importing Release Control solution gives "Failed to extract the solution. You do not have permission to delete the obsolete snapshot"
Log into the Application Repository ( http://server:8085/mashupmgr ). Switch to the Privileges view. Select your user, and verify that you have all privileges, including Delete Process App, Delete App/Orch, and Break Lock .
CMS-XML Dim12: Deploy: MDHNET4502541E Error: Unable to insert deployment lock for database
2012/05/29 21:45:42 UTC 1.016 T T3560 DDeployService::connectToDb: Connecting to database CM_TYPICAL@DIM12 on host MYSERVER as user dmsys ... 2012/05/29 21:45:48 UTC 6.909 T T3560 DDeployServiceLockImpl::dbInsertDeploymentLock: Caught a DbException: MDHNET4502287E Error: Failed to execute a statement.
CMS-XML Decision step operation fails during automatic execution
Lock for this record has been broken : We're sorry, Chad Support, but your lock on this record was broken . By using the back button you may be able to see the changes you were about to make. If your data has been cleared please re-enter it.
CMS-XML SRA Agent Install for connection via Relay fails to auto-configure correctly
The config file should contain a line containing the entered relay server host name locked /agent.brokerUrl=failover\:(ah3\://relayhost\:7916) Actual result:
CMS-XML Asynch orch failures leave the JMS record and the orch is unexpectedly and automatically re-run many times.
<transportSender name="jms" class="org.apache.axis2.transport.jms.JMSSender"> <parameter name="tscTopicConnectionFactory" locked ="false"> <parameter name="java.naming.factory.initial">org.jnp.interfaces.NamingContextFactory</parameter>
CMS-XML How to get a copy of the certificate chain and copy it to the certificate trust store ("PKIX path building failed" or similar SSL connection errors.)
Internet Explorer may display a warning about a problem with the security certificate: There is a problem with this website's security certificate Click Continue to this website. The browser will display some garbled text if the server and port you are connecting to is not a HTTP type service, but you will see either a lock or certificate error warning next to the location bar. Click the lock or location bar and View Certificate like below.
MS-WORD S141325-Upgrading to Release Control 6.0 WITH Using Old Data.docx
Switch to the Privileges view. Select your user, and verify that you have all privileges, including Delete Process App, Delete App/Orch, and Break Lock . Continue with STEP 3 : Install Release Control 6.0.
CMS-XML Error "Please check selected SRA application history. Request Status Failed."
<!--This will give out the timout of the configuration contexts, in seconds--> <parameter name="ConfigContextTimeoutInterval" locked ="false">120</parameter> ... <!--This will give out the timout of the configuration contexts, in seconds--> <parameter name="ConfigContextTimeoutInterval" locked ="false">120000</parameter>
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs