Error messages

4070 Topics

VSS timeout issues, restart not suitable solution
Hello I have had continual issues with vss writers time outs on one of our machines we are backing up. Running Windows Server 2008R2 SP1, using BE2010 R3 SP1 The vss writers continue to cause the backup to fail due to timeout. They restart fixes the error status on the writers, but they will time out almost each and every time i run the job. The tech's say i have the job setup correctly, with aofo selected, ms volume shadow copy service(windows 2003 and later) selected and System-use microsoft software shadow copy provider selected. And backup files following junction points. I have selected "Process logical volumes for backup one at a time" too see if this helps. Any suggestions on fixes, besides contanct MS? We don't have support with MS, and as we are suggested to use their system writers by symantec, i would hope that Symantec would provide better aid in fixing VSS issues. Thanks for the help vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool (C) Copyright 2001-2005 Microsoft Corp. Writer name: 'Task Scheduler Writer' Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124} Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b} State: [1] Stable Last error: No error Writer name: 'VSS Metadata Store Writer' Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06} Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93} State: [1] Stable Last error: No error Writer name: 'Performance Counters Writer' Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2} Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381} State: [1] Stable Last error: No error Writer name: 'System Writer' Writer Id: {e8132975-6f93-4464-a53e-1050253ae220} Writer Instance Id: {bcedc94e-0c21-4212-8bbf-b65083123138} State: [9] Failed Last error: Timed out Writer name: 'ASR Writer' Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4} Writer Instance Id: {fe09e27a-4aef-4e90-bbd3-2308b5d8c6ae} State: [1] Stable Last error: No error Writer name: 'Shadow Copy Optimization Writer' Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f} Writer Instance Id: {e6368e5a-147a-4561-bf1e-d46989773b71} State: [1] Stable Last error: No error Writer name: 'Registry Writer' Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485} Writer Instance Id: {47a3c30f-0074-4427-9937-749e88f3e5b0} State: [1] Stable Last error: No error Writer name: 'COM+ REGDB Writer' Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f} Writer Instance Id: {f054ffeb-46ea-4d21-b9b3-b4c040a31214} State: [1] Stable Last error: No error Writer name: 'BITS Writer' Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0} Writer Instance Id: {3e2f6dc9-6533-4fad-9658-ece31839d8bf} State: [1] Stable Last error: No error Writer name: 'IIS Config Writer' Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6} Writer Instance Id: {f28b57b4-4222-497d-b54f-e75269db970e} State: [9] Failed Last error: Timed out Writer name: 'WMI Writer' Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0} Writer Instance Id: {d50d5687-717b-4535-b70f-bee3ecb3f177} State: [9] Failed Last error: Timed out
Solved
Giermo
12 years ago Place Backup Exec
30KViews
2likes
9Comments
Ready; No idle devices are available
I'm new to Symantec Backup Exec as I've taken over the duties of someone else that left the company. The problem that I'm having is I can't get Backup Exec to backup anything, not to tape, not to a shared drive, etc.. Logically I would have thought the issue was that the previous employee had used his account for all Symantec functions, I was able to change his account information for all the services and the connection to the server. Everything appears to be fine, I'm able to do a Test Run without any problems but when I go to do a backup I don't receive any alerts I just get a message that says "Ready; No Idle devices are available". Same result no matter where I try to backup to. Anyone seen this before, have any suggestions of how I can fix it? We're using Backup Exec 2012 S1a. Thanks
Cyprusg21
12 years ago Place Backup Exec
28KViews
1like
11Comments
Backup exec management services could not be started
I am facing issue in Backup exec 2014. When i started backup exec console then it first ask for credentials and then gave an error "Backup exec management services could not be started. Backup exec database is offline, turn it online then restart backup exec services" i re install the backup exec 2014 but still have the same issue. Platform consist of Windows server 2008 R2 standard and also it consist of SQL 2008 which is running by client but Backup exec database use its built in database.
Solved
Kashan_Nawaz
10 years ago Place Backup Exec
22KViews
1like
14Comments
Snapshot provider error (0xE000FED1): A failure occurred querying the Writer status.
Running Backup Exec 12.0 Small Business Server Suite Rev. 1364 og getting random failing file data-backupjobs with error code E000FED1: Backup- E: DataV-79-57344-34110 - AOFO: Initialization failure on: "Shadow?Copy?Components". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS). Snapshot provider error (0xE000FED1): A failure occurred querying the Writer status. Check the Windows Event Viewer for details. Writer Name: Event Logs, Writer ID: {EEE8C692-67ED-4250-8D86-390603070D00}, Last error: The VSS Writer timed out (0x800423f2), State: Failed during freeze operation (9). Writer Name: Windows Internet Name Service, Writer ID: {F08C1483-8407-4A26-8C26-6C267A629741}, Last error: The VSS Writer timed out (0x800423f2), State: Failed during thaw operation (10). When runningVSSADMIN LIST WRITERS - command from prompt I'm given the following output: C:\Documents and Settings\xxx>VSSADMIN LIST WRITERS vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool (C) Copyright 2001 Microsoft Corp. Writer name: 'System Writer' Writer Id: {e8132975-6f93-4464-a53e-1050253ae220} Writer Instance Id: {e1eae7cb-e621-4ab2-ba63-e5a534cc5e7a} State: [1] Stable Last error: No error Writer name: 'FRS Writer' Writer Id: {d76f5a28-3092-4589-ba48-2958fb88ce29} Writer Instance Id: {51359454-ca5e-44f2-bbde-6fd81712dcc1} State: [1] Stable Last error: No error Writer name: 'SqlServerWriter' Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a} Writer Instance Id: {dc2f12b7-d951-41ba-8724-bc474e7a5f7e} State: [1] Stable Last error: No error Writer name: 'MSDEWriter' Writer Id: {f8544ac1-0611-4fa5-b04b-f7ee00b03277} Writer Instance Id: {5cb6d93a-bb72-4a0d-b90b-e6174402c580} State: [1] Stable Last error: No error Writer name: 'WINS Jet Writer' Writer Id: {f08c1483-8407-4a26-8c26-6c267a629741} Writer Instance Id: {a0bbbb7a-8d3d-47ae-93b2-7f7e008365d0} State: [10] Failed Last error: Retryable error Writer name: 'NTDS' Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757} Writer Instance Id: {3be2277a-66e1-43f1-a484-446320b9681f} State: [1] Stable Last error: No error Writer name: 'COM+ REGDB Writer' Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f} Writer Instance Id: {23e6136d-6943-4108-90cb-a40089bad1b9} State: [1] Stable Last error: No error Writer name: 'Registry Writer' Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485} Writer Instance Id: {8ae68311-ead2-4af4-8009-874337783ecc} State: [1] Stable Last error: No error Writer name: 'Event Log Writer' Writer Id: {eee8c692-67ed-4250-8d86-390603070d00} Writer Instance Id: {bc0eb6b5-835b-4a97-a8d0-7ba5f6db426e} State: [1] Stable Last error: No error Writer name: 'IIS Metabase Writer' Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366} Writer Instance Id: {8a3a101e-0dfd-46a2-9334-8ac0d57bf929} State: [1] Stable Last error: No error Writer name: 'WMI Writer' Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0} Writer Instance Id: {af7bf8db-a57e-47a8-a0b5-3a754d46f58a} State: [1] Stable Last error: No error The following warnings and errors is shown in Windows Event Viewer: Event Type: Error Event Source: ESENT Event Category: ShadowCopy Event ID: 2004 Date: 09-10-2012 Time: 01:09:09 User: N/A Computer: SERVER01 Description: wins (3316) Shadow copy 13 time-out (70000 ms). Event Type: Warning Event Source: VSS Event Category: None Event ID: 12290 Date: 09-10-2012 Time: 01:09:29 User: N/A Computer: SERVER01 Description: Volume Shadow Copy Service warning: ESENT ERROR {f08c1483-8407-4a26-8c26-6c267a629741} WINS Jet Writer: -2402. hr = 0x00000000. Event Type: Error Event Source: Backup Exec Event Category: None Event ID: 34113 Date: 09-10-2012 Time: 06:20:30 User: N/A Computer: SERVER01 Description: Backup Exec Alert: Job Failed (Server: "SERVER01") (Job: "MANDAG-DATA") MANDAG-DATA -- The job failed with the following error: A failure occurred querying the Writer status. The data selected for the backup-job is pure files and System State. The server is a Windows Small Business Server 2003 SP2.
Solved
MJ_TIT
13 years ago Place Backup Exec
18KViews
1like
12Comments
A failure occurred querying the Writer status.
Dear all, Since some weeks I have been experiencing this horrible error. I have consulted the Symantec Support pages, but I can find no 'permanent' solution for the environment I am using. Rebooting the server every day is not an option, this is the fileserver that people access remotely almost nearly 24/7. It also doesn't seem to work, the first one or two backups after a reboot work but then it just goes back into the error listen in this threads topic. There is also a suggestion about freeing more space on C:\, I think there is enough (see below). My backup server is Windows Server 2008 R2 Standard. It's fully up to date up with the most recent Windows Updates. This is a physical server. The server I am having trouble with is Windows Server 2012 Standard. It's fully up to date up with the most recent Windows Updates. This is also a physical server. It has a C:\ drive with 125GB free of 150GB It has a D:\ drive with 1.6TB free of 1.6TB It has an E:\ drive with 2.2TB free of 5.5TB I have attached a screenshot showing the amount of times this server won't backup properly because of the above error. The worst thing about it is because I am backup up such an immense amoutn of data it takes about 25-30 hours to do a full backup. But it doesn't go into error until it's completely done! How can it POSSIBLY give a Writer error status at the very end of the backup process!! How is that even possible? The writer error is about failing to make a snapshot, why does it not INSTANTLY see that theres a problem and goes into error, why do I have to wait for 30 hours in anticipation to see if the backup software does why I purchased it. I have 53 servers to backup which takes me over four days, if my fileserver goes into error my entire backup schedule for that week goes out the window. This is becoming increasingly annoying.I don't want to have to come in on weekends because the backup software andomly decides it doesn't want to work. I'd like to add that my Exchange server also experiences this problem, except not that often. It's just as annoying though as you can understand that if my fileserver gets used 24/7 the Exchange server can't exactly get a daily reboot either. It's even more of a pita to reboot. All my other servers never have any problems, physical or virtual. Hyper-V or V-Sphere. It just works. Please advise. Thanks
Solved
Notlupus
11 years ago Place Backup Exec
17KViews
1like
7Comments
all devices stuck at "discovering devices
I have an issue with my media servers where all devices get stuck at "discovering devices" and service restart or reboot of the server. We are running BE2010R3 on windows server 2008r2 platform. I know back in the day there was a regedit for diodrivers as a temp fix, but need to get this resolved permanently ASAP.
Solved
208923557
12 years ago Place Backup Exec
16KViews
1like
5Comments
Backup Exec 2014_TCP error code 10061: no connection could be made because the target machine actively refused
Hi everyone I need some help. I have installed Symantec Backup Exec 2014 on a Windows Server 2012 R2 Std. I have use the local administrator account for the installation and the login. The installation have been quite easy. However, when I start Backup Exec 2014 it always give me an error msg: "Could not connect to net.tcp//[server_name]:50104/BEMService/ServerData. The connection attempt lasted for a time span of 00:00:02.0002511. TCP error code 10061: No connection could be made because the target machine actively refused it [server_ip]:50104." I have found that some users have posted this problem on the forum. I have try to have a look about the solution proposed in the forum. Like creating a new rule in the Firewall setting, I have also disable the firewall. The problem is still there. I have noticed that some services is not started. Unfortunately, I cannot start them. They always give error message like: "Error 1068: The dependancy service or group failed to start". The services are: Backup Exec Remote Agent for Windows Backup Exec Agent for Browser Backup Exec Device & Media Service Backup Exec Job Engine Backup Exec Management Service Backup Exec Server I have try tochange the services execute path using administrative command in windows environment,the problem is still the same. Can someone help me please ... Thanks.
Solved
David_Elizabeth
11 years ago Place Backup Exec
16KViews
1like
6Comments
Unable to establish trust with Backuped hosts.
I have 3 BE 2012 (version 14.0 Rev. 1798 64-bit) and menegement point on one of them. one server can't establish connection and backup jobs fails on it: "The job failed with the following error: Backup Exec cannot connect to the remote computer because a trust was not established between that computer and the Backup Exec server. From the list of servers in the Backup Exec administration console, right-click the remote computer and then click Establish Trust." I try reestablish trust, but I get: I receive this mistake from other backup jobs on this backup exec 2012 server. What can i do? I didn't find anybody solutions.
Solved
apomazkin
11 years ago Place Backup Exec
15KViews
1like
8Comments
Backup job Fails: Error e0008488 Access Is Denied
Hi Guys I am struggling with the following error on my Backup Exec 2010 Media Server: The backupfailedwith error code: e0008488 - Access Is Denied Agent Used: No AOFO Used: Yes I am trying to backup a NAS Device I need to urgently backup the NAS Device and therefore had allocated 4 Tapes to the Scratch Media Set for this Job as i intend to do it manually until i have a succesfull backup set. This is theonlybackup job scheduled at the moment. Weird thing is it does'nt state 'what' was it that the access was denied to ? It does'nt give me any file names under Set Detail Information - Backup. It only gives me a set of filenames which were either 'skipped' or detected as 'corrupt'. Under the Devices Tab i See that 2 Tapes have been written to completely. The 3rd tape is almost 90% full but did not complete (probably due to the error) and the 4th tape is still in the Scratch Media Set. I looked into the following article:http://www.symantec.com/business/support/index?page=content&id=TECH71644&profileURL=https%3A%2F%2Fsymaccount-profile.symantec.com%2FSSO%2Findex.jsp%3FssoID%3D1375605283542jGBWRVRpNH2H4odkBn89L2AXb8CcbYNUCxc2D Out of the 4causes listed in the above article for the error, i could not find any one of the 4 to be of any relevance in this scenario. Any help is appreciated. Thanks a Lot !
Solved
Mac1983
12 years ago Place Backup Exec
13KViews
1like
11Comments
Event 1023 Windows cannot load the extensible counter DLL Backup Exec.
I am getting the following events from our newly build server 2012 r2 server with BE 15. I am not sure what is causing this issue, but it appears to be related to BE and performance counters. Log Name: Application Source: Microsoft-Windows-Perflib Date: 4/24/2015 11:02:17 AM Event ID: 1008 Task Category: None Level: Error Keywords: Classic User: N/A Computer: XXXXXXX Description: The Open Procedure for service "BITS" in DLL "C:\Windows\System32\bitsperf.dll" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section contains the error code. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-Perflib" Guid="{13B197BD-7CEE-4B4E-8DD0-59314CE374CE}" EventSourceName="Perflib" /> <EventID Qualifiers="49152">1008</EventID> <Version>0</Version> <Level>2</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2015-04-24T18:02:17.000000000Z" /> <EventRecordID>3405</EventRecordID> <Correlation /> <Execution ProcessID="0" ThreadID="0" /> <Channel>Application</Channel> <Computer>XXXXXXX</Computer> <Security /> </System> <UserData> <EventXML xmlns="Perflib"> <param1>BITS</param1> <param2>C:\Windows\System32\bitsperf.dll</param2> <binaryDataSize>4</binaryDataSize> <binaryData>02000000</binaryData> </EventXML> </UserData> </Event> Log Name: Application Source: Microsoft-Windows-Perflib Date: 4/24/2015 10:53:43 AM Event ID: 1023 Task Category: None Level: Error Keywords: Classic User: N/A Computer: XXXXX Description: Windows cannot load the extensible counter DLL Backup Exec. The first four bytes (DWORD) of the Data section contains the Windows error code. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-Perflib" Guid="{13B197BD-7CEE-4B4E-8DD0-59314CE374CE}" EventSourceName="Perflib" /> <EventID Qualifiers="49152">1023</EventID> <Version>0</Version> <Level>2</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2015-04-24T17:53:43.000000000Z" /> <EventRecordID>3403</EventRecordID> <Correlation /> <Execution ProcessID="0" ThreadID="0" /> <Channel>Application</Channel> <Computer>XXXXXX</Computer> <Security /> </System> <UserData> <EventXML xmlns="Perflib"> <param1>Backup Exec</param1> <binaryDataSize>4</binaryDataSize> <binaryData>7E000000</binaryData> </EventXML> </UserData> </Event>
Vdang
10 years ago Place Backup Exec
12KViews
0likes
4Comments