Knowledge Center Search


 

[SSL VPN/MAG/UAC] Failed to fetch lease information from the server. Please check the event logs and the admin logs for more information

  [KB22865] Show KB Properties

  [KB22865] Hide KB Properties

Categories:
Knowledge Base ID: KB22865
Last Updated: 27 Dec 2012
Version: 5.0

Summary:
 This article describes the issue of the Failed to fetch lease information from the server. Please check the event logs and the admin logs for more information error being generated, when the Pull state from server button is clicked on the SSL VPN admin page.

The setup includes MAG/SA/UAC as a licensing server and MAG/SA/UAC devices as members.

Problem or Goal:
 When the Pull state from server button is clicked, located at System > Configuration > Licensing > License Summary on the License server, the following error is generated:
Failed to fetch lease information from the server. Please check the event logs and the admin logs for more information.




Checked for generated errors in the Event log:

The error could have been generated due to the time difference between the Licensing server and  it's members. The following error can be found in event codes on the SSL VPN admin page:
System()[] - License Server Protocol Error: Code=(0x34) Error="Large Time Drift"

Cause:
 


Solution:
 To resolve this issue :

On the SSL VPN admin page, go to System > Status > Overview page. Click Edit for System Date & Time:




On the next screen, under Time Source, you can manually set the time by clicking the Get from browser button, under the Set Time Manually section, or utilize the Use NTP Server option. After the time is set, click Save Changes.




You might also see the following error in the System > Log/Monitoring > Events Log, when the Pull state from server button in the Licensing Server is clicked:

License server low-level protocol error, server=SGSGVPLIC, Code = [7] :Could not connect

This issue occurs, if there is no connectivity between the two SA devices. Verify the connectivity between the two devices by using the Commands > Ping utility, which is found in Troubleshooting > Tools > Commands, select Ping from the command drop-down menu.

When troubleshooting an issue, at times, network changes cause unexpected issues. Some of the possible changes on a network are:

  • Hardware changes (firewall, switch, router, server, and so on).

  • Software updates to any client side software

  • Security patches being applied.

  • Group policy changes.

  • Any configuration changes on the IVE (Instant Virtual Extranet).

To verify if there has not been any changes to the network, discuss all of these possible changes with the internal Network Administrator.

Purpose:
Configuration
Implementation
Troubleshooting

Related Links:

 

 

ASK THE KB

Question or KB ID:


 


 

 
Copyright© 1999-2012 Juniper Networks, Inc. All rights reserved.