If you experience a problem using SAS® Enterprise Miner™, you can often resolve the problem by following the techniques in this note. These are the same techniques that are used by SAS Technical Support team members. If you follow the techniques, then you can probably solve the problem. Even if you cannot solve the problem, the techniques help organize information so that SAS Technical Support staff can assist you more quickly.
Most SAS Enterprise Miner problems generally fall into these categories:
A first step to solving an unexpected problem is to search the SAS Technical Support website for existing notes about your problem.
In the "Search only Samples and SAS Notes" area, enter some of the words from the error message or symptom that you encountered. Use "miner" as the first word. Notes are given titles that match the symptom of the problem. Look for titles that approximate your problem.
Sometimes solutions are found by examining additional SAS Enterprise Miner documentation.
If you need to contact SAS Technical Support online about your problem, then use the form on this web page:
The form guides you through information that is usually necessary for directing your issue quickly to the most appropriate team, and for troubleshooting your problem.
TROUBLESHOOTING THE CATEGORIES
Common problems in this category include symptoms such as these:
The recommended strategy for those types of problems is to use the "Search only Samples and SAS Notes" area. Notes are added and updated based on common customer experiences.
If you are encountering a problem creating a project or a diagram in a new SAS Enterprise Miner installation, then a first step is to follow the "Verify the Installation" steps. The steps are documented in the Administration and Configuration guide, and you can download the guide from the product documentation page above. Follow the steps in the guide. If the steps in the guide do not complete successfully, then a problem exists with the installation.
If you cannot open a project that was migrated, then be sure to include the word "migrate" when you use the "Search only Samples and SAS Notes" area to search. Migration problems might result when you move from a previous release of SAS Enterprise Miner, or when you move to a different operating system. If you need to contact SAS Technical Support for help, then be sure to include information about the SAS Enterprise Miner release and operating system of the original project. Include information about the destination release and operating system. Note that often it is easier to create a new diagram in the new release than it is to try to debug a migrated project. You might be able to move forward with your analysis more quickly if you create a new project in the new release.
If you are using Java Web Start to run SAS Enterprise Miner, then a quick and often useful step is to exit SAS Enterprise Miner, and clear the caches. Clear your Java cache, clear your web browser cache, and re-start SAS Enterprise Miner.
A data source in SAS Enterprise Miner points to a SAS data set. If the underlying SAS data set is changed after the data source is created, problems might occur. If you experience problems accessing the data source in that case, then an often-employed quick solution is to delete the data source, and replace it with a new one.
If your underlying data set contains formats, then you might encounter this error, or a similar error:
A common solution when a node creates an error is to delete the node, replace it with a new node, and try again. When you replace the node with a new one, try using default settings first, to see whether the problem is due to specific node settings.
Most node problems produce a generic message stating that "a problem has been encountered on the server". To find a specific cause, examine the node log. To open the node log, right-click the node, and select Results.... Click the Log icon in the upper left corner of the Results window (or select View ► SAS Results ► Log). Use the Find tool to search for errors in the log, starting from the top, and working down. Sometimes no error information is displayed because the log is truncated. If the log is truncated, a note appears at the bottom, and the note tells where to look for the complete log. If you need assistance interpreting any of the errors, try the "Search only Samples and SAS Notes" area to see whether SAS notes exist.
Sometimes a problem with a node is data-specific. To diagnose whether something about your data is causing the problem, try the flow using one of the SAS Enterprise Miner sample data sets in the SAMPSIO library. The SAS Enterprise Miner Help chapter that corresponds to the node that you are using usually identifies a sample data set that can be used for testing that node. If no data source is identified for testing the problem node, then try using the HMEQ data source. You can create the HMEQ data source using these settings.
In the "Select a SAS table" step, click Browse. Double-click Sampsio. Double-click Hmeq.
If you can reproduce the problem using sample data, then continue to simply the flow to try to narrow the scope of possibilities. If you can reproduce a problem using sample data, then SAS Technical Support can try exactly what you are trying.
If the problem occurs with your data, but not with sample data, then examine your data to see what might be causing a problem. Look for causes that might involve having too many missing values, or not enough variability, and so on.
If your data source is large, you can reduce the amount of time needed to conduct diagnostic tests by trying a sample of the data. Add a Sample node to your flow to help the flow run more quickly. If the problem occurs on the full data, but not on the sample, do not automatically conclude that the size is the problem. The problem might be caused by some of the data that is not included in the sample.
Once you have simplified the flow as much as possible, you can send a model package to SAS Technical Support if you need help with resolving the problem. The model package shows your flow, the variable settings, and logs with errors. The model package does not include your data. If you can reproduce your problem using sample data, then send the model package that used the sample data. This SAS note tells how to create a model package.
46764, "Creating a model package (SPK file) in SAS® Enterprise Miner™"
If you are opening a new track for your problem, first use the SAS Technical Support Form above to create a track. When you receive a tracking number via e-mail, reply to the e-mail and attach your model package (the SPK file).
|Product Family||Product||System||SAS Release|
|SAS System||SAS Enterprise Miner||z/OS|
|Microsoft® Windows® for 64-Bit Itanium-based Systems|
|Microsoft Windows Server 2003 Datacenter 64-bit Edition|
|Microsoft Windows Server 2003 Enterprise 64-bit Edition|
|Microsoft Windows XP 64-bit Edition|
|Microsoft® Windows® for x64|
|Microsoft Windows 8 Pro|
|Microsoft Windows 95/98|
|Microsoft Windows 2000 Advanced Server|
|Microsoft Windows 2000 Datacenter Server|
|Microsoft Windows 2000 Server|
|Microsoft Windows 2000 Professional|
|Microsoft Windows NT Workstation|
|Microsoft Windows Server 2003 Datacenter Edition|
|Microsoft Windows Server 2003 Enterprise Edition|
|Microsoft Windows Server 2003 Standard Edition|
|Microsoft Windows Server 2003 for x64|
|Microsoft Windows Server 2008|
|Microsoft Windows Server 2008 for x64|
|Microsoft Windows Server 2012|
|Microsoft Windows XP Professional|
|Windows 7 Enterprise 32 bit|
|Windows 7 Enterprise x64|
|Windows 7 Home Premium 32 bit|
|Windows 7 Home Premium x64|
|Windows 7 Professional 32 bit|
|Windows 7 Professional x64|
|Windows 7 Ultimate 32 bit|
|Windows 7 Ultimate x64|
|Windows Millennium Edition (Me)|
|Windows Vista for x64|
|64-bit Enabled AIX|
|64-bit Enabled HP-UX|
|64-bit Enabled Solaris|
|ABI+ for Intel Architecture|
|Linux for x64|
|Linux on Itanium|
|Solaris for x64|
|Date Modified:||2013-10-17 13:43:18|
|Date Created:||2010-10-12 12:52:51|