Error: A transport-level error has occurred when sending the request to the server.

Title

Summary

This article explains the error message "A transport-level error has occurred during Compliance Import".

Symptoms

The Compliance Import can fail with an error similar to the one below:

The import process has failed with the following error (use -verbose to see error details):
Error: A transport-level error has occurred when sending the request to the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.)

Cause

This transport-level error usually means the connection between the FNMP server and the database dropped unexpectedly. This can be caused by a number of things and is usually just a one-off and so will complete when the compliance import next runs. If it keeps occurring then we will need to investigate what is happening, in over 90% of the cases where this error occurs on a regular basis the problem is caused by either DB maintenance or Network maintenance occurring at the time when the import is running. A common reason for this is that the server has been restarted, this will close the existing connections.

Resolution

Each environment has its own setup / tasks and so what we recommend is investigating what takes place in your environment round that time of failure.

Some general suggestions of what to look for are:

Is the database on the same server as FNMP or on a different server? If on the same server then network problems are not an issue, if they're on different servers then network problems could be an issue.
Check with your DBA for database backups, maintenance jobs, or other activities occurring around the same time.
If your FNMP server is separate to your database server and your DBA confirms that no other significant process is occurring at that time, check with your network team to see if anything occurs at that time which could interfere with network traffic between the FNMP and database server.
This is a transient error for your SQL Server. You may not see it next time once you can confirm your SQL Server is working properly.

The suggestions above are some common examples but you may have individual systems in your environment that could cause conflict e.g. some Network Security tools can block traffic while they're updating so if they're scheduled to update at the same time as the compliance import then this could occur.

As mentioned previously, in most cases the error is a one-off (a sudden and unexpected drop) and so will work the next time, the steps above are only required if you see the error on several consecutive days.

Was this helpful?

Support Hub

Product

FlexNet Manager Suite

Deployment type

On-premises

Visibility

Guest

URL Name

a-transport-level-error-has-occurred-during-compliance-import

Are you sure you want to cancel the case creation?

Case closed successfully

Action performed successfully

Upload Attachment

Maximum file size allowed is 3 MB.

File type not supported.

Supported file types:

Documents (.txt, .doc, .docx, .pdf), Images (.jpg, .png), Comma Separated Files (.csv) Speadsheets (.xlsx, .xls)

Are you sure you want to close this case

Get Hotline support

Products	Region	Phone Numbers
FlexNet Operations FlexNet Embedded FlexNet Publisher FlexNet Connect FlexNet Code Insight InstallAnywhere InstallShield	North America *	+1 630-332-2513 (toll) +1 877-279-2853 (toll-free in North America)
	Europe *	+44 1925 944367 (toll) +44 800 047 8642 (toll-free in Europe)
	Japan *	+81 3-4540-5335 (select option 2)
	Australia *	+61 3 9895 2177 +61 1800 560 603 (toll-free in Australia)
Usage Intelligence (formerly Revulytics) Compliance Intelligence	Please use the Case Portal to submit your support ticket or reach out to your Revenera contact.

Revenera Assistant

Summary

Symptoms

Cause

Resolution

Related Articles

Please wait...

Case id: 00001065