Please enter search query.
Search <product_name> all support & community content...
NetBackup SAN Client Fibre Transport Service fails to start with "Timeout (30000 milliseconds) waiting for the NetBackup SAN Client Fibre Transport Service service to connect".
Article: 100030037
Last Published: 2008-01-30
Ratings: 0 0
Product(s): NetBackup
Problem
NetBackup SAN Client Fibre Transport Service fails to start with "Timeout (30000 milliseconds) waiting for the NetBackup SAN Client Fibre Transport Service service to connect".Error Message
The NetBackup SAN Client Fibre Transport Service service failed to start due to the following error:The service did not respond to the start or control request in a timely fashion.
Solution
Overview:
If the Client machine believes it is also a Master or Media Server, it will timeout when starting on a client because the server side binaries are not installed on a client machine.
Troubleshooting:
Checked the System Event Logs for the following error:
Event Type: Error
Event Source: Service Control Manager
Event Category: None
EventID: 7009
Date: 12/21/2007
Time: 2:43:24PM
User: N/A
Computer: CLIENTNAME
Description:
Timeout (30000milliseconds) waiting for the NetBackup SAN Client Fibre Transport Service service to connect.
Event Type: Error
Event Source: Service Control Manager
Event Category: None
EventID: 7000
Date: 12/21/2007
Time: 2:43:24PM
User: N/A
Computer: CLIENTNAME
Description:
The NetBackup SAN Client Fibre Transport Service service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.
Error Found in FTclient Unified Log OID200:
12/20/2007 10:46:55.469 [Application] NB 51216 137 PID:7148TID:5224 File ID:200 [Info] V-137-74=====================================================
12/20/2007 10:46:55.469[Application] NB 51216 137 PID:7148 TID:5224 File ID:200 [Info]V-137-13 Starting service: nbFTClient
12/20/200710:46:55.469 [Application] NB 51216 137 PID:7148 TID:5224 File ID:200 [Info]V-137-74 =====================================================
12/20/200710:46:55.485 [Debug] NB 51216 137 PID:7148 TID:5224 File ID:200 1 [TAO]ACE_DLL_Manager::open_dll: Could not open dll.
12/20/2007 10:46:55.485[Debug] NB 51216 137 PID:7148 TID:5224 File ID:200 1 [mlic_get_nb_features]d:\65GA\src\licensing\libminlicense\minlicfile.c.352: status = <Statfailed>
12/20/2007 10:46:55.485 [Debug] NB 51216 137 PID:7148 TID:5224File ID:200 1 [get_expiration]d:\65GA\src\licensing\libminlicense\minlicfile.c.513: status = <Statfailed>
12/20/2007 10:46:55.485 [Application] NB 51216 137 PID:7148TID:5224 File ID:200 [Error] V-137-515 The license is expired or this is not aNBU server. Please check your configuration. Note: unless NBU server, the hostname can't be listed as server in NBU configuration.
12/20/2007 10:46:55.485[Application] NB 51216 137 PID:7148 TID:5224 File ID:200 [Critical] V-137-7Service/Daemon will not start since license is not valid
12/20/200710:46:55.485 [Application] NB 51216 137 PID:7148 TID:5224 File ID:200 [Critical]V-137-15 Unable to pass service start criteria
12/20/2007 10:46:55.485[Application] NB 51216 137 PID:7148 TID:5224 File ID:200 [Info] V-137-74=====================================================
12/20/2007 10:46:55.485[Application] NB 51216 137 PID:7148 TID:5224 File ID:200 [Info]V-137-12 Stopping service:nbFTClient
Resolution:
On the client machine experiencing the issue, remove the client name from the Servers list.
From the Administration Console, open the Host Properties of the Client machine. Proceed to the Servers and remove the client name from the Additional Servers List .
If the Client machine believes it is also a Master or Media Server, it will timeout when starting on a client because the server side binaries are not installed on a client machine.
Troubleshooting:
Checked the System Event Logs for the following error:
Event Type: Error
Event Source: Service Control Manager
Event Category: None
EventID: 7009
Date: 12/21/2007
Time: 2:43:24PM
User: N/A
Computer: CLIENTNAME
Description:
Timeout (30000milliseconds) waiting for the NetBackup SAN Client Fibre Transport Service service to connect.
Event Type: Error
Event Source: Service Control Manager
Event Category: None
EventID: 7000
Date: 12/21/2007
Time: 2:43:24PM
User: N/A
Computer: CLIENTNAME
Description:
The NetBackup SAN Client Fibre Transport Service service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.
Error Found in FTclient Unified Log OID200:
12/20/2007 10:46:55.469 [Application] NB 51216 137 PID:7148TID:5224 File ID:200 [Info] V-137-74=====================================================
12/20/2007 10:46:55.469[Application] NB 51216 137 PID:7148 TID:5224 File ID:200 [Info]V-137-13 Starting service: nbFTClient
12/20/200710:46:55.469 [Application] NB 51216 137 PID:7148 TID:5224 File ID:200 [Info]V-137-74 =====================================================
12/20/200710:46:55.485 [Debug] NB 51216 137 PID:7148 TID:5224 File ID:200 1 [TAO]ACE_DLL_Manager::open_dll: Could not open dll.
12/20/2007 10:46:55.485[Debug] NB 51216 137 PID:7148 TID:5224 File ID:200 1 [mlic_get_nb_features]d:\65GA\src\licensing\libminlicense\minlicfile.c.352: status = <Statfailed>
12/20/2007 10:46:55.485 [Debug] NB 51216 137 PID:7148 TID:5224File ID:200 1 [get_expiration]d:\65GA\src\licensing\libminlicense\minlicfile.c.513: status = <Statfailed>
12/20/2007 10:46:55.485 [Application] NB 51216 137 PID:7148TID:5224 File ID:200 [Error] V-137-515 The license is expired or this is not aNBU server. Please check your configuration. Note: unless NBU server, the hostname can't be listed as server in NBU configuration.
12/20/2007 10:46:55.485[Application] NB 51216 137 PID:7148 TID:5224 File ID:200 [Critical] V-137-7Service/Daemon will not start since license is not valid
12/20/200710:46:55.485 [Application] NB 51216 137 PID:7148 TID:5224 File ID:200 [Critical]V-137-15 Unable to pass service start criteria
12/20/2007 10:46:55.485[Application] NB 51216 137 PID:7148 TID:5224 File ID:200 [Info] V-137-74=====================================================
12/20/2007 10:46:55.485[Application] NB 51216 137 PID:7148 TID:5224 File ID:200 [Info]V-137-12 Stopping service:nbFTClient
Resolution:
On the client machine experiencing the issue, remove the client name from the Servers list.
From the Administration Console, open the Host Properties of the Client machine. Proceed to the Servers and remove the client name from the Additional Servers List .