Forum Discussion

Ken_Morley's avatar
Ken_Morley
Level 3
15 years ago

The Backup Exec user interface can only be run as a fully trusted application under .NET security policies

I downloaded and installed BEWS 12.5 on our Windows 2008 Small Business Server (64-bit) this morning without problem.  Following installation, Live Update ran and applied a bunch of patches including SP3.  I then rebooted the server and tried launching Backup Exec for the first time.  I immediately get the following error:

The Backup Exec user interface can only be run as a fully trusted application under .NET security policies.  This means you must run it from a directory on your local computer or you must configure .NET security to fully trust the application from a network location.  (For more information, see http://entsupport.symantec.com/umi/V-259-0012)

The application is being run from C:\Program Files\Symantec\Backup Exec, which is about as local as I can get.  The referenced URL link opens Document ID 290571, which has absolutely nothing to do with this issue.

The problem details are:

Description:
Stopped working

Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: bkupexec.exe
Problem Signature 02: 12.5.2213.152
Problem Signature 03: 4addee38
Problem Signature 04: mscorlib
Problem Signature 05: 2.0.0.0
Problem Signature 06: 4a7cb192
Problem Signature 07: 2d18
Problem Signature 08: 79
Problem Signature 09: System.Security.Security
OS Version: 6.0.6001.2.1.0.305.9
Locale ID: 1033

 

Any ideas or suggestions?   

12.x and Earlier
Backup and Recovery
Backup Exec
Installing

24 Replies

Sort By
  • Hemant_Jain's avatar
    Hemant_Jain
    Level 6
    15 years ago
    Can you browse to c:\program files\symantec\backup exec\  and try launching bkupexe.exe from there? Is the install folder shared in your case? It seems .net policy configured on your server, do not trust the location where bkupexec.exe is located, and hence the message. This problem may exist, when trying to launch installable from a shared location, so make sure none of the folders in the folder structure for Backup Exec install is shared.

    Please mark it a solution, if this is useful.
    Thanks
  • Ken_Morley's avatar
    Ken_Morley
    Level 3
    15 years ago
    Thanks for the suggestion, but I already tried everything obvious.

    Looking through the directory structure, nothing in the path C:\Program Files\Symantec\Backup Exec\ is shared (I examined the properties of each folder and verified that Network Path: is "Not Shared").  I tried launching using BkupLnch.exe and BkupExec.exe and get the same error.  I am logged in as Administrator, but choosing the "Run as administrator" option makes no difference either.

    Any other ideas?
  • Mike_Microtask's avatar
    Mike_Microtask
    Level 2
    15 years ago
    I am having the same issue.  The server is brand new with very little configuration done to it.
    Anyone have any ideas?
  • townsepw's avatar
    townsepw
    15 years ago
    Make sure you are using the right version.  You will get that error when you run the 32 bit version on 64 bit and vice versa
  • darksilver's avatar
    darksilver
    Level 2
    15 years ago

    Same thing here also.

    Using Win 2k8 server standard 64Bit.
    BEWS is very dificult to install, never works the first time (I get error 1719) and only after rebooting I can get it to fully install. But then I get the same error (The Backup Exec user interface can only be run as a fully trusted application under .NET security policies. ) when I try to start it. I've spent several hours trying to get it to work with no luck. 

    Decided to remove all Symantec apps and go with some other apps that at least will load...


  • ErikT's avatar
    ErikT
    Level 2
    15 years ago
    Just installed the BE2010 beta version on a Win 2K8 std 64bit platform, fully updated/patched, no shares whatsoever, and cannot launch the interface.  Getting exact same error message as 1st poster.

    Anyone got any further with this?  Is messing with the .NET security an option?

    Any help would be greatly appreciated!
  • Anoop_Gervasis's avatar
    Anoop_Gervasis
    Level 2
    15 years ago


    Hi,

    We would like to investigate this further and do request your help for the same.

    Can you please try the following steps :

    1. Visit  http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx and download the Procmon utility from the site.

    2.Launch the console with the Procmon utility and the Sgmon utility running in the background.

    3.After the error message comes up, save the Procmon log, Sgmon log and the VXGather log from the Backup Exec server.

    Note:  Do not add any filters in the Procmon utility and please do save the logs in the PML format itself.

    4.Also, could you please go to  HKEY_LOCAL_MACHINE\Software\Classes\.pdf  and check if the user account you are logged on with has permissions on this key.

    We would really appreciate if you could please send us a screen shot of the permissions on this key in the registry.

    Please refer the below technotes if you need assistance in running the Sgmon debugging utility or in collecting the VXGather logs.

    Using the Backup Exec Debug Monitor (SGMon) for troubleshooting

    http://support.veritas.com/docs/309683

    How to collect Backup Exec for Windows Servers log file information needed by Symantec Technical Support for troubleshooting purposes (using VxGather 1.2.2)

    http://support.veritas.com/docs/318474

    How to schedule Live Debugging with Backup Exec for Windows Servers using the SGMon utility

    http://support.veritas.com/docs/329711

    Regards,

    Anoop