![]() | ![]() | ![]() | ![]() | ![]() |
If you send a web service request to SAS Enterprise Case Management to search for subjects, an error message might be returned. The error message is different for each database type, but the error message is about an invalid column name "relation_type_cd". Here is an example of an error message that occurs with the Microsoft SQL Server database:
2012-04-16 23:32:08,935 ERROR [ProxyHelperNew.callWithSender(178)]: java.lang.RuntimeException: com.ibatis.common.jdbc.exception.NestedSQLException: --- The error occurred while applying a parameter map. --- Check the getPartyPartyReferences-InlineParameterMap. --- Check the statement (query failed). --- Cause: com.microsoft.sqlserver.jdbc.SQLServerException: Invalid column name 'relation_type_cd'. 2012-04-16 23:32:08,939 ERROR [TestClientDriver.processLookupRequest(413)]: Error submitting lookup request: com.ibatis.common.jdbc.exception.NestedSQLException: --- The error occurred while applying a parameter map. --- Check the getPartyPartyReferences-InlineParameterMap. --- Check the statement (query failed). --- Cause: com.microsoft.sqlserver.jdbc.SQLServerException: Invalid column name 'relation_type_cd'. java.lang.RuntimeException: com.ibatis.common.jdbc.exception.NestedSQLException: --- The error occurred while applying a parameter map. --- Check the getPartyPartyReferences-InlineParameterMap. --- Check the statement (query failed). --- Cause: com.microsoft.sqlserver.jdbc.SQLServerException: Invalid column name 'relation_type_cd'. at com.sas.solutions.casemgmt.webservice.proxy.CaseManagementServiceInterfaceProxy.lookup (CaseManagementServiceInterfaceProxy.java:113) at com.sas.solutions.casemgmt.client.TestClientDriver.processLookupRequest (TestClientDriver.java:397) at com.sas.solutions.casemgmt.client.TestClientDriver.processFile(TestClientDriver.java:159) at com.sas.solutions.casemgmt.client.TestClientDriver.drive(TestClientDriver.java:127) at com.sas.solutions.casemgmt.client.TestClientDriver.main(TestClientDriver.java:45)
Click the Hot Fix tab in this note to access the hot fix for this issue.
Product Family | Product | System | Product Release | SAS Release | ||
Reported | Fixed* | Reported | Fixed* | |||
SAS System | SAS Enterprise Case Management | Microsoft® Windows® for x64 | 3.1 | 3.2 | 9.3 TS1M1 | 9.3 TS1M2 |
Microsoft Windows Server 2003 Datacenter Edition | 3.1 | 3.2 | 9.3 TS1M1 | 9.3 TS1M2 | ||
Microsoft Windows Server 2003 Enterprise Edition | 3.1 | 3.2 | 9.3 TS1M1 | 9.3 TS1M2 | ||
Microsoft Windows Server 2003 Standard Edition | 3.1 | 3.2 | 9.3 TS1M1 | 9.3 TS1M2 | ||
Microsoft Windows Server 2003 for x64 | 3.1 | 3.2 | 9.3 TS1M1 | 9.3 TS1M2 | ||
Microsoft Windows Server 2008 | 3.1 | 3.2 | 9.3 TS1M1 | 9.3 TS1M2 | ||
Microsoft Windows Server 2008 for x64 | 3.1 | 3.2 | 9.3 TS1M1 | 9.3 TS1M2 | ||
Microsoft Windows XP Professional | 3.1 | 3.2 | 9.3 TS1M1 | 9.3 TS1M2 | ||
Windows 7 Enterprise 32 bit | 3.1 | 3.2 | 9.3 TS1M1 | 9.3 TS1M2 | ||
Windows 7 Enterprise x64 | 3.1 | 3.2 | 9.3 TS1M1 | 9.3 TS1M2 | ||
Windows 7 Home Premium 32 bit | 3.1 | 3.2 | 9.3 TS1M1 | 9.3 TS1M2 | ||
Windows 7 Home Premium x64 | 3.1 | 3.2 | 9.3 TS1M1 | 9.3 TS1M2 | ||
Windows 7 Professional 32 bit | 3.1 | 3.2 | 9.3 TS1M1 | 9.3 TS1M2 | ||
Windows 7 Professional x64 | 3.1 | 3.2 | 9.3 TS1M1 | 9.3 TS1M2 | ||
Windows 7 Ultimate 32 bit | 3.1 | 3.2 | 9.3 TS1M1 | 9.3 TS1M2 | ||
Windows 7 Ultimate x64 | 3.1 | 3.2 | 9.3 TS1M1 | 9.3 TS1M2 | ||
Windows Vista | 3.1 | 3.2 | 9.3 TS1M1 | 9.3 TS1M2 | ||
Windows Vista for x64 | 3.1 | 3.2 | 9.3 TS1M1 | 9.3 TS1M2 | ||
64-bit Enabled AIX | 3.1 | 3.2 | 9.3 TS1M1 | 9.3 TS1M2 | ||
64-bit Enabled Solaris | 3.1 | 3.2 | 9.3 TS1M1 | 9.3 TS1M2 | ||
HP-UX IPF | 3.1 | 3.2 | 9.3 TS1M1 | 9.3 TS1M2 | ||
Linux for x64 | 3.1 | 3.2 | 9.3 TS1M1 | 9.3 TS1M2 | ||
Solaris for x64 | 3.1 | 3.2 | 9.3 TS1M1 | 9.3 TS1M2 |