It would help to see the code or the log.  Are you using a permanent library defined in SAS Management console?  If so - you may need to make the change in the SAS Management console/Data library ... View more

You can try the following, which will write the "active" log to a single fixed log file name:   -  Backup/save the file /opt/sas94/SASConfig/Lev1/SASMeta/MetadataServer/logconfig.xml  as logconfig.xml.bak -  Edit the file /opt/sas94/SASConfig/Lev1/SASMeta/MetadataServer/logconfig.xml  (You will need to insert one line)   <!-- Rolling log file with default rollover of midnight. --> <appender class="RollingFileAppender" name="TimeBasedRollingFile"> <param name="File" value="/opt/sas94/SASConfig/Lev1/SASMeta/MetadataServer/Logs/SAS_MetadataServer.log"/> <param name="Append" value="false"/>   -   Afterwards, stop/restart your services.   Now, you can use the log file: /opt/sas94/SASConfig/Lev1/SASMeta/MetadataServer/Logs/SAS_MetadataServer.log  in your syslog-ng.conf source sas_log { file("/opt/sas94/SASConfig/Lev1/SASMeta/MetadataServer/Logs/SAS_MetadataServer.log"); };   Note 1.  I do not know much about syslog-ng, so check the syntax carefully 2.  I did not test the above...but I believe the above would work.  You will need to test the above in a "test environment" before you change production configuration.         ... View more

I did not quite understand your question.   But if you are interested in information about syslog-ng then you may want to look at the knowledgebase at https://support.oneidentity.com/syslog-ng-premium-edition/7.0.14   Moreover, I do not know which version of the product you are using.   But perhaps the following information helps you:   Metadata server logs are written usually to a folder named:             <..../lev1/Web/WebAppServer/SASServer1_1/logs/ >   The log4j configurations are stored in a folder named:             <.../lev1/Web/Common/LogConfig> Before attempting to make changes, ensure that you know how log4j works and its syntax.  Extensive documentation is available via google.   Hope this helps.     ... View more

This type of errors are best handled through SAS Technical support.  Typically, these errors require us to know the events preceding this error and possibly the log files.   The event that is named in the error, is included in the out of the box configuration. ... View more

One of the other resources available for you (besides the calculated field option), is to write your SAS code to perform any computation or derive a field of your choice.   If you can do it using Base SAS, you pretty much can do the same using a "process node" on the MA diagram.   Inside a process node, you can write your own data step code or PROC-SQL to access databases/SAS datasets etc.  You can also store intermediate results in a SAS dataset or a database and then retrieve/combine the results with other calculations in a second process node on the same or other diagrams.   Please explore the "process node" documentation (SAS MA user guide) for additional help or ask your questions on this forum. ... View more