What Do I Do If a License Cannot Be Imported to ServiceCenter Because It Contains Invalid Characters

6

【Product�?
ServiceCenter

【Version�?
3.0, 3.0.SPC2, 3.0.5, 3.0.5.SP1, 3.0.5.SP2, 3.0.5.SP3, 3.0.5.SP5, and 3.0.7

【Fault Type�?
License fault

【Symptom�?
When a license is imported to ServiceCenter, the error message "The request has Invalid parameter: <, >." or "The request has invalid parameter <, >" is displayed.

【Fault Locating�?
The error message displayed on the page indicates that the license contains special characters such as angle brackets <>. Special characters will result in a verification failure.

【Root Cause�?
The license file contains angle brackets <>. After the license is imported to ServiceCenter, the security framework verifies the license file. The verification will fail to prevent XSS attacks if special characters are found.
Check the BOQ and find that the site information contains angle brackets <>. The license file generated on the ESDP platform contains the site information. As a result, the license contains special characters.

【Solution�?
Temporary Solution
After an ESN change (set ESN Change Type to Without revocation code) is performed on the ESDP platform, the changed ESN is still the original ESN. After the change, the new license file does not contain angle brackets <>.
Final Solution
This problem will be resolved in ServiceCenter 3.0.8.

----End

Other related questions:
What Do I Do If a License Failed to Be Imported to ServiceCenter Because License Feature Verification Fails
【Product�? ServiceCenter 【Version�? 3.0.5 【Fault Type�? License fault 【Symptom�? When a license file is imported to ServiceCenter, a message is displayed indicating that the license feature verification fails. 【Fault Locating�? Contact frontline engineers to ask the process for applying for the license. When the license is applied for, both standard and advanced versions are selected. After the database is modified, the license is successfully imported. 【Root Cause�? When a license is applied for, both standard and advanced versions are selected. 【Solution�? Step 1 Use PuTTY to log in to the ServiceCenter node. Ensure that user galaxmanager and the floating IP address of the ServiceCenter management node External API network are used to establish the connection. Step 2 Run the following command to disable logout on timeout: TMOUT=0 Step 3 Run the following command to enter the engineering mode: gotoEngineerMode Run the following command to disable logout on timeout: TMOUT=0 Step 4 Run the following commands to switch to user dbadmin: su �?dbadmin Run the following command to disable logout on timeout: TMOUT=0 Step 5 Run the following command to access the database: gsql -U galaxmanager -d topfmdb -W GalaxManager7! Step 6 Run the following command to update the database: update swm.tbl_featureswitchs_info set ISSUPPORT = 0 where comptype ='SC' and version ='ALL' and virtualtype='ALL' and featurename='VERSION'; ----End

What Do I Do If the Domain Name Cannot Be Used to Log In to ServiceCenter After ServiceCenter Is Mapped to the Public Network Because the Domain Name Is Not Added to the Whitelist
【Product�? ManageOne ServiceCenter 【Version�? 3.X 【Question�? What do I do if the domain name cannot be used to log in to ServiceCenter after ServiceCenter is mapped to the public network because the domain name is not added to the whitelist? 【Answer�? Step 1 Log in to the ServiceCenter active and standby nodes as user galaxmanager. Step 2 Run the white-ls-cfg show command on the active and standby nodes to check whether the domain name is added to the whitelist. If no domain name is displayed in the command output, the domain name is not added to the whitelist. Step 3 Run the following command on the active and standby nodes to add the domain name to the whitelist: white-ls-cfg add Domain name ----End

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top