Problem Note 35001: A "String index out of range" error might occur when attempting to connect to the SAS® Metadata Server
When attempting to invoke SAS Preferences or to execute a SAS Stored Process from within the SAS® Information Delivery Portal, the process might fail.
If the process fails, the following error might occur in the Tomcat stdout.log file at Tomcat invocation if the SAS® Web applications are deployed in Tomcat:
INFO: System properties were read from a file.
com.sas.services.security.LoginServiceException:
java.lang.StringIndexOutOfBoundsException: String index out of range: -1
at java.lang.String.substring(String.java:1444)
at javax.security.auth.PrivateCredentialPermission.init
(PrivateCredentialPermission.java:403)
at javax.security.auth.PrivateCredentialPermission.
(PrivateCredentialPermission.java:163)
at javax.security.auth.Subject$SecureSet.contains(Subject.java:1135)
at com.sas.services.security.login.OMILoginModule.commit(Unknown Source)
...
[ javax.security.auth.login.LoginException:
java.lang.StringIndexOutOfBoundsException: String index out of range: -1
at java.lang.String.substring(String.java:1444)
at javax.security.auth.PrivateCredentialPermission.init
(PrivateCredentialPermission.java:403)
at javax.security.auth.PrivateCredentialPermission.
(PrivateCredentialPermission.java:163)
...
The above error will occur in the stdout.log file at every occurrence where the SAS Remote Services attempts to connect to the SAS Metadata Server via the sas_metadata_source_server.properties and sas_metadata_source_client.properties
files.
The SAS Remote Services Wrapper.log or Services.log files will contain the following error:
[ERROR] as.services.deployment.OMRMetadataSource - Unable to obtain a connection to
the SAS Metadata Server. sam.S249.ex.msg: A connection to server host sasserver could not
be established on port 8561. Either there is no server listening for connections or the
server is too busy to accept any new connections. Make sure that the server has started
and that the values provided for host and port are correct.
This problem will occur if the SAS Metadata Server hostname that is defined in these two files can not be resolved. The sas_metadata_source_server.properties and as_metadata_source_client.properties files are located in the \Lev1\web\Deployments\RemoteServices\WEB-INF\conf directory.
To correct the problem, perform either of the following steps:
- Verify that the hostname specified in the files is correct for the SAS Metadata Server, and replace the hostname with the actual IP Address of the SAS Metadata Server host in the sas_metadata_source_server.properties and sas_metadata_source_client.properties files.
- Correct the hostname resolution problem on the system.
Operating System and Release Information
| SAS System | SAS Information Delivery Portal | Microsoft Windows Server 2003 Standard Edition | 2.0 | | 9.1 TS1M3 SP4 | |
| Microsoft Windows Server 2003 Enterprise Edition | 2.0 | | 9.1 TS1M3 SP4 | |
| Microsoft Windows Server 2003 Datacenter Edition | 2.0 | | 9.1 TS1M3 SP4 | |
| Microsoft Windows NT Workstation | 2.0 | | 9.1 TS1M3 SP4 | |
| Microsoft Windows 2000 Professional | 2.0 | | 9.1 TS1M3 SP4 | |
| Microsoft Windows 2000 Server | 2.0 | | 9.1 TS1M3 SP4 | |
| Microsoft Windows 2000 Datacenter Server | 2.0 | | 9.1 TS1M3 SP4 | |
| Microsoft Windows 2000 Advanced Server | 2.0 | | 9.1 TS1M3 SP4 | |
| Microsoft® Windows® for x64 | 2.0 | | 9.1 TS1M3 SP4 | |
| Microsoft Windows XP Professional | 2.0 | | 9.1 TS1M3 SP4 | |
| Windows Vista | 2.0 | | 9.1 TS1M3 SP4 | |
| 64-bit Enabled AIX | 2.0 | | 9.1 TS1M3 SP4 | |
| 64-bit Enabled Solaris | 2.0 | | 9.1 TS1M3 SP4 | |
| HP-UX IPF | 2.0 | | 9.1 TS1M3 SP4 | |
*
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.
| Type: | Problem Note |
| Priority: | medium |
| Date Modified: | 2009-03-16 15:50:46 |
| Date Created: | 2009-03-02 14:35:07 |