Checking C3S for Potential Errors
Unhandled exception has occurred in your application.
Could not find a base address that matches scheme http for the endpoint with binding MedataExchangeHttpBinding. Registered base address schemes are [].
Cause
This error typically occurs when the database being used is disabled in the SSLIP.
Resolution
The type initializer for 'System.ServiceModel.DiagnosticUtility' threw an exception.
A connection with the server could not be established -
http://localhost:8731/Cyrious/Utilities/C3S/Public/StoreData/- SOAPAction:http://tempuri.org/IC3SBRService/Test
Verify the C3S host application is running and the SSLIP.exe.config has the appropriate URL to the service.
Would you like to try connecting again?
“Connection string for Store Data could not be found. Verify the C3S configuration file is setup correctly.”
Cause
The C3S install is corrupted or using incorrect files.
Resolution
Check file versions to make sure they're the correct ones. Replace with a new install.
Error:
HTTP could not register URL http://+:8731/Cyrious/Utilities/C3S/Public/.
Your process does not have access rights to this namespace
Cause:
On Windows Vista and later versions, HTTP web services listening at a particular HTTP address on user accounts other than the system administrator are restricted to run with Administrator privileges by default.
Resolution #1:
Login as the system administrator for that machine and run the SSLIP.
Resolution #2:
The URL must be reserved for the user running the SSLIP using the netsh http command:
Error:
Login failed for user ''. Verify the C3SConnectionString property is
pointing to the right database in the C3S config file
'C:\Program Files\Cyrious\SSLIP\Utilities\C3S\C3SHost.exe.config'
Cause:
By default, the C3S host is configured to connect to the SQL database using “Integrated Security=True” in the connection string. For most Control setups, the SSLIP is run on the same machine as the SQL Server and the logged in user has access to the database. However, in cases where SQL Server is located on a dfferent machine and the logged in user does not access privileges to SQL, C3S will fail to login.
Resolution #1: Modify rights for BUILTIN\Users
Resolution #2: Add User to SQL Server login
Resolution #3: Modify the C3S Connection String
*Note: Replace USERNAME and PASSWORD with the appropriate user name and password to access the SQL Server database.
Resolution #4: Switch Users
Cause:
The C3SHost.exe.config file was not updated by the SSLIP.
Resolution
Error:
Error 1001. Exception occurred while initializing the installation:
System.IO.FileNotFoundException: Could not load file or assembly
'file:/C:\SERVERNAME\cyrious$\SSLIP\Utilties\C3S\C3S Host.exe'
or one of its dependencies. The system cannot find the file specified..
code
Cause:
Running the SSLIP with the C3S installer MSI in the path from a UNC such as “\\CyriousServer\Cyrious$\”. The SSLIP passes the file path it is running from to the C3S installer as a parameter but the installer expects a local path to install to.
Resolution:
Go to the actual local path where the SSLIP is located (“C:\Program Files\Cyrious\SSLIP\”) and run it.
—-
—-
===== When Storing Credit Card Information or Posting Payments =====
==== The operation timed out … ====
Unable to save:
Unable to post Payment:
Error: Credit card processing failed.
The operation timed out - URL:http://localhost:8731/Cyrious/Utilities/C3S/Public/Store Data/ -
SOAPAction:http://tempuri.org/IC3SBRService/Charge
==== The connection with the server was reset … ====
Unable to save:
Unable to post Payment:
Error: Credit card processing failed.
The connection with the server was reset -
URL:http://localhost:8731/Cyrious/Utilities/C3S/Public/Store Data/ -
Unable to save:
Unable to post Payment:
Error: Credit card processing failed. The operation timed out -
URL:http://localhost:8731/Cyrious/Utilities/C3S/Public/Store Data/ -
SOAPAction:http://tempuri.org/IC3SBRService/StoreNewCustomerInformation
Cause:
The communication between the SSLIP and C3S is being blocked.
Resolution #1 - AVG Anti-Virus:
If AVG is installed:
1. Open AVG's User interface.
2. Disable “LinkScanner” and “Online Shield” components. Ensure that the status within the AVG window shows “Disabled”.
4. Click 'Save changes'
Note: Other brands of Anti-Virus applications can also cause this problem to occur. If the anti-virus appears to have any type of link scanner component be
sure to verify through testing that this component is not leading to your problem.
Known Anti-Virus Software that causes issue:
* AVG www.avg.com - Disable Link Scanner and Online Shield components.
* Kaseya www.kaseya.com - Unable to add exclusions, user must contact Kaseya technical support or uninstall Kaseya.
Retry posting the payment.
Resolution #2:
During these steps we'll force the SSLIP to recreate the necessary connection strings for C3S.
- Shutdown the SSLIP.
- Naviagate to the C:\Program Files\Cyrious\SSLIP\ folder.
- Open the file SSLIP_Options.txt.
- If the option UpdateC3SHostConfig=0 option exists delete that option from the file and save your changes.
- Restart the SSLIP. During the restart of the SSLIP the connection strings are recreated each time based on the configuration within the SSLIP.
===== Partial credit card number unmasking =====
==== C3S Credit Card Issues ====
===== See Also =====
* Cyrious Credit Card Service (C3S)
* Upgrading to Control 4.4 (PCI Requirements)
* Historical Payment Updates for PCI
* PCI-DSS Compliance include_pagepage_componentbacklinks
—-
—-
===== When Starting Control… =====
Error:
The server name or address could not be resolved - URL:http://localhost:8731/Cyrious/Utilities/C3S/Public/Store Data/- SOAPAction:http://tempuri.org/IC#SBRService/Test
Verify the C3S Host application is running and the SSLIP.exe.config has the appropriate URL to the service.
Would you like to try connecting again?
Cause:
“localhost” can not be resolved on the server.
Resolution:
1. Open cmd.exe and type: ping localhost.
2. If the ping fails, open the host.txt file (located in c:\windows\System32\drivers\etc).
3. Look for all instances of localhost and ensure that the ip associated with these entries is 127.0.0.1. If not, correct it and save your changes.
4. Re-start the SSLIP and log into Control.