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


50138 - When you use an alias file as the CONFIG file, an error appears in the SASŪ 9.3 Metadata Server log- Problem Note

If you use an alias for the SAS CONFIG file with a SAS 9.3 Metadata Server on a z/OS system, this error occurs in the SAS Metadata Server log every time the alias file is referenced. ERROR: Unexpected error For ...

http://support.sas.com/kb/50/138.html, 27KB


51979 - Synchronizing identity data in metadata generates the error message "IdentityGroup with this name is being added and deleted"- Problem Note

The %MDUCHGV macro, one of the user import macros for managing identity information in metadata, generates the following error message when the distinguished name (DistinguishedName=value) for an identity group ( ...

http://support.sas.com/kb/51/979.html, 31KB


51423 - Using a long XMLSELECT search string in the SASŪ Open Metadata Interface might generate the error "The XMLSELECT options length is invalid"- Problem Note

When you use a long XMLSELECT search string in the SAS Open Metadata Interface, the following error might occur: The XMLSELECT options length is invalid. This error occurs when the internal buffer length is too small ...

http://support.sas.com/kb/51/423.html, 34KB


50673 - Searching in SASŪ Web Report Studio from the SAS Folders root folder might cause the SASŪ Metadata Server to become unresponsive- Problem Note

Searching for all objects in all folders results in an inefficient query. The total processing time for such a search is geometrically proportional to the size of the foundation repository. Therefore, the request might ...

http://support.sas.com/kb/50/673.html, 33KB


50467 - The SASŪ Metadata Server log contains an error that the CPU serial is unlicensed even though the serial number matches the setinit information- Problem Note

When you are using SASŪ 9.3 (M2) and you start the SAS Metadata Server, you might see the following message in the server log: The SAS System is executing on a processor (CPU) whose model name, model number, and serial ...

http://support.sas.com/kb/50/467.html, 27KB


50277 - SASŪ Metadata Server alert e-mail fails with the message "An attempt to send an ALERT EMAIL to 'userid@domain.com' has resulted in ''"- Problem Note

SAS Metadata Server alert e-mail fails when it is configured for a mail server that requires authentication.

http://support.sas.com/kb/50/277.html, 30KB


49607 - The maximum number of database connections is exceeded when you access databases that are registered in metadata- Problem Note

The following error message might occur when the maximum number of database connections is exceeded: [Error] CLI error trying to establish connection: The permitted number of client connections (510) has been ...

http://support.sas.com/kb/49/607.html, 30KB


49740 - The SASŪ Metadata Server might become unresponsive because of a memory overlay- Problem Note

The SAS Metadata Server might become unresponsive because of a memory overlay (segmentation violation). Both existing and new connections to the SAS Metadata Server might be unresponsive. You might also see a ...

http://support.sas.com/kb/49/740.html, 32KB


41093 - An error occurs and you cannot access an Oracle table when you use a schema name or a user ID that contains a dollar sign ($)- Problem Note

If an Oracle user ID or schema name contains a dollar sign (, you must add double quotation marks around the user ID or schema name when you register Oracle tables from SASŪ Management Console. After you register the ...

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


48647 - Libraries that are created with generic library templates in SASŪ 9.2 do not import incorrectly to SASŪ 9.3- Problem Note

Libraries that you create with the generic library template in SASŪ 9.2 do not import into SAS 9.3 correctly. However, the package file seems to import successfully. After you import a library, problems occur when you ...

http://support.sas.com/kb/48/647.html, 31KB


48142 - The SASŪ Metadata Server might not respond when you use SSL with direct LDAP authentication- Problem Note

When you configure for direct Lightweight Directory Access Protocol (LDAP) authentication over the Secure Sockets Layer (SSL), the SASŪ Metadata Server might stop responding to all requests. The server's lack of ...

http://support.sas.com/kb/48/142.html, 31KB


47945 - The DATA step function METASEC_APPLYACT fails to apply an Access Control Template to an object- Problem Note

Submitting the METASEC_APPLYACT function in a SASŪ 9.3 (TS1M2) Foundation client fails. Under Windows, the client returns the error

http://support.sas.com/kb/47/945.html, 31KB


45139 - Unable to connect to the SASŪ Metadata Server when using direct authentication to a load-balanced LDAP server using SSL- Problem Note

The SASŪ Metadata Server fails to authenticate users when authenticating directly to a load-balanced LDAP server using SSL. The failure is due to mismatches between the host defined in the LDAP_HOST option and the host ...

http://support.sas.com/kb/45/139.html, 32KB


43097 - The error "No available engine session manager slots" occurs when you access Teradata tables with the META LIBNAME engine- Problem Note

Connections might be leaked when you access Teradata tables with the META LIBNAME engine. The leak leads to the error.

http://support.sas.com/kb/43/097.html, 29KB


31894 - The SASŪ Metadata Server might appear to hang during a period of high activity- Problem Note

Due to the way the AIX operating system manages thread locks, the SASŪ Metadata Server might become unresponsive for a period of time. If left alone, the server eventually catches up with queued requests and begins ...

http://support.sas.com/kb/31/894.html, 29KB


36830 - The %MDUEXTR bulkload macro fails with an XML processing error when you use non-English encoding- Problem Note

When you execute the %MDUEXTR macro in a non-English encoded version of SASŪ, an XML processing failure might occur and produce errors similar to the following: MPRINT(MDUEXTR): LIBNAME _metpinf XML xmlmap=_USERMAP ...

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


39550 - A Read access violation occurs when you use the METALIB procedure to import or register database tables into the SASŪ Metadata Repository- Problem Note

The METALIB procedure enables you to import or register tables from a SAS library or a database library into the SAS Metadata Repository. This procedure provides a programmatic approach to import or register tables as ...

http://support.sas.com/kb/39/550.html, 30KB


39944 - The error "Command returned error code SYSRC=4" when you run a backup job in the SASŪ Metada Server- Problem Note

In some Microsoft Windows operating environments, when the SASŪ Metadata Server backup runs, it produces

http://support.sas.com/kb/39/944.html, 31KB


38042 - Error and warning messages might write to the SASŪ log after you run the migrate_template.sas program- Problem Note

Error and warning messages might write to the SAS log after you run migrate_template.sas, a validation program supplied by SAS, while you are migrating from a 32-bit Microsoft Windows system to a 64-bit ...

http://support.sas.com/kb/38/042.html, 52KB


38007 - The Configuration Failure dialog box might appear during an installation of SASŪ Enterprise Miner? 6.1- Problem Note

When you are installing SAS Enterprise Miner 6.1, the Configuration Failure dialog box such as the following one might appear: The configuration failure might be caused by the configuration script occupying too much ...

http://support.sas.com/kb/38/007.html, 43KB


38795 - ERROR: Invalid credentials and Access denied when running the SASŪ Metadata Repository Backup utility- Problem Note

Invalid credentials and access denied errors occur when the SAS Workspace Server host name does not exactly match the host defined in the user's login profile.

http://support.sas.com/kb/38/795.html, 30KB


34955 - The SASŪ Metadata Server stops accepting new client connections and returns an error when too many files are open- Problem Note

When there is a lot of activity on the SASŪ Metadata Server, the server might return the following error: ERROR: Bridge protocol engine socket access method was unable to accept a new client connection, error = 24 (Too ...

http://support.sas.com/kb/34/955.html, 28KB


37901 - Running omabakup macro from csh or tcsh in UNIX environments causes errors- Problem Note

If you attempt to run %omabakup from the csh or tcsh shell, errors occur.

http://support.sas.com/kb/37/901.html, 27KB


36711 - Opening a job in SASŪ Data Integration Studio 4.2 may result in ERROR: Reading Metadata Null- Problem Note

When you open a job in SASŪ Data Integration Studio, an error may occur showing ERROR: Reading Metadata Null. This may occur when you open a job in SAS Data Integration Studio or when you open job properties.

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


37090 - PROC METALIB allows you to create duplicate tables with the same name in the same SASŪ Metadata Server folder- Problem Note

SAS<sup>Ū</sup> 9.2 no longer allows multiple objects with the same name to exist in the same metadata folder. PROC METALIB does not enforce this restriction as it should.

http://support.sas.com/kb/37/090.html, 29KB

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