Installation Note 43740: "The SAS Model Manager service was not invoked. Please contact your SAS Model Manager administrator."
 |  |  |  |
When you log on to SAS® Model Manager, a pop-up message might appear after several minutes. A problem occurs after migrating SAS Model Manager 2.1 to SAS Model Manager 3.1, even if the migration is successful. The error appears if you start your Web Application Server but you are not the owner of the SAS Model Manager configuration directory.
The SAS Model Manager service was not invoked. Please contact your SAS Model Manager administrator.
If you click on the Close button another error might appear:
com.sas.services.ServiceException: nullcheckLicenseForInDatabase.sas (No such file or directory)
The Web Application Server log contains this error:
[WebContainer : 0] ERROR [sastrust] com.sas.analytics.modelmanager.server.RemoteModelManagementImpl - mmapi failed to initialize in init() java.lang.NullPointerException at com.sas.analytics.modelmanager.util.DAVUtility.moveFilesToLocal(DAVUtility.java:73) at com.sas.analytics.modelmanager.util.DAVUtility.moveFilesToLocal(DAVUtility.java:86) at com.sas.analytics.modelmanager.util.DAVUtility.moveFilesToLocal(DAVUtility.java:86) at com.sas.analytics.modelmanager.server.RemoteModelManagementImpl.moveFilesFromDavToLocal(RemoteModelManagementImpl.java:3865) at com.sas.analytics.modelmanager.server.RemoteModelManagementImpl.init(RemoteModelManagementImpl.java:3475) at com.sas.modelmanager.impl.MetadataDelegate.getMmRepository(MetadataDelegate.java:97) at com.sas.modelmanager.impl.MMFolderDelegate.getRoot(MMFolderDelegate.java:40)
Here is an example location of a Web Application Server log, using a JBoss installation on Windows:
To work around the problem, follow these steps.
Remove the _mm_config directory. The location of the _mm_config directory depends on your operating system:
UNIX:
/var/tmp/_mm_config
WINDOWS:
C:\Documents and Settings\<userid>\Local Settings\Temp\_mm_configorC:\users\<userid>\Local Settings\Temp\_mm_configRestart your Web Application Server.
After following these steps, launch the SAS Model Manager Client again. You should be able to log on with no errors.
Operating System and Release Information
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | SAS Model Manager | Microsoft® Windows® for x64 | 3.1 | 9.3 TS1M0 | ||
| Microsoft Windows Server 2003 Datacenter Edition | 3.1 | 9.3 TS1M0 | ||||
| Microsoft Windows Server 2003 Enterprise Edition | 3.1 | 9.3 TS1M0 | ||||
| Microsoft Windows Server 2003 Standard Edition | 3.1 | 9.3 TS1M0 | ||||
| Microsoft Windows Server 2003 for x64 | 3.1 | 9.3 TS1M0 | ||||
| Microsoft Windows Server 2008 | 3.1 | 9.3 TS1M0 | ||||
| Microsoft Windows Server 2008 for x64 | 3.1 | 9.3 TS1M0 | ||||
| Microsoft Windows XP Professional | 3.1 | 9.3 TS1M0 | ||||
| Windows 7 Enterprise 32 bit | 3.1 | 9.3 TS1M0 | ||||
| Windows 7 Enterprise x64 | 3.1 | 9.3 TS1M0 | ||||
| Windows 7 Home Premium 32 bit | 3.1 | 9.3 TS1M0 | ||||
| Windows 7 Home Premium x64 | 3.1 | 9.3 TS1M0 | ||||
| Windows 7 Professional 32 bit | 3.1 | 9.3 TS1M0 | ||||
| Windows 7 Professional x64 | 3.1 | 9.3 TS1M0 | ||||
| Windows 7 Ultimate 32 bit | 3.1 | 9.3 TS1M0 | ||||
| Windows 7 Ultimate x64 | 3.1 | 9.3 TS1M0 | ||||
| Windows Vista | 3.1 | 9.3 TS1M0 | ||||
| Windows Vista for x64 | 3.1 | 9.3 TS1M0 | ||||
| 64-bit Enabled AIX | 3.1 | 9.3 TS1M0 | ||||
| 64-bit Enabled Solaris | 3.1 | 9.3 TS1M0 | ||||
| HP-UX IPF | 3.1 | 9.3 TS1M0 | ||||
| Linux for x64 | 3.1 | 9.3 TS1M0 | ||||
| Solaris for x64 | 3.1 | 9.3 TS1M0 | ||||
| Type: | Installation Note |
| Priority: | medium |
| Date Modified: | 2011-07-30 13:46:03 |
| Date Created: | 2011-07-14 10:24:54 |