1 - 25 of 220 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


52535 - The SASŪ Metadata Server or associated client processes might become unresponsive during the authorization decision process- Problem Note

The SASŪ Metadata Server uses an authorization decision process to determine whether a requesting identity has access to the requested metadata objects. During the authorization process, locks are requested on the ...

http://support.sas.com/kb/52/535.html, 32KB


51088 - When you run multiple TCP/IP stacks on a z/OS system, the z64 SASŪ Metadata Server incorrectly binds to all available TCP/IP stacks- Problem Note

If your site runs multiple TCP/IP stacks under z/OS, the 64-bit SAS Metadata Server incorrectly binds to all available TCP/IP stacks. To control which TCP/IP stack the SAS Metadata Server binds to, you must code the ...

http://support.sas.com/kb/51/088.html, 26KB


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


48994 - During termination, a SASŪ 9.3 Metadata Server that is executing in a z/OS operating environment might abend with a user 4039 or system 0C2 abend code- Problem Note

During termination of a SAS 9.3 Metadata Server that is executing under z/OS, you might see an LE (Language Environment) user abend 4039 in module CELQLIB. In the system log for the SAS Metadata Server, you might also ...

http://support.sas.com/kb/48/994.html, 26KB


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


33666 - The METAOPERATE procedure returns error messages when you specify the ACTION=PURGE option- Problem Note

When you submit PROC METAOPERATE with the ACTION=PURGE option and you do not specify the NOAUTOPAUSE statement, the procedure terminates with the following error message: ERROR: The DoRequest request failed because the ...

http://support.sas.com/kb/33/666.html, 28KB


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


32044 - An error occurs if you attempt to use the SASŪ Migration Utility to migrate from one SASŪ 9.2 system to another SAS 9.2 system- Problem Note

Currently, the SAS Migration Utility does not support migration from one SAS 9.2 system to another SAS 9.2 system. If you attempt such a migration, the following messages occur: "The client has connected to a SAS (9.2) ...

http://support.sas.com/kb/32/044.html, 29KB


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


30435 - PROC METALIB fails to analyze all tables in a DBMS library if one table contains a column with an unsupported datatype- Problem Note

If you run PROC METALIB on a library that refers to a relational database, the procedure may fail to analyze all the tables in the library. This problem occurs when one or more tables in the RDBMS schema contains a ...

http://support.sas.com/kb/30/435.html, 29KB


15667 - SSL support is not available between the SASŪ Metadata Server and LDAP- Problem Note

SASŪ servers which can be configured for Direct Authentication to LDAP, such as the SASŪ Metadata Server and the SASŪ OLAP Server, do not support LDAP over SSL (also referred to as LDAPS support) in SAS versions prior ...

http://support.sas.com/kb/15/667.html, 29KB


36662 - Running the Metadata repair utility on a running SASŪ Metadata Server might cause corruption- Problem Note

If you run the Metadata Analyze and Repair utility in the Metadata Manager Plug?Ins tab of SASŪ Management Console and choose to repair, or if you run the Analyze Metadata batch utility with the ?REPAIR option, you ...

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


35783 - The %MDSECDS security reporting macro with MEMBERTYPE set to Table or Cube returns other object types that were not requested- Problem Note

%MDSECDS also returns all "child" objects associated with the Table or Cube, such as Column, Level, Dimension, Hierarchy object types.

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


43216 - The message, "Requested Permission does not exist in the SASŪ Metadata Server," appears in the SAS Metadata Server log- Problem Note

This informational message is harmless and can appear when you are running the Metadata Analyze and Repair utility.

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


35778 - The %MDSECDS macro returns folder information along with the specified member type- Problem Note

In addition to the types requested on the MEMBERTYPES= parameter, the %MDSECDS security reporting macro also returns authorization information for all the folders in the path to those requested objects.

http://support.sas.com/kb/35/778.html, 30KB


38707 - An error occurs when you add the DBSASTYPE= option to a database table in SASŪ Management Console and you run a query that uses the metadata engine- Problem Note

You might receive the following error if you try to reference a table in a library that uses the DBSASTYPE= option: ERROR: Incorrect length in SAS Metadata Repository for column Age. This error occurs when you define ...

http://support.sas.com/kb/38/707.html, 31KB

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