Error: Communications are down with the Backup Exec services

[Doofus1980]

Hi!

I get these messages every morning I check the backups. The only way around this is for me to restart the server, then run the backup manually or to start the services manually.

I also see this in the event log, could this have anything to do with it? I have followed these steps to try and correct it but no luck!

http://support.microsoft.com/kb/940032

http://www.pcreview.co.uk/forums/thread-3774861.php

Any help would be greatly appreciated! :)

[AmolB]

Could you please post the error description of  event id 1000

[itsmeaffinity]

Hi

Can you please follow the link below

http://www.symantec.com/docs/TECH71917

Please post update in case of any issue or you can mark this solved if this resolves the issue

Thank You

[Doofus1980]

I noticed I had a problem with Explorer today, but this wasn't an issue when I started getting these errors.

Thank you :)

[itsmeaffinity]

Hi

Please check if that Tech article help if not when you post update next time do let me know the backupexec version with updates like BE 2010 r2 sp1 & waht is version of windows like win2008 standar /enterprise or R2

Thank You

[CraigV]

Hi Doofus,

I'd recommend you start your troubleshooting by installing the latest service pack for BE along with any updates that followed that. Restart your server, and then try a backup again and see if it generates that same error.

If it does, run an update on Windows. Unless you're generating errors in the Application Log specifically referring to BE, I'd go with Windows being the issue here.

Laters!

[Doofus1980]

Thanks for the input so far, I have done a Windows update and see if it helped. This seems to happen over night. Once I've restartd the services manually it works all day.

I will have to see Monday morning, I will let you know :) 

Thanks! Albert

[itsmeaffinity]

Hi

Welcome & thanks for update

Cheers....:-)

Thank You

[itsmeaffinity]

Hi

Any updates here

Please mark this post solved if this has resolved the issue

Thank You

[Doofus1980]

Hi!

So sorry!

I tried those steps got a few funny messages that indicates something about me not having the rights to do this operation. So I need my manager to log in as the full administrator first. He was off yesterday and I'm not sure if he's in today.

Sorry guys I will update ASAP.

Thanks for your help :)

Albert

[itsmeaffinity]

Hi

Thanks for your update & much appreciated I will wait for your response on same

Keep posted

Thank You

[Doofus1980]

Update:

I have run those commands whilst logged in as an administarator and didn't get any errors. On my profile it ran for a few seconds then stopped, with the administrator account it ran for much longer and didn't give me the errors. I can now see Writer Name: 'System Writer' after running the "vssadmin list writers" command. I couldn't before. I will have to wait for the morning to see if the service has dropped again before I can give more feedback, but it looks promising. 

Thank you for your patience

Albert

[itsmeaffinity]

Hi

Hey thanks for update again & would wait for your next update on same & good to see all working fine till now

Please mark this solved if this issue is resolved

Keep Posted

Thank You

[Doofus1980]

Good morning, I'm still getting the message stating that the services hasn't started (as indicated in the very first picture in this thread). The VSS error is not in the event log anymore but this CAPI2 error still pops up in the log. Is this related to BE at all?

[itsmeaffinity]

Hi

Can you please link below to see if that help

http://technet.microsoft.com/en-us/library/cc734021%28WS.10%29.aspx

http://social.technet.microsoft.com/Forums/en-US/itprovistasp/thread/14abbc90-cab5-4fc6-953a-96c1929f9a7b/

If that doesn't resolve this then you will have to open case with Microsoft as that event is regarding the Microsoft source & will be out of scope of this backupexec forum

Please mark this solved if this answers your questions

Keep posted

Thank You

[CraigV]

...another external forum you can look at. Doesn't appear to be Symantec-related...

http://social.technet.microsoft.com/Forums/en/itprovistasp/thread/14abbc90-cab5-4fc6-953a-96c1929f9a...

[itsmeaffinity]

OOPS......1

Seems to be same link what i have posted for forum craig.

Thank You :)

[Doofus1980]

Hi,

I have done this http://technet.microsoft.com/en-us/library/cc734021%28WS.10%29.aspx and I can see Writer Name: 'System Writer' but I still get that CAPI2 error, I'm not sure if it's BE related but even if it's not I'm still getting this errer every morning. It then wants me to start it by logging in with my Windows credentials. The CAPI2 error might be something else, I don't know, just pointed it out because it's the only real error I see in the log. The VSS error seems to have gone away after your help yesterday. Thanks for that :)

[itsmeaffinity]

Hi

Yes for that error if you have done already as per the link then you need to reslove that issue with opening a case with Microsoft

About the backupexec services this happen when you restart the computer everyday & or exactly when

Thank You

[Doofus1980]

Thanks I will go the Microsoft route if that has nothing to do with BE :)

I get this error every morning on the server, I simply lock the server, no restart. So it just stops over night for some reason. I can't seem to find anything obvious in the event log besides the VSS error we got, which has been resolved. Well at least it's not giving me the same error.

Any other event log info I can give to help? :)