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 Cannot checkout files from CA machine
Cannot checkout files from CA machine
CMS-XML Cannot validate users on HP-UX trusted mode OS
Cannot validate users on HP-UX trusted mode OS
CMS-XML Unable to validate user on OS/390 USS
ChangeMan DS does not validate passwords for user when adding an area on OS/390 USS. When using the remote directory browser, it appears that the agent does not have the permission to check security, so a message 'Failed to validate user login' is received. The agent is being started with an operator account so it is a zero account which is as close to root as you get on USS.
CMS-XML Merge-to-Production on a file that is not checkout increments the version.
Merge-to-Production on a file that is not checkout increments the version.
CMS-XML VAJava 3.5 does not show visual information when checking out file.
In order for the information to display after check out , it is important to set the 'generate meta data method' check box to enabled. This is found under Window --> Options, select Visual Composition, then select Code Generation. Enabling this option will allow you to export as .java files and maintain the visual information by generating a getBuilderData() method.
CMS-XML Modified 2nd Checked Out File On Merge (Pending Set) Doesn't Wait For Approval
If you have a production area which is checked out to Dev A and a second check out performed for Dev B and checkin the file from Dev A, all files will be in a requested state waiting for approval. Once the approval has been made for the files in Dev A and if Dev B checks in the files, a merge will appear for the files that were changed. Then, the only files that wait for the approval are the files that were not changed (no merge was performed on them).
CMS-XML CLI - CMNXFER - Second Checkout does not work using the answer values
Checkout of files from Production to Development area does not work when file(s) are already checked out. The '-oversec:y' option to continue on a second checkout does not work and errors. e.g. Error #-32: The file Prod:D:\Prod_Area\CMP CMP0001E.ASP is already checked out .
CMS-XML Check out receiving prompt to overwrite when no changes are in development
When performing a check out of a frozen release from within WSAD, then performing a "Cancel Checkout" operation and then performing the checkout operation again, you will be continually prompted to "overwrite" the file in the development location when there is no difference. Also, removing the contents from the folder and performing a check out of a frozen release from the GUI, performing a cancel check out and then repeating the checkout operation, you will be prompted to "merge or overwrite" when the source and target are the same.
CMS-XML CMNXFER - Second Checkout does not work using the answer values
area:Kris_Prod -frompath:"D:\Kris_Murthy_Prod_Area" -toarea:Kris_Dev -topath:"C: \KrisDevelopment\Devarea" -desc:" Checkout " -oversec:y -verbose Answer: ChangeMan DS Transfer Command, Version 5.6.0
CMS-XML Ability to undo all checkouts of an user
DS Administrators need the ability to cancel checkout's or undo checkouts of employees who are no longer there
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs