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 User gets: Unable to access. The filename may be illegal, the filename may already exist as a directory, part of the directory path may already exist as a file, the TEMP directory may not exist, or there may be insufficient privileges.
User gets: Unable to access. The filename may be illegal , the filename may already exist as a directory, part of the directory path may already exist as a file, the TEMP directory may not exist, or there may be insufficient privileges.
CMS-XML How to fix the Add Workfiles errors 'The path "ArchivePath" is not mapped by any available known server' and 'Unable to access. The filename may be illegal, ...'
How to fix the Add Workfiles errors 'The path "ArchivePath" is not mapped by any available known server' and 'Unable to access. The filename may be illegal , ...'
CMS-XML VM on UNIX/Linux cannot use SSH (Secure shell) when GUI is running in setuid mode
Setuid mode is a way for Version Manager to ensure all read and write operations for the repository (i.e. the files contained in the project databases) are performed by a single user ID, typically named "pvcs". Doing so allows access to the repository to get locked down to just that user ID, preventing unauthorized modifications to individual files in the repository outside using Version Manager applications. By default, Version Manager on UNIX/Linux installs with setuid mode enabled.
CMS-XML PVCS VM GUI on UNIX/Linux cannot run in setuid mode when tunneling X11 (X-Windows) through SSH (Secure shell)
Setuid mode is a way for Version Manager to ensure all read and write operations for the repository (i.e. the files contained in the project databases) are performed by a single user ID, typically named "pvcs". Doing so allows access to the repository to get locked down to just that user ID, preventing unauthorized modifications to individual files in the repository outside using Version Manager applications. By default, Version Manager on UNIX/Linux installs with setuid mode enabled.
CMS-XML VM: Error during authentication. You are not authorized for path "".
If you are not granted access to the Path Map you can't access any Project Database or archive inside of it, so this is an extra level of security. Because the same credentials need to satisfy both the Path Map and the Project Database(s) inside of it, you can be denied access to the Project Database if there is a mismatch between the authentication sources.
CMS-XML 401 unauthorized message received when using the JSON API URL
JSON API functions are accessed using the following format: http://AEserverName/jsonapi/getitem/1000/2 Alternatively, start with any of the following addresses:
CMS-XML RECOMPILE FROM BASELINE is NOT AUTHORIZED
Recompile of participating package where user has been denied security access to the (different) application of the associated complex package, fails with CMN1090A - Application access denied (referring to the application of the complex package). Contrary to this, a stage (and implied recompile) of the the same component is allowed. This is inconsistent.
CMS-XML ISPF long message for CMR7034I (area checkin not authorized) contains invalid data
A customer is reporting that they are receiving an invalid ISPF long message when a user request for an area-to-area checkin is rejected because the user does not have access to the associated security entity. Instead of receiving something like this:
CMS-XML You are not authorized to view this page - HTTP 401.1 Unauthorized access is denied due to invalid credentials
Solution 1) Create a new NT user account with the appropriate privileges and then use that user in IIS for anonymous access in the IIS > Web Site > Properties> Directory Security>Anonymous Access and Authentication Control > Edit > Anonymous Access Set this user's password to 'Password Never Expires'.
MS-WORD Understanding anonymous authentication and the IUSR account
Anonymous access, the most common Web site access control method, allows anyone to visit the public areas of a Web site while preventing unauthorized users from gaining access to a Web server's critical administrative features and private information. Anonymous authentication gives users access to a Web site without prompting them for a user name or password. When a user attempts to connect to a public Web site, the Web server assigns the user to the Windows user account called IUSR_computername, where computername is the name of the server on which IIS is running.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs