SUPPORT / SAMPLES & SAS NOTES
 

Support

Problem Note 61005: The warning "A valid directory was not found in log4j.properties" is generated when you use SAS® Marketing Automation Integration Utilities

DetailsHotfixAboutRate It

You might encounter the following warning when you use the SAS Marketing Automation Integration Utilities command sasmaextract:

"/SASHome/SASMarketingAutomationIntegrationUtilities/6.5/sasmaextract sasdemo password DefaultAuth "Business Context" "/campaign_request.xml" "/campaign_out.xml";
********************************************************************************
> * A valid directory was not found in log4j.properties so logging is attempting to use the fall back directory. *
> * Logging to <It was not possible to locate the logging file. Please inform the administrator.>               
********************************************************************************

This warning is displayed when you change the log4j.properties file (located in the /SASHome/SASMarketingAutomationIntegrationUtilities/6.5 directory) to a valid log location. The log file is not written to the location that is defined in the log4j.properties file. Instead, it is written to a subdirectory of the executing user (for example, /MALogs/sasdemo).

Click the Hot Fix tab in this note to access the hot fix for this issue.



Operating System and Release Information

Product FamilyProductSystemProduct ReleaseSAS Release
ReportedFixed*ReportedFixed*
SAS SystemSAS Marketing Automation Integration UtilitiesMicrosoft® Windows® for x646.56.69.4 TS1M39.4 TS1M6
64-bit Enabled AIX6.56.69.4 TS1M39.4 TS1M6
64-bit Enabled Solaris6.56.69.4 TS1M39.4 TS1M6
HP-UX IPF6.56.69.4 TS1M39.4 TS1M6
Linux for x646.56.69.4 TS1M39.4 TS1M6
Solaris for x646.56.69.4 TS1M39.4 TS1M6
* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.