We use cookies on our website to ensure we provide you with the best experience on our website. By using our website, you agree to the use of cookies for analytics and personalized content.This website uses cookies. More Information
It seems like your browser didn't download the required fonts. Please revise your security settings and try again.
Barracuda NextGen Firewall X

How to debug Barracuda NG Network Access Client installation?

  • Type: Knowledgebase
  • Date changed: 2 years ago
Solution #00005134
 
Scope:
This solution replies to:
- NG Network Access Client versions 2.0-SPx
- Entegra Client versions 1.0-SPx, 2.0-SPx
-NG Network Access Client versions 3.x.
 
Symptoms:

This article describes how to debug Barracuda NG Network Access Client installation.


 

Solution:

Two files exist containing debugging information - the files setupapi.log and setupclient.log. Apply one or both methods if debugging is needed.

 

 

Windows system debug file (for Windows VISTA and lower): SetupAPI.log

 

The file SetupAPI.log is maintained by the Windows operating system. To gather information useful for debugging Barracuda NG Network Access Client installation, this file has to be made more verbose.

Do get a more verbose SetupAPI.log file, the debug level has to be increased. Proceed as follows to do so:

 

1. Open the Registry Editor (Regedit.exe) and browse to the key

    HEKY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\

 

2. Create a new REG_DWORD value with the following values:
    Value name: LogLevel
    Value data: 0x0000FFFF  

 

3. The default debug level has the Value data 0x00000000. Reset the debug level to the default after installation has 
    completed.

4. The SetupAPI.log will be stored in c:\WINDOWS\ 


Windows system debug file (for Windows 7 and higher): SetupAPI.app.log and SetupAPI.dev.log

The file SetupAPI.app.log and SetupAPI.dev.log is maintained by the Windows operating system. To gather information useful for debugging Barracuda NG Network Access Client installation, this file has to be made more verbose.

Do get a more verbose SetupAPI.app.log and SetupAPI.dev.log file, the debug level has to be increased. Proceed as follows to do so:

 

1. Open the Registry Editor (Regedit.exe) and browse to the key

  HEKY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\

 

2. Create a new REG_DWORD value with the following values:
    Value name: LogLevel
    Value data: 0x0000xxxx  

 

        The possible "value data" are...
              0x00000000     Sets the logging level to the default values for both logs.
              0x00000101     Sets the logging level to OFF for both logs.
              0x00001010     Sets the logging level to TXTLOG_ERROR for both logs.
              0x00002020     Sets the logging level to TXTLOG_WARNING for both logs.
              0x00005050     Sets the logging level to TXTLOG_DETAILS for both logs.
              0x00006060     Sets the logging level to TXTLOG_VERBOSE for both logs.
              0x00007070     Sets the logging level to TXTLOG_VERY_VERBOSE for both logs.

 

3. The default debug level has the Value data 0x00000000. Reset the debug level to the default after installation has
    completed.


4. The SetupAPI.app.log and SetupAPI.dev.log will be stored in c:\WINDOWS\ 


Barracuda NG Network Access Client debug file: setupclient.log

 

Creation of the setupvpn.log file can be triggered on demand. Proceed as follows to obtain a Barracuda NG Network Access Client installation log file:

 

1. Copy the phion VPN Client installation file setup.exe to a specific subdirectory (e.g. C:\TEMP).

    C:\TEMP\setup.exe

 

2. Create a shortcut to the installation file on the desktop.

 

3. Open the shortcut's properties and on the "Shortcut" tab extend the value in the field "Target" with the option 
    "/Lvecumwi setupclient.log".

    C:\TEMP\setup.exe /V"/L*vx setupclient.log"

 

*vx is the same, plus extra, of the command already there. Since the parameter for this solution was initially done under the very old setups, still using Windows Installer 2.0, this was not yet included. But all recent versions of Windows use the newer 3.0 Installer, so this adjustment helps.


 

4. As soon as installation is executed through the shortcut, the file setupvpn.log will be created in the same folder as the file "setup.exe" is lying in.C:\TEMP\setupclient.log.

 

screenshot1.png - Latest 02/Jun/16 9:41 PM - Martin Tschugg 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Attention!
If you use Registry Editor incorrectly, you can cause serious problems that may require you to reinstall your operating system. phion does not guarantee that problems that you cause by using Registry Editor incorrectly can be resolved. Use Registry Editor at your own risk.

 

 

Link to This Page:
https://campus.barracuda.com/solution/50160000000IKYpAAO