Follow

arcserve-KB : UDP | Unable to access Arcserve UDP console

Last Update: 2018-09-24 07:15:18 UTC
Description:
Unable to access Arcserve UDP console when launched as the following error is displayed:
 
Error Message:
“The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.' 
 or
“Service Unavailable 503” 

Environment: 
UDP version: 6.0 update 3
Console + RPS + Proxy servers are all the same and it is VM [on ESXi]
SQL version – Express edition 

Cause: This particular update KB4015553 (and all consequent roll ups that include it) causes the system to run out of free RPC ports when there are failed iSCSI connections.

From the wso2Carbon Log we see the following SQL Exception:

Caused by: org.wso2.carbon.user.core.UserStoreException: Database Error - The TCP/IP connection to the host localhost, port 49349 has failed. Error: 'No buffer space available (maximum connections reached?): connect. Verify the connection properties, check that an instance of SQL Server is running on the host and accepting TCP/IP connections at 

Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: The TCP/IP connection to the host localhost, port 49349 has failed. Error: 'No buffer space available (maximum connections reached?): connect. Verify the connection properties, check that an instance of SQL Server is running on the host and accepting TCP/IP connections at the port, and that no firewall is blocking TCP connections to the port.'.

at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDriverError(SQLServerException.java:171)


Re-starting the SQL Instance service give us this error 





SQL Error Log:

2017-12-26 13:08:26.99 spid15s TDSSNIClient initialization failed with error 0x2747, status code 0xa. Reason: Unable to initialize the TCP/IP listener. An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full.
2017-12-26 13:08:26.99 spid15s Error: 17826, Severity: 18, State: 3.
2017-12-26 13:08:26.99 spid15s Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
2017-12-26 13:08:26.99 spid15s Error: 17120, Severity: 16, State: 1.
2017-12-26 13:08:26.99 spid15s SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.​


Solution:

Repairing or removing unsuccessful iSCSI connections, followed by the server reboot, was found to fix the issue.

This issue has been addressed by Microsoft. Apply the appropriate update below to resolve the issue

For 2016: https://support.microsoft.com/en-us/help/4025334
For 2012 R2: https://support.microsoft.com/en-us/help/4025335

------ 




 

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments