02-24-2013 12:28 PM
Hi guys,
i am getting this error while trying to open a technical support case. I am filling all required data with a valid support contract
CaseOwner_AutoFollowUnFollowCase: execution of AfterInsert caused by: System.DmlException: Insert failed. First exception on row 0; first error: INVALID_CROSS_REFERENCE_KEY, This user cannot follow any other users or records: [] Trigger.CaseOwner_AutoFollowUnFollowCase: line 103, column 1
any idea?
02-24-2013 03:26 PM
Hi
Please contact Customer Support by calling on 18006344747. So that they can help you to fix the issue with managing cases online by web.
Also you can use below link to use different ways to contact Symantec
http://www.symantec.com/support/contact_techsupp_static.jsp
Hope that helps
Thanks
02-24-2013 10:12 PM
Walid: the other option, while waiting for support to get back to you, is to post the error here and see if anybody can assist you.
Thanks!
02-24-2013 10:38 PM
Thank you all for your support.
I will share the issue here as well.
I am getting the below when i try to backup SQL DBs. My troubleshooting scenario revealed that the error is happening while trying to backup a specific DB. This specific DB which is failing the job represents our most critical DB, the applications DB.
02-24-2013 11:01 PM
Is this dB part of the same SQL instance or a different one ? Does a dbcc check come out fine for this dB ?
02-24-2013 11:28 PM
Hi,
Which version of BE is this?
Have you tried the following:
1. From a command prompt, run: vssadmin list writers. Your VSS writers must all be running and stable. If not, restart the server and try again.
2. Check to see if the RAWS agent stopped during the backup, or is currently stopped.
3. Make sure your media server is fully patched, and that these patches have been push-installed to any remote servers you might have!
Also, it isn't recommended that you use AOFO when backing up DBs...let VSS do it's thing.
Thanks!
02-24-2013 11:50 PM
"A communications failure has occurred with a SQL Server resource." occurs when attempting to backup an SQL Database.
0xe000ff19 - A communications failure has occurred with a SQL Server resource. V-79-57344-65305 - The database server is not responding. Backup set canceled.
The errors below may also show in the event logs.
Event Type: Error
Event Source: SQLVDI
Event Category: None
Event ID: 1
Date: 3/8/2010
Time: 10:01:44 AM
User: N/A
Computer: SERVER
Description:
SQLVDI: Loc=TriggerAbort. Desc=invoked. ErrorCode=(0). Process=1616. Thread=4376. Server. Instance=MSSQLSERVER. VD=Global\NovaStorBackup_00__0dfb0e38_b466_47af_9c51_7d13107e9b12__SQLVDIMemoryName_0.
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 18210
Date: 3/8/2010
Time: 10:01:45 AM
User: administrator
Computer: SERVER
Description:
BackupVirtualDeviceFile::RequestDurableMedia: Flush failure on backup device '_00__0dfb0e38_b466_47af_9c51_7d13107e9b12_'. Operating system error 995 (The I/O operation has been aborted because of either a thread exit or an application request.).
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (6)
Event ID: 3041
Date: 3/8/2010
Time: 10:01:45 AM
User: administrator
Computer: SERVER
Description:
BACKUP failed to complete the command BACKUP DATABASE. Check the backup application log for details
.
3. If the error continues, re-register both the "SQLVDI.dll" files which are located in the following SQL Directory locations
X:\Program Files\Microsoft SQL Server\80\COM
X:\Program Files\Microsoft SQL Server\80\Tools\Binn
Register both the files with the "Regsvr32" command and run the backup job again.
02-24-2013 11:58 PM
...in future, please don't plagiarise official Symantec TNs...put in the link!
THanks!