1 - 10 of 10 results
Previous   |    1    |    Next
Sort by:
Date | Relevance

2010-06-11

39344 - SASŪ solutions support for migration and the "Update Host Name References Tool" in the third maintenance release for SASŪ 9.2 (TS2M3)- Installation Note

This SAS note provides information about solution support for Windows to Windows migration, UNIX to UNIX migration, and the Update Host Name References tool. In the following table, the Windows to Windows Migration ...

http://support.sas.com/kb/39/344.html, 101KB

2010-04-28

39438 - The CREATERISKUSERS.SAS program that initializes XML librefs fails if "CMHOME" is not replaced with "CMAPP"- Installation Note

In SASŪ Credit Risk Management for Banking 4.6, the CREATERISKUSERS.SAS program, which is located in <configdir>/Applications/SASCreditRiskMgmtBankSrvr/4.6/omr, initializes XML librefs, but it fails to set the proper ...

http://support.sas.com/kb/39/438.html, 32KB

2011-10-25

31943 - "ERROR: WEBDAV transport engine encountered errors while publishing the package" when running Update Dashboard analysis- Installation Note

When the Update Dashboard analysis is executed in SASŪ Credit Risk Studio, the following error might be produced in the resulting SAS log: ERROR: WEBDAV transport engine encountered errors while publishing the package. ...

http://support.sas.com/kb/31/943.html, 28KB

2011-10-25

38099 - Cannot access Credit Risk macros error when logging on to SASŪ Credit Risk Studio- Installation Note

When you try to log on to SASŪ Credit Risk Studio, you might get the following error: Cannot access Credit Risk macros. Please check the macro search path and permissions on the macros directory. The error results ...

http://support.sas.com/kb/38/099.html, 27KB

2010-12-22

34500 - "ERROR 48-59: The format $MAP_SENIORITY_TYPE was not found or could not be loaded."- Installation Note

Install media for SAS Credit Risk Management for Banking has VALID_TO_DTTM of 01JAN09. If this date is not modified, then during installation, after 01JAN09, these mapping tables will not be copied to the install ...

http://support.sas.com/kb/34/500.html, 30KB

2010-11-17

41617 - CRM_ACCOUNT table is not populated correctly after running Populate ETL03_LOAD_DATAMART_CRM_ACCOUNT job- Installation Note

In the staging job named ETL03_LOAD_DATAMART_CRM_ACCOUNT, the join between the I_CREDIT_RISK_MITIGANT table extract, the I_FINANCIAL_COLLATERAL table, and the I_PRIMARY_CPTY_CR_MITIGANT table is missing a subsetting ...

http://support.sas.com/kb/41/617.html, 31KB

2010-11-10

41539 - I_FINANCIAL_POSITION table is not populated correctly after running Populate I_FINANCIAL_POSITION ETL job- Installation Note

In the SASŪ Credit Risk Management for Banking intermediate job named Populate I_FINANCIAL_POSITION, the join between the FINANCIAL_POSITION table extract and the FINANCIAL_INSTRUMENT_ASSOC table is of the wrong type. ...

http://support.sas.com/kb/41/539.html, 30KB

2010-10-04

41111 - Data sets in the solution data mart are non-native to the host operating system or have an incorrect encoding- Installation Note

After installing SASŪ Credit Risk Management for Banking 4.6, data sets that are located in the solution data mart might have an incorrect encoding or a format that is non-native to the host operating system. The ...

http://support.sas.com/kb/41/111.html, 30KB

2010-09-28

40889 - I_FINANCIAL_INSTRUMENT table is not populated correctly after running Populate I_FINANCIAL_INSTRUMENT ETL job- Installation Note

In the SASŪ Credit Risk Management for Banking intermediate job named Populate I_FINANCIAL_INSTRUMENT, the join condition between the FINANCIAL_INSTRUMENT table and the TIME_FREQUENCY table is incorrect. The join ...

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

2013-04-17

49588 - Russian localization is now available for SASŪ Credit Risk Management for Banking 4.61- Installation Note

A Russian localization is now available for SAS Credit Risk Management for Banking 4.61. To obtain the Russian localization, you must apply the following hot fix. A hot fix is planned for this issue.

http://support.sas.com/kb/49/588.html, 29KB

1 - 10 of 10 results
Previous   |    1    |    Next