Failed to initialize COM runtime (0x8007058) -Case #00503567

Hyper-V specific discussions

Failed to initialize COM runtime (0x8007058) -Case #00503567

Veeam Logoby dbarroco » Thu Jan 16, 2014 11:47 am

Any one has been across this error?

One HyperV host and a win7 veeam 7 R2.

Often is failing the populate the local Backup Repository (on a local disk). Jobs fail right after the initial vm listing.

Event errors show either the "Failed to Initialize COM Runtime" and "Failed to initialize agent".

Only backup that ran ok was after a reboot. Other than that fails.
dbarroco
Novice
 
Posts: 9
Liked: never
Joined: Thu Apr 14, 2011 6:59 pm
Full Name: David B

Re: Failed to initialize COM runtime (0x8007058) -Case #0050

Veeam Logoby Vitaliy S. » Thu Jan 16, 2014 2:39 pm

Seems like something is wrong with the Windows Server itself. Let's see what our support can say after reviewing your log files. Also I wonder what other system errors are present in the Windows Event log, this might give a clue on what's going on.
Vitaliy S.
Product Manager
 
Posts: 11720
Liked: 411 times
Joined: Mon Mar 30, 2009 9:13 am
Full Name: Vitaliy Safarov

Re: Failed to initialize COM runtime (0x8007058) -Case #0050

Veeam Logoby dbarroco » Thu Jan 16, 2014 2:41 pm

Meanwhile some updates while digging for more information

Aside from the error posted, I got some others when the backup does run, related to not being able to backup properly the SQL server. These are related to AAIP, so I went and did the registry update on the guests from this thread http://forums.veeam.com/microsoft-hyper-v-f25/job-warnings-after-upgrade-to-v7-t17719.html?hilit=Guest%20processing%20skipped and also on the sql server enabled the option for "Ignore application processing failures". The job options are set up for crash consistent. I followed these from this thread http://forums.veeam.com/microsoft-hyper-v-f25/v7-dynamic-disks-t18199.html as this machine has in fact a dynamic disk.

So for now I'm narrowed to the COM runtime error thing...and cannot replicate it everytime. Now the job runs when demanded...
dbarroco
Novice
 
Posts: 9
Liked: never
Joined: Thu Apr 14, 2011 6:59 pm
Full Name: David B

Re: Failed to initialize COM runtime (0x8007058) -Case #0050

Veeam Logoby dbarroco » Thu Jan 16, 2014 2:47 pm

Vitaliy S. wrote:Seems like something is wrong with the Windows Server itself. Let's see what our support can say after reviewing your log files. Also I wonder what other system errors are present in the Windows Event log, this might give a clue on what's going on.


Hi Vitaly,

The windows server would that be the host you say? Or the 'server' where Veeam is running (that is in fact a W7 machine)?

On the host I have few errors. Just one today that the server did not register DCOM. Can't really tell if they're related, since I have no error for yesterday on the host, but the job failed.

On the Veeam Server machine, On the event Ihave mainly the two errors posted. COM runtime and Failed to initialize agent (these on the veeam related events). On system/application events nothing relevant as well
dbarroco
Novice
 
Posts: 9
Liked: never
Joined: Thu Apr 14, 2011 6:59 pm
Full Name: David B

Re: Failed to initialize COM runtime (0x8007058) -Case #0050

Veeam Logoby Vitaliy S. » Thu Jan 16, 2014 3:28 pm

dbarroco wrote:Often is failing the populate the local Backup Repository (on a local disk). Jobs fail right after the initial vm listing.

I would start looking at the server that hosts this repository. BTW, if you temporary change the repository (Windows Server), does this issue confirm?
Vitaliy S.
Product Manager
 
Posts: 11720
Liked: 411 times
Joined: Mon Mar 30, 2009 9:13 am
Full Name: Vitaliy Safarov

Re: Failed to initialize COM runtime (0x8007058) -Case #0050

Veeam Logoby dbarroco » Thu Jan 16, 2014 3:49 pm

Don't know very well what else to look for on this machine. The repository is a new local SATA 3TB disk just large enough to accomodate some retention points. The repo is set to Windows Server.

Don't have many options left, maybe try on the main disk for a go and see.
dbarroco
Novice
 
Posts: 9
Liked: never
Joined: Thu Apr 14, 2011 6:59 pm
Full Name: David B

Re: Failed to initialize COM runtime (0x8007058) -Case #0050

Veeam Logoby Vitaliy S. » Thu Jan 16, 2014 3:54 pm

Changing disk might not solve the issue, I was thinking about isolating the problem either to the repository server/backup server or to some other component. Using a completely new Windows host could help with this.
Vitaliy S.
Product Manager
 
Posts: 11720
Liked: 411 times
Joined: Mon Mar 30, 2009 9:13 am
Full Name: Vitaliy Safarov

Re: Failed to initialize COM runtime (0x8007058) -Case #0050

Veeam Logoby dbarroco » Fri Jan 17, 2014 11:51 am

I got off the costumer plant...could not do any more tests. I was able to backup on demand during the day. Next time I go there I will check this and post further feedback.
dbarroco
Novice
 
Posts: 9
Liked: never
Joined: Thu Apr 14, 2011 6:59 pm
Full Name: David B

Re: Failed to initialize COM runtime (0x8007058) -Case #0050

Veeam Logoby ronken » Wed Jul 30, 2014 5:45 pm 1 person likes this post

the only way I was able to get the backup jobs running and bypass the com error was to select Edit Settings for each of our backup jobs and run through each screen, choosing to 'recalculate' and then Finish. Once I had done that the job would start and run with no errors. A restart of services and a reboot did not help.
ronken
Lurker
 
Posts: 1
Liked: 1 time
Joined: Wed Jul 30, 2014 3:26 pm
Full Name: Roger Onken


Return to Microsoft Hyper-V



Who is online

Users browsing this forum: No registered users and 4 guests