Error Details
EGCSqlException: (EOleException) System.Data.SqlClient.SqlException (0x80131904): String or binary data would be truncated.
This error happens when the telephone numbers are longed than the maximum allowed length and is occurring within one of the latest versions of SIMS.
Resolving this error involves a patch being applied to your SIMS application. Please contact the SIMS support desk and request patch number 19813. Once the patch has been applied, this error should be eradicated.
Error Details (1)
EGCSqlException: (EGCSqlSimsNetException) SIMS: Login 3 Failed - Login failed for user 'LoginName'.
This error can occur when the login specified for Xporter is incorrect or does not have the necessary group permissions. To resolve this, first ensure that the login details (the username and password) for the user have been entered correctly.
In the event that the job still fails, this could be due to the group permissions that are associated with the login that has been specified. Ensure that the login which has been entered as per the above has the following group associations:
Error Details (2)
SIMS: Login 1 Failed - A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified).
This indicates that Xporter cannot connect to the SIMS SQL server. This is commonly because the SIMS SQL Server has been moved recently and the SIMS settings on the server have not been updated. Xporter picks up SQL connection settings from a connect.ini file, located either in the Xporter installation directory or from a network drive.
Error Details
2014/08/01 01:20:35: Error: There was no endpoint listening at https://customernumber.microlibrarian.net/services/StudentIntake.svc that could accept the message.This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details. Exception: System.ServiceModel.EndpointNotFoundException: There was no endpoint listening at https://customernumber.microlibrarian.net/services/StudentIntake.svc that could accept the message. This is often caused by an incorrect address or SOAP action.
This error occurs when the service URL is wrong or the Xporter program cannot get a connection to the specified address.
Firstly, check that the correct service URL has been entered.
Please note that the URL should be 'https://api-intake.microlibrarian.net/services/studentintake.svc?url=https://U012345.microlibrarian.net' where the u012345 should be your customer number. For example, if your customer number is 123 then the URL should be adjusted to u000123 (padding with 0s to 6 digits).
Should this fail, it is likely that you will need to enter the details of a proxy server.
Error Details
2014-08-01 09:21:23 EGCSqlException: (EOleException) System.ArgumentNullException: Buffer cannot be null.
This is normally caused by the SIMS Document Server not running. Please contact your SIMS support representative for information about starting the document service.
Error Details
EGCSqlException: (EOleException) Groupcall.Sims.SimsReportException: SIMS.Processes.Exception: You are not permitted to see any information in this report.
This means that every field in the report was blocked by the Xporter users SIMS permissions and so the report had no columns. To resolve this error, ensure the user running the job has the required group associations
Error Details
EGCExpSys_OdbcException: [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied.
This error usually occurs when the connection details for the library system have been specified incorrectly in the MLS Xporter settings window.
Error Details
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server).
This error happens when the connection details for the library system have been specified incorrectly in the MLS Xporter settings window or, when the SQL Server is not configured to allow connections from remote servers.
1. Check the Connection detailsIf the library SQL Server is running on a different server to Xporter and it is not configured to allow TCP connections then each time a connection is attempted it will fail. To resolve this, you need to ensure that remote connections are allowed. Instructions for configuring this are widely available on the internet, such as in this msdn post.
If the SQL Server is configured to allow TCP connections then you should also check that the SQL Browser Service is running on the remote SQL Server.
Error Details
2014/08/01 01:17:32: Error: The network path was not found.
2014/08/01 01:17:32: Exception: System.IO.IOException: The network path was not found.
This error occurs when the path to the library database has been specified incorrectly.
Error Details
EGCSqlException: (EPSException) Missing Integris API login details
This is due to the Local Groupcall service no longer being active for MLS Connect. The customer will need to grant access to Groupcall Xporter within their new RMIntergris Datashare Management Tool.
Once access has been granted for Groupcall within the Datashare Management Tool, contact Groupcall Support via Phone or Email with the schools Name, Postcode, DFE Number and specific library Server/Endpoint URL to assist with set-up of their hosted xporter service. Please ensure to advise Groupcall it is regarding 'Integration between RM Integris and MLS'.
Please note that the Server/Endpoint URL should be 'https://api-intake.microlibrarian.net/services/studentintake.svc?url=https://U012345.microlibrarian.net' where the u012345 should be your customer number. For example, if your customer number is 123 then the URL should be adjusted to u000123 (padding with 0s to 6 digits).