After you install SAS® Marketing Automation 4.3 and successfully log on to the SAS® Marketing Automation Plug-ins for SAS® Management Console or SAS® Campaign Studio, you might receive the following error message when you attempt to open anything further in the application:
Unable to run Marketing Automation stored process.
Make sure the SAS Stored Process server is running
and configured properly.
The remote services log file for MA Core contains the following errors:
For SAS Marketing Automation 4.4:
The Stored Process Service is undiscoverable.
Error running setinit stored process.
com.sas.analytics.crm.error.client.ApplicationException:
Service exception in stored process.
For SAS® Customer Intelligence 5.1:
Error running setinit stored process.
com.sas.analytics.crm.error.client.ApplicationException: Service exception when
executing stored process: MAInit
This error occurs because the sas_metadata_source_server.properties file is missing a necessary entry, which means MA Core cannot search the SAS® Stored Process Server.
To resolve this issue, insert the following stored process service entry in the configuration file:
Lev1/web/Deployments/RemoteServices/WEB-INF/conf/
sas_metadata_source_server.properties and
sas_metadata_source_server.poroperties.orig
deployment_group_2=BIP Stored Process Service
If this line is already in the file, make sure that the file does not have a blank value at the end of the line.
This error might also occur after the Web Infrastructure hot fix
913WEBINFRAKITxx is applied. This hot fix
overwrites these files and removes the deployment_group_2=BIP Stored Process Service setting.
If this happens, insert the stored process service entry again.
The Web Infrastructure hot fix overwrites the SAS Remote Services server logging configuration file and the StartRemoteServices.bat/.sh files. On Windows operating systems the wrapper.conf file is also overwritten.
UNIX:
Lev1/web/Deployments/RemoteServices/logging_config_svc.xml.
Lev1/web/Deployments/RemoteServices/WEB-INF/StartRemoteServices.sh
Windows:
Lev1\web\Deployments\RemoteServices\logging_config_svc.xml.
Lev1\web\Deployments\RemoteServices\WEB-INF\StartRemoteServices.bat
Lev1\web\Deployments\RemoteServices\WEB-INF\conf\wrapper.conf
Take a copy of these files before applying the hot fix so you can reinstate them afterwards
If the files has already been overwritten, review the "Specifying Debugging Options in the Logging Service File" and "Configuring JVM for SAS Remote Services" chapters of the SAS Customer Intelligence/SAS Marketing Automation Administrators Guide and re-apply the settings appropriate to your installation.
Operating System and Release Information
| SAS System | SAS Marketing Automation-Server | Microsoft Windows XP Professional | 4.3 | | | |
| Microsoft Windows Server 2003 Enterprise Edition | 4.3 | | | |
| Microsoft Windows Server 2003 Standard Edition | 4.3 | | | |
| Microsoft Windows Server 2003 Datacenter Edition | 4.3 | | | |
| Microsoft Windows 2000 Server | 4.3 | | | |
| Microsoft Windows 2000 Professional | 4.3 | | | |
| Microsoft Windows 2000 Datacenter Server | 4.3 | | | |
| Microsoft Windows 2000 Advanced Server | 4.3 | | | |
| 64-bit Enabled Solaris | 4.3 | | | |
| Solaris | 4.3 | | | |
| AIX | 4.3 | | | |
| 64-bit Enabled AIX | 4.3 | | | |
| HP-UX IPF | 4.3 | | | |
*
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.
