Re: Help - Backup not working after trying to get ISA 2004 to log to SQL
- From: "Mark" <nospam@xxxxxxxxxxxxx>
- Date: Fri, 9 Jun 2006 12:57:01 +0930
Thanks for your replies.
In cliconfig, Shared memory protocol was already enabled. On the Alias tab,
there was an alias set up that had <servername> as the alias, pointing to
<servername>. Seems redundant, and (I think)was causing two SQL instances of
<servername> to show up in DSN creation wizard, so I deleted the alias.
I did a lot of restarting the SQL, WSUS and VSS services, but didn't make
any other configuration changes. It seems to have resolved itself, and is
working OK again now despite the only change being deleting the alias. Very
weird.
I'm concerned that I didn't figure out the cause of this fault, but am happy
that backups and WSUS are working again.
Thanks,
Mark
But there was also an Alias set up for
"David Copeland [MSFT]" <davidcop@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:Odq3RExiGHA.4716@xxxxxxxxxxxxxxxxxxxxxxx
Mark,
Check to verify that the shared memory protocol is enabled. Check by
doing Start/Run/cliconfg and verify that the checkbox for Enable shared
memory protocol is selected.
If you uninstalled SQL 2000 with SP4 on it then you may also want to check
the following kb article as well..
http://support.microsoft.com/default.aspx?scid=kb;en-us;918767
--
Hope that helps,
David Copeland
Microsoft Small Business Server Support
This posting is provided "AS IS" with no warranties, and confers no
rights.
SBS Newsgroups:
SBS v4.x: microsoft.public.backoffice.smallbiz
SBS 2000: microsoft.public.backoffice.smallbiz2000
SBS 2003: microsoft.public.windows.server.sbs
"Mark" <nospam@xxxxxxxxxxxxx> wrote in message
news:epN2LGuiGHA.4056@xxxxxxxxxxxxxxxxxxxxxxx
Hi All,
My SBS 2003 Premium SP1 has a problem
I tried to set up ISA 2004 to log to SQL following this MS KB: 838710
http://support.microsoft.com/default.aspx?scid=kb;en-us;838710
I couldn't get logging to SQL working, so reversed the steps in that KB.
Since then, backups and WSUS no longer work. I'm mainly concerned with
fixing backups, and think that if I can work out how, then WSUS will
probably be fixed by the same solution.
Backup log file shows this error:
=====================<BEGIN NTBACKUP LOG FILE>=====================
Backup Status
Operation: Backup
Active backup destination: LTO Ultrium
Media name: "Media created 6/06/2006 at 11:30 PM"
Volume shadow copy creation: Attempt 1.
Timeout before function completed
Error returned while creating the volume shadow copy:0xffffffff.
Error returned while creating the volume shadow copy:ffffffff
Aborting Backup.
=====================================
This is in the event log:
===============
Event Type: Error
Event Source: VSS
Event Category: None
Event ID: 6013
Date: 8/06/2006
Time: 7:01:27 PM
User: N/A
Computer: CS1
Description:
Sqllib error: OLEDB Error encountered calling IDBInitialize::Initialize.
hr = 0x80004005. SQLSTATE: 08001, Native Error: 14
Error state: 1, Severity: 16
Source: Microsoft OLE DB Provider for SQL Server
Error message: [DBNETLIB][ConnectionOpen (Invalid Instance()).]Invalid
connection.
Event Type: Error
Event Source: Windows Server Update Services
Event Category: Update Services Service
Event ID: 421
Date: 8/06/2006
Time: 7:05:45 PM
User: N/A
Computer: CS1
Description:
Connection to database failed. Reason=Invalid connection.. Connection
string: Data Source=CS1;Initial Catalog=SUSDB;Connection
Timeout=60;Application Name=WSUS SQL
Connection;Trusted_Connection=Yes;Pooling='true'; Max Pool Size = 100
===============================
I've hunted around on google for an answer but am hesitant to change
anything outside the scope of the KB above, as I don't want to make
things worse. I've re-checked that I reversed my steps in the KB article,
but things are still not working despite many reboots.
I'm thinking I may need to recreate the System DSN called 'LocalServer'
under Data Sources (ODBC), or at least verify what the settings should
be. If there's any way to test if this is the problem, I'd appreciate it.
Any other ideas are welcome too!
Thanks in advance,
Mark
.
- References:
- Help - Backup not working after trying to get ISA 2004 to log to SQL
- From: Mark
- Re: Help - Backup not working after trying to get ISA 2004 to log to SQL
- From: David Copeland [MSFT]
- Help - Backup not working after trying to get ISA 2004 to log to SQL
- Prev by Date: Re: External Reply Address to Internal Mail
- Next by Date: Re: Vanishing email
- Previous by thread: Re: Help - Backup not working after trying to get ISA 2004 to log to SQL
- Next by thread: Allow users/groups write acces to "C" drive on Terminal Server
- Index(es):
Relevant Pages
|