1 - 25 of 101 results for offering:'METADATASRV'
Previous   |    1 , 2, 3 ... Last   |    Next >
Sort by:
Date | Relevance


51911 - Troubleshooting SASŪ Metadata Server authentication issues in SASŪ 9.3 and later- Usage Note

It is often necessary to see more detailed logging of the authentication process on the SAS Metadata Server. In particular, detailed logging is helpful in troubleshooting unexpected or erroneous behavior in for the ...

http://support.sas.com/kb/51/911.html, 33KB


50663 - When you use the sas.servers script to start all SASŪ servers as UNIX processes, the script reports that the metadata server did not start- Usage Note

When you use the sas.servers script file to start all SAS servers as UNIX processes, the script might report that the SASŪ Metadata Server did not start. The metadata server log might not show any errors. In this ...

http://support.sas.com/kb/50/663.html, 26KB


35088 - The error "NO JAVA EXECUTABLE COULD BE FOUND IN ANY CONFIGURED LOCATION" occurs when you are using the SASŪ Migration Utility- Usage Note

The SAS Migration Utility must be run on every machine that is running SASŪ 9.1.3 SP4 Intelligence Platform, and it requires that the same Java Runtime Environment (JRE) be installed. If a valid version of the JRE is ...

http://support.sas.com/kb/35/088.html, 29KB


46531 - Special characters might cause the Platform Object Framework batch import and export utilities to fail on Z/OS with a syntax error.- Usage Note

When entering batch export and import commands (ImportPackage or ExportPackage) on z/OS systems, you might need to precede special characters with a backslash character (. Otherwise a syntax error will be produced.

http://support.sas.com/kb/46/531.html, 27KB


46410 - The Properties of a Recovery operation shows a misleading exception the first time a SASŪ Metadata Repository recovery is performed- Usage Note

The Recovery properties from the first metadata restore displays a message indicating that an element is missing from the Backup Manifest.

http://support.sas.com/kb/46/410.html, 30KB


45508 - SASŪ Metadata Server in SASŪ 9.3 fails to start if MetadataServerBackupManifest.xml has been moved or deleted- Usage Note

The SASŪ Metadata Server in SASŪ 9.3 will fail and the SAS environment is not available anymore if the MetadataServerBackup.Manifest.xml file is being deleted.

http://support.sas.com/kb/45/508.html, 30KB


45206 - Slow performance when updating table metadata- Usage Note

When updating table metadata using PROC METALIB, or the Update Metadata menu item in SASŪ Management Console or SASŪ Data Integration Studio, you might experience a longer time to execute than when you initially ...

http://support.sas.com/kb/45/206.html, 31KB


46007 - The option to define content mapping for a SASŪ Metadata folder to a location on the file system is deprecated in SASŪ 9.3- Usage Note

Beginning with SASŪ 9.3, you may only assign content mapping for a SASŪ Metadata folder to the SASŪ Content Server (WebDAV).

http://support.sas.com/kb/46/007.html, 30KB


45703 - The SASŪ 9.3 Metadata Server in z/OS operating environments might report incorrect time values- Usage Note

The 64-bit version of the SAS 9.3 Metadata Server might report incorrect time values.

http://support.sas.com/kb/45/703.html, 27KB


45686 - New SASŪ Metadata Server logging functionality is available with SASŪ 9.2 TS2M3 hot fix- Usage Note

With the installation of the fix referenced in the Hot Fix tab, you can now configure the logging for your SAS Metadata Server to audit changes to public SASŪ Metadata objects.

http://support.sas.com/kb/45/686.html, 27KB


43649 - Recovering an Unresponsive SASŪ Metadata Server- Usage Note

Recovering an Unresponsive SASŪ Metadata Server 9.3

http://support.sas.com/kb/43/649.html, 42KB


44704 - Active Directory account locked after one login attempt using a bad password- Usage Note

When configured for Direct Authentication to Active Directory, the SASŪ Metadata Server attempts to form a qualified account with which to authenticate with Active Directory. For SAS 9.2, the Metadata Server supports ...

http://support.sas.com/kb/44/704.html, 34KB


45294 - Users are able to see plug-ins or tasks in client applications when they are not granted the corresponding capabilities by any role- Usage Note

If a user has insufficient authorizations on the /System folder or its subfolders in metadata, they might receive errors or be given access to features of client applications that they should not see, even if they are ...

http://support.sas.com/kb/45/294.html, 30KB


42980 - In-database processing with the Metadata LIBRARY engine (META) is not supported in SASŪ 9.2- Usage Note

In-database processing that uses the metadata LIBRARY engine (the META engine) is not supported in SAS 9.2. Support for this feature is available with SAS 9.3.

http://support.sas.com/kb/42/980.html, 28KB


41877 - Memory requirements for SASŪ Metadata Server- Usage Note

SAS recommends that the SASŪ Metadata Server be run on a 64?bit machine whenever practical. The standard SAS Enterprise Excellence Center minimum recommendation for SAS hardware is 4GB/core (8GB minimum.) This should ...

http://support.sas.com/kb/41/877.html, 29KB


42145 - How to change SMTP server authentication information that is entered during configuration of the SASŪ Metadata Server- Usage Note

When you configure a SAS 9.2 Metadata Server, the SASŪ Deployment Wizard requests information for an SMTP server, including authentication information if needed. After the configuration is completed, if the ...

http://support.sas.com/kb/42/145.html, 30KB


43378 - META Libname Engine does not support SASŪ Catalog access- Usage Note

The SAS Metadata Libname Engine is a thin layer engine which receives commands and passes them to the underlying data access engine for performing the tasks. The META engine is capable of interfacing with tables and ...

http://support.sas.com/kb/43/378.html, 31KB


41983 - You cannot log on with a local account when you connect to a SASŪ Metadata Server that is configured to use direct LDAP authentication- Usage Note

You cannot log on with a local account when you connect to a SASŪ Metadata Server that is configured to use direct LDAP authentication.

http://support.sas.com/kb/41/983.html, 28KB


42727 - The SASŪ Metadata Server I/O subsystem has returned error message 'ERROR: Library TMP000 does not exist.'- Usage Note

When installing a new SASŪ environment, an I/O error might appear in the SASŪ Metadata Server log when the server is started for the first time.

http://support.sas.com/kb/42/727.html, 30KB


40599 - Assigning users to a custom role that has limited capabilities might still have access to additional capabilities even after applying the custom role- Usage Note

You can create a custom role that grants access to only a particular plug-in within SASŪ Management Console and then assign that role to users. However, those users might still have access to other plug-ins than the ...

http://support.sas.com/kb/40/599.html, 29KB


35444 - ERROR: Write access to member RPOSMGR.RPOSCTRL.DATA is denied.- Usage Note

The following messages may appear in the SASŪ Metadata Server log: PauseRepository Id=A0000001, Name=REPOSMGR, State=READONLY. The I/O subsystem has returned error message 'ERROR: Write access to member RPOSMGR. ...

http://support.sas.com/kb/35/444.html, 28KB


40834 - The Replication Wizard and the OMAPORT macros in SASŪ 9.2 have been deprecated- Usage Note

SAS has deprecated the metadata replication tool (the Replication Wizard) in SASŪ Management Console for SAS 9.2, as well as the %OMAPORT macros used for porting a SASŪ Metadata Repository created in one host ...

http://support.sas.com/kb/40/834.html, 30KB


36245 - "A lock is not available....lock held by another process" error occurs when running the %OMABAKUP macro- Usage Note

Running the SAS Metadata Server in a Windows 2003 Failover Cluster environment can cause the %OMABAKUP macro to produce errors regarding locked data sets.

http://support.sas.com/kb/36/245.html, 28KB


32132 - The SASŪ Migration Utility requires a shared network location for the migration package- Usage Note

The SAS Migration Utility must be able to read and write to a single shared location from each server tier that will be migrated. For example, the SASŪ Metadata Server and the middle tier must be able to read and ...

http://support.sas.com/kb/32/132.html, 28KB


36575 - New XML tags are available for the omaconfig.xml file to analyze and repair a damaged SASŪ Metadata Repository- Usage Note

There are two new tags that can be added to the omaconfig.xml file for the SASŪ Metadata Server. The first, &ltDEBUG ANALYZE_METADATA_FILES="y"/, allows you to analyze your SAS Metadata Repository files for damage. ...

http://support.sas.com/kb/36/575.html, 29KB

1 - 25 of 101 results for offering:'METADATASRV'
Previous   |    1 , 2, 3 ... Last   |    Next >