cancel
Showing results for 
Search instead for 
Did you mean: 

Management Console lässt sich nicht starten

sam36
Level 4

Hallo,

ich brauche dringend Hilfe. Unsere Backup Exec Management Konsole lässt sich nicht mehr starten. Die Dienste scheinen alle zu laufen, aber ich komme nicht mehr in die Verwaltungskonsole. Wo kann man weitere Fehlermeldungen finden?

Windows Server 2008 R2
Symantec Backup 2014.1

 

 

Name der fehlerhaften Anwendung: BackupExec.exe, Version: 14.1.1786.0, Zeitstempel: 0x5371d883
Name des fehlerhaften Moduls: clr.dll, Version: 4.0.30319.18063, Zeitstempel: 0x526767d0
Ausnahmecode: 0xc00000fd
Fehleroffset: 0x0000000000009774
ID des fehlerhaften Prozesses: 0x1108
Startzeit der fehlerhaften Anwendung: 0x01d07b448dfb392e
Pfad der fehlerhaften Anwendung: C:\Program Files\Symantec\Backup Exec\BackupExec.exe
Pfad des fehlerhaften Moduls: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
Berichtskennung: e66e080b-e737-11e4-9c21-00199958a462

 

[04/20/15 09:22:30]:[0872:0560]:[1]  [THEFHQuery::GetRecord::1087]   INVALID_RECORD_NUMBER 
[04/20/15 09:22:30]:[0872:0560]:[1]  [THEFHFileSystemObject::Status::2190]  GetRecord failed for record number 1868787301
[04/20/15 09:22:30]:[0872:0560]:[1]  [THEFHQuery::GetRecord::1087]   INVALID_RECORD_NUMBER 
[04/20/15 09:22:30]:[0872:0560]:[1]  [THEFHFileSystemObject::Status::2190]  GetRecord failed for record number 1868787301
[04/20/15 09:22:30]:[0872:0560]:[1]  [THEFHQuery::CacheNext::509]  file(r:\columbus\1786r\becat\beplugins\thefh\libbasictemplate\memorymappedfile.cpp) function(MemoryMappedFile::alloc) line(1064) error(1)

 

 

Stefan

5 REPLIES 5

AmolB
Moderator
Moderator
Employee Accredited Certified

Have you checked the below Microsoft article.

https://support.microsoft.com/en-us/kb/2640103?wa=wsignin1.0

pkh
Moderator
Moderator
   VIP    Certified

1) Delete your .Net Framework

2) Go to Add/Remove Programs and repair BE.  This will also re-install the .Net Framework.

3) Try again.

sam36
Level 4

Hi,

that works not for me.

I have open a support case.  pparently caused a vm the error.

I hope the technical support can help

sam36
Level 4

The Symantec Technical still waiting for. Ok. 

Today i can open the admin console, the backups are running. But when i connect my vmware vcenter, the console hangs. I have seen in the log:

 

BEREMOTE: [04/20/15 15:27:38] [3184]     [fsys\shared]        - FS_ResolveDevName: [\\MEDIA01.xx-x.de]
BEREMOTE: [04/20/15 15:27:38] [3184]     [fsys\mb2]           - MB2-Resolve returned 1
BEREMOTE: [04/20/15 15:27:38] [3184]     [fsys\notes2]        - Notes Agent:CLNFileSystem::ResolveDeviceName
BEREMOTE: [04/20/15 15:27:38] [3184]     [fsys\sql2]          - SQL_ResolveDeviceName - Not AG Job
BEREMOTE: [04/20/15 15:27:38] [3184]     [fsys\sql2]          - NOT SQL Device Name: \\MEDIA01.xx-x.de
BEREMOTE: [04/20/15 15:27:38] [3184]     [fsys\adc]           - ADC_ResolveDeviceName: pid = 2832, checking \\MEDIA01.xx-x.de
BEREMOTE: [04/20/15 15:27:38] [3184]     [beutil]             - ApplyRegExp(): Invalid input (\\MEDIA01.xx-x.de). Parsing Failed.
BEREMOTE: [04/20/15 15:27:38] [3184]     [beutil]             - GoodEvName(): Invalid EV device (\\MEDIA01.xx-x.de).
BEREMOTE: [04/20/15 15:27:38] [3184]     [beutil]             - ApplyRegExp(): Invalid input (\\MEDIA01.xx-x.de). Parsing Failed.
BEREMOTE: [04/20/15 15:27:38] [3184]     [beutil]             - GoodEvName(): Invalid EV device (\\MEDIA01.xx-x.de).
BEREMOTE: [04/20/15 15:27:38] [3184]     [beutil]             - Input Error (e000fe23) for Type: (43)
BEREMOTE: [04/20/15 15:27:38] [3184]     [fsys\ev]            - EVM_ResolveDeviceName: Function Enter
BEREMOTE: [04/20/15 15:27:38] [3184]     [beutil]             - ApplyRegExp(): Invalid input (\\MEDIA01.xx-x.de). Parsing Failed.
BEREMOTE: [04/20/15 15:27:38] [3184]     [fsys\ev]            - EVM_ResolveDeviceName: Invalid device name (\\MEDIA01.xx-x.de). Parsing Failed.
BEREMOTE: [04/20/15 15:27:38] [3184]     [fsys\ev]            - EVM_ResolveDeviceName: Function Exit
BEREMOTE: [04/20/15 15:27:38] [3184]     [fsys\ntfs]          - Not valid device name : \\MEDIA01.xx-x.de
BEREMOTE: [04/20/15 15:27:38] [3184]     [dsss]               + rpcdsserver.cpp (320):
BEREMOTE: [04/20/15 15:27:38] [3184]     [dsss]               | DS_OpenEnum2
BEREMOTE: [04/20/15 15:27:38] [3184]     [dsss\rpc]           - RPCDsSession::GetLoginCredentials: Connecting to BEM API as user: xx-x\besadmin
BEREMOTE: [04/20/15 15:27:38] [3184]     [dsss]               + rpcdssession.cpp (414):
BEREMOTE: [04/20/15 15:27:38] [3184]     [dsss]               | RPCDsSession::OpenEnum being called for:
BEREMOTE: [04/20/15 15:27:38] [3184]     [dsss]               |     device = '\\MEDIA01.xx-x.de';
BEREMOTE: [04/20/15 15:27:38] [3184]     [dsss]               |     deviceType = 2;
BEREMOTE: [04/20/15 15:27:38] [3184]     [dsss]               |     osId = 14;
BEREMOTE: [04/20/15 15:27:38] [3184]     [dsss]               |     path = '';
BEREMOTE: [04/20/15 15:27:38] [3184]     [dsss]               |     username = 'xx-x\besadmin';
BEREMOTE: [04/20/15 15:27:38] [3184]     [dsss]               |     password is present
BEREMOTE: [04/20/15 15:27:38] [3184]     [dsss]               | .
BEREMOTE: [04/20/15 15:27:38] [2336]     [fsys\shared]        - FS_CreateTempDLE
BEREMOTE: [04/20/15 15:27:38] [2336]     [fsys\shared]        -   11 = 0xE000FE23
BEREMOTE: [04/20/15 15:27:38] [2336]     [fsys\shared]        -   12 = 0x00000001
BEREMOTE: [04/20/15 15:27:38] [2336]     [fsys\notes2]        - Notes Agent:CLNFileSystem::CreateTempDLE
BEREMOTE: [04/20/15 15:27:38] [2336]     [fsys\notes2]        - Notes Agent:CLNFileSystem::CreateTempDLE Exiting[-536805853]
BEREMOTE: [04/20/15 15:27:38] [2336]     [fsys\shared]        -   13 = 0xE000FE23
BEREMOTE: [04/20/15 15:27:38] [2336]     [fsys\oracle]        - RMAN_CreateTempDLE: Function called
BEREMOTE: [04/20/15 15:27:38] [2336]     [fsys\shared]        -   14 = 0xE000FE23
BEREMOTE: [04/20/15 15:27:38] [2336]     [fsys\sql2]          - CreateTempDLE \\MEDIA01.xx-x.de
BEREMOTE: [04/20/15 15:27:38] [2336]     [fsys\sql2]          - CreateTempDLE bailing, osId != SQL2_ID
BEREMOTE: [04/20/15 15:27:38] [2336]     [fsys\shared]        -   16 = 0xE000FE23
BEREMOTE: [04/20/15 15:27:38] [2336]     [fsys\shared]        -   17 = 0xE000FE23
BEREMOTE: [04/20/15 15:27:38] [2336]     [fsys\shared]        -   18 = 0x00000001
BEREMOTE: [04/20/15 15:27:38] [2336]     [fsys\ese]           - CreateTempDLE: \\MEDIA01.xx-x.de
BEREMOTE: [04/20/15 15:27:38] [2336]     [fsys\shared]        -   19 = 0xE00084AF
BEREMOTE: [04/20/15 15:27:38] [2336]     [fsys\shared]        -   20 = 0xE00084AF
BEREMOTE: [04/20/15 15:27:38] [2336]     [fsys\shared]        -   21 = 0xE00084AF
BEREMOTE: [04/20/15 15:27:38] [2336]     [fsys\ohfs]          - OFF_HOST_FS::OpenOHMetadataFile( :( error Opening the file (C:\Program Files\Symantec\Backup Exec\Data\OHTEMP\) error (3)
BEREMOTE: [04/20/15 15:27:38] [2336]     [fsys\ohfs]          - OFF_HOST_FS::GetDLEDetailsFromMDSrc() Status E_FS_OFF_HOST_DATA_CREATE_ERROR (E0000301) Opening the metadata source
BEREMOTE: [04/20/15 15:27:38] [2336]     [fsys\ohfs]          - OFF_HOST_FS::CreateTempDLE( ) Status E_FS_OFF_HOST_DATA_CREATE_ERROR (E0000301) creating Dle when creating temp Dle for device \\MEDIA01.xx-x.de
BEREMOTE: [04/20/15 15:27:38] [2336]     [fsys\shared]        -   23 = 0xE0000301
BEREMOTE: [04/20/15 15:27:38] [2336]     [fsys\shared]        -   30 = 0xE00084AF
BEREMOTE: [04/20/15 15:27:38] [2336]     [fsys\shared]        -   31 = 0xE00084AF
BEREMOTE: [04/20/15 15:27:38] [2336]     [fsys\shared]        -   33 = 0xE000FE23
BEREMOTE: [04/20/15 15:27:38] [2336]     [fsys\ese]           - CreateTempDLE: \\MEDIA01.xx-x.de
BEREMOTE: [04/20/15 15:27:38] [2336]     [fsys\shared]        -   35 = 0xE00084AF
BEREMOTE: [04/20/15 15:27:38] [2336]     [fsys\shared]        -   36 = 0xE00084AF
BEREMOTE: [04/20/15 15:27:38] [2336]     [fsys\shared]        -   37 = 0xE000FE23
BEREMOTE: [04/20/15 15:27:38] [2336]     [fsys\shared]        -   38 = 0xE00084AF
BEREMOTE: [04/20/15 15:27:38] [2336]     [fsys\vmvcb]         - VM_VCBPROXY_FS::CreateTempDLE( ) Status DRIVE_DESCRIPTOR_ERROR (E000FE23) creating Dle when creating temp Dle for device \\MEDIA01.xx-x.de
BEREMOTE: [04/20/15 15:27:38] [2336]     [fsys\shared]        -   39 = 0xE000FE23
BEREMOTE: [04/20/15 15:27:38] [2336]     [fsys\shared]        -   42 = 0xE000FE23
BEREMOTE: [04/20/15 15:27:38] [2336]     [fsys\shared]        -   45 = 0xE000FE23
BEREMOTE: [04/20/15 15:27:38] [2336]     [fsys\shared]        -   46 = 0xE00084AF
BEREMOTE: [04/20/15 15:27:38] [2336]     [fsys\shared]        -   47 = 0xE000FE23
BEREMOTE: [04/20/15 15:27:38] [2336]     [fsys\ese]           - CreateTempDLE: \\MEDIA01.xx-x.de
BEREMOTE: [04/20/15 15:27:38] [2336]     [fsys\shared]        -   48 = 0xE00084AF
BEREMOTE: [04/20/15 15:27:38] [2336]     [fsys\shared]        -    5 = 0xE000FE23
BENETNS:  [04/20/15 15:27:38] [0396]                          - NRDS API - client connected.
BEREMOTE: [04/20/15 15:27:38] [2336]     [fsys\ntfs\mnet]     - no NRDS cache-hit for MEDIA01.xx-x.de
BENETNS:  [04/20/15 15:27:38] [0396]                          - NRDS API - client disconnected.
BEREMOTE: [04/20/15 15:27:38] [2336]     [fsys\ntfs\mnet]     - Informational: Restrict Anonymous Support is enabled
BEREMOTE: [04/20/15 15:27:38] [2336]     [fsys\ntfs\mnet]     - creating DLE for remote machine \\MEDIA01.xx-x.de
BEREMOTE: [04/20/15 15:27:38] [2336]     Did not detect Microsoft cluster (MEDIA01)
BEREMOTE: [04/20/15 15:27:38] [2336]     Did not detect VCS cluster (MEDIA01)
BEREMOTE: [04/20/15 15:27:38] [2336]                          - Acquiring Critical Resource interface in 'ICriticalResource::AcquireInstance:496'
BEREMOTE: [04/20/15 15:27:38] [2336]                          - Successfully acquired critical resource interface.  Critical device bits will be set. in 'CritSysProt::CritSysProt:39'
BEREMOTE: [04/20/15 15:27:38] [2336]                          - Resource '\\MEDIA01.xx-x.de' supports features: ' NONE '  (0x00000200) in 'CritSysProt::DetermineCriticalResources:204'
BEREMOTE: [04/20/15 15:27:38] [2336]     [fsys\shared]        -    7 = 0x00000000
BEREMOTE: [04/20/15 15:27:38] [2336]                          - Acquiring Critical Resource interface in 'ICriticalResource::AcquireInstance:496'
BEREMOTE: [04/20/15 15:27:38] [2336]                          - Successfully acquired critical resource interface.  Critical device bits will be set. in 'CritSysProt::CritSysProt:39'
BEREMOTE: [04/20/15 15:27:38] [2336]                          - Resource '\\MEDIA01.xx-x.de' supports features: ' NONE '  (0x00000200) in 'CritSysProt::DetermineCriticalResources:204'
BEREMOTE: [04/20/15 15:27:38] [2336]     [dsss]               + dsworkerthread.cpp (220):

apparently he has problems with this vm media01. the machine I was deleting it from the inventory.But I do not dare to make a connect to the vcenter, because otherwise I do not come back today in the admin console.

Does anyone know this error?

 

 

 

sam36
Level 4

After delete the vm "media01.xxx", (show logs) at admin console, i can connect the vcenter. it works.