07.08.2013 Views

SAS 9.1.3 Intelligence Platform: System Administration Guide

SAS 9.1.3 Intelligence Platform: System Administration Guide

SAS 9.1.3 Intelligence Platform: System Administration Guide

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

CHAPTER<br />

24<br />

Troubleshooting the <strong>SAS</strong><br />

Metadata Server<br />

Overview of Troubleshooting the <strong>SAS</strong> Metadata Server 233<br />

How to Respond When the <strong>SAS</strong> Metadata Server Will Not Start 233<br />

Check for a <strong>SAS</strong> Log File 233<br />

Check for <strong>SAS</strong> Initialization Failure 234<br />

How to Respond When a Client Cannot Connect to <strong>SAS</strong> Metadata Server 235<br />

Overview of Troubleshooting the <strong>SAS</strong> Metadata Server<br />

The following are two common problems that you might encounter when using a <strong>SAS</strong><br />

Metadata Server:<br />

3 The <strong>SAS</strong> Metadata Server will not start.<br />

3 Clients cannot connect to the <strong>SAS</strong> Metadata Server.<br />

This chapter provides troubleshooting recommendations for these problems.<br />

For help with diagnosing user dialog error messages for a running server, consult the<br />

<strong>SAS</strong> Metadata Server log. Error messages from the I/O subsystem are prefaced with<br />

the statement “The I/O subsystem has returned error message message-text” and are<br />

followed by another message that describes the corresponding error event on the <strong>SAS</strong><br />

Metadata Server.<br />

Repository containers are <strong>SAS</strong> data sets. If you suspect that your repository<br />

containers are damaged, see “Repairing Damaged <strong>SAS</strong> Files” in the <strong>SAS</strong> Language<br />

Reference: Concepts.<br />

How to Respond When the <strong>SAS</strong> Metadata Server Will Not Start<br />

Check for a <strong>SAS</strong> Log File<br />

When the metadata server fails to initialize, first check to see if a <strong>SAS</strong> log file exists.<br />

The default path and filename are as follows:<br />

sas-config-dir\Lev1\<strong>SAS</strong>Main\MetadataServer\logs\MetadataServer#d#b#y.log<br />

3 If the <strong>SAS</strong> log does not exist, then one of the following statements is true:<br />

3 The LOG parameter was omitted from the metadata server start command, or<br />

the destination filename does not match the name of the destination directory.<br />

233

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!