01-27-2014 08:09 PM
This is driving me nuts,
Envirement: Sharepoint 2007 on Win2k3 SP2 (workgroup and not on the domain)
BE2012 on Win2k8 R2
Hello peeps,
I hope i will find a life saver here,
our two sharepoint server are standalons and when trying to back up their databases i'm getting this wired errors.
Backup- Shared Search Index\Search-DB 1 (SPServer\OFFICESERVERS\SharedServices1_Search_DB_d696b2ed-0af1-423c-95e1-50625736b8ec)
V-79-57344-794 - Error: Unable to query the Team database meta-data.
Backup- SharedServices1\Services-DB 1 (SPServer\OFFICESERVERS\SharedServices1_DB_c7706c2f-cecb-4ca4-95e9-7862636c19cf)
V-79-57344-794 - Error: Unable to query the Team database meta-data.
Permissions are correct and agent installed localy (Tried to run the job with the local admin account or the Service account but no luck)
backing up the jobs using the Microsoft Sharepoint Ressources as it has been advised on this forum and not using the MS SQL Server Instance.
Appreciate your help guys
Solved! Go to Solution.
03-21-2014 12:52 PM
hell all,
just an update abou this issue which was caused by the sharepoint site.
The exception is self explaining: the issue in the the url of your "My Sites".
you have to check the typed url in "My Sites" configuration page (central administration).
It could be empty or invalid.
worth a try
Thansk all/
01-27-2014 11:20 PM
Would recommend to ensure Backup Exec & the remote servers are fully patched first.
Secondly, would you pls enable debugging per this KB and either post/pm the logs. - http://www.symantec.com/business/support/index?page=content&id=TECH37467
01-28-2014 02:58 AM
Hello Mourad,
There is high possibility that you are hitting a known issue here as mentioned in the technote
http://www.symantec.com/docs/TECH212800 : Sharepoint backup fails with error 'Error: Unable to query the Team database meta-data.'
I would suggest you to apply the Workaround as mentioned in the technote till the issue is permanently resolved. Also do subscribe to this technote so that you will receive a notification email when the issue is fixed.
Regards,
-Sush...
01-28-2014 08:10 AM
01-28-2014 08:51 AM
Is the Sharepoint server 32 or 64 bits? what version of SQL? check and make sure your configuration is supported in the Backup Exec 2012 SCL http://www.symantec.com/docs/TECH175581
01-28-2014 09:47 AM
Thanks for the reply guys but done my home work before installing BE2012
FYI:
SQL 2008 R2 SP1
SP 2007 SP1
Server 2003 SP2
Thanks
01-28-2014 10:23 AM
Make sure Backup Exec and the remote servers are fully patched, as Vivek Jain recommended.
01-28-2014 06:21 PM
... then why did you say
Envirement: Sharepoint 2003 on Win2k3 SP2 (workgroup and not on the domain)
in your initial post.
01-28-2014 07:03 PM
My bad dude, this is a Sharepoint2007 and not 2003
01-28-2014 07:04 PM
My mistake here, this is a sharepoint 2007 and not 2003.
01-28-2014 07:04 PM
I wilkl have a look into that, thanks for your reply
01-28-2014 07:11 PM
this is a log where I've captured the error (Attached Doc file.),
for some reason the job starts and get's around 25GB of data from this machine and then once it starts the SQL DBs, the jobs comeback with errors.
I really appreciate your help people and thanks for the effort again.
much appreciated,
01-28-2014 07:11 PM
My Mistake again and thanks for Mister pkh for bringing this,
mu SharePoint is 2007 and not 2003
Thanks again pkh
01-29-2014 05:52 AM
Hello all,
Just to add, I have done a quick test thjis mornig and attached is the authentication result
01-29-2014 05:56 AM
Hello Mourad,
As I have posted before I still feel this issue is as mentioned in the technote
http://www.symantec.com/docs/TECH212800
Can you run the job and post the error from SPSWRAPPER log to confirm the same?
Regards,
-Sush...
02-04-2014 01:27 PM
Again, here are teh logs from the Sharepoint server and I cant see anything unusual here,
I appreciate your help Community.
03-21-2014 12:52 PM
hell all,
just an update abou this issue which was caused by the sharepoint site.
The exception is self explaining: the issue in the the url of your "My Sites".
you have to check the typed url in "My Sites" configuration page (central administration).
It could be empty or invalid.
worth a try
Thansk all/