Failed to get configuration from server

• 
  Margaret,
  
  Look here for answers http://www.red-gate.com/SupportCenter/C ... 0710000177
  
  HTH
  
  Chris

  ChrisAVWood July 12, 2012 10:48

  - 0 +
• 
  I can't even get my GUID to connect to the database, so can't configure these things as suggested in the one article. The other article says to check memory on the server -- there is plenty of available memory.

  eyespi20 July 12, 2012 11:08

  - 0 +
• 
  Could you please check the Windows Event log to see if there were any entries raised by the SQLVDI component at around the time of the error (7/11/2012 3:00:00 AM)?
  
  Thank you.

  petey July 12, 2012 11:23

  - 0 +
• 
  The Windows error log has no errors in it at all.

  eyespi20 July 12, 2012 11:27

  - 0 +
• 
  Looking on my machine (where I'm running the GUID from) I have the following error:
  
  ngWrapper.LogManager
  #6:Failed to load assembly Microsoft.SqlServer.SqlEnum

  eyespi20 July 12, 2012 11:42

  - 0 +
• 
  Margaret,
  
  You didn't mention the O/S or SQL version. This might help understand things a little better.
  
  Chris

  ChrisAVWood July 12, 2012 14:42

  - 0 +
• 
  The SQL box is running Windows Server 2003 and SQL 2008 R2 SP2. My personal computer is running Windows 7 Professional.

  eyespi20 July 12, 2012 14:51

  - 0 +
• 
  Unless you mean SQL2008R2 SP2 CTP I don't believe that version is freely available yet.
  
  Is this 32 or 64 bit and how much memory does the server have and are you giving to SQL?
  
  Chris

  ChrisAVWood July 12, 2012 14:57

  - 0 +
• 
  Microsoft SQL Server 2008 R2 (SP1) - 10.50.2500.0 (X64) Jun 17 2011 00:54:03 Copyright (c) Microsoft Corporation Standard Edition (64-bit) on Windows NT 5.2 <X64> (Build 3790: Service Pack 2)

  eyespi20 July 12, 2012 14:58

  - 0 +
• 
  SLQ server is allocated 28GB and there is 32 GB of RAM on the server.

  eyespi20 July 12, 2012 15:01

  - 0 +
• 
  There doesn't appear to be any fixes in the CU's raised after SP1 that talk about memory.
  
  Red Gate SQLBackup uses the vas space in SQL which defaults to 256Mb in SQL2008R2. If this was changed you would see a line like this -g 400 in the SQL errorlog after lines like -l \DBMS\MSSQL.1\MSSQL\DATA\mastlog.ldf to indicate where the master db log is after the last SQL startup.
  
  I am not currently using SQLBackup on any SQL2008R2 servers but saw this error many times in SQL2005 running on W2K3R2 SP2.
  
  A -g can be added to the startup of SQL but it would need to be stopped and restarted for it to apply.
  
  Chris

  ChrisAVWood July 12, 2012 15:35

  - 0 +
• 
  I stopped and restarted the SQL Backup Agent and that seems to have solved the problem for now. no idea why it stopped working which I would like to know.

  eyespi20 July 12, 2012 15:36

  - 0 +
• 
  Do you use CLR routines and do you see any AppDomain 6 (AAA_BBB.dbo[runtime].5) is marked for unload due to memory pressure messages in the errorlog?
  
  if you do then your problem could well be lack of contiguous memory in the vas.
  
  Chris

  ChrisAVWood July 12, 2012 15:43

  - 0 +
• 
  No we don't use any CLR routines.

  eyespi20 July 12, 2012 15:56

  - 0 +
• 
  SQL Backup uses the SQL Server Virtual Device Interface (VDI) to back up and restore databases.
  
  In your case, the VDI is raising error 80070008, which is undocumented in the VDI specification. Hence, I can't tell exactly what went wrong. In most cases, SQL Server will add an entry to the Windows event log providing more details about the VDI error e.g.
  
  
  
  You could also try looking in the SQL Server error log to see if any errors were recorded.

  petey July 13, 2012 04:20

  - 0 +

Add comment

Please sign in to leave a comment.