Usage Note 62501: An error occurs when you open campaigns in SAS® Customer Intelligence Studio
When you open a campaign in SAS Customer Intelligence Studio, the following error message is generated:

At the same time, the SASCustIntelCore6.x log displays this error message:
2018-06-22 10:19:38,366 ERROR [CIAsyncExec-8] [7e220988a47d42b7:757eb471:16426640e5f:-71a7] [sasdemo] crm.custdata.storedprocess.StoredProcess -
[no SAS log available]
2018-06-22 10:19:38,366 ERROR [CIAsyncExec-8] [7e220988a47d42b7:757eb471:16426640e5f:-71a7] [sasdemo] crm.custdata.storedprocess.StoredProcess - The process runner has failed while trying to execute the SP ( MA_Verify_Tables )
com.sas.analytics.crm.platformservices.storedprocess.ProcessRunnerException: com.sas.services.storedprocess.ExecutionException: A connection could not be obtained.
Caused by: com.sas.services.connection.FatalConnectionFactoryException: The application could not log on to the server "sas.xxx.sas.com:8601". No server is available at that port on that machine.
In addition, the SAS® Object Spawner log contains this message:
2018-06-22T10:16:27,401 WARN [00000030] :SYSTEM@SASBAP - The credentials specified for the SASApp - Pooled Workspace Server (A55VN5C6.AZ00000B) server definition failed to authenticate. Therefore this server definition will not be included.
2018-06-22T10:16:27,401 WARN [00000030] :SYSTEM@SASBAP - The password obtained from the metadata indicates that it was obtained by a user that has unrestricted access. Please check your configuration.
2018-06-22T10:16:27,412 WARN [00000030] :SYSTEM@SASBAP - Unrestricted access can include being an unrestricted user, or being a member of the SAS Administrators group, or being a member of any group that has the role Metadata Server: User Administration.
To resolve this problem, ensure that you did not specify the Metadata Server: unrestricted role for any of the SAS Customer Intelligence users or user groups, as demonstrated below:

If you did add that role, you need to remove it from the user or user group. Then restart the object spawner.
Operating System and Release Information
| SAS System | SAS Customer Intelligence Studio | Microsoft® Windows® for x64 | 6.4 | | 9.4 TS1M2 | |
| Microsoft Windows 8 Enterprise 32-bit | 6.4 | | 9.4 TS1M2 | |
| Microsoft Windows 8 Enterprise x64 | 6.4 | | 9.4 TS1M2 | |
| Microsoft Windows 8 Pro 32-bit | 6.4 | | 9.4 TS1M2 | |
| Microsoft Windows 8 Pro x64 | 6.4 | | 9.4 TS1M2 | |
| Microsoft Windows 8.1 Enterprise 32-bit | 6.4 | | 9.4 TS1M2 | |
| Microsoft Windows 8.1 Enterprise x64 | 6.4 | | 9.4 TS1M2 | |
| Microsoft Windows 8.1 Pro 32-bit | 6.4 | | 9.4 TS1M2 | |
| Microsoft Windows 8.1 Pro x64 | 6.4 | | 9.4 TS1M2 | |
| Microsoft Windows 10 | 6.4 | | 9.4 TS1M2 | |
| Microsoft Windows Server 2008 | 6.4 | | 9.4 TS1M2 | |
| Microsoft Windows Server 2008 R2 | 6.4 | | 9.4 TS1M2 | |
| Microsoft Windows Server 2008 for x64 | 6.4 | | 9.4 TS1M2 | |
| Microsoft Windows Server 2012 Datacenter | 6.4 | | 9.4 TS1M2 | |
| Microsoft Windows Server 2012 R2 Datacenter | 6.4 | | 9.4 TS1M2 | |
| Microsoft Windows Server 2012 R2 Std | 6.4 | | 9.4 TS1M2 | |
| Microsoft Windows Server 2012 Std | 6.4 | | 9.4 TS1M2 | |
| Windows 7 Enterprise 32 bit | 6.4 | | 9.4 TS1M2 | |
| Windows 7 Enterprise x64 | 6.4 | | 9.4 TS1M2 | |
| Windows 7 Home Premium 32 bit | 6.4 | | 9.4 TS1M2 | |
| Windows 7 Home Premium x64 | 6.4 | | 9.4 TS1M2 | |
| Windows 7 Professional 32 bit | 6.4 | | 9.4 TS1M2 | |
| Windows 7 Professional x64 | 6.4 | | 9.4 TS1M2 | |
| Windows 7 Ultimate 32 bit | 6.4 | | 9.4 TS1M2 | |
| Windows 7 Ultimate x64 | 6.4 | | 9.4 TS1M2 | |
| 64-bit Enabled AIX | 6.4 | | 9.4 TS1M2 | |
| 64-bit Enabled Solaris | 6.4 | | 9.4 TS1M2 | |
| HP-UX IPF | 6.4 | | 9.4 TS1M2 | |
| Linux for x64 | 6.4 | | 9.4 TS1M2 | |
| Solaris for x64 | 6.4 | | 9.4 TS1M2 | |
*
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.
When you open camapigns in SAS Customer Intelligence Studio, the following error is generated: "Unable to verify tables. There was an error in the stored process or a called macro. Contact your administrator. Check the log files for more details."
| Date Modified: | 2018-06-26 07:59:16 |
| Date Created: | 2018-06-22 04:21:50 |