Comprehensive data protection for all workloads
Post Reply
johnb23
Novice
Posts: 9
Liked: 1 time
Joined: Nov 08, 2020 2:56 am
Full Name: John Bragg
Contact:

Veeam Backup & Replication Console Fails to Open

Post by johnb23 »

Hi,
I have been running Veeam Backup & Replication v9 Community for around 6 months and recently the Console Fails to Open.

I tried reinstalling the console, then reinstalling the product, then upgrading to version 10a. I have also checked that the services are running (SQL Server service + Veeam Services), ran Windows updates, ran Veeam's "Configure Database Connection Settings", and just going next > next > finish to apply the settings.

But none of this has solved the issue. The system is Windows Server 2012R2.

Please assist

John.
Egor Yakovlev
Product Manager
Posts: 2578
Liked: 707 times
Joined: Jun 14, 2013 9:30 am
Full Name: Egor Yakovlev
Location: Prague, Czech Republic
Contact:

Re: Veeam Backup & Replication Console Fails to Open

Post by Egor Yakovlev »

Hi John

Please provide a support case ID for this issue, as requested when you click New Topic, otherwise we will have to play a guessing game here.
Does it give any error message? Check console logs under C:\ProgramData\Veeam\Backup\

/Thanks!
johnb23
Novice
Posts: 9
Liked: 1 time
Joined: Nov 08, 2020 2:56 am
Full Name: John Bragg
Contact:

Re: Veeam Backup & Replication Console Fails to Open

Post by johnb23 »

Hi Egor,
Thanks for your reply. Since posting this I have spent several hours investigating and discovered Windows Event Log entries as per below:

Faulting application name: veeam.backup.shell.exe, version: 10.0.1.4854, time stamp: 0x5f171f15
Faulting module name: KERNELBASE.dll, version: 6.3.9600.19724, time stamp: 0x5ec5262a
Exception code: 0xe0434352
Fault offset: 0x0000000000007afc
Faulting process id: 0x2604
Faulting application start time: 0x01d6b5802e48b267
Faulting application path: C:\Program Files\Veeam\Backup and Replication\Console\veeam.backup.shell.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: 6c2bee16-2173-11eb-8144-20474784743e
Faulting package full name:
Faulting package-relative application ID:

I have also lodged a support ticket (case number is 04483683).

In terms of logs. I have checked these four directories which are under C:\Program Files\Veeam and couldn't find any logs.
Backup and Replication
Backup File System VSS Integration
Endpoint Backup
Veeam Distribution Service
soncscy
Veteran
Posts: 643
Liked: 312 times
Joined: Aug 04, 2019 2:57 pm
Full Name: Harvey
Contact:

Re: Veeam Backup & Replication Console Fails to Open

Post by soncscy »

Hey John,

Programdata, not Files ;)

I just checked my lab installation and there's a Backup and Replication folder there, which I suppose you need. Maybe the setup one too, but who knows, better more than less right?

Also, anything lead up to that message in your event log?
johnb23
Novice
Posts: 9
Liked: 1 time
Joined: Nov 08, 2020 2:56 am
Full Name: John Bragg
Contact:

Re: Veeam Backup & Replication Console Fails to Open

Post by johnb23 »

Hi,
I have checked and could not find ProgramData\Veeam\Backup\ under C drive, but did find the directory under F Drive. I navigated all the way down to F:\ProgramData\Veeam\Backup\IRCache\NfsDatastore but no files existed. (I checked to ensure that the directories are showing hidden files).

In regards to the event log - these are the three events posted under the Application event log when I attempt to open Veeam Backup & Replication Console

Code: Select all

Log Name:      Application
Source:        Windows Error Reporting
Date:          9/11/2020 6:44:27 PM
Event ID:      1001
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      LJServer.LJHJIM.local
Description:
Fault bucket 1522622337223970793, type 5
Event Name: CLR20r3
Response: Not available
Cab Id: 0

Problem signature:
P1: veeam.backup.shell.exe
P2: 10.0.1.4854
P3: 5f171f15
P4: System.Xml
P5: 4.8.3761.0
P6: 5c9c701a
P7: b85
P8: 27
P9: IOIBMURHYNRXKW0ZXKYRVFN0BOYYUFOW
P10: 

Attached files:
C:\Users\admin22\AppData\Local\Temp\WER686F.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_veeam.backup.she_171d546e8023101a23c843e7d79b61b51cb48d4_d7583113_2d0b7c74

Analysis symbol: 
Rechecking for solution: 0
Report Id: c2a3c5b3-2267-11eb-8144-20474784743e
Report Status: 0
Hashed bucket: 09eeef740875b2f4452170f2d14f4fe9
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Windows Error Reporting" />
    <EventID Qualifiers="0">1001</EventID>
    <Level>4</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2020-11-09T08:44:27.000000000Z" />
    <EventRecordID>3271742</EventRecordID>
    <Channel>Application</Channel>
    <Computer>LJServer.LJHJIM.local</Computer>
    <Security />
  </System>
  <EventData>
    <Data>1522622337223970793</Data>
    <Data>5</Data>
    <Data>CLR20r3</Data>
    <Data>Not available</Data>
    <Data>0</Data>
    <Data>veeam.backup.shell.exe</Data>
    <Data>10.0.1.4854</Data>
    <Data>5f171f15</Data>
    <Data>System.Xml</Data>
    <Data>4.8.3761.0</Data>
    <Data>5c9c701a</Data>
    <Data>b85</Data>
    <Data>27</Data>
    <Data>IOIBMURHYNRXKW0ZXKYRVFN0BOYYUFOW</Data>
    <Data>
    </Data>
    <Data>
C:\Users\admin22\AppData\Local\Temp\WER686F.tmp.WERInternalMetadata.xml</Data>
    <Data>C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_veeam.backup.she_171d546e8023101a23c843e7d79b61b51cb48d4_d7583113_2d0b7c74</Data>
    <Data>
    </Data>
    <Data>0</Data>
    <Data>c2a3c5b3-2267-11eb-8144-20474784743e</Data>
    <Data>0</Data>
    <Data>09eeef740875b2f4452170f2d14f4fe9</Data>
  </EventData>
</Event>


Log Name:      Application
Source:        Application Error
Date:          9/11/2020 6:44:21 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      LJServer.LJHJIM.local
Description:
Faulting application name: veeam.backup.shell.exe, version: 10.0.1.4854, time stamp: 0x5f171f15
Faulting module name: KERNELBASE.dll, version: 6.3.9600.19724, time stamp: 0x5ec5262a
Exception code: 0xe0434352
Fault offset: 0x0000000000007afc
Faulting process id: 0x22d4
Faulting application start time: 0x01d6b67483d22e2b
Faulting application path: C:\Program Files\Veeam\Backup and Replication\Console\veeam.backup.shell.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: c2a3c5b3-2267-11eb-8144-20474784743e
Faulting package full name: 
Faulting package-relative application ID: 
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2020-11-09T08:44:21.000000000Z" />
    <EventRecordID>3271741</EventRecordID>
    <Channel>Application</Channel>
    <Computer>LJServer.LJHJIM.local</Computer>
    <Security />
  </System>
  <EventData>
    <Data>veeam.backup.shell.exe</Data>
    <Data>10.0.1.4854</Data>
    <Data>5f171f15</Data>
    <Data>KERNELBASE.dll</Data>
    <Data>6.3.9600.19724</Data>
    <Data>5ec5262a</Data>
    <Data>e0434352</Data>
    <Data>0000000000007afc</Data>
    <Data>22d4</Data>
    <Data>01d6b67483d22e2b</Data>
    <Data>C:\Program Files\Veeam\Backup and Replication\Console\veeam.backup.shell.exe</Data>
    <Data>C:\Windows\system32\KERNELBASE.dll</Data>
    <Data>c2a3c5b3-2267-11eb-8144-20474784743e</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>


Log Name:      Application
Source:        .NET Runtime
Date:          9/11/2020 6:44:21 PM
Event ID:      1026
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      LJServer.LJHJIM.local
Description:
Application: veeam.backup.shell.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Xml.XmlException
   at System.Xml.XmlTextReaderImpl.Throw(System.Exception)
   at System.Xml.XmlTextReaderImpl.ParseDocumentContent()
   at System.Configuration.XmlUtil..ctor(System.IO.Stream, System.String, Boolean, System.Configuration.ConfigurationSchemaErrors)
   at System.Configuration.BaseConfigurationRecord.InitConfigFromFile()

Exception Info: System.Configuration.ConfigurationErrorsException
   at System.Configuration.ConfigurationSchemaErrors.ThrowIfErrors(Boolean)
   at System.Configuration.BaseConfigurationRecord.ThrowIfParseErrors(System.Configuration.ConfigurationSchemaErrors)
   at System.Configuration.ClientConfigurationSystem.OnConfigRemoved(System.Object, System.Configuration.Internal.InternalConfigEventArgs)

Exception Info: System.Configuration.ConfigurationErrorsException
   at System.Configuration.ClientConfigurationSystem.OnConfigRemoved(System.Object, System.Configuration.Internal.InternalConfigEventArgs)
   at System.Configuration.Internal.InternalConfigRoot.OnConfigRemoved(System.Configuration.Internal.InternalConfigEventArgs)
   at System.Configuration.Internal.InternalConfigRoot.RemoveConfigImpl(System.String, System.Configuration.BaseConfigurationRecord)
   at System.Configuration.BaseConfigurationRecord.GetSectionRecursive(System.String, Boolean, Boolean, Boolean, Boolean, System.Object ByRef, System.Object ByRef)
   at System.Configuration.BaseConfigurationRecord.GetSection(System.String)
   at System.Configuration.ConfigurationManager.GetSection(System.String)
   at System.Configuration.ClientSettingsStore.ReadSettings(System.String, Boolean)
   at System.Configuration.LocalFileSettingsProvider.GetPropertyValues(System.Configuration.SettingsContext, System.Configuration.SettingsPropertyCollection)
   at System.Configuration.SettingsBase.GetPropertiesFromProvider(System.Configuration.SettingsProvider)
   at System.Configuration.SettingsBase.GetPropertyValueByName(System.String)
   at System.Configuration.SettingsBase.get_Item(System.String)
   at System.Configuration.ApplicationSettingsBase.GetPropertyValue(System.String)
   at System.Configuration.ApplicationSettingsBase.get_Item(System.String)
   at Veeam.Backup.UI.Launcher.Properties.Settings.get_IsUpgradeRequired()
   at Veeam.Backup.UI.Launcher.CClientLauncherRunner.UpgradeUserSettings()
   at Veeam.Backup.UI.Launcher.CClientLauncherRunner.Run()
   at Veeam.Backup.UI.Launcher.CClientLauncherRunner.Run(Veeam.Backup.UI.Launcher.Vault.CProductHelper, Veeam.Backup.UI.Launcher.CServiceConnectionSpec ByRef)
   at VeeamShell.Program.Main(System.String[])


Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name=".NET Runtime" />
    <EventID Qualifiers="0">1026</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2020-11-09T08:44:21.000000000Z" />
    <EventRecordID>3271740</EventRecordID>
    <Channel>Application</Channel>
    <Computer>LJServer.LJHJIM.local</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Application: veeam.backup.shell.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Xml.XmlException
   at System.Xml.XmlTextReaderImpl.Throw(System.Exception)
   at System.Xml.XmlTextReaderImpl.ParseDocumentContent()
   at System.Configuration.XmlUtil..ctor(System.IO.Stream, System.String, Boolean, System.Configuration.ConfigurationSchemaErrors)
   at System.Configuration.BaseConfigurationRecord.InitConfigFromFile()

Exception Info: System.Configuration.ConfigurationErrorsException
   at System.Configuration.ConfigurationSchemaErrors.ThrowIfErrors(Boolean)
   at System.Configuration.BaseConfigurationRecord.ThrowIfParseErrors(System.Configuration.ConfigurationSchemaErrors)
   at System.Configuration.ClientConfigurationSystem.OnConfigRemoved(System.Object, System.Configuration.Internal.InternalConfigEventArgs)

Exception Info: System.Configuration.ConfigurationErrorsException
   at System.Configuration.ClientConfigurationSystem.OnConfigRemoved(System.Object, System.Configuration.Internal.InternalConfigEventArgs)
   at System.Configuration.Internal.InternalConfigRoot.OnConfigRemoved(System.Configuration.Internal.InternalConfigEventArgs)
   at System.Configuration.Internal.InternalConfigRoot.RemoveConfigImpl(System.String, System.Configuration.BaseConfigurationRecord)
   at System.Configuration.BaseConfigurationRecord.GetSectionRecursive(System.String, Boolean, Boolean, Boolean, Boolean, System.Object ByRef, System.Object ByRef)
   at System.Configuration.BaseConfigurationRecord.GetSection(System.String)
   at System.Configuration.ConfigurationManager.GetSection(System.String)
   at System.Configuration.ClientSettingsStore.ReadSettings(System.String, Boolean)
   at System.Configuration.LocalFileSettingsProvider.GetPropertyValues(System.Configuration.SettingsContext, System.Configuration.SettingsPropertyCollection)
   at System.Configuration.SettingsBase.GetPropertiesFromProvider(System.Configuration.SettingsProvider)
   at System.Configuration.SettingsBase.GetPropertyValueByName(System.String)
   at System.Configuration.SettingsBase.get_Item(System.String)
   at System.Configuration.ApplicationSettingsBase.GetPropertyValue(System.String)
   at System.Configuration.ApplicationSettingsBase.get_Item(System.String)
   at Veeam.Backup.UI.Launcher.Properties.Settings.get_IsUpgradeRequired()
   at Veeam.Backup.UI.Launcher.CClientLauncherRunner.UpgradeUserSettings()
   at Veeam.Backup.UI.Launcher.CClientLauncherRunner.Run()
   at Veeam.Backup.UI.Launcher.CClientLauncherRunner.Run(Veeam.Backup.UI.Launcher.Vault.CProductHelper, Veeam.Backup.UI.Launcher.CServiceConnectionSpec ByRef)
   at VeeamShell.Program.Main(System.String[])

</Data>
  </EventData>
</Event>
Regards
John.
johnb23
Novice
Posts: 9
Liked: 1 time
Joined: Nov 08, 2020 2:56 am
Full Name: John Bragg
Contact:

Re: Veeam Backup & Replication Console Fails to Open

Post by johnb23 »

further to the above - I have navigated to C:\ProgramData\Microsoft\Windows\WER\ReportArchive and opened the specified file: ReportArchive\AppCrash_veeam.backup.she_171d546e8023101a23c843e7d79b61b51cb48d4_d7583113_2d0b7c74 in Notepad. The contents is pasted below. Hopefully this also helps.

Code: Select all

Version=1
EventType=CLR20r3
EventTime=132493850619600313
ReportType=2
Consent=1
UploadTime=132493850619990242
ReportIdentifier=c2a3c5b4-2267-11eb-8144-20474784743e
IntegratorReportIdentifier=c2a3c5b3-2267-11eb-8144-20474784743e
NsAppName=veeam.backup.shell.exe
Response.BucketId=09eeef740875b2f4452170f2d14f4fe9
Response.BucketTable=5
Response.LegacyBucketId=1522622337223970793
Response.type=4
Sig[0].Name=Problem Signature 01
Sig[0].Value=veeam.backup.shell.exe
Sig[1].Name=Problem Signature 02
Sig[1].Value=10.0.1.4854
Sig[2].Name=Problem Signature 03
Sig[2].Value=5f171f15
Sig[3].Name=Problem Signature 04
Sig[3].Value=System.Xml
Sig[4].Name=Problem Signature 05
Sig[4].Value=4.8.3761.0
Sig[5].Name=Problem Signature 06
Sig[5].Value=5c9c701a
Sig[6].Name=Problem Signature 07
Sig[6].Value=b85
Sig[7].Name=Problem Signature 08
Sig[7].Value=27
Sig[8].Name=Problem Signature 09
Sig[8].Value=IOIBMURHYNRXKW0ZXKYRVFN0BOYYUFOW
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.3.9600.2.0.0.305.50
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=3081
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=e44c
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=e44c9bae2a19f2a4176eff968e00ad1a
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=1516
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=15164b3f3941f9ee93e95fb3a5673d9e
UI[2]=C:\Program Files\Veeam\Backup and Replication\Console\veeam.backup.shell.exe
LoadedModule[0]=C:\Program Files\Veeam\Backup and Replication\Console\veeam.backup.shell.exe
LoadedModule[1]=C:\Windows\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\Windows\SYSTEM32\MSCOREE.DLL
LoadedModule[3]=C:\Windows\system32\KERNEL32.dll
LoadedModule[4]=C:\Windows\system32\KERNELBASE.dll
LoadedModule[5]=C:\Windows\system32\ADVAPI32.dll
LoadedModule[6]=C:\Windows\system32\msvcrt.dll
LoadedModule[7]=C:\Windows\SYSTEM32\sechost.dll
LoadedModule[8]=C:\Windows\system32\RPCRT4.dll
LoadedModule[9]=C:\Windows\system32\SspiCli.dll
LoadedModule[10]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\mscoreei.dll
LoadedModule[11]=C:\Windows\system32\SHLWAPI.dll
LoadedModule[12]=C:\Windows\SYSTEM32\combase.dll
LoadedModule[13]=C:\Windows\system32\USER32.dll
LoadedModule[14]=C:\Windows\system32\GDI32.dll
LoadedModule[15]=C:\Windows\system32\IMM32.DLL
LoadedModule[16]=C:\Windows\system32\MSCTF.dll
LoadedModule[17]=C:\Windows\SYSTEM32\kernel.appcore.dll
LoadedModule[18]=C:\Windows\SYSTEM32\VERSION.dll
LoadedModule[19]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
LoadedModule[20]=C:\Windows\SYSTEM32\VCRUNTIME140_CLR0400.dll
LoadedModule[21]=C:\Windows\SYSTEM32\ucrtbase_clr0400.dll
LoadedModule[22]=C:\Windows\assembly\NativeImages_v4.0.30319_64\mscorlib\9feb7da5be83625fe0b90296fdb01d2f\mscorlib.ni.dll
LoadedModule[23]=C:\Windows\system32\ole32.dll
LoadedModule[24]=C:\Windows\SYSTEM32\CRYPTBASE.dll
LoadedModule[25]=C:\Windows\SYSTEM32\bcryptPrimitives.dll
LoadedModule[26]=C:\Windows\system32\uxtheme.dll
LoadedModule[27]=C:\Program Files (x86)\TeamViewer\tv_x64.dll
LoadedModule[28]=C:\Windows\system32\SHELL32.dll
LoadedModule[29]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clrjit.dll
LoadedModule[30]=C:\Windows\SYSTEM32\CRYPTSP.dll
LoadedModule[31]=C:\Windows\system32\rsaenh.dll
LoadedModule[32]=C:\Windows\SYSTEM32\bcrypt.dll
LoadedModule[33]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System\adc3274d14839555a41f86a16e69371b\System.ni.dll
LoadedModule[34]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Core\21f58d7b44f86a37f41c285a11cb635d\System.Core.ni.dll
LoadedModule[35]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Drawing\76d07ed40af688e16268adac57348a00\System.Drawing.ni.dll
LoadedModule[36]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Windows.Forms\3c19b6bcab27d68ddcee00814e3a59aa\System.Windows.Forms.ni.dll
LoadedModule[37]=C:\Windows\assembly\NativeImages_v4.0.30319_64\WindowsBase\52cf23ead6542e83e015c4cd1d2eb617\WindowsBase.ni.dll
LoadedModule[38]=C:\Windows\assembly\NativeImages_v4.0.30319_64\PresentationCore\4ca03082a002fa2fd06bf3ee4e78eb5c\PresentationCore.ni.dll
LoadedModule[39]=C:\Windows\assembly\NativeImages_v4.0.30319_64\Presentatio5ae0f00f#\515c36c57dbcbb4290ebed9643a4b6e2\PresentationFramework.ni.dll
LoadedModule[40]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Xaml\412621795dd68a58138ff81385476645\System.Xaml.ni.dll
LoadedModule[41]=C:\Windows\SYSTEM32\dwrite.dll
LoadedModule[42]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\WPF\wpfgfx_v0400.dll
LoadedModule[43]=C:\Windows\SYSTEM32\MSVCP140_CLR0400.dll
LoadedModule[44]=C:\Windows\system32\OLEAUT32.dll
LoadedModule[45]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\WPF\PresentationNative_v0400.dll
LoadedModule[46]=C:\Windows\system32\SHCORE.dll
LoadedModule[47]=C:\Windows\system32\profapi.dll
LoadedModule[48]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Configuration\c9dabb08bcb0c404e7cbc9d367f8e209\System.Configuration.ni.dll
LoadedModule[49]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Xml\d999e7e6ee9c44d2bfe5faf69e7208ba\System.Xml.ni.dll
LoadedModule[50]=C:\Windows\system32\dwmapi.dll
LoadedModule[51]=C:\Windows\assembly\NativeImages_v4.0.30319_64\WindowsForm0b574481#\d08495fe385bb7b95444552b1f3f8872\WindowsFormsIntegration.ni.dll
LoadedModule[52]=C:\Windows\assembly\NativeImages_v4.0.30319_64\Presentatio53a7a42c#\c3f096f190de757426d411faef584c39\PresentationFramework.AeroLite.ni.dll
LoadedModule[53]=C:\Windows\SYSTEM32\urlmon.dll
LoadedModule[54]=C:\Windows\SYSTEM32\iertutil.dll
LoadedModule[55]=C:\Windows\SYSTEM32\WININET.dll
LoadedModule[56]=C:\Windows\SYSTEM32\USERENV.dll
LoadedModule[57]=C:\Windows\SYSTEM32\Secur32.dll
LoadedModule[58]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\diasymreader.dll
State[0].Key=Transport.DoneStage1
State[0].Value=1
FriendlyEventName=Stopped working
ConsentKey=CLR20r3
AppName=Veeam.Backup.Shell
AppPath=C:\Program Files\Veeam\Backup and Replication\Console\veeam.backup.shell.exe
NsPartner=windows
NsGroup=windows8
ApplicationIdentity=34FC929D7211798B6B51E2723E8D51B3
6:51 PM 9/11/2020
Egor Yakovlev
Product Manager
Posts: 2578
Liked: 707 times
Joined: Jun 14, 2013 9:30 am
Full Name: Egor Yakovlev
Location: Prague, Czech Republic
Contact:

Re: Veeam Backup & Replication Console Fails to Open

Post by Egor Yakovlev »

Thanks for sharing case ID.
You can try refreshing your .NET Framework installation on said machine meanwhile waiting an answer from support.
johnb23
Novice
Posts: 9
Liked: 1 time
Joined: Nov 08, 2020 2:56 am
Full Name: John Bragg
Contact:

Re: Veeam Backup & Replication Console Fails to Open

Post by johnb23 »

I have refreshed .NET Framework but this did not resolve the issue. Hopefully I will receive a resolution soon.

John.
johnb23
Novice
Posts: 9
Liked: 1 time
Joined: Nov 08, 2020 2:56 am
Full Name: John Bragg
Contact:

Re: Veeam Backup & Replication Console Fails to Open

Post by johnb23 »

I hope that Veeam technical support can look at this and post a resolution. From a google search - it seems that others have experienced the same issue.

John.
Egor Yakovlev
Product Manager
Posts: 2578
Liked: 707 times
Joined: Jun 14, 2013 9:30 am
Full Name: Egor Yakovlev
Location: Prague, Czech Republic
Contact:

Re: Veeam Backup & Replication Console Fails to Open

Post by Egor Yakovlev » 4 people like this post

It is an infrastructure-specific issue.

Can you please try the following:
- navigate to C:\Users\[YourUserName]\AppData\Local\Veeam_Software_Group_GmbH\veeam.backup.shell.exe_Url_hu1utqnj52thvmhrg5kie2bl15o22i22\10.0.0.0
- rename the user.config file
- launch VBR console

See if that helps.
johnb23
Novice
Posts: 9
Liked: 1 time
Joined: Nov 08, 2020 2:56 am
Full Name: John Bragg
Contact:

Re: Veeam Backup & Replication Console Fails to Open

Post by johnb23 »

Hi,
This has resolved the issue and Console now opens. However - when I attempt to start the backup job it stops with the error "11/11/2020 11:01:55 PM :: Processing LJServer.LJHJIM.local Error: No connection could be made because the target machine actively refused it 192.168.15.250:6184 "

I have ran 'Configuration Database Connection Settings' but this has not resolved the new issue.

Thank you - much appreciated in terms of resolving the console issue. Any suggestion in regards to the next issue would be appreciated. It is late here so I re-check this forum tomorrow.

John.
Egor Yakovlev
Product Manager
Posts: 2578
Liked: 707 times
Joined: Jun 14, 2013 9:30 am
Full Name: Egor Yakovlev
Location: Prague, Czech Republic
Contact:

Re: Veeam Backup & Replication Console Fails to Open

Post by Egor Yakovlev »

Thanks for update and I am glad it sorted out with the console start!

Fresh issue with job is non-related and it looks like communication with Veeam Agent is broken - give LJ server a reboot and go under Inventory node -> rescan the agent machine from Physical Infrastructure there - that should give more clues to follow.

/Cheers!
johnb23
Novice
Posts: 9
Liked: 1 time
Joined: Nov 08, 2020 2:56 am
Full Name: John Bragg
Contact:

Re: Veeam Backup & Replication Console Fails to Open

Post by johnb23 »

Thank you for the reply.

I have performed the inventory scan and discovered that the agent is missing. Tried to install the agent but the server is advising that it requires a reboot first. Unfortunately - I have to wait until afterhours tonight. I will advise of the outcome once the server has been rebooted and agent installed.

Regards
John.
johnb23
Novice
Posts: 9
Liked: 1 time
Joined: Nov 08, 2020 2:56 am
Full Name: John Bragg
Contact:

Re: Veeam Backup & Replication Console Fails to Open

Post by johnb23 » 1 person likes this post

Hi All,
This has now resolved itself after a server reboot.

Thank you for your assistance and I hope that this thread assists others in the future.

Regards
John.
alexmilla
Lurker
Posts: 1
Liked: 2 times
Joined: Jan 28, 2021 11:28 am
Full Name: Alex Milla
Contact:

Re: Veeam Backup & Replication Console Fails to Open

Post by alexmilla » 2 people like this post

Egor Yakovlev wrote: Nov 11, 2020 11:29 am It is an infrastructure-specific issue.

Can you please try the following:
- navigate to C:\Users\[YourUserName]\AppData\Local\Veeam_Software_Group_GmbH\veeam.backup.shell.exe_Url_hu1utqnj52thvmhrg5kie2bl15o22i22\10.0.0.0
- rename the user.config file
- launch VBR console

See if that helps.
Great, your solution worked on the first try. :D
StephanG
Enthusiast
Posts: 80
Liked: 4 times
Joined: Sep 07, 2014 11:15 am
Full Name: Stephan G
Contact:

Re: Veeam Backup & Replication Console Fails to Open

Post by StephanG »

Having the same problem. But where is the folder for v11?
Renaming the file does not work.
--
Workaround: Created a new user on the server and with a clean profile it works - the config file must be somewhere ;)
Egor Yakovlev
Product Manager
Posts: 2578
Liked: 707 times
Joined: Jun 14, 2013 9:30 am
Full Name: Egor Yakovlev
Location: Prague, Czech Republic
Contact:

Re: Veeam Backup & Replication Console Fails to Open

Post by Egor Yakovlev »

Hi Stephan,

Path to config file is pretty much the same in v11, just a different sub

Code: Select all

C:\Users\[UserName]\AppData\Local\Veeam_Software_Group_GmbH\veeam.backup.shell.exe_Url_hu1utqnj52thvmhrg5kie2bl15o22i22\11.0.0.0\user.config
stevenrodenburg1
Expert
Posts: 135
Liked: 20 times
Joined: May 31, 2011 9:11 am
Full Name: Steven Rodenburg
Location: Switzerland
Contact:

Re: Veeam Backup & Replication Console Fails to Open

Post by stevenrodenburg1 »

"Workaround: Created a new user on the server and with a clean profile it works - the config file must be somewhere"

No no no that is a "throwing away the baby with the bathwater solution" :|
The console can be a bit "iffy" and so if this happens again in the future, simply delete the "C:\Users\[UserName]\AppData\Local\Veeam_Software_Group_GmbH" folder and it should start again without a problem. The folder will be re-created and all is good again.
Butha
Enthusiast
Posts: 41
Liked: 22 times
Joined: Oct 03, 2012 10:59 am
Full Name: Butha van der Merwe
Contact:

Re: Veeam Backup & Replication Console Fails to Open

Post by Butha »

Sorted it out straight away thanks.

W11..
robnicholsonmalt
Expert
Posts: 128
Liked: 22 times
Joined: Dec 21, 2018 11:42 am
Full Name: Rob Nicholson
Contact:

Re: Veeam Backup & Replication Console Fails to Open

Post by robnicholsonmalt »

Egor Yakovlev wrote: Nov 11, 2020 11:29 am It is an infrastructure-specific issue.

Can you please try the following:
- navigate to C:\Users\[YourUserName]\AppData\Local\Veeam_Software_Group_GmbH\veeam.backup.shell.exe_Url_hu1utqnj52thvmhrg5kie2bl15o22i22\10.0.0.0
- rename the user.config file
- launch VBR console

See if that helps.
Just a heads up that I've just had the console not opening and this worked for me too.
icesteel
Novice
Posts: 5
Liked: never
Joined: Sep 21, 2020 7:02 pm
Full Name: Porto
Contact:

Re: Veeam Backup & Replication Console Fails to Open

Post by icesteel »

Thanks! It work for me too. I think was a pending update, but, it work. :D
Egor Yakovlev
Product Manager
Posts: 2578
Liked: 707 times
Joined: Jun 14, 2013 9:30 am
Full Name: Egor Yakovlev
Location: Prague, Czech Republic
Contact:

Re: Veeam Backup & Replication Console Fails to Open

Post by Egor Yakovlev »

Already released Veeam Backup & Replication v12 offers an automatic detection & healing of a corrupted user.config file.
/Cheers!
john.kinnaird
Lurker
Posts: 1
Liked: 1 time
Joined: May 14, 2023 5:19 pm
Full Name: john kinnaird
Contact:

Re: Veeam Backup & Replication Console Fails to Open

Post by john.kinnaird » 1 person likes this post

Egor Yakovlev wrote: Nov 11, 2020 11:29 am It is an infrastructure-specific issue.

Can you please try the following:
- navigate to C:\Users\[YourUserName]\AppData\Local\Veeam_Software_Group_GmbH\veeam.backup.shell.exe_Url_hu1utqnj52thvmhrg5kie2bl15o22i22\10.0.0.0
- rename the user.config file
- launch VBR console

See if that helps.
Worked for me as well - Many Thanks !!!!
Post Reply

Who is online

Users browsing this forum: FrancWest, Google [Bot], HansMeiser, Majestic-12 [Bot], Maxim.Arkhangelskiy, Semrush [Bot] and 137 guests